Example of a CONFIG.G file that appears to stop on error
-
Hey @droftarts,
Here is a simple file that shows one time that config.g appears to stop.
I'm not claiming that it always stops on every error, just that there are some that seem to cause it to stop.
This simple example has the type of error that caused my problem where the rest of the file did not seem to be executed.
; =================================================================================================== ; *** TEST *** config.g BOF - printer FT5 - hardware Duet 2 WiFi/Duex 5 - RRF 3.4.6 ; =================================================================================================== ; **************************************************************************************************** ; prologue ; **************************************************************************************************** M111 S0 ; debug off M550 P"FT5" ; machine name (can be anything you like) M555 P1 ; firmware compatibility (P1=RepRap P2=Marlin P6=nanoDLP) M575 P0 B115200 S2 ; communication parameters for USB serial M575 P1 B115200 S1 ; communication parameters for PanelDue M552 S1 ; enable WiFi (S1) M586 S1 P1 T0 R21 ; enable (S1) FTP (P1) Disable TLS (T0) Port (R) M586 S1 P2 T0 R2323 ; enable (S1) Telnet (P2) Disable TLS (T0) Port (R) G21 ; dimensions in mm G90 ; for X,Y,Z use absolute coordinate values M83 ; for E0,E1,etc use relative coordinate values ; **************************************************************************************************** ; testing ; **************************************************************************************************** global G1 = "G1" ; this is the type of error that caused my problem - reference to a non-existant global var ; leave this invalid reference in and check the object browser for global vars - only G1 exists ; comment it out and both G1 and G3 exist set global.G2 = "G2" global G3 = "G3" ; =================================================================================================== ; *** TEST *** config.g EOF - printer FT5 - hardware Duet 2 WiFi/Duex 5 - RRF 3.4.6 ; ===================================================================================================
-
-
@fcwilt you are correct. An error encountered while evaluating expressions or executing meta GCode expressions will abort the file that is executing and any other files in the call stack. This is true even if the executing file is config.g.
-
Thanks for the clarification.
Is there anyway that errors of this type could be reported when the printer is "booting"?
Frederick
-
@fcwilt in RRF 3.5.0-rc.1 and later it already is reported when DWC connects.
-