When does a board give a Vdd brownout error?
-
Hi, can you help me understand when a board gives a vdd brownout error?
What triggers this event?
What sensors this event is based on? -
@Inlinebrother What board are you using, when are you seeing this error, if it is being reported in the M122 output, please post that output.
-
@gloomyandy Hi
It's a Fysetc Big Dipper boardM122 === Diagnostics === RepRapFirmware for Duet 3 Mini 5+ version 3.5.3 (2024-09-18 11:25:48) running on Duet 3 Mini5plus WiFi (standalone mode) Board ID: RHYS5-6J9MK-K65J0-40TK2-JRW2Z-ZLX8A Used output buffers: 3 of 40 (18 max) === RTOS === Static ram: 103368 Dynamic ram: 121884 of which 12 recycled Never used RAM 16484, free system stack 202 words Tasks: NETWORK(2,nWait 7,12.1%,217) HEAT(3,nWait 1,0.0%,335) Move(4,nWait 6,0.0%,355) CanReceiv(6,nWait 1,0.0%,939) CanSender(5,nWait 7,0.0%,336) CanClock(7,delaying,0.0%,339) TMC(4,nWait 6,1.4%,110) MAIN(1,running,84.8%,651) IDLE(0,ready,0.9%,29) AIN(4,delaying,0.8%,263), total 100.0% Owned mutexes: WiFi(NETWORK) === Platform === Last reset 00:00:22 ago, cause: Vdd brownout Last software reset at 2024-10-24 17:04, reason: User, Gcodes spinning, available RAM 13464, slot 1 Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00000000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a Error status: 0x00 MCU revision 3, ADC conversions started 17648, completed 17647, timed out 0, errs 0 MCU temperature: min 33.3, current 34.0, max 34.4 Supply voltage: min 23.9, current 24.1, max 24.1, 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 0, read errors 0, write errors 0, ifcnt 11, reads 2055, writes 11, timeouts 0, DMA errors 0, CC errors 0 Driver 1: standstill, SG min 0, read errors 0, write errors 0, ifcnt 11, reads 2055, writes 11, timeouts 0, DMA errors 0, CC errors 0 Driver 2: standstill, SG min 0, read errors 0, write errors 0, ifcnt 10, reads 2056, writes 10, timeouts 0, DMA errors 0, CC errors 0 Driver 3: standstill, SG min 0, read errors 0, write errors 0, ifcnt 10, reads 2056, writes 10, timeouts 0, DMA errors 0, CC errors 0 Driver 4: standstill, SG min 0, read errors 0, write errors 0, ifcnt 10, reads 2056, writes 10, timeouts 0, DMA errors 0, CC errors 0 Driver 5: standstill, SG min 0, read errors 0, write errors 0, ifcnt 11, reads 2055, writes 11, timeouts 0, DMA errors 0, CC errors 0 Driver 6: standstill, SG min 0, read errors 0, write errors 0, ifcnt 10, reads 2056, writes 10, timeouts 0, DMA errors 0, CC errors 0 Date/time: 2024-10-24 17:13:08 Cache data hit count 43616670 Slowest loop: 4.59ms; fastest: 0.16ms === Storage === Free file entries: 20 SD card 0 detected, interface speed: 22.5MBytes/sec SD card longest read time 0.7ms, write time 0.0ms, max retries 0 === Move === DMs created 83, segments created 0, maxWait 0ms, bed compensation in use: none, height map offset 0.000, max steps late 0, min interval 0, bad calcs 0, ebfmin 0.00, ebfmax 0.00 no step interrupt scheduled Moves shaped first try 0, on retry 0, too short 0, wrong shape 0, maybepossible 0 === DDARing 0 === Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1 === DDARing 1 === 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 === GCodes === Movement locks held by null, 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 File2 is idle in state(s) 0 Queue2 is idle in state(s) 0 Q0 segments left 0, axes/extruders owned 0x0000000 Code queue 0 is empty Q1 segments left 0, axes/extruders owned 0x0000000 Code queue 1 is empty === CAN === Messages queued 205, received 0, lost 0, errs 108148, boc 0 Longest wait 0ms for reply type 0, peak Tx sync delay 0, free buffers 26 (min 26), ts 115/0/0 Tx timeouts 0,0,114,0,0,89 last cancelled message type 30 dest 127 === Network === Slowest loop: 4.43ms; fastest: 0.00ms Responder states: MQTT(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) HTTP sessions: 1 of 8 === WiFi === Interface state: active Module is connected to access point Failed messages: pending 0, notrdy 0, noresp 0 Firmware version 2.1.0 MAC address 08:3a:8d:eb:24:44 Module reset reason: Power up, Vcc 3.38, flash size 2097152, free heap 42924 WiFi IP address 192.168.1.69 Signal strength -47dBm, channel 7, mode 802.11n, reconnections 0 Clock register 00002001 Socket states: 0 0 0 0 0 0 0 0You didn't answer my question though)
I also want to debug this problem, but for now I can't understand what to look for exactly.
As far as I understand brownout means that the power was lost
Though the voltage is fine
The 450w PSU for FFCP should be fine
I checked my wiring lots of times now and I did find a lot of mistakes
If I have something wrong it's not obvious for me at allThis thing happens to the printer after a few minutes of printing
If I restart it happens almost at the same time -
@Inlinebrother That status means that the main mcu has reset because it detected a brownout situation. Which means that the ATSAME54P20A has decided that the supply to the main chip is not sufficient/stable enough to operate correctly. If this happens during a print I'd be checking for something shorting out either the 5V or 3.3V supply. Either that or you are exceeding the max current that your psu can supply.
-
I fried my first board I guess.
New board is working fine
