Posting a program
Export turns toolpaths into G-code programs and puts them in Projects, ready to load on Control. Nothing is sent to the machine.
Export
- Make sure the toolpaths are current: no red ⚠ in the tree. Regenerate any that are out of date.
- Tap Export in the rail. The Export drawer opens.
- Check the Project name. It starts as the design's name.
- Under Toolpaths, every generated toolpath is ticked, grouped by Tool Run. Untick any you do not want. You can rename a Tool Run or a toolpath here for the export only; the tree keeps its names. A toolpath with nothing generated reads ‹name› — no toolpath and cannot be ticked.
- Tap Export.
When it finishes the drawer closes and a message says Exported '‹name›' — N file(s). The export is listed under Exports in the tree.
Where the programs go
| In Projects | Holds |
|---|---|
| A project named after Project name | The whole export |
| A folder per Tool Run | That setup's programs, in operation order |
‹toolpath›.nc | One program per toolpath |
Exporting again under the same project name replaces that export's files. Each program begins with a comment naming its work offset and where zero is, for example WCS G54 - zero at Top Front-Left corner of stock.
The export report
Double-tap a project under Exports to see it: the project, when it was exported and how many files, and each Tool Run with its .nc files. If you deleted the project from Projects, the report says so in red: Missing in Projects — this project was removed from the machine's Projects.
Refusals
Nothing is written when export refuses:
| Message | Fix |
|---|---|
| '‹op›' is out of date — its inputs changed since it was generated. Regenerate it in the tree and export again; nothing has been written. | Regenerate, then export |
| '‹run›' has an empty stock — the bodies it is sized from are missing, suppressed or rolled back… | Restore the bodies, or set the stock |
| '‹name›' already exists as an imported project — rename the export | Change Project name |
| '‹name›' is running on the machine — stop it before re-exporting | Let the job finish or stop it |
| Exporting requires a signed-in account with an active Prime Motion license… | See License |
With no generated toolpaths, Export shows '‹design›' has no generated toolpaths — nothing to export. Create an operation and generate its toolpath, then export again.
When the design changes
A posted program is a snapshot. If you change the design after exporting, the program in Projects does not change, and Prime Motion refuses to start it: Not started — '‹file›' no longer matches the toolpath it was exported from. Open the design, regenerate, and export again… Regenerate the toolpaths and export again.