BEACON_INITIAL_CALIBRATION moves the head to incorrect place, crashing head
Vc4 400. v2.1.0-RC2-106-g8614d79e.
Most of the time the BEACON_INITIAL_CALIBRATION works ok. However on two occasions it (or BEACON_RATOS_CALIBRATE) has now moved the head to x=400 before doing initial approach. First time was as part of BEACON_RATOS_CALIBRATE. The second time was when running it explicitly. The first time this happenend, I believe the y was also set to 400, since the head moved to the very back right corner. In that position there is nothing that beacon would detect, so the head crashed with the bed during the initial approach.
The second time y was at 200, so perhaps beacon would have stopped, but i switched off the printer rather than wait and see.
What might cause this? An uninitialized variable somewhere? Included is the mainsail screenshot from the latest incident.
What might cause this? An uninitialized variable somewhere? Included is the mainsail screenshot from the latest incident.
Solution:Jump to solution
Missing G90. You're in relative positioning, so you've already homed and have moved the axis around with the mainsail toolhead dialog (which sets relative positioning)
4 Replies
Happened the third time. Perhaps G90 vs G91?
Solution
Missing G90. You're in relative positioning, so you've already homed and have moved the axis around with the mainsail toolhead dialog (which sets relative positioning)
That explains. Had a few of those in my own macros.
@mazas fixed in v2.1.x 🙂