# Problems with printing after getting homing working

**URL:** <https://klipper.discourse.group/t/problems-with-printing-after-getting-homing-working/6374>\
**Category:** General Discussion\
**Created:** [February 2, 2023, 9:07pm UTC](https://klipper.discourse.group/t/problems-with-printing-after-getting-homing-working/6374 "2023-02-02T21:07:34Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![mykepredko](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/mykepredko/32/2085_2.png) [@mykepredko](https://klipper.discourse.group/u/mykepredko)\
**Post date:** [February 2, 2023, 9:07pm UTC](https://klipper.discourse.group/t/problems-with-printing-after-getting-homing-working/6374/1 "2023-02-02T21:07:35Z")

</div>

### Basic Information:

Printer Model: Custom CoreXY  
 MCU / Printerboard: rPi 4B, Octopus V1.1, FLY SHT42  
 [klippy.log](https://klipper.discourse.group/uploads/short-url/vjS8smnQzOdH7KahyF5wdYRYhMJ.log) (3.5 MB)  
 [printer.cfg](https://klipper.discourse.group/uploads/short-url/fLodhaAx5JF4hYI2olJuHFxubvg.cfg) (22.1 KB)  
 [canFly.cfg](https://klipper.discourse.group/uploads/short-url/s1jKdXoyGgRCn89j0B097w2UXz6.cfg) (3.7 KB)  
 [ABS-2-225-70-raft\_Voron\_Design\_Cube\_v7.gcode](https://klipper.discourse.group/uploads/short-url/3vhYjm2DOqNhlbgTGOyihtwHG2G.gcode) (2.6 MB)

Sometimes you just can’t win for losing.

After getting homing operations working with sensorless homing (see: ), I now find that every time I try to print, the toolhead moves outside of the print range as shown here:

[![](https://global.discourse-cdn.com/free1/uploads/klipper/original/2X/c/c783d5098d4882943fc7cad261268a7e9df0ec81.jpeg "Print operation moves outside of print envelope") ](https://www.youtube.com/watch?v=lKj-afez6aw)

Everytime it executes, I get the error message Move out of range:

 ![image](https://global.discourse-cdn.com/free1/uploads/klipper/original/2X/8/88e830570a18bef8159ed116d2e6cfa0a238d09b.png)

This is for multiple gcode files (I’ve attached one I just built to see if there was a version issue) and I’ve power cycled the machine. The only options selected in Cura was to produce the thumbnails so the design is displayed on Mainsail.

I’m guessing this has to do with the homing stuff that was discussed here:

> [@Z Axis Probing Issues](https://klipper.discourse.group/t/z-axis-probing-issues/6328/):
>
> Basic Information: Printer Model: Custom CoreXY MCU / Printerboard: rPi 4B, Octopus V1.1 & FLY SHT42 [klippy.log](https://klipper.discourse.group/uploads/short-url/esRgcdYPzptjT8ii6WwljQV2SzY.log) (851.2 KB) I have two issues that need to be addressed when trying to implement sensorless homing that will allow SAVE\_CONFIG updates from functions like SHAPER\_CONFIGURATION. This is a continuation to [https://klipper.discourse.group/t/problem-with-shaper-calibrate-tmc2209s-with-sensorless-homing/6247](https://klipper.discourse.group/t/problem-with-shaper-calibrate-tmc2209s-with-sensorless-homing/6247)1. Updating printer.toolhead.homed\_axes after single axis homing: I’m using t…

I’d be very grateful if anybody has any ideas here.

---

<div class="post-metadata">

**Author:** ![mykepredko](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/mykepredko/32/2085_2.png) [@mykepredko](https://klipper.discourse.group/u/mykepredko)\
**Post date:** [February 2, 2023, 9:34pm UTC](https://klipper.discourse.group/t/problems-with-printing-after-getting-homing-working/6374/2 "2023-02-02T21:34:11Z")

</div>

Just one piece of information I didn’t put in my original post.

I did try moving the toolhead to Y=0 from the Z axis homing point to see if that would eliminate the problem but nothing changed other than I added to the wait for the toolhead to move to the out of range condition.

---

<div class="post-metadata">

**Author:** ![jakep\_82](https://avatars.discourse-cdn.com/v4/letter/j/ea666f/32.png) [@jakep\_82](https://klipper.discourse.group/u/jakep_82)\
**Post date:** [February 3, 2023, 3:01am UTC](https://klipper.discourse.group/t/problems-with-printing-after-getting-homing-working/6374/3 "2023-02-03T03:01:33Z")

</div>

Have you tried adding G90 to your start gcode to explicitly set absolute coordinates?

---

<div class="post-metadata">

**Author:** ![mykepredko](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/mykepredko/32/2085_2.png) [@mykepredko](https://klipper.discourse.group/u/mykepredko)\
**Post date:** [February 3, 2023, 3:03am UTC](https://klipper.discourse.group/t/problems-with-printing-after-getting-homing-working/6374/4 "2023-02-03T03:03:22Z")

</div>

Nope. What will that do exactly?

I’m trying it right now…

---

<div class="post-metadata">

**Author:** ![jakep\_82](https://avatars.discourse-cdn.com/v4/letter/j/ea666f/32.png) [@jakep\_82](https://klipper.discourse.group/u/jakep_82)\
**Post date:** [February 3, 2023, 3:07am UTC](https://klipper.discourse.group/t/problems-with-printing-after-getting-homing-working/6374/5 "2023-02-03T03:07:10Z")

</div>

G90 tells the printer to interpret gcode moves as absolute positions. G91 tells the printer to interpret move commands relative to the current position.

---

<div class="post-metadata">

**Author:** ![mykepredko](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/mykepredko/32/2085_2.png) [@mykepredko](https://klipper.discourse.group/u/mykepredko)\
**Post date:** [February 3, 2023, 3:13am UTC](https://klipper.discourse.group/t/problems-with-printing-after-getting-homing-working/6374/6 "2023-02-03T03:13:19Z")

</div>

Sorry, where do I put it?

The current initial code is:

```auto
; myke's Custom CoreXY Start G-code
G92 E0 ; Reset Extruder
G28 ; Home all axes
; #### Put G90 here?
G1 Z2.0 F3000 ; Move Z Axis up little to prevent scratching of Heat Bed
G1 X0.1 Y20 Z0.3 F5000.0 ; Move to start position
G1 X0.1 Y200.0 Z0.3 F1500.0 E15 ; Draw the first line
G1 X0.4 Y200.0 Z0.3 F5000.0 ; Move to side a little
G1 X0.4 Y20 Z0.3 F1500.0 E30 ; Draw the second line
G92 E0 ; Reset Extruder
G1 Z2.0 F3000 ; Move Z Axis up little to prevent scratching of Heat Bed
G1 X5 Y20 Z0.3 F5000.0 ; Move over to prevent blob squish

```

I’m guessing after the `G28` as I’ve marked in the comments above?

---

<div class="post-metadata">

**Author:** ![jakep\_82](https://avatars.discourse-cdn.com/v4/letter/j/ea666f/32.png) [@jakep\_82](https://klipper.discourse.group/u/jakep_82)\
**Post date:** [February 3, 2023, 3:15am UTC](https://klipper.discourse.group/t/problems-with-printing-after-getting-homing-working/6374/7 "2023-02-03T03:15:02Z")

</div>

That should be fine.

---

<div class="post-metadata">

**Author:** ![mykepredko](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/mykepredko/32/2085_2.png) [@mykepredko](https://klipper.discourse.group/u/mykepredko)\
**Post date:** [February 3, 2023, 3:21am UTC](https://klipper.discourse.group/t/problems-with-printing-after-getting-homing-working/6374/8 "2023-02-03T03:21:00Z")

</div>

That seems to have fixed the problem.

Thanx!

---

<div class="post-metadata">

**Author:** ![EddyMI3D](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/eddymi3d/32/1981_2.png) [@EddyMI3D](https://klipper.discourse.group/u/EddyMI3D)\
**Post date:** [October 27, 2024, 9:44pm UTC](https://klipper.discourse.group/t/problems-with-printing-after-getting-homing-working/6374/9 "2024-10-27T21:44:47Z")

</div>


