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.
@Inlinebrother I was working on a refreshed version of pfn's config earlier this year. But then I managed to formate the wrong drive when doing a clean Windows install and lost all that work (+ alot of other projects).
After that i kinda dropped off for a bit, I still got all my notes etc. anf plan to take it up again in the future. But seeing how much TLC the klipper addons have been getting the last year it's not something one person can keep up with porting over to RRF unless it's his full time job.
Still haven't had one single event on 3.5.3-debug other than that one without any output. So I'm moving back over to 3.6.0-debug again so that I can get some prints done.
With nothing happening in well over 72hours I doubt anything will tbh.
Mine had a reset today while I was @work, but the only output in YAT is:
ok<LF>
HTTP is enabled on port 80<LF>
FTP is enabled on port 21<LF>
TELNET is disabled<LF>
CAN response timeout: board 121, req type 6054, RID 8<LF>
Warning: Heater 1 predicted maximum temperature at full power is 543°C<LF>
Log level is : debug<LF>
Done!<LF>
RepRapFirmware for Duet 3 Mini 5+ is up and running.<LF>
WiFi module started<LF>
WiFi module is connected to access point IoT, IP address 192.168.30.x<LF>
HTTP is enabled on port 80<LF>
FTP is enabled on port 21<LF>
TELNET is disabled<LF>
CAN response timeout: board 121, req type 6054, RID 8<LF>
Warning: Heater 1 predicted maximum temperature at full power is 543°C<LF>
Log level is : debug<LF>
Done!<LF>
RepRapFirmware for Duet 3 Mini 5+ is up and running.<LF>
WiFi module started<LF>
WiFi module is connected to access point IoT, IP address 192.168.30.x<LF>
Printed in one line on YAT, I just split it up for readabilty.
This is the M122 report:
2024-10-25 15:56:08 [debug] === Diagnostics ===
2024-10-25 15:56:08 [debug] RepRapFirmware for Duet 3 Mini 5+ version 3.5.3+1dbg (2024-10-20 14:13:46) running on Duet 3 Mini5plus WiFi (standalone mode)
2024-10-25 15:56:08 [debug] Board ID: XNHXF-HR6KL-K65J0-409N2-K9W1Z-RV2MZ
2024-10-25 15:56:08 [debug] Used output buffers: 1 of 40 (39 max)
2024-10-25 15:56:08 [debug] === RTOS ===
2024-10-25 15:56:08 [debug] Static ram: 103368
2024-10-25 15:56:08 [debug] Dynamic ram: 123956 of which 0 recycled
2024-10-25 15:56:08 [debug] Never used RAM 11572, free system stack 142 words
2024-10-25 15:56:08 [debug] Tasks:
2024-10-25 15:56:08 [debug] NETWORK(1,ready,18.9%,209)
2024-10-25 15:56:08 [debug] HEAT(3,nWait 6,0.0%,325)
2024-10-25 15:56:08 [debug] Move(4,nWait 6,0.0%,341)
2024-10-25 15:56:08 [debug] CanReceiv(6,nWait 1,0.1%,773)
2024-10-25 15:56:08 [debug] CanSender(5,nWait 7,0.0%,336)
2024-10-25 15:56:08 [debug] CanClock(7,delaying,0.0%,348)
2024-10-25 15:56:08 [debug] TMC(4,nWait 6,0.8%,101)
2024-10-25 15:56:08 [debug] MAIN(1,running,78.5%,665)
2024-10-25 15:56:08 [debug] IDLE(0,ready,0.8%,29)
2024-10-25 15:56:08 [debug] AIN(4,delaying,0.8%,259)
2024-10-25 15:56:08 [debug] , total 100.0%
Owned mutexes:
2024-10-25 15:56:08 [debug] WiFi(NETWORK)
2024-10-25 15:56:08 [debug] USB(MAIN)
2024-10-25 15:56:08 [debug] === Platform ===
2024-10-25 15:56:08 [debug] Last reset 05:58:26 ago, cause: software
2024-10-25 15:56:08 [debug] Last software reset at 2024-10-25 09:57, reason: HardFault ibus, Gcodes spinning, available RAM 11596, slot 0
2024-10-25 15:56:08 [debug] Software reset code 0x0063 HFSR 0x40000000 CFSR 0x00000100 ICSR 0x00487803 BFAR 0xe000ed38 SP 0x20012038 Task NETW Freestk 494 ok
2024-10-25 15:56:08 [debug] Stack: 2002c620 200324a0 200014e4 00000000 20033689 000304b5 0d0a0d30 61010000 0d0a0d31 00000000 00000000 00000000 200120b8 00000014 000a0ea3 00000102 eeb20050 380aa8c0 080001ad 00000003 00034db1 2002c3b8 2002c3b8 00000001 0002fbf1 20011800 200114f8
2024-10-25 15:56:08 [debug] Error status: 0x00
2024-10-25 15:56:08 [debug] Aux0 errors 0,0,0
2024-10-25 15:56:08 [debug] MCU revision 3, ADC conversions started 16129917, completed 16129915, timed out 0, errs 0
2024-10-25 15:56:08 [debug] MCU temperature: min 35.5, current 35.9, max 38.8
2024-10-25 15:56:08 [debug] Supply voltage: min 3.8, current 24.2, max 24.3, under voltage events: 0, over voltage events: 0, power good: yes
2024-10-25 15:56:08 [debug] Heap OK, handles allocated/used 99/33, heap memory allocated/used/recyclable 2048/580/152, gc cycles 4679
2024-10-25 15:56:08 [debug] Events: 1 queued, 1 completed
2024-10-25 15:56:08 [debug] Driver 0: standstill, SG min 0, read errors 0, write errors 0, ifcnt 13, reads 17785, writes 13, timeouts 0, DMA errors 0, CC errors 0
2024-10-25 15:56:08 [debug] Driver 1: standstill, SG min 0, read errors 0, write errors 0, ifcnt 13, reads 17784, writes 13, timeouts 1, DMA errors 0, CC errors 0, failedOp 0x6f
2024-10-25 15:56:08 [debug] Driver 2: standstill, SG min 2, read errors 0, write errors 1, ifcnt 50, reads 17783, writes 13, timeouts 0, DMA errors 0, CC errors 0
2024-10-25 15:56:08 [debug] Driver 3: standstill, SG min 2, read errors 0, write errors 1, ifcnt 51, reads 17783, writes 13, timeouts 0, DMA errors 0, CC errors 0
2024-10-25 15:56:08 [debug] Driver 4: standstill, SG min 0, read errors 0, write errors 0, ifcnt 13, reads 17785, writes 13, timeouts 0, DMA errors 0, CC errors 0
2024-10-25 15:56:08 [debug] Driver 5: not present
2024-10-25 15:56:08 [debug] Driver 6: not present
2024-10-25 15:56:08 [debug] Date/time:
2024-10-25 15:56:08 [debug] 2024-10-25 15:56:08
2024-10-25 15:56:08 [debug] Cache data hit count 4294967295
2024-10-25 15:56:08 [debug] Slowest loop: 13.34ms; fastest: 0.16ms
2024-10-25 15:56:08 [debug] === Storage ===
Free file entries: 18
2024-10-25 15:56:08 [debug] SD card 0 detected, interface speed: 22.5MBytes/sec
2024-10-25 15:56:08 [debug] SD card longest read time 8.0ms, write time 4.4ms, max retries 0
2024-10-25 15:56:08 [debug] === Move ===
DMs created 83, segments created 0, maxWait 0ms, bed compensation in use: none, height map offset 0.000, max steps late 0, min interval 0, bad calcs 0, ebfmin 0.00, ebfmax 0.00
2024-10-25 15:56:08 [debug] no step interrupt scheduled
2024-10-25 15:56:08 [debug] Moves shaped first try 0, on retry 0, too short 0, wrong shape 0, maybepossible 0
2024-10-25 15:56:08 [debug] === DDARing 0 ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
2024-10-25 15:56:08 [debug] === DDARing 1 ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
2024-10-25 15:56:08 [debug] === Heat ===
2024-10-25 15:56:08 [debug] Bed heaters 0 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0
2024-10-25 15:56:08 [debug] Heater 1 is on, I-accum = 0.0
2024-10-25 15:56:08 [debug] === GCodes ===
2024-10-25 15:56:08 [debug] Movement locks held by null, null
2024-10-25 15:56:08 [debug] HTTP is idle in state(s) 0
2024-10-25 15:56:08 [debug] Telnet is idle in state(s) 0
2024-10-25 15:56:08 [debug] File is idle in state(s) 0
2024-10-25 15:56:08 [debug] USB is ready with "m122" in state(s) 0
2024-10-25 15:56:08 [debug] Aux is idle in state(s) 0
2024-10-25 15:56:08 [debug] Trigger is idle in state(s) 0
2024-10-25 15:56:08 [debug] Queue is idle in state(s) 0
2024-10-25 15:56:08 [debug] LCD is idle in state(s) 0
2024-10-25 15:56:08 [debug] SBC is idle in state(s) 0
2024-10-25 15:56:08 [debug] Daemon is doing "G4 P250" in state(s) 0 0, running macro
2024-10-25 15:56:08 [debug] Aux2 is idle in state(s) 0
2024-10-25 15:56:08 [debug] Autopause is idle in state(s) 0
2024-10-25 15:56:08 [debug] File2 is idle in state(s) 0
2024-10-25 15:56:08 [debug] Queue2 is idle in state(s) 0
2024-10-25 15:56:08 [debug] Q0 segments left 0, axes/extruders owned 0x0000803
2024-10-25 15:56:08 [debug] Code queue 0 is empty
2024-10-25 15:56:08 [debug] Q1 segments left 0, axes/extruders owned 0x0000000
2024-10-25 15:56:08 [debug] Code queue 1 is empty
2024-10-25 15:56:08 [debug] === Filament sensors ===
check 0 clear 0
2024-10-25 15:56:08 [debug] Extruder 0 sensor: no filament
2024-10-25 15:56:08 [debug] === CAN ===
2024-10-25 15:56:08 [debug] Messages queued 193567, received 440879, lost 0, errs 383, boc 0
2024-10-25 15:56:08 [debug] Longest wait 2ms for reply type 6053, peak Tx sync delay 10353, free buffers 26 (min 25), ts 107533/107532/0
2024-10-25 15:56:08 [debug] Tx timeouts 0,0,0,0,0,0
2024-10-25 15:56:08 [debug] === Network ===
2024-10-25 15:56:08 [debug] Slowest loop: 13.86ms; fastest: 0.00ms
2024-10-25 15:56:08 [debug] Responder states:
2024-10-25 15:56:08 [debug] MQTT(0)
2024-10-25 15:56:08 [debug] HTTP(2)
2024-10-25 15:56:08 [debug] HTTP(0)
2024-10-25 15:56:08 [debug] HTTP(0)
2024-10-25 15:56:08 [debug] HTTP(0)
2024-10-25 15:56:08 [debug] FTP(0)
2024-10-25 15:56:08 [debug] Telnet(0)
2024-10-25 15:56:08 [debug] HTTP sessions: 6 of 8
2024-10-25 15:56:08 [debug] === WiFi ===
Interface state: active
Module is connected to access point
Failed messages: pending 0, notrdy 0, noresp 0
2024-10-25 15:56:08 [debug] Firmware version 2.1.0
2024-10-25 15:56:08 [debug] MAC address c4:5b:be:ce:91:93
2024-10-25 15:56:08 [debug] Module reset reason: Power up, Vcc 3.38, flash size 2097152, free heap 39616
2024-10-25 15:56:08 [debug] WiFi IP address 192.168.30.x
2024-10-25 15:56:08 [debug] Signal strength -51dBm, channel 6, mode 802.11n, reconnections 0
2024-10-25 15:56:08 [debug] Clock register 00002001
2024-10-25 15:56:08 [debug] Socket states:
2024-10-25 15:56:08 [debug] 0
2024-10-25 15:56:08 [debug] 0
2024-10-25 15:56:08 [debug] 0
2024-10-25 15:56:08 [debug] 0
2024-10-25 15:56:08 [debug] 0
2024-10-25 15:56:08 [debug] 0
2024-10-25 15:56:08 [debug] 0
2024-10-25 15:56:08 [debug] 0
2024-10-25 15:56:08 [debug] ok
@oliof Uuuuhm, nope:
25.10.2024, 06:51:35 M555
Output mode: RepRapFirmware
I didn't know it was a thing even 😆
@dc42 said in Random Hard Fault resets on Duet 3 Mini WiFi:
@Exerqtor bear in mind that recent versions of YAT do not reconnect automatically when the Duet restarts. I always have to disconnect and reconnect YAT manually using the icons n the menu bar.
Yeah i've made sure to home the printer, and it's still homed. So it haven't been any resets 😅
@dc42 Ok, should i do that too? At least until tomorrow, or do you have enough datapoints on 3.5?
Reverted to 3.5.3 debug and have it running now. Straight off the bat I noticed a difference, when I sent G28Z in YAT to comfirm connection i got ok<LF> in return, but I didn't get anything in return when I input something in the 3.6 debug.
No output in my end what so ever. Has anyone else had outputs with the 3.6 build? 🤔
@dc42 Not really, after I stopped using chrome (other than the occasionall check-in with chrome on my phone) I haven't really had any resets at all that I've noticed.
The laptop have restarted (forced Windows update 🤦♂️) within the last two hours. So i don't know if anything got output in that timespan (no resets though). I've got it back up logging now and plan to have it runnning until the weekend.
I see the debug log has reached 3.21gb by now though. So idk if I maybe should have disabled that.
Going on 22hours since the laptop rebooted, and it's still no output on my end.
@gloomyandy Added that info to the previous post 🙈
@omtek said in Random Hard Fault resets on Duet 3 Mini WiFi:
@Exerqtor With both debug builds I logged a memory difference message within a couple of hours. The first debug build was under an hour, the second took maybe 1-2 hours to show up.
@dc42 said in Random Hard Fault resets on Duet 3 Mini WiFi:
For comparison, my system has logged anything from 0 to 4 memory differences in 24 hours. I have two instances of DWC connected (from Firefox and Chrome running on the same PC) and I reduced the DWC polling interval to 100ms.
Hmm ok, in that case my machine is either really good behaved or I've setup something wrong 
M111 P8 S1 through YAT.It's now been sitting for roughly 22 hours without anything happening. No output in YAT, and no reboot/reset.