@fletcher You can probably get logs from the SBC:

sudo journalctl  --unit duetcontrolserver 

@dc42 Yep, looks good. No issues in the last 24h.
Many thanks for sorting this out!

I have a 515mm x 515mm x 540mm build volume HevORT which is printing quite well. Mostly its for larger parts where accuracy is important but fine detail isn't critical.
Yesterday i was getting 200mm/s with PLA out of the volcano hotend.

@dc42 It must do? The Duet Mini 3 has a jumper to select the SBC as power source.

I haven't tried but did theorise that I could feed 5v in externally, bridge all three pins of the +5 Source jumper and add jumper to "internal 5v disable" jumper.

More recently I have created a custom cable for the SBC interface so i can fee the SBC and Duet Mini 3 separately from the same external supply.

@dc42 Yep, looks good. No issues in the last 24h.
Many thanks for sorting this out!

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

With the 18:55 version I had a print paused over night and the printer didn't have any VSSA or VIN troubles.
Print has now been resumed and will upgrade again later today after it finishes.

Actually this is a bit weird. I just went through the remaining versions in sequence and 3.3b2+2 isn't spamming the logs.

FIRMWARE_NAME: RepRapFirmware for Duet 3 Mini 5+ FIRMWARE_VERSION: 3.3beta2+1 ELECTRONICS: Duet 3 Mini5plus WiFi FIRMWARE_DATE: 2021-04-09 14:40:21

This is the first version that causes the DCS log spam

@dc42 Looks like this version (and probably the other recent ones) breaks duetcontrolserver.

With 3.3b2 the logs are nice and quiet, with 3.3b2+2 the duetcontrolserver log is a fast rolling spam like this:

Apr 13 20:58:38 ender3 DuetControlServer[1585]: [error] Failed to merge JSON due to internal error: {"key":"","flags":"d99fn","result":{"boards":[{"mcuTemp":{},"vIn":{"current":0.4}}],"fans":[],"heat":{"heaters":[]},"inputs":[{"feedRate":50.0,"lineNumber":0,"state":"idle"},{"feedRate":50.0,"lineNumber":0,"state":"idle"},{"feedRate":50.0,"lineNumber":0,"state":"idle"},{"feedRate":50.0,"lineNumber":0,"state":"idle"},{"feedRate":50.0,"lineNumber":0,"state":"idle"},{"feedRate":50.0,"lineNumber":0,"state":"idle"},{"feedRate":50.0,"lineNumber":0,"state":"idle"},{"feedRate":50.0,"lineNumber":0,"state":"idle"},{"feedRate":50.0,"lineNumber":0,"state":"idle"},{"feedRate":50.0,"lineNumber":0,"state":"idle"},{"feedRate":50.0,"lineNumber":0,"state":"idle"},{"feedRate":50.0,"lineNumber":0,"state":"idle"}],"job":{"build":null,"duration":null,"filePosition":0,"layer":null,"layerTime":null,"pauseDuration":null,"timesLeft":{"filament":null,"file":null,"slicer":null},"warmUpDuration":null},"move":{"axes":[{"machinePosition":0,"userPosition":0},{"machinePosition":0,"userPosition":0},{"machinePosition":0,"userPosition":0}],"currentMove":{"acceleration":0,"deceleration":0,"laserPwm":null,"requestedSpeed":0,"topSpeed":0},"extruders":[],"virtualEPos":0},"sensors":{"analog":[],"endstops":[null,null,null],"filamentMonitors":[],"gpIn":[],"probes":[]},"seqs":{"boards":0,"directories":0,"fans":0,"global":0,"heat":0,"inputs":77,"job":1,"move":2,"network":2,"reply":0,"scanner":1,"sensors":0,"spindles":0,"state":0,"tools":0,"volChanges":[0,0],"volumes":0},"spindles":[{"current":0,"state":"unconfigured"},{"current":0,"state":"unconfigured"}],"state":{"atxPower":null,"currentTool":-1,"gpOut":[],"laserPwm":null,"msUpTime":101,"nextTool":-1,"previousTool":-1,"status":"off","time":"2021-04-13T20:58:38","upTime":83},"tools":[]},"next":0}
Apr 13 20:58:38 ender3 DuetControlServer[1585]:    System.InvalidOperationException: The requested operation requires an element of type 'Number', but the target element has type 'Array'.
Apr 13 20:58:38 ender3 DuetControlServer[1585]:    at System.Text.Json.JsonDocument.TryGetValue(Int32 index, Int32& value)
Apr 13 20:58:38 ender3 DuetControlServer[1585]:    at System.Text.Json.JsonElement.GetInt32()
Apr 13 20:58:38 ender3 DuetControlServer[1585]:    at DuetControlServer.Model.Updater.Run() in /home/christian/Duet3D/DuetSoftwareFramework/src/DuetControlServer/Model/Updater.cs:line 157

