I'm just moving to smoothie from the typical ramps setup with Repetier.

@John_Herrington would something like the following work:

custom_menu.babystepdown.enable true #
http://custom_menu.babystepdown.name Babystep_Down #
custom_menu.babystepdown.command G91_G10_L2_P1_Z-.01_G90 #

custom_menu.babystepup.enable true #
http://custom_menu.babystepup.name Babystep_Up #
custom_menu.babystepup.command G91_G10_L2_P1_Z.01_G90 #

No it wouldn’t read the docs on G10 L2 here… http://linuxcnc.org/docs/2.6/html/gcode/gcode.html#sec:G10-L2_
http://linuxcnc.org/docs/2.6/html/gcode/gcode.html#sec:G10-L2_

@Wolfmanjm I see - so Z needs to increment / decrement after every run. Any suggestions on how this can be implemented easily? Maybe I can do something in Octoprint. Does this command skip the buffer - so that the change is instantaneous, or it takes into effect only when it reaches the head of the buffer.

Apologies for so many questions, but this is my first time moving to Smoothie, and am still figuring out stuff

you should be able to do it in octoprint, increment and decrement the value. it acts on any gcode that is received after the change in setting

@Wolfmanjm so doesn’t skip the buffer - I can probably work with that. And, as a last resort, do things properly and not act like a lazy ass :-). Thanks for your help.

G91 does effect G10 in FANUC word, I even tested it on a 15T yesterday.

Like I said I was just spit balling a bit.

Was revisiting this; but turned out that after changing the coordinate system offsets using G10 L2, you need to even issue a G1 Z command. In effect to get psudo-babystepping you would have to give a G1 Z (first layer height) in addition to the G10 L2 command with an incrementing Z value…