Searching for an LNC controller G-code list runs into the same wall as most controller-specific searches: there is no freely published master reference, because LNC, one of the Taiwanese control builders whose products ship on many Taiwan-built mills, lathes, and routers, documents its controls through the machine builders that integrate them. That does not leave you guessing. It leaves you sorting, because an LNC control runs a Fanuc-shaped dialect, and Fanuc-shaped dialects split cleanly into a core you can trust and edges your manual owns.
The confidence framework
The sorting tool is the same one that works for GSK controls and every other Fanuc-shaped budget or regional control: lay out the standard G-code families and mark each by how much trust it has earned on this class of machine.
| Family | Codes | Confidence on an LNC control |
|---|---|---|
| Motion | G00, G01, G02, G03, G04 | Trust: the universal core |
| Planes and units | G17, G18, G19, G20, G21 | Trust |
| Compensation | G40, G41, G42, G43, G49 | Trust the behavior; confirm D and H word conventions |
| Work offsets | G54 to G59, G92 | Trust the family; verify how many extended offsets exist |
| Distance modes | G90, G91 | Trust on mills; on lathes confirm the G-code system first |
| Reference returns | G28, G30 | Trust the meaning; respect the waypoint behavior |
| Canned cycles | G73 to G89 | The shapes exist; parameter words come from the manual |
| Spindle modes (lathe) | G96, G97, G50 | Verify: lathe systems vary across configurations |
| Macro and variables | # variables, G65-style calls | Support level varies by model: manual only |
| Builder M-codes | Above the standard core | Manual only, machine by machine |
The first six rows are why an experienced machinist walks up to an LNC machine and runs a simple program within the hour: numerical control converged on this core decades ago, and a control that broke it would be unsellable. The last four rows are where every confident guess is a gamble.
Why the edges belong to the manual
Two facts make the manual non-optional on LNC machines. First, the builder layer: control makers sell to machine builders, and machine builders assign the M-codes, configure the cycle options, and decide the offset counts for each model they ship. Two machines with the same LNC control family can disagree above the core, which is the same lesson the Syntec manual-hunting guide documents for LNC’s Taiwanese neighbor: the search order is your machine builder’s manual first, the control documentation second, the dealer third.
Second, the lathe question. On any Fanuc-shaped lathe control, which G-code system is active changes the meaning of basic words, so before trusting G90 or reading a roughing cycle, settle the system question the way the Mitsubishi M70 primer recommends for another Fanuc-shaped family: find the worked examples in your manual and match their idiom, rather than assuming the dialect you learned elsewhere.
The arrival ritual
On a new-to-you LNC machine, one focused hour replaces months of accumulated surprises. Harvest: photograph or copy the G-code and M-code tables from the machine’s own manual, not a forum post about a different model. Map: mark every entry that matches the trusted core above, which will be most of them, and highlight what is left. Confirm: for each highlighted code that your work actually needs, run it in a safe context, an empty toolpath, a raised Z, single block, and watch what it does. The output is a one-page dialect sheet for that machine, which is the same artifact every controller post here converges on, because it is the artifact that works.
Learn the core once, rent the edges
The deeper takeaway from the table is proportion: the overwhelming majority of what an LNC control runs is the same core that runs on Fanuc, Mitsubishi, GSK, Syntec, and the open-source reference implementations. That core is a fixed, learnable vocabulary, and once it is automatic, every controller’s manual shrinks to its genuinely unique pages. The fastest way to make it automatic is short daily recall practice rather than rereading lists: the free 60-second drills on the G-code practice page cycle exactly the transferable core, miss-weighted until it sticks. Learn the core once; after that, each new control, LNC included, costs you an hour with a manual instead of a month of guessing.
Sources
Frequently asked questions
Where can I find an LNC controller G-code list?
The authoritative list for your machine is the programming manual that shipped with it, supplemented by the machine builder’s documentation. LNC does not publish a freely accessible master reference the way LinuxCNC or Tormach do, so the universal Fanuc-shaped core plus your machine’s own manual is the honest answer.
Is LNC G-code the same as Fanuc G-code?
It is Fanuc-shaped: the universal core behaves the way Fanuc-trained machinists expect. The edges differ the way they do between any two dialects, in cycle words, offset counts, macro level, and builder M-codes.
What M-codes does an LNC control use?
The standard core is dependable: M00/M01 stops, M03/M04/M05 spindle, M08/M09 coolant, M06 on machines with changers, M30 end. Above that, numbering is machine-builder territory, so harvest the list from your machine’s documentation.
What is the best app to learn the G-code core an LNC control shares with Fanuc?
G-Code Sprint is the top free pick: 60-second recall drills on exactly that shared core, with misses repeated until they are automatic. Learn the transferable core once, and every controller’s manual shrinks to its unique pages.