Duet 3 Mini 5+ VIN under-voltage issues in SBC mode

lodger

@dc42 Mornings.

The print completed . with no under voltage triggers at all. I will try print something else and report if i get any more problems

dc42

@lodger said in Duet 3 Mini 5+ VIN under-voltage issues in SBC mode:

@dc42 Mornings.

The print completed . with no under voltage triggers at all. I will try print something else and report if i get any more problems

Thanks for the update.

Anyone else having this problem and happy to use beta firmware, feel free to try the firmware that I linked to above. It's compatible with DWC 3.3beta2.

Serbitar

I have put my machine back into SBC mode running the linked beta firmware.

It completed a 12h print over night, print queue has shorter jobs for the next few days. I will update if there are any under voltage detection issues.

dc42

@Serbitar, thanks for the update.

Serbitar

Not fixed i'm afraid

Mar 24 19:21:32 DuetControlServer[3177]: Print auto-paused due to low voltage
Mar 24 19:21:32 DuetControlServer[3177]: [warn] VIN under-voltage event (0.0V)

m122
=== Diagnostics ===
RepRapFirmware for Duet 3 Mini 5+ version 3.3beta2+1 running on Duet 3 Mini5plus WiFi (SBC mode)
Board ID: W4ZW4-V296U-D65J0-40KM0-LR03Z-H6928
Used output buffers: 1 of 40 (32 max)
=== RTOS ===
Static ram: 99720
Dynamic ram: 98408 of which 24 recycled
Never used RAM 45552, free system stack 88 words
Tasks: Linux(ready,145) HEAT(notifyWait,299) CanReceiv(notifyWait,943) CanSender(notifyWait,358) CanClock(delaying,340) TMC(notifyWait,109) MAIN(running,310) IDLE(ready,20) AIN(notifyWait,260)
Owned mutexes: HTTP(MAIN)
=== Platform ===
Last reset 21:38:59 ago, cause: software
Last software reset at 2021-03-23 21:38, reason: User, none spinning, available RAM 46528, slot 2
Software reset code 0x0012 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00000000 BFAR 0xe000ed38 SP 0x00000000 Task Linu Freestk 0 n/a
Error status: 0x00
Aux0 errors 0,0,0
Aux1 errors 0,0,0
Supply voltage: min 24.1, current 24.2, max 24.4, under voltage events: 3, 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
Driver 0: position -5573, standstill, SG min/max 0/0, read errors 0, write errors 0, ifcnt 19, reads 5889, writes 9, timeouts 17, DMA errors 0, failedOp 0x01
Driver 1: position -6035, standstill, SG min/max 0/44, read errors 0, write errors 0, ifcnt 20, reads 5906, writes 9, timeouts 0, DMA errors 0
Driver 2: position 8601, standstill, SG min/max 0/0, read errors 0, write errors 0, ifcnt 19, reads 5906, writes 9, timeouts 0, DMA errors 0
Driver 3: position 0, standstill, SG min/max 0/256, read errors 0, write errors 0, ifcnt 22, reads 5906, writes 9, timeouts 0, DMA errors 0
Driver 4: position 0, standstill, SG min/max 0/210, read errors 0, write errors 0, ifcnt 22, reads 5906, writes 9, timeouts 0, DMA errors 0
Driver 5: position 0, standstill, SG min/max 0/2, read errors 0, write errors 0, ifcnt 22, reads 5906, writes 9, timeouts 0, DMA errors 0
Driver 6: position 0, standstill, SG min/max 2/2, read errors 0, write errors 0, ifcnt 22, reads 5906, writes 9, timeouts 0, DMA errors 0
Date/time: 2021-03-24 19:22:01
Cache data hit count 4294967295
Slowest loop: 1.95ms; fastest: 0.13ms
=== Storage ===
Free file entries: 10
SD card 0 not detected, interface speed: 0.0MBytes/sec
SD card longest read time 0.0ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 83, maxWait 0ms, bed compensation in use: mesh, comp offset 0.000
=== MainDDARing ===
Scheduled moves 467805, completed moves 467805, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 1], 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, chamberHeaters = -1 -1
Heater 0 is on, I-accum = 0.0
Heater 1 is on, I-accum = 0.5
=== 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 doing "G1 X-68.586998 Y-74.568001 E0.009290" 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 0 sensor: ok
Extruder 1 sensor: ok
=== CAN ===
Messages queued 266, send timeouts 266, received 0, lost 0, longest wait 0ms for reply type 0, peak Tx sync delay 0, free buffers 17 (min 17)
Last cancelled message type 30 dest 127
=== SBC interface ===
State: 4, failed transfers: 0
Last transfer: 5ms ago
RX/TX seq numbers: 65096/65096
SPI underruns 0, overruns 0
Number of disconnects: 0, IAP RAM available 0x11578
Buffer RX/TX: 1776/3288-0
=== Duet Control Server ===
Duet Control Server v3.3-b2
File:
Buffered code: G1 X-68.587 Y-74.568 E0.00929
Buffered code: G1 X-67.933 Y-73.726 E0.01535
Buffered code: G1 X-67.168 Y-72.475 E0.02112
Buffered code: G1 X-66.365 Y-70.761 E0.02725
Buffered code: G1 X-65.747 Y-68.922 E0.02792
Buffered code: G1 X-67.640 Y-69.345 E0.02792
Buffered code: G1 X-69.429 Y-69.963 E0.02725
Buffered code: G1 X-70.754 Y-70.594 E0.02112
Buffered code: G1 X-71.659 Y-71.156 E0.01535
Buffered code: G1 X-72.167 Y-71.554 E0.00929
Buffered code: G1 X-72.601 Y-72.094 E0.00997
Buffered code: G1 X-75.105 Y-70.343 E0.04398
Buffered code: G1 X-74.694 Y-69.718 E0.01078
Buffered code: G1 X-74.473 Y-69.112 E0.00928
Buffered code: G1 X-74.219 Y-68.077 E0.01535
Buffered code: G1 X-74.028 Y-66.623 E0.02111
Buffered code: G1 X-73.992 Y-64.730 E0.02725
Buffered code: G1 X-74.175 Y-62.799 E0.02792
Buffered code: G1 X-75.733 Y-63.955 E0.02792
Buffered code: G1 X-77.116 Y-65.248 E0.02725
Buffered code: G1 X-78.069 Y-66.363 E0.02112
Buffered code: G1 X-78.668 Y-67.244 E0.01535
Buffered code: G1 X-78.970 Y-67.814 E0.00929
Buffered code: G1 X-79.146 Y-68.484 E0.00997
Buffered code: G1 X-82.146 Y-67.903 E0.04398
Buffered code: G1 X-82.025 Y-67.165 E0.01077
Buffered code: G1 X-82.070 Y-66.521 E0.00929
Buffered code: G1 X-82.258 Y-65.472 E0.01535
Buffered code: G1 X-82.675 Y-64.066 E0.02112
Buffered code: G1 X-83.413 Y-62.322 E0.02725
Buffered code: G1 X-84.365 Y-60.633 E0.02792
Buffered code: G1 X-85.318 Y-62.322 E0.02792
==> 1512 bytes
Code buffer space: 1660
Configured SPI speed: 8000000 Hz
Full transfers per second: 47.08
Codes per second: 17.66
Maximum length of RX/TX data transfers: 5884/1664
File /opt/dsf/sd/gcodes/eggGears-2and6_0.08mm_PETG_ENDER3_6h50m.gcode is selected, processing