root@ender3 ~ # dpkg -l duetcontrolserver
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name              Version      Architecture Description
+++-=================-============-============-============================================
ii  duetcontrolserver 3.3-b2       armhf        Control server application for Duet 3 series

I was hoping to do another batch of small sequential prints with the new firmware

@dc42 I had reset the board much earlier, around 17:00.
At 17:24 the VSSA faults started.
At 1729 I did m122 and then reset the board so that I could copy the result out of DWC. The m122 is from before that reset.

My M122 after the board started with VSSA faults. Machine was idle at the time.

m122
=== Diagnostics ===
RepRapFirmware for Duet 3 Mini 5+ version 3.3beta2+1 (2021-04-12 08:36:30) 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: 100072
Dynamic ram: 97524 of which 0 recycled
Never used RAM 46108, free system stack 200 words
Tasks: Linux(ready,149) HEAT(delaying,314) CanReceiv(notifyWait,944) CanSender(notifyWait,371) CanClock(delaying,332) TMC(notifyWait,99) MAIN(running,596) IDLE(ready,20) AIN(notifyWait,260)
Owned mutexes: HTTP(MAIN)
=== Platform ===
Last reset 00:28:47 ago, cause: software
Last software reset at 2021-04-12 17:01, reason: User, GCodes spinning, available RAM 45892, slot 1
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
MCU revision 3, ADC conversions started 2063042, completed 2063041, timed out 0, errs 0
tnd=0 rnd=0 wrd=0 wtd=0 war=0
Supply voltage: min 0.1, current 0.1, max 18.9, under voltage events: 1, over voltage events: 0, power good: no
Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0
Driver 0: position 0, standstill, SG min/max 0/0, read errors 0, write errors 1, ifcnt 20, reads 24, writes 9, timeouts 0, DMA errors 0
Driver 1: position 0, standstill, SG min/max 0/0, read errors 0, write errors 1, ifcnt 20, reads 24, writes 9, timeouts 0, DMA errors 0
Driver 2: position 0, standstill, SG min/max 0/0, read errors 0, write errors 1, ifcnt 20, reads 24, writes 9, timeouts 0, DMA errors 0
Driver 3: position 0, standstill, SG min/max 0/0, read errors 0, write errors 1, ifcnt 20, reads 24, writes 9, timeouts 0, DMA errors 0
Driver 4: position 0, standstill, SG min/max 0/0, read errors 0, write errors 1, ifcnt 20, reads 24, writes 9, timeouts 0, DMA errors 0
Driver 5: position 0, standstill, SG min/max 0/0, read errors 0, write errors 1, ifcnt 20, reads 24, writes 9, timeouts 0, DMA errors 0
Driver 6: position 0, standstill, SG min/max 0/0, read errors 0, write errors 1, ifcnt 20, reads 24, writes 9, timeouts 0, DMA errors 0
Date/time: 2021-04-12 17:29:53
Cache data hit count 3667011328
Slowest loop: 2.60ms; 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
=== 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
Extruder 1 sensor: ok
=== CAN ===
Messages queued 15540, send timeouts 15538, 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 4514 dest 127
=== SBC interface ===
State: 4, failed transfers: 0
Last transfer: 3ms ago
RX/TX seq numbers: 57208/57208
SPI underruns 0, overruns 0
Number of disconnects: 0, IAP RAM available 0x113e8
Buffer RX/TX: 0/0-0
=== Duet Control Server ===
Duet Control Server v3.3-b2
Code buffer space: 4096
Configured SPI speed: 2000000 Hz
Full transfers per second: 33.13
Codes per second: 0.04
Maximum length of RX/TX data transfers: 2928/1088

@fletcher You can probably get logs from the SBC:

sudo journalctl  --unit duetcontrolserver