Can I Connect Aspire Directly To My CNC Machine?
Aspire does not run a machine. It writes a toolpath, then a post processor turns that toolpath into G-code your controller can read. This page covers the handoff, the settings that decide whether it works, and the cases where it does not.
No direct link, but a clean handoff
Vectric Aspire is CAM software. Your CNC runs on G-code. The bridge between them is a post processor file.
Aspire writes a file, not a motor command
Aspire takes your vectors, 3D models and toolpath settings and calculates cutter positions along each pass. What it produces at the end is a text file of G-code: G0, G1, G2, M3, M5, spindle speed, feed rate, tool change lines. Nothing in that file moves an axis on its own.
The machine controller reads the file and drives the motors. A hobby router might use GRBL on an Arduino-class board. A benchtop mill might run Mach3 or UCCNC on a PC. Production routers usually carry a dedicated unit such as WinCNC, LinuxCNC or a Fanuc-style control. Aspire never talks to any of these directly.
Matching the post processor to your controller
The post processor is a small script that tells Aspire how your specific controller wants its G-code formatted. Two machines can run the same toolpath and need different output, because one wants a line number on every block and the other does not. Get this file wrong and the machine either refuses the program or cuts in the wrong place.
Major brands ship ready-made posts. ShopBot, Haas, AXYZ, Multicam and most Chinese routers have a profile in the Aspire list. Pick your model from the dropdown and you are usually done.
A generic or DIY machine is the hard case. You start from a GRBL or Mach3 post and edit the header, the arc handling and the tool change lines until the output matches what your controller accepts. Change one thing at a time and keep a copy of the original.
- 1Arc modeChoose between G2/G3 arcs and linearized segments; wrong choice shows up as faceted radii.
- 2UnitsInch and metric posts are separate files. Mixing them scales the part by 25.4×.
- 3Tool changeManual, automatic or none. A post that emits T1 M6 on a manual machine will just stall.
Getting a job from Aspire to the machine
Work in Aspire until the toolpath preview looks right. Check the stock size, the datum position and the tool numbers against what is actually loaded in the machine. A wrong zero point is the most common reason a first run cuts air or cuts the table.
Save the toolpath with the correct post selected. Aspire gives you a .tap, .nc or .gcode file depending on the post. Then load that file into your controller software, not into Aspire. Aspire is finished at that point.
Run the program in the air first, with the spindle off and the Z zero set well above the stock. Watch the X and Y moves match the preview. Only then set Z to the real work surface and cut.
If your controller is network-connected, you can push the file straight over Ethernet from the shop PC. The G-code still has to pass through the right post. The transfer method never changes the syntax.
Which transfer route fits your machine
Pick the row that matches your controller, then confirm the post processor name in Aspire.
| Controller | Typical link | Post to select | Watch for |
|---|---|---|---|
| GRBL (Arduino-class) | USB serial | GRBL (mm) (*.gcode) | Baud rate mismatch, buffer stalls |
| Mach3 / Mach4 | Parallel or USB | Mach2/3 Arcs (mm) (*.txt) | Arc mode, active plane |
| UCCNC | Ethernet or USB | UCCNC (*.nc) | Tool change macro conflicts |
| WinCNC | Ethernet | WinCNC (*.tap) | Header and speed codes |
| LinuxCNC | Ethernet | LinuxCNC (*.ngc) | G64 path blending tolerance |
| Fanuc-style control | Ethernet or drip feed | Fanuc (*.nc) | Line numbers, M30 end block |
When the file loads but the cut is wrong
The machine stops mid-file. That is usually a buffer problem on serial links, not a bad toolpath. Drop the baud rate one step, or split the job into two files. Long 3D reliefs push a lot of short moves through a narrow pipe.
Axes run the wrong way or the part comes out mirrored. This is a post or controller setting, not an Aspire modelling error. Check the axis direction bits in the controller before you touch the design.
The cut is undersized or oversized by a fixed ratio. Almost always an inch and metric mismatch between the post and the controller. Fix the units in both places and re-post the file.
Corners come out faceted on a curve. The post is linearizing arcs, or the controller tolerance is too coarse. Switch to G2/G3 output if the controller supports it, or tighten the blending tolerance.
Depth is wrong on the first pass only. The Z zero moved between setup and run, or the material surface is not flat. Re-zero on the actual stock and check for swarf under the plate.
Common questions
Can Aspire send G-code straight to my CNC over USB?
No. Aspire saves a file. Your controller software, or the controller itself, sends the motion commands.
Some workflows feel direct because the shop PC and the machine share one screen. The G-code still passes through a post processor first.
Do I need a different post processor for each machine?
Yes, if the controllers differ. A GRBL router and a WinCNC router want different headers, arc codes and end blocks.
If two machines share the same controller and firmware version, one post usually covers both.
Why does the same file cut fine on one machine and stall on another?
Look at the link speed and the controller buffer, not the toolpath. Serial connections at 115200 baud can starve on files with thousands of short moves.
A network-connected controller handles the same file without a pause.
Can I run a simulation with the machine still connected?
We disconnect the control cable before any dry run or simulation. A stray command during a preview can send the Z axis down at rapid speed.
Set Z zero high above the work and keep a hand on the feed hold until the first pass is proven.
Does the post processor affect surface finish?
Indirectly. It sets arc output, blending tolerance and feed codes, which change how smoothly the tool follows a curve.
Tool geometry, stepover and spindle speed do more of the work. A good post just stops the controller from adding its own errors.
What if my machine has no post processor in the Aspire list?
Start from the closest match, usually GRBL or Mach3, and edit a copy. Adjust one parameter at a time and keep the original file.
Send us your controller model and G-code sample, and we can tell you which syntax differences matter.
Need parts cut to a real tolerance?
Send your model and we return a quote with DFM notes within 12 hours.
12-hour quote100% inspection±0.005 mm
