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

Serbitar

I have a small cartesian printer that is controlled with a Duet 3 Mini 5+ and Mini 2+ expansion.

I have been trying to chase down a problem with the controller pausing prints due to "Warning: VIN under-voltage event (0.0V)" when I certainly have not suffered a power cut.

When I have tested resume on power loss functionality by removing the mains input, the printer correctly completes the pause instructions in the config, with the erroneous events it does not.

This could suggest a power supply problem so I have replaced the power supply with a brand new Meanwell RSP-500-24. Estimated peak load plus headroom is around 400W.

My SBC is powered by an external usb-c power supply and the RSP-500-24 is wired directly to the controller, there is no remote power control in use.

Controller is runing from its internal 5v power supply and the 5V_SBC / 5V_COM / 5V_EXT_IN jumper is absent.

What can I do to further diagnose this issue? Is there possibly a fault with my controller?

Most recent M122 taken immediately after the power event and config.g is included here.

m122
=== Diagnostics ===
RepRapFirmware for Duet 3 Mini 5+ version 3.2.2 running on Duet 3 Mini5plus WiFi (SBC mode)
Board ID: W4ZW4-V296U-D65J0-40KM0-LR03Z-H6928
Used output buffers: 1 of 40 (12 max)
=== RTOS ===
Static ram: 98732
Dynamic ram: 100644 of which 60 recycled
Never used RAM 45780, free system stack 118 words
Tasks: Linux(blocked,99) HEAT(blocked,315) CanReceiv(blocked,947) CanSender(blocked,358) CanClock(blocked,362) TMC(blocked,106) MAIN(running,432) IDLE(ready,20) AIN(blocked,260)
Owned mutexes: HTTP(MAIN)
=== Platform ===
Last reset 01:19:41 ago, cause: software
Last software reset at 2021-03-09 15:16, reason: User, none spinning, available RAM 46064, 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 0.0, current 24.3, max 24.4, under voltage events: 1, over voltage events: 0, power good: yes
Driver 0: position -562, standstill, SG min/max 0/0, read errors 0, write errors 1, ifcnt 47, reads 38554, writes 21, timeouts 5, DMA errors 0, failedOp 0x72
Driver 1: position -1478, standstill, SG min/max 0/254, read errors 0, write errors 1, ifcnt 59, reads 38551, writes 29, timeouts 0, DMA errors 0
Driver 2: position 1707, standstill, SG min/max 0/0, read errors 0, write errors 1, ifcnt 53, reads 38550, writes 23, timeouts 7, DMA errors 0, failedOp 0x6a
Driver 3: position 0, standstill, SG min/max 0/356, read errors 0, write errors 1, ifcnt 78, reads 38539, writes 40, timeouts 0, DMA errors 0
Driver 4: position 0, standstill, SG min/max 0/348, read errors 0, write errors 1, ifcnt 78, reads 38480, writes 40, timeouts 60, DMA errors 0, failedOp 0x6a
Driver 5: position 0, standstill, SG min/max 0/98, read errors 0, write errors 1, ifcnt 88, reads 38538, writes 42, timeouts 0, DMA errors 0
Driver 6: position 0, standstill, SG min/max 0/110, read errors 0, write errors 1, ifcnt 88, reads 37274, writes 42, timeouts 1264, DMA errors 0, failedOp 0x01
Date/time: 2021-03-09 16:36:35
Cache data hit count 4294967295
Slowest loop: 203.85ms; fastest: 0.08ms
=== 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 408845ms, bed compensation in use: mesh, comp offset 0.045
=== MainDDARing ===
Scheduled moves 15097, completed moves 15097, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 2], 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.4
=== 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 F1500.000000" 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 43244, send timeouts 43241, received 0, lost 0, longest wait 0ms for reply type 0, free buffers 16
=== SBC interface ===
State: 4, failed transfers: 0
Last transfer: 4ms ago
RX/TX seq numbers: 47922/47922
SPI underruns 0, overruns 0
Number of disconnects: 0, IAP RAM available 0x10eec
Buffer RX/TX: 2584/4080-0
=== Duet Control Server ===
Duet Control Server v3.2.2
File:
Buffered code: G1 F1500.000
Buffered code: G1 X-11.892 Y17.217 E0.01293
Buffered code: G1 X-14.152 Y15.492 E0.04298
Buffered code: G1 X-13.578 Y14.849 E0.01303
Buffered code: G1 X-12.562 Y15.740 E0.02043
Buffered code: G1 X-11.473 Y16.468 E0.01978
Buffered code: G1 X-11.287 Y17.084 F9000.000
Buffered code: G1 F2400.000
Buffered code: G1 X-11.784 Y17.844 E0.01373
Buffered code: G1 X-14.787 Y15.552 E0.05709
Buffered code: G1 X-14.176 Y14.869 E0.01386
Buffered code: G1 X-14.789 Y14.330 E0.01234
Buffered code: G1 X-16.524 Y12.352 E0.03978
Buffered code: G1 X-17.986 Y10.164 E0.03978
Buffered code: G1 X-19.150 Y7.804 E0.03978
Buffered code: G1 X-19.996 Y5.312 E0.03978
Buffered code: G1 X-20.510 Y2.731 E0.03978
Buffered code: G1 X-20.682 Y0.105 E0.03978
Buffered code: G1 X-20.510 Y-2.520 E0.03978
Buffered code: G1 X-19.996 Y-5.101 E0.03978
Buffered code: G1 X-19.150 Y-7.593 E0.03978
Buffered code: G1 X-17.986 Y-9.953 E0.03978
Buffered code: G1 X-16.524 Y-12.141 E0.03978
Buffered code: G1 X-14.789 Y-14.120 E0.03978
Buffered code: G1 X-12.811 Y-15.855 E0.03978
Buffered code: G1 X-10.623 Y-17.317 E0.03978
Buffered code: G1 X-9.907 Y-17.670 E0.01208
Buffered code: G1 X-10.316 Y-18.480 E0.01373
Buffered code: G1 X-6.831 Y-19.935 E0.05709
Buffered code: G1 X-6.544 Y-19.064 E0.01386
Buffered code: G1 X-5.771 Y-19.326 E0.01234
Buffered code: G1 X-3.190 Y-19.840 E0.03978
==> 1464 bytes
Code buffer space: 2512
Configured SPI speed: 8000000 Hz
Full transfers per second: 37.44
Maximum length of RX/TX data transfers: 3396/968
File /opt/dsf/sd/gcodes/eggrocket2_0.08mm_PETG_ENDER3_2h1m.gcode is selected, processing

