New tool library format

[Anonymous]

As per the May 7th update (http://www.autodesk.com/products/fusion-360/blog/may-7-2016-update-whats-new/), the format for exported tool libraries has changed from JSON to some kind of binary format. This is fine for re-importing into Fusion, but it just broke the tool I wrote for converting the library file into a LinuxCNC tool table file meaning I have to manually add new tools which is a pain.

Is there some kind of format specification for the new tool library format so I can convert it into other formats?

[Anonymous]

Thats kinda scary.. I wondered if that change is what has thrown off my tool accuracy. I tell the machine to bore a one inch hole with a half inch end mill and it is undersized by several thousandths, I am running a haas.

[ekinsb · Accepted solution]

I just asked about this and found out the new format isn't really a new format at all but is the old JSON file zipped up.  If you change the extension of the .tools file to .zip, you can extract the JSON file out. You also need to be aware that the format of the tool library is not published and could change at any time.  I know it's the only option you have now, but you should be aware of the risks.

[Anonymous]

Does this go for tools that are manually put into the system by me? Or only the tooling samples that are provided? What I enter should not change.. That can seriously damage our machines.

[Anonymous]

Thanks for taking the time to find out about this ekinsb. I've patched my tool to look for a ZIP archive and it works great.

I'm aware of the risks of parsing an undocumented format, but if it means I can be lazy and not hand-type a tool table once in a while I'm fine with that.

The tool is hosted on Github if anyone's interested: https://github.com/jamwaffles/FusionToolTranslator

[Anonymous]

Wish I had found this earlier.  I wrote my own tool to do just this.  It's in Python.  Check it out if you have interest.  I looked at your script.  https://github.com/ntc490/fusion360/