Duet mini toolboard extruder problem

jay_s_uk

@simonk you shouldn't be doubling up all your Z values.
Only M584 should have Z0.2:0.3
Everything else such as M350 should only have a single z value

SimonK

@jay_s_uk Thanks, that will make it a bit cleaner.

jay_s_uk

@simonk it may have a knock on effect to your E driver not working. Give it a go and see. Otherwise your config looks ok from the quick look I gave it.
Might be worth running M98 p"config g" to see if any errors are detected

SimonK

@jay_s_uk That's made the config a lot cleaner, thanks, also took out the decimals.

; Configuration file for Duet 3 Mini 5+ (firmware version 3.3)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v3.3.13 on Sat Oct 08 2022 15:04:45 GMT+0100 (British Summer Time)

; General preferences
M575 P1 S1 B57600                                ; enable support for PanelDue
G90                                              ; send absolute coordinates...
M83                                              ; ...but relative extruder moves
M550 P"Duet 3"                                   ; set printer name
M669 K1                                          ; select CoreXY mode

; Wait a moment for the CAN expansion boards to start
G4 S2

; Network
M552 P0.0.0.0 S1                                 ; enable network and acquire dynamic address via DHCP
M586 P0 S1                                       ; enable HTTP
M586 P1 S0                                       ; disable FTP
M586 P2 S0                                       ; disable Telnet

; Drives
M569 P0.0 S1 D3 V40                                     ; physical drive 0.0 goes forwards (X)
M569 P0.1 S0 D3 V40                                     ; physical drive 0.1 goes forwards (Y)
M569 P0.2 S0                                     ; physical drive 0.2 goes forwards (Z1)
M569 P0.3 S0                                     ; physical drive 0.3 goes forwards (Z2)
M569 P121.0 S1                                   ; physical drive 121.0 goes forwards (Extruder)
M584 X0.0 Y0.1 Z0.2:0.3 E121.0                   ; set drive mapping
M350 X16 Y16 Z16 E16 I1                       ; configure microstepping with interpolation
M92 X100 Y100 Z400 E397       ; set steps per mm
M566 X900 Y900 Z24 E800        ; set maximum instantaneous speed changes (mm/min)
M203 X20000 Y20000 Z600 E4000   ; set maximum speeds (mm/min)
M201 X4000 Y4000 Z100 E4000        ; 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 X-184 Y-140 Z0 S1                           ; set axis minima
M208 X157 Y150 Z400 S0                           ; set axis maxima

; Endstops
M574 X1 S3                                       ; configure sensorless endstop for low end on X
M574 Y1 S3                                       ; configure sensorless endstop for low end on Y
M574 Z1 S2                                       ; configure Z-probe endstop for low end on Z

; Filament sensor
;M591 D0 P3 C3 S1 R50:135 L25.09 E10 
M591 P3 C"121.io1.in" D0 S1 L25.09 R50:135 E10 ; Duet3D rotating magnet sensor for extruder drive 0 is connected to E0 endstop input, enabled, sensitivity 24.8mm.rev, 70% to 130% tolerance, 6mm detection length

; Z-Probe
M950 S0 C"121.io0.out"                           ; create servo pin 0 for BLTouch
M558 P9 C"121.io0.in" H5 F120 T6000              ; set Z probe type to bltouch and the dive height + speeds
G31 P500 X-41 Y-34 Z2.5                          ; set Z probe trigger value, offset and trigger height
M557 X-104:104 Y-104:104 S104                    ; define mesh grid

; Heaters
M308 S0 P"temp0" Y"thermistor" T100000 B4138     ; 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 R0.420 K0.297:0.000 D3.21 E1.35 S1.00 B0 ; enable bang-bang mode for the bed heater and set PWM limit
M140 H0                                          ; map heated bed to heater 0
M143 H0 S100                                     ; set temperature limit for heater 0 to 100C
M308 S1 P"121.temp0" Y"thermistor" T100000 B4138 ; configure sensor 1 as thermistor on pin 121.temp0
M950 H1 C"121.out0" T1                           ; create nozzle heater output on 121.out0 and map it to sensor 1
M307 H1 A780.6 C250.7 D0.7 V24.0 B0			; Set PID for hotend values - 0.4MM NOZZLE - Tool 0
M143 H1 S280                                     ; set temperature limit for heater 1 to 280C

