I do not know what happened, but it all works now.
I have tried several times with restart of both printer and PC in between. Maybe it comes back.
When upload from slicer failed I still could upload from DWC.
No errors, except within Slic3r when trying to upload.
I have installed latest DWC but I am not using it. I had failures without connecting with the DWC to the Duet since bootup of the Duet. So I do not thing the new DWC is the cause of this.
I will post again if this problem occurs again.
@zerspaner_gerd said in Firmware 2.02 released!:
M291 no longer allows S0 and T0 together because that would create a message that can never time out of be dismissed
I used it as follows
M291 P"Nozzle is heated" R"Loading Support" S0 T0
G10 S230; TEMP
G1 X125. Y10. F6000
M116 H1:2 S3
M292 ; Hide the message
I see now no way to implement the equivalent after the change.
Maybe we could create a new mode that includes:
Only with the "Cancel" button, to cancel the current process.
That would have been missing before me, because if there is a mistake (for example, unintentional confirm) was the one zigste way to end this with an emergency stop.
What do the other people mean?
Why don't you just set a long timeout instead of no timeout? Or allow it to be dismissed?
the error message was added as a warning. the problems that this causes are present in the previous firmware as well, you just dont get the warning.
for 2.04RC1 see the changelog
The P parameter of the G29 S0 (or plain G29) command has been withdrawn, because it didn't work when deployprobe.g and retractprobe.g files were used and wasn't easy to fix without wasting memory. A new subfunction G29 S3 P"name.csv" has been added to facilitate saving the height map file under a different name. It behaves the same as M374 P"name.csv".
This could explain why my delta's nozzle started engraving the build platform. It didn't happen every time, so I assumed it was my 4 year old, heavily used, printer wearing out, even though I couldn't find much slack. In the end I stripped out all the electronics to go in a second CoreXY machine. I didn't think to roll back to an earlier firmware version. Don't I feel silly now. I've still got the delta chassis, so I may refit it.
@kraegar said in Firmware 2.03 (Duet 2) and 1.24 (Duet 06/085) released:
Yes, I saw that bit. I'm using the offsetson.g / offsetsoff.g work around, regardless.
It's working fine for the other tools, and I'm not seeing any reason it would cause the active Z height to display as -3.30.
The config files + gcode file are all here, should be everything relevant: https://www.dropbox.com/sh/7z7txheqdhdvcjc/AADQY-h_WdGFe1kDW3i2lrYYa?dl=0
Dropping to 2.02 did fix the odd behavior with tool 3's printing at -3.30mm. (It's not coincidence that's the correct Z height of 0.35 minus the offset for the tool, I just can't see a reason it would happen)
Firmware 2.04RC1 is available now. I suggest you try that, and if you think there is still a problem, start a new thread.
@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.
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 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.
Looks like your connection to Duet3D was lost, please wait while we try to reconnect.