; Configuration file for Duet 3 Mini 5+ (firmware version 3)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v3.2.2 on Thu Feb 11 2021 19:15:43 GMT+0000 (Greenwich Mean Time)

; General preferences
G90                                                ; send absolute coordinates...
M83                                                ; ...but relative extruder moves
M550 P"Small DE Printer"                           ; set printer name
M918 P1 E4 F2000000                                ; configure direct-connect display
M929 P"log.txt" S1                                 ; Enable logging
;M552 S1                                           ; Enable network

; Drives
M569 P0.0 S1 D3 V0 F4                              ; physical drive 0.0 goes backwards, stealthchop enabled
M569 P0.1 S1 D3 V0 F4                              ; physical drive 0.1 goes forwards, stealthchop enabled
M569 P0.2 S0 D3 V0 F4                              ; physical drive 0.2 goes forwards, stealthchop enabled
M569 P0.3 S1 D3 V0 F4                              ; physical drive 0.3 goes backwards, stealthchop enabled 
M569 P0.4 S0 D3 V0 F4                              ; physical drive 0.4 goes forwards, stealthchop enabled 
M569 P0.5 S1 D3 V0 F4                              ; physical drive 0.5 goes backwards, stealthchop enabled 
M569 P0.6 S0 D3 V0 F4                              ; physical drive 0.6 goes forwards, stealthchop enabled 
M584 X0.3 Y0.4 Z0.5:0.6 E0.1:0.2                   ; set drive mapping
M350 X16 Y16 Z16 E16:16 I1                         ; configure microstepping with interpolation
M92 X80.00 Y80.00 Z400.00 E419.6:419.6             ; set steps per mm
M566 X900.00 Y900.00 Z60.00 E120.00:120.00         ; set maximum instantaneous speed changes (mm/min)
M203 X6000.00 Y6000.00 Z180.00 E1200.00:1200.00    ; set maximum speeds (mm/min)
M201 X500.00 Y500.00 Z20.00 E250.00:250.00         ; set accelerations (mm/s^2)
M906 X1100 Y1100 Z1100 E800:800 I30                ; set motor currents (mA) and motor idle factor in per cent
M84 S30                                            ; Set idle timeout
M915 X Y S1 F1 R3 H150                             ; Stall detection XY pause on stall
M915 Z   S3 F1 R2 H200                             ; Stall detection Z pause on stall
M915 P0.1:0.2 S30 F1 R0                                                    ; Stall detection E0,E1 do nothing


