Duet3 6hc malfunction?

[Heartleander81]

Today I had the problem that I had the message VSSA Vault. After that, the diagnosis LED had shone red continuously. After I had removed the thermistors and restarted it took a moment and the diagnosis led flashed as usual. Thermistors back on and everything back as before, only with V12 I only have 9.6V. is the board broken now or is there just a problem with the cables.

M122
=== Diagnostics === RepRapFirmware for Duet 3 MB6HC version 3.3 (2021-06-15 21:45:47) running on Duet 3 MB6HC v1.01 or later (SBC mode) 
Board ID: 08DJM-956L2-G43S8-6JTDG-3SJ6P-KB0UG 
Used output buffers: 1 of 40 (15 max) 
=== RTOS === 
Static ram: 150904 
Dynamic ram: 62360 of which 76 recycled 
Never used RAM 140852, free system stack 216 words 
Tasks: SBC(ready,4.3%,349) HEAT(delaying,0.0%,350) Move(notifyWait,0.0%,352) CanReceiv(notifyWait,0.0%,944) CanSender(notifyWait,0.0%,374) CanClock(delaying,0.0%,342) TMC(notifyWait,0.0%,105) 
MAIN(running,95.6%,974) IDLE(ready,0.0%,29), total 100.0% 
Owned mutexes: HTTP(MAIN) 
=== Platform === 
Last reset 00:12:28 ago, cause: power up 
Last software reset at 2021-07-30 20:35, reason: MemoryProtectionFault mmarValid daccViol, GCodes spinning, available RAM 140852, slot 1 
Software reset code 0x4163 HFSR 0x00000000 CFSR 0x00000082 ICSR 0x00400804 BFAR 0x00000038 SP 0x2041b178 Task MAIN Freestk 1661 ok 
Stack: 00000000 00000001 00000001 00000000 00000000 0047a515 0047a16c 610f0000 00000000 0047a51f 00000000 00000000 baef53bb 0000000a d7b71d43 2042b7f0 20419728 2042d10c 00000000 00000001 
00000000 0047a1d7 2042d10c fffc0000 003fffff ffffffff ffffffff 
Error status: 0x00 
Aux0 errors 0,0,0 
Step timer max interval 751 
MCU temperature: min 39.4, current 39.7, max 39.9 
Supply voltage: min 24.8, current 24.8, max 24.9, under voltage events: 0, over voltage events: 0, power good: no 
12V rail voltage: min 9.5, current 9.6, max 9.6, under voltage events: 0 
Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0 
Driver 0: position 0, ok, reads 0, writes 0 timeouts 0, SG min/max not available 
Driver 1: position 0, ok, reads 0, writes 0 timeouts 0, SG min/max not available 
Driver 2: position 0, ok, reads 0, writes 0 timeouts 0, SG min/max not available 
Driver 3: position 0, ok, reads 0, writes 0 timeouts 0, SG min/max not available 
Driver 4: position 0, ok, reads 0, writes 0 timeouts 0, SG min/max not available 
Driver 5: position 0, ok, reads 0, writes 0 timeouts 0, SG min/max not available 
Date/time: 2021-07-30 20:48:11 
Slowest loop: 1.03ms; fastest: 0.05ms 
=== Storage === 
Free file entries: 10 
SD card 0 not detected, interface speed: 37.5MBytes/sec 
SD card longest read time 0.0ms, write time 0.0ms, 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 = -1 -1 -1 -1 
=== GCodes === 
Segments left: 0 
Movement lock held by null 
HTTP* is doing "M122" 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. 
=== CAN === 
Messages queued 2047, received 0, lost 0, longest wait 0ms for reply type 0, peak Tx sync delay 0, free buffers 49 (min 49), ts 1137/0/0 
Tx timeouts 0,0,1137,0,0,910 last cancelled message type 4514 dest 127 
=== SBC interface === 
State: 4, failed transfers: 1, checksum errors: 0 
Last transfer: 0ms ago 
RX/TX seq numbers: 27002/27002 
SPI underruns 0, overruns 0 
Disconnects: 0, timeouts: 0, IAP RAM available 0x2c83c 
Buffer RX/TX: 0/0-0 
=== Duet Control Server === 
Duet Control Server v3.3.0 Code buffer space: 4072 
Configured SPI speed: 8000000Hz 
Full transfers per second: 35.52, max wait times: 27.4ms/0.0ms 
Codes per second: 0.00 
Maximum length of RX/TX data transfers: 3668/816

[Heartleander81]

After I have the Accelerometer turn off from the Bord, have I 16V on the 12V side. Have anyone a tip for me?

[Phaedrux]

Can you show us your wiring? Did you perhaps short something out?
Perhaps remove all wiring and check the board with only USB connected first and then start adding back components one at a time.

[dc42]

@Heartleander81 after you have checked that it is working as far as expected with just USB power connected, please remove the USB power, connect just VIN power, and run M122 to see what it reports for the VIN and 12V rails.

The driver error reports are probably caused by the 12V rail reading low. That in turn could be caused by overloading the 12V rail, for example if a device connected to an OUT port that is set for 12V output was drawing too much current.

[Heartleander81]

@dc42 I have found the problem.
After I have turn off my accelerometer Was 16V on 12V side. Next Day I turn on the printer and have 12V on 12V side. At Moment looks all good.

[Heartleander81]

@phaedrux thanks for your Info.

I hope the board was not damaged by the accelerometer error.

If necessary, I have a new Duet3 6HC board at home since yesterday as a replacement.