🛑 V-Core Z Homing Crash | “Shutdown due to X and Y must be homed before homing Z” Error on RatOS /
Hey all,
I’m having an issue with my V-Core running RatOS + Klipper. When I home the printer with the homing button, XY homes perfectly. But right before Z starts, the plate drops ~5mm and the system immediately shuts down. Console Output: This repeats even though XY was clearly homed first. No clue why it thinks otherwise. --- Any idea what’s causing this or how to fix it?
Appreciate any help.
I’m having an issue with my V-Core running RatOS + Klipper. When I home the printer with the homing button, XY homes perfectly. But right before Z starts, the plate drops ~5mm and the system immediately shuts down. Console Output: This repeats even though XY was clearly homed first. No clue why it thinks otherwise. --- Any idea what’s causing this or how to fix it?
Appreciate any help.
8 Replies
What happens if you home X and Y separately, then try Z?
Same behaviour.. full home x then y preform normally then z crashes.. if i home them speratelay in order still crashes
physically crashes, or same error?
same error(s)..
4:46 AM
Shutdown due to X and Y must be homed before homing Z
4:46 AM
Shutdown due to X and Y must be homed before homing Z
Once the underlying issue is corrected, use the
"FIRMWARE_RESTART" command to reset the firmware, reload the
config, and restart the host software.
Printer is shutdown
4:46 AM
Shutdown due to X and Y must be homed before homing Z
4:46 AM
Shutdown due to X and Y must be homed before homing Z
Once the underlying issue is corrected, use the
"FIRMWARE_RESTART" command to reset the firmware, reload the
config, and restart the host software.
Printer is shutdown
4:46 AM
Shutdown due to X and Y must be homed before homing Z
4:46 AM
Shutdown due to X and Y must be homed before homing Z
Once the underlying issue is corrected, use the
"FIRMWARE_RESTART" command to reset the firmware, reload the
config, and restart the host software.
Printer is shutdown
4:46 AM
Klipper state: Shutdown
4:46 AM
G28 Z
4:46 AM
No Beacon model loaded
4:46 AM
No Beacon model loaded
4:46 AM
No Beacon model loaded
4:46 AM
RatOS: Homing Z
4:46 AM
G28
this is the consol output for the last time i tried.
that sounds like a homing macro is corrupted or something, that makes no sense
I also experienced an issue where the PWM signal wasn't sent to the toolboard, even after Klipper loaded. The config showed that the signal was coming from the control board at PA8. After checking the pinout for both boards, I moved the wire to PA8 on the control board and was able to control the part cooling fan, which contradicts the official layout. Could this be cascading issue stemming from a firmware issue with incorrect pin mapping?
.
out of curioisity .. i unpluged the printer and rebooted it, after the reboot i attempted to home once more.. this time it only threw the no beacon model loaded error x3.
i figured it out. with the help of Martin.
i re-ran the 'BEACON_INITIAL_CALIBRATION'
everything is running ..