expected probe state to be deployed but is stowed (1) on start of print
Just added the klicky to my RR 3.1 500 and the klicky does everything fine. Z home, z tikt, bed mesh, stow and deploy. When I print I get the above error after the inital home and heating before print, extruder moves to do the pre print blob and the error comes.
The probe is infact attached as this point. I would of expected it to detect before it does the blob and I think that is the error
Solution:Jump to solution
Solved it. There is a bug in the adaptive mesh "[gcode_macro PROBE_FOR_PRIMING]" line 105 - "{% set z = printer.configfile.settings.bed_mesh.horizontal_move_z|float %}" where it doesn't account for the probe z offset. The config for my machine has a horizontal_move_z set to 5 and my probe offset is also about 5. For my fix I added "horizontal_move_z: 10" to the [bed_mesh] section (add section if not there)
4 Replies
"4:17 PM
Error evaluating 'gcode_macro _ASSERT_PROBE_STATE:gcode': gcode.CommandError: expected probe state to be deployed but is stowed (1)
4:17 PM
Error evaluating 'gcode_macro _ASSERT_PROBE_STATE:gcode': gcode.CommandError: expected probe state to be deployed but is stowed (1)
4:17 PM
Error evaluating 'gcode_macro _ASSERT_PROBE_STATE:gcode': gcode.CommandError: expected probe state to be deployed but is stowed (1)
4:17 PM
Error evaluating 'gcode_macro _ASSERT_PROBE_STATE:gcode': gcode.CommandError: expected probe state to be deployed but is stowed (1)
4:17 PM
Error evaluating 'gcode_macro _ASSERT_PROBE_STATE:gcode': gcode.CommandError: expected probe state to be deployed but is stowed (1)
4:17 PM
Error evaluating 'gcode_macro _ASSERT_PROBE_STATE:gcode': gcode.CommandError: expected probe state to be deployed but is stowed (1)
4:17 PM
Error evaluating 'gcode_macro _ASSERT_PROBE_STATE:gcode': gcode.CommandError: expected probe state to be deployed but is stowed (1)
4:17 PM
probe: TRIGGERED
4:17 PM
RatOS | Adaptive Mesh: Probing the start of the prime location at 492.05, 42.46
4:17 PM
RatOS | Adaptive Mesh: Probing the prime location..
4:17 PM
RatOS | Adaptive Mesh: bicubic interpolation with a probe_count of less than 4 points detected. Forcing lagrange interpolation.
4:17 PM
Probe batch mode enabled: already deployed
4:17 PM
RatOS | Adaptive Mesh: Recieved coordinates X0=218.644 Y0=153.644 X1=281.356 Y1=346.356
4:17 PM
Probe batch mode enabled: not stowing
4:17 PM
Probe batch mode enabled: already deployed
4:17 PM
RatOS: Homing Z
4:17 PM
RatOS: Rehoming Z after Z tilt adjustment...
4:17 PM
Probe batch mode enabled: not stowing
4:17 PM
Retries: 1/10 Probed points range: 0.014297 tolerance: 0.020000"
Solution
Solved it. There is a bug in the adaptive mesh "[gcode_macro PROBE_FOR_PRIMING]" line 105 - "{% set z = printer.configfile.settings.bed_mesh.horizontal_move_z|float %}" where it doesn't account for the probe z offset. The config for my machine has a horizontal_move_z set to 5 and my probe offset is also about 5. For my fix I added "horizontal_move_z: 10" to the [bed_mesh] section (add section if not there)
where abouts in the config is the sample tolerance setting for probing and z tilt ?