Driver shutdown

fma

Hi!

A few days ago, during a print, I saw a message on the Panel Due saying that Driver 8 (I have a Duex5) was shutdown because of overheating (or something like that).

But Driver 8 is unused, and has no motor connected! I only have a motor on the first channel of the Duex5...

Any idea what happenned ?

Phaedrux

Have you tested if the driver works? Does it still produce the error? Was it actually hot at the time? What does M122 say about those drivers?

fma

@phaedrux No, I didn't check this driver output; I'll do that.
The error did not reprodduce.
It was not hot at all (I checked only with my finger).
I'll run M122 tomorrow.

Thanks.

fma

M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.1.1 running on Duet WiFi 1.02 or later + DueX5
Board ID: 08DDM-9FAM2-LW4S8-6JTDG-3SD6Q-13YRX
Used output buffers: 3 of 24 (12 max)
=== RTOS ===
Static ram: 27980
Dynamic ram: 94292 of which 136 recycled
Exception stack ram used: 472
Never used ram: 8192
Tasks: NETWORK(blocked,364) HEAT(blocked,1224) DUEX(suspended,160) MAIN(running,1880) IDLE(ready,80)
Owned mutexes: WiFi(NETWORK)
=== Platform ===
Last reset 00:04:04 ago, cause: power up
Last software reset at 2021-04-08 17:35, reason: User, spinning module GCodes, available RAM 8016 bytes (slot 3)
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0441f000 BFAR 0xe000ed38 SP 0xffffffff Task MAIN
Error status: 0
MCU temperature: min 13.4, current 23.8, max 23.9
Supply voltage: min 23.4, current 23.7, max 24.5, under voltage events: 0, over voltage events: 0, power good: yes
Driver 0: standstill, SG min/max not available
Driver 1: standstill, SG min/max not available
Driver 2: standstill, SG min/max 0/300
Driver 3: standstill, SG min/max not available
Driver 4: standstill, SG min/max not available
Driver 5: standstill, SG min/max not available
Driver 6: standstill, SG min/max not available
Driver 7: standstill, SG min/max not available
Driver 8: standstill, SG min/max not available
Driver 9: standstill, SG min/max not available
Date/time: 2021-04-18 08:49:10
Cache data hit count 405592994
Slowest loop: 6.09ms; fastest: 0.13ms
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 2.7ms, write time 0.0ms, max retries 0
=== Move ===
Hiccups: 0(0), FreeDm: 169, MinFreeDm: 168, MaxWait: 32481ms
Bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves: 3, completed moves: 3, StepErrors: 0, LaErrors: 0, Underruns: 0, 0  CDDA state: -1
=== AuxDDARing ===
Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0  CDDA state: -1
=== Heat ===
Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1 -1 -1
Heater 0 is on, I-accum = 0.8
Heater 1 is on, I-accum = 0.2
=== 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
Daemon is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Slowest loop: 41.09ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(2) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
HTTP sessions: 1 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 5c:cf:7f:61:99:c5
WiFi Vcc 3.35, reset reason Unknown
WiFi flash size 4194304, free heap 24432
WiFi IP address 192.168.0.3
WiFi signal strength -59dBm, reconnections 0, sleep mode modem
Socket states: 0 0 0 0 0 0 0 0
=== DueX ===
Read count 1, 0.25 reads/min

fma

Mmm, now, over temperature shutdown is reported for driver 7!!!

M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.1.1 running on Duet WiFi 1.02 or later + DueX5
Board ID: 08DDM-9FAM2-LW4S8-6JTDG-3SD6Q-13YRX
Used output buffers: 3 of 24 (13 max)
=== RTOS ===
Static ram: 27980
Dynamic ram: 94564 of which 64 recycled
Exception stack ram used: 584
Never used ram: 7880
Tasks: NETWORK(ready,368) HEAT(blocked,1224) DUEX(suspended,160) MAIN(running,1848) IDLE(ready,80)
Owned mutexes: WiFi(NETWORK)
=== Platform ===
Last reset 05:22:57 ago, cause: power up
Last software reset at 2021-04-08 17:35, reason: User, spinning module GCodes, available RAM 8016 bytes (slot 3)
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0441f000 BFAR 0xe000ed38 SP 0xffffffff Task MAIN
Error status: 0
MCU temperature: min 14.2, current 37.1, max 38.0
Supply voltage: min 23.2, current 23.5, max 24.6, under voltage events: 0, over voltage events: 0, power good: yes
Driver 0: ok, SG min/max 0/413
Driver 1: ok, SG min/max 0/426
Driver 2: standstill, SG min/max 0/300
Driver 3: standstill, SG min/max not available
Driver 4: standstill, SG min/max not available
Driver 5: ok, SG min/max 0/1023
Driver 6: standstill, SG min/max not available
Driver 7: standstill, SG min/max not available
Driver 8: standstill, SG min/max not available
Driver 9: standstill, SG min/max not available
Date/time: 2021-04-18 18:39:39
Cache data hit count 4294967295
Slowest loop: 311.40ms; fastest: 0.13ms
I2C nak errors 0, send timeouts 27, receive timeouts 0, finishTimeouts 27, resets 27
=== Storage ===
Free file entries: 9
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest read time 45.4ms, write time 0.0ms, max retries 0
=== Move ===
Hiccups: 0(0), FreeDm: 163, MinFreeDm: 136, MaxWait: 7796464ms
Bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves: 207672, completed moves: 207641, StepErrors: 0, LaErrors: 0, Underruns: 0, 3  CDDA state: 3
=== AuxDDARing ===
Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0  CDDA state: -1
=== Heat ===
Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1 -1 -1
Heater 0 is on, I-accum = 0.1
Heater 1 is on, I-accum = 0.4
=== GCodes ===
Segments left: 1
Movement lock held by null
HTTP is idle in state(s) 0
Telnet is idle in state(s) 0
File is doing "G1 X213.653 Y124.192 F9000.000" 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
Daemon is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Slowest loop: 40.51ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
HTTP sessions: 1 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 5c:cf:7f:61:99:c5
WiFi Vcc 3.34, reset reason Unknown
WiFi flash size 4194304, free heap 24240
WiFi IP address 192.168.0.3
WiFi signal strength -59dBm, reconnections 0, sleep mode modem
Socket states: 0 0 0 0 0 0 0 0
=== DueX ===
Read count 39, 0.12 reads/min

Phaedrux

and was driver 7 in use at the time?

fma

@phaedrux Nope! Only Driver 5 is in use (first one on Duex5), for the hotend...

How driver status are reported? Could it be a wire problem in the cable between the 2 boards?

SIam

@fma

I'm not sure, but maybe this can be an issue from the flat cable

I2C nak errors 0, send timeouts 27, receive timeouts 0, finishTimeouts 27, resets 27

Phaedrux

How is your duex wired up? Particularly the grounding?

Anything running near the ribbon cable?

https://duet3d.dozuki.com/Wiki/Duex2_and_Duex5_Features#Section_Wiring

fma

Boards are wired as described in the documentation. Nothing is near the ribbon cable.
But I'll check all connections...