Inconsistent Out of Range error

General Discussion
1

Basic Information:

Printer Model: Voron 0.2 R1
MCU / Printerboard: Fly Gemini v3
klippy.log
2-29-24klippy.log (7.9 MB)

Hello All,

So I’ve been trying to chase down an odd issue with my new voron 0. It seems that there is an inconsistent out of range error that keeps occurring. I’ve had 3-4 prints fail at different points, getting through about 10-30mm of print before stopping due to the out of range error. I’ve been banging my head on this one, and any help would be appreciated. Thank you!

2

For some reason you or your gcode is commanding the printer to a position that is not valid. See Move out of range: X Y Z [E]

3

To be more precise:

Filament Sensor DLJC: runout event detected, Time 6797.53
Exiting SD card print (position 5669189)
Stats 6798.0: gcodein=0  mcu: mcu_awake=0.034 mcu_task_avg=0.000038 mcu_task_stddev=0.000083 bytes_write=19693239 bytes_read=5668761 bytes_retransmit=9 bytes_invalid=0 send_seq=518229 receive_seq=518229 retransmit_seq=2 srtt=0.001 rttvar=0.000 rto=0.025 ready_bytes=0 upcoming_bytes=0 freq=168002308 display: mcu_awake=0.085 mcu_task_avg=0.000641 mcu_task_stddev=0.001247 bytes_write=1617058 bytes_read=344723 bytes_retransmit=9 bytes_invalid=0 send_seq=48712 receive_seq=48712 retransmit_seq=2 srtt=0.003 rttvar=0.002 rto=0.025 ready_bytes=0 upcoming_bytes=0 freq=47978801 adj=47977212 host: mcu_awake=0.000 mcu_task_avg=0.000008 mcu_task_stddev=0.000012 bytes_write=42016 bytes_read=131266 bytes_retransmit=0 bytes_invalid=0 send_seq=6979 receive_seq=6979 retransmit_seq=0 srtt=0.000 rttvar=0.000 rto=0.025 ready_bytes=0 upcoming_bytes=0 freq=50000539 adj=49999835  FLY-Gemini: temp=48.6 heater_bed: target=70 temp=70.0 pwm=0.299 sysload=0.33 cputime=987.493 memavail=730332 print_time=6809.333 buffer_time=1.682 print_stall=0 extruder: target=230 temp=229.9 pwm=0.568
Move out of range: 230.000 230.000 29.800 [7963.453]

You had a runout event → Run out is calling PAUSE → Pause is trying to move to 230 / 230

4

I think that’s exactly the problem. I didn’t realize the runout sensor was calling the pause macro, and the stock macro for pause looks designed for a bigger printer I’ll try this out this evening. Thank you!