CAM ToolBit Library: Difference between revisions
(Created page with "{{Page in progress}} {{Docnav <!-- |Simulator |Complete Loop |Path |IconL=Path_Simulator.png |IconC=Workbench_Path.s...") |
No edit summary |
||
Line 24: | Line 24: | ||
==Description== |
==Description== |
||
A tool library is a (JSON) file with a mapping of tool id to the path of the toolbit file. As a consequence each toolbit can be in multiple libraries and doesn't have an id of it's own. The id is a property of the library. |
|||
Due to each tool being stored in its own file and the storage/organization of those files being quite flexible the importance of a tool library for organisational purposes is quite diminished. The user is free to organise their tools in whichever directory hierarchy they see fit and can also name them as best fits their use and organisation. A tool library is nevertheless a great representation for a physical grouping of tools, such as in an automatic tool changer. |
|||
==Usage== |
==Usage== |
||
==JSON Structure== |
|||
{ |
|||
"tools": [ |
|||
{ |
|||
"nr": 1, |
|||
"path": "t1.fctb" |
|||
}, |
|||
{ |
|||
"nr": 2, |
|||
"path": "t2.fctb" |
|||
}, |
|||
{ |
|||
"nr": 3, |
|||
"path": "t3.fctb" |
|||
} |
|||
], |
|||
"version": 1 |
|||
} |
|||
==Options== |
==Options== |
Revision as of 15:31, 24 October 2020
This documentation is a work in progress. Please don't mark it as translatable since it will change in the next hours and days.
{{{Name}}} |
Menu location |
---|
None |
Workbenches |
{{{Workbenches}}} |
Default shortcut |
None |
Introduced in version |
- |
See also |
None |
Description
A tool library is a (JSON) file with a mapping of tool id to the path of the toolbit file. As a consequence each toolbit can be in multiple libraries and doesn't have an id of it's own. The id is a property of the library.
Due to each tool being stored in its own file and the storage/organization of those files being quite flexible the importance of a tool library for organisational purposes is quite diminished. The user is free to organise their tools in whichever directory hierarchy they see fit and can also name them as best fits their use and organisation. A tool library is nevertheless a great representation for a physical grouping of tools, such as in an automatic tool changer.
Usage
JSON Structure
{
"tools": [ { "nr": 1, "path": "t1.fctb" }, { "nr": 2, "path": "t2.fctb" }, { "nr": 3, "path": "t3.fctb" } ], "version": 1
}
Options
User documentation
- Getting started
- Installation: Download, Windows, Linux, Mac, Additional components, Docker, AppImage, Ubuntu Snap
- Basics: About FreeCAD, Interface, Mouse navigation, Selection methods, Object name, Preferences, Workbenches, Document structure, Properties, Help FreeCAD, Donate
- Help: Tutorials, Video tutorials
- Workbenches: Std Base, Arch, Assembly, CAM, Draft, FEM, Inspection, Mesh, OpenSCAD, Part, PartDesign, Points, Reverse Engineering, Robot, Sketcher, Spreadsheet, Start, Surface, TechDraw, Test Framework, Web
- Hubs: User hub, Power users hub, Developer hub