Learn/GcodePilot/Running programs
Post to Machine
At a glance
- Post in Plasma, Laser, or Router and the program lands loaded on the machine — no save dialog, no file hunting
- Post while the machine is cutting and it queues for the next run without interrupting
- Each machine has a reorderable program queue; a "Load next?" prompt fires when a run finishes
- Works offline — post to a disconnected machine and it's staged for when you plug in
When the machine selected in a CAM workspace is GcodePilot-controlled, the Post button becomes Post to Machine: it posts the program, switches to that machine's workspace, and loads it, ready to run. Programs are written to a dedicated per-machine spool folder, so each machine keeps its own latest jobs.
The queue
Post while that machine is mid-program and JetCad3 asks whether to queue it for the next run — the current cut is never interrupted, and you stay in CAM. Each machine's queue is visible in its workspace: drag to reorder, remove entries, or clear it. When a program finishes with jobs queued, a Load next program? prompt finds you wherever you are — yes loads the next job ready to run (it never starts cutting on its own).
Post to File and Load from File still exist in the ▾ menu next to Reveal Spool Folder.