BLTouch.init should not deploy (#13988)
Low or unknown probe clearance on init (even at powerup) is a risk and therefore, a deploy should be avoided because dragging the pin is possible: A deploy goes into alarm if it can't extend fully and then the subsequent stow will fail.
This commit is contained in:
parent
211563e533
commit
dcaefc68a5
1 changed files with 2 additions and 1 deletions
|
@ -49,7 +49,8 @@ void BLTouch::init() {
|
||||||
#if ENABLED(BLTOUCH_FORCE_5V_MODE)
|
#if ENABLED(BLTOUCH_FORCE_5V_MODE)
|
||||||
_set_5V_mode(); // Set 5V mode if explicitely demanded (V3 upwards)
|
_set_5V_mode(); // Set 5V mode if explicitely demanded (V3 upwards)
|
||||||
#endif
|
#endif
|
||||||
clear();
|
_reset();
|
||||||
|
_stow();
|
||||||
// There really should be no alarm outstanding now, and no triggered condition. But if there is,
|
// There really should be no alarm outstanding now, and no triggered condition. But if there is,
|
||||||
// there is no need to worry people here on init right at the start of the printer.
|
// there is no need to worry people here on init right at the start of the printer.
|
||||||
}
|
}
|
||||||
|
|
Reference in a new issue