Incorrect H # in g code

[Anonymous]

When I write up a program and post it and transfer it to my tormach mill, the H in the top of the g code is always H1 . I have my tool live matching the tool library on the machine,  if I edit the g code and enter the tool number in place of the 1 in the g code, it works fine. If someone could help me out I'd certainly appreciate it. 

[Anonymous]

I hear ya, how do I update it. I renumbered all the offsets in my library but I don't know how to update it.

[HughesTooling]

Are you using Windows, if you are do you know about the snipping tool it'll make screen grabs a lot easier.

If you've updated the tool in the document when you edit the op and pick select tool in the tool manager it should look like this. I attached you file with the tool updated give that a try.

Mark

[HughesTooling]

---

tbevins wrote:
I hear ya, how do I update it. I renumbered all the offsets in my library but I don't know how to update it.

---

When you open the tool manager your Document libraries will be at the top, just double click each tool in the document library and update as well. You'll have to go through all your documants and update.

Mark

[tmodcustoms]

Got it, Thanks again bud!

[amcfarlen]

No I hadn't updated the tools in that file. So when I did and reposted everything has been updated. 

It's always a good day when you learn something new. Thank you.

[Laurens-3DTechDraw]

I've found what went wrong.

It should normally make the length offset default to your tool number. This is true when you make a new tool. But the Fusion Tool library is filled up with sample tools the moment you install.

These tools have tool number 0 and it will stay 0 for the length and diameter offset for some reason when you change the main tool number.

See the video.

Jeff or Dave could you write this up because this will cause a lot of crashes?

You would expect the system to always keep the Length and diameter offset the same unless deliberatly changed by the user.

[Anonymous]

👍👍👍

[amcfarlen]

Yes, I would have assumed so as well. I would hope that this gets picked up as something that needs to be remedied in a future update.

I also noticed that all the feeds and speeds that are in the sample library do not carry over when you build up copy at tool to your own library. The speed always defaults to 5000 and feeds to 1000.