@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

@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 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.

@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.

@robiiinx
Do you have line like

M950 S0 C"exp.heater3"
M558 P9 C"^zprobe.in" H5 F120 T6000 

and try use

M280 P0 S10

M280 P0 S90

look on this docs https://docs.duet3d.com/en/User_manual/Connecting_hardware/Z_probe_connecting

@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 said in Duet 2 WiFi v1.04c and problems with stepstick:

M122

Q: So drivers 0 and 1 are having the same issue, but the motors and cabling work correctly when using another driver?
A: Yes

Q: When and where was the Duet purchased?

A: We are your official resellers in Poland. The board is from a July 2021 order and the customer bought it in October (We built 2 printers for a client). He has now sent the printer back to us for repair and we have replaced the board for him after diagnosing it for 2 weeks.

M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.4.0 (2022-03-15 18:58:31) running on Duet WiFi 1.02 or later + DueX5v0.11
Board ID: 0JD0M-9P6B2-NJ4S8-6J9FA-3SJ6K-KB4UK
Used output buffers: 3 of 24 (22 max)
=== RTOS ===
Static ram: 23868
Dynamic ram: 75184 of which 24 recycled
Never used RAM 12788, free system stack 112 words
Tasks: NETWORK(ready,12.5%,234) HEAT(notifyWait,0.0%,316) Move(notifyWait,0.0%,293) DUEX(notifyWait,0.0%,24) MAIN(running,87.4%,458) IDLE(ready,0.1%,30), total 100.0%
Owned mutexes: WiFi(NETWORK)
=== Platform ===
Last reset 00:32:24 ago, cause: power up
Last software reset at 2022-04-06 15:49, reason: User, GCodes spinning, available RAM 12716, slot 2
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x08
Aux0 errors 0,1,0
Step timer max interval 0
MCU temperature: min 24.8, current 28.4, max 29.1
Supply voltage: min 24.0, current 24.2, max 24.4, under voltage events: 0, over voltage events: 0, power good: yes
Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0
Events: 0 queued, 0 completed
Driver 0: standstill, SG min n/a
Driver 1: standstill, SG min n/a
Driver 2: standstill, SG min 0
Driver 3: standstill, SG min n/a
Driver 4: standstill, SG min n/a
Driver 5: standstill, SG min 0
Driver 6: standstill, SG min 0
Driver 7: standstill, SG min 0
Driver 8: standstill, SG min n/a
Driver 9: standstill, SG min 0
Driver 10: 
Driver 11: 
Date/time: 2022-04-07 11:36:33
Cache data hit count 4294967295
Slowest loop: 30.53ms; fastest: 0.14ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest read time 3.9ms, write time 13.4ms, max retries 0
=== Move ===
DMs created 83, segments created 9, maxWait 74663ms, bed compensation in use: mesh, comp offset 0.000
=== MainDDARing ===
Scheduled moves 237, completed 237, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 1], CDDA state -1
=== AuxDDARing ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== Heat ===
Bed heaters 0 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0
Heater 0 is on, I-accum = 0.7
Heater 1 is on, I-accum = 0.0
=== GCodes ===
Segments left: 0
Movement lock held by null
HTTP is idle in state(s) 0
Telnet is idle in state(s) 0
File is idle in state(s) 0
USB is idle in state(s) 0
Aux is idle in state(s) 0
Trigger is idle in state(s) 0
Queue is idle in state(s) 0
LCD is idle in state(s) 0
Daemon is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty
=== DueX ===
Read count 2, 0.06 reads/min
=== Network ===
Slowest loop: 15.77ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
HTTP sessions: 2 of 8
- WiFi -
Network state is active
WiFi module is connected to access point 
Failed messages: pending 0, notready 0, noresp 0
WiFi firmware version 1.23
WiFi MAC address e0:98:06:22:cf:c6
WiFi Vcc 3.40, reset reason Turned on by main processor
WiFi flash size 4194304, free heap 20400
WiFi IP address 10.44.0.89
WiFi signal strength -59dBm, mode none, reconnections 0, sleep mode modem
Clock register ffffffff
Socket states: 0 4 0 0 0 0 0 0

M98 P"config.g"
HTTP is enabled on port 80
FTP is disabled
TELNET is disabled
Error: Heater 7 not found
Warning: Heater 0 predicted maximum temperature at full power is 321°C
Warning: Heater 0 predicted maximum temperature at full power is 194°C
Warning: Heater 1 predicted maximum temperature at full power is 504°C

And config.g
config.g

@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.

Ok thx.

Is it possible to stop or pause printing automatically when a problem with an overheated engine controller or faulty engine wiring is detected when we receive a notification in the logs

2022-04-04 19:20:23 [warn] Warning: motor phase A may be disconnected reported by driver(s) 1
2022-04-04 19:20:23 [warn] Warning: motor phase B may be disconnected reported by driver(s) 1

Is there any solution for the printer to pause printing with this type of error? Because we have already had 2 head repairs with bltouch broken because of this problem.

I have firmware ver 3.3

Hello.

We have a problem with one of the motherboards in o printer. We have 3 HevORT printers on the same build and settings but the problem is only in one.

I would like to point out that we have changed motors, wiring, measured everything and it is ok. We have good cooling because 2 fans for electronics from the top and a one fan that cools the back of the board.

We use Duet 2 Wifi 1.04c with DUEX5
Board: Duet 2 WiFi (2WiFi)
Firmware: RepRapFirmware for Duet 2 WiFi/Ethernet 3.3 (2021-06-15)
Duet WiFi Server Version: 1.23

One of the motor drivers on port 0 is giving information that there are no A and B pairs connected. It is most likely defective. We switched the motor to another port on the expander

power up + 22:54:52 [warn] Warning: motor phase A may be disconnected reported by driver(s) 0
power up + 22:54:52 [warn] Warning: motor phase B may be disconnected reported by driver(s) 0

However, now port 1 of the motor where we have the Y axis connected, after some time randomly displays information about the lack of correct connection of motor pairs A, B

2022-04-01 22:30:03 [warn] Error: over temperature shutdown reported by driver(s) 1
2022-04-01 22:30:08 [warn] Warning: motor phase A may be disconnected reported by driver(s) 1
2022-04-01 22:30:08 [warn] Warning: motor phase B may be disconnected reported by driver(s) 1

Or with no temp error

2022-04-04 19:20:23 [warn] Warning: motor phase A may be disconnected reported by driver(s) 1
2022-04-04 19:20:23 [warn] Warning: motor phase B may be disconnected reported by driver(s) 1

And the printer continues to print without a single axis.

We would like to replace it under warranty.

P.s.
Is there any solution for the printer to pause printing with this type of error? Because we have already had 2 head repairs with bltouch broken because of this problem.