M291 / M999 bug
-
Wasn't sure where to put this.. I ran into a bug today that I need to report. I am currently running 3.2b1, so I am unsure if it is specific to it or not.
If you create a macro with the two commands, the M291 is not processed - the M999 is immediately processed. This one should be pretty easy to reproduce..
M291 S3 R"Prompt" P"Prompt" M999 -
See here for what I was working on which exposed the issue:
https://forum.duet3d.com/topic/18797/m80-81-duet-3-toolboard-usage/11
-
Are you running in standalone mode, or on Duet 3 with attached SBC?
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 -
@dc42 Sorry, I should have clarified.. it's a Duet3 / RPi combo running 3.2b1. If there is anything else I can do to help, let me know..
-
This is bigger than just M291 when used with M999. I was modifying the power toggle macro I posted earlier after realizing I needed to add M81 S1 to the script to allow the hotend to cool down - it's not waiting to cool before rebooting.
To test, I created a macro with the following which instantly soft reboots the system and does not wait for the hot end to cool like it should:
M81 S1 M999 -
This is to do with the way that DSF prioritises certain commands. One for @chrishamm.
-
Thanks, I could reproduce and identify the cause of this problem. It is indeed an issue in DSF which will be fixed in the next beta.