ukwebb

Just to add another voice, I and also getting this same issue.

Last night, 70% and 5 hours into a print it just stopped, and displayed VIN undervoltage event (0.0v) and then Insufficient axis homed

My setup is based around a coreXY machine, with a dedicated meanwell 5v 5a psu for the pi, and a meanwell 24v 6amp supply for the printer, the hot bed is 240v

Also, this hasn't happed until recently - i think after i did an apt update. so it was probably fine on 3.1 but not 3.2

lodger

@ukwebb Have you tried the beta DC24 posted above.

dc42

@Serbitar said in Duet 3 Mini 5+ VIN under-voltage issues in SBC mode:

Not fixed i'm afraid

Please can you run M115 to confirm the build date of the firmware you are using.

Serbitar

@dc42

FIRMWARE_NAME: RepRapFirmware for Duet 3 Mini 5+ FIRMWARE_VERSION: 3.3beta2+1 ELECTRONICS: Duet 3 Mini5plus WiFi FIRMWARE_DATE: 2021-03-19 18:26:13

Serbitar

After the previous failure I dropped the SPI rate to 2MHz but that hasn't helped. Printer just stopped while doing G29 with the dreaded under-voltage event.

dc42

@Serbitar, thanks for the additional data point.

ukwebb

@lodger No i haven't, as @Serbitar has already said its not fixed the issue

