Duet 3 + Tool Board Extruder/Retraction Issue

evomotors

My hardware:
Duet3 board, Tool distribution board, Tool board and RPi4. I'm running latest released firmware.

After about month long debugging my random inconsistent extrusions (replacing motors, heater blocks, heaters, nozzles even complete extruder replacement) , I temporary connected my extruder motor to main board and I can say inconsistent extrusion issue has disappeared.

TolBoard issue.jpg

I tried Firmware retraction and Slicer retraction, firmware refraction effect is worst.
My retraction settings: Distance 0.6, Speed 7mm/s . This issue is less pronounced when retraction is not used.

As you see on the picture when extruder motor is connected to toll, it generates blobs(over extruding) and parts on some layers are missing (under extruding)

Defect in firmware of defective board?

evomotors

Another image

dc42

If you are running tool board firmware 3.1, then it could be that you are getting hiccups on the tool board (which you can check by doing a M122 report for the tool board). If that is the reason, then upgrading the tool board firmware to 3.2beta1 should fix it.

evomotors

@dc42 said in Duet 3 + Tool Board Extruder/Retraction Issue:

If you are running tool board firmware 3.1, then it could be that you are getting hiccups on the tool board (which you can check by doing a M122 report for the tool board). If that is the reason, then upgrading the tool board firmware to 3.2beta1 should fix it.

It looks to me that it's retracting, but retracting too late in the game. this could explain the blobs at the end of the line and under retractions on the middle of line. Tool Board does reports hiccups constantly.

I will gladly upgrade the firmware to the latest beta if I can do it safely from the DWC. If it fails, I would most likely have issues with recovery.

evomotors

@dc42 said in Duet 3 + Tool Board Extruder/Retraction Issue:

If you are running tool board firmware 3.1, then it could be that you are getting hiccups on the tool board (which you can check by doing a M122 report for the tool board). If that is the reason, then upgrading the tool board firmware to 3.2beta1 should fix it.

Why so many blocked and suspended CAN bus messages?

Tasks: NETWORK(ready,1972) HEAT(blocked,1088) CanReceiv(suspended,3388) CanSender(suspended,1392) CanClock(blocked,1436)

Phaedrux

In future can you copy and paste the text of the M122 rather than a screen shot?

evomotors

@Phaedrux said in Duet 3 + Tool Board Extruder/Retraction Issue:

In future can you copy and paste the text of the M122 rather than a screen shot?

Sorry, here we go.

