Docs menu: acceptance

Docs › Command line › acceptance

acceptance

Write the acceptance test program for a controller: a short job that exercises everything a post writes, so unit, arc and tool-change problems show up on scrap rather than on a real part.

Synopsis

nativecam-cli acceptance [machine.nativecam] [--controller name] [--sender name]
                         [--units inch|mm] [--tool-change m6|pause|atc] [-o out]

Description

The program has a square, circles from 1 to 50 mm radius in all four quadrants, a helix, a 3-second dwell and two tool changes. It's posted for the machine you describe and checked like any export, then written to a file. The same program is on the last page of the app's setup assistant.

The machine starts as the one in machine.nativecam if you give a project, or NativeCAM's default (an Avid PRO6060 with Mach4) if not. The options then change it.

Options

OptionDescription
machine.nativecamOptional project whose machine to use: controller, units, tool changes, spindle and travel.
--controller <name>The controller to post for (names below). Makes the machine a custom one.
--sender <name>With a Grbl-family controller: the program that sends files to it, such as gSender or CNCjs. It decides whether a tool change can stop the job. Only read together with --controller.
--units inch|mmThe units the G-code is written in. Match your controller's setting.
--tool-change m6|pause|atcHow tools change: m6 by hand on M6 (touch plate or tool setter), pause by hand at an M0 pause, or atc with an automatic tool changer.
-o <path>Output stem; the extension is replaced with the controller's. Default: acceptance-<controller> in the current folder, for example acceptance-linuxcnc.ngc or acceptance-carbide-motion.nc.

Controller names

NameControllerStatus
(leave out)Avid's Mach4 profile, the defaultRun on a real machine
grblGrbl 1.1From documentation and firmware source
grblHALgrblHALFrom documentation and firmware source
fluidNCFluidNCFrom documentation and firmware source
carbideMotionCarbide MotionFrom documentation and firmware source
linuxCNCLinuxCNCFrom documentation
massoMassoFrom documentation
centroidCentroid CNC12From Avid's EX posts
buildboticsBuildboticsFrom documentation
openSBPShopBot (OpenSBP part files)From ShopBot's command reference and vendor posts
richAutoRichAuto DSPConservative

Names are case-sensitive. For Avid's Mach4 profile, leave --controller out: mach4 means a generic Mach4 machine, which NativeCAM has no post for. Names without a post stop with the reason and status 1, for example NativeCAM can't write G-code for UCCNC yet, so this job can't be exported…

Examples

$ nativecam-cli acceptance
Avid CNC Mach4 acceptance test -> acceptance-avid-mach4.tap
$ nativecam-cli acceptance --controller grbl --sender gSender --units mm
[warning] G-code: Line 14: Whether M6 stops for the tool change depends on the program sending the file. Make sure yours pauses on M6. (2 more lines like this.)
Grbl via gSender acceptance test -> acceptance-grbl.nc
$ nativecam-cli acceptance --controller centroid --tool-change atc -o centroid-test
Centroid CNC12 acceptance test -> centroid-test.cnc

Where the controller can't stop for a tool change (stock Grbl with no sender named, ShopBot without a tool changer, RichAuto), the test is split into one file per tool:

$ nativecam-cli acceptance --controller grbl
Grbl acceptance test -> acceptance-grbl 1 of 3 - T1.nc
Grbl acceptance test -> acceptance-grbl 2 of 3 - T2.nc
Grbl acceptance test -> acceptance-grbl 3 of 3 - T1.nc

From a project you've already set up, so the test uses exactly your machine:

$ nativecam-cli acceptance my-job.nativecam

Running the test

  1. Run it in check mode where the controller has one (Grbl's $C).
  2. Run it as an air cut, above the material.
  3. Run it 0.5 mm deep in scrap and measure the circles. Unit and arc errors show up in their sizes, and re-zero errors in the depth after each tool change.

Results from your own machine are what move a controller from "from documentation" to tested. Please report them, good or bad.

Exit status

0 when the program was written; warnings don't change this. 1 when the project can't be read, there's no post for the controller, or the file can't be written.