; Axis Limits
M208 X-116 Y-125 Z0 S1                             ; set axis minima
M208 X129 Y116 Z230 S0                             ; set axis maxima

; Endstops
M574 X1 S1 P"io5.in"                               ; configure active-high endstop for low end on X via pin io6.in
M574 Y1 S1 P"io6.in"                               ; configure active-high endstop for low end on Y via pin io5.in
M574 Z1 S2                                         ; configure Z-probe endstop for low end on Z

; Filament runout sensors
M591 D0 P1 C"^io3.in" S0                           ; Left extruder runout
M591 D1 P1 C"^io2.in" S0                           ; Right extruder runout

; Z-Probe
M950 S0 C"io1.out"                                 ; create servo pin 0 for BLTouch
M558 P9 C"^io1.in" B1 H5 F120 T6000                ; set Z probe type to bltouch and the dive height + speeds disable heaters when probing
G31 P500 X-24 Y-1 Z1.414                           ; set Z probe trigger value, offset and trigger height
M557 X-116:113 Y-116:116 S20                       ; define mesh grid

; Heaters
M308 S0 P"temp0" Y"thermistor" T100000 B4138       ; configure sensor 0 as thermistor on pin temp0
M950 H0 C"out0" T0                                 ; create bed heater output on out0 and map it to sensor 0
M140 H0                                            ; map heated bed to heater 0
M143 H0 S120                                       ; set temperature limit for heater 0 to 120C
M308 S1 P"temp1" Y"thermistor" T100000 B4138       ; configure sensor 1 as thermistor on pin temp1
M950 H1 C"out1" T1                                 ; create nozzle heater output on out1 and map it to sensor 1
M307 H1 B0 S1.00                                   ; disable bang-bang mode for heater  and set PWM limit
M143 H1 S280                                       ; set temperature limit for heater 1 to 280C
M308 S2 P"temp2" Y"thermistor" T100000 B4138       ; configure sensor 2 as thermistor on pin temp2
M950 H2 C"out2" T2                                 ; create nozzle heater output on out2 and map it to sensor 2
M307 H2 B0 S1.00                                   ; disable bang-bang mode for heater  and set PWM limit
M143 H2 S280                                       ; set temperature limit for heater 2 to 280C

; Fans
M950 F0 C"out6" Q1000                              ; create fan 0 on pin out6 and set its frequency
M106 P0 C"Part Cooling" S0 H-1                     ; set fan 0 name and value. Thermostatic control is turned off
M950 F1 C"out5" Q1000                              ; create fan 1 on pin out5 and set its frequency
M106 P1 C"Hotend Fan" S1 H2:1 T45                  ; set fan 1 name and value. Thermostatic control is turned on

; Tools
M563 P0 S"Left Nozzle"  D0 H1 F0                   ; define tool 0
G10 P0 X0 Y0 Z0                                    ; set tool 0 axis offsets
G10 P0 R0 S0                                       ; set initial tool 0 active and standby temperatures to 0C
M563 P1 S"Right Nozzle" D1 H2 F0                   ; define tool 1
G10 P1 X20 Y0 Z0                                   ; set tool 1 axis offsets
G10 P1 R0 S0                                       ; set initial tool 1 active and standby temperatures to 0C

; Custom settings are not defined
M307 H0 R0.281 C428.8 D4.28 S1.00 V23.9
 
; Miscellaneous
M911 S21 R23 P"M913 X0 Y0; G10 P0 R0 S0 G10 P1 R0 S0 G91 M83 G1 Z3 E-5 F10000" ; set voltage thresholds and actions to run on power loss
M572 D0:1 S0.1:0.1                                 ; Guestimate pressure advance setting

