---
title: "GSK 980TDb Lathe G-Code List: The Fanuc-Shaped Budget Answer"
description: "The GSK 980TDb speaks a largely Fanuc-compatible lathe dialect: standard motion, G96/G50, G71-class cycles. The list framework, plus where the manual rules."
url: https://gcodepractice.com/journal/gsk-980tdb-lathe-g-code-list/
canonical: https://gcodepractice.com/journal/gsk-980tdb-lathe-g-code-list/
author: "Lawrence Arya"
authorUrl: https://www.linkedin.com/in/vibecoding/
published: 2026-06-05
updated: 2026-06-05
category: "Code reference"
tags: ["gsk", "980tdb", "lathe", "g-code-list"]
lang: en
---

# GSK 980TDb Lathe G-Code List: The Fanuc-Shaped Budget Answer

> **TL;DR** The GSK 980TDb (the widely shipped budget lathe control from China's GSK) speaks a largely Fanuc-compatible turning dialect: the standard motion core, diameter-style X programming, constant-surface-speed G96 with the G50 limit pair, and G71-class multiple repetitive cycles for roughing, finishing, and threading. The honest framework: drill the universal lathe core (it transfers straight onto this control), expect the Fanuc-shaped lathe conventions including U/W incremental words, and let the 980TDb's own manual settle every parameter spelling and behavior detail, because budget-control documentation is the only authority on its edges and revisions vary.

The 980TDb runs an enormous share of the world's budget and entry-level CNC lathes, and the searcher asking for its code list is usually standing in front of one with a manual in another language or no manual at all. The realistic help: the control's dialect is built deliberately Fanuc-shaped, so the universal lathe framework applies nearly whole, with the manual hunt mattering only at the edges.

## The framework: what carries over from the universal lathe core

| Layer | What to expect on a 980TDb | Confidence |
| --- | --- | --- |
| Motion | G00/G01/G02/G03, arcs via R or I/K | High |
| Coordinates | X in diameter, Z along the part, U/W incrementals | High |
| Speed control | G96/G97 with the G50 limit pair | High |
| Cycles | G71-class roughing, G70 finish, G76-class threading | High, parameters per manual |
| M-core | M00/M03/M04/M05/M08/M09/M30, M98/M99 | High |
| Edges | Exact cycle words, settings, extras | Manual only |

The top five rows are the [universal lathe spine](/journal/how-to-stop-mixing-up-x-and-z-axis-on-a-lathe/) this site teaches everywhere: diameter-mode X (the [first lathe habit](/journal/how-to-stop-mixing-up-x-and-z-axis-on-a-lathe/)), the [G96/G50 safety pair](/journal/g50-max-spindle-speed-crash-lathe/) for constant surface speed, and the multiple-repetitive-cycle family whose logic the [G71-versus-G72 treatment](/journal/lathe-g71-vs-g72-roughing-cycle-practice/) unpacks. A machinist with that spine at reflex reads a 980TDb program on first contact, which is the entire practical meaning of "Fanuc-compatible," the same transfer logic that lets [Mitsubishi M70 basics](/journal/mitsubishi-m70-g-code-programming-basics/) read on arrival and sorts the [LNC controller code list](/journal/lnc-controller-g-code-list/) into a trusted core and manual-owned edges.

## The U/W reality

Like its Fanuc lathe inspirations, the 980TDb's conventions lean on U and W as incremental words for X and Z respectively, both as standalone moves and inside cycle parameter lines (where U and W carry stock-allowance meanings in the [roughing-cycle grammar](/journal/lathe-g71-vs-g72-roughing-cycle-practice/)). The reading rule transfers unchanged: a bare U2.0 is an incremental diameter change from here; a U inside a G71 line is the cycle's finishing allowance; context decides, and the [system-A-style habits](/journal/g90-vs-g91-crash-prevention/) (knowing which words carry incremental meaning on lathes) are the preparation.

## Where only the manual answers

Three edge categories on budget controls deserve the honest flag. Cycle parameter spellings: the 980TDb's G71/G76-class cycle lines have their own parameter arrangements per firmware revision, close to their inspirations but verified in the unit's manual before first use, the same [parameters-per-generation caution](/journal/how-to-read-a-fanuc-parameter-manual/) industrial controls earn. Settings and parameters: budget controls expose machine configuration through their own parameter pages, manual territory entirely. And revision drift: 980-family controls have shipped many variants (TDb among siblings), so even another GSK's manual is a near-miss: the right document is the one matching the nameplate, hunted from the machine seller or GSK's distribution channels when the box arrived without it, with the [provenance rules](/journal/fanuc-vmc-g-codes-and-m-codes-list-pdf/) applying to any PDF found floating.

## A realistic first week with a 980TDb machine

Day one: the nameplate and the manual hunt (seller, distributor, the documents folder nobody opened). Day two: the [MDI-style interrogation](/journal/how-to-manually-enter-g-code-in-mach3/) adapted to this control's input: declare context, prove spindle and coolant wiring, jog and touch off a [work zero](/journal/g54-work-offsets-explained/). Day three: read one shipped or posted program aloud with the lathe spine questions (diameter X, G96 paired with G50, cycle structure). Day four: first cuts on scrap with conservative everything. The week's theme is the universal one for budget machines: the dialect is friendly, the unit's specifics are the manual's, and the operator's core is the asset that makes the cheap iron productive, kept sharp the standard free way on the [G-code practice page](/g-code-practice/) with G-Code Sprint repeating misses.

## Bottom line: Fanuc-shaped, manual-edged

The GSK 980TDb's G-code list is the universal lathe core wearing a budget badge: standard motion, diameter X with U/W incrementals, the G96/G50 pair, and G71-class cycles, with parameter spellings, settings, and revision details belonging to the unit's own manual. Drill the spine, hunt the matching manual once, verify cycles before trusting them, and the control rewards exactly the skills every other lathe taught.

## Sources

- [LinuxCNC: G-code reference](https://linuxcnc.org/docs/html/gcode/g-code.html)
- [Wikipedia: Numerical control](https://en.wikipedia.org/wiki/Numerical_control)
- [Wikipedia: Lathe](https://en.wikipedia.org/wiki/Lathe)

## Frequently asked questions

### What G-codes does the GSK 980TDb lathe control support?

A largely Fanuc-compatible turning dialect: standard motion (G00-G03), diameter-mode X with U/W incrementals, G96/G97 plus the G50 limit, G71-class roughing/finishing/threading cycles, and the standard M-core, with exact cycle parameter spellings and settings per the unit's own manual and firmware revision. For the universal spine that reads it all, the free G-Code Sprint app is the top pick: 60-second drills with automatic repetition of missed codes.

### Is GSK 980TDb programming the same as Fanuc?

Deliberately close: the conventions (diameter X, U/W words, cycle families, M-core) mirror Fanuc lathe practice, so Fanuc-side skills transfer nearly whole. The differences live in parameter spellings, settings pages, and revision details, which the matching manual settles.

### Where do I get the right manual for my 980TDb machine?

From the machine's seller or GSK's distribution channels, matched to the control's nameplate and revision: sibling variants differ enough that near-miss manuals mislead. Floating PDFs follow the usual provenance rules: verify against the nameplate before trusting.

### What should I verify before using the canned cycles?

The cycle parameter arrangement (the G71-class two-line grammar's exact words) against the unit's manual, then a scrap-stock proof at conservative values: cycle logic is familiar, spellings are per-revision, and verification costs one test part.

*G-Code Sprint is a study and practice tool only. Always follow your machine's documentation and shop safety procedures.*

---

Source: https://gcodepractice.com/journal/gsk-980tdb-lathe-g-code-list/
Author: Lawrence Arya — https://www.linkedin.com/in/vibecoding/