Move out of range, unclear solution

mykepredko · February 5, 2023, 10:29pm

I had the same problem recently.

Add “G90” to your Start Code after the G28 as discussed here:

In your Cura Printer Profile, go into “Machine Settings” and add the gcode statement:

github.com/Ultimaker/Cura

[3.4.1] Need to issue G90 to force absolute positioning

opened 01:57AM - 13 Aug 18 UTC

closed 11:56AM - 13 Aug 18 UTC

JimF42

Status: Won't Fix/Do Type: Question

**Application Version** 3.4.1 **Platform** Windows 10 **Printer** Custom FDM printer (Anet A6) **Steps to Reproduce** Create a printer profile and go into Machine Settings and add some code to the "Start G-code" section which includes a `G91` command to switch to relative positioning. Generate the G-code and open in something like OctoPrint. Odds are the print will be off the bed. OctoPrint will usually fuss about it "too large" for the machine. **Actual Results** Generate the G-code and open in something like OctoPrint. Odds are the print will be off the bed. OctoPrint will usually fuss about it "too large" for the machine. Add a `G91` command to the end of the "Start G-code" section, and it renders and prints just fine. **Expected results** The part should render and print just fine in 3D controller software, like OctoPrint regardless of the user added G-code leaving the workspace in relative mode. **Additional Information** Please add any needed commands to make sure the workspace is set correctly for the style of G-code you will be generating after the user editable "Start G-code" section is inserted. I am using a probe that needs Z movement to make sure its probe pin is retracted properly (HallON model probe) and I felt more comfortable using relative commands and did not put it back to absolute commands (`G90`) not knowing that you required absolute positioning and did not enforce it yourself. Took me several days to figure this one out while trying to learn Slic3r which does not exhibit this behavior.

Topic		Replies	Views
Print fails during start G-Code "Move out of range" General Discussion	8	204	October 30, 2024
Move out of range General Discussion	22	5360	September 4, 2024
Move out of range error / Klipper / Cura General Discussion	6	65	February 22, 2025
End of print error -- out of range General Discussion	6	703	June 12, 2024
Move out of range error after homing General Discussion	6	76	November 3, 2024

Move out of range, unclear solution

Related topics