M207 S6 F2400 ; Retraction 6mm @40mm/s

M671 X-145:145 Y0:0 Z2 ; leadscrew co-ordinates

;Turn off power supply (makes power switch show in webui)
M81

Phaedrux

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

"Warning: VIN under-voltage event (0.0V)"

Where are you seeing that errors?

What does your VIN connector look like?

Serbitar

The error is in the DWC console tab and in the logfile written to the card.

2021-03-09 16:32:07 Print auto-paused due to low voltage
2021-03-09 16:32:07 Warning: VIN under-voltage event (0.0V)

Cable to the power supply is 14AWG silicone cable with fork terminals on each end. Firmly bolted to the barrier strips on both the PSU and the controller.
I replaced the cables when I installed the new power supply because the previous ones were not long enough.

Phaedrux

Thanks. Looking into it.

Serbitar

I should have said, that when i run this in standalone mode I don't see the under-voltage warnings.

dc42

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

I should have said, that when i run this in standalone mode I don't see the under-voltage warnings.

Thanks for that information, it's very useful. I have one other report of spurious under-voltage readings from a Duet 3 Mini, also in SBC mode.

Can you provide a photo showing the Duet, the Pi and the wiring?

Serbitar

Its all a bit of a mess due to the investigations... Power supply and controller are on opposite sides of the printer currently. Approx 50cm cable length in the main power cables.

Terminals on the psu from centre outwards are:
Controller, 10000uF capacitor, LED lighting.

Capacitor was added as part of the investigations when i thought I was possibly suffering from mains failures. Ideally i would put it at the controller end of the cable run. LED lighting was not connected until late this afternoon (after the log messages i shared earlier).

Let me know if these aren't quite what you are looking for, I can probably shuffle things around tomorrow to give more context if necessary.

Thanks for your help!

Serbitar

I have been printing smaller parts for the last few days (<4h) and no power issues until running a longer job over night (24h).

Woke up to find the job was paused during a nozzle swap.

Mar 16 06:30:13 ender3 DuetControlServer[820]: [info] Print auto-paused due to low voltage
Mar 16 06:30:13 ender3 DuetControlServer[820]: [warn] VIN under-voltage event (0.0V)

SBC however didn't loose power

root@smalldeprinter ~ # uptime
 08:53:25 up 1 day, 11 min,  1 user,  load average: 0.10, 0.08, 0.08

Nor did anything else in the house.

Better photo including all the power wiring:

The smaller power supply at the top of the photo is currently completely disconnected.

Serbitar

Another occurrence over night.
Is there anything I can do to contribute to investigation? If not I'm going to go back to standalone mode.