10/17/2020, 10:50:39 AM	M122 B121
Diagnostics for board 121:
Board TOOL1LC firmware 3.1.0 (2020-05-15b1)
Never used RAM 8.4Kb, max stack 684b
HEAT 640 CanAsync 1392 CanRecv 1380 TMC 156 AIN 524 MAIN 2284
Last reset 96:28:07 ago, cause: software
Driver 0: open-load-A open-load-B, SG min/max 0/16, read errors 0, write errors 0, ifcount 54, reads 47102, writes 0, timeouts 0, DMA errors 0, failedOp 0xff
Moves scheduled 3079196, completed 3079194, hiccups 7539
VIN: 24.0V
MCU temperature: min 44.0C, current 56.2C, max 65.1C
Ticks since heat task active 66, ADC conversions started 347266771, completed 347266770, timed out 0
Last sensors broadcast 00000002 found 1 69 ticks ago
Free CAN buffers: 36
NVM user row b1d088a9 fffff8bb 20002a18 b
TSENS 001602 GAIN 014ffc OFFS 00273f CAL 1f2a
10/17/2020, 10:50:30 AM	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-6JKDL-3SJ6L-1802G
Used output buffers: 1 of 40 (22 max)
=== RTOS ===
Static ram: 154604
Dynamic ram: 162928 of which 140 recycled
Exception stack ram used: 552
Never used ram: 74992
Tasks: NETWORK(ready,1972) HEAT(blocked,1088) CanReceiv(suspended,3388) CanSender(suspended,1392) CanClock(blocked,1436) TMC(blocked,60) MAIN(running,2672) IDLE(ready,76)
Owned mutexes:
=== Platform ===
Last reset 96:27:46 ago, cause: software
Last software reset at 2020-10-13 15:22, reason: User, spinning module LinuxInterface, available RAM 75056 bytes (slot 1)
Software reset code 0x0010 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0444a000 BFAR 0x00000000 SP 0xffffffff Task MAIN
Error status: 0
MCU temperature: min 43.3, current 44.6, max 45.6
Supply voltage: min 23.7, current 23.8, max 24.0, 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: ok, reads 59467, writes 0 timeouts 0, SG min/max 0/1023
Driver 1: ok, reads 59467, writes 0 timeouts 0, SG min/max 0/1023
Driver 2: ok, reads 59467, writes 0 timeouts 0, SG min/max 0/1023
Driver 3: ok, reads 59467, writes 0 timeouts 0, SG min/max 0/1023
Driver 4: ok, reads 59467, writes 0 timeouts 0, SG min/max 0/1023
Driver 5: ok, reads 59468, writes 0 timeouts 0, SG min/max 0/242
Date/time: 2020-10-17 15:50:17
Slowest loop: 20.33ms; fastest: 0.21ms
=== 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: 368, MinFreeDm: 336, MaxWait: 0ms
Bed compensation in use: mesh, comp offset 0.000
=== MainDDARing ===
Scheduled moves: 1176142, completed moves: 1176118, 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.2
Heater 1 is on, I-accum = 0.0
=== 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 X202.007996 Y218.643997 E6.881300" 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.72ms; 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 1170785, longest wait 9ms for type 6024
=== Linux interface ===
State: 0, failed transfers: 0
Last transfer: 20ms ago
RX/TX seq numbers: 52239/52241
SPI underruns 0, overruns 0
Number of disconnects: 0
Buffer RX/TX: 1632/3096-0
=== Duet Control Server ===
Duet Control Server v3.1.1
File:
Buffered code: G1 X202.008 Y218.644 E6.8813
Buffered code: G1 X200.366 Y221.101 E6.9796
Buffered code: G1 X198.832 Y223.628 E7.0779
Buffered code: G1 X197.411 Y226.220 E7.1762
Buffered code: G1 X196.104 Y228.870 E7.2746
Buffered code: G1 X194.913 Y231.576 E7.3729
Buffered code: G1 X193.842 Y234.330 E7.4712
Buffered code: G1 X192.892 Y237.129 E7.5695
Buffered code: G1 X192.065 Y239.967 E7.6678
Buffered code: G1 X191.483 Y242.343 E7.7491
Buffered code: G1 X191.362 Y242.838 E7.7661
Buffered code: G1 X190.786 Y245.736 E7.8644
Buffered code: G1 X190.336 Y248.658 E7.9627
Buffered code: G1 X190.014 Y251.596 E8.0610
Buffered code: G1 X189.821 Y254.545 E8.1593
Buffered code: G1 X189.756 Y257.500 E8.2576
Buffered code: G1 X189.821 Y260.455 E8.3559
Buffered code: G1 X190.014 Y263.404 E8.4542
Buffered code: G1 X190.281 Y265.836 E8.5356
Buffered code: G1 X190.336 Y266.342 E8.5525
Buffered code: G1 X190.786 Y269.264 E8.6508
Buffered code: G1 X191.362 Y272.162 E8.7491
Buffered code: G1 X192.065 Y275.033 E8.8474
Buffered code: G1 X192.892 Y277.871 E8.9457
Buffered code: G1 X193.842 Y280.670 E9.0440
Buffered code: G1 X194.913 Y283.424 E9.1423
Buffered code: G1 X196.104 Y286.130 E9.2407
Buffered code: G1 X197.411 Y288.781 E9.3390
Buffered code: G1 X198.832 Y291.372 E9.4373
Buffered code: G1 X200.101 Y293.463 E9.5186
Buffered code: G1 X200.366 Y293.899 E9.5356
Buffered code: G1 X202.008 Y296.356 E9.6339
==> 1524 bytes
Code buffer space: 1588
Configured SPI speed: 8000000 Hz
Full transfers per second: 32.49
File /opt/dsf/sd/gcodes/Pineapple_Bottom120_percent.gcode is selected, processing

