VSSA Fault - Duet 3

tom33

Hi,

I have the following error : VSSA Fault

I'im running rrf 3.3 Rc3 on duet 3

tom33

@tom33
M122
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.3RC3 (2021-05-26 12:29:42) running on Duet 3 MB6HC v1.01 or later (standalone mode)
Board ID: 08DJM-9P63L-DJ3T0-6J9DL-3S06S-K81H9
Used output buffers: 1 of 40 (17 max)
=== RTOS ===
Static ram: 150784
Dynamic ram: 94176 of which 72 recycled
Never used RAM 106304, free system stack 180 words
Tasks: NETWORK(ready,27.9%,234) ETHERNET(notifyWait,0.1%,126) HEAT(delaying,0.0%,295) Move(notifyWait,0.0%,352) CanReceiv(notifyWait,0.0%,945) CanSender(notifyWait,0.0%,374) CanClock(delaying,0.0%,339) TMC(notifyWait,8.2%,93) MAIN(running,63.8%,1114) IDLE(ready,0.0%,29), total 100.0%
Owned mutexes:
=== Platform ===
Last reset 00:08:24 ago, cause: reset button
Last software reset at 2021-06-09 10:49, reason: User, GCodes spinning, available RAM 106260, slot 0
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00400000 BFAR 0x00000000 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
Aux0 errors 0,0,0
Aux1 errors 0,0,0
Step timer max interval 126
MCU temperature: min 38.1, current 40.1, max 40.2
Supply voltage: min 24.0, current 24.0, max 24.1, under voltage events: 0, over voltage events: 0, power good: yes
12V rail voltage: min 12.2, current 12.3, max 12.3, under voltage events: 0
Heap OK, handles allocated/used 99/0, heap memory allocated/used/recyclable 2048/408/408, gc cycles 0
Driver 0: position 0, standstill, reads 44498, writes 16 timeouts 0, SG min/max 0/0
Driver 1: position 0, standstill, reads 44500, writes 14 timeouts 0, SG min/max 0/0
Driver 2: position 0, standstill, reads 44500, writes 14 timeouts 0, SG min/max 0/0
Driver 3: position 0, standstill, reads 44501, writes 14 timeouts 0, SG min/max 0/0
Driver 4: position 0, standstill, reads 44501, writes 14 timeouts 0, SG min/max 0/0
Driver 5: position 0, standstill, reads 44504, writes 11 timeouts 0, SG min/max 0/0
Date/time: 2021-06-09 10:58:09
Slowest loop: 36.31ms; fastest: 0.05ms
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 25.0MBytes/sec
SD card longest read time 1.0ms, write time 5.9ms, max retries 0
=== Move ===
DMs created 125, maxWait 0ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== AuxDDARing ===
Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== Heat ===
Bed heaters = 0 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1, chamberHeaters = 3 -1 -1 -1
=== 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
SBC is idle in state(s) 0
Daemon is idle in state(s) 0
Aux2 is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty.
=== Filament sensors ===
Extruder 1: no data received
=== CAN ===
Messages queued 4563, send timeouts 0, received 24, lost 0, longest wait 2ms for reply type 6036, peak Tx sync delay 6, free buffers 49 (min 48), ts 2522/2521/0
=== Network ===
Slowest loop: 69.25ms; fastest: 0.02ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions Telnet(0), 0 sessions
HTTP sessions: 1 of 8

Ethernet -
State: active
Error counts: 0 0 1 0 0
Socket states: 5 2 2 2 2 0 0 0

dc42

@tom33 that usually means that there is a short between your thermistor wiring and your heater wiring on the hot end. Disconnect the thermistors from the Duet one by one until the warning goes away, to find out which thermistor it is.

tom33

@dc42 Thanks, problem resolve !

dc42

I'm glad you resolved it. BTW most other controller boards don't tolerate this type of short, it's likely to wreck the board. We designed Duets to tolerate it, because we know that it is relatively common.