m122
=== Diagnostics ===
RepRapFirmware for Duet 3 Mini 5+ version 3.2.2 running on Duet 3 Mini5plus WiFi (SBC mode)
Board ID: W4ZW4-V296U-D65J0-40KM0-LR03Z-H6928
Used output buffers: 1 of 40 (30 max)
=== RTOS ===
Static ram: 98732
Dynamic ram: 100676 of which 60 recycled
Never used RAM 45748, free system stack 126 words
Tasks: Linux(ready,83) HEAT(blocked,297) CanReceiv(blocked,947) CanSender(blocked,358) CanClock(blocked,362) TMC(blocked,106) MAIN(running,380) IDLE(ready,20) AIN(blocked,262)
Owned mutexes: HTTP(MAIN)
=== Platform ===
Last reset 09:35:39 ago, cause: software
Last software reset at 2021-03-16 23:02, reason: User, none spinning, available RAM 46164, 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 0.0, current 24.1, max 25.3, under voltage events: 505, over voltage events: 0, power good: yes
Driver 0: position -1155, standstill, SG min/max 0/0, read errors 0, write errors 23, ifcnt 243, reads 41867, writes 4545, timeouts 7, DMA errors 0, failedOp 0x01
Driver 1: position -2187, standstill, SG min/max 0/44, read errors 0, write errors 23, ifcnt 79, reads 41848, writes 4545, timeouts 2, DMA errors 0, failedOp 0x71
Driver 2: position 9535, standstill, SG min/max 0/66, read errors 1, write errors 23, ifcnt 79, reads 41831, writes 4545, timeouts 3, DMA errors 0, failedOp 0x6a
Driver 3: position 0, standstill, SG min/max 0/46, read errors 0, write errors 20, ifcnt 242, reads 41574, writes 4546, timeouts 5, DMA errors 0, failedOp 0x72
Driver 4: position 0, standstill, SG min/max 0/298, read errors 2, write errors 22, ifcnt 57, reads 41858, writes 4546, timeouts 5, DMA errors 0, failedOp 0x71
Driver 5: position 0, standstill, SG min/max 0/2, read errors 1, write errors 16, ifcnt 242, reads 41847, writes 4545, timeouts 3, DMA errors 0, failedOp 0x80
Driver 6: position 0, standstill, SG min/max 0/2, read errors 0, write errors 16, ifcnt 242, reads 41630, writes 4545, timeouts 30, DMA errors 0, failedOp 0x6f
Date/time: 2021-03-17 08:38:39
Cache data hit count 4294967295
Slowest loop: 4.77ms; 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 108660, completed moves 108660, 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, chamberHeaters = -1 -1
Heater 0 is on, I-accum = 0.0
Heater 2 is on, I-accum = 0.4
=== 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 X29.985001 Y-4.522000 E0.322590" 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 194722, send timeouts 194722, received 0, lost 0, longest wait 0ms for reply type 0, free buffers 16
=== SBC interface ===
State: 4, failed transfers: 0
Last transfer: 5ms ago
RX/TX seq numbers: 23696/23696
SPI underruns 0, overruns 0
Number of disconnects: 0, IAP RAM available 0x10eec
Buffer RX/TX: 1464/2272-0
=== Duet Control Server ===
Duet Control Server v3.2.2
File:
Buffered code: G1 X29.985 Y-4.522 E0.32259
Buffered code: G1 X29.967 Y-5.211 F9000.000
Buffered code: G1 F1800.000
Buffered code: G1 X29.940 Y-5.511 E0.00858
Buffered code: G1 X29.914 Y-5.812 E0.00763
Buffered code: G1 X29.892 Y-6.011 E0.00444
Buffered code: G1 X29.871 Y-6.211 E0.00373
Buffered code: G1 X29.849 Y-6.410 E0.00302
Buffered code: G1 X29.827 Y-6.609 E0.00232
Buffered code: G1 X29.805 Y-6.809 E0.00161
Buffered code: G10 ; retract
Buffered code: G1 X29.967 Y5.211 F9000.000
Buffered code: G11 ; unretract
Buffered code: G1 F1800.000
Buffered code: G1 X29.940 Y5.511 E0.00858
Buffered code: G1 X29.914 Y5.812 E0.00763
Buffered code: G1 X29.892 Y6.011 E0.00444
Buffered code: G1 X29.871 Y6.211 E0.00373
Buffered code: G1 X29.849 Y6.410 E0.00302
==> 800 bytes
Code buffer space: 1824
Configured SPI speed: 8000000 Hz
Full transfers per second: 36.74
Maximum length of RX/TX data transfers: 3777/1612
File /opt/dsf/sd/gcodes/stripyegg1_0.2mm_PLA_ENDER3_9h33m.gcode is selected, processing

Log looks a bit different this time! I added m122 to the power fail actions.

M911 S21 R23 P"M122 M913 X0 Y0; G10 P0 R0 S0 G10 P1 R0 S0 G91 M83 G1 Z3 E-5 F10000" ; set voltage thresholds and actions to run on power loss

