Changing Fixture Offets

Tom,

My KFlops have been worling so well the last few years, I've had a hard time getting motivated to go in and fix the handful of bugs. One of the most annoying bugs is in setting fixture offsets. I can double-click on a DRO, and type in a new value, which then sets the corresponding fixture offset using G10L2. This works just fine, except for the Z axis, when a tool length offset is in effect. The net result, I believe, is the tool length offset ends up getting added in a second time. Having not looked at the code in at least two years, I'm not clear on exactly how to correct this. Can you give me a push in the right direction?

Regards,
Ray L.

Hi Ray,

I haven't looked at your code lately either :)

Are you using the .NET interface? There is an Interpreter Property called "ToolLengthOffset" that you can probably subtract from what you are setting your fixture offset to.

HTH
Regards

Tom,

Thanks! I'll give that a look. I assume that property will give me the current tool length offset, if G43 is in effect, otherwise 0?

The correct approach would then be to pass a Z value to the G10 that was equal to the new Z position (DRO value), minus the current Z position, minus the current ToolLengthOffset?

Regards,
Ray L.

It was indeed just that simple. Now works perfectly!

Regards,
Ray L.

Maybe you can help me as well. When I set my Z to zero it seems ok. But most times, when the machine starts to run the job it then cuts in the air. Why does it do that? What should I look for?

Hi Antennas,

What Hardware/Software are you using? What are you doing to Zero the Z axis? What is your GCode?

Regards

I have a tb6560 board that is modified. Mach3. I used the auto zero script off the forums, but it does it even if I manually zero as well.
Is there a tool length somewhere? I looked around but didn't see anything. All tools are tool 1.

Hi Antennas,

So you don't have a Dynomotion KFLOP controller? But regardless I believe the Mach3 "Zero" buttons compute a "work" (sometimes called "fixture") offset for the currently selected work offset. You can see this by looking at the "Offsets" screen or by looking at the "Diagnostic" screen. Maybe your GCode switches which work offset to be a different set of offsets from the one you "zeroed".

HTH
Regards

Ok thanks ill look in there!