Mid print stalls on new Duet3 printer

Olby

Switch to 3.2-beta3 and increase event logging M929 to debug level. Will start a longer print tomorrow to see if i can reproduce the issue. Anything else I can do to get more data to help pinpoint the issue?

Phaedrux

@Olby said in Mid print stalls on new Duet3 printer:

Anything else I can do to get more data to help pinpoint the issue?

If you're still using the SBC you can get some additional info captured with this: https://duet3d.dozuki.com/Wiki/Getting_Started_With_Duet_3#Section_Monitoring_optional

Otherwise capturing M122 afterwards is helpful to see the error codes.

Olby

Turns out that 3.2-beta3 will make this a lot easier to track down the skipped steps that I thought i had worked around. Now I can easily get it to skip steps with just a couple of quick moves.

Same printer, same gcode and 3.1 no missed steps for 9h+. 3.2-beta3 missed steps first layer, missed step after 5 rapid moves and also manage to break the z switch after what i think are missed steps on z. The bed was skewed as if one of my 3 z motors skipped.

I will try to reproduce it on individual axis when i get time after work. Thinking rapid diagonals to test each X/Y individually and rapid z with a dial gauge near each z-motor.

TypQxQ

Try turning off all bed compensations with M561. I am having similar problems with it enabled.

Olby

@TypQxQ Thanks, disabling the bed compensation solved my X/Y skipping issue. Strange that things got worse after the update to 32-beta3, I use the same settings and same bed mesh.

So one down, will start a long print tomorrow to see if I can reproduce the stall with the new firmware.

The version update also brought a new issue. Something has changed since 3.1 that breaks my Z-homing from time to time.

	; Home Z Axis
	M561 ; Disable any Mesh Bed Compensation
	G90 G1 X150 Y150 F10000 ; Move to the center of the bed
	M558 F500 ; Set the probing speed
	G30
	M558 F50 ; Set a slower probing speed
	G30
	G32      ; Run 3-point bed calibration defined in bed.g
	G29 S1   ; Enable Mesh Bed Compensation
	G1 Z5
	G1 X50 Y50 F10000

It is as if the center probe ends with the bed too high and drags the z limit switch against the be so i snaps. Not always but i'm on my second broken switch today after max 10 homings. Never got that behaviour in the old version. (And this is before the bed mesh is applied)

TypQxQ

@Olby Try setting all parameters of M558 each time. I have experienced that it sometimes looses parameters when only setting one of them. Try like this:

M558 P8 C"0.io3.in" F500 H5 T24000 A2 S0.02 ; Set the probing speed
G30
M558 P8 C"0.io3.in" F50 H5 T24000 A2 S0.02 ; Set a slower probing speed

You can also put "G31 Z-1", if you haven't already, in the start to add an extra mm to the switch. You will have to add 1mm to your Z tool offsets until you recalibrate them.

Olby

Updated to 3.2-beta3+3-ch and the skipping issues are gone all works with bed mesh compensation activated.

Will run some long prints this weekend to see if i can reproduce the mid print stop with 100% complete status.

Olby

@TypQxQ Will test that as soon as I soldered on a new switch, thanks.

Olby

Managed to reproduce the mid print halt again. This time with 3.2-beta3.2. Same behaviour ui reports 100% complete but there are lots of gcode in the buffer.

