Hi dirtdigger257,
I'm not sure why that would be. Backlash should be applied instantly within KFLOP as soon as the Init program is executed to set the backlash values and the axis is enabled regardless of what moves the axis. Backlash correction is applied when moving in the positive direction and not applied when moving in the negative direction. A movement of 0.5% of the backlash amount must be moved for it to be applied or removed.Does anyone know when backlash compensation is used by the G code interpreter?
My problem was when adjusting backlash settings in my init program I could see the changes when jogging the respective axis.
But when I ran test cuts in g code it had no affect even setting to a big value it had no effect when run threw the interpreter
I'am cutting a square and a circle
Using cutter comp
Only after restarting my computer
It would change the backlash amount and rate in Gcode
In case someone else is having this problem restarting the PC fixed it for me
I wouldn't expect it to matter as long as Backlash correction is always set before homing.My other question is, what is the proper sequence for Setting backlash, homing and should I home to the negative or positive limit switch?
I can't think of a reason for this. You might post your homing program and explain how you are measuring this. What if you home twice after a restart?If I home my system set a work offset then home again it's with in a few tenths usually under .0003 of an inch.
If I restart my PC and home it can be off as much as .002