Duet3D 6HC + Toolboard missing filament on curves

evomotors

I had exactly the same issue with extruder motor connected to tool board, but not when it's connected directly to Duet3. Of course Duet3d guys was fast to blame my extruder. But it's working flawlessly when connected directly to Duet3. I been told by @dc42 that 3.2 will fix the issue. But it didn't fix it.

I didn't get this problem solved, so I had to eliminate my tool board from the printer. Now I have exactly the same Issue with extruder connected to 3CH expansion board.

Phaedrux

@jbarros @evomotors They may have identified the issue and hope to have something to test soon. Thanks for your patience.

dc42

I think these problems are very likely caused by CAN clock sync jitter. I have been working all day to resolve this, and I have early 3.3betas builds of main and expansion board firmwares that resolve this jitter. I have one further related issue to investigate before I release an official beta.

jbarros

Thank you for your responses, I'll wait for the new firmwares

Luke'sLaboratory

@dc42 Thank you - I've been perplexed by these random gaps as well, but was assuming it was a mechanical restriction/poor slicing

jbarros

I have made 2 prints with the new firmware but not yet with the speeds as high as when I originally reported the issue, which I will do tomorrow.

Nevertheless here is M122 of apparently good prints:

M122
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.3beta running on Duet 3 MB6HC v1.01 or later (standalone mode)
Board ID: 08DJM-956BA-NA3TJ-6J9D2-3S06S-9V8AT
Used output buffers: 10 of 40 (23 max)
=== RTOS ===
Static ram: 149772
Dynamic ram: 95952 of which 172 recycled
Never used RAM 108776, free system stack 122 words
Tasks: NETWORK(ready,240) ETHERNET(blocked,117) SENSORS(blocked,15) HEAT(blocked,274) CanReceiv(blocked,857) CanSender(blocked,339) CanClock(blocked,326) TMC(blocked,16) MAIN(running,921) IDLE(ready,19)
Owned mutexes:
=== Platform ===
Last reset 12:27:16 ago, cause: software
Last software reset at 2021-01-11 21:46, reason: User, GCodes spinning, available RAM 114916, slot 1
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0044a000 BFAR 0x00000000 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x10
Aux0 errors 0,0,0
Aux1 errors 0,0,0
MCU temperature: min 24.5, current 31.1, max 34.7
Supply voltage: min 23.9, current 24.1, max 24.3, under voltage events: 0, over voltage events: 0, power good: yes
12V rail voltage: min 12.1, current 12.2, max 12.2, under voltage events: 0
Driver 0: position 27600, standstill, reads 31400, writes 12 timeouts 0, SG min/max 0/1023
Driver 1: position -19600, standstill, reads 31400, writes 12 timeouts 0, SG min/max 0/1023
Driver 2: position 37631, standstill, reads 31400, writes 12 timeouts 0, SG min/max 0/1023
Driver 3: position 0, standstill, reads 31399, writes 12 timeouts 0, SG min/max 0/1023
Driver 4: position 0, standstill, reads 31411, writes 0 timeouts 0, SG min/max not available
Driver 5: position 0, standstill, reads 31400, writes 12 timeouts 0, SG min/max 0/1023
Date/time: 2021-01-16 23:33:04
Slowest loop: 85.51ms; fastest: 0.03ms
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 25.0MBytes/sec
SD card longest read time 3.2ms, write time 647.8ms, max retries 0
=== Move ===
DMs created 125, maxWait 14858111ms, bed compensation in use: mesh, comp offset 0.000
=== MainDDARing ===
Scheduled moves 141744, completed moves 141744, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 4], CDDA state -1
=== 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.2
Heater 1 is on, I-accum = 0.0
=== GCodes ===
Segments left: 0
Movement lock held by null
HTTP is idle 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: 709.03ms; fastest: 0.02ms
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: 1 of 8
- Ethernet -
State: active
Error counts: 0 0 1 0 0
Socket states: 5 2 2 2 2 0 0 0
=== CAN ===
Messages queued 443663, send timeouts 0, received 538919, lost 0, longest wait 3ms for reply type 6024, peak Tx sync delay 426, free buffers 48

