Duet 3 / Toolboard - significant issue when connection is lost

oozeBot

We recently had the power wire leading to the toolboard fray which resulted in it losing power. When this happened, the print continued, however the BLTouch's probe extended breaking it in half.

While this exposed our carriage needs better strain relief, we would like to request the firmware immediately pause the print if it loses it's connection to the toolboard.

Is this possible? Thanks

oozeBot

@dc42 / @T3P3Tony - We need to raise this issue again to see if anything could be done about it, potentially in 3.4 as it creates a significant risk.

What was just discovered is that if the toolboard isn't communicating with RRF, the following errors are reported but then the script continue. This is extremely hazardous for bed leveling as it continues with the homez.g script even though the toolboard/probe isn't responding.

3/5/2022, 12:54:39 PM	Error: Failed to enable probe
3/5/2022, 12:54:39 PM	Error: M280: Response timeout: CAN addr 20, req type 4012, RID=73
3/5/2022, 12:54:38 PM	Error: Response timeout: CAN addr 20, req type 6037, RID=72
3/5/2022, 12:54:37 PM	Error: M280: Response timeout: CAN addr 20, req type 4012, RID=71

To us, the condition of losing connection with the toolboard is significant enough that RRF should immediately halt.

Alex.cr

@oozebot

While I think its important in the long run to get this hardcoded, I think we can do something in daemon.g for now.

if state.status = "processing" & sensors.analog[2].lastReading>1900
		echo "Error: Connection to toolboard lost, pausing..."
		M98 P"pause.g"

dc42

@oozebot it's too late to do anything in 3.4 but I can look into this for RRF 3.5. However, I think you may already be able to provide protection against probing failing, if you put the following line after each G29 S0, G30 and M280 line in the relevant files (mesh.g, deployprobe.g etc.):

if result > 1
  abort "your message here"

I haven't tested this, so please do so before relying on it (e.g. by unplugging the CAN cable before sending the command). Let me know if it doesn't work.

oozeBot

@dc42 said in Duet 3 / Toolboard - significant issue when connection is lost:

it's too late to do anything in 3.4 but I can look into this for RRF 3.5.

@dc42 - Bumping this back up to make sure it doesn't get lost for 3.5. The request is for the firmware to immediately stop all movement if communication with a can-connected device is lost and alert the user.

I guess it could be as simple as an emergency stop, but the user would need to be notified why it happened.

Thanks

oozeBot

@dc42 David - bumping this as we'd really like to see it addressed in firmware. Can this be worked in 3.5? It seems appropriate to immediately halt the machine if any CAN connected device loses connection.

Phaedrux

It's hoped to be in 3.5, but probably not for the initial beta release.