Warning: Lost connection to Duet - help needed

[KCMARINE]

Now I am getting the same SPI connection has been reset error when bed leveling G32

Warning: Lost connection to Duet (SPI connection reset because the number of maximum retries has been exceeded)
Warning: M307: Heater 1 predicted maximum temperature at full power is 450°C
Warning: SPI connection has been reset
Leadscrew adjustments made: 0.727 -0.022 -0.481 -0.485, points used 4, (mean, deviation) before (-0.103, 0.543) after (0.000, 0.000)
Warning: SPI connection has been reset

[KCMARINE]

M115
FIRMWARE_NAME: RepRapFirmware for Duet 3 MB6HC FIRMWARE_VERSION: 3.5beta1 ELECTRONICS: Duet 3 MB6HC v1.01 FIRMWARE_DATE: 2022-12-23 18:27:08

[KCMARINE]

When I try to do a calibration print I immediately get a Timeout while waiting for macro ?

M32 "0:/gcodes/First layer calibration.gcode"
File 0:/gcodes/First layer calibration.gcode selected for printing
Error: Timeout while waiting for macro file start.g (channel File2)

[gloomyandy]

@KCMARINE You may want to try the stable release version (3.4.5) to see if you have the same problems. If things work with 3.4.5 then it would probably be a good idea to report the above in the beta section of the forum.

[droftarts]

@KCMARINE in your M122 I see

=== 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

SD card not detected. Check your SD card.
Scratch that, SBC mode.

Ian

[KCMARINE]

Thanks - what's the process to roll back the firmware - I tried to do this by uploading 3.4.5 to DWC, and it did not work - so I am guessing I have to reset and erase and reinstall with BOSSA

[gloomyandy]

@KCMARINE Are you using an SBC setup? Can you still talk to the board using DWC after you tried to install 3.4.5?

It looks like you are still on DSF 3.4.5

@KCMARINE said in Warning: Lost connection to Duet - help needed:

Duet Control Server v3.4.5

So you had a mixture of 3.4.5 on the SBC and 3.5beta1 on your Duet board. That's probably not a good idea. Did you deliberately install the beta? What steps did you use to do that?

This is probably not good:

TfrRdy pin glitches: 298

But it may be a side effect of mixing different versions.

[KCMARINE]

@gloomyandy, thanks for catching that, mate.

A question, please, Can you advise if the MB6HC running 3.4.5 and EXP3HC running 3.4.4 will work?

What I did is keep the SBC on 3.4.5 - no change.

I removed the Duet 3 MB6HC board from the machine - erased the firmware, and reinstalled it with BOSSA version 3.4.5.

I also erased the Duet EXP3HC board and used DWC to load version 3.4.4 as I do not see a later version in the git repo - 3.4.4 was the last release.

Confirming:

M115
FIRMWARE_NAME: RepRapFirmware for Duet 3 MB6HC FIRMWARE_VERSION: 3.4.5 ELECTRONICS: Duet 3 MB6HC v1.01 FIRMWARE_DATE: 2022-11-30 19:35:23

M115 B1
Duet EXP3HC rev 1.01 or earlier firmware version 3.4.4 (2022-10-14 11:45:56)

