New beta firmware 2.01beta1/1.21.2beta1 available
-
I have just released this at https://github.com/dc42/RepRapFirmware/releases/tag/2.01beta1. This fixes a bunch of mostly minor bugs in the 2.0 release:
- When using a mixing extruder, the feed rate for extruder-only moves was incorrect
- If additional axes were not created in the order UVWABC then incorrect homing files might be run (thanks chrishamm)
- On the Duet Maestro, the 7th stepper step/dir pin numbers were swapped
- If you paused a print during a G2/G3 arc move, on resuming it the arc centre was at the wrong place. This release defers the pause until the arc move is completed.
- If a command that interrogated the network (e.g. M122 on the Duet WiFi) was sent from USB, PanelDue or another non-network channel, the network subsystem could be accessed by multiple tasks concurrently, causing network disconnections or other errors
- When using a bltouch, between probe points the pin retracted, deployed and retracted again
- M206 with no parameters didn't report the current axis offsets
- During heating, the firmware returned M408 S0 responses to the PanelDue port even if the last request was M408 S2
- Fixed VBUS detection (thanks chrishamm)
- If the resume threshold in the M911 command was set higher than the supply voltage then the save-on-power-off mechanism never got primed. It will now prime at the auto-save threshold plus 0.5V or the resume threshold, whichever is lower.
- Fixed "2dtstc2diva=u" in debug printout
- Where a G- or M-code command parameter was supposed to accept unsigned values only, if a negative value was supplied then it was accepted and converted to a large unsigned value
New features and changed behaviour:
- If the firmware gets stuck in a spin loop, the RTOS builds now discard LR and 16 stack dwords in order to get more useful information from the stack trace
- Increased M999 delay to 1 second
- The report generated by M122 now includes a list of mutexes and their owners
- Added SW_ENC pin on CONN_SD to available GPIO ports (thanks chrishamm)
Please note, although I have done test prints with this release, I have not had time to test all the changes. So if you were affected by one of the issues that I have attempted to fix, please report whether the fix has worked for you.
-
@dc42 said in New beta firmware 2.01beta1/1.21.2beta1 available:
If you paused a print during a G2/G3 arc move, on resuming it the arc centre was at the wrong place. This release defers the pause until the arc move is completed.
I'm just imagining the situation while machining some larger part and looking at the spindle going to hit some material holding fixture during a long arc move! This shouldn't happen very often, but it may be a lot more expensive when compared to the original bug (BTW I saw it happening once and couldn't tell what hit me! Luckily I was machining some POM and the end mill survived the wrong re-entry point!).
-
In that situation, I think emergency stop would be more appropriate.
-
@dc42 said in New beta firmware 2.01beta1/1.21.2beta1 available:
- Increased M999 delay to 1 second
Should this change avoid this mistake?
Appears every time trigger "T0"
(M581 E0 S0 T0 C0) -
Possibly.
-
@dc42 were you able to reproduce/fix the issue I had with the Duex5 not being recognized after a reset?
https://forum.duet3d.com/topic/5713/duet2-with-2-0-rtos-looses-duex5-on-reset -
@gtj0 said in New beta firmware 2.01beta1/1.21.2beta1 available:
@dc42 were you able to reproduce/fix the issue I had with the Duex5 not being recognized after a reset?
https://forum.duet3d.com/topic/5713/duet2-with-2-0-rtos-looses-duex5-on-resetI didn't have time to try that, because I needed to get the beta released before I go on vacation. It's on my list to try.
-
Oddly enough, it seems to be working now. Anyway have a good holiday!
-
Updated and started printing last night with this new version. No issues at all so far.
-
@gtj0 said in New beta firmware 2.01beta1/1.21.2beta1 available:
Oddly enough, it seems to be working now. Anyway have a good holiday!
I spoke too soon, about the Duex5 not your holiday :). It seems I'm back to losing it after a reset.
-
The Web Interface of this version is junk.
Why publish an untested Version as beta? This is early alpha. -
@autsch, please explain what problems you are having with the web interface. You can revert to Duet Web Control 1.21 or 1.21.1 if necessary.
-
@dc42, Java script error, if you save settings in the web interface.
I use windows 10, error was in Firefox developer.
Z moved in -Y. -
@dc42, if you want, I could install it this night and write down the errors.
John had the same problem with a Delta in Z axis
https://forum.duet3d.com/topic/5842/weird-z-behavior-with-first-attempt-with-rtos-firmware-on-delta/2
When I tried to open the js.gz, I got an error from Microsoft Scripting host:
-
-
-
just installed the beta 2 today and the Script errors are gone if i want to add a new temp button
-
hi! i did not find a link to b2 and now using b1 .
in webUI it showsError: Can't open 0:/sys/oem.json to read, error code 4
-
There is no b2 - @Barracuda72 is this a typo?
@c310 the oem.json error is normal - only OEM vendors ship this file. "Normal" users can ignore the error.
-
There is a b2 of DWC 1.21.2, it's in chrishamm's github repo.
-
As David stated...no typo
-
Hello,
I am getting an error that I know I am making happen. I currently have V2.0 and I tried to upgrade to 2.01. I downloaded "Duet2CombinedFirmware.bin, loaded it to my DuetWifi, try to update, and I get an error,
'Error: M997: In-application programming binary "iap4e.bin not found'I know this has to be something I am missing, but I dont have any idea where to start looking to fix the problem. Hopefully someone can point me in the direction I need to go to fix this problem.
Thanks
TC -
Maybe try updating the IAP files again?
-
@iamturbo1978, download iap4e.bin from https://github.com/dc42/RepRapFirmware/releases/tag/2.0 and upload it through the Settings General page of DWC.
-
@dc42, Wonderful. Thank you so much for the help.
