@dc42 Thank you! Glad to know it wasn't just a mistake on my end.

@mikeabuilder

I prefer the macro because
1- Cura doesn't have conditional gcode
2- I can use the macro with any Slicer without changing it

Brilliant, thank you both, @achrn and @zapta

@ben-0 https://docs.duet3d.com/en/User_manual/Connecting_hardware/Z_probe_auto_levelling

As always thank you for your prompt reply!

There may be more creative ways to do what you want using conditional gcode and daemon.g as you said, but if the simple method works for you, that's great.

@audryhome which firmware version are you using? Please try firmware 3.4 if you are not already using it.

@ti21 I think the M585 command may be what you are looking for. https://docs.duet3d.com/en/User_manual/Reference/Gcodes#m585-probe-tool

@oliof that isn't supported. You would need to define your own kinematics class instead.

@oliof Thank you very much for your advise it worked great.

The location of an axis is found with this
move.axes[n].machinePosition

Returns null if the position is unknown (machine not homed).

All looks good provided that your actual files are indented correctly
Otherwise each command will just execute sequentially

if job.file.fileName == null M99 if {{global.filamentProgress + 11500.0} <= move.extruders[0].position} ; set global.filamentProgress = {move.extruders[0].position + 11500.0} M106 P0 S255 G4 S3 M106 P0 S0

@owend Oh yeah, I have overread this! Thank you...I had expected this to be a "function" like length() or var.length ...
mea culpa for to scanning the docs more intensively.

https://docs.duet3d.com/en/User_manual/Reference/Gcode_meta_commands

@chrishamm yes, I did know about the H0, it was just while testing and trying to isolate the cause. I even tested with M564 Sx as I sometimes have a negative Z coord as starting position and wanted to react properly - as G1 then would not do anything at all. Adding comments to the docs is really welcome...what is with sensors (endstops) when G0/G1 are involved?
Nevertheless I a ma a great fan of the DUET + RepRap (currently at RRF 3.4) and appreciate the fantastic community!

M308 S1 P"temp1" Y"thermistor" A"HotEnd" T100000 B3950 ; configure sensor 1 as thermistor on pin temp1 M950 F1 C"out5" Q50 ; create fan 1 on pin out5 and set its frequency M106 P1 C"HOTEND" S1.0 H1 T50 ; set fan 1 value. Thermostatic control is turned on

H1 - Enable thermostatic mode and select sensor monitored. Relates to the sensor number(s) created by M308.
T50 - Set thermostatic mode trigger temperature 50C.

https://docs.duet3d.com/en/User_manual/Reference/Gcodes#m106-fan-on

@moth4017
Go to settings and start the built in object model browser plugin.
You will then see the browser listed
Capture.PNG
This will let you see the object model and drill down to get the info you need.
If you select a value, the correct path can be copied to the clipboard using the copy button at top right.
Screenshot 2022-04-03 105251.png