CAM Post: Difference between revisions

From FreeCAD Documentation
m (Moved Postprocessor details here from FAQ)
mNo edit summary
Line 8: Line 8:
This command exports the selected [[Path_Job|Job]] to a G-code file.
This command exports the selected [[Path_Job|Job]] to a G-code file.


* Because each CNC Controller speaks a specific G-Code dialect, a Dialect-correct Postprocessor translates from the internal agnostic FreeCAD G-Code. Several Postprocessors are included allowing direct use, or as a templates for modification. Postprocessors contain configuration flags and are designed to be tuned by adding G-Codes and M-Codes to provided definitions for:
Each CNC Controller speaks a specific G-Code dialect, requiring a Dialect-correct Postprocessor to translate the final output from the agnostic internal FreeCAD G-Code dialect. Several Postprocessors are provided, allowing direct use, or as templates for modification. Postprocessors contain configuration flags and are designed to be tuned by adding G-Codes and M-Codes to provided definitions for:
**Machine initialization
**Machine initialization
**Job finalization
**Job finalization

Revision as of 16:32, 18 January 2018

Path PostProcess

Menu location
Path → Project Setup → Post Process
Workbenches
Path
Default shortcut
P,P
Introduced in version
-
See also
None

Description

This command exports the selected Job to a G-code file.

Each CNC Controller speaks a specific G-Code dialect, requiring a Dialect-correct Postprocessor to translate the final output from the agnostic internal FreeCAD G-Code dialect. Several Postprocessors are provided, allowing direct use, or as templates for modification. Postprocessors contain configuration flags and are designed to be tuned by adding G-Codes and M-Codes to provided definitions for:

    • Machine initialization
    • Job finalization
    • Tool-Changes
    • Cooling on /off
    • Etc...

Usage

  1. Select the Job you wish to export
  2. Press the PostProcess button
  3. Confirm the Output File name and directory

Options

  • If output file and post-processor properties are not set in the Job, you can catch up during export
  • You can also export a single Path directly to G-code by using the PostProcess button


Do not use the File->Export menu for export to G-code, it will produce damaged G-code!