Error when trying to home
I just upgraded my V-Core3 500 to RatOS 2.0 and on couple of occasions I run into the following error when I try homing the printer (G28):
behavior is printer begins homing (lowering Z, does first endstop bump, then error appears (printhead does not move to the middle as expected). Firmware reset seems to resolve the situation.
12 Replies
adverse-sapphire•12mo ago
Looks like it is happening after generating a heat map
Make sure no g-code transforms are loaded outside of a print (bed_mesh, skew, z_thermal_adjust etc)
I've complained about this on the klipper forums, but Kevin made some good points about why it is like it is, and i had to agree with him.
I argued that g-code transforms should automatically be ignored during homing
adverse-sapphire•12mo ago
thx what are the g-code transfroms actually (sorry for the lame question)? I have not done anything outside using mainsail interface
Anything in klipper that modifies gcode coordinates.
gcode offset, skew, bed_mesh, z_thermal_adjust all carry out gcode transforms. (ergo, when you issue G0 Xsomething Ysomething Zsomething it will be transformed to G0 Xsomethingelse Ysomethingelse Zsomethingelse)
So make sure no runtime gcode offset is set, no bed mesh profile or skew profile is loaded, and disable z_thermal_adjust if configured.
If you use FDC there might be something there too
adverse-sapphire•12mo ago
👍
i guess it must be due to taking bed_mesh which loads the set, followed by homing without removing the bed mesh and/or disabling steppers
That will do it
Just clear the bed_mesh and it should work again
adverse-sapphire•12mo ago
ok - understood. I am surprised i never ran into this before
BED_MESH_CLEAR that is 🙂
RatOS 2.0 centers the X and Y after homing, 1.0 didn't.
adverse-sapphire•12mo ago
gotcha!
So that's probably why
V1 only did it if you were using sensorless homing
V2 unified all homing related stuff, so everything behaves the same and predictably
adverse-sapphire•12mo ago
thanks!!
(and most important of all is highly configurable)
np 🙂