I was about to jump on to make a thread myself, but you beat me to it! 😅
I want to dedicate a special nod of appreciation to the cornerstones like @T3P3Tony, @dc42, @droftarts , @chrishamm, @mfs12, @Phaedrux, @gloomyandy & @jay_s_uk (to mention some) for all the time you guys spend on this project & making it what it is!
My current workhorse is a Voron trident powered by a Duet Mini 5+ with a 1LC running RRF 3.4.4 and with that also using both a bed probe (klicky probe), and a nozzle probe located next to the bed.
The RRF macro's avalible for Voron printers don't get much work done if any at all, and the exisisting versions of the "auto-z" macro were somewhat outdated. Not using a much of the newer conditional commands we have to our disposition now.
So i sat out to make a new one, would be cool to get some input on what the hivemind thinks about it. And PLEASE come with hints on improvements or more importantly any errors/bugs!
I would say most sub-macros are quite self explanatory, but if you(?) want me to add them to see what they contain just say so
; /sys/lib/z_cal.g (v2.2)
; Called when "M98 P"/sys/lib/z_cal.g" is sent
; Used to calibrate the Z offsett between the Nozzle and buildplate.
; report whats going on
M291 R"Z Offset Calibration" P"Please wait..." T0 ; leveling bed message
; ====================
; preparation before probing
; ====================
; the distance from the body of the klicky probe to it's own trigger point
var base_Hot_offset = global.klicky_offset
var add_Cold_offset = 0.06
; remember the old offsets
var old_k0_offset = sensors.probes[0].triggerHeight ; old klicky offset
var old_k1_offset = sensors.probes[1].triggerHeight ; old z-pin offset
; reset existing calibration
G31 K0 Z7.50 ; reset klicky
G31 K1 Z0.00 ; reset z-pin
; variables for klicky calculation
var temp0 = 0 ; placeholder value
var temp1 = 5 ; placeholder value
var temp2 = 10 ; set value above target value
; variables for z-pin calculation
var temp3 = 0 ; placeholder value
var temp4 = 2.5 ; placeholder value
var temp5 = 5 ; set value above target value
; Make sure all axes are Homed
if !move.axes[0].homed || !move.axes[1].homed || !move.axes[2].homed ; if axes aren't homed
G28 ; home all axes
else
G28 Z ; probe nozzle to make Z is correct anyways
; LED status
set global.sb_leds = "homing"
; Lower currents, speed & accel
M98 P"/sys/lib/current/xy_current_low.g" ; set low XY currents
M98 P"/sys/lib/current/z_current_low.g" ; Set low Z currents
M98 P"/sys/lib/speed/speed_probing.g" ; set low speed & accel
if move.axes[2].userPosition < 20
G1 Z20 F2400 ; lower Z
M401 P0 ; load the klicky probe
; ====================---------------------------------------------------------
; calibrate klicky
; ====================
; position for probing
G1 X{global.z_pin_x - 4} Y{global.z_pin_y - 23.5} F18000 ; move the klicky body over the Z-pin
G1 Z10 F2400 ; move probe closer to z-pin
; lower probing speed for accuracy
M558 K1 F100:50 ; lower probing speed
; probe klicky body on Z-pin, minimum 0.004mm accuracy
while var.temp2 >= 0.004
G30 K1 S-1 ; probe the klicky body with the Z-pin and report value
M400 ; wait for moves to finish
; lift from z-pin
G91 ; relative pos
G1 Z2 F500 ; quickly move up 2mm
G90 ; absolute pos
M400 ; wait for moves to finish
; save first probe result
set var.temp0 = sensors.probes[1].lastStopHeight
;probe klicky body on Z-pin again
G30 K1 S-1 ; probe the klicky body with the Z-pin and report value
M400 ; wait for moves to finish
; lift from z-pin
G91 ; relative pos
G1 Z2 F500 ; quickly move up 2mm
G90 ; absolute pos
M400 ; wait for moves to finish
; save second probe result
set var.temp1 = sensors.probes[1].lastStopHeight
;calculate deviation
set var.temp2 = (var.temp0-var.temp1)
; calculate the new klicky offset
var new_k0_offset = {((var.temp0 + var.temp1) / 2) + var.base_Hot_offset}
; compensate for cold extruder
if heat.heaters[1].current < 160
set var.new_k0_offset = {var.new_k0_offset + var.add_Cold_offset}
; enable the new klicky offset
G31 K0 Z{var.new_k0_offset} ; apply the new Z offsett value
; return standard probing speed
M558 K1 F600:180 ; reset probing speed to normal values
;echo the klicky offset
echo "Old Klicky offset " ^ var.old_k0_offset ^ " New Klicky offset " ^ var.new_k0_offset
; ====================---------------------------------------------------------
; calibrate Z-pin
; ====================
; move bed away from nozzle
G1 Z10 F2400 ; lower the bed
; position for probing
M98 P"/sys/lib/goto/bed_center.g" ; move to the center of the bed
M400 ; wait for moves to finish
; lower probing speed for accuracy
M558 K0 F100:50 ; lower probing speed
; probe the bed, minimum 0.004mm accuracy
while var.temp5 >= 0.004
G30 K0 S-1 ; probe the klicky body with the Z-pin and report value
M400 ; wait for moves to finish
; lift from z-pin
G91 ; relative pos
G1 Z2 F500 ; quickly move up 2mm
G90 ; absolute pos
M400 ; wait for moves to finish
; save first probe result
set var.temp3 = sensors.probes[0].lastStopHeight
;probe klicky body on Z-pin again
G30 K0 S-1 ; probe the klicky body with the Z-pin and report value
M400 ; wait for moves to finish
; lift from z-pin
G91 ; relative pos
G1 Z2 F500 ; quickly move up 2mm
G90 ; absolute pos
M400 ; wait for moves to finish
; save second probe result
set var.temp4 = sensors.probes[0].lastStopHeight
;calculate deviation
set var.temp5 = (var.temp3-var.temp4)
; calculate the new z-pin offset
var new_k1_offset = {var.new_k0_offset - ((var.temp3 + var.temp4) / 2)}
; enable the new z-pin offset
G31 K1 Z{var.new_k1_offset} ; apply the new Z offsett value
; return standard probing speed
M558 K0 F600:180 ; reset probing speed to normal values
; move bed away from nozzle
G1 Z{global.klicky_clearance} F2400 ; lower the bed
;echo the z-pin offset
echo "Old Z-pin offset " ^ var.old_k1_offset ^ " New Z-pin offset " ^ var.new_k1_offset
; ====================---------------------------------------------------------
; finish up
; ====================
; save the new offsets
M500 P10:31 ; store the new Z offsett values to config-override.g
G4 P250 ; wait 250 milliseconds
M402 P0 ; dock the klicky probe
; home z with the new offsets
G28 Z
set global.Z_cal = true
; report whats going on
M291 R"Z Offset Calibration" P"Done" T5 ; bed leveling done message
;LED status
set global.sb_leds = "ready"
I've done some more testing and tuning as well, both PA, Acceleration & Jerk has gotten some adjustments. This new approach to input shapiny is REALLY a huge improvement!
I'll upload some pictures once i get home, but i at least was able to shave down PA to 0.0075s from 0.0450s ,acceleration to 3000mm/s2 from 2500mm/s2 & upped the jerk to 7mm/s (i can't remember the Jerk values so i'll update those with the pics later). I also turned up the printspeed with 50mm/s across the board.
Here is the "PA-tower" results with a range from 0-0.05s, before i had to run 0.045s PA to get the same result as I get with 0.0072s now.
The printer sounds happier, and the surface quality in the prints is better than ever. Gread job @dc42 & and others who contributed!😁
So i'm currently upgrading my printer from 1 color to 3 colors.
And for that i ofcourse needed one more stepper driver for my third extruder, that being said i thought the space an Duex2/5 would take up just for one extra driver was a little excessive. So i'm opting for the "Driver breakout board" approach to it.
After reading up on the duet wiki and a couple other sites i came to see that the above mentioned approach didn't have a straight forward guide to follow. So i threw this little "How to" together to maybe help others wanting to do the same thing.
Hope this can come in handy for someone, and for gods sake if any of the graybeard's here see something wrong please let me know so that i can correct it!
https://drive.google.com/open?id=1Rtw6UGXi_EILRHi1uBiB5z1u2HCFVHDR
Cheers!
@Proschi78
Install the one he just made live on Github instead.
Would be great to have a full backup function in the DWC, now that filament control have been implemented along with all the other macro's it's starting to be quite a bit of information/configeration excisting outisde the easily to backup /sys/. Don't want / need a way to "import" and full backup to the SDcard, but a way to get all the files off it and to a downloadable .zip or something without having to remove the SDcard and insert it to a computer.
I finally had some more time to mess with this!
I've put together and compiled a working Multiclient firmware that utilize FreeRTOS to que the stream(s) with ESP32 Arduino Core 2.0.14 and Espressif 2.0.6 drivers, which adds support for a couple new sensors and dev boards. And some other under the hood improvements like lower stream latency/lag (at least in my case).
The new Arduino Core brings the posibility to use the slightly more expensive but much more compact Seeed Studio XIAO ESP32S3 Sense (which i'm looking into trying)..
Anywho, with this firmware you can have up too 10 active connected clients on each ESP32-CAM module so it's more flexible to use in my opinion, since I like to check in on the printer with my smartphone every now and then.
As of now I've opted to run on SVGA / 800X600 (with an OV2640) resolution but a higher JPEG quality to make the stream reasonably quick without too much loss in image quality/size.
Still doing some more testing and polishing then i'm going to put it on GIT 
️
For who it might concern/help, I feel like I've got filament-change.g working decently well at this point:
; /sys/filament-change.g v2.2
; Called when M600 is sent
; Used to do a filament change while printing
;---/
; -/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--
; THIS MACRO ONLY WORKS WITH RRF 3.5.0b1 AND LATER!!
;--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--
;-/
; ====================---------------------------------------------------------
; Settings section
; ====================
; Will not be used if you're using a "goto" macro
var x = 40 ; The X axis location where you want the hotend to "park" while changing filament
var y = 0 ; The Y axis location where you want the hotend to "park" while changing filament
var spd = 15000 ; The speed of which you want the hotend to move to the "park" location
var lift = 20 ; The Z clearance you want your nozzle to have from the print while changing filament
var lights = true ; true / false depending if you have chamber lights or not that you want to turn on
; If you don't have lights you want to turn on don't mess with these
var io = 0 ; The GPIO port number (set by M950) for the lights you want to turn on
var pwm = 1 ; The PWM to be set on the GPIO port above, 0=off 1=full power
var purge = 60 ; The amount of filament your hotend need to purge for a clean filament/color change
; Will be swaped out with global.unload_length if you have that defined!
var unload = 12 ; The length of which filament have to be retracted to clear the meltzone
; Don't touch anyting beyond this point(unless you know what you're doing)!!
; ====================---------------------------------------------------------
if exists(global.unload_length)
set var.unload = global.unload_length
var pwm_res = state.gpOut[{var.io}].pwm ; Store the PWM from the PPIO port so that it can be returned after changing filament
if var.lights
M42 P{var.io} S{var.pwm} ; Turn on the lights
if fileexists("/sys/lib/beep/l.g")
M98 P"/sys/lib/beep/l.g" ; Long beep
M400 ; Wait for moves to finish
G91 ; Relative positioning
M83 ; Extruder relative positioning
G10 ; Retraction
G1 Z1.00 X20.0 Y20.0 F20000 ; Short quick move to disengage from print
G1 Z{var.lift - 1} F800 ; Go to spesified Z clearance
if !fileexists("/sys/lib/goto/front_right.g")
G90 ; Absolute positioning
G1 X{var.x} Y{var.y} F{var.spd} ; Move the nozzle to the location defined in the settings section
if fileexists("/sys/lib/goto/front_right.g")
M98 P"/sys/lib/goto/front_right.g" {var.spd} ; Move to front right for filament change
G1 E2 F800 ; Extrude slightly to help form a nice tip on the filament
G1 E{-(var.unload)} F800 ; Retract filament from the meltzone
M400 ; Wait for moves to finish
if fileexists("/sys/lib/beep/xl.g")
M98 P"/sys/lib/beep/xl.g" ; Extra long beep
M291 S4 R"Manual Filament Change" P"Change & prime filament, then press OK." K{"OK","SKIP",}
; "OK"
if input = 0
G1 E{var.purge} F200 ; Purge filament
; "SKIP"
if input = 1
G1 E{var.unload} F800 ; Extrude filament back to the meltzone
M400 ; Wait for moves to finish
if var.lights
M42 P{var.io} S{var.pwm_res} ; Return lights to previous state
if !exists(global.FilamentCHG)
global FilamentCHG = true
else
set global.FilamentCHG = true
@dc42 Had a glance at this in the last 3,5 months? 
@oct_opus
Tbh i just think those sensors are next to snakeoil 
Given how cheap the real probes are, it's not worth the potential headache and anoyance any of the knocnoffs can make.
And for the sake of testing, I swaped the setup around, law and behold it don't stop extruding.
So i think we can say with some amount of certainty that the issue is within the tool board code don't you think @dc42? 🤔
M122
=== Diagnostics ===
RepRapFirmware for Duet 3 Mini 5+ version 3.5.0-rc.3+ (2024-02-27 13:52:47) running on Duet 3 Mini5plus WiFi (standalone mode)
Board ID: XNHXF-HR6KL-K65J0-409N2-K9W1Z-RV2MZ
Used output buffers: 24 of 40 (40 max)
=== RTOS ===
Static ram: 103264
Dynamic ram: 125884 of which 24 recycled
Never used RAM 9052, free system stack 151 words
Tasks: NETWORK(2,nWait 7,15.8%,196) HEAT(3,nWait 6,0.0%,351) Move(4,nWait 6,0.2%,241) CanReceiv(6,nWait 1,0.1%,555) CanSender(5,nWait 7,0.0%,337) CanClock(7,delaying,0.0%,340) TMC(4,nWait 6,0.8%,68) MAIN(1,running,80.6%,667) IDLE(0,ready,1.5%,30) AIN(4,delaying,0.9%,260), total 100.0%
Owned mutexes: WiFi(NETWORK)
=== Platform ===
Last reset 00:03:44 ago, cause: software
Last software reset at 2024-03-09 09:39, reason: User, Gcodes spinning, available RAM 9400, slot 0
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00000000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x04
Aux0 errors 0,0,0
MCU revision 3, ADC conversions started 224703, completed 224702, timed out 0, errs 0
MCU temperature: min 42.3, current 45.2, max 45.4
Supply voltage: min 2.9, current 23.7, max 24.4, under voltage events: 0, over voltage events: 0, power good: yes
Heap OK, handles allocated/used 99/32, heap memory allocated/used/recyclable 2048/2008/1560, gc cycles 56
Events: 0 queued, 0 completed
Driver 0: standstill, SG min 0, read errors 0, write errors 0, ifcnt 31, reads 11755, writes 31, timeouts 0, DMA errors 0, CC errors 0
Driver 1: ok, SG min 0, read errors 0, write errors 0, ifcnt 32, reads 11754, writes 32, timeouts 0, DMA errors 0, CC errors 0
Driver 2: standstill, SG min 0, read errors 0, write errors 0, ifcnt 24, reads 11762, writes 24, timeouts 0, DMA errors 0, CC errors 0
Driver 3: standstill, SG min 0, read errors 0, write errors 0, ifcnt 24, reads 11762, writes 24, timeouts 0, DMA errors 0, CC errors 0
Driver 4: standstill, SG min 0, read errors 0, write errors 0, ifcnt 23, reads 11763, writes 23, timeouts 0, DMA errors 0, CC errors 0
Driver 5: not present
Driver 6: not present
Date/time: 2024-03-09 09:43:18
Cache data hit count 362270903
Slowest loop: 217.97ms; fastest: 0.10ms
=== Storage ===
Free file entries: 16
SD card 0 detected, interface speed: 22.5MBytes/sec
SD card longest read time 6.0ms, write time 7.0ms, max retries 0
=== Move ===
DMs created 83, segments created 14, maxWait 87892ms, bed compensation in use: mesh, height map offset 0.000, max steps late 1, min interval 0, bad calcs 0, ebfmin 0.00, ebfmax 0.00
next step interrupt due in 63 ticks, enabled
Moves shaped first try 7, on retry 0, too short 2, wrong shape 147, maybepossible 1
=== DDARing 0 ===
Scheduled moves 206, completed 167, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 25], CDDA state 3
=== DDARing 1 ===
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 0 is on, I-accum = 0.4
Heater 1 is on, I-accum = 0.0
=== GCodes ===
Movement locks held by null, null
HTTP is idle in state(s) 0
Telnet is idle in state(s) 0
File is idle in state(s) 3
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 doing "G4 P250" in state(s) 0 0, running macro
Aux2 is idle in state(s) 0
Autopause is idle in state(s) 0
File2 is idle in state(s) 0
Queue2 is idle in state(s) 0
Q0 segments left 6, axes/extruders owned 0x0000807
Code queue 0 is empty
Q1 segments left 0, axes/extruders owned 0x0000000
Code queue 1 is empty
=== Filament sensors ===
check 0 clear 0
Extruder 0 sensor: no filament
=== CAN ===
Messages queued 2200, received 4594, lost 0, errs 1357, boc 0
Longest wait 3ms for reply type 6053, peak Tx sync delay 16014, free buffers 26 (min 25), ts 1122/1120/0
Tx timeouts 0,0,1,0,0,0 last cancelled message type 30 dest 127
=== Network ===
Slowest loop: 212.55ms; fastest: 0.00ms
Responder states: MQTT(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)
HTTP sessions: 1 of 8
=== WiFi ===
Interface state: active
Module is connected to access point
Failed messages: pending 0, notrdy 0, noresp 0
Firmware version 2.1beta7
MAC address c4:5b:be:ce:91:93
Module reset reason: Power up, Vcc 3.38, flash size 2097152, free heap 43064
WiFi IP address 192.168.10.x
Signal strength -51dBm, channel 6, mode 802.11n, reconnections 0
Clock register 00002001
Socket states: 0 0 0 0 0 0 0 0
M122 B121
Diagnostics for board 121:
Duet TOOL1LC rev 1.1 or later firmware version 3.5.0-beta.4 (2023-06-08 16:22:30)
Bootloader ID: SAMC21 bootloader version 2.8 (2023-07-25)
All averaging filters OK
Never used RAM 1496, free system stack 88 words
Tasks: Move(3,nWait,0.0%,111) HEAT(2,nWait,0.6%,67) CanAsync(5,nWait,0.0%,54) CanRecv(3,nWait,0.0%,75) CanClock(5,nWait,0.0%,66) ACCEL(3,nWait,0.0%,53) TMC(2,delaying,3.0%,57) MAIN(1,running,91.5%,346) IDLE(0,ready,0.0%,27) AIN(2,delaying,4.9%,142), total 100.0%
Last reset 00:03:47 ago, cause: power up
Last software reset data not available
Driver 0: pos 0, 568.8 steps/mm, ok, SG min 0, read errors 0, write errors 0, ifcnt 13, reads 48316, writes 13, timeouts 0, DMA errors 0, CC errors 0, steps req 0 done 46224
Moves scheduled 194, completed 193, in progress 1, hiccups 7, step errors 0, maxPrep 563, maxOverdue 71, maxInc 71, mcErrs 0, gcmErrs 0, ebfmin 0.00, ebfmax 1.00
Peak sync jitter -2/9, peak Rx sync delay 215, resyncs 0/0, no timer interrupt scheduled
VIN voltage: min 23.7, current 24.5, max 24.9
MCU temperature: min 62.7C, current 66.0C, max 66.1C
Last sensors broadcast 0x00000012 found 2 108 ticks ago, 0 ordering errs, loop time 1
CAN messages queued 4696, send timeouts 0, received 2281, lost 0, free buffers 18, min 18, error reg 0
dup 0, oos 0/0/0/0, bm 0, wbm 0, rxMotionDelay 325, adv 35765/74646
Accelerometer: LIS3DH, status: 00
I2C bus errors 0, naks 3, other errors 0
=== Filament sensors ===
Interrupt 5726621 to 0us, poll 4 to 2096us
Driver 0: ok
M122
=== Diagnostics ===
RepRapFirmware for Duet 3 Mini 5+ version 3.5.0-rc.3+ (2024-02-27 13:52:47) running on Duet 3 Mini5plus WiFi (standalone mode)
Board ID: XNHXF-HR6KL-K65J0-409N2-K9W1Z-RV2MZ
Used output buffers: 23 of 40 (40 max)
=== RTOS ===
Static ram: 103264
Dynamic ram: 125884 of which 24 recycled
Never used RAM 8476, free system stack 132 words
Tasks: NETWORK(2,nWait 7,17.0%,196) HEAT(3,nWait 6,0.0%,342) Move(4,nWait 6,2.5%,237) CanReceiv(6,nWait 1,0.1%,555) CanSender(5,nWait 7,0.1%,328) CanClock(7,delaying,0.0%,340) TMC(4,nWait 6,0.9%,68) MAIN(1,running,77.1%,667) IDLE(0,ready,1.4%,30) AIN(4,delaying,0.9%,260), total 100.0%
Owned mutexes: WiFi(NETWORK)
=== Platform ===
Last reset 00:12:56 ago, cause: software
Last software reset at 2024-03-09 09:39, reason: User, Gcodes spinning, available RAM 9400, slot 0
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00000000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x04
Aux0 errors 0,0,0
MCU revision 3, ADC conversions started 777401, completed 777401, timed out 0, errs 0
MCU temperature: min 44.9, current 46.0, max 46.6
Supply voltage: min 23.7, current 23.8, max 24.4, under voltage events: 0, over voltage events: 0, power good: yes
Heap OK, handles allocated/used 99/32, heap memory allocated/used/recyclable 2048/1368/920, gc cycles 174
Events: 0 queued, 0 completed
Driver 0: ok, SG min 0, read errors 0, write errors 0, ifcnt 31, reads 29074, writes 0, timeouts 0, DMA errors 0, CC errors 0
Driver 1: ok, SG min 0, read errors 0, write errors 0, ifcnt 32, reads 29074, writes 0, timeouts 0, DMA errors 0, CC errors 0
Driver 2: ok, SG min 0, read errors 0, write errors 0, ifcnt 24, reads 29074, writes 0, timeouts 0, DMA errors 0, CC errors 0
Driver 3: ok, SG min 0, read errors 0, write errors 0, ifcnt 24, reads 29073, writes 0, timeouts 0, DMA errors 0, CC errors 0
Driver 4: ok, SG min 0, read errors 0, write errors 0, ifcnt 23, reads 29074, writes 0, timeouts 0, DMA errors 0, CC errors 0
Driver 5: not present
Driver 6: not present
Date/time: 2024-03-09 09:52:31
Cache data hit count 1142083576
Slowest loop: 32.68ms; fastest: 0.10ms
=== Storage ===
Free file entries: 16
SD card 0 detected, interface speed: 22.5MBytes/sec
SD card longest read time 9.6ms, write time 9.2ms, max retries 0
=== Move ===
DMs created 83, segments created 38, maxWait 2726ms, bed compensation in use: mesh, height map offset 0.000, max steps late 1, min interval 0, bad calcs 0, ebfmin 0.00, ebfmax 0.00
next step interrupt due in 68 ticks, enabled
Moves shaped first try 1226, on retry 351, too short 400, wrong shape 6579, maybepossible 230
=== DDARing 0 ===
Scheduled moves 11221, completed 11183, hiccups 0, stepErrors 0, LaErrors 14, Underruns [0, 0, 0], CDDA state 3
=== DDARing 1 ===
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 0 is on, I-accum = 0.4
Heater 1 is on, I-accum = 0.0
=== GCodes ===
Movement locks held by null, null
HTTP is idle in state(s) 0
Telnet is idle in state(s) 0
File is doing "G1 Z3.75 F21000" 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 doing "G4 P250" in state(s) 0 0, running macro
Aux2 is idle in state(s) 0
Autopause is idle in state(s) 0
File2 is idle in state(s) 0, sync state 1
Queue2 is idle in state(s) 0
Q0 segments left 0, axes/extruders owned 0x0000807
Code queue 0 is empty
Q1 segments left 0, axes/extruders owned 0x0000000
Code queue 1 is empty
=== Filament sensors ===
check 0 clear 0
Extruder 0 sensor: no filament
=== CAN ===
Messages queued 14546, received 11362, lost 0, errs 0, boc 0
Longest wait 5ms for reply type 6024, peak Tx sync delay 240, free buffers 26 (min 25), ts 2763/2763/0
Tx timeouts 0,0,0,0,0,0
=== Network ===
Slowest loop: 20.28ms; fastest: 0.06ms
Responder states: MQTT(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)
HTTP sessions: 1 of 8
=== WiFi ===
Interface state: active
Module is connected to access point
Failed messages: pending 0, notrdy 0, noresp 0
Firmware version 2.1beta7
MAC address c4:5b:be:ce:91:93
Module reset reason: Power up, Vcc 3.38, flash size 2097152, free heap 43064
WiFi IP address 192.168.10.x
Signal strength -53dBm, channel 6, mode 802.11n, reconnections 0
Clock register 00002001
Socket states: 0 0 0 0 0 0 0 0
M122 B121
Diagnostics for board 121:
Duet TOOL1LC rev 1.1 or later firmware version 3.5.0-beta.4 (2023-06-08 16:22:30)
Bootloader ID: SAMC21 bootloader version 2.8 (2023-07-25)
All averaging filters OK
Never used RAM 920, free system stack 88 words
Tasks: Move(3,nWait,0.7%,111) HEAT(2,nWait,0.6%,65) CanAsync(5,nWait,0.0%,54) CanRecv(3,nWait,0.1%,75) CanClock(5,nWait,0.0%,66) ACCEL(3,nWait,0.0%,53) TMC(2,delaying,3.2%,57) MAIN(1,running,90.3%,346) IDLE(0,ready,0.0%,27) AIN(2,delaying,5.1%,142), total 100.0%
Last reset 00:13:01 ago, cause: power up
Last software reset data not available
Driver 0: pos 0, 568.8 steps/mm, ok, SG min 0, read errors 0, write errors 0, ifcnt 13, reads 12625, writes 0, timeouts 1, DMA errors 0, CC errors 0, failedOp 0x6a, steps req 0 done 1021829
Moves scheduled 9744, completed 9742, in progress 1, hiccups 973, step errors 0, maxPrep 1118, maxOverdue 13312, maxInc 10770, mcErrs 0, gcmErrs 0, ebfmin -0.99, ebfmax 1.00
Peak sync jitter -2/10, peak Rx sync delay 282, resyncs 0/0, no timer interrupt scheduled
VIN voltage: min 24.2, current 24.5, max 24.7
MCU temperature: min 62.7C, current 70.2C, max 70.3C
Last sensors broadcast 0x00000012 found 2 185 ticks ago, 0 ordering errs, loop time 1
CAN messages queued 11375, send timeouts 0, received 14606, lost 0, free buffers 18, min 17, error reg 0
dup 0, oos 0/0/0/0, bm 0, wbm 0, rxMotionDelay 494, adv 35801/110985
Accelerometer: LIS3DH, status: 00
I2C bus errors 0, naks 0, other errors 0
=== Filament sensors ===
Interrupt 5726621 to 0us, poll 10 to 3404us
Driver 0: ok
I'm going to let the print finish just to make sure that the issue haven't moved further out in the job, but i'm quite sure it will finish. I'll report back once it's done.
And the print finished without issues👌
Only loading/unloading the tool. I guess the reason for the question is to probe weither or not to let them go to free up space on the pcb for other HW in future revisions? In that case i would gladly go back to using the PD or DWC to run the load/unload macros (a little depedant on what they would have to be removed to make place for ofc).
@Merlin246 Sorry it turned out the ones i have on my git are somewhat old / bugged 
So i didn't want to share them 
I'll make sure to upload the newest set this afternoon!
Finally got around to upload the latest iteration to my git, I've been using these for while now without issues. They are however somewhat interwined with other parts of my config set so you should read through them before you deploy anything (as usual).
The adaptive mesh part is the one that's most "involved" in regard to other parts of my config since it checks if the bed is trammed or not etc. I bet you will figure it out lol.
Also i haven't gotten around to writing a readme for the adaptive probing/mesh, so that's also something you would have to figure out on your own until i get it sorted out. It shouldn't need much more than what's mentioned in the adaptive purge one, except you need to have global.Print_Probe defined and True + you need to call M98 P"/sys/lib/print/print_probe.g" in the startup at the point you would want a adaptive mesh to be probed.
@theruttmeister
Isn't precise and accurate more or less synonyms?
EDIT: forget what i just said, googled the definisions and disproved myself 
️
@dc42 Ok, I just installed both the Mini (even though it's the MMS version) & 1LC from that drive now and am about to fire up the test, I'll update this post once that's done.
It finished without any issues! High five on that fix, it's been annoying me for quite some time now 😂
You loosely mentioned a PD successor being on the drawingboard a while back @dc42.
Some time has passed now, and I bet progress has been made 😇. Could we get some hints to what features you're looking at adding/bringing to the table with this new product? 🙈
This happens to me with my Duet 3 Mini wifi too. Same behaviour with all FW releases i've tried (3.3.x-3.4.1). Get the feeling the wifi module takes a little to long time to start up or something. Plan on trying to remove the wifi setup from config. And execute a macro at the very end of it with a couple seconds of dwell time between M552 S-1, M552 S0 & M552 S1 to see if that works around the issue.
@Notepad
Added in printer & print info in the post above 😊
Did a new print with the exact same g-code & settings, just with PA disabled, and it sure did remove the underextrusion i was seeing (top is 3.6.0-a2+2 with PA off, bottom is 3.6.0-a2+3 with 0.045mm PA):
I'll try to crank up some acceleration and jerk later today and see how that plays out.
But I must say that the delay after a probe move is somewhat annoying lmao.
Dodged the bullet this time!
Took the board out and cleaned it off repeated times with some Würth electronics cleaner and blowdried it with compressed air.
When i hooked it back up again everything except the Y stepper moved. Turned out that the Dimafix had soaked into a allready bad crimp on the molex connector, so with that re-cripmed it's now all good again
Would be really nice to have the current volumetric flow displayed in the status area of the DWC in the same way as the rest of the info.
Is this something that could be implimented down the line? Both requested and actual.