Duet 3 6hc + SBC just stops printing
-
Tried a new setup on a different card. Can't connect to the Pi4, DWC or PuTTy doesn't connect. Put other card back, it connects, but won't keep printing. does show a low voltage on the screen just before to showes DWC. Tried the Pi0W again with the 2020-07-20-DuetPi.img, didn't connect.
Next: direct connection, it works.
Looks like my Pi4 is flakey, need to get another one. Will know for sure in a few days.
-
@Stephen6309 So far, the direct mode is still working.
-
Update: Got a new Pi4 from Adafruit with an acrylic case. Installed DuetPi OS with GUI and a fanshim. So far it works and seem to be a bit more responsive. Printed a magic fish just fine.
In a few days, we'll see if it stays working
-
It's still printing.
-
Spoke too soon. It's doing it again. Going to ask for a new ribbon cable.
-
-
@Stephen6309 said in Duet 3 6hc + SBC just stops printing:
Filastruder needs authorization for a replacement cable.
Approved.
Duet WiFi hardware designer and firmware engineer
Please do not ask me for Duet support via PM or email, use the forum
http://www.escher3d.com, https://miscsolutions.wordpress.com -
Received new ribbon cable, installed last Thursday. Worked fine Thursday and Saturday. Today it's once again stopping during the skirt. Emergancy stop needed to get any axes to move. The ribblon cable wasn't the problem. Can run in direct mode with no problems.
Disabled the write buffer:
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-6J9FD-3SJ6K-TB0LG
Used output buffers: 1 of 40 (10 max)
=== RTOS ===
Static ram: 154604
Dynamic ram: 163052 of which 44 recycled
Exception stack ram used: 504
Never used ram: 75012
Tasks: ETHERNET(blocked,832) NETWORK(ready,1968) HEAT(blocked,1188) CanReceiv(suspended,3820) CanSender(suspended,1432) CanClock(blocked,1436) TMC(blocked,68) MAIN(running,4952) IDLE(ready,76)
Owned mutexes:
=== Platform ===
Last reset 00:04:28 ago, cause: software
Last software reset at 2020-10-04 14:15, reason: User, spinning module LinuxInterface, available RAM 75204 bytes (slot 2)
Software reset code 0x0010 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0444a000 BFAR 0x00000000 SP 0xffffffff Task MAIN
Error status: 0
MCU temperature: min 37.6, current 39.4, max 40.1
Supply voltage: min 23.7, current 24.2, max 24.2, 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: ok, reads 59415, writes 17 timeouts 0, SG min/max 0/930
Driver 1: ok, reads 59416, writes 17 timeouts 0, SG min/max 0/1023
Driver 2: ok, reads 59416, writes 17 timeouts 0, SG min/max 0/846
Driver 3: standstill, reads 59417, writes 17 timeouts 0, SG min/max 0/133
Driver 4: standstill, reads 59423, writes 11 timeouts 0, SG min/max 0/0
Driver 5: standstill, reads 59424, writes 11 timeouts 0, SG min/max 0/0
Date/time: 2020-10-04 14:20:07
Slowest loop: 5.34ms; 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: 295, MinFreeDm: 295, MaxWait: 77339ms
Bed compensation in use: mesh, comp offset 0.000
=== MainDDARing ===
Scheduled moves: 175, completed moves: 115, StepErrors: 0, LaErrors: 0, Underruns: 0, 0 CDDA state: 3
=== 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
Heater 0 is on, I-accum = 0.1
Heater 1 is on, I-accum = 0.3
=== GCodes ===
Segments left: 1
Movement lock held by null
HTTP* is ready with "M122" in state(s) 0
Telnet is idle in state(s) 0
File* is doing "G1 X102.293999 Y192.054993 E0.178150" 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 0, running macro
Aux2 is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Slowest loop: 0.97ms; 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
=== CAN ===
Messages sent 1050, longest wait 0ms for type 0
=== Linux interface ===
State: 0, failed transfers: 0
Last transfer: 20ms ago
RX/TX seq numbers: 8369/8371
SPI underruns 0, overruns 0
Number of disconnects: 0
Buffer RX/TX: 3696/1128-4080
=== Duet Control Server ===
Duet Control Server v3.1.1
File:
Buffered code: G1 X102.294 Y192.055 E0.17815
Buffered code: G1 X100.964 Y188.823 E0.16215
Buffered code: G1 X99.743 Y185.547 E0.16218
Buffered code: G1 X98.556 Y182.005 E0.17331
Buffered code: G1 X97.531 Y178.554 E0.16700
Buffered code: G1 X96.647 Y175.165 E0.16248
Buffered code: G1 X95.826 Y171.521 E0.17331
Buffered code: G1 X95.157 Y167.978 E0.16730
Buffered code: G1 X94.623 Y164.523 E0.16218
Buffered code: G1 X94.178 Y160.820 E0.17301
Buffered code: G1 X93.865 Y157.103 E0.17304
Buffered code: G1 X93.688 Y153.606 E0.16246
Buffered code: G1 X93.627 Y150.000 E0.16730
Buffered code: G1 X93.693 Y146.271 E0.17304
Buffered code: G1 X93.872 Y142.780 E0.16216
Buffered code: G1 X94.178 Y139.187 E0.16730
Buffered code: G1 X94.623 Y135.477 E0.17334
Buffered code: G1 X95.157 Y132.023 E0.16215
Buffered code: G1 X95.806 Y128.581 E0.16248
Buffered code: G1 X96.645 Y124.841 E0.17782
Buffered code: G1 X97.529 Y121.452 E0.16248
Buffered code: G1 X98.523 Y118.101 E0.16218
Buffered code: G1 X99.703 Y114.563 E0.17301
Buffered code: G1 X101.008 Y111.069 E0.17304
Buffered code: G1 X102.339 Y107.837 E0.16216
Buffered code: G1 X103.778 Y104.651 E0.16218
Buffered code: G1 X105.429 Y101.300 E0.17331
Buffered code: G1 X107.134 Y98.122 E0.16730
Buffered code: G1 X108.890 Y95.099 E0.16218
Buffered code: G1 X110.873 Y91.933 E0.17331
Buffered code: G1 X112.893 Y88.946 E0.16730
Buffered code: G1 X114.911 Y86.166 E0.15940
==> 1532 bytes
Daemon:
Finishing macro daemon.g, started by system
Next stack level
Code buffer space: 2568
Configured SPI speed: 8000000 Hz
Full transfers per second: 32.12
File /opt/dsf/sd/gcodes/SPOOL/PLA_custom_B_2_215C.gcode is selected, processing
After the emergency stop:
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-6J9FD-3SJ6K-TB0LG
Used output buffers: 1 of 40 (10 max)
=== RTOS ===
Static ram: 154604
Dynamic ram: 163052 of which 44 recycled
Exception stack ram used: 512
Never used ram: 75004
Tasks: ETHERNET(blocked,832) NETWORK(ready,1968) HEAT(blocked,1188) CanReceiv(suspended,3820) CanSender(suspended,1420) CanClock(blocked,1436) TMC(blocked,192) MAIN(running,4952) IDLE(ready,76)
Owned mutexes:
=== Platform ===
Last reset 00:02:33 ago, cause: software
Last software reset at 2020-10-04 14:26, reason: User, spinning module LinuxInterface, available RAM 75452 bytes (slot 0)
Software reset code 0x0010 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0444a000 BFAR 0x00000000 SP 0xffffffff Task MAIN
Error status: 0
MCU temperature: min 39.0, current 39.6, max 40.3
Supply voltage: min 23.7, current 24.0, max 24.2, 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 29308, writes 17 timeouts 0, SG min/max 0/260
Driver 1: standstill, reads 29308, writes 17 timeouts 0, SG min/max 0/255
Driver 2: standstill, reads 29309, writes 17 timeouts 0, SG min/max 0/459
Driver 3: standstill, reads 29309, writes 17 timeouts 0, SG min/max 0/122
Driver 4: standstill, reads 29316, writes 11 timeouts 0, SG min/max 0/0
Driver 5: standstill, reads 29316, writes 11 timeouts 0, SG min/max 0/0
Date/time: 2020-10-04 14:28:51
Slowest loop: 5.20ms; 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: 295, MinFreeDm: 295, MaxWait: 83293ms
Bed compensation in use: mesh, comp offset 0.000
=== MainDDARing ===
Scheduled moves: 175, completed moves: 115, StepErrors: 0, LaErrors: 0, Underruns: 0, 0 CDDA state: 3
=== 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
Heater 0 is on, I-accum = 0.1
Heater 1 is on, I-accum = 0.4
=== GCodes ===
Segments left: 1
Movement lock held by null
HTTP* is ready with "M122" in state(s) 0
Telnet is idle in state(s) 0
File* is doing "G1 X102.293999 Y192.054993 E0.178150" 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.95ms; 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
=== CAN ===
Messages sent 588, longest wait 0ms for type 0
=== Linux interface ===
State: 0, failed transfers: 0
Last transfer: 19ms ago
RX/TX seq numbers: 4669/4671
SPI underruns 0, overruns 0
Number of disconnects: 0
Buffer RX/TX: 3696/1128-4080
=== Duet Control Server ===
Duet Control Server v3.1.1
File:
Buffered code: G1 X102.294 Y192.055 E0.17815
Buffered code: G1 X100.964 Y188.823 E0.16215
Buffered code: G1 X99.743 Y185.547 E0.16218
Buffered code: G1 X98.556 Y182.005 E0.17331
Buffered code: G1 X97.531 Y178.554 E0.16700
Buffered code: G1 X96.647 Y175.165 E0.16248
Buffered code: G1 X95.826 Y171.521 E0.17331
Buffered code: G1 X95.157 Y167.978 E0.16730
Buffered code: G1 X94.623 Y164.523 E0.16218
Buffered code: G1 X94.178 Y160.820 E0.17301
Buffered code: G1 X93.865 Y157.103 E0.17304
Buffered code: G1 X93.688 Y153.606 E0.16246
Buffered code: G1 X93.627 Y150.000 E0.16730
Buffered code: G1 X93.693 Y146.271 E0.17304
Buffered code: G1 X93.872 Y142.780 E0.16216
Buffered code: G1 X94.178 Y139.187 E0.16730
Buffered code: G1 X94.623 Y135.477 E0.17334
Buffered code: G1 X95.157 Y132.023 E0.16215
Buffered code: G1 X95.806 Y128.581 E0.16248
Buffered code: G1 X96.645 Y124.841 E0.17782
Buffered code: G1 X97.529 Y121.452 E0.16248
Buffered code: G1 X98.523 Y118.101 E0.16218
Buffered code: G1 X99.703 Y114.563 E0.17301
Buffered code: G1 X101.008 Y111.069 E0.17304
Buffered code: G1 X102.339 Y107.837 E0.16216
Buffered code: G1 X103.778 Y104.651 E0.16218
Buffered code: G1 X105.429 Y101.300 E0.17331
Buffered code: G1 X107.134 Y98.122 E0.16730
Buffered code: G1 X108.890 Y95.099 E0.16218
Buffered code: G1 X110.873 Y91.933 E0.17331
Buffered code: G1 X112.893 Y88.946 E0.16730
Buffered code: G1 X114.911 Y86.166 E0.15940
==> 1532 bytes
Code buffer space: 2568
Configured SPI speed: 8000000 Hz
Full transfers per second: 31.71
File /opt/dsf/sd/gcodes/SPOOL/PLA_custom_B_2_215C.gcode is selected, processing
- Ethernet -
-
@dc42 Looks like the problem is with the Duet 3. M122 in prior post.
-
@Stephen6309, thanks for your report. Please try release 3.2beta2 which we plan to release later today.
Duet WiFi hardware designer and firmware engineer
Please do not ask me for Duet support via PM or email, use the forum
http://www.escher3d.com, https://miscsolutions.wordpress.com -
@dc42 I've installed it. It's currently printing, but problem usually has taken a few days to show up. Will update later this week.
-
@dc42 So far, it's working fine. Had to change to my BLTouch v3.1 from the first original version.
-
@Stephen6309 said in Duet 3 6hc + SBC just stops printing:
@dc42 So far, it's working fine. Had to change to my BLTouch v3.1 from the first original version.
Thanks. What was the problem with the older BLTouch?
Duet WiFi hardware designer and firmware engineer
Please do not ask me for Duet support via PM or email, use the forum
http://www.escher3d.com, https://miscsolutions.wordpress.com -
@dc42 It would do a double tap on the bed. It would do it when homing Z, and doing the G29.
Watching it do it, the moment it would hit the bed, it would fully retract, but it would imediately redeploy and trigger again.
Watching the 3.1, it would trigger and not rectract completely, the full retract was delayed,