M122 B20
Diagnostics for board 20:
Duet TOOL1LC firmware version 3.3beta (2021-01-16 08:18:31)
Bootloader ID: SAMC21 bootloader version 2.1 (2020-11-03b2)
Never used RAM 3900, free system stack 45 words
HEAT 86 CanAsync 87 CanRecv 81 TMC 56 MAIN 203 AIN 62
Last reset 12:19:33 ago, cause: software
Last software reset at 2020-11-30 00:59, reason: HardFault, available RAM 4224, slot 0
Software reset code 0x0060 ICSR 0x00000003 SP 0x200011c0 Task  Freestk 4294967295 ok
Stack: 20001014 0000000f 0001d3e3 00000000 20000928 0001757d 000184fe 01000000 00014822 0001491c 20001210 200032d8 00000020 00017d11 20004668 00000000 20001300 000086e5 00014822 20004678 0001491c 42eb80ae a5a5a5a5 a5a5a5a5 a5a5a5a5 a5a5a5a5 a5a5a5a5
Driver 0: position 12747604, 830.0 steps/mm, standstill, SG min/max 0/496, read errors 0, write errors 0, ifcnt 43, reads 32886, writes 9, timeouts 0, DMA errors 0, steps req 11749397 done 11682205
Moves scheduled 263285, completed 263285, in progress 0, hiccups 330, step errors 0
Peak sync jitter 4, peak Rx sync delay 224, resyncs 0, no step interrupt scheduled
VIN: 24.3V
MCU temperature: min 26.0C, current 39.4C, max 53.0C
Ticks since heat task active 242, ADC conversions started 44313973, completed 44313972, timed out 0
Last sensors broadcast 0x00000002 found 1 246 ticks ago, loop time 0
CAN messages queued 317958, send timeouts 0, received 463496, lost 0, free buffers 36, error reg 0

jbarros

@dc42
Here is the test with the 3.3 unofficial beta.

It's not failing in the same spot (curve left to hole) but on other layers with straight extrusion:

alt text

M122
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.3beta running on Duet 3 MB6HC v1.01 or later (standalone mode)
Board ID: 08DJM-956BA-NA3TJ-6J9D2-3S06S-9V8AT
Used output buffers: 1 of 40 (29 max)
=== RTOS ===
Static ram: 149772
Dynamic ram: 95952 of which 172 recycled
Never used RAM 108776, free system stack 122 words
Tasks: NETWORK(ready,234) ETHERNET(blocked,117) SENSORS(blocked,15) HEAT(blocked,274) CanReceiv(blocked,857) CanSender(blocked,339) CanClock(blocked,326) TMC(blocked,16) MAIN(running,921) IDLE(ready,19)
Owned mutexes:
=== Platform ===
Last reset 14:05:08 ago, cause: software
Last software reset at 2021-01-11 21:46, reason: User, GCodes spinning, available RAM 114916, slot 1
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0044a000 BFAR 0x00000000 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x10
Aux0 errors 0,0,0
Aux1 errors 0,0,0
MCU temperature: min 30.6, current 33.1, max 34.2
Supply voltage: min 24.0, current 24.1, max 24.2, under voltage events: 0, over voltage events: 0, power good: yes
12V rail voltage: min 12.1, current 12.2, max 12.2, under voltage events: 0
Driver 0: position 27600, standstill, reads 56101, writes 4 timeouts 0, SG min/max 0/1023
Driver 1: position -19600, standstill, reads 56101, writes 4 timeouts 0, SG min/max 0/1023
Driver 2: position 34591, standstill, reads 56101, writes 4 timeouts 0, SG min/max 0/1023
Driver 3: position 0, standstill, reads 56101, writes 4 timeouts 0, SG min/max 0/1023
Driver 4: position 0, standstill, reads 56104, writes 0 timeouts 0, SG min/max not available
Driver 5: position 0, standstill, reads 56101, writes 4 timeouts 0, SG min/max 0/1023
Date/time: 2021-01-17 01:10:57
Slowest loop: 698.53ms; fastest: 0.03ms
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 25.0MBytes/sec
SD card longest read time 2.4ms, write time 20.6ms, max retries 0
=== Move ===
DMs created 125, maxWait 3813194ms, bed compensation in use: mesh, comp offset 0.000
=== MainDDARing ===
Scheduled moves 58007, completed moves 58007, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 1, 0], CDDA state -1
=== 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.2
Heater 1 is on, I-accum = 0.0
=== GCodes ===
Segments left: 0
Movement lock held by null
HTTP is idle 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: 49.60ms; fastest: 0.02ms
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: 1 of 8
- Ethernet -
State: active
Error counts: 0 0 1 0 0
Socket states: 5 2 2 2 2 0 0 0
=== CAN ===
Messages queued 78269, send timeouts 0, received 70602, lost 0, longest wait 699ms for reply type 6029, peak Tx sync delay 426, free buffers 48

M122 B20
Diagnostics for board 20:
Duet TOOL1LC firmware version 3.3beta (2021-01-16 08:18:31)
Bootloader ID: SAMC21 bootloader version 2.1 (2020-11-03b2)
Never used RAM 3900, free system stack 45 words
HEAT 86 CanAsync 87 CanRecv 81 TMC 56 MAIN 203 AIN 62
Last reset 14:05:17 ago, cause: software
Last software reset at 2020-11-30 00:59, reason: HardFault, available RAM 4224, slot 0
Software reset code 0x0060 ICSR 0x00000003 SP 0x200011c0 Task  Freestk 4294967295 ok
Stack: 20001014 0000000f 0001d3e3 00000000 20000928 0001757d 000184fe 01000000 00014822 0001491c 20001210 200032d8 00000020 00017d11 20004668 00000000 20001300 000086e5 00014822 20004678 0001491c 42eb80ae a5a5a5a5 a5a5a5a5 a5a5a5a5 a5a5a5a5 a5a5a5a5
Driver 0: position 18081149, 830.0 steps/mm, standstill, SG min/max 0/496, read errors 0, write errors 0, ifcnt 45, reads 26326, writes 2, timeouts 0, DMA errors 0, steps req 5413456 done 5386063
Moves scheduled 317851, completed 317851, in progress 0, hiccups 735, step errors 0
Peak sync jitter 4, peak Rx sync delay 48846, resyncs 73, no step interrupt scheduled
VIN: 24.3V
MCU temperature: min 26.0C, current 44.8C, max 53.0C
Ticks since heat task active 133, ADC conversions started 50658111, completed 50658110, timed out 0
Last sensors broadcast 0x00000002 found 1 137 ticks ago, loop time 0
CAN messages queued 76287, send timeouts 0, received 111749, lost 133, free buffers 36, error reg 0

