Babystepping not moving not matter what

Just complied bugfix 2.0 from last week, flashed my Artillery Hornet but now Babystepping does not move no matter what direction or amount. any ideas greatly appreciated.
#define BABYSTEPPING //SonicBoom 3/24
#if ENABLED(BABYSTEPPING)
//#define INTEGRATED_BABYSTEPPING // EXPERIMENTAL integration of babystepping into the Stepper ISR
//#define BABYSTEP_WITHOUT_HOMING
//#define BABYSTEP_ALWAYS_AVAILABLE // Allow babystepping at all times (not just during movement).
//#define BABYSTEP_XY // Also enable X/Y Babystepping. Not supported on DELTA!
#define BABYSTEP_INVERT_Z false // Change if Z babysteps should go the other way
//#define BABYSTEP_MILLIMETER_UNITS // Specify BABYSTEP_MULTIPLICATOR_(XY|Z) in mm instead of micro-steps
#define BABYSTEP_MULTIPLICATOR_Z 1 // (steps or mm) Steps or millimeter distance for each Z babystep
#define BABYSTEP_MULTIPLICATOR_XY 1 // (steps or mm) Steps or millimeter distance for each XY babystep

//#define DOUBLECLICK_FOR_Z_BABYSTEPPING // Double-click on the Status Screen for Z Babystepping.
#if ENABLED(DOUBLECLICK_FOR_Z_BABYSTEPPING)
#define DOUBLECLICK_MAX_INTERVAL 1250 // Maximum interval between clicks, in milliseconds.
// Note: Extra time may be added to mitigate controller latency.
//#define MOVE_Z_WHEN_IDLE // Jump to the move Z menu on doubleclick when printer is idle.
#if ENABLED(MOVE_Z_WHEN_IDLE)
#define MOVE_Z_IDLE_MULTIPLICATOR 1 // Multiply 1mm by this factor for the move step size.
#endif
#endif

#define BABYSTEP_DISPLAY_TOTAL // Display total babysteps since last G28 //SonicBoom 3/24

//#define BABYSTEP_ZPROBE_OFFSET // Combine M851 Z and Babystepping
#if ENABLED(BABYSTEP_ZPROBE_OFFSET)
//#define BABYSTEP_HOTEND_Z_OFFSET // For multiple hotends, babystep relative Z offsets
//#define BABYSTEP_ZPROBE_GFX_OVERLAY // Enable graphical overlay on Z-offset editor

Have you tried to reset the controller using

In terminal mode send commands
M502 (Factory Default)
Then
M500 (Save Settings) – Saves the settings to EEPROM.

---

Computer Programmer / Electronics Technician

yes, i always use
#define EEPROM_INIT_NOW // Init EEPROM on first boot after a new build.
just downloaded todays bugfix and starting fresh just to make sure it wasn't something corrupted

I can not see anything that would stop baby-stepping from working.
Personally I use

  #define BABYSTEP_MULTIPLICATOR_Z  5       // (steps or mm) Steps or millimeter distance for each Z babystep
  #define BABYSTEP_MULTIPLICATOR_XY 5       // (steps or mm) Steps or millimeter distance for each XY babystep

Because of how slowly baby steps changes using my 3D Printer.
With my lead screws rise of 2mm turn per 360 degree revolution.

---

Computer Programmer / Electronics Technician

that is good to know, wondering if it is actually moving but i am not noticing it because the increments are so small. my other two printers use the same defaults but i can immediately notice the difference in the first layer, only difference is the two sidewinders are touch and the Hornet has an Encoder knob, just flashed a fresh config and i am still see a fat first layer, letting it run a bit with a babystep of -00.102 where normally i am at -00.003

not sure if that is directly affected by something else like #define MESH_EDIT_Z_STEP 0.025 but increasing babystep to -00.190 still gives me a first layer thickness of 0.025 oddly enough

What version of Marlin firmware are you currently working with.

---

Computer Programmer / Electronics Technician

i just downloaded todays Bugfix 2.0.9.3

Hi Sonicboom.

Did you ever get this working? I'm having the same issue.