m122
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.2-beta3.2 running on Duet 3 MB6HC v0.6 or 1.0 (SBC mode)
Board ID: 08DJM-956L2-G43S4-6J9DD-3SJ6S-TB66H
Used output buffers: 1 of 40 (14 max)
=== RTOS ===
Static ram: 122236
Dynamic ram: 139504 of which 68 recycled
Never used RAM 130384, free system stack 122 words
Tasks: Linux(ready,79) HEAT(blocked,296) CanReceiv(blocked,869) CanSender(blocked,335) CanClock(blocked,352) TMC(blocked,20) MAIN(running,669) IDLE(ready,19)
Owned mutexes: HTTP(MAIN)
=== Platform ===
Last reset 07:13:50 ago, cause: power up
Last software reset at 2020-11-21 17:24, reason: User, GCodes spinning, available RAM 130384, slot 2
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00400000 BFAR 0x00000000 SP 0xffffffff Task Linu
Error status: 0x00
MCU temperature: min 8.1, current 26.4, max 26.5
Supply voltage: min 23.8, current 24.1, max 24.2, under voltage events: 0, over voltage events: 0, power good: yes
12V rail voltage: min 12.2, current 12.3, max 12.4, under voltage events: 0
Driver 0: position 25039, standstill, reads 22878, writes 30 timeouts 0, SG min/max 0/1023
Driver 1: position -526, standstill, reads 22878, writes 30 timeouts 0, SG min/max 0/1023
Driver 2: position 391749, standstill, reads 22883, writes 26 timeouts 0, SG min/max 0/73
Driver 3: position 0, standstill, reads 22879, writes 31 timeouts 0, SG min/max 0/1023
Driver 4: position 0, standstill, reads 22880, writes 31 timeouts 0, SG min/max 0/1023
Driver 5: position 0, standstill, reads 22881, writes 30 timeouts 0, SG min/max 0/1023
Date/time: 2020-11-26 04:21:46
Slowest loop: 261.09ms; fastest: 0.08ms
=== 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: 332, MaxWait: 4966114ms
Bed compensation in use: mesh, comp offset 0.124
=== MainDDARing ===
Scheduled moves 152108, completed moves 152108, StepErrors 0, LaErrors 0, Underruns [0, 0, 3], CDDA state -1
=== AuxDDARing ===
Scheduled moves 0, completed moves 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, chamberHeaters = -1 -1 -1 -1
=== 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 sent 589618, send timeouts 589618, longest wait 1ms for type 6018, free CAN buffers 47
=== SBC interface ===
State: 0, failed transfers: 0
Last transfer: 19ms ago
RX/TX seq numbers: 58211/58212
SPI underruns 0, overruns 0
Number of disconnects: 1, IAP RAM available 0x20a08
Buffer RX/TX: 0/0-0
=== Duet Control Server ===
Duet Control Server v3.2.0-beta3
File:
Buffered code: G1 X69.704 Y98.334 E0.02468
Buffered code: G1 X69.880 Y98.698 E0.01369
Buffered code: G1 X70.865 Y99.790 E0.04976
Buffered code: G1 X71.138 Y100.518 E0.02632
Buffered code: G1 X71.094 Y101.246 E0.02468
Buffered code: G1 X70.918 Y101.610 E0.01369
Buffered code: G1 X69.933 Y102.702 E0.04976
Buffered code: G1 X69.661 Y103.430 E0.02632
Buffered code: G1 X69.704 Y104.158 E0.02468
Buffered code: G1 X69.880 Y104.522 E0.01369
Buffered code: G1 X70.865 Y105.614 E0.04976
Buffered code: G1 X71.138 Y106.342 E0.02632
Buffered code: G1 X71.094 Y107.070 E0.02468
Buffered code: G1 X70.918 Y107.434 E0.01369
Buffered code: G1 X69.933 Y108.525 E0.04976
Buffered code: G1 X69.661 Y109.253 E0.02632
Buffered code: G1 X69.704 Y109.981 E0.02468
Buffered code: G1 X69.880 Y110.345 E0.01369
Buffered code: G1 X70.073 Y110.567 E0.00995
Buffered code: G1 X67.558 Y110.567 E0.08513
Buffered code: G1 X67.022 Y109.981 E0.02689
Buffered code: G1 X66.749 Y109.253 E0.02632
Buffered code: G1 X66.792 Y108.525 E0.02468
Buffered code: G1 X66.968 Y108.162 E0.01369
Buffered code: G1 X67.953 Y107.070 E0.04976
Buffered code: G1 X68.226 Y106.342 E0.02632
Buffered code: G1 X68.182 Y105.614 E0.02468
==> 1292 bytes
Trigger:
Finishing macro config.g, started by system
> Next stack level
Pending code: M905 P"2020-11-26" S"06:39:00"
Pending code: M905 P"2020-11-26" S"13:51:18"
Code buffer space: 4096
Configured SPI speed: 8000000 Hz
Full transfers per second: 14.03
File /opt/dsf/sd/gcodes/Part_5.gcode is selected, processing

M122 B1
Diagnostics for board 1:
Duet EXP3HC firmware version 3.2beta3.1 (2020-11-08)
Bootloader ID: not available
Never used RAM 154920, free system stack 154 words
HEAT 40 CanAsync 93 CanRecv 76 TMC 30 MAIN 334 AIN 257
Last reset 07:17:20 ago, cause: power up
Last software reset data not available
Driver 0: position 21928487, 830.0 steps/mm,  standstill, reads 31013, writes 23 timeouts 0, SG min/max 0/661
Driver 1: position 0, 830.0 steps/mm,  standstill, reads 31021, writes 18 timeouts 0, SG min/max 0/0
Driver 2: position 0, 80.0 steps/mm,  standstill, reads 31031, writes 11 timeouts 0, SG min/max 0/0
Moves scheduled 485558, completed 485558, in progress 0, hiccups 0
No step interrupt scheduled
VIN: 24.1V, V12: 12.2V
MCU temperature: min 39.0C, current 39.2C, max 39.4C
Ticks since heat task active 175, ADC conversions started 26240916, completed 26240916, timed out 0
Last sensors broadcast 0x00000000 found 0 178 ticks ago, loop time 0
Free CAN buffers: 36, messages lost 721666, duplicates 0, oos 0, busOff 0

The latest beta and a replaced crimp has solved all other issues. But this remains...

The event log is empty and i didn't run with the extra monitoring on the sbc this time.

dc42

There is a known issue with occasional print stalls when running with attached SBC. This was confirmed and fixed yesterday. The fix is in 3.2beta4, which is being tested right now.