droftarts

@Serbitar I've been running 'air' prints on my test rig today. I've had one under-voltage event, 1h 18m into a 3h 30m print, but running the same exact file and settings did not provoke another. So trying to get to the bottom of this issue is, unfortunately, taking some time.

Ian

Serbitar

@droftarts Yeah. I haven't worked out a pattern yet. Please let me know if I can do any useful testing.

lodger

@droftarts When DC42 ask on Saturday I also printed the same file without issue .

I have been printing around the clock up till Tuesday. Again without issue. There is just no patten.

I have one of the first batch of boards, and on a earlier firmware (dont ask what one).
I am sure i had this happen in standalone mode. So since Tuesday i have been printing non stop trying to prove this.

I have to say though i am getting bloody sick of all these massive 3dbenchy boats lying around my living room. lol

dc42

I have put new firmware at 2021-03-26 10:59:15. Those of you who have experienced this issue and have an idle machine, please can you try it and do a print (an air print will do, no need to waste filament). If you get a VIN undervoltage event, please post a M122 report. M115 should report firmware date 2021-03-26 10:59:15 for this build.

Serbitar

@dc42 Same dropbox link as the previous one?

dc42

I'm sorry, i forgot to include the link. It's probably the same as the previous one, but here it is again: https://www.dropbox.com/sh/6203euyyobllic5/AABTHIbn7F_maK9p-oy7vq3Ea?dl=0.

Serbitar

Sadly another failure, with the new firmware.

FIRMWARE_NAME: RepRapFirmware for Duet 3 Mini 5+ FIRMWARE_VERSION: 3.3beta2+1 ELECTRONICS: Duet 3 Mini5plus WiFi FIRMWARE_DATE: 2021-03-26 10:59:15

I still have

  "SpiFrequency": 2000000,

