Help me! I made a duet3 6ch, and the power failed

wanwan

@Rushmere3D Thank you. I made it myself

Rushmere3D

@wanwan That's impressive to be fair and I'm not the person to help, lol.

o_lampe

@wanwan
Impressive indeed.
Do these two parts touch and cause a shortcut?

wanwan

@o_lampe I checked. No problem. And they're parallel connection

dc42

Are you using our standard RRF 3.2 firmware binary, or have you built your own?

wanwan

@dc42 Use the official standard firmware. Now the problem has been solved. thank you

o_lampe

@wanwan
If you have a few more empty PCBs, you could populate them step-by-step, beginning with the DC-DC power converter and test every function one at a time.
Or do a shortcut test on an empty PCB, maybe some inner layers aren't OK?

It seems, there is a lot of solder on the pads, maybe there's a heatsink/GND pad under the MPU or the MOSFETs which got too much solderpaste and caused a shortcut?

wanwan

@o_lampe I want to have a cheap DUET3. I decided to do it myself. Now it doesn't seem like a good idea

dc42

@wanwan said in Help me! I made a duet3 6ch, and the power failed:

@dc42 Use the official standard firmware. Now the problem has been solved. thank you

How did you solve it?

I asked about the firmware because the stack trace didn't seem to match up exactly with the map file for the standard firmware binary.

wanwan

@dc42 I made a mistake 。Down to 3.0, the problem still exists.

wanwan

@dc42 This problem is an error that occurred after the driver was burned

dc42

@wanwan said in Help me! I made a duet3 6ch, and the power failed:

@dc42 This problem is an error that occurred after the driver was burned

Can you explain more? I would not expect the firmware to crash even if a driver failed, unless the failed driver fed injection current into the MCU sufficient to cause it to behave incorrectly. What type of driver did you connect that failed?

wanwan

@dc42 Do you mean that the current breaks down the MUC when the drive is burned?
I connected a piece of TMC5160A

dc42

@wanwan said in Help me! I made a duet3 6ch, and the power failed:

Do you mean that the current breaks down the MUC when the drive is burned?

It's possible that a burned driver may feed current into the MCU pin driving Step, Dir, or one of the SPI signals. The input protection diodes shunt this current to Vcc (3.3V). If the current is small enough, operation of the chip will be unaffected. With somewhat higher current, the chip may malfunction, but no permanent damage will be done. Higher still and permanent damage will be done.

What I would ideally like to know is whether the firmware crashed because it didn't get the expected response from the driver (which I would regard as a firmware bug to be fixed), or the MCU crashed because of injection current.

Veti

@wanwan said in Help me! I made a duet3 6ch, and the power failed:

I decided to do it myself. Now it doesn't seem like a good idea

did the parts work out to be more in the end?

wanwan

@dc42 After hearing your explanation, I think it's ，the MCU crashed because of injection current

wanwan

This is just generated

2021/2/4下午9:57:21	M122
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.2 running on Duet 3 MB6HC v1.01 or later (standalone mode)
Board ID: 08DGM-9561L-D63T4-6J1FA-3S46J-KA0RG
Used output buffers: 1 of 40 (25 max)
=== RTOS ===
Static ram: 149788
Dynamic ram: 92280 of which 404 recycled
Never used RAM 116360, free system stack 187 words
Tasks: NETWORK(ready,223) ETHERNET(blocked,109) HEAT(blocked,353) CanReceiv(blocked,927) CanSender(blocked,371) CanClock(blocked,349) TMC(blocked,65) MAIN(running,1148) IDLE(ready,19)
Owned mutexes:
=== Platform ===
Last reset 02:36:41 ago, cause: power up
Last software reset details not available
Error status: 0x00
Aux0 errors 0,0,0
Aux1 errors 0,0,0
MCU temperature: min 31.7, current 32.3, max 32.9
Supply voltage: min 3.9, current 3.9, max 4.0, under voltage events: 0, over voltage events: 0, power good: no
12V rail voltage: min 3.8, current 3.9, max 7.1, under voltage events: 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-02-04 21:57:18
Slowest loop: 1.41ms; fastest: 0.05ms
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 25.0MBytes/sec
SD card longest read time 0.7ms, 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 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.
=== Network ===
Slowest loop: 0.97ms; 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 0 0 0
Socket states: 5 2 2 2 2 0 0 0
=== CAN ===
Messages queued 0, send timeouts 46881, received 0, lost 0, longest wait 0ms

dc42

@wanwan said in Help me! I made a duet3 6ch, and the power failed:

Last reset 02:36:41 ago, cause: power up

So if the reset was unexplained, it was caused by a loss of power.

wanwan

@dc42 I'm relieved that the worst didn't happen.Thank you

jrockland

soo... you did your own board, and put Duet3D logo on it ? am I missing something here ?