Thanks once again @Phaedrux.
I honestly thought it was not being applied as it went 0.25 then to 0.20.
Is there a way to show the actual height as opposed to the corrected height, ie 0.25? For me it confirms that I have my settings in Cura correct.

(Damn, I had a 5 minute video, powerpoint presentation and the likes to show how it was not working!! 😉 )

I have a similar problem with one of my Ormerods and hadn't considered nozzle axis to bed normal alignment or more the the point variation.

Thanks! I will focus on my custom with a v-slot x-arm from now on and 'fix' the sloppy x-carriage another time.

@deckingman said in Z-Probe Trigger Height - Adjust for different materials?:

@pprovost

What @Phaedrux said.

IMO, if you need to adjust the first layer height to suit different filaments, then the use of baby stepping would be a better approach. You can still do that in your slicer start gcode but if you do it that way, then I would recommend that your slicer end gcode applies the reverse baby stepping so that every print starts from the same datum point.

I agree, IMO the M290 babystepping command with R0 to apply absolute babystepping is the best way to do this.

@dc42
AH!
Found all those "old" forum-talks where this wasn´t fully implimented like after RRF1.21
THANKS!
Will try all and report back 🙂