M122
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.4.5 (2022-11-30 19:35:23) running on Duet 3 MB6HC v1.01 (SBC mode)
Board ID: 08DJM-9P63L-DJ3T8-6J9DD-3SJ6N-9B7ZA
Used output buffers: 1 of 40 (20 max)
=== RTOS ===
Static ram: 152760
Dynamic ram: 67576 of which 16 recycled
Never used RAM 130320, free system stack 192 words
Tasks: SBC(ready,0.6%,473) HEAT(notifyWait,0.0%,322) Move(notifyWait,0.0%,351) CanReceiv(notifyWait,0.0%,799) CanSender(notifyWait,0.0%,336) CanClock(delaying,0.0%,339) TMC(notifyWait,7.7%,91) MAIN(running,91.4%,923) IDLE(ready,0.4%,30), total 100.0%
Owned mutexes: HTTP(MAIN)
=== Platform ===
Last reset 00:02:37 ago, cause: software
Last software reset at 2023-01-22 04:24, reason: User, GCodes spinning, available RAM 130276, slot 0
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0043c000 BFAR 0x00000000 SP 0x00000000 Task SBC Freestk 0 n/a
Error status: 0x00
Aux0 errors 0,0,0
Step timer max interval 134
MCU temperature: min 42.3, current 42.6, max 44.8
Supply voltage: min 24.3, current 24.4, max 24.4, under voltage events: 0, over voltage events: 0, power good: yes
12V rail voltage: min 12.2, current 12.3, max 12.3, under voltage events: 0
Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0
Events: 0 queued, 0 completed
Driver 0: standstill, SG min 0, mspos 8, reads 27109, writes 14 timeouts 0
Driver 1: standstill, SG min 0, mspos 8, reads 27110, writes 14 timeouts 0
Driver 2: standstill, SG min 0, mspos 8, reads 27110, writes 14 timeouts 0
Driver 3: standstill, SG min 0, mspos 8, reads 27110, writes 14 timeouts 0
Driver 4: standstill, SG min 0, mspos 8, reads 27110, writes 14 timeouts 0
Driver 5: standstill, SG min 0, mspos 8, reads 27110, writes 14 timeouts 0
Date/time: 2023-01-22 04:27:32
Slowest loop: 1.27ms; fastest: 0.05ms
=== 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, segments created 0, maxWait 0ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== AuxDDARing ===
Scheduled moves 0, completed 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, chamber heaters -1 -1 -1 -1, ordering errs 0
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
=== CAN ===
Messages queued 1408, received 1267, lost 0, boc 0
Longest wait 1ms for reply type 6042, peak Tx sync delay 290, free buffers 50 (min 49), ts 788/787/0
Tx timeouts 0,0,0,0,0,0
=== SBC interface ===
Transfer state: 5, failed transfers: 0, checksum errors: 1
RX/TX seq numbers: 6088/6088
SPI underruns 1, overruns 0
State: 5, disconnects: 0, timeouts: 0 total, 0 by SBC, IAP RAM available 0x2ad48
Buffer RX/TX: 0/0-0, open files: 0
=== Duet Control Server ===
Duet Control Server v3.4.5
Code buffer space: 4096
Configured SPI speed: 8000000Hz, TfrRdy pin glitches: 5
Full transfers per second: 39.44, max time between full transfers: 102.9ms, max pin wait times: 59.0ms/14.9ms
Codes per second: 0.48
Maximum length of RX/TX data transfers: 2988/904
 

[KCMARINE]

Still happening - Restarted and tried to run bed leveling - immediately getting

Connection to Duet established
1/22/2023, 12:45:13 PM	Warning: Lost connection to Duet (Timeout while waiting for transfer ready pin)
1/22/2023, 12:45:04 PM	Connection to Duet established
1/22/2023, 12:45:04 PM	Warning: Lost connection to Duet (SPI connection reset because the number of maximum retries has been exceeded)
1/22/2023, 12:44:57 PM	Connection to Duet established
1/22/2023, 12:44:57 PM	Warning: Lost connection to Duet (SPI connection reset because the number of maximum retries has been exceeded)
1/22/2023, 12:44:54 PM	Warning: SPI connection has been reset
1/22/2023, 12:44:47 PM	Connection to Duet established
1/22/2023, 12:44:47 PM	Warning: Lost connection to Duet (SPI connection reset because the number of maximum retries has been exceeded)
1/22/2023, 12:44:17 PM	Warning: M307: Heater 1 predicted maximum temperature at full power is 450°C
1/22/2023, 12:44:16 PM	Connection established

I am at a loss now what can be wrong

[KCMARINE]

@KCMARINE - TfrRdy Pin glitches: 5

Configured SPI speed: 8000000Hz, TfrRdy pin glitches: 5
Full transfers per second: 39.44, max time between full transfers: 102.9ms, max pin wait times: 59.0ms/14.9ms

[KCMARINE]

@gloomyandy - recap to answer your questions

Are you using an SBC setup?

Yes, I downloaded https://pkg.duet3d.com/DuetPi.zip and flashed the SD card.

Did you deliberately install the beta?

Yes, did make the upgrade

What steps did you use to do that?

I made the upgrade by downloading the 3.5 beta from the git repo and uploaded to DWC then installed it unknowingly that it may conflict with the SBC 3.4.5

Can you still talk to the board using DWC after you tried to install 3.4.5?
.Yes, however SPI connection reset and timeouts are still happening

It looks like you are still on DSF 3.4.5

Yes, now I have downgraded all firmware to match the Pi SBC and problems still remain

[gloomyandy]

@KCMARINE So you are now on 3.4.5 on for both DSF and RRF (at least that is what your last posted M122 shows). Can you post another one just so we can be sure. What SBC are you using? Is it a raspberry Pi (which model) or something else?

[KCMARINE]

@gloomyandy thanks. I can confirm the following:

SBC is Raspberry Pi 4 Model B

and M122

