Move out of range: 209.000 -3.000 0.200 [0.000]

General Discussion
21

Nope.

Should look like this:

[gcode_macro G32]
gcode:
	SAVE_GCODE_STATE NAME=STATE_G32
	G90
	G28
	QUAD_GANTRY_LEVEL
	G28
    G90
    G0 X150 Y150 Z30 F3600
	RESTORE_GCODE_STATE NAME=STATE_G32
22

How can this work when the probe is not activated?

[stepper_z]
step_pin = PF11
dir_pin = PG3
enable_pin = !PG5
rotation_distance = 40
gear_ratio = 80:16
microsteps = 32
endstop_pin = PG10       #<----
position_endstop = -0.5
position_max = 260
position_min = -5
homing_speed = 25
second_homing_speed = 3
homing_retract_dist = 3

Ore is there a different way?

23 
So this is what i have now.

Still getting the:
Move out of range: 0.000 -3.000 10.000 [-10.000]
[gcode_macro G32]
gcode:
SAVE_GCODE_STATE NAME=STATE_G32
G90
G28
QUAD_GANTRY_LEVEL
G28
G90
G0 X150 Y150 Z30 F3600
RESTORE_GCODE_STATE NAME=STATE_G32

24

What slicer are you using and did you add the G90 command before the G28 IN THE SLICER CREATED GCODE, like I did in the link I sent?

I just realized that I wasn’t specific in my reply and it looks like you’re playing around with the macros when the (optimal) solution is with the slicer.

25

I am using the Prusaslicer.

26

So I could remove the G-code’s in my macros on Mainsail and put them in the Start G-code of Prusaslicer?

27

Could you try adding the G90 to the gcode generated by PrusaSlicer?

Here is a discussion that you might want to follow:

You’re asking about reverting other macros (which I believe should be in printer.cfg and not in the Mainsail configs) and I would say don’t touch them, at least for now.

Just change one thing and see if it works.

I’ve got my fingers crossed for you!

28

That fixed it! Chuckles, thank you so much for your time and persistance.

2 Likes
29

I’m happy that fixed the problem.

Happy printing and show us what you’re doing!