Change Z-babystepping to Y-babystepping for Belt printers.

NAK_3D

@dc42 That would make dialing in a belt printer much easier... I would be more than happy to test the feature should you implement the ability to baby step the y-axis.

NAK_3D

@dc42 I was just on a live stream with Scott Lahteine from Marlin.. He told me that with Marlin if you enable "Babystep_XY" it will let you babystep all axis.. I know currently this feature is not supported by RepRap.. Any chance you guys have the pull to get this feature supported as well as I believe this would resolve my problem.. Thanks

dc42

Please remind me again about a week from now. Just to be clear, do you need to babystep Y while the print is running, or would you do it before starting the print?

NAK_3D

@dc42 I will do my best to remember to remind you in a week... As for when I would use babystepping, both would be nice but I see it being used more during the print for my application.

dc42

@nak_3d, wouldn't babystepping during a print give you a Y layer shift as well as adjusting the Z height?

NAK_3D

@dc42 I suppose you might see a slight shift but I'm wanting to be able to adjust for flow variances that effect first layer adhesion..so I'd only be using it to make small adjustment in the first few layers... If you've never seen a belt printer running it may be hard to grasp, but on each layer only 1 line moving across the x-axis touches the bed.. the z-axis moves horizontally away from the nozzle while the y-axis varies the distance from the bed moving on a 45 degree angle.. So the only way to compensate for bed adhesion is to slightly adjust the Y axis.. Hope this all makes sense...

NAK_3D

@dc42 This is your friendly reminder one week later..

dc42

Thanks for the reminder. Can you confirm that your machine uses a single Y motor, that affects nothing other than the Y position?

NAK_3D

@dc42 Its a CoreXY design.. I do believe two motors have to run to go a single direction.

dc42

@nak_3d said in Change Z-babystepping to Y-babystepping for Belt printers.:

@dc42 Its a CoreXY design.. I do believe two motors have to run to go a single direction.

That complicates things, if you want the babystepping to work quickly.

I've implemented changes to the M290 command in my latest internal build to allow any axis to be baby stepped. Currently it will only attempt to apply baby stepping to existing moves in the queue for the Z axis. So Y baby stepping will work on a CoreXY machine, but you will need to wait for existing moves in the queue to complete before it takes effect.