Duet 3 6HC stuttering and not using up filament during print

Marshal

Hi all,

I am running first prints with a newly built printer.

For some reason I am running into an issue, where the printer is not moving smoothly and is not using filament.

not moving smoothly is especially visible during circles
not using filament, the extruder stepper is changing from extrusion to retract but is averaging at ~0

Giving the same gcode several tries will eventually result in a working one.
I am trying to run it down with one routine

power up printer
goto "Jobs"
select/start print
within gcode:
-- heat up of bed / tool
-- G32 for homing and tramming

From M122 (see below) i am wondering, if:

=== CAN ===
Messages queued 1976, send timeouts 0, received 4518, lost 0, longest wait 2ms for reply

is ok, due to the messages in queue?
Maybe, bad CAN connection?

Thx in advance.

System Details:

Board: Duet 3 MB6HC (MB6HC)
DSF Version: 3.2.2
Firmware: RepRapFirmware for Duet 3 MB6HC 3.2.2 (2021-02-11)

RPI 4 SBC, updates last checked today

Duet TOOL1LC firmware version 3.2 (2021-01-05)

M122:

M122
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.2.2 running on Duet 3 MB6HC v0.6 or 1.0 (SBC mode)
Board ID: 08DJM-956L2-G43S8-6J9D4-3SN6M-TU0UG
Used output buffers: 4 of 40 (10 max)
=== RTOS ===
Static ram: 149788
Dynamic ram: 62836 of which 88 recycled
Never used RAM 146120, free system stack 128 words
Tasks: Linux(ready,77) HEAT(blocked,297) CanReceiv(blocked,834) CanSender(blocked,344) CanClock(blocked,352) TMC(blocked,17) MAIN(running,720) IDLE(ready,19)
Owned mutexes: HTTP(MAIN)
=== Platform ===
Last reset 00:06:09 ago, cause: software
Last software reset at 2021-04-27 20:51, reason: User, Platform spinning, available RAM 146536, slot 1
Software reset code 0x0000 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00400000 BFAR 0x00000000 SP 0x00000000 Task Linu Freestk 0 n/a
Error status: 0x00
Aux0 errors 0,0,0
Aux1 errors 0,0,0
MCU temperature: min 40.0, current 41.1, max 42.1
Supply voltage: min 24.1, current 24.2, max 24.3, 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: position 65938, ok, reads 37397, writes 17 timeouts 0, SG min/max 0/1023
Driver 1: position 1629, standstill, reads 37397, writes 17 timeouts 0, SG min/max 0/1023
Driver 2: position 840, standstill, reads 37399, writes 17 timeouts 0, SG min/max 0/1023
Driver 3: position 0, standstill, reads 37399, writes 17 timeouts 0, SG min/max 0/439
Driver 4: position 0, standstill, reads 37399, writes 17 timeouts 0, SG min/max 0/476
Driver 5: position 0, standstill, reads 37405, writes 11 timeouts 0, SG min/max 0/0
Date/time: 2021-04-27 20:57:17
Slowest loop: 183.64ms; 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, maxWait 77883ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 1148, completed moves 1141, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state 3
=== AuxDDARing ===
Scheduled moves 0, completed moves 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, chamberHeaters = -1 -1 -1 -1
Heater 0 is on, I-accum = 0.1
Heater 1 is on, I-accum = 0.0
=== GCodes ===
Segments left: 1
Movement lock held by null
HTTP* is doing "M122" in state(s) 0
Telnet is idle in state(s) 0
File* is doing "G1 X198.794006 Y186.348999 E0.581140" 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 1976, send timeouts 0, received 4518, lost 0, longest wait 2ms for reply type 6049, free buffers 48
=== SBC interface ===
State: 4, failed transfers: 0
Last transfer: 3ms ago
RX/TX seq numbers: 13507/13507
SPI underruns 0, overruns 0
Number of disconnects: 0, IAP RAM available 0x2c85c
Buffer RX/TX: 1296/2808-0
=== Duet Control Server ===
Duet Control Server v3.2.2
File:
Buffered code: G1 X198.794 Y186.349 E0.58114
Buffered code: G1 X199.36 Y186.349 E0.01883
Buffered code: G1 X211.149 Y198.138 E0.55452
Buffered code: G1 X211.149 Y197.572 E0.01883
Buffered code: G1 X199.925 Y186.349 E0.52792
Buffered code: G1 X200.491 Y186.349 E0.01883
Buffered code: G1 X211.149 Y197.007 E0.50132
Buffered code: G1 X211.149 Y196.441 E0.01883
Buffered code: G1 X201.057 Y186.349 E0.4747
Buffered code: G1 X201.623 Y186.349 E0.01883
Buffered code: G1 X211.149 Y195.875 E0.44807
Buffered code: G1 X211.149 Y195.309 E0.01883
Buffered code: G1 X202.188 Y186.349 E0.42147
Buffered code: G1 X202.754 Y186.349 E0.01883
Buffered code: G1 X211.149 Y194.744 E0.39488
Buffered code: G1 X211.149 Y194.178 E0.01883
Buffered code: G1 X203.32 Y186.349 E0.36825
Buffered code: G1 X203.885 Y186.349 E0.01879
Buffered code: G1 X211.149 Y193.612 E0.34165
Buffered code: G1 X211.149 Y193.047 E0.01879
Buffered code: G1 X204.451 Y186.349 E0.31505
Buffered code: G1 X205.017 Y186.349 E0.01883
Buffered code: G1 X211.149 Y192.481 E0.28843
Buffered code: G1 X211.149 Y191.915 E0.01883
Buffered code: G1 X205.582 Y186.349 E0.26183
Buffered code: G1 X206.148 Y186.349 E0.01883
Buffered code: G1 X211.149 Y191.35 E0.23523
Buffered code: G1 X211.149 Y190.784 E0.01883
Buffered code: G1 X206.714 Y186.349 E0.20861
Buffered code: G1 X207.279 Y186.349 E0.01879
Buffered code: G1 X211.149 Y190.218 E0.18201
Buffered code: G1 X211.149 Y189.653 E0.01879
==> 1520 bytes
Code buffer space: 1288
Configured SPI speed: 8000000 Hz
Full transfers per second: 36.75
Maximum length of RX/TX data transfers: 4454/1552
File /opt/dsf/sd/gcodes/TXXPRO_CHEPCalibrationCube.gcode is selected, processing

