Stopping a printing job after a warning or error

Hobby-Store

@dc42 said in Stopping a printing job after a warning or error:

@hobby-store with firmware 3.4 you can do this. See https://docs.duet3d.com/en/User_manual/RepRapFirmware/Events.

Hello.
I upgrade firmware to 3.4. But it's not working. I start print and disconnect one drive and nothing has happened and the printout did not stop and nothing was displayed in the logs or in the message.

I read "Pause print without running pause.g and inform user vis message box" when error-drive default.

Płyta główna: Duet 2 WiFi (2WiFi)
Oprogramowanie sprzętowe: RepRapFirmware for Duet 2 WiFi/Ethernet 3.4.0 (2022-03-15)
Wersja serwera Duet WiFi: 1.23

Phaedrux

You disconnected a motor mid-print? Did the driver survive? Was no error created at all? Was the driver not configured at the time?

Hobby-Store

@phaedrux said in Stopping a printing job after a warning or error:

You disconnected a motor mid-print? Did the driver survive? Was no error created at all? Was the driver not configured at the time?

Driver sill working.

I know you shouldn't do this because it can damage the driver, but I need to be sure that this feature works so that if there is an overheating or wiring problem the printer will stop, and it turns out that it didn't even tell me about it. I am already testing on another older board but also duet 2 with the same revision.

And so the printer reported no error, no notification, nothing in the logs and nothing happened. The printer was printing without a connected motor as if nothing had happened, of course the motor did not move.
In an older version 3.3 we had logs and info about missing pairs for A or B and now nothing.

OwenD

@hobby-store
You can test various faults using M957
https://docs.duet3d.com/en/User_manual/Reference/Gcodes#m957-raise-event-or-trigger

For example

M957 E"driver_error" D3

I just created this job file and uploaded it

;test-job.gcode
G28
while iterations < 100
	G1 X10 F3600
	G1 X150
	M400

If you do not have a macro called driver-error.g in your 0:/sys folder then the job will be paused as per the docs

If you do have a driver-error.g macro, then the content of that macro will be executed. It's up to you whether or not you pause in that case.
The same applies to all the other events.

EDIT:
Forgot to say I'm using a Duet 2 running 3.4.0 in stand alone mode

Hobby-Store

@owend said in Stopping a printing job after a warning or error:

ou do not have a macro called driver-error.g in your 0:/sys folder then the job will be paused as per the docs
If you do have a driver-error.g macro, then the content of that macro will be executed. It's up to you whether or not you pause in that case.
The same applies to all the other events.
EDIT:
Forgot to say I'm using a Duet 2 running 3.4.0 in stand alone mode

Yes, in a controlled environment it does indeed pause the printout. But when the motor is really disconnected, it does not react.

Due to problems with the wiring (sudden cable break) or overheating of the motor controller we had damage mainly to the head carriage and BLTouch. This is quite expensive. Therefore we are looking for a solution to make the printer stop in this situation.

OwenD

@hobby-store
In the case of the example you gave about "phase may be disconnected", the log level is warning.
In that case I would expect it to be written to the console only.
I'm not prepared to disconnect a motor to test though.

Hobby-Store

@owend said in Stopping a printing job after a warning or error:

@hobby-store
In the case of the example you gave about "phase may be disconnected", the log level is warning.
In that case I would expect it to be written to the console only.
I'm not prepared to disconnect a motor to test though.

Only that it does not even inform anymore after the upgrade to 3.4

In 3.3 there were notifications in the log

I can use own driver-warning.g and pause printing?? Have I understood the documentation correctly?
By default when it's not create this file is default is Inform user via console and continue

OwenD

@hobby-store said in Stopping a printing job after a warning or error:

Only that it does not even inform anymore after the upgrade to 3.4

In 3.3 there were notifications in the log

I can use own driver-warning.g and pause printing?? Have I understood the documentation correctly?
By default when it's not create this file is default is Inform user via console and continue

If you want to pause on a warning, then yes, you need driver-warning,g
@DC42 would have to confirm what waning/error disconnecting a stepper completely would cause as opposed to loss of a single wire by breakage.

Hobby-Store

@owend said in Stopping a printing job after a warning or error:

@hobby-store said in Stopping a printing job after a warning or error:

Only that it does not even inform anymore after the upgrade to 3.4

In 3.3 there were notifications in the log

I can use own driver-warning.g and pause printing?? Have I understood the documentation correctly?
By default when it's not create this file is default is Inform user via console and continue

If you want to pause on a warning, then yes, you need driver-warning,g
@DC42 would have to confirm what waning/error disconnecting a stepper completely would cause as opposed to loss of a single wire by breakage.

Ok i must check with this files and back with informations Thx

Hobby-Store

This post is deleted!