Maestro config not being executed on startup
-
try running M98 Pconfig.g and see if it complains about any errors?
-
I get these two errors:
Error: M911: No power fail script provided
Error: G0/G1: insufficient axes homed -
not too familiar with how the firmware handles errors, but does it make a difference to move the network config block up to over the M911 command? or commenting out the offending lines with a ;
-
Ah yep so I got rid of the M911 line from the config and that's fixed it. The error must have been stopping the Duet from reading the rest of the config file. Thanks heaps for the help.
-
-
@joshl said in Maestro config not being executed on startup:
M911 S21 R23 P'M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000' ; set voltage thresholds and actions to run on power loss
I can't see anything particularly wrong with this line, except you've used single quotes rather than double quotes. However, you probably need to set up the sys/resurrect-prologue.g file.
See here for more details: https://duet3d.dozuki.com/Wiki/Setting_up_to_resume_a_print_after_a_power_failureIan
-
@droftarts said in Maestro config not being executed on startup:
I can't see anything particularly wrong with this line, except you've used single quotes rather than double quotes.
According to https://duet3d.dozuki.com/Wiki/Gcode#Section_M911_Configure_auto_save_on_loss_of_power you need to use double quotes for the P parameter.
The messageError: G0/G1: insufficient axes homedleads me to think that the single-quoted P parameter command line from theM911command is being interpreted and executed at config.g runtime as there is aG1command in there. -
@themelle that seems to be the explanation, I was wondering where the G0/G1 line was.
-
@joshl said in Maestro config not being executed on startup:
including going through RepRap firmware configuration tool to generate a config file.
Did the RRF configurator generate the M911 line with single quotes? If so that should probably be filed as a bug
-
@bearer said in Maestro config not being executed on startup:
Did the RRF configurator generate the M911 line with single quotes? If so that should probably be filed as a bug
it is a bug @chrishamm
-
I would move the whole network section of g code to almost the top of the config.g file so that the network gets started first...
-
@calvinx said in Maestro config not being executed on startup:
I would move the whole network section of g code to almost the top of the config.g file so that the network gets started first...
seems it was further up earlier, but changed recently, and the quotes bug was introduced at the same time. wonder if that is the reason for the sudden increase in threads with network issues.
anyways, hopefully the quotes will be fixed and the network moved back to the top shortly.
-
The position of the network command shouldn't matter, but the wrong quotes for the power loss recovery halting the execution of the config certainly is a problem.
Oddly, if the network section hadn't been moved down it would have been much harder to spot the wrong quote problem.
-
@phaedrux said in Maestro config not being executed on startup:
The position of the network command shouldn't matter
for users who find it difficult to use the serial terminal it does matter when errors are introduced, further complicated by the missmatch between default EOL in the firmware and the recommended terminal.
if the network were given "priority" at the top, and the web interface and/or paneldue would indicate that config.g was terminated due to an error everyone wins.
-
@bearer No argument there.
One helpful trick for issues like this is to send
M98 Pconfig.gwhich will re-execute config.g as a macro, and any error messages will be echoed back, unlike at startup. I do wish that any startup errors would get punted to the console as well, but currently that's not the case. -
I find Arduino IDE serial monitor really quick and easy to use to talk to Duets and other boards, it has a drop down menu to set line endings and baud rate on the serial window.
