Move out of range

General Discussion
1

Hi, i’m new here and I trying klipper on the Ender 3 S1 Pro for the first time and I love it!

It seems that the problem occurs with larger prints. Smaller prints are going fine.
After homing and heating it says:

Move out of range: 154.000 364.000 77.474 [0.000]

Can someone help with this?

Thanks!
klippy.log (2.6 MB)
moonraker.log (65.3 KB)

2

i THINK I fixed with changing this:

G1 X{X_START} Y{Y_START} Z{PRIMER_HEIGHT} F6000.0

to this

G1 X{X_START} Y{Y_START} Z{PRIMER_HEIGHT} F3000.0

Now it’s printing.

Was this the fix? Or was it the restart that fixed it temporary?

3

Hello @Mess !

For the Ender 3 has lead screws for the Z-axes, it requires way lower feed rate than X and Y.
So you should set X/Y and Z in separate lines. E.g.:

G1 X{X_START} Y{Y_START} F6000.0
G1 Z{PRIMER_HEIGHT} F600.0
1 Like
4

Thanks. I did it like this. Is this ok?

      G92 E0     
      G1 X{X_START} Y{Y_START} F3000.0
      G1 Z{PRIMER_HEIGHT} F600.0    
      G1 X{X_MAX - 12 * X_START} Y{Y_START} F2000.0 E20
      G1 Z{PRIMER_HEIGHT} F600.0 E20
      G1 X{X_MAX - 12 * X_START} Y{Y_START + PRIMER_WIDTH} Z{PRIMER_HEIGHT} 
      G1 X{X_MAX - 12 * X_START} Y{Y_START + PRIMER_WIDTH} Z{PRIMER_HEIGHT} 
      G1 X{X_START} Y{Y_START + PRIMER_WIDTH} F2000.0 E20
      G1 Z{PRIMER_HEIGHT} F600.0 E20
      G92 E0
5

If you move the Z-axes, you usually do no extrusion (E20). And if there is no change in the height, you can omit that move too.
So like this:

1 Like
6

Great thanks! Now I understand it better. I’m gonna try this.

By the way, this is the second time the print pauses on its own. When I press resume, the print resumes. Do you have any idea what that could be?

klippy (3).log (6.4 MB)

7

Maybe there is something in the gcode file that causes the pause.

8

I can’t find anything. But I’m still a noob. Can I upload it for you? Or do you don’t want to do that?

9

I can take a look on it. You can upload it here as a zipped file.

10

printer.zip (3.5 KB)
Here you go!

11

Actually I asked for the gcode file where the pause occur

12

My apologies. Here you go.

CE3_Nonlethal_Door_Stop_Multitool (2).zip (1.8 MB)

13

I also have to tell you that I’ve done a lot of installations like telegram, klipperscreen, a tutorial to get V2 screen working that I don’t use anymore, and more. Maybe it’s a good idea to do a complete reinstall?

14 
Filament Sensor RunoutSensor: runout event detected, Time 28465.20
Exiting SD card print (position 410777)
Stats 28465.7: gcodein=0  mcu: mcu_awake=0.010 mcu_task_avg=0.000027 mcu_task_stddev=0.000019 bytes_write=1552281 bytes_read=277077 bytes_retransmit=9 bytes_invalid=0 send_seq=26886 receive_seq=26883 retransmit_seq=2 srtt=0.003 rttvar=0.000 rto=0.025 ready_bytes=375 stalled_bytes=0 freq=83998628 heater_bed: target=30 temp=31.2 pwm=0.000 Board_MCU: temp=32.8 Raspberry_Pi: temp=56.5  sysload=0.18 cputime=534.158 memavail=1484152 print_time=877.806 buffer_time=2.458 print_stall=0 extruder: target=215 temp=215.0 pwm=0.291
Stats 28466.7: gcodein=0  mcu: mcu_awake=0.011 mcu_task_avg=0.000027 mcu_task_stddev=0.000019 bytes_write=1553071 bytes_read=277355 bytes_retransmit=9 bytes_invalid=0 send_seq=26902 receive_seq=26902 retransmit_seq=2 srtt=0.002 rttvar=0.000 rto=0.025 ready_bytes=0 stalled_bytes=0 freq=83998626 heater_bed: target=30 temp=31.1 pwm=0.268 Board_MCU: temp=32.8 Raspberry_Pi: temp=57.0  sysload=0.18 cputime=534.188 memavail=1483608 print_time=878.572 buffer_time=2.224 print_stall=0 extruder: target=215 temp=214.8 pwm=0.403
Print already paused

Your runout sensor is misbehaving.

1 Like
15

o-m-g… You are totaly right!

This is TPU and a bit flexible… Indeed when I play with the TPU I see the sensor light go on and of…

So simple! I didn’t noticed it in the log, but now I see it.

Is there any macro/script that send me a message in telegram or webinterface thats says something with filament issue? Now it just pauzes the print without telling whats going on.

Thanks again for your great help! :slight_smile:

16

Hi, again.

Again with bigger objects: Move out of range: 154.000 364.000 77.452 [1.000]

I’m printing with the fast Chep profile, but its also with the normale profile.
The print stops before laying the purge lines.
With the professional firmware it worked.

I don’t know how to fix it. Can some help me with this?

See log, printer.cfg and gcode file in the zip file.

Thanks!

printer.zip (1.3 MB)

17

Guys, I fixed it already to adding G90 before homing!

      #Home
      G28

      G90

      #Move up to clean bed
      G1 Y{Y_MAX - 20} Z{Z_MAX/4.0} F6000                

      #Heat nozzle and bed
      M190 S{BED_TEMP}                               
      M109 S{EXTRUDER_TEMP} T0          


      #Precondition extruder
      G92 E0     
      G1 X{X_START} Y{Y_START} F3000.0
      G1 Z{PRIMER_HEIGHT} F600.0    
      G1 X{X_MAX - 12 * X_START} Y{Y_START} F2000.0 E20
      G1 X{X_MAX - 12 * X_START} Y{Y_START + PRIMER_WIDTH} 
      G1 X{X_START} Y{Y_START + PRIMER_WIDTH} F2000.0 E20
      G92 E0
1 Like
18

Hi agian,

New problem: Move exceeds maximum extrusion (9.033mm^2 vs 0.640mm^2)

I went on to print an Eclipse plane. Before this I did it with professional firmware but now with Klipper.

According to the manual Cura needs to be set up a bit differently, but now I get an error message after printing the first line.

I really can’t figure this out. Does anyone know what the problem is?

See zip file.

Thanks in advance!
files.zip (1.2 MB)

19

Aaaand I solved my own problem again!!

G3 = ARC welder. And in this Cura profile it was on!

So klipper doens’t support ARC welder I think.

Next time I will do my best more to solve the problem instead of posting here first :wink: Great help guys! :stuck_out_tongue:

1 Like
20

If you run Klipper on OctoPrint you can use the Arcwelder plugin.
That is the benefit with Klipper + OctoPrint: The huge amount of plugins.