Duet 3 SBC DCS has stopped
-
Is it possible there was an extrusion command issued while the heater wasn't at the min temp?
-
@Phaedrux I highly doubt it. That was in the middle of a print. I had to restart the printer to get it to respond so I couldn't take a screenshot but the temp was stable until those errors started showing and it wasn't in a fault state.
-
I tried with a different raspberry pi but same outcome. I was able to connect a monitor but was unable to copy the full output. This was the best I could get
-
So it happened again. I swapped to a Raspberry Pi 4 with new firmware.
11/6/2020, 12:04:08 AM Cancelled printing file 0:/gcodes/a1.gcode, print time was 0h 20m 11/6/2020, 12:04:08 AM Warning: Controller has been reset 11/5/2020, 11:48:41 PM Height map saved to file heightmap.csv 11/5/2020, 11:48:41 PM 16 points probed, min error -0.018, max error 0.070, mean 0.034, deviation 0.027 11/5/2020, 11:48:41 PM Leadscrew adjustments made: -0.027 -0.025 -0.033, points used 3, (mean, deviation) before (-0.028, 0.003) after (-0.000, 0.000) 11/5/2020, 11:48:41 PM Leadscrew adjustments made: -0.059 -0.023 -0.016, points used 3, (mean, deviation) before (-0.031, 0.014) after (0.000, 0.000) 11/5/2020, 11:48:41 PM Leadscrew adjustments made: -0.022 -0.039 -0.054, points used 3, (mean, deviation) before (-0.039, 0.010) after (0.000, 0.000) 11/5/2020, 11:46:07 PM Height map loaded from file heightmap.csv 11/5/2020, 11:44:01 PM M32 "0:/gcodes/a1.gcode" File 0:/gcodes/a1.gcode selected for printing11/6/2020, 12:12:01 AM M122 === Diagnostics === RepRapFirmware for Duet 3 MB6HC version 3.1.1 running on Duet 3 MB6HC v1.01 or later (SBC mode) Board ID: 08DJM-956L2-G43S8-6J9D0-3S46T-9U2LF Used output buffers: 1 of 40 (13 max) === RTOS === Static ram: 154604 Dynamic ram: 163392 of which 64 recycled Exception stack ram used: 544 Never used ram: 74612 Tasks: ETHERNET(blocked,824) NETWORK(ready,1960) HEAT(blocked,1188) CanReceiv(suspended,3820) CanSender(suspended,1420) CanClock(blocked,1436) TMC(blocked,60) MAIN(running,2672) IDLE(ready,76) Owned mutexes: === Platform === Last reset 03:23:27 ago, cause: power up Last software reset at 2020-11-05 20:48, reason: User, spinning module LinuxInterface, available RAM 74612 bytes (slot 3) Software reset code 0x0010 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0444a000 BFAR 0x00000000 SP 0xffffffff Task MAIN Error status: 0 MCU temperature: min 39.7, current 39.9, max 41.4 Supply voltage: min 24.3, current 24.6, max 24.7, under voltage events: 0, over voltage events: 0, power good: yes 12V rail voltage: min 12.1, current 12.1, max 12.2, under voltage events: 0 Driver 0: standstill, reads 17162, writes 4 timeouts 0, SG min/max 0/160 Driver 1: standstill, reads 17162, writes 4 timeouts 0, SG min/max 0/400 Driver 2: standstill, reads 17162, writes 4 timeouts 0, SG min/max 0/384 Driver 3: standstill, reads 17162, writes 4 timeouts 0, SG min/max 0/1023 Driver 4: standstill, reads 17162, writes 4 timeouts 0, SG min/max 0/1023 Driver 5: standstill, reads 17162, writes 4 timeouts 0, SG min/max 0/1019 Date/time: 2020-11-06 00:12:00 Slowest loop: 9.38ms; fastest: 0.21ms === 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 === Hiccups: 0(0), FreeDm: 375, MinFreeDm: 322, MaxWait: 302820ms Bed compensation in use: mesh, comp offset 0.000 === MainDDARing === Scheduled moves: 3599, completed moves: 3599, StepErrors: 0, LaErrors: 0, Underruns: 0, 0 CDDA state: -1 === AuxDDARing === Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0 CDDA state: -1 === Heat === Bed heaters = 0 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1, chamberHeaters = -1 -1 -1 -1 === GCodes === Segments left: 0 Movement lock held by null HTTP* is ready with "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. === Network === Slowest loop: 0.77ms; fastest: 0.03ms Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions Telnet(0), 0 sessions HTTP sessions: 0 of 8 - Ethernet - State: establishingLink Error counts: 0 0 0 0 0 Socket states: 0 0 0 0 0 0 0 0 === Filament sensors === Extruder 0 sensor: ok === CAN === Messages sent 7459, longest wait 0ms for type 0 === Linux interface === State: 0, failed transfers: 8 Last transfer: 19ms ago RX/TX seq numbers: 2795/56430 SPI underruns 13, overruns 11 Number of disconnects: 3 Buffer RX/TX: 0/0-0 === Duet Control Server === Duet Control Server v3.1.1 Code buffer space: 4096 Configured SPI speed: 8000000 Hz Full transfers per second: 32.12 -
Hi, please keep an eye out for RRF 3.2 Beta 3 which may have a fix for you. Not sure on the ETA other than.. soon.
-
This is mostly to maintain tracking
Errored out a few times during printing but it didn't stop printing until 4:54:48
11/6/2020, 4:59:19 PM Connection established 11/6/2020, 4:58:54 PM Connection interrupted, attempting to reconnect... Network error 11/6/2020, 4:54:57 PM Connection established 11/6/2020, 4:54:48 PM Connection interrupted, attempting to reconnect... DCS has been stopped 11/6/2020, 4:19:04 PM Connection to Duet established 11/6/2020, 4:19:04 PM Warning: Lost connection to Duet (Board is not available (no data response)) 11/6/2020, 4:08:08 PM Connection to Duet established 11/6/2020, 4:08:08 PM Warning: Lost connection to Duet (Board is not available (no data response)) 11/6/2020, 3:50:15 PM Connection to Duet established 11/6/2020, 3:50:15 PM Warning: Lost connection to Duet (Board is not available (no data response)) 11/6/2020, 2:44:36 PM Connection to Duet established 11/6/2020, 2:44:36 PM Warning: Lost connection to Duet (Board is not available (no data response)) 11/6/2020, 1:39:53 PM Height map saved to file heightmap.csvM98 P"config.g" HTTP is enabled on port 80 FTP is disabled TELNET is disabled Warning: M307: Heater 0 appears to be over-powered. If left on at full power, its temperature is predicted to reach 351C11/6/2020, 5:01:05 PM m122 === Diagnostics === RepRapFirmware for Duet 3 MB6HC version 3.1.1 running on Duet 3 MB6HC v1.01 or later (SBC mode) Board ID: 08DJM-956L2-G43S8-6J9D0-3S46T-9U2LF Used output buffers: 1 of 40 (10 max) === RTOS === Static ram: 154604 Dynamic ram: 163184 of which 64 recycled Exception stack ram used: 528 Never used ram: 74836 Tasks: ETHERNET(blocked,832) NETWORK(ready,1968) HEAT(blocked,1188) CanReceiv(suspended,3820) CanSender(suspended,1420) CanClock(blocked,1436) TMC(blocked,68) MAIN(running,2672) IDLE(ready,76) Owned mutexes: === Platform === Last reset 03:27:54 ago, cause: power up Last software reset at 2020-11-05 20:48, reason: User, spinning module LinuxInterface, available RAM 74612 bytes (slot 3) Software reset code 0x0010 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0444a000 BFAR 0x00000000 SP 0xffffffff Task MAIN Error status: 0 MCU temperature: min 36.5, current 40.1, max 40.9 Supply voltage: min 24.3, current 24.6, max 24.8, 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: standstill, reads 30653, writes 19 timeouts 0, SG min/max 0/227 Driver 1: standstill, reads 30649, writes 23 timeouts 0, SG min/max 0/1023 Driver 2: standstill, reads 30650, writes 23 timeouts 0, SG min/max 0/1023 Driver 3: standstill, reads 30650, writes 23 timeouts 0, SG min/max 0/1023 Driver 4: standstill, reads 30651, writes 23 timeouts 0, SG min/max 0/1023 Driver 5: standstill, reads 30651, writes 23 timeouts 0, SG min/max 0/708 Date/time: 2020-11-06 17:01:05 Slowest loop: 9.23ms; fastest: 0.14ms === 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 === Hiccups: 0(0), FreeDm: 375, MinFreeDm: 317, MaxWait: 187934ms Bed compensation in use: mesh, comp offset 0.000 === MainDDARing === Scheduled moves: 270437, completed moves: 270437, StepErrors: 0, LaErrors: 0, Underruns: 0, 0 CDDA state: -1 === AuxDDARing === Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0 CDDA state: -1 === Heat === Bed heaters = 0 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1, chamberHeaters = -1 -1 -1 -1 === GCodes === Segments left: 0 Movement lock held by null HTTP* is ready with "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. === Network === Slowest loop: 0.94ms; fastest: 0.01ms Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions Telnet(0), 0 sessions HTTP sessions: 0 of 8 - Ethernet - State: establishingLink Error counts: 0 0 0 0 0 Socket states: 0 0 0 0 0 0 0 0 === Filament sensors === Extruder 0 sensor: ok === CAN === Messages sent 49847, longest wait 0ms for type 0 === Linux interface === State: 0, failed transfers: 22 Last transfer: 20ms ago RX/TX seq numbers: 3664/7222 SPI underruns 35, overruns 14 Number of disconnects: 1 Buffer RX/TX: 0/0-0 === Duet Control Server === Duet Control Server v3.1.1 Code buffer space: 4096 Configured SPI speed: 8000000 Hz Full transfers per second: 32.07 -
Disconnected panel due
11/6/2020, 5:23:22 PM Connection established 11/6/2020, 5:21:46 PM Connection interrupted, attempting to reconnect... DCS has been stopped 11/6/2020, 5:21:16 PM Cancelled printing file 0:/gcodes/a1.gcode, print time was 0h 19m 11/6/2020, 5:21:15 PM Warning: Controller has been reset 11/6/2020, 5:06:52 PM Height map saved to file heightmap.csv11/6/2020, 5:23:59 PM M122 === Diagnostics === RepRapFirmware for Duet 3 MB6HC version 3.1.1 running on Duet 3 MB6HC v1.01 or later (SBC mode) Board ID: 08DJM-956L2-G43S8-6J9D0-3S46T-9U2LF Used output buffers: 1 of 40 (13 max) === RTOS === Static ram: 154604 Dynamic ram: 163392 of which 140 recycled Exception stack ram used: 544 Never used ram: 74536 Tasks: ETHERNET(blocked,832) NETWORK(ready,1968) HEAT(blocked,1188) CanReceiv(suspended,3820) CanSender(suspended,1384) CanClock(blocked,1436) TMC(blocked,68) MAIN(running,2672) IDLE(ready,76) Owned mutexes: === Platform === Last reset 03:50:47 ago, cause: power up Last software reset at 2020-11-05 20:48, reason: User, spinning module LinuxInterface, available RAM 74612 bytes (slot 3) Software reset code 0x0010 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0444a000 BFAR 0x00000000 SP 0xffffffff Task MAIN Error status: 0 MCU temperature: min 39.5, current 39.8, max 40.3 Supply voltage: min 24.3, current 24.6, max 24.8, under voltage events: 0, over voltage events: 0, power good: yes 12V rail voltage: min 12.0, current 12.1, max 12.1, under voltage events: 0 Driver 0: standstill, reads 32788, writes 7 timeouts 0, SG min/max 0/1023 Driver 1: standstill, reads 32787, writes 8 timeouts 0, SG min/max 0/226 Driver 2: standstill, reads 32788, writes 7 timeouts 0, SG min/max 0/1023 Driver 3: standstill, reads 32788, writes 7 timeouts 0, SG min/max 0/179 Driver 4: standstill, reads 32788, writes 7 timeouts 0, SG min/max 0/175 Driver 5: standstill, reads 32788, writes 7 timeouts 0, SG min/max 0/127 Date/time: 2020-11-06 17:23:58 Slowest loop: 9.29ms; fastest: 0.21ms === 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 === Hiccups: 0(0), FreeDm: 375, MinFreeDm: 323, MaxWait: 541330ms Bed compensation in use: mesh, comp offset 0.000 === MainDDARing === Scheduled moves: 3364, completed moves: 3364, StepErrors: 0, LaErrors: 0, Underruns: 0, 0 CDDA state: -1 === AuxDDARing === Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0 CDDA state: -1 === Heat === Bed heaters = 0 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1, chamberHeaters = -1 -1 -1 -1 === GCodes === Segments left: 0 Movement lock held by null HTTP* is ready with "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. === Network === Slowest loop: 0.76ms; fastest: 0.03ms Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions Telnet(0), 0 sessions HTTP sessions: 0 of 8 - Ethernet - State: establishingLink Error counts: 0 0 0 0 0 Socket states: 0 0 0 0 0 0 0 0 === Filament sensors === Extruder 0 sensor: ok === CAN === Messages sent 5531, longest wait 0ms for type 0 === Linux interface === State: 0, failed transfers: 22 Last transfer: 20ms ago RX/TX seq numbers: 1766/48405 SPI underruns 38, overruns 14 Number of disconnects: 2 Buffer RX/TX: 0/0-0 === Duet Control Server === Duet Control Server v3.1.1 Code buffer space: 4096 Configured SPI speed: 8000000 Hz Full transfers per second: 32.0311/6/2020, 5:24:21 PM M98 P"config.g" HTTP is enabled on port 80 FTP is disabled TELNET is disabled Warning: M307: Heater 0 appears to be over-powered. If left on at full power, its temperature is predicted to reach 351C -
So last night I swapped to standalone mode completely disconnecting the pi. I was able to print the same file I had issues with. So sounds like the issue is with the communication between the Pi and the Duet 3.
I'm going to try the beta 3.2.3 with SBC and try again.
-
@dhusolo said in Duet 3 SBC DCS has stopped:
So last night I swapped to standalone mode completely disconnecting the pi. I was able to print the same file I had issues with. So sounds like the issue is with the communication between the Pi and the Duet 3.
I'm going to try the beta 3.2.3 with SBC and try again.
Sounds like a good plan to me. As with any beta, exercise caution - I suggest you baby-sit the print, at least for a while.
-
@dhusolo said in Duet 3 SBC DCS has stopped:
So last night I swapped to standalone mode completely disconnecting the pi. I was able to print the same file I had issues with. So sounds like the issue is with the communication between the Pi and the Duet 3.
I'm going to try the beta 3.2.3 with SBC and try again.
I did try to tell you a few days ago.....
Nice to be proven correct again....
It must be noted that I had the same problem on 3.1.1 firmware too
-
@CaLviNx Yea you're correct but why did you feel the need to say it like that? I was troubleshooting. I started focusing on the firmware side. When all options were exhausted i eliminated the Pi
-
After upgrading to the latest beta 3.2.3 I get the error Could not connect to duet (Board is not available (no header))
The error exists even after swapping back to the original 3.1.1 pi.
-
What version is on the Duet itself?
See this thread for downgrading instructions.
https://forum.duet3d.com/topic/19257/downgrade-from-3-2beta2-to-3-1-1/
-
@Phaedrux thanks. I ran
sudo wget -O /opt/dsf/sd/sys/Duet3Firmware_MB6HC.bin https://github.com/Duet3D/RepRapFirmware/releases/download/3.1.1/Duet3Firmware_MB6HC.bin sudo apt -y --allow-downgrades install duetsoftwareframework=3.1.1 duetcontrolserver=3.1.1 duetruntime=3.1.1 duetsd=1.0.6 duettools=3.1.1 duetwebcontrol=3.1.1 duetwebserver=3.1.0 reprapfirmware=3.1.1-1Unpacking duetruntime (3.1.1) over (3.2.0-beta3) ... Setting up duetruntime (3.1.1) ... Setting up duetwebcontrol (3.1.1) ... Setting up duetcontrolserver (3.1.1) ... Installing new version of config file /opt/dsf/conf/config.json ... Setting up duettools (3.1.1) ... Setting up duetwebserver (3.1.0) ... Setting up duetsd (1.0.6) ... Setting up reprapfirmware (3.1.1-1) ... [fatal] Could not connect to Duet (Board is not available (no header)) Setting up duetsoftwareframework (3.1.1) ... -
The cable is good. I used a continuity tester to check each pin from the duet board to the pi. Every pin had a connection to it's corresponding one. I'm starting to suspect there's an issue with the board
-
@dc42 any ideas? everything i've tried has failed. The board will work in standalone but the reason I bought it is for the benefits of with the SBC
-
@dhusolo said in Duet 3 SBC DCS has stopped:
@CaLviNx Yea you're correct but why did you feel the need to say it like that? I was troubleshooting. I started focusing on the firmware side. When all options were exhausted i eliminated the Pi
I was trying to help you and save you time, instead of listening to reason you blew it off and acted like I was speaking out of my ass
-
@CaLviNx said in Duet 3 SBC DCS has stopped:
@dhusolo said in Duet 3 SBC DCS has stopped:
@CaLviNx Yea you're correct but why did you feel the need to say it like that? I was troubleshooting. I started focusing on the firmware side. When all options were exhausted i eliminated the Pi
I was trying to help you and save you time, instead of listening to reason you blew it off and acted like I was speaking out of my ass
How bout you save us all some time and just exit the thread please.
-
@dhusolo said in Duet 3 SBC DCS has stopped:
After upgrading to the latest beta 3.2.3 I get the error Could not connect to duet (Board is not available (no header))
The error exists even after swapping back to the original 3.1.1 pi.
Can you try beta 3 again? It seems like something might have gone wrong on the update.
-
@Phaedrux said in Duet 3 SBC DCS has stopped
How bout you save us all some time and just exit the thread please.
What why? Don't you don't like the fact that I pointed out the problem days ago, a problem that has been proven to be true, just because you don't like the fact its still a fact none the less.
