Duet 3 and SBC connection issue.
-
Good morning,
I have run out into a problem that says:
Warning: Lost connection to Duet (Board is not available (no header)).
So, short story. Two days ago everything was fine, I was printing no issue. Today, I try to print something and that problem occurred.
I run diagnostics by M122 and for me everything looks fine:
For SBC I am using an SD card that was supplied with the Duet 3.
The duet was purchased a month ago so it's relatively new.
-
M122 code below:
24/01/2021, 09:31:36 M122
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.2 running on Duet 3 MB6HC v1.01 or later (SBC mode)
Board ID: 08DJM-956BA-NA3TJ-6JTD4-3S06M-KV8GS
Used output buffers: 1 of 40 (10 max)
=== RTOS ===
Static ram: 149788
Dynamic ram: 62932 of which 24 recycled
Never used RAM 146088, free system stack 200 words
Tasks: Linux(ready,77) HEAT(blocked,296) CanReceiv(blocked,927) CanSender(blocked,371) CanClock(blocked,352) TMC(blocked,53) MAIN(running,1179) IDLE(ready,19)
Owned mutexes: HTTP(MAIN)
=== Platform ===
Last reset 00:03:50 ago, cause: power up
Last software reset at 2021-01-24 08:51, reason: User, none spinning, available RAM 146088, slot 1
Software reset code 0x0012 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00400000 BFAR 0x00000000 SP 0x00000000 Task Linu Freestk 0 n/a
Error status: 0x00
Aux0 errors 0,0,0
Aux1 errors 0,0,0
MCU temperature: min 25.4, current 31.1, max 31.3
Supply voltage: min 23.9, current 24.0, max 24.3, under voltage events: 0, over voltage events: 0, power good: yes
12V rail voltage: min 12.0, current 12.1, max 12.2, under voltage events: 0
Driver 0: position 0, standstill, reads 45118, writes 14 timeouts 0, SG min/max 0/0
Driver 1: position 0, standstill, reads 45118, writes 14 timeouts 0, SG min/max 0/0
Driver 2: position 0, standstill, reads 45118, writes 14 timeouts 0, SG min/max 0/0
Driver 3: position 0, standstill, reads 45118, writes 14 timeouts 0, SG min/max 0/0
Driver 4: position 0, standstill, reads 45119, writes 14 timeouts 0, SG min/max 0/0
Driver 5: position 0, standstill, reads 45122, writes 11 timeouts 0, SG min/max 0/0
Date/time: 2021-01-24 09:31:35
Slowest loop: 51.95ms; fastest: 0.04ms
=== Storage ===
Free file entries: 10
SD card 0 not detected, interface speed: 37.5MBytes/sec
SD card longest read time 0.0ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 125, 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 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1, chamberHeaters = 2 -1 -1 -1
Heater 0 is on, I-accum = 0.4
Heater 1 is on, I-accum = 0.2
=== 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.
=== CAN ===
Messages queued 834, send timeouts 1983, received 0, lost 0, longest wait 0ms for reply type 0, free buffers 48
=== SBC interface ===
State: 4, failed transfers: 17
Last transfer: 1ms ago
RX/TX seq numbers: 5973/7561
SPI underruns 147, overruns 10
Number of disconnects: 1, IAP RAM available 0x2c8a8
Buffer RX/TX: 0/0-0
=== Duet Control Server ===
Duet Control Server v3.2.0
Code buffer space: 4096
Configured SPI speed: 8000000 Hz
Full transfers per second: 36.91
Maximum length of RX/TX data transfers: 2564/48 -
Is there an SD card in the Duet by chance?
Is your wiring all good? Ribbon cable?
Can you try and capture some extra data on the pi?
https://duet3d.dozuki.com/Wiki/Getting_Started_With_Duet_3#Section_Monitoring_optional
-
I think I have fixed the issue.
The SBC and Duet had external PSU 5v, the cable for SBC was going in the same path where the Bed cable is. Somehow, those two were interfering with each other (inducing current/voltage) and creating issues. Also, my ribbon cable was going under the duet which wasn't helping as well.
I have disconnected 5v PSU and now the Duet powers up the SBC. The ribbon cable is above the duet. I had a successful 2.5h print.
Those parts are very sensitive to be honest.