alankilian

Jesus that's terrible.

I know I'm not helpful, but I can express my sympathy for the problems you are experiencing.

How about trying a calibration cube (without the X,Y and Z inserts) instead of this?

jbarros

Thank you
When I repeat tests I like to maintain the same variables.
I'm saying this and I changed filament but the bottom part was printed perfectly.

Reducing speeds I can print ok, here's some proof of that and that this filament is printable

alt text
Those are 3mm holes, for scale.

dc42

@jbarros, thanks for the data. The tool board is reporting lost CAN messages, so this appears to be the same issue that @evomotors is having in the other thread. I will work on resolving this in the next few days. Please share your print file and config.g if you haven't already.

jbarros

@dc42 thank you for your work on this issue.
config.g and g-code are on the initial post.

Luke'sLaboratory

Reducing the print+retraction speeds I'm able to print w/out lost messages on 3.3 alpha. My extruders are on my 3hc expansion, and the filament depositon was the squiffy part of all of my lost prints, whether it be for some reason jamming constantly with known good settings ( I run identical extruders on different platforms w/out issues with same settings/filament) or getting the kind of gaps/curves that are shown here.

Going to run a longer, toolchanged print to see if there are still issues.

dc42

@jbarros, please try the latest unofficial 3.3beta main and expansion board firmware. It solves all the issues we are aware of except for a very slight reduction in actual vs. requested extrusion.

jbarros

@dc42 I just did a test with another part that was giving me trouble before and it looks way better (see the nut inserts on the top right).
I do notice some ringing that was not so pronounced before (see the round middle part).

I am using DAA which you say was the culprit:
M593 F50.0 ; cancel ringing at 50.0Hz

Can I assume the "fix" also reduced some of the DAA "power" ?

Phaedrux

@jbarros said in Duet3D 6HC + Toolboard missing filament on curves:

I am using DAA which you say was the culprit:
M593 F50.0 ; cancel ringing at 50.0Hz
Can I assume the "fix" also reduced some of the DAA "power" ?

May need to retune?

matt3o

ohmy I thought I was going insane until I saw this post.

I thought it was a problem with my extruder motor or the extruder itself... or the filament tensioner... I went ahead and recabled everything and twisted the CAN data wires, added ferrite bead... thanks god I saw this post before I rebuilt my printer all over again

This is just to say that I'm experiencing the same issue with a toolboard.

jbarros

@matt3o I too was going crazy for a while thinking I had slicer setting issues or something but it ended up getting worse and then I saw another thread with CAN issues on an expansion board and I started to be suspicious

You can try the beta firmware here:
https://www.dropbox.com/sh/wme9k0z86sytg33/AAAT6wrHp2eeJHK-dYoW1Um4a?dl=0
Note: you have to upgrade both 6HC and 1LC

jbarros

@Phaedrux said in Duet3D 6HC + Toolboard missing filament on curves:

@jbarros said in Duet3D 6HC + Toolboard missing filament on curves:

I am using DAA which you say was the culprit:
M593 F50.0 ; cancel ringing at 50.0Hz
Can I assume the "fix" also reduced some of the DAA "power" ?

May need to retune?

Probably will need to but didn't want added variables now

dc42

@jbarros said in Duet3D 6HC + Toolboard missing filament on curves:

Can I assume the "fix" also reduced some of the DAA "power" ?

No, the fix didn't reduce the effectiveness of DAA.

The bug was an oversight when I implemented DAA. Adding DAA meant that the deceleration of a move was no longer always the same as the acceleration; so I introduced a new deceleration move parameter, and I went through the code changing "acceleration" to "deceleration" where required. At that time, CAN support was experimental and not released. Unfortunately I was using a standard build configuration without CAN support when I made the change for DAA, so the "find all references" command in Eclipse didn't pick up a reference to "acceleration" in the CAN-specific code that should have been changed to "deceleration".

jbarros

@dc42 said in Duet3D 6HC + Toolboard missing filament on curves:

@jbarros, please try the latest unofficial 3.3beta main and expansion board firmware. It solves all the issues we are aware of except for a very slight reduction in actual vs. requested extrusion.

Per your previous comments, rounding issues?
Do you know the loss % and do you believe it's fixable?