OpenChuckCAM User guide
Version: latest Print the guide

10. Post and export the G-code and the setup sheet

  1. Press Continue to post and export, then Post and export… (in the current program, the Post and export… button on the Simulate step; see the note on the first page). The dialog opens.
The Post and export dialog: the Makera Z1 post, one file per setup, the output folder, file name templates and a preview of the start of the program.
Figure 1. The Post and export dialog, with a preview of the start of the program.

The dialog shows:

Post-processor
Makera Z1 writes G-code for that machine (units in millimetres, A as the rotary axis, feed in units per minute). A LinuxCNC post is also available; it is used to check the output in a simulator.
Files
One file for the project, per setup, per operation or per tool. Keep One file per setup here.
Output folder
Where the files go. Type a folder.
File names
The names are made from templates ({n}-{contents} gives 01-setup-1.nc). The defaults are fine.
Files to write
The list shows the file’s lines (here 28,119) and programmed time, and the start of the program so you can read it.
  1. Scroll down to Checks before writing.
The Checks before writing part of the dialog: the tool numbers table, a warning that machine values are not confirmed, and the notice to verify the G-code before running it with the box I will verify this G-code before running it on a machine.
Figure 2. The checks before writing: the tool numbers, the warning about unconfirmed machine values, and the notice to verify the G-code.
  1. Read the warning about the unconfirmed machine values, and the notice “Verify this G-code before you run it.”
  2. Tick I will verify this G-code before running it on a machine (the program asks this once per project on each computer).
  3. Press Write G-code.
The Export result window: Wrote 3 files, listing 01-setup-1.nc, baluster-setup-sheet.html and baluster-setup-sheet.pdf in the output folder.
Figure 3. The result: three files written to the output folder.

Three files are written to the output folder:

  • 01-setup-1.nc: the G-code (about 800 KB for this job).
  • baluster-setup-sheet.html and baluster-setup-sheet.pdf: the setup sheet. It lists the project, machine, stock, held length, tools, operations with their speeds and times, each program file with its SHA-256 hash, and the notice to verify. Compare the hash of a file on the machine with the sheet to be sure it is the file the sheet describes.

Dismiss the result and save the project with File > Save.