; Fans
M950 F0 C"121.out1" Q500                         ; create fan 0 on pin 121.out1 and set its frequency
M106 P0 S0 H-1                                   ; set fan 0 value. Thermostatic control is turned off
M950 F1 C"121.out2" Q500                         ; create fan 1 on pin 121.out2 and set its frequency
M106 P1 S1 H1 T45                                ; set fan 1 value. Thermostatic control is turned on

; Tools
M563 P0 D0 H1 F0                       ; 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

; Miscellaneous
T0                                       ; Select first tool

; Custom settings are not defined

M98 comes back clear of faults.

I'm thinking the driver may be dead, assuming I got lucky that everything else seems to work correctly.

jay_s_uk

@simonk that's better. I'm surprised it doesn't complain when you try to extrude. Usually if the drivers dead the firmware gives you warnings etc.
I'm assuming your either up to temp or have cold extrusion enabled? And you have the tool selected too?

Phaedrux

Can you send M122 and M122 B121 and copy paste the results here?
Do you see any visible damage to the toolboard near the driver?

SimonK

@jay_s_uk Originally I didn't have the T0 at the end of config, and it had the usual "Attempting to extrude with no tool selected" error, but once selected it was ok. Then I added the T0 and it's fine once heated up.

SimonK

@phaedrux

M122:

m122
=== Diagnostics ===
RepRapFirmware for Duet 3 Mini 5+ version 3.4.3 (2022-10-05 09:05:15) running on Duet 3 Mini5plus Ethernet (standalone mode)
Board ID: 5HB9X-VB67A-G65J0-401GW-1S82Z-Z5UJ3
Used output buffers: 1 of 40 (13 max)
=== RTOS ===
Static ram: 103684
Dynamic ram: 105228 of which 20 recycled
Never used RAM 32780, free system stack 196 words
Tasks: NETWORK(ready,25.6%,229) ETHERNET(notifyWait,0.1%,560) HEAT(notifyWait,0.0%,373) Move(notifyWait,0.0%,363) CanReceiv(notifyWait,0.0%,772) CanSender(notifyWait,0.0%,336) CanClock(delaying,0.0%,348) TMC(notifyWait,0.7%,106) MAIN(running,72.7%,425) IDLE(ready,0.1%,30) AIN(delaying,0.8%,263), total 100.0%
Owned mutexes:
=== Platform ===
Last reset 00:05:01 ago, cause: software
Last software reset time unknown, reason: User, GCodes spinning, available RAM 33184, slot 2
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00000000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
Aux0 errors 0,0,0
MCU revision 3, ADC conversions started 301949, completed 301948, timed out 0, errs 0
Step timer max interval 1487
MCU temperature: min 22.1, current 26.0, max 26.2
Supply voltage: min 24.2, current 24.2, max 24.3, under voltage events: 0, over voltage events: 0, power good: yes
Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0
Events: 0 queued, 0 completed
Driver 0: standstill, SG min 0, read errors 0, write errors 1, ifcnt 27, reads 15861, writes 13, timeouts 0, DMA errors 0, CC errors 0
Driver 1: standstill, SG min 0, read errors 0, write errors 1, ifcnt 27, reads 15860, writes 13, timeouts 0, DMA errors 0, CC errors 0
Driver 2: standstill, SG min 0, read errors 0, write errors 1, ifcnt 23, reads 15862, writes 11, timeouts 0, DMA errors 0, CC errors 0
Driver 3: standstill, SG min 0, read errors 0, write errors 1, ifcnt 23, reads 15862, writes 11, timeouts 0, DMA errors 0, CC errors 0
Driver 4: standstill, SG min 0, read errors 0, write errors 1, ifcnt 19, reads 15865, writes 9, timeouts 0, DMA errors 0, CC errors 0
Driver 5: not present
Driver 6: not present
Date/time: 2022-10-13 16:16:24
Cache data hit count 521434232
Slowest loop: 4.38ms; fastest: 0.13ms
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 22.5MBytes/sec
SD card longest read time 3.2ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 83, segments created 0, maxWait 0ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== AuxDDARing ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== Heat ===
Bed heaters 0 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0
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
=== Filament sensors ===
Extruder 0: no data received
=== CAN ===
Messages queued 2736, received 6203, lost 0, boc 0
Longest wait 2ms for reply type 6026, peak Tx sync delay 252, free buffers 18 (min 17), ts 1510/1509/0
Tx timeouts 0,0,0,0,0,0
=== Network ===
Slowest loop: 4.36ms; fastest: 0.03ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
HTTP sessions: 1 of 8
= Ethernet =
State: active
Error counts: 0 0 0 0 0 0
Socket states: 5 2 2 2 2 0 0 0

