CNC controller and CAM handover before buying from China

A CNC software handover needs the exact tested controller, CAM/post combination and reproducible files. Keep technical compatibility, software rights and future support as separate commitments; a demonstration on the seller’s laptop settles none of them by itself.

Separate delivered compatibility from support ownership

A ready-to-run machine and a used unit can arrive with equally convincing videos but different rights and support arrangements. Obtain a written handover for this transaction rather than assuming the original buyer’s account, training or service entitlement transfers with the hardware.

Do not request another customer’s account credentials or treat copied proprietary files as a legitimate deliverable. Where the provider supplies official downloads rather than installers, preserve the required version and how it remains obtainable. An update subscription, a delivered post file and troubleshooting labor are separate cost lines.

If an old controller cannot provide an exportable backup, ask for a bounded replacement proposal rather than inventing a recovery promise. The resulting scope may be acceptable to the buyer, but the dependency and potential extra work should stay visible. This adds an ownership and cost decision to the existing technical handover manifest; it is not an activation or machine-configuration procedure.

You are buying the software chain alongside the frame and spindle. If the demonstration runs only on the seller’s laptop, the handover is still unresolved.

Identify every link between your drawing and the machine

Record the CAD/CAM product and version you plan to use, your computer’s operating system, the post processor filename and revision, the sender or control application, and the controller model and firmware. Include the connection method and any required drivers. Ask the seller to check this list against the quoted machine revision, rather than a photograph of a different machine.

Autodesk’s NC Program documentation shows that the selected post and its properties control machine-dependent output, including tool changes and other functions. That is why choosing a post by a similar brand name is insufficient evidence. Autodesk NC Program reference.

Keep software entitlement separate from compatibility. Ask the software provider to confirm the licence terms, activation or transfer process, account owner, permitted use and support arrangements. Preinstalled software or a screenshot of its activation does not establish those details.

Replace “G-code compatible” with a feature checklist

Give each required operation its own row: linear moves, arcs, selected units, work offsets, spindle commands, probing, drilling cycles and the intended tool-change method. Ask the seller to mark each as supported, supported with a documented workaround, or unavailable. Leave unanswered rows marked as unresolved.

For a concrete boundary, the original Grbl v1.1 documentation describes a limited interpreter without canned cycles, variables or a tool database. Some CAM output may therefore need different post settings or explicit moves. This statement applies to the documented original project, not every board advertised as “GRBL,” grblHAL or FluidNC. Confirm the installed implementation. Grbl project wiki.

An unavailable feature you do not need may not make the machine unsuitable. A feature required for every production job must be resolved before you can make a meaningful price comparison.

Give the seller a small, buyer-owned test project

Use a simple project that exercises the required functions without including confidential production geometry. Provide the model, material description, proposed tools and intended work-coordinate convention. Ask the supplier to recommend a safe test and identify unsupported functions before generating the code.

Link the CAM project, the post and properties used, the generated NC file and the recorded execution results. Without the corresponding files, a video shows a demonstration but does not let you reproduce the software chain.

Autodesk advises verifying generated code before machine use and testing individual operations when evaluating a post. Follow the specific machine manufacturer’s procedure with qualified personnel; a purchasing checklist is not authority to run unverified code. Autodesk post testing guidance.

Ask for a usable handover folder

A proposed folder manifest highlights what is left out.

• Machine identity: model, quoted revision and controller/firmware record.
• Software: names, versions, legitimate installers or official download links, and entitlement records.
• Post: exact file, revision or file hash, properties and machine configuration used for the test.
• Controller: manufacturer-supported configuration backup and documented recovery method.
• Test: CAM project, setup sheet, tool list, NC file and results linked to that same configuration.
• Support: contact, language, response scope and who owns a post-related fault.

These are requested deliverables, not a guarantee that every controller has an exportable configuration. If a backup is unavailable, ask how the supplier would restore or replace that exact controller and what records the buyer must keep.

Make acceptance and later changes explicit

Treat file delivery, the software-chain demonstration and dimensional part acceptance as separate checks. Reading a file without an alarm does not prove the part’s dimensions or surface finish. Define the required measurements in the overall machine purchase agreement.

After acceptance, keep the tested software combination together. A later firmware, CAM or post update creates a new combination to check. Do not silently replace the accepted post; record the reason, responsible person and test evidence for each update. Ask whether support includes future CAM versions or only the delivered configuration.

Copy this RFQ paragraph

“Please quote the exact controller and firmware supplied with this machine. Our CAM and computer environment are listed in the attached brief. Identify the post processor and settings, confirm each required function, and provide a supported backup/recovery plan. Please return the CAM project, generated NC file, setup information and recorded test results for the agreed configuration. List licence rights, unavailable functions, extra software costs and post-support exclusions separately. Do not substitute the controller without written approval.”

Add your destination, quantity and required date, then use the CNC quote form. For the broader purchase scope, start with the first CNC checklist.

The original Grbl wiki now identifies that project as discontinued. Retain the installed implementation in the quote; this historical feature example is not a recommendation for ongoing support.

AI-assisted editorial update, 26 October 2026. Sources and bilingual wording were checked with AI assistance; technical acceptance remains with the responsible provider.

Related purchasing decisions: Controller selection context.