I am just using babystepping as a workaround until I figure out my probe offsets. I understand that this is not what baby stepping is for.
The behaviour of the M290 command was just different from what I expected. I think there should be a hint in the documentation what the command can do. It confused me quite a bit that I can add even .01mm with relative babysteps, but only full mm with absolute steps.

Forgot to mention: I am on version 1.21

Hi,

I am trying to set Z baby steps in my config.g:
M290 R0 Z1.23 (for example)
That results in an offset of 1mm (as displayed in DWC and in the gcode console).

M290 R0 Z0 does reset the offset to 0mm.
A manual M290 R0 Z1.23 results in the same offset: 1mm
https://www.dropbox.com/s/0a6txpzsxvjgik2/Screenshot 2018-04-24 11.21.55.png?dl=0

What does work is setting the offset step by step:
https://www.dropbox.com/s/os20xd2rge3pzd7/Screenshot 2018-04-24 11.23.21.png?dl=0
M290 Z1.6 (offset is now 1mm)
M290 Z0.23 (offset is now 1.23mm)

There is no difference in using Z or S as parameter for M290.
The up and down buttons in DWC are working as expected.

Am I missing something here?

Best regards,
Paul