M122 B121:

m122 B121
Diagnostics for board 121:
Duet TOOL1LC rev 1.1 or later firmware version 3.4.3 (2022-10-05 09:18:26)
Bootloader ID: SAMC21 bootloader version 2.3 (2021-01-26b1)
All averaging filters OK
Never used RAM 2204, free system stack 62 words
Tasks: Move(notifyWait,0.0%,153) HEAT(notifyWait,0.2%,91) CanAsync(notifyWait,0.0%,65) CanRecv(notifyWait,0.0%,76) CanClock(notifyWait,0.0%,65) ACCEL(notifyWait,0.0%,61) TMC(notifyWait,0.4%,67) MAIN(running,94.4%,351) IDLE(ready,0.0%,26) AIN(delaying,4.9%,142), total 100.0%
Last reset 00:05:47 ago, cause: software
Last software reset data not available
Driver 0: pos 0, 397.0 steps/mm,not present, steps req 0 done 0
Moves scheduled 0, completed 0, in progress 0, hiccups 0, step errors 0, maxPrep 0, maxOverdue 0, maxInc 0, mcErrs 0, gcmErrs 0
Peak sync jitter -3/9, peak Rx sync delay 212, resyncs 0/0, no step interrupt scheduled
VIN voltage: min 24.4, current 24.5, max 24.7
MCU temperature: min 17.5C, current 26.3C, max 26.3C
Last sensors broadcast 0x00000002 found 1 57 ticks ago, 0 ordering errs, loop time 0
CAN messages queued 7100, send timeouts 0, received 3127, lost 0, free buffers 37, min 37, error reg 110000
dup 0, oos 0/0/0/0, bm 0, wbm 0, rxMotionDelay 0
Accelerometer: LIS3DH, status: 00
I2C bus errors 0, naks 3, other errors 0
=== Filament sensors ===
Interrupt 4 to 8us, poll 8 to 710us
Driver 0: pos 2160.00, errs: frame 0 parity 0 ovrun 0 pol 0 ovdue 0

No damage that I can see, it all looks good.

dc42

@simonk said in Duet mini toolboard extruder problem:

Driver 0: pos 0, 397.0 steps/mm,not present

There is a problem with communication between the microcontroller and the driver. We will replace the tool board. Please email warranty@duet3d.com to start the warranty replacement process. Include a link to this thread in the email.

SimonK

@dc42 I noticed that after comparing it with another users M122. Figured I did blow the driver. I'm actually quite glad nobody said there was a silly mistake with the config.

Thanks for the offer but I've just ordered a replacement, it was my mistake to fix.

dc42

@SimonK ah OK, I've just read your first post in this thread. Yes, reversing the VIN power does blow the driver, unless the supply current is limited to a very low value.