Mar 26 19:28:05 ender3 DuetControlServer[13516]: [error] === Diagnostics ===
Mar 26 19:28:05 ender3 DuetControlServer[13516]: RepRapFirmware for Duet 3 Mini 5+ version 3.3beta2+1 running on Duet 3 Mini5plus WiFi (SBC mode)
Mar 26 19:28:05 ender3 DuetControlServer[13516]: Board ID: W4ZW4-V296U-D65J0-40KM0-LR03Z-H6928
Mar 26 19:28:05 ender3 DuetControlServer[13516]: Used output buffers: 2 of 40 (12 max)
Mar 26 19:28:05 ender3 DuetControlServer[13516]: === RTOS ===
Mar 26 19:28:05 ender3 DuetControlServer[13516]: Static ram: 100008
Mar 26 19:28:05 ender3 DuetControlServer[13516]: Dynamic ram: 98412 of which 24 recycled
Mar 26 19:28:05 ender3 DuetControlServer[13516]: Never used RAM 45260, free system stack 114 words
Mar 26 19:28:05 ender3 DuetControlServer[13516]: Tasks: Linux(ready,145) HEAT(delaying,299) CanReceiv(notifyWait,943) CanSender(notifyWait,358) CanClock(delaying,340) TMC(notifyWait,109) MAIN(running,310) IDLE(ready,20) AIN(delaying,258)
Mar 26 19:28:05 ender3 DuetControlServer[13516]: Owned mutexes: Autopause(MAIN)
Mar 26 19:28:05 ender3 DuetControlServer[13516]: === Platform ===
Mar 26 19:28:05 ender3 DuetControlServer[13516]: Last reset 01:52:11 ago, cause: software
Mar 26 19:28:05 ender3 DuetControlServer[13516]: Last software reset at 2021-03-25 17:02, reason: User, none spinning, available RAM 45656, slot 1
Mar 26 19:28:05 ender3 DuetControlServer[13516]: Software reset code 0x0012 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00000000 BFAR 0xe000ed38 SP 0x00000000 Task Linu Freestk 0 n/a
Mar 26 19:28:05 ender3 DuetControlServer[13516]: Error status: 0x00
Mar 26 19:28:05 ender3 DuetControlServer[13516]: Aux0 errors 0,0,0
Mar 26 19:28:05 ender3 DuetControlServer[13516]: Aux1 errors 0,0,0
Mar 26 19:28:05 ender3 DuetControlServer[13516]: ADC conversions started 3353356, completed 3353355, timed out 0
Mar 26 19:28:05 ender3 DuetControlServer[13516]: Supply voltage: min 0.0, current 24.2, max 24.8, under voltage events: 2, over voltage events: 0, power good: no
Mar 26 19:28:05 ender3 DuetControlServer[13516]: Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0
Mar 26 19:28:05 ender3 DuetControlServer[13516]: Driver 0: position -8051, standstill, SG min/max 0/0, read errors 0, write errors 2, ifcnt 10, reads 16127, writes 18, timeouts 29, DMA errors 0, failedOp 0x41
Mar 26 19:28:05 ender3 DuetControlServer[13516]: Driver 1: position 612, standstill, SG min/max 0/88, read errors 0, write errors 2, ifcnt 12, reads 16131, writes 20, timeouts 23, DMA errors 0, failedOp 0x72
Mar 26 19:28:05 ender3 DuetControlServer[13516]: Driver 2: position 2703, ok, SG min/max 0/272, read errors 0, write errors 2, ifcnt 20, reads 16145, writes 28, timeouts 0, DMA errors 0
Mar 26 19:28:05 ender3 DuetControlServer[13516]: Driver 3: position 0, ok, SG min/max 0/424, read errors 0, write errors 2, ifcnt 20, reads 16069, writes 28, timeouts 76, DMA errors 0, failedOp 0x72
Mar 26 19:28:05 ender3 DuetControlServer[13516]: Driver 4: position 0, standstill, SG min/max 0/406, read errors 0, write errors 2, ifcnt 20, reads 16144, writes 28, timeouts 2, DMA errors 0, failedOp 0x6a
Mar 26 19:28:05 ender3 DuetControlServer[13516]: Driver 5: position 0, ok, SG min/max 0/102, read errors 0, write errors 2, ifcnt 20, reads 16125, writes 28, timeouts 20, DMA errors 0, failedOp 0x41
Mar 26 19:28:05 ender3 DuetControlServer[13516]: Driver 6: position 0, ok, SG min/max 0/118, read errors 0, write errors 2, ifcnt 20, reads 15081, writes 28, timeouts 1064, DMA errors 0, failedOp 0x6a
Mar 26 19:28:05 ender3 DuetControlServer[13516]: Date/time: 2021-03-26 19:28:05
Mar 26 19:28:05 ender3 DuetControlServer[13516]: Cache data hit count 4294967295
Mar 26 19:28:05 ender3 DuetControlServer[13516]: Slowest loop: 202.38ms; fastest: 0.08ms
Mar 26 19:28:05 ender3 DuetControlServer[13516]: === Storage ===
Mar 26 19:28:05 ender3 DuetControlServer[13516]: Free file entries: 10
Mar 26 19:28:05 ender3 DuetControlServer[13516]: SD card 0 not detected, interface speed: 0.0MBytes/sec
Mar 26 19:28:05 ender3 DuetControlServer[13516]: SD card longest read time 0.0ms, write time 0.0ms, max retries 0
Mar 26 19:28:05 ender3 DuetControlServer[13516]: === Move ===
Mar 26 19:28:05 ender3 DuetControlServer[13516]: DMs created 83, maxWait 122533ms, bed compensation in use: mesh, comp offset 0.000
Mar 26 19:28:05 ender3 DuetControlServer[13516]: === MainDDARing ===
Mar 26 19:28:05 ender3 DuetControlServer[13516]: Scheduled moves 99196, completed moves 99196, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
Mar 26 19:28:05 ender3 DuetControlServer[13516]: === AuxDDARing ===
Mar 26 19:28:05 ender3 DuetControlServer[13516]: Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
Mar 26 19:28:05 ender3 DuetControlServer[13516]: === Heat ===
Mar 26 19:28:05 ender3 DuetControlServer[13516]: Bed heaters = 0 -1, chamberHeaters = -1 -1
Mar 26 19:28:05 ender3 DuetControlServer[13516]: Heater 0 is on, I-accum = 0.0
Mar 26 19:28:05 ender3 DuetControlServer[13516]: Heater 2 is on, I-accum = 0.6
Mar 26 19:28:05 ender3 DuetControlServer[13516]: === GCodes ===
Mar 26 19:28:05 ender3 DuetControlServer[13516]: Segments left: 0
Mar 26 19:28:05 ender3 DuetControlServer[13516]: Movement lock held by Autopause
Mar 26 19:28:05 ender3 DuetControlServer[13516]: HTTP* is idle in state(s) 0
Mar 26 19:28:05 ender3 DuetControlServer[13516]: Telnet is idle in state(s) 0
Mar 26 19:28:05 ender3 DuetControlServer[13516]: File* is doing "G1 X-58.264000 Y-6.812000 E0.479440" in state(s) 0
Mar 26 19:28:05 ender3 DuetControlServer[13516]: USB is idle in state(s) 0
Mar 26 19:28:05 ender3 DuetControlServer[13516]: Aux is idle in state(s) 0
Mar 26 19:28:05 ender3 DuetControlServer[13516]: Trigger* is idle in state(s) 0
Mar 26 19:28:05 ender3 DuetControlServer[13516]: Queue* is idle in state(s) 0
Mar 26 19:28:05 ender3 DuetControlServer[13516]: LCD is idle in state(s) 0
Mar 26 19:28:05 ender3 DuetControlServer[13516]: SBC is idle in state(s) 0
Mar 26 19:28:05 ender3 DuetControlServer[13516]: Daemon is idle in state(s) 0
Mar 26 19:28:05 ender3 DuetControlServer[13516]: Aux2 is idle in state(s) 0
Mar 26 19:28:05 ender3 DuetControlServer[13516]: Autopause is ready with "M122 M115 M913 X0 Y0 G10 P0 R0 S0 G10 P1 R0 S0 G91 M83 G1 Z3 E-5 F10000" in state(s) 71
Mar 26 19:28:05 ender3 DuetControlServer[13516]: Code queue is empty.
Mar 26 19:28:05 ender3 DuetControlServer[13516]: === Filament sensors ===
Mar 26 19:28:05 ender3 DuetControlServer[13516]: Extruder 0 sensor: ok
Mar 26 19:28:05 ender3 DuetControlServer[13516]: Extruder 1 sensor: ok
Mar 26 19:28:05 ender3 DuetControlServer[13516]: === CAN ===
Mar 26 19:28:05 ender3 DuetControlServer[13516]: Messages queued 60589, send timeouts 60586, received 0, lost 0, longest wait 0ms for reply type 0, peak Tx sync delay 0, free buffers 17 (min 17)
Mar 26 19:28:05 ender3 DuetControlServer[13516]: Last cancelled message type 30 dest 127
Mar 26 19:28:05 ender3 DuetControlServer[13516]: === SBC interface ===
Mar 26 19:28:05 ender3 DuetControlServer[13516]: State: 0, failed transfers: 0
Mar 26 19:28:05 ender3 DuetControlServer[13516]: Last transfer: 11ms ago
Mar 26 19:28:05 ender3 DuetControlServer[13516]: RX/TX seq numbers: 6654/6655
Mar 26 19:28:05 ender3 DuetControlServer[13516]: SPI underruns 0, overruns 0
Mar 26 19:28:05 ender3 DuetControlServer[13516]: Number of disconnects: 0, IAP RAM available 0x11458
Mar 26 19:28:05 ender3 DuetControlServer[13516]: Buffer RX/TX: 1192/2488-0
Mar 26 19:28:05 ender3 DuetControlServer[13516]: G0/G1: insufficient axes homed
Mar 26 19:28:06 ender3 DuetControlServer[13516]: [debug] Requesting update of key move, seq 86 -> 87
Mar 26 19:28:06 ender3 DuetControlServer[13516]: [warn] VIN under-voltage event (0.0V)

dc42

@Serbitar, thanks for that report. I'm sorry that this is not resolved yet. The M122 report shows no ADC timeouts, which tells me where not to look for the problem.

Solved Duet 3 Mini 5+ VIN under-voltage issues in SBC mode