1/22/2023, 5:53:12 PM	m122
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.4.5 (2022-11-30 19:35:23) running on Duet 3 MB6HC v1.01 (SBC mode)
Board ID: 08DJM-9P63L-DJ3T8-6J9DD-3SJ6N-9B7ZA
Used output buffers: 1 of 40 (19 max)
=== RTOS ===
Static ram: 152760
Dynamic ram: 67576 of which 16 recycled
Never used RAM 130320, free system stack 200 words
Tasks: SBC(ready,0.6%,461) HEAT(notifyWait,0.0%,322) Move(notifyWait,0.0%,351) CanReceiv(notifyWait,0.0%,774) CanSender(notifyWait,0.0%,336) CanClock(delaying,0.0%,339) TMC(notifyWait,7.6%,91) MAIN(running,90.9%,923) IDLE(ready,0.9%,30), total 100.0%
Owned mutexes: HTTP(MAIN)
=== Platform ===
Last reset 00:04:22 ago, cause: power up
Last software reset time unknown, reason: MemoryProtectionFault mmarValid daccViol, GCodes spinning, available RAM 132888, slot 0
Software reset code 0x4163 HFSR 0x00000000 CFSR 0x00000082 ICSR 0x00400804 BFAR 0x0000633a SP 0x2041b450 Task MAIN Freestk 1628 ok
Stack: 2042a370 00000000 20418198 0000632e 00000000 00489db5 00489de6 21030000 2042c550 00000000 00000000 0048922f 00000000 00000000 00000000 0000000a 00000000 2042c550 20419a84 2042d1ac 00000000 00000001 00000000 00488ee7 00000001 00489db5 00000000
Error status: 0x00
Aux0 errors 0,0,0
Step timer max interval 135
MCU temperature: min 35.9, current 44.9, max 44.9
Supply voltage: min 24.3, current 24.3, max 24.4, under voltage events: 0, over voltage events: 0, power good: yes
12V rail voltage: min 12.2, current 12.3, max 12.3, under voltage events: 0
Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0
Events: 0 queued, 0 completed
Driver 0: standstill, SG min 0, mspos 8, reads 22115, writes 14 timeouts 0
Driver 1: standstill, SG min 0, mspos 8, reads 22115, writes 14 timeouts 0
Driver 2: standstill, SG min 0, mspos 8, reads 22115, writes 14 timeouts 0
Driver 3: standstill, SG min 0, mspos 8, reads 22115, writes 14 timeouts 0
Driver 4: standstill, SG min 0, mspos 8, reads 22115, writes 14 timeouts 0
Driver 5: standstill, SG min 0, mspos 8, reads 22115, writes 14 timeouts 0
Date/time: 2023-01-22 09:53:11
Slowest loop: 2.22ms; fastest: 0.03ms
=== 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, segments created 0, maxWait 0ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== AuxDDARing ===
Scheduled moves 0, completed 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, chamber heaters -1 -1 -1 -1, ordering errs 0
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
=== CAN ===
Messages queued 2265, received 2101, lost 0, boc 0
Longest wait 0ms for reply type 0, peak Tx sync delay 6, free buffers 50 (min 49), ts 1311/1310/0
Tx timeouts 0,0,0,0,0,0
=== SBC interface ===
Transfer state: 5, failed transfers: 0, checksum errors: 0
RX/TX seq numbers: 11230/11230
SPI underruns 0, overruns 0
State: 5, disconnects: 0, timeouts: 0 total, 0 by SBC, IAP RAM available 0x2ad48
Buffer RX/TX: 0/0-0, open files: 0
=== Duet Control Server ===
Duet Control Server v3.4.5
Code buffer space: 4096
Configured SPI speed: 8000000Hz, TfrRdy pin glitches: 0
Full transfers per second: 0.61, max time between full transfers: 425.3ms, max pin wait times: 44.1ms/51.4ms
Codes per second: 0.00
Maximum length of RX/TX data transfers: 6196/836
 

[jay_s_uk]

@KCMARINE are you using the supplied cable between the pi and the duet? Can you post a photo of it's routing so we can see what's near it etc?

[KCMARINE]

@gloomyandy

[gloomyandy]

@KCMARINE Yep both versions match. Could you also post a picture showing how the two boards are connected. After that I think this is one for @chrishamm

[gloomyandy]

@gloomyandy Ha Jay got there first!

[KCMARINE]

@gloomyandy

[KCMARINE]

@gloomyandy

Thanks for the help - I appreciate all that you do

I am out of ideas.

My last attempt/thought is to flash another SD card with a new copy of DuetPi.zip and see what happens!

[KCMARINE]

@gloomyandy @droftarts @jay_s_uk

Success - after flashing a new SD card with DuetPi.zip I am happy to report that I have no more communication errors and I can print my first calibration cube.

I believe that the issue may have been caused by the additional motion installation for the Logitech webcam

https://www.instructables.com/How-to-Make-Raspberry-Pi-Webcam-Server-and-Stream-/

The strange thing is I have this running on another SBC Pi 4 and MB6HC running 3.4.5 on a delta with no issues, guessing it could be a compatibility issue with 3.5 upgrades and then a downgrade, just a stab in the dark.

Thanks again for your support gents - very much appreciated.