Warning: Lost connection to Duet - help needed
-
Hello Gents,
I have got my Voron 2.4 350 homing, leveling, and mesh compensation.
When I tune the Heat Bed with M303 H0 S100 and the process, enters
Auto tune starting phase 2, settling
I get Error -
Warning: Lost connection to Duet (SPI connection reset because the number of maximum retries has been exceeded)
Warning: SPI connection has been reset
Any help is greatly appreciated.
M122 === Diagnostics === RepRapFirmware for Duet 3 MB6HC version 3.5beta1 (2022-12-23 18:27:08) running on Duet 3 MB6HC v1.01 (SBC mode) Board ID: 08DJM-9P63L-DJ3T8-6J9DD-3SJ6N-9B7ZA Used output buffers: 1 of 40 (17 max) === RTOS === Static ram: 151524 Dynamic ram: 73640 of which 0 recycled Never used RAM 125508, free system stack 200 words Tasks: SBC(ready,0.6%,426) HEAT(notifyWait,0.0%,219) Move(notifyWait,0.0%,350) CanReceiv(notifyWait,0.0%,773) CanSender(notifyWait,0.0%,335) CanClock(delaying,0.0%,340) TMC(notifyWait,7.6%,90) MAIN(running,91.5%,953) IDLE(ready,0.3%,30), total 100.0% Owned mutexes: HTTP(MAIN) === Platform === Last reset 00:07:47 ago, cause: power up Last software reset at 2023-01-21 10:43, reason: MemoryProtectionFault iaccViol, GCodes spinning, available RAM 125508, slot 2 Software reset code 0x4163 HFSR 0x00000000 CFSR 0x00000001 ICSR 0x0440f804 BFAR 0x00000000 SP 0x2041b100 Task MAIN Freestk 1678 ok Stack: 00000006 204344f8 00000014 00000000 00000002 00409385 004093bc 810f0000 00000000 0048fed7 20429ed8 ffffffff 00460f95 2042c5e0 2042a5c8 00466e7f ffffffff 00000000 0000000c 0048ffef 2042c5e0 00000000 2042a5c8 0000000c 00000003 00466faf 746e6576 Error status: 0x00 Aux0 errors 0,0,0 Step timer max interval 135 MCU temperature: min 37.4, current 45.6, max 46.6 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 n/a, mspos 8, reads 53788, writes 14 timeouts 0 Driver 1: standstill, SG min n/a, mspos 8, reads 53788, writes 14 timeouts 0 Driver 2: standstill, SG min n/a, mspos 8, reads 53788, writes 14 timeouts 0 Driver 3: standstill, SG min n/a, mspos 8, reads 53788, writes 14 timeouts 0 Driver 4: standstill, SG min n/a, mspos 8, reads 53788, writes 14 timeouts 0 Driver 5: standstill, SG min n/a, mspos 8, reads 53788, writes 14 timeouts 0 Date/time: 2023-01-21 11:10:07 Slowest loop: 1.46ms; 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, segments created 0, maxWait 0ms, bed compensation in use: none, comp offset 0.000 no step interrupt scheduled === DDARing 0 === Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1 === DDARing 1 === 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 === GCodes === Movement locks held by null, 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 File2 is idle in state(s) 0 Queue2 is idle in state(s) 0 Q0 segments left 0, axes/extruders owned 0x1000003 Code queue 0 is empty Q1 segments left 0, axes/extruders owned 0x0000000 Code queue 1 is empty === CAN === Messages queued 4126, received 3747, lost 0, boc 0 Longest wait 1ms for reply type 6042, peak Tx sync delay 7, free buffers 50 (min 49), ts 2339/2338/0 Tx timeouts 0,0,0,0,0,0 === SBC interface === Transfer state: 5, failed transfers: 2, checksum errors: 9 RX/TX seq numbers: 17870/17869 SPI underruns 10, overruns 0 State: 5, disconnects: 1, timeouts: 0 total, 0 by SBC, IAP RAM available 0x29b04 Buffer RX/TX: 0/0-0, open files: 0 === Duet Control Server === Duet Control Server v3.4.5 Failed to deserialize the following properties: - InputChannel -> CodeChannel from "File2" Code buffer space: 4096 Configured SPI speed: 8000000Hz, TfrRdy pin glitches: 298 Full transfers per second: 5.62, max time between full transfers: 896.5ms, max pin wait times: 53.6ms/9.2ms Codes per second: 0.02 Maximum length of RX/TX data transfers: 4244/904 ; Configuration file for Duet 3 MB 6HC (firmware version 3.3) ;++++++General preferences M575 P1 S1 B57600 ; enable support for PanelDue G90 ; send absolute coordinates... M83 ; ...but relative extruder moves M550 P"Harlod" ; set printer name M669 K1 ; select CoreXY mode ; Thermal section ------------------------------------------------------------ M308 S3 Y"mcu-temp" A"Board" ; Board thermal sensor M912 P0 S-2 ; MCU tempurature sensor correction (subtract 2°K) ;+++++Wait a moment for the CAN expansion boards to start G4 S2 ; Drives --------------------------------------------------------------------- ; ----+---- Z-Drives ; | 2 | 3 | ; ----+---- ; | 1 | 4 | ; ----+---- ; Front M584 X0.4 Y0.5 Z0.0:0.1:0.2:0.3 E1.0 ; set drive mapping +++ possible swap X and Y M569 P0.4 S1 ; A motor goes forwards M569 P0.5 S1 ; B motor goes forwards M569 P0.0 S1 ; Z0 motor FL goes forwards M569 P0.1 S0 ; Z1 motor RL goes backwards M569 P0.2 S1 ; Z2 motor RR goes forwards M569 P0.3 S0 ; Z3 motor FR goes backwards M569 P1.0 S0 ; E motor Extruder goes backwards M350 X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation M92 X162.222 Y161.298 Z400 E693.051 ; set steps per mm ;M92 X162.222 Y161.222 Z400 E410 ; set steps per mm M566 X600.00 Y600.00 Z60.00 E8000.00 ; set maximum instantaneous speed changes (mm/min) M203 X18000.00 Y18000.00 Z3000.00 E15000.00 ; set maximum speeds (mm/min) M201 X15000.00 Y15000.00 Z350.00 E1800.00 ; set accelerations (mm/s^2) M204 P1500 T2000 ; set printing acceleration M906 X1200 Y1200 Z1200 E600 I20 ; set motor currents (mA) and motor idle factor in per cent M84 S30 ; Set idle timeout ; Axis Limits ---------------------------------------------------------------- M208 X0 Y0 Z0 S1 ; set axis minima M208 X340 Y340 Z250 S0 ; set axis maxima ; Endstops ------------------------------------------------------------------- M574 X2 S1 P"io1.in" ; configure switch-type (e.g. microswitch) endstop for high end on X via pin io1.in M574 Y2 S1 P"io2.in" ; configure switch-type (e.g. microswitch) endstop for high end on Y via pin io2.in ; Z-Probe -------------------------------------------------------------------- M558 P1 C"io3.in" H5 F120 T6000 ; set Z probe type to switch and the dive height + speeds G31 P500 X0 Y0 Z0 ; set Z probe trigger value, offset and trigger height M557 X15:335 Y25:335 S80 ; define mesh grid ; Heaters -------------------------------------------------------------------- ;-Hot Bed M308 S0 A"HOT-BED" P"temp0" Y"thermistor" T100000 B3950 ; 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 M307 H0 B1 S1.00 ; enable bang-bang mode for the bed heater and set PWM limit M140 H0 ; map heated bed to heater 0 M143 H0 S120 ; set temperature limit for heater 0 to 120C ;-Hot End M308 S1 A"HOT-END" 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 ;-Chamber Heater M308 S2 A"CHAMBER" P"temp2" Y"thermistor" T100000 B4138 ; configure sensor 2 as thermistor on pin temp2 M950 H2 C"out3" T2 ; create nozzle heater output on out1 and map it to sensor 2 M307 H2 B1 S1.00 ; disable bang-bang mode for heater and set PWM limit M143 H2 S280 ; set temperature limit for heater 1 to 280C ; Fans ----------------------------------------------------------------------- ;-Part Cooling Fan M950 F0 C"out7" Q500 ; create fan 0 on pin out7 and set its frequency M106 P0 S0 H-1 ; set fan 0 value P0. Thermostatic control is turned off H-1 ;-Hot End Fan set to start at 45 degrees M950 F1 C"out8" Q500 ; create fan 1 on pin out8 and set its frequency M106 P1 S0 H1 T45 ; set fan 1 value P1. Thermostatic control is turned on H1 ;-Hot Bed Fans M950 F2 C"out4" Q500 ; create fan 2 on pin out4 and set its frequency M106 P2 S0 H1 T45 ; set fan 2 value P2. Thermostatic control is turned off ; Tools ---------------------------------------------------------------------- M563 P0 S"Stealth Burner " D0 H1 F0:1 ; 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 ; Custom settings are not defined -------------------------------------------- ;M671 X15:15:330:330 Y25:330:330:25 S20 ; define Z belt locations ;+++++Miscellaneous M501 ; load saved parameters from non-volatile memory T0 ; select first tool -
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 -
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 -
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) -
@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.
-
@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 0SD card not detected. Check your SD card.
Scratch that, SBC mode.Ian
-
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
-
@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: 298But it may be a side effect of mixing different versions.
-
@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 -
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 - 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 -
@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 happeningIt 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
-
@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?
-
@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 -
@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 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 Ha Jay got there first!
-
-
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!