Phaedrux

@evomotors said in Duet 3 + Tool Board Extruder/Retraction Issue:

hiccups 7539

So you are getting a lot of hiccups on the tool board, so perhaps try the new beta?

is 7mm/s correct for your retraction speed?

evomotors

@Phaedrux said in Duet 3 + Tool Board Extruder/Retraction Issue:

@evomotors said in Duet 3 + Tool Board Extruder/Retraction Issue:

hiccups 7539

So you are getting a lot of hiccups on the tool board, so perhaps try the new beta?

is 7mm/s correct for your retraction speed?

Retraction speed is 7 mm/s, any value higher that that was performing extremely worst when stepper connected to the tool board.

I didn't install beta yet. I'm willing to do so, but a little confused in the instructions for installing unstable version using SBC and DWC.

What about bunch of blocked and suspended CAN bus commands on the Duet3 board itself?:
CanReceiv(suspended,3388) CanSender(suspended,1392) CanClock(blocked,1436)

dc42

@evomotors said in Duet 3 + Tool Board Extruder/Retraction Issue:

What about bunch of blocked and suspended CAN bus commands on the Duet3 board itself?:
CanReceiv(suspended,3388) CanSender(suspended,1392) CanClock(blocked,1436)

Those do not refer to messages. The clue is the "Tasks:" label at the start of the line.

evomotors

@dc42 said in Duet 3 + Tool Board Extruder/Retraction Issue:

@evomotors said in Duet 3 + Tool Board Extruder/Retraction Issue:

What about bunch of blocked and suspended CAN bus commands on the Duet3 board itself?:
CanReceiv(suspended,3388) CanSender(suspended,1392) CanClock(blocked,1436)

Those do not refer to messages. The clue is the "Tasks:" label at the start of the line.

Can you please point me to how to update to latest beta? What files do I need to download update DWC (looks like it's required for new beta) what bin files do I need to update Duet3 and tool board?

I'm looking at this guide right now:
https://duet3d.dozuki.com/Wiki/Getting_Started_With_Duet_3#Section_Updating_Duet_3_from_RRF3_0_Beta_12_to_3_0_Final_via_DWC

Phaedrux

@evomotors said in Duet 3 + Tool Board Extruder/Retraction Issue:

I'm looking at this guide right now:
https://duet3d.dozuki.com/Wiki/Getting_Started_With_Duet_3#Section_Updating_Duet_3_from_RRF3_0_Beta_12_to_3_0_Final_via_DWC

This is for a specific case for updating to 3.0 final from 3.0 beta 12.

To update to the 3.2 beta2 using a SBC you can add the unstable repository on the pi and then use sudo apt update sudo apt upgrade as usual.

https://duet3d.dozuki.com/Wiki/Getting_Started_With_Duet_3#Section_Software_Installation

User3D

@evomotors
Do you still face the same issue in extrusion ?
I'm planning to drive extruder from other board too.

Phaedrux

@user3d I believe all tool board extrusion issues are solved in recent firmware, though the firmware version must match between mainboard and toolboard.

User3D

@phaedrux said in Duet 3 + Tool Board Extruder/Retraction Issue:

@user3d I believe all tool board extrusion issues are solved in recent firmware, though the firmware version must match between mainboard and toolboard.

Not toolboard. I'm planning so with EXP1XD
@phaedrux is it recommended?

dc42

@user3d I am not aware of any issues using a EXP1XD to drive an extruder. The EXP1XD and the TOOL1LC use common source code, so the issues we fixed for the tool board are also fixed for the EXP1XD.

User3D

@dc42 ok. Thank you