Tool z offset doesn't update

I measured a tool I had and entered a Z offset in the tool table. The machine knows that the tool is in the spindle. However, in manual mode, the tool information section doesn't use the new Z offset, it shows 0. It has the name of the tool and its position but doesn't update its length. This persists even when I restart the control. The tool length is visible in the tool table, but not in the tool information. It also doesn't affect the position of the spindle on the DRO. The tool was previously created as having no offset.

You need a G43

When I type G43 H1 in MDI, the tool information still shows 0 under Z offset. There's also no difference on the DRO between G53 H1 and G49.

Have you connected the gmoccapy toolofset pin in your postgui hal?
Just see the sample file in the sim config folder for the exact names.

And i recommend not to use G43 H1, but just a G43. That will pull the offsets for the tool in spindle not the value according to the index you submit with tbeH value.
Just think about editing a ngc file and you change tool 1 to tool 2 if you forget to change also the index, you will have a crash for sure.

Norbert

Thanks Norbert, I copied a line from the sample config and now the Z offsets change.

Now I have another question, is it possible to use the manual tool change component?

I have a hydraulic tool clamping system but no ATC. When I program an M6 code in MDI, the machine disables most of the commands and I have to switch it off, then turn it on again. I assume it's because it's waiting for an imaginary ATC toolchange to complete, or because it wasn't programmed in hal to know what to do.

I tired using the userspace manual tool change component, and it loads on start up, but the behaviour of the machine is unchanged. There is no prompt or confirmation button, which makes the machine stay in tool change mode indefinitely.

Do you know, that i did write quite a lot of documentation?

Does This help.

Norbert

Norbert,

No one reads the docs any more lol...

JT

@john,

not writing doku would save a lot of time :whistle: :S :evil:

Norbert

Yes you did, along with the 700+ pages of the main LCNC documentation and several hundred pages of Mesa board manuals, all of which I've read and thoroughly memorised in the past three weeks, always remembering where every bit of info is stored. /sarcasm