Startup m291 not displayed
-
I'm trying to call a macro (...init_derack.g) from config.g which contains:
M561
M291 P"CLEAR THE BUILD AREA!!" R"STARTUP GANTRY DE-RACK" S3 T0G28
M98 P"/macros/zprobe/use_itall.g"
M98 P"/macros/homing/scripts/probe_zlevel.g"
M561The trouble I'm having is the Wifi messages are displaying on the panel due and not letting the M291 startup message display.
Suggestions?
I tried setting notification time out to 0 but then they just persist...also tried the other timings which did not help.
Paneldue firmware 1.23.2
-
Are you trying to home in config.g?
If so you might want to rethink that - it's not something I would recommend.
And as I seem to recall M291 dialogs don't display during startup.
I might be wrong about that though.
-
@fcwilt
I would like to automatically call the scripts on startup or emergency stop...not exactly "home in config.g" hence the M291 S3 with infinite T0 so I can waive the operation if needed.
Problem is the message window with "ok" and "cancel" only appears consistently on a total power down. Emergency stop seems to be different to the paneldue 7i.The scripts are necessary on EVERY loss of holding current to Z motors... so every boot or every E-stop.
-
Firmware version of the Duet?
I don't think using M291 in config.g is going to happen. You might be able to add a call to a separate macro that has your commands in it at the end of config.g maybe even add a few seconds of delay with G4 S5.
The startup up sequence in config.g isn't a good time to start initiating blocking user prompts. You need to give the system time to finish starting up.
I think a better place for your macro might be homeall? You need to home before you can move the motors anyway.
-
@phaedrux
Board: Duet 2 WiFi (2WiFi)
Firmware: RepRapFirmware for Duet 2 WiFi/Ethernet 3.3RC2 (2021-05-11)
Duet WiFi Server Version: 1.26and the panel due firmware is now current at 3.2.11
I'm not calling m291 in config.g as I am calling a separate macro that has my commands in it at the end of config.g
I tried dwell and this just delays the wifi message stack and then the m291 is still buried but only on emergency stop. Also after the Due7 is reset or powered down it catches the "pending" m291 message.
It's odd though that the behavior is as expected for a full power cycle or emergency stop combined with panel due reset switch.
It's functional enough I suppose just an interesting limit at this point for me.
-
@printernoodle said in Startup m291 not displayed:
I'm not calling m291 in config.g as I am calling a separate macro that has my commands in it ant the end of config.g
That's basically the same as calling it in config.g.
Is there a reason you cannot simply hit the "home all" button on the DWC or PD after the printer is powered up?
Thanks.
-
Oh sure it's because the gantry de-rack is typically a few mm....but can be as much as 10 or more mm depending on which moron has had their way with the machine....so a special de-rack with a suitably large dive value is called so as to avoid the creaming of the bed. Then every sliced print can call a simple g28 which will home everything much more accurately and quickly without the large dive to correct for error which is no longer there.
Thank you!
-
@printernoodle said in Startup m291 not displayed:
Oh sure it's because the gantry de-rack is typically a few mm....but can be as much as 10 or more mm depending on which moron has had their way with the machine....so a special de-rack with a suitably large dive value is called so as to avoid the creaming of the bed. Then every sliced print can call a simple g28 which will home everything much more accurately and quickly without the large dive to correct for error which is no longer there.
Thank you!
Thanks but I have no idea what you are talking about.
