You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jul 9, 2020. It is now read-only.
Fixed issue with G1 H1 moves when endstops are not already triggered. There is still an issue if a move involves only remote drivers and a main board endstop switch.
Don't set up a default bed heater on Duet 3
Fixed issue when creating a switch endstop failed
afterPrepare.moveStartTime = (st == DDAState::executing || st == DDAState::frozen)
1496
-
? prev->afterPrepare.moveStartTime + prev->clocksNeeded// this move will follow the previous one, so calculate the start time assuming no more hiccups
1496
+
? prev->afterPrepare.moveStartTime + prev->clocksNeeded// this move will follow the previous one, so calculate the start time assuming no more hiccups
1497
1497
: StepTimer::GetTimerTicks() + MovementStartDelayClocks; // else this move is the first so start it after a short delay
1498
1498
1499
+
if (flags.checkEndstops)
1500
+
{
1501
+
// Before we send movement commands to remote drives, if any endstop switches we are monitoring are already set, make sure we don't start the motors concerned.
1502
+
// This is especially important when using CAN-connected motors or endstops, because we rely on receiving "endstop changed" messages.
1503
+
// Moves that check endstops are always run as isolated moves, so there can be no move in progress and the endstops must already be primed.
1504
+
platform.EnableAllSteppingDrivers();
1505
+
CheckEndstops(platform); // this may modify pending CAN moves, and may set status 'completed'
// Check the endstops, given that we know that this move checks endstops.
1641
+
// Either this move is currently executing (DDARing.currentDDA == this) and the state is 'executing', or we have almost finished preparing it and the state is 'provisional'.
0 commit comments