2021-03-16 23:03:28 Error: G0/G1: insufficient axes homed
2021-03-17 02:38:04 === Diagnostics ===
RepRapFirmware for Duet 3 Mini 5+ version 3.2.2 running on Duet 3 Mini5plus WiFi (SBC mode)
Board ID: W4ZW4-V296U-D65J0-40KM0-LR03Z-H6928
Used output buffers: 2 of 40 (13 max)
=== RTOS ===
Static ram: 98732
Dynamic ram: 100676 of which 60 recycled
Never used RAM 45748, free system stack 126 words
Tasks: Linux(ready,99) HEAT(blocked,297) CanReceiv(blocked,947) CanSender(blocked,358) CanClock(blocked,362) TMC(blocked,106) MAIN(running,388) IDLE(ready,20) AIN(blocked,262)
Owned mutexes: Autopause(MAIN)
=== Platform ===
Last reset 03:35:03 ago, cause: software
Last software reset at 2021-03-16 23:02, reason: User, none spinning, available RAM 46164, 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 0.0, current 20.9, max 24.4, under voltage events: 0, over voltage events: 0, power good: yes
Driver 0: position -1155, standstill, SG min/max 0/0, read errors 0, write errors 1, ifcnt 139, reads 11001, writes 12, timeouts 8, DMA errors 0, failedOp 0x72
Driver 1: position -2187, standstill, SG min/max 0/242, read errors 0, write errors 1, ifcnt 201, reads 10987, writes 18, timeouts 16, DMA errors 0, failedOp 0x01
Driver 2: position 9535, standstill, SG min/max 0/250, read errors 0, write errors 1, ifcnt 187, reads 10991, writes 20, timeouts 10, DMA errors 0, failedOp 0x06
Driver 3: position 0, ok, SG min/max 0/356, read errors 0, write errors 1, ifcnt 229, reads 10914, writes 21, timeouts 86, DMA errors 0, failedOp 0x71
Driver 4: position 0, ok, SG min/max 0/346, read errors 0, write errors 1, ifcnt 235, reads 10862, writes 21, timeouts 138, DMA errors 0, failedOp 0x6a
Driver 5: position 0, ok, SG min/max 0/100, read errors 0, write errors 1, ifcnt 246, reads 10990, writes 23, timeouts 8, DMA errors 0, failedOp 0x01
Driver 6: position 0, ok, SG min/max 0/110, read errors 0, write errors 1, ifcnt 246, reads 8032, writes 23, timeouts 2966, DMA errors 0, failedOp 0x01
Date/time: 2021-03-17 02:38:03
Cache data hit count 4294967295
Slowest loop: 163.49ms; fastest: 0.08ms
=== 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 50255ms, bed compensation in use: mesh, comp offset 0.000
=== MainDDARing ===
Scheduled moves 108660, completed moves 108660, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 2], 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 2 is on, I-accum = 0.6
=== GCodes ===
Segments left: 0
Movement lock held by Autopause
HTTP* is idle in state(s) 0
Telnet is idle in state(s) 0
File* is doing "G1 X29.985001 Y-4.522000 E0.322590" 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 ready with "M122 M913 X0 Y0" in state(s) 64
Code queue is empty.
=== Filament sensors ===
Extruder 0 sensor: ok
Extruder 1 sensor: ok
=== CAN ===
Messages queued 116136, send timeouts 116133, received 0, lost 0, longest wait 0ms for reply type 0, free buffers 16
=== SBC interface ===
State: 0, failed transfers: 0
Last transfer: 17ms ago
RX/TX seq numbers: 50168/50169
SPI underruns 0, overruns 0
Number of disconnects: 0, IAP RAM available 0x10eec
Buffer RX/TX: 1464/2104-0
Print auto-paused due to low voltage
2021-03-17 02:38:07 Warning: VIN under-voltage event (9.3V)
2021-03-17 02:38:11 Warning: VIN under-voltage event (7.1V)
2021-03-17 02:38:16 Warning: VIN under-voltage event (7.9V)
2021-03-17 02:38:20 Warning: VIN under-voltage event (3.8V)
2021-03-17 02:38:24 Warning: VIN under-voltage event (5.1V)
2021-03-17 02:38:29 Warning: VIN under-voltage event (5.1V)
2021-03-17 02:38:33 Warning: VIN under-voltage event (5.1V)
2021-03-17 02:38:38 Warning: VIN under-voltage event (5.1V)
2021-03-17 02:38:42 Warning: VIN under-voltage event (5.2V)
2021-03-17 02:38:46 Warning: VIN under-voltage event (5.2V)
2021-03-17 02:38:51 Warning: VIN under-voltage event (5.2V)
2021-03-17 02:38:55 Warning: VIN under-voltage event (5.2V)
2021-03-17 02:39:00 Warning: VIN under-voltage event (5.2V)
2021-03-17 02:39:04 Warning: VIN under-voltage event (5.2V)
2021-03-17 02:39:09 Warning: VIN under-voltage event (5.3V)
2021-03-17 02:39:13 Warning: VIN under-voltage event (5.3V)
2021-03-17 02:39:18 Warning: VIN under-voltage event (5.3V)
2021-03-17 02:39:22 Warning: VIN under-voltage event (5.3V)
2021-03-17 02:39:27 Warning: VIN under-voltage event (5.3V)
2021-03-17 02:39:31 Warning: VIN under-voltage event (5.3V)
2021-03-17 02:39:36 Warning: VIN under-voltage event (5.3V)
2021-03-17 02:39:40 Warning: VIN under-voltage event (5.3V)
2021-03-17 02:39:45 Warning: VIN under-voltage event (5.3V)
2021-03-17 02:39:49 Warning: VIN under-voltage event (5.3V)
2021-03-17 02:39:54 Warning: VIN under-voltage event (5.3V)
2021-03-17 02:39:58 Warning: VIN under-voltage event (5.3V)
2021-03-17 02:40:03 Warning: VIN under-voltage event (5.3V)
2021-03-17 02:40:07 Warning: VIN under-voltage event (5.3V)
2021-03-17 02:40:12 Warning: VIN under-voltage event (5.4V)
2021-03-17 02:40:16 Warning: VIN under-voltage event (5.4V)
2021-03-17 03:01:26 Warning: VIN under-voltage event (0.0V)
2021-03-17 06:28:49 Warning: VIN under-voltage event (0.0V)

Phaedrux

@Serbitar Thanks for the report.

In SBC mode you could try enabling more detailed logging.

https://duet3d.dozuki.com/Wiki/Getting_Started_With_Duet_3#Section_Monitoring_optional

carcamerarig

I also had one this evening why performing home all
3.3b2 sbc mini 5

dc42

@carcamerarig, thanks for the additional data point.

My best guess at this point is that the DMA for the SPI transfers between the Pi and the Duet is somehow interfering with the DMA used by the ADC. Do any of you experiencing this problem see short-lived temperature jumps too?

Serbitar

@dc42 by the time i'm back at the printer, usually several hours have past since it stopped so the temperature charts have gone past.

I have a few prints to complete in standalone mode and then i will enable the extra monitoring. Is there any way to save logs of the temp values too?

dc42

Until I have pinned down the exact cause, it might be worth trying a lower SPI frequency. The frequency is set in the DCS configuration file on the Pi.

dc42

PS - if anyone who has experienced this has their machine idle, please can you run some simulated prints, to see whether they can trigger this issue. The increased SPI traffic rate from the Pi during a simulation might make it happen more often. OTOH it could turn out that step interrupts also need to happen for this issue to occur.

WILD9

@dc42 Happy to try, how would this manifest during a simulation, just console messages showing low voltage detected? In which case I will make sure I have 24Vin active during simulation.

dc42

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

@dc42 Happy to try, how would this manifest during a simulation, just console messages showing low voltage detected? In which case I will make sure I have 24Vin active during simulation.

I expect the indications of the problem to be:

A console report of an under-voltage event, with the reported VIN being 0.0
If you run M122 afterwards then it will report that one or more under-voltage events occurred and the minimum recorded VIN will be 0.0. Note, a subsequent M122 will only report under-voltage events and the minimum VIN that happened since the previous M122.

You will need to have VIN power applied throughout.

carcamerarig

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

PS - if anyone who has experienced this has their machine idle, please can you run some simulated prints, to see whether they can trigger this issue. The increased SPI traffic rate from the Pi during a simulation might make it happen more often. OTOH it could turn out that step interrupts also need to happen for this issue to occur.

I’ve been spending quite a few hours daily of stop start printing while I’m still tuning and configuring (mostly learning) and have only seen the one which was at a home all, the effect was a crash into the left x carriage carrier, I’m unsure if the error was before during or after the crash.
I’ll be doing more of the same later if you want me to test or log anything, I’ll need some instructions though if I’m to alter some code.

Serbitar

@dc42 Is 4MHz low enough?

lodger

Is it worth running some heaters duing a simulation. To give the PSU some load.
During a print my VIN can jump up and down a few points of a volt. But during a sim . She is bang on 24.2v and dont move.