If BLtouch z probe fails, printer disable all endstops and start mashing things

[burner-]

With current git version is BLtouch fails at bed mesh leveling because table is too close for proper probe deploy it gives: STOP called because of BLTouch error - restart with M999 BUT instead of stopping probing it continue retrying again and again. And if it finally manage to get probe deployed it will diable all endstops and first mash Z to zero (even bltouch give signal to stop) and then it mash X to zero and ignore that sensor and after while it do same for Y. I think that if probing fails it would be better to just stop everything but at least not disable all endstops. Only way what I found to get it stop driving motors was board reset. I use Ultratronics board with newest git version of firmware and there is configuration https://github.com/burner-/MK4duo/tree/master/MK4duo

Here is log:

Recv: echo:Active Extruder: 0 Recv: X:62.00 Y:10.00 Z:4.00 E:0.00 Recv: ok Send: G1 X0 Y0 Z0 F3000 [...] Recv: busy:processing [...] Recv: busy:processing [...] Recv: Error:STOP called because of BLTouch error - restart with M999 Recv: Error:Printer stopped due to errors. Fix the error and use M999 to restart. (Temperature is reset. Set it after restarting) Recv: //action:notification STOPPED. Recv: Error:STOP called because of BLTouch error - restart with M999 Recv: Error:STOP called because of BLTouch error - restart with M999 Recv: Error:STOP called because of BLTouch error - restart with M999 Recv: Error:STOP called because of BLTouch error - restart with M999 Recv: Error:STOP called because of BLTouch error - restart with M999 Recv: Error:STOP called because of BLTouch error - restart with M999 Recv: Error:STOP called because of BLTouch error - restart with M999 Recv: Error:STOP called because of BLTouch error - restart with M999 Recv: Error:STOP called because of BLTouch error - restart with M999 Recv: Error:STOP called because of BLTouch error - restart with M999 Recv: Error:STOP called because of BLTouch error - restart with M999 Recv: Error:STOP called because of BLTouch error - restart with M999 Recv: Error:STOP called because of BLTouch error - restart with M999 Recv: Error:STOP called because of BLTouch error - restart with M999 Recv: Error:STOP called because of BLTouch error - restart with M999 Recv: Error:STOP called because of BLTouch error - restart with M999 Recv: Error:STOP called because of BLTouch error - restart with M999 Recv: Error:STOP called because of BLTouch error - restart with M999 Recv: Error:STOP called because of BLTouch error - restart with M999 Recv: Error:STOP called because of BLTouch error - restart with M999 Recv: Error:STOP called because of BLTouch error - restart with M999 Recv: Error:STOP called because of BLTouch error - restart with M999 Recv: Error:STOP called because of BLTouch error - restart with M999 Recv: Error:STOP called because of BLTouch error - restart with M999 Recv: Error:STOP called because of BLTouch error - restart with M999 Recv: Error:STOP called because of BLTouch error - restart with M999 Recv: Error:STOP called because of BLTouch error - restart with M999 Recv: Error:STOP called because of BLTouch error - restart with M999 Recv: Error:STOP called because of BLTouch error - restart with M999 Recv: Error:STOP called because of BLTouch error - restart with M999 Recv: Error:STOP called because of BLTouch error - restart with M999 Recv: Error:STOP called because of BLTouch error - restart with M999 Recv: Error:STOP called because of BLTouch error - restart with M999 Recv: Error:STOP called because of BLTouch error - restart with M999 Recv: Error:STOP called because of BLTouch error - restart with M999 Recv: Error:STOP called because of BLTouch error - restart with M999 Recv: Error:STOP called because of BLTouch error - restart with M999 Recv: Error:STOP called because of BLTouch error - restart with M999 Recv: Error:STOP called because of BLTouch error - restart with M999 Recv: Error:STOP called because of BLTouch error - restart with M999 Recv: Error:STOP called because of BLTouch error - restart with M999 Recv: Error:STOP called because of BLTouch error - restart with M999 Recv: Error:STOP called because of BLTouch error - restart with M999 Recv: Error:STOP called because of BLTouch error - restart with M999 Recv: Error:STOP called because of BLTouch error - restart with M999 Recv: Error:STOP called because of BLTouch error - restart with M999 Recv: Error:STOP called because of BLTouch error - restart with M999 Recv: Error:STOP called because of BLTouch error - restart with M999 Recv: Error:STOP called because of BLTouch error - restart with M999 Recv: Error:STOP called because of BLTouch error - restart with M999 Recv: Error:STOP called because of BLTouch error - restart with M999 Recv: Error:STOP called because of BLTouch error - restart with M999 Recv: Error:STOP called because of BLTouch error - restart with M999 Recv: Error:STOP called because of BLTouch error - restart with M999 Recv: Error:STOP called because of BLTouch error - restart with M999 Send: M112 Send: N3 M11234 Send: N4 M104 T0 S037 Send: N5 M104 T1 S037 Send: N6 M104 T2 S037 Send: N7 M104 T3 S037 Send: N8 M140 S0109 Closing serial port due to emergency stop M112. Connection closed, closing down monitor Changing monitoring state from "Operational" to "Offline (Error: Closing serial port due to emergency stop M112.)" Connecting to: /dev/ttyACM0 Changing monitoring state from "Offline" to "Opening serial port" Connected to: Serial(port='/dev/ttyACM0', baudrate=250000, bytesize=8, parity='N', stopbits=1, timeout=10.0, xonxoff=False, rtscts=False, dsrdtr=False), starting monitor Changing monitoring state from "Opening serial port" to "Connecting" Send: N0 M110 N0125 Send: N0 M110 N0125 Recv: Error:STOP called because of BLTouch error - restart with M999 Send: N0 M110 N0125 Recv: Error:STOP called because of BLTouch error - restart with M999 Recv: Error:STOP called because of BLTouch error - restart with M999 Recv: Error:STOP called because of BLTouch error - restart with M999 Recv: Error:STOP called because of BLTouch error - restart with M999 Recv: Error:STOP called because of BLTouch error - restart with M999 Recv: Error:STOP called because of BLTouch error - restart with M999 Recv: Error:STOP called because of BLTouch error - restart with M999 Unexpected error while reading serial port, please consult octoprint.log for details: SerialException: 'device reports readiness to read but returned no data (device disconnected or multiple access on port?)' @ comm.py:_readline:2793 Please see https://faq.octoprint.org/serialerror for possible reasons of this. Changing monitoring state from "Connecting" to "Offline (Error: SerialException: 'device reports readiness to read but returned no data (device disconnected or multiple access on port?)' @ comm.py:_readline:2793)" Connection closed, closing down monitor Changing monitoring state from "Offline" to "Detecting serial port" Serial port list: ['/dev/ttyACM0'] Connecting to: /dev/ttyACM0 Changing monitoring state from "Detecting serial port" to "Opening serial port" Connected to: Serial(port='/dev/ttyACM0', baudrate=250000, bytesize=8, parity='N', stopbits=1, timeout=10.0, xonxoff=False, rtscts=False, dsrdtr=False), starting monitor Changing monitoring state from "Opening serial port" to "Connecting" Send: N0 M110 N0125 Recv: ok Send: N0 M110 N0125 Changing monitoring state from "Connecting" to "Operational" Send: N0 M110 N0125 Recv: ok Recv: ok Send: N1 M11539 Send: N2 M2118 Recv: FIRMWARE_NAME:MK4duo 4.4.0 FIRMWARE_URL:marlinkimbra.it PROTOCOL_VERSION:2.0 MACHINE_TYPE:Cartesian EXTRUDER_COUNT:4 UUID:aedacceff24-1a3b-4114-de0e-1aba5ff215ef Recv: Recv: Cap:SERIAL_XON_XOFF:0 Recv: Cap:EEPROM:1 Recv: Cap:VOLUMETRIC:0 Recv: Cap:AUTOREPORT_TEMP:1 Recv: Cap:PROGRESS:1 Recv: Cap:BUILD_PERCENT:1 Recv: Cap:PRINT_JOB:1 Recv: Cap:PAUSESTOP:1 Recv: Cap:PROMPT_SUPPORT:1 Recv: Cap:AUTOLEVEL:1 Recv: Cap:Z_PROBE:1 Recv: Cap:LEVELING_DATA:1 Recv: Cap:SOFTWARE_POWER:1 Recv: Cap:TOGGLE_LIGHTS:0 Recv: Cap:EMERGENCY_PARSER:1 Recv: Cap:CHAMBER_TEMPERATURE:1 Recv: ok Recv: ok Send: M301 H0 P13.573215 I1.296949 D35.512619 Send: M301 H1 P13.573215 I1.296949 D35.512619 Recv: ok Send: M301 H2 P13.573215 I1.296949 D35.512619 Recv: ok Send: M301 H3 P13.573215 I1.296949 D35.512619 Recv: ok Recv: ok Send: M353 D4 E4 H4 B1 C0 F2 Send: M563 T0 D0 H1 Recv: ok Recv: ok Send: M563 T1 D1 H1 Recv: ok Send: M563 T2 D2 H1 Send: M563 T3 D3 H1 Recv: ok Recv: ok Send: M155 S2 Recv: ok Send: M876 P1 Recv: ok [...] Send: G91 Send: G1 Z10 F200 Recv: ok Send: G90 Recv: ok Recv: ok [...] Send: G91 Recv: ok Send: G1 Z100 F200 Recv: ok Send: G90 Recv: ok [...] Send: G91 Send: G1 Z100 F200 Recv: ok Send: G90 Recv: ok Recv: ok [...] Unexpected error while reading serial port, please consult octoprint.log for details: SerialException: 'device reports readiness to read but returned no data (device disconnected or multiple access on port?)' @ comm.py:_readline:2793 Please see https://faq.octoprint.org/serialerror for possible reasons of this. Changing monitoring state from "Operational" to "Offline (Error: SerialException: 'device reports readiness to read but returned no data (device disconnected or multiple access on port?)' @ comm.py:_readline:2793)" Connection closed, closing down monitor Changing monitoring state from "Offline" to "Detecting serial port" Serial port list: ['/dev/ttyACM0'] Connecting to: /dev/ttyACM0 Changing monitoring state from "Detecting serial port" to "Opening serial port" Connected to: Serial(port='/dev/ttyACM0', baudrate=250000, bytesize=8, parity='N', stopbits=1, timeout=10.0, xonxoff=False, rtscts=False, dsrdtr=False), starting monitor Changing monitoring state from "Opening serial port" to "Connecting" Send: N0 M110 N0125 Recv: ok Send: N0 M110 N0125 Changing monitoring state from "Connecting" to "Operational" Send: N0 M110 N0125 Recv: ok Send: N1 M11539 Recv: ok Send: N2 M21*18