3.2-beta3 - conditional gcode errors after update



  • After updating to 3.2beta3 I am experiencing trouble with my homing macros that are using conditional gcode to check if an axis has been homed.

    Here is an example of my homex.g:

    ; homex.g
    
    ; Check if Z is homed
    if !move.axes[2].homed		; Check if Z axis is not homed. If axis are not homed, call home.z macro
    	M98 P"0:/sys/homez.g"
    else						; if Z is already homed, move it down by 5mm
    G91               			; relative positioning
    G1 Z+5							; move Z down by 5mm
    G90               			; absolute positioning
    
    ; Check if Y is homed
    if !move.axes[1].homed		; check if Y axis is not homed. If axis are not homed, call home.y macro
    	M98 P"0:/sys/homey.g"						
    else
    G1 Y0 F18000				; If Y axis is already homed, move it to Y0 Position
    
    ; Home X axis
    G91               			; relative positioning
    G1 H1 X-430 F3000 			; move quickly to X axis endstop and stop there (first pass)
    G1 X5 F4000       			; go back a few mm
    G1 H1 X-6 F300   			; move slowly to X axis endstop once more (second pass)
    G90               			; absolute positioning
    

    And this is the error I am receiving:

    Error: Homing file homex.g not found
    Error: Failed to get macro response within 8000ms from SBC (channel HTTP)

    The macro is at least partly executed but apparently it gets stuck at some point. The only way to get it unstuck is a firmware reset.

    Without the conditional gcode everything works just fine

    -Max


  • administrators

    This type of error when using attached SBC is fixed in the 3.2beta3.1 release, which we expect to make available tomorrow.


  • administrators

    You can try to upload this firmware build on the Files -> System page, confirm the update prompt, and check if that resolves your problem. As dc42 already said, we'll release a new RRF version tomorrow if everything goes well.



  • Hello @dc42 and @chrishamm,

    thank you very much for your immediate response.

    After uploading the firmware as chrishamm suggested the issue is solved!

    Cheers!
    Max


Log in to reply