M122 B20

M122 B20
Diagnostics for board 20:
Duet TOOL1LC firmware version 3.2 (2021-01-05)
Bootloader ID: not available
Never used RAM 4040, free system stack 50 words
HEAT 86 CanAsync 85 CanRecv 83 TMC 54 MAIN 216 AIN 64
Last reset 00:44:57 ago, cause: software
Last software reset data not available
Driver 0: position -9956, 430.1 steps/mm, ok, SG min/max 0/16, read errors 0, write errors 1, ifcnt 34, reads 37840, writes 21, timeouts 0, DMA errors 0
Moves scheduled 7866, completed 7865, in progress 1, hiccups 0
Next step interrupt due in 2517 ticks, enabled
VIN: 23.9V
MCU temperature: min 41.2C, current 51.3C, max 51.5C
Ticks since heat task active 211, ADC conversions started 2686474, completed 2686473, timed out 0
Last sensors broadcast 0x00000002 found 1 215 ticks ago, loop time 0
CAN messages queued 32597, send timeouts 0, received 32342, lost 0, free buffers 36

Screenshot DWC:

Phaedrux

@marshal said in Duet 3 6HC stuttering and not using up filament during print:

Duet TOOL1LC firmware version 3.2 (2021-01-05)

Looks like your tool board firmware is out of sync with the mainboard. Try sending M997 B20 to initiate the firmware update on the tool board.

JamesM

Are you set to relative extrusion in your slicer?

Marshal

@phaedrux: my bad, i have changed the LC1 due to a bad resitstor, but didn't confirm the firmware ...

M122 B20
Diagnostics for board 20:
Duet TOOL1LC firmware version 3.2.2 (2021-02-11)
Bootloader ID: not available
Never used RAM 4108, free system stack 94 words
HEAT 90 CanAsync 89 CanRecv 83 TMC 56 MAIN 216 AIN 64
Last reset 00:00:16 ago, cause: software
Last software reset data not available
Driver 0: position 0, 430.1 steps/mm, standstill, SG min/max 0/0, read errors 0, write errors 1, ifcnt 23, reads 8021, writes 11, timeouts 0, DMA errors 0
Moves scheduled 0, completed 0, in progress 0, hiccups 0
No step interrupt scheduled
VIN: 24.3V
MCU temperature: min 39.1C, current 39.2C, max 39.3C
Ticks since heat task active 97, ADC conversions started 16060, completed 16059, timed out 0
Last sensors broadcast 0x00000002 found 1 101 ticks ago, loop time 0
CAN messages queued 122, send timeouts 0, received 149, lost 0, free buffers 36

I will test soon.

@JamesM: M83 is called before from job to run.

;FLAVOR:RepRap
;TIME:1876
;Filament used: 0.562977m
;Layer height: 0.2
;MINX:177.567
;MINY:181.574
;MINZ:0.125
;MAXX:225.933
;MAXY:211.149
;MAXZ:52.925
;Generated with Cura_SteamEngine 4.9.0
T0
M190 S70
M104 S240
M109 S240
M82 ;absolute extrusion mode
G32
M83 ;relative extrusion mode
G1 F2400 E-2
;LAYER_COUNT:265
;LAYER:0
M107
G0 F1800 X180.77 Y185.898 Z0.125
;TYPE:SKIRT
G1 F2400 E2
G1 F1200 X181.549 Y185.164 E0.04005
G1 X181.772 Y184.974 E0.01096
.
.
.

dc42

@marshal you may wish to upgrade to firmware 3.3beta3. This addresses issues with using CAN-connected expansion boards when there are a lot of very small movements.

Marshal

Hi,

i continued testing this evening,

Upgrading Toolboard to 3.2.2 (all system 3.2.2) --> issue remains
Upgrading all to 3.3beta3 --> issue remains

Currently i am using a 3DTouch (BLTouch clone), with 3.3beta3 i had some events, where probe was not deployed, or was triggered before touching bed. Which seemed more an issue of the sensor after the previous "touch" than anything else.

I have extended retractprobe.g
from:

 M280 P10 S90

to:

M280 P10 S90
G4 P200
M280 P10 S160

I have done 3 test prints in a row now, no issue yet.
Maybe the sensor was putting noise on Toolboar.io0.in?

More prints will tell if it is fixed like this. Maybe a BLTouch will replace the 3DTouch soon.