Firmware 2.02 released!
-
Just wanted to say how fantastic it is to finally have the network reconnect after my POS cable modem/router stops working, and I have to reboot the thing. I hated flying blind until the print ended.
Thanks devs
-
Thank you.
What would be great would be an online update function that the board could download the firmware data itself. If that's possible.
(Auto Update Firmware Button on the Webinterface)
With release channels Beta and Stable.
And with update message in the Webinterface when a new Version is available
Also that if you click on Update you will get the realse notes as well. -
@dc42 I tried 2.02 code branch, and init is definitely not right, the startup move takes 30 seconds instead of < 1 seconds. I went back to 2.02RC5 and it's fine. I'll use RC5 until 2.02RC gets sorted out. I have a patch with my mods so I can try new firmware very easy.
EDIT:
I tried 2.02RC6 -- problem persists. Went back to RC5 -- problem goes away -- something was changed between RC5 and RC6 which makes init bootup moves not workEDIT2:
I changed the move to beG1 S2 Y0.1 U0.1 F30000
(I added S2) and now it's fast as before, something between 05 and 06 changed, so without S2 this move on startup takes 30 seconds.
I am on 2.02 and with S2 it works fine -
Hi David,
Same problem for me with 2-02rc6 on my Scara
https://forum.duet3d.com/topic/8155/firmware-2-02rc6-released/5 -
I've been using 2.02 for a few days now and have not noticed any issues myself.
I just installed the new DWC while exploring it, I realized that the new FW also has a way to set material parameters on the machine. I'm really excited to migrate all of my machine/material combo specific firmware parameters out of the slicer and into the machine. This should make it much easier to use various slicers (currently I can only use KISSlicer with my configuration system) while maintaining a well-automated system of parameters for machine/material combos. Thanks for all of your work David!
-
After running a 4 hour or so print, the end stops on the Duex5 don't respond in homing. Worked fine in RC5. I thought it was wiring, or other issues, but seems firmware related -- the lights on the Duex5 change accordingly, but Duet doesn't recognize the end stops as triggered.
edit -- after rebooting the duet, end stops work again.
going back to 2.02RC5. I think end stop changes are in RC7 -- all I was missing in RC5 was the the ditto filament fix,and I migrated that. I can't run a long print and rely on it ending smoothly as it homes some of the Duex5 axes, so I'll be using the RC5 build until there is a solution for end stop issue.
-
@kazolar said in Firmware 2.02 released!:
After running a 4 hour or so print, the end stops on the Duex5 don't respond in homing. Worked fine in RC5. I thought it was wiring, or other issues, but seems firmware related -- the lights on the Duex5 change accordingly, but Duet doesn't recognize the end stops as triggered.
edit -- after rebooting the duet, end stops work again.
I had the same problem yesterday while testing something:
M119 did show that the X axis endstop is triggered while it wasn't. And it didn't change while manually triggering it.
However, the status LED showed the correct status and changed accordingly.
After rebooting it worked again... -
Updated from 2.02 RC4 today and sometimes the Duet just starts refusing uploads without any specific error message after another print is done or canceled. Only a reboot helps then. Sometimes it's even more sporadic - I need to delete a few files before it allows another upload, but I don't even have that many files.
All otherwise it appears to work as expected.
-
@edgars-batna I'm having similar symptoms that after it gets into some confused state, uploads slow down drastically normally at 450-600kbps, then they plumin to 160-180k, so it seems it has something better to do. There seem to be other glitches, so I went back rc5
-
@hurzhurz m119 was showing not triggered for me and led was working, end stops on the duet proper were ok, just appear to not work with end stops on the expansion which for me starts with my 2nd gantry - w axis. I tried bridging the wires by had remocing the plug, only reboot cleared it..
-
I'm having weird homing behavior related to dual limit switches with 2.02. Though, I reverted to rc5 and the problem was still there.
https://forum.duet3d.com/topic/8307/dual-z-homing-weird-behavior-on-u-limit-first/7
-
@leonmf I replied on that thread -- hope that helps you, dual (or more ) z homing works fine in RC5 -- I believe there are some transient issues in 2.02 final -- possibly started with RC7 -- I notice that after a long period of on time there is some issue that builds up which results in a few other oddities, @dc42 -- i.e I noticed a slow down behavior between moves -- for example it moves, then thinks then moves again, the move is not slow (I've see that before), but it thinks a good bit before the next move -- in that state is when it starts to lose end stop triggers.
-
David, I am running rc5 and after over 20 hours of printing, no issues with end stops, it's a 30 hour print, but I just checked the diagnostic page while it's printing and checked the end stops on the duex5 and they work fine. Definitely there was an issue with the new firmware and duex5 end stops.
-
I think the U Axis homing I'm seeing is not 2.02 final specific (even though I believe it to be a real bug).
I'm also seeing a new thing in 2.02 where the first move of any axis after homing any axis is exceptionally slow and ignores the FXXXX parameter. Subsequent moves are fine, though.
-
@kazolar said in Firmware 2.02 released!:
@leonmf I replied on that thread -- hope that helps you, dual (or more ) z homing works fine in RC5 -- I believe there are some transient issues in 2.02 final -- possibly started with RC7 -- I notice that after a long period of on time there is some issue that builds up which results in a few other oddities, @dc42 -- i.e I noticed a slow down behavior between moves -- for example it moves, then thinks then moves again, the move is not slow (I've see that before), but it thinks a good bit before the next move -- in that state is when it starts to lose end stop triggers.
That sort of slow down is usually the result of I2C communication between the Duet and the DueX breaking down. Please check the I2C stats in the M122 report when this happens. The usual cause is a poor ground connection between the VIN terminal blocks of the Duet and the DueX.
Duet WiFi hardware designer and firmware engineer
Please do not ask me for Duet support via PM or email, use the forum
http://www.escher3d.com, https://miscsolutions.wordpress.com -
@kazolar said in Firmware 2.02 released!:
David, I am running rc5 and after over 20 hours of printing, no issues with end stops, it's a 30 hour print, but I just checked the diagnostic page while it's printing and checked the end stops on the duex5 and they work fine. Definitely there was an issue with the new firmware and duex5 end stops.
If/when this happens again, after the print finishes please check:
- The I2C stats in the M122 report
- If you have any fans connected to the DueX then test whether they are still working.
-
@dc42 David, this never happens with rc5, how can it be hardware/wiring related. I'm running rc5 now and haven't had it happen in over 100 hours of printing.
-
@kazolar said in Firmware 2.02 released!:
@dc42 David, this never happens with rc5, how can it be hardware/wiring related. I'm running rc5 now and haven't had it happen in over 100 hours of printing.
Whatever the reason for the problem, I need the results of the tests I requested, to determine whether the I2C comms have stopped working or just the endstops on the DueX5.
-
@dc42 I have a long print project to complete, so I won't be able to roll back to 2.02 final until after it's done. I am in hour 10 of a 2nd 30 hour print, then I have 3 12 hour parts to print out. I can test it on a benchy this weekend -- it is absolutely repeatable after 4+ hours of printing. BTW when it happened I did electrical testing the duet and duex5 -- I tested the 5v, 3.3v and 24v rails for any variants -- and everything was copacetic, my first thought it was wiring related, but everything checked out fine, and since a rollback to rc5 fixed it, I'm sure it's not.
BTW, i have 2 fans blowing across the duet and they're working fine -- duet MCU reports 25-26c even during 20+ hour long print jobs
-
Just wanted to say the new firmware is working fine on my Hypercube Evolution. Only problem I found was that I had to make changes to my config.g to get it to work after upgrading. 2.01 I believe was my old firmware. Now with 2.02 I had to make these changes to config.g to get it to work.
Old settings:
; Axis Limits
M208 X0 Y0 Z0:0 U0 S1 ; Set axis minimumM208 X285 Y270 Z285:285 U285 S0 ; Set axis max
New Settings:
; Axis Limits
M208 X0 Y0 Z0 S1 ; Set axis minimumM208 X285 Y270 Z285 S0 ; Set axis max
What would happen is it would set my Z axis Min and Max to 285mm with the old settings. This would always move the bed to the furthest position from the head and start printing in air. Not on the bed. Those old settings worked fine in the old version but mess things up bad in the latest firmware. Spent about 10 hours trying to figure out this problem.
Hope this is of some help to others that may have problems with Z axis moving strange after upgrading.
