This documentation is not finished. Please help and contribute documentation.
GuiCommand model explains how commands should be documented. Browse Category:UnfinishedDocu to see more incomplete pages like this one. See Category:Command Reference for all commands.
See WikiPages to learn about editing the wiki pages, and go to Help FreeCAD to learn about other ways in which you can contribute.
CAM Sanity |
Menu location |
---|
CAM → Check the CAM job for common errors |
Workbenches |
CAM |
Default shortcut |
P S |
Introduced in version |
0.19 |
See also |
None |
Many CAM users are hobbyists and DIYers. As such, they use their CNC machines to run G-code that they configured and generated themselves. That isn't the case for most professional/commercial users. In professional shops, different people are responsible for creating the G-code (CNC programmers) from those who run it on the machines (CNC operator).
Hobbyists usually run the G-code just a few minutes after post-processing it and probably only once or twice. In a professional shop, proven G-code may be run many times for months or years after initially generated.
One issue that arises in a professional CNC shop is that there are many assumptions made by the programmer that are NOT communicated in the G-code itself. For example, the G-code can call for a tool "T3" but unless its commented, the G-code doesn't say what kind of tool "T3" refers to. It's just assumed that T3 in the CAM system is the same as T3 on the machine. There are many assumptions like this involving machine setup, tooling, material, part orientation, etc. Even if the G-code is perfect, if the operator doesn't set up the machine with the same assumptions, it can crash.
Commercial shops will often create a 'setup book' which documents all these assumptions and gives the operators what they need to configure the machine and produce a part.
CAM Sanity is the tool in CAM workbench to generate this kind of information. The output of this command is a stand-alone .html file with embedded images.
Above: Example of a CAM Sanity generated report
As much as possible, the content is FreeCAD agnostic. The CNC Operator may never use FreeCAD so FreeCAD/CAM specific terminology is confusing. The report has distinct sections and is formatted to make finding things easy and predictable.
This section gives an overview of what is being made. Ideally the image should show the base objects. If there are multiple base objects, the image should show how they nest.
Gives a quick view of minimum and maximum heights and run times.
Details the Stock object from the Job. This is an area where CAM would benefit from some improvement. A rudimentary material property for the stock would be useful here and could also be used to help suggest feeds/speeds.
Has subsections for each tool number used in the job. It details what the programmer assumes the tool to be and which operations are using it. This section only works with the new Toolbit system. This is another area where CAM needs improvement. Specifically, Toolbits need additional attributes about the tool like manufacturer/url/part number.
Gives details about where and when the G-code was post-processed. It also shows whether the job contains optional/mandatory stops so the operator knows if it's safe to walk away from the machine during a run.
What kind of coolant, if any, is required.
Shows the parts in the context of the stock envelope and also shows the Part origin.
Warnings and errors detected by CAM Sanity. These may or may not be problems but they're noted for additional attention. For example if the same tool number is used for different toolbits, it will show as an error. If a tool controller has no feed/speed configured, it will appear as a warning. It will also detect and warn about unused tool controllers. CAM would benefit here from the ability to add arbitrary notes or warnings.