there were a lot of changes to the lcd menu code since 2.01.

i suggest updating to 2.03 and replacing the menu system with this
https://github.com/mudcruzr/Duet-Maestro-12864-Menu-Files/releases

@veti After some research I've found that both of my thermistors had the wrong beta coefficient on Marlin since e3d says to use the TEMP_SENSOR 5 (wich has 4267 K beta value) and that my heatbed thermistor looks like a cheap chinese one with 3950 beta value. So I've put the e3d preset B4725 and C7.060000e-8 for the hotend and B3950 C0 for the heatbed on RRF.

I guess the manufacturer didnt care about the +-150 difference on both thermistors and just went with TEMP_SENSOR 1 on Marlin.

@deckingman said in oops, updated wifi server bin and printer is now offline:

@sethipus If you scroll down the list in the link that @bearer provided, to RRF 1.19, you'll see this in the upgrade notes:

"Important! On a CoreXY machine, if upgrading from a version prior to 1.19beta9, you need to reverse the Y motor direction in the M569 command. Similarly for CoreXYU machines."

Do that and you X Y movement will be restored.

Thanks! I suppose I probably should have read all of the release notes of all the versions of the firmware I just skipped over.

Anyhow, that did it! Btw @deckingman I watched your video about your pressure advance and whatnot, and I was really astounded by your printer. That's just awesome. I just ran that pressure advance testing python gcode generator last night and got some funky results (massively chunky sections where the print speed was 5mm/s, and I mean massive, like 3 or 4 times as wide as when it was at 100mm/s). I'll post about it in that other thread.

I gotta run a print now, just to make sure everything else is working right again. Guys, I appreciate the help. Thanks for helping me get my D-Bot/Duet Wifi back online and apparently functioning properly again after my update screwup from last night.

After a lot of hair pulling I think I got the board working on the bench, however I am unsure what fixed it since I been trying everything I could think off. I did check the guide that Phaedrux suggested I did notice that in /sys there where missing files ... config.json, sleep.g, stop.g, tfree0.g, tpost0.g and tpre0.g. I did generated a new config file downloaded and replaced the /sys. However I was still seeing disconnection to DWC, changed to 1.22.6 from 1.21 once more thereafter I was still experiencing drops every so often. I deleted all saved WiFi's with M588 S"*", re-added my AP with M587 S"networkname" P"password" and finally reset it again with M552 S0 and re-enabled it with M552 S1. cleared cache in my browser and tried again so far so good 🙂
Thank you all for your help!

It looks like M579 works well in 2.02, I'd say something changed between then and 2.04RC1

Phaedrux, thank for the help just some tuning to do now.

Upgrade from 1.22.6 to 1.24 has left the machine invisible on the browser on the .local address but visible on the IP address.

See: https://forum.duet3d.com/topic/11425/upgrade-from-1-22-6-to-1-24-has-goosed-local-addressing/7

@runklestiltskin said in z speed when paused/canceled and beyond:

@deckingman thanks again, I thought, that the both had better interchangeablility.

Recent firmware with accept me of the Marlin specific gcode commands but in the case of max speed they just the same gcode, but different units.

Glad it's all working now.

@3mm said in Update FW for DUET3D WiFi v1.02 Board:

Hey...what do you do in your spare time?

🙂

thanks...3mm

I write RepRapFirmware ☺

@mihaitintea said in Delta X and Y head position change during Z autocalibration:

Calibrated 6 factors using 16 points, deviation before 0.072 after 0.034
Calibrated 6 factors using 16 points, deviation before 3.062 after 0.034
Calibrated 6 factors using 16 points, deviation before 1.234 after 0.032

There is a bug in firmware 2.03 whereby if the firmware updates the delta radius or the rod length, it adjusts the homed height incorrectly. I think that is what is happening in your case, and explains why the deviation went up from 1.234mm to 3.062mm before coming down again. This bug is fixed in the forthcoming 2.04RC1.

Also note that any of the four home buttons (ALL, X, Y, Z) will have the same result on a Delta... all three towers will home... the separation of buttons is really for Cartesian printers.

Thanks a lot for your suggestion! The config.g was on the SD but turns out it was a broken card. I repaced it and followed the tutorial in the wiki you send me. Now the Duet is running the newest updates and works perfect! 😄

I'm looking forward to see my first print results! Thanks again for the support!

Unfortunately that probably means that the WiFi module has failed. However, if you were running M997 S1 with just USB power applied, try again with VIN power applied.

The WiFi module is one of the easier components to replace. The important part is removing the old one without lifting any PCB traces.

@phaedrux said in How can I find the right firmware?:

@zapta yup

Thanks.

Thanks, I contacted him but he told me that I should first open a tread on your forum.
..so I did

its currently in development.

see
https://forum.duet3d.com/topic/10071/reprapfirmware-3-0

@phaedrux said in Help with custom firmware settings for Rostock Max V2 upgrade:

@metallikahn said in Help with custom firmware settings for Rostock Max V2 upgrade:

throwing in a PT100 sensor for me

Don't forget that to use a PT100 you will need the daughter board.

Yep! Included in my first post. Just some of the many $ I've spent with Filastruder in the last couple weeks! 🤣

The fan has to be configured for thermostatic control with the chamber heater or a part cooling fan; which is why if you want it on at all times then you don't need to make a distinction. If you want to vary the speed for different layers on the other hand you'll run into problems with the heater being tuned for one airflow and used for another.

And yes, 180C hot air would cool the PEEK which is printed at more than twice the temperature. Same with 60C hot air for ABS.

@pdbeal, it's highly likely that every Duet Maestro or Ethernet on a LAN will have a different MAC address. It's not guaranteed, because the unique ID is 128 bits long whereas MAC addresses are only 48 bits.