Duet 3 6hc + SBC just stops printing
-
Another one for @chrishamm
-
@Phaedrux No errors. Pause button just gets the busy symbol. Also, unable to move any of the axes.
A few days ago, it worked fine.It has a Raspberry Pi 4 4GB.
; Configuration file for Duet 3 (firmware version 3)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v3.1.4 on Tue Jul 21 2020 16:28:37 GMT-0400 (Eastern Daylight Time); General preferences
G90 ; send absolute coordinates...
M83 ; ...but relative extruder moves
M550 P"raspberrypi" ; set printer name
M669 K1 ; select CoreXY mode; Drives
M569 P0.0 S0 ; physical drive 0.0 goes backwards
M569 P0.1 S0 ; physical drive 0.1 goes backwards
M569 P0.2 S1 ; physical drive 0.2 goes forwards
M569 P0.3 S1 ; physical drive 0.3 goes forwards
M584 X0.0 Y0.1 Z0.2 E0.3 ; set drive mapping
M350 X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation
M92 X80.00 Y80.00 Z800.00 E417.00 ; set steps per mm
M566 X2500.00 Y2500.00 Z12.00 E120.00 ; set maximum instantaneous speed changes (mm/min)
M203 X12000.00 Y12000.00 Z720.00 E7200.00 ; set maximum speeds (mm/min)
M201 X1000.00 Y1000.00 Z250.00 E250.00 ; set accelerations (mm/s^2)
M906 X800 Y800 Z800 E800 I30 ; 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 X400 Y300 Z200 S0 ; set axis maxima; Endstops
M574 X1 S1 P"io1.in" ; configure active-high endstop for low end on X via pin io1.in
M574 Y1 S1 P"io2.in" ; configure active-high endstop for low end on Y via pin io2.in
M574 Z1 S2 ; configure Z-probe endstop for low end on Z; Z-Probe
M558 P5 C"^io3.in" H5 F120 T6000 B1 ; set Z probe type to switch and the dive height + speeds
G31 P500 X0 Y-55 Z0 ; set Z probe trigger value, offset and trigger height
M557 X10:400 Y10:300 S50 ; define mesh grid; Heaters
M308 S0 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 B0 S1.00 ; disable 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
M308 S1 P"temp1" Y"thermistor" T100000 B4388 ; 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; Fans
M950 F0 C"out7" Q500 ; create fan 0 on pin out7 and set its frequency
M106 P0 S0 H-1 ; set fan 0 value. Thermostatic control is turned off
M950 F1 C"out8" Q500 ; create fan 1 on pin out8 and set its frequency
M106 P1 S1 H1 T45 ; set fan 1 value. Thermostatic control is turned on; Tools
M563 P0 D0 H1 F-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
;M572 D0 S0.02 ; Pressure advance
M207 S1.5 F6000 R0 Z0.03 ; firmware retraction
M376 H5 ; taper bed compensation
M593 F23 ; cancel ringing at 23Hz; Miscellaneous
M501 ; load saved parameters from non-volatile memory
M911 S10 R11 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000" ; set voltage thresholds and actions to run on power loss
T0 ; select first tool -
@Phaedrux Attempted to do debug: the first command never finishes.
I have a Pi 0 W coming tomorrow, so I'll try that.
-
I'll be surprised if the Pi 0 W can handle it well, but worth trying I suppose.
-
@Phaedrux PI0W didn't work, would not bring up DWC. The Pi0W sure is slow.
I upgraded my Duet 2 to 3.11, no problems there.
It'll be several days before I can try again. I'll redo the raspberry OS on the Pi4. One thing, 5ghz wifi won't connect, but 2.4ghz does. If the new install doesn't work, I'll find a long enough ethernet cable and try the direct connection.
-
Setup the pi4 with the new os, install the duet stuff. Left the pi4 hanging off the side and this morning it started to print. Currently doing the first layer. Ain't computers fun.
Will have wait a few days to see it stays working.
-
Fired up the printer today, so far printed twice with no problem.
The OS on the pi4 must have been messed up when I was powering the pi touchscreen via the dotstar connector. The pi4 was showing the low voltage lightning on the screen. Now powering from a 5vdc Meanwell.
-
Today, it's once again dying on the second leg of the skirt.
Wrapped the ribbon cable in aluminum foil and grounded it. No change. Disconnected the pi touchscreen.
It appears my pi4 stops talking to the duet 3. Emergency stop restores the ability to send gcode.
Going to see if the 2020-07-20-DuetPi.img lasts longer. It's current printing. Now, will it keep working over the next few days. Ribbon cable still shielded. Didn't do the updates yet.
Next time I'll try the direct connection.
-
@Stephen6309 said in Duet 3 6hc + SBC just stops printing:
Today, it's once again dying on the second leg of the skirt.
Wrapped the ribbon cable in aluminum foil and grounded it. No change. Disconnected the pi touchscreen.
It appears my pi4 stops talking to the duet 3. Emergency stop restores the ability to send gcode.
Going to see if the 2020-07-20-DuetPi.img lasts longer. It's current printing. Now, will it keep working over the next few days. Ribbon cable still shielded. Didn't do the updates yet.
Next time I'll try the direct connection.
I have been using a Pi-3B+ on my duet 3 Unit with NO issues, maybe its a Pi-4 thing, latest is not always best...
-
Can you provide M122 results after the stop?
Or enable the monitoring I linked above?
-
@Phaedrux I will try the debug mode again, if it does it again.
Running a similation of a print has worked fine.
-
@Phaedrux 2020-07-20-DuetPi.img smae thing happens the next day. Tempertures still update, can set them. Simulating print time was completed successfully.
Emergency stop restores movement.Will try to set debug. Stop the servers, and the first command in PuTTy:
sudo /opt/dsf/bin/DuetControlServer -l debug
Stops after showing: Updated key volumesVNC Connect will not connect, via IP or CXY-MSv1.local.
Used Advanced IP Scanner to verify IP.
Connected the touchscreen: desktop screen garbled.The M122 is below.
Did the update and upgrade. That took a while. The update let me set the resolution for the touchscreen. Started print via touchscreen. Stopped again.
Where is the terminal in 2020-07-20-DuetPi.img?
Ther M122 doesn't change, except for the bytes transmitted/received.
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: 162844 of which 44 recycled
Exception stack ram used: 520
Never used ram: 75204
Tasks: NETWORK(ready,1972) HEAT(blocked,1188) CanReceiv(suspended,3820) CanSender(suspended,1420) CanClock(blocked,1436) TMC(blocked,68) MAIN(running,4952) IDLE(ready,76)
Owned mutexes:
=== Platform ===
Last reset 00:44:07 ago, cause: power up
Last software reset at 2020-08-22 15:28, reason: User, spinning module LinuxInterface, available RAM 77008 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 24.4, current 36.1, max 37.5
Supply voltage: min 23.9, current 24.2, 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: standstill, reads 55236, writes 17 timeouts 0, SG min/max 0/253
Driver 1: standstill, reads 55236, writes 17 timeouts 0, SG min/max 0/956
Driver 2: standstill, reads 55237, writes 17 timeouts 0, SG min/max 0/1023
Driver 3: standstill, reads 55237, writes 17 timeouts 0, SG min/max 0/144
Driver 4: standstill, reads 55244, writes 11 timeouts 0, SG min/max 0/0
Driver 5: standstill, reads 55244, writes 11 timeouts 0, SG min/max 0/0
Date/time: 2020-08-23 14:11:55
Slowest loop: 4.95ms; 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: 281, MinFreeDm: 281, MaxWait: 454488ms
Bed compensation in use: mesh, comp offset 0.000
=== MainDDARing ===
Scheduled moves: 81, completed moves: 45, 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.3
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 X217.895996 Y52.673000 E4.612160" 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.82ms; 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: disabled
Error counts: 0 0 0 0 0
Socket states: 0 0 0 0 0 0 0 0
=== CAN ===
Messages sent 10514, longest wait 0ms for type 0
=== Linux interface ===
State: 0, failed transfers: 0
Last transfer: 17ms ago
RX/TX seq numbers: 18425/18426
SPI underruns 0, overruns 0
Number of disconnects: 0
Buffer RX/TX: 3548/984-4076
=== Duet Control Server ===
Duet Control Server v3.1.1
File:
Buffered code: G1 X217.896 Y52.673 E4.61216
Buffered code: G1 X218.739 Y51.836 E0.06141
Buffered code: G1 X220.019 Y50.790 E0.08550
Buffered code: G1 X221.406 Y49.902 E0.08514
Buffered code: G1 X222.512 Y49.340 E0.06417
Buffered code: G1 X224.040 Y48.744 E0.08481
Buffered code: G1 X225.634 Y48.327 E0.08515
Buffered code: G1 X226.859 Y48.133 E0.06416
Buffered code: G1 X228.509 Y48.038 E0.08547
Buffered code: G1 X230.116 Y48.130 E0.08319
Buffered code: G1 X231.213 Y48.294 E0.05735
Buffered code: G1 X232.297 Y48.546 E0.05755
Buffered code: G1 X233.827 Y49.053 E0.08332
Buffered code: G1 X234.844 Y49.503 E0.05755
Buffered code: G1 X236.252 Y50.288 E0.08331
Buffered code: G1 X237.164 Y50.919 E0.05735
Buffered code: G1 X238.389 Y51.943 E0.08255
Buffered code: G1 X239.180 Y52.747 E0.05833
Buffered code: G1 X240.199 Y53.992 E0.08319
Buffered code: G1 X240.819 Y54.920 E0.05768
Buffered code: G1 X241.581 Y56.323 E0.08255
Buffered code: G1 X242.018 Y57.355 E0.05800
Buffered code: G1 X242.506 Y58.882 E0.08287
Buffered code: G1 X242.741 Y59.966 E0.05735
Buffered code: G1 X242.931 Y61.507 E0.08028
Buffered code: G1 X242.966 Y237.499 E9.09980
Buffered code: G1 X242.873 Y239.115 E0.08374
Buffered code: G1 X242.703 Y240.243 E0.05898
Buffered code: G1 X242.306 Y241.812 E0.08365
Buffered code: G1 X241.890 Y242.968 E0.06355
Buffered code: G1 X241.238 Y244.352 E0.07911
Buffered code: G1 X240.607 Y245.411 E0.06371
==> 1512 bytes
Code buffer space: 2572
Configured SPI speed: 8000000 Hz
Full transfers per second: 1.32
File /opt/dsf/sd/gcodes/PETG_Spacer3mm20mmX8.gcode is selected, processing
- Ethernet -
-
Pulled the 5vdc to Pi jumper and tried powering the pi4 from a wall wart, no change.
-
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
