Thanks @dc42 for all your help, it now works great.
Will be even better when we can use variables.
What would be a good source to learn the syntax of the commands used for conditional gcodes?

@dc42 Is this still on the to-do list or has it been implemented?

great, thanks, looks like I'll have to figure out another way as andromeda is too unstable 😞 ..

@dc42, thanks for your help
This is the line I want to display on the screen.
M291 P"auto bed levelling using 3 Z motors completed deviation " ^ move.calibrationDeviation.deviation ^ "mm"
this is the error
Error: Bad command: M291 P"auto bed levelling using 3 Z motors completed deviation " ^ move.calibrationDeviation.deviation ^ "mm"

and then I thought that it needed a ","
M291 P"auto bed levelling using 3 Z motors completed deviation ", ^ move.calibrationDeviation.deviation ^ "mm"
this is the error
Error: Bad command: M291 P"auto bed levelling using 3 Z motors completed deviation ", ^ move.calibrationDeviation.deviation ^ "mm"

Not knowing much about code, I am stuck.

But that would be pull instead of push, I would like the printer to be able to communicate events at the point of time when they happen. Push whenever an event happens would consume much less resources than contineously pulling...

its not a current feature, but its all open source and for the most par well documented so nothing stopping you from polling the status and creating a log.

Sweet! some work left on the laser but will make a note to test with caution and report back if no one beats me to it!

@denke If you use G10/G11 firmware retraction, you can set different retract/ unretract distances (and speeds).

A 2Hz signal would require an approximately 0,2Hz time constant for the CP detection circuitry. Completely acceptable for me. 0,02Hz would be acceptable too. But a 2Hz signal is not very useable with other off the shelf hardware unfortunately.

I don't really care where the CP signal is generated and what it's actual frequency is, as long as it is a reasonable reflection of software health state. The tick interrupt handler might be the most convenient place and the most conventient frequency. If it ever proves to be ineffective it can always be improved.

Beats me 🙂 I've always used the 3 screw auto levelling.

Thanks @Danal.

You opened my eyes. Since your last post i thought it is possible to have multiple triggers for the same number.
Double checked this in the code. Tn is definitely the key.

So i have to change my emergency stop triggers a little bit otherwise they are not fully functional.

Recap:
So to copy my X and Y movements 1:1 to a new defined U-axis.

M584 X5 Y6 Z7:8 U0 E3:4 ; set drive mapping first
M584 P3 ; Only show 3 axis (not showing U in web interface)
;Redefine CoreXY kinematics for 4th axis
M669 K1 X1:1:0:1 Y1:-1-1:0:-1 U0:0:0:0 ; CoreXY redefined Adding X movement to U-axis, Adding -Y to U-axis.
;Now U(X-Y)
;M669 K1 X"movement" by (Xmotor):(Ymotor):(Zmotor):(Umotor)..etc..

[Solved !! ]

In my experience, yes. I'd still hook up the tach signal, but you can't trust the RPM reading when controlling the speed. However if I recall correctly it'll still be usable as a running/not running feedback, at least with the fans I tested.

M32 will be fixed for this use case in the next DSF version.

@deckingman said in Steppers PID - NOT heaters PID:

Belt stretch on a 3D printer? Nah - doesn't happen with timing belts from a reputable source.

exactly my point "reputable source"

reputable:
7b95d1d5-79b7-4eb3-bce9-c07f42234a77-image.png

ender 5
1d196b53-490f-4c32-b2a0-a8161d602d27-image.png

noname aliexpress "double price" (marked as high quality) pack for corexy
c8322929-06d9-4552-a201-10ac8d4164cd-image.png

wanhao i3
28db0616-39af-4105-87f2-18d4627780e8-image.png

as you can see there's nothing in the e5 belt for e.g.

the wanhao i3 belt have "something" as reinforcement, that "something" is not glass/kevlar as when you clean the rubber and get to it you find it's syntetic rope hence the stretching

just do a simple test take 1.2m of the belt stretch it over 100cm board, put a pulley at the end, get belt over it and on that 20cm connect a scale. then link the belt around the pulley to indiator and null it, load the scale slowly and measure how much the belt stretch for each weight you add .. do that for few different PRC belts and do it with gates (unitta) or any other brand name and compare results ... I did .. 10kg on gates and my 0.001mm indicator did not move .. these "syntetic rope" reinforced ones and it starts moving after 100g 😞

extract the reinforcement from generic belt
e1a6d900-c473-487b-8086-7fce7adebf1a-image.png

you will see it's not glass, it's standard syntetic rope

Thank you for the explanation re multi material. SInce I am currently struggling with registration of two nozzles due to a slight bend in a heat break, I can fully appreciate this. Further, when it comes time to a set up a multi head system, I can see this feature to become critical.

Phaedrux, thanks for moving this onto the wish list.