Duet3 Mini Stalling mid print
-
Hi,
Using a duet 3 Mini with a pi4 SBC. Every few print jobs it will stop suddenly as if the emergency stop button has been pressed it will then show an insufficient axis homed message and a voltage low warning and appear as paused but there is no resurrect.g file created(at this point heaters are still held at temperature)
Any attempt to home axis results in a very odd buzzing noise coming from the steppers for a few seconds and then an extremely slow move to the end stop. The only way to continue at this point as an actual emergency stop at which point everything continues to function correctly although I cant resume the print job since there is no resurrect file.
There is also a voltage out of range warning when it stops but my PSU is switched by the duet so I'm guessing this a repercussion of the issue rather than the cause
Any thoughts?
Board: Duet 3 Mini 5+ (Mini5plus)
DSF Version: 3.2.2
Firmware: RepRapFirmware for Duet 3 Mini 5+ 3.2.2 (2021-02-11) -
grab an M122 report when it does it again.
but if its a low voltage report it could be an issue with the PSU -
@jay_s_uk Thanks, I have an M122 from after the manual emergency stop but I'm guessing I really need one from before the restart? The one I have is below:
M122
=== Diagnostics ===
RepRapFirmware for Duet 3 Mini 5+ version 3.2.2 running on Duet 3 Mini5plus WiFi (SBC mode)
Board ID: K1UT9-Z196U-D65J0-40KML-NY03Z-7ZF9S
Used output buffers: 1 of 40 (14 max)
=== RTOS ===
Static ram: 98732
Dynamic ram: 102260 of which 100 recycled
Never used RAM 44124, free system stack 128 words
Tasks: Linux(blocked,99) HEAT(blocked,315) CanReceiv(blocked,947) CanSender(blocked,358) CanClock(blocked,363) TMC(blocked,106) MAIN(running,519) IDLE(ready,20) AIN(blocked,264)
Owned mutexes: HTTP(MAIN)
=== Platform ===
Last reset 00:04:19 ago, cause: software
Last software reset at 2021-03-04 18:11, reason: User, none spinning, available RAM 44160, slot 1
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 23.9, max 23.9, under voltage events: 1, over voltage events: 0, power good: yes
Driver 0: position 240, standstill, SG min/max 0/8, read errors 0, write errors 2, ifcnt 13, reads 34757, writes 21, timeouts 0, DMA errors 0
Driver 1: position 24000, standstill, SG min/max 0/22, read errors 0, write errors 2, ifcnt 13, reads 34755, writes 21, timeouts 2, DMA errors 0, failedOp 0x6f
Driver 2: position 2400, standstill, SG min/max 0/14, read errors 0, write errors 2, ifcnt 13, reads 34752, writes 21, timeouts 3, DMA errors 0, failedOp 0x6f
Driver 3: position 0, standstill, SG min/max 0/0, read errors 0, write errors 2, ifcnt 10, reads 34736, writes 18, timeouts 22, DMA errors 0, failedOp 0x01
Driver 4: position 0, standstill, SG min/max 0/0, read errors 0, write errors 2, ifcnt 10, reads 34760, writes 18, timeouts 0, DMA errors 0
Driver 5: position 0, assumed not present
Driver 6: position 0, assumed not present
Date/time: 2021-03-04 18:15:55
Cache data hit count 605340839
Slowest loop: 157.29ms; 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 25503ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 7, completed moves 7, 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 1 is on, I-accum = 0.0
=== 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.
=== Filament sensors ===
Extruder 0 sensor: no data received
=== CAN ===
Messages queued 2283, send timeouts 2280, 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: 9359/9359
SPI underruns 0, overruns 0
Number of disconnects: 0, IAP RAM available 0x10eec
Buffer RX/TX: 0/0-0
=== Duet Control Server ===
Duet Control Server v3.2.2
Code buffer space: 4096
Configured SPI speed: 8000000 Hz
Full transfers per second: 36.34
Maximum length of RX/TX data transfers: 3208/796 -
yea, needs to be at the point where you've found its stopped before you do a reset
-
@WILD9 you mention that the PSU is controlled from the Duet. can you temporarily remove that. That way if the reset of the duet is resetting the PSU then that part of the issue will stop happening, the Duet will remain powered and you can get the M122 report.
-
@T3P3Tony Yes good idea, I will do that now.
-
OK,luckily this failed again sooner rather than later, printer is currently in the failed state M122 below. I got the voltage warning again despite bypassing the relay for 24v.
SBC uptime shows no reboot there and no low voltage events in the syslog so doesn't look like the 5v psu (powers the sbc and duet) has been interrupted at all.
for reference the above event occurred at ~11:10 am 06/03/21
does this look like 24V PSU failure?
M122
=== Diagnostics ===
RepRapFirmware for Duet 3 Mini 5+ version 3.2.2 running on Duet 3 Mini5plus WiFi (SBC mode)
Board ID: K1UT9-Z196U-D65J0-40KML-NY03Z-7ZF9S
Used output buffers: 1 of 40 (10 max)
=== RTOS ===
Static ram: 98732
Dynamic ram: 102152 of which 140 recycled
Never used RAM 44192, free system stack 150 words
Tasks: Linux(ready,79) HEAT(blocked,297) CanReceiv(blocked,947) CanSender(blocked,358) CanClock(blocked,362) TMC(blocked,106) MAIN(running,519) IDLE(ready,20) AIN(blocked,264)
Owned mutexes: HTTP(MAIN)
=== Platform ===
Last reset 02:40:49 ago, cause: power up
Last software reset at 2021-03-04 18:11, reason: User, none spinning, available RAM 44160, slot 1
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 23.8, max 24.0, under voltage events: 1, over voltage events: 0, power good: yes
Driver 0: position 9138, standstill, SG min/max 0/48, read errors 0, write errors 0, ifcnt 22, reads 65137, writes 22, timeouts 34, DMA errors 0, failedOp 0x06
Driver 1: position 21161, standstill, SG min/max 0/50, read errors 0, write errors 0, ifcnt 22, reads 64966, writes 22, timeouts 205, DMA errors 0, failedOp 0x01
Driver 2: position 111, standstill, SG min/max 0/18, read errors 0, write errors 0, ifcnt 22, reads 65116, writes 22, timeouts 54, DMA errors 0, failedOp 0x72
Driver 3: position 0, standstill, SG min/max 0/44, read errors 0, write errors 0, ifcnt 22, reads 64947, writes 22, timeouts 223, DMA errors 0, failedOp 0x06
Driver 4: position 0, standstill, SG min/max 0/0, read errors 0, write errors 0, ifcnt 18, reads 65175, writes 18, timeouts 0, DMA errors 0
Driver 5: position 0, assumed not present
Driver 6: position 0, assumed not present
Date/time: 2021-03-06 11:17:48
Cache data hit count 4294967295
Slowest loop: 1416.05ms; fastest: 0.07ms
=== 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 8190255ms, bed compensation in use: mesh, comp offset 0.000
=== MainDDARing ===
Scheduled moves 4712, completed moves 4712, 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.5
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 X114.337997 Y256.683014 E1.985030" 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 86709, send timeouts 86706, 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: 16041/16041
SPI underruns 0, overruns 0
Number of disconnects: 0, IAP RAM available 0x10eec
Buffer RX/TX: 832/2136-0
=== Duet Control Server ===
Duet Control Server v3.2.2
File:
Buffered code: G1 X114.338 Y256.683 E1.98503
Buffered code: G1 X114.092 Y256.974 E1.99703
Buffered code: G1 X112.048 Y254.929 E2.08820
Buffered code: G1 X112.048 Y255.466 E2.10511
Buffered code: G1 X113.892 Y257.310 E2.18737
Buffered code: G1 X113.744 Y257.698 E2.20047
Buffered code: G1 X112.048 Y256.002 E2.27611
Buffered code: G1 X112.047 Y256.538 E2.29302
Buffered code: G1 X113.663 Y258.154 E2.36507
Buffered code: G1 X113.663 Y258.521 E2.37665
Buffered code: G1 X113.698 Y258.725 E2.38318
Buffered code: G1 X112.047 Y257.074 E2.45680
Buffered code: G1 X112.047 Y257.610 E2.47371
Buffered code: G1 X116.116 Y261.679 E2.65516
Buffered code: G1 X116.384 Y261.411 E2.66712
Buffered code: G1 X115.579 Y260.606 E2.70300
Buffered code: G1 X115.683 Y260.629 E2.70636
Buffered code: G1 X116.146 Y260.637 E2.72095
Buffered code: G1 X116.652 Y261.143 E2.74353
Buffered code: G1 X116.920 Y260.875 E2.75545
Buffered code: G1 X116.465 Y260.419 E2.77577
Buffered code: G1 X117.033 Y260.550 F10800.000
Buffered code: G1 F1200.000
Buffered code: G1 X117.264 Y260.381 E2.78382
Buffered code: G1 X117.573 Y260.113 E2.79529
Buffered code: G1 X117.857 Y259.821 E2.80705
Buffered code: G1 X118.089 Y259.539 E2.81786
Buffered code: G1 X118.012 Y259.255 E2.82658
==> 1324 bytes
Code buffer space: 1960
Configured SPI speed: 8000000 Hz
Full transfers per second: 35.01
Maximum length of RX/TX data transfers: 3088/1456
File /opt/dsf/sd/gcodes/Full_Mining_Rig_Set_PETG_CR10_8h24m.gcode is selected, processing -
@WILD9 said in Duet3 Mini Stalling mid print:
Supply voltage: min 0.0, current 23.8, max 24.0, under voltage events: 1, over voltage events: 0, power good: yes
Driver 0: position 9138, standstill, SG min/max 0/48, read errors 0, write errors 0, ifcnt 22, reads 65137, writes 22, timeouts 34, DMA errors 0, failedOp 0x06
Driver 1: position 21161, standstill, SG min/max 0/50, read errors 0, write errors 0, ifcnt 22, reads 64966, writes 22, timeouts 205, DMA errors 0, failedOp 0x01
Driver 2: position 111, standstill, SG min/max 0/18, read errors 0, write errors 0, ifcnt 22, reads 65116, writes 22, timeouts 54, DMA errors 0, failedOp 0x72
Driver 3: position 0, standstill, SG min/max 0/44, read errors 0, write errors 0, ifcnt 22, reads 64947, writes 22, timeouts 223, DMA errors 0, failedOp 0x06
Driver 4: position 0, standstill, SG min/max 0/0, read errors 0, write errors 0, ifcnt 18, reads 65175, writes 18, timeouts 0, DMA errors 0The under-voltage event and the timeouts writing to the drivers suggest that VIN power was lost briefly.
Duet WiFi hardware designer and firmware engineer
Please do not ask me for Duet support via PM or email, use the forum
http://www.escher3d.com, https://miscsolutions.wordpress.com -
This post is deleted! -
@dc42 Thanks, in this case is VIN the 24V PSU as opposed to the separate 5V feeding the Duet/SBC?
-
OK, Ordered a new PSU. Fingers crossed.
-
No Luck, replacement Meanwell PSU installed and still coming back to occasionally find the printer stopped mid print.
Latest M122:
M122
=== Diagnostics ===
RepRapFirmware for Duet 3 Mini 5+ version 3.2.2 running on Duet 3 Mini5plus WiFi (SBC mode)
Board ID: K1UT9-Z196U-D65J0-40KML-NY03Z-7ZF9S
Used output buffers: 1 of 40 (10 max)
=== RTOS ===
Static ram: 98732
Dynamic ram: 102268 of which 24 recycled
Never used RAM 44192, free system stack 200 words
Tasks: Linux(blocked,120) HEAT(blocked,315) CanReceiv(blocked,947) CanSender(blocked,372) CanClock(blocked,363) TMC(blocked,106) MAIN(running,519) IDLE(ready,20) AIN(blocked,272)
Owned mutexes: HTTP(MAIN)
=== Platform ===
Last reset 00:00:43 ago, cause: software
Last software reset at 2021-03-16 08:05, reason: User, GCodes spinning, available RAM 44124, slot 2
Software reset code 0x0003 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 1.3, max 24.0, under voltage events: 1, over voltage events: 0, power good: no
Driver 0: position 0, standstill, SG min/max 0/0, read errors 0, write errors 1, ifcnt 33, reads 485, writes 9, timeouts 586, DMA errors 0, failedOp 0x6f
Driver 1: position 0, standstill, SG min/max 0/0, read errors 0, write errors 1, ifcnt 33, reads 483, writes 9, timeouts 588, DMA errors 0, failedOp 0x06
Driver 2: position 0, standstill, SG min/max 2/2, read errors 0, write errors 1, ifcnt 33, reads 482, writes 9, timeouts 588, DMA errors 0, failedOp 0x41
Driver 3: position 0, standstill, SG min/max 2/2, read errors 0, write errors 1, ifcnt 31, reads 467, writes 9, timeouts 603, DMA errors 0, failedOp 0x72
Driver 4: position 0, standstill, SG min/max 0/0, read errors 0, write errors 1, ifcnt 29, reads 484, writes 9, timeouts 587, DMA errors 0, failedOp 0x01
Driver 5: position 0, assumed not present
Driver 6: position 0, assumed not present
Date/time: 2021-03-16 08:06:07
Cache data hit count 114694806
Slowest loop: 1.38ms; fastest: 0.09ms
=== 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: 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, chamberHeaters = -1 -1
Heater 1 is on, I-accum = 0.0
=== 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.
=== Filament sensors ===
Extruder 0 sensor: no data received
=== CAN ===
Messages queued 343, send timeouts 341, 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: 1654/1654
SPI underruns 0, overruns 0
Number of disconnects: 0, IAP RAM available 0x10eec
Buffer RX/TX: 0/0-0
=== Duet Control Server ===
Duet Control Server v3.2.2
Code buffer space: 4096
Configured SPI speed: 8000000 Hz
Full transfers per second: 38.93
Maximum length of RX/TX data transfers: 3100/796 -
@WILD9 said in Duet3 Mini Stalling mid print:
Supply voltage: min 0.0, current 1.3, max 24.0, under voltage events: 1, over voltage events: 0, power good: no
That M122 report is interesting because it says the current voltage is 1.3V. If it says that, you can test the actual voltage with a multimeter as see if that’s true.
Ian
Bed-slinger - Mini5+ WiFi/1LC | RRP Fisher v1 - D2 WiFi | Polargraph - D2 WiFi | TronXY X5S - 6HC/Roto | CNC router - 6HC | Tractus3D T1250 - D2 Eth
-
is your m122 being done automatically? (i.e. when powerloss is detected?)
-
May be related to this https://forum.duet3d.com/topic/22031/duet-3-mini-5-vin-under-voltage-issues-in-sbc-mode/7. In summary, we have a few instances of what appear to be spurious under-voltage detection, always with the voltage being recorded as 0.0, and so far always when in SBC mode not standalone mode.
-
@droftarts The duet controls my 24Vin it seems to have turned the relay off here hence the 1.3v reading but during printing I'm at 24v The same failures occur with the relay bypassed and Im now on my second 24V PSU.
@Serbitar No, that last one was manually run ~5 minutes after the print stopped but before I had taken any action to restart things.
@dc42 Thanks I will keep an eye on this, is there anything I can do to help with logging etc as I seem to have this occurring quite frequently at the moment.
-
Another failure so another m122 with the console messages precursing it:
8/03/2021, 08:42:37 m122 === Diagnostics === RepRapFirmware for Duet 3 Mini 5+ version 3.2.2 running on Duet 3 Mini5plus WiFi (SBC mode) Board ID: K1UT9-Z196U-D65J0-40KML-NY03Z-7ZF9S Used output buffers: 1 of 40 (13 max) === RTOS === Static ram: 98732 Dynamic ram: 95896 of which 60 recycled Never used RAM 50528, free system stack 124 words Tasks: Linux(ready,77) HEAT(blocked,297) CanReceiv(blocked,947) CanSender(blocked,358) CanClock(blocked,362) TMC(blocked,106) MAIN(running,438) IDLE(ready,20) AIN(blocked,264) Owned mutexes: Telnet(MAIN) === Platform === Last reset 15:36:04 ago, cause: power up Last software reset at 2021-03-17 13:46, reason: User, none spinning, available RAM 44124, slot 1 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 23.9, current 24.0, max 24.0, under voltage events: 4, over voltage events: 0, power good: yes Driver 0: position -13134, ok, SG min/max 0/4, read errors 0, write errors 0, ifcnt 21, reads 18144, writes 0, timeouts 5, DMA errors 0, failedOp 0x06 Driver 1: position -6070, ok, SG min/max 0/18, read errors 0, write errors 0, ifcnt 21, reads 18148, writes 0, timeouts 1, DMA errors 0, failedOp 0x06 Driver 2: position 2057, standstill, SG min/max 0/6, read errors 0, write errors 0, ifcnt 20, reads 18148, writes 0, timeouts 1, DMA errors 0, failedOp 0x72 Driver 3: position 0, standstill, SG min/max 14/14, read errors 0, write errors 0, ifcnt 21, reads 18147, writes 0, timeouts 3, DMA errors 0, failedOp 0x6f Driver 4: position 0, standstill, SG min/max 0/0, read errors 0, write errors 0, ifcnt 19, reads 18149, writes 0, timeouts 0, DMA errors 0 Driver 5: position 0, assumed not present Driver 6: position 0, assumed not present Date/time: 2021-03-18 08:42:37 Cache data hit count 4294967295 Slowest loop: 57.64ms; fastest: 0.09ms === 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.147 === MainDDARing === Scheduled moves 554, completed moves 553, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state 3 === 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.2 Heater 1 is on, I-accum = 0.4 === GCodes === Segments left: 0 Movement lock held by HTTP HTTP* is idle in state(s) 1 0, running macro Telnet* is doing "M122" 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. === Filament sensors === Extruder 0 sensor: ok === CAN === Messages queued 1148, send timeouts 1148, received 0, lost 0, longest wait 0ms for reply type 0, free buffers 16 === SBC interface === State: 4, failed transfers: 0 Last transfer: 1ms ago RX/TX seq numbers: 1256/35183 SPI underruns 0, overruns 0 Number of disconnects: 0, IAP RAM available 0x10eec Buffer RX/TX: 2736/632-4080 === Duet Control Server === Duet Control Server v3.2.2 HTTP: Buffered code: G1 H1 X-305 Y-305 F240 ; move slowly to X and Y axis endstops once more (second pass) Buffered code: G90 ; absolute positioning Buffered code: G1 X3 Y300 F6000 ; go to first bed probe point and home Z Buffered code: G30 ; home Z by probing the bed ==> 152 bytes Executing macro 0:/macros/Safety Home, started by M98 P"0:/macros/Safety Home" > Next stack level File: Buffered code: G1 X75.475 Y162.206 E243.68582 Buffered code: G1 X151.794 Y238.525 E248.68940 Buffered code: G1 X152.582 Y238.525 E248.72595 Buffered code: G1 X75.475 Y161.418 E253.78122 Buffered code: G1 X75.475 Y160.629 E253.81777 Buffered code: G1 X153.371 Y238.525 E258.92473 Buffered code: G1 X154.159 Y238.525 E258.96128 Buffered code: G1 X75.475 Y159.841 E264.11994 Buffered code: G1 X75.475 Y159.052 E264.15649 Buffered code: G1 X154.948 Y238.525 E269.36683 Buffered code: G1 X155.736 Y238.525 E269.40339 Buffered code: G1 X75.475 Y158.264 E274.66543 Buffered code: G1 X75.475 Y157.475 E274.70198 Buffered code: G1 X156.525 Y238.525 E280.01571 Buffered code: G1 X157.313 Y238.525 E280.05226 Buffered code: G1 X75.475 Y156.687 E285.41769 Buffered code: G1 X75.475 Y155.898 E285.45424 Buffered code: G1 X158.102 Y238.525 E290.87136 Buffered code: G1 X158.890 Y238.525 E290.90791 Buffered code: G1 X75.475 Y155.110 E296.37672 Buffered code: G1 X75.475 Y154.322 E296.41328 Buffered code: G1 X159.678 Y238.525 E301.93378 Buffered code: G1 X160.467 Y238.525 E301.97033 Buffered code: G1 X75.475 Y153.533 E307.54253 Buffered code: G1 X75.475 Y152.745 E307.57908 Buffered code: G1 X161.255 Y238.525 E313.20298 Buffered code: G1 X162.044 Y238.525 E313.23953 Buffered code: G1 X75.475 Y151.956 E318.91511 Buffered code: G1 X75.475 Y151.168 E318.95166 Buffered code: G1 X162.832 Y238.525 E324.67894 Buffered code: G1 X163.621 Y238.525 E324.71549 Buffered code: G1 X75.475 Y150.379 E330.49446 ==> 1504 bytes Code buffer space: 2104 Configured SPI speed: 8000000 Hz Full transfers per second: 35.55 Maximum length of RX/TX data transfers: 3108/1608 File /opt/dsf/sd/gcodes/Front Mid_0.3mm_PETG_CR10_2h15m.gcode is selected, processing ok 18/03/2021, 08:40:30 m122 === Diagnostics === RepRapFirmware for Duet 3 Mini 5+ version 3.2.2 running on Duet 3 Mini5plus WiFi (SBC mode) Board ID: K1UT9-Z196U-D65J0-40KML-NY03Z-7ZF9S Used output buffers: 1 of 40 (11 max) === RTOS === Static ram: 98732 Dynamic ram: 95896 of which 60 recycled Never used RAM 50528, free system stack 124 words Tasks: Linux(ready,77) HEAT(blocked,297) CanReceiv(blocked,947) CanSender(blocked,358) CanClock(blocked,362) TMC(blocked,106) MAIN(running,519) IDLE(ready,20) AIN(blocked,264) Owned mutexes: HTTP(MAIN) === Platform === Last reset 15:33:56 ago, cause: power up Last software reset at 2021-03-17 13:46, reason: User, none spinning, available RAM 44124, slot 1 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.0, max 24.1, under voltage events: 4, over voltage events: 0, power good: yes Driver 0: position 10866, standstill, SG min/max 0/36, read errors 0, write errors 2, ifcnt 21, reads 59697, writes 55, timeouts 433, DMA errors 0, failedOp 0x6f Driver 1: position 17930, standstill, SG min/max 0/50, read errors 0, write errors 2, ifcnt 21, reads 52724, writes 55, timeouts 7405, DMA errors 0, failedOp 0x6a Driver 2: position 57, standstill, SG min/max 0/24, read errors 1, write errors 2, ifcnt 20, reads 40721, writes 53, timeouts 19408, DMA errors 0, failedOp 0x72 Driver 3: position 0, standstill, SG min/max 0/42, read errors 0, write errors 2, ifcnt 21, reads 41378, writes 52, timeouts 18751, DMA errors 0, failedOp 0x72 Driver 4: position 0, standstill, SG min/max 0/0, read errors 0, write errors 2, ifcnt 19, reads 60139, writes 45, timeouts 0, DMA errors 0 Driver 5: position 0, assumed not present Driver 6: position 0, assumed not present Date/time: 2021-03-18 08:40:30 Cache data hit count 4294967295 Slowest loop: 176.39ms; fastest: 0.07ms === 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 47646562ms, bed compensation in use: mesh, comp offset -0.147 === MainDDARing === Scheduled moves 550, completed moves 550, 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.2 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 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. === Filament sensors === Extruder 0 sensor: ok === CAN === Messages queued 504335, send timeouts 504332, 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: 62260/30651 SPI underruns 0, overruns 0 Number of disconnects: 0, IAP RAM available 0x10eec Buffer RX/TX: 2736/216-4080 === Duet Control Server === Duet Control Server v3.2.2 File: Buffered code: G1 X75.475 Y162.206 E243.68582 Buffered code: G1 X151.794 Y238.525 E248.68940 Buffered code: G1 X152.582 Y238.525 E248.72595 Buffered code: G1 X75.475 Y161.418 E253.78122 Buffered code: G1 X75.475 Y160.629 E253.81777 Buffered code: G1 X153.371 Y238.525 E258.92473 Buffered code: G1 X154.159 Y238.525 E258.96128 Buffered code: G1 X75.475 Y159.841 E264.11994 Buffered code: G1 X75.475 Y159.052 E264.15649 Buffered code: G1 X154.948 Y238.525 E269.36683 Buffered code: G1 X155.736 Y238.525 E269.40339 Buffered code: G1 X75.475 Y158.264 E274.66543 Buffered code: G1 X75.475 Y157.475 E274.70198 Buffered code: G1 X156.525 Y238.525 E280.01571 Buffered code: G1 X157.313 Y238.525 E280.05226 Buffered code: G1 X75.475 Y156.687 E285.41769 Buffered code: G1 X75.475 Y155.898 E285.45424 Buffered code: G1 X158.102 Y238.525 E290.87136 Buffered code: G1 X158.890 Y238.525 E290.90791 Buffered code: G1 X75.475 Y155.110 E296.37672 Buffered code: G1 X75.475 Y154.322 E296.41328 Buffered code: G1 X159.678 Y238.525 E301.93378 Buffered code: G1 X160.467 Y238.525 E301.97033 Buffered code: G1 X75.475 Y153.533 E307.54253 Buffered code: G1 X75.475 Y152.745 E307.57908 Buffered code: G1 X161.255 Y238.525 E313.20298 Buffered code: G1 X162.044 Y238.525 E313.23953 Buffered code: G1 X75.475 Y151.956 E318.91511 Buffered code: G1 X75.475 Y151.168 E318.95166 Buffered code: G1 X162.832 Y238.525 E324.67894 Buffered code: G1 X163.621 Y238.525 E324.71549 Buffered code: G1 X75.475 Y150.379 E330.49446 ==> 1504 bytes Code buffer space: 2520 Configured SPI speed: 8000000 Hz Full transfers per second: 35.60 Maximum length of RX/TX data transfers: 3108/1608 File /opt/dsf/sd/gcodes/Front Mid_0.3mm_PETG_CR10_2h15m.gcode is selected, processing 18/03/2021, 08:39:12 Warning: VIN under-voltage event (0.0V) 18/03/2021, 08:39:12 Error: G0/G1: insufficient axes homed 18/03/2021, 08:32:13 Height map loaded from file heightmap.csv 18/03/2021, 08:29:22 T:26.5 /240.0 T0:26.5 /240.0 B:26.7 /80.0the relevant log lines:
2021-03-18 08:39:13 Error: G0/G1: insufficient axes homed 2021-03-18 08:39:13 Warning: VIN under-voltage event (0.0V)Unlike @serbitar I notice I have no
xxxx Print auto-paused due to low voltageline in my logs which I can see in which I can see in Serbitars logs
I'm now trying to look into a simple way to log the Vout of the PSU directly during prints
-
Thanks, I think this is the same as https://forum.duet3d.com/topic/22031/duet-3-mini-5-vin-under-voltage-issues-in-sbc-mode/7 which has been reported by several users, so nothing to do with your PSU. The fact that the VIN reading is always 0.0 when it occurs confirms that. What I really need is a way of triggering this issue reliably so that I can test possible fixes. Please look at my most recent post in that thread.
Duet WiFi hardware designer and firmware engineer
Please do not ask me for Duet support via PM or email, use the forum
http://www.escher3d.com, https://miscsolutions.wordpress.com -
@dc42 Thanks, I will move over to that thread for discussion
