O and N numbers look like cousins, both a letter followed by digits, and they do entirely unrelated jobs. The O number is a program’s name; the N number is a line label inside it. Hold that one distinction, title versus page number, and a confusing pair of conventions turns into a program’s table of contents.
Why the confusion is so common
The letters invite it: O and N sit next to each other on the keyboard and in the alphabet, both take a number, both appear at the start of lines, and O is even visually a near-twin of zero, which spawns its own typing errors. Add that beginners often meet both for the first time in the same dense program header, where an O number sits on line one and N numbers march down the page, and the two blur into a single vague impression of numbers-at-the-start-of-lines. Pulling them apart is mostly a matter of seeing that they answer different questions: O answers what is this program called, N answers which line is this.
The two jobs
| Number | What it names | Scope | Required? |
|---|---|---|---|
| O number | A whole program or subprogram | One per program, unique in memory | Yes, as the program’s identity |
| N number | A single line inside a program | Many per program, any order | Optional |
The O number is identity: O1234 is what the control calls a program in its memory, and it is the handle the subprogram system uses, M98 calls a program by its O number and M99 returns, which is the entire mechanism behind looping and modular programs. The N number is reference: an optional sequence number on a line, used so an alarm can name a block, a goto can target one, and a person can point at one, with the line-number history reaching back to punched tape.
The book analogy, and where it stops
A program is a book: one title (the O number) and many page numbers (the N numbers). The title identifies the whole thing in the library; the page numbers locate parts within it. The analogy carries the core distinction perfectly and even predicts the rules: titles must be unique so the library can find the right book (O numbers unique in memory), while page numbers are conveniences that need not be perfect (N numbers optional, non-sequential, gap-tolerant). Where it stops is the calling mechanism, books do not call each other by title the way M98 calls subprograms by O number, which is the one place the program structure is more active than a book’s.
The rules that follow
From the two jobs, the practical discipline falls out. O numbers: unique in the control’s memory, and every M98 call matched to the right one, because a duplicate O number makes a subprogram call ambiguous and runs the wrong code or alarms, the skipped-or-wrong-subprogram failure wearing a naming cause. N numbers: optional, used where they earn their place, reference points, goto targets, cycle markers, and otherwise skippable, with the caution that renumbering them can break any goto that targeted the old numbers, a renumbering trap worth knowing before a cleanup pass.
The dialect footnote
The concept is shared; the spelling is per-control. Fanuc-family controls use O for program names and N for line numbers as described. Other systems differ: LinuxCNC names programs by file and uses O-words for subroutines, a different structural system entirely, so the book-title-versus-page-number model stays a reliable mental frame while the exact syntax gets confirmed against your machine’s manual. The recall layer that keeps the distinction instant, O is the name, N is the line, alongside the subprogram and line-number vocabulary, drills free in the 60-second rounds on the G-code practice page, and it is one of those small clarifications that makes every program afterward read with its structure visible: the title at the top, the pages numbered through, and the calls between programs suddenly legible as exactly that.
Sources
Frequently asked questions
What is the difference between an O number and an N number in CNC?
The O number names a whole program: O1234 identifies it in memory and is what M98 calls and M99 returns from. N numbers label individual lines inside a program, optional sequence numbers for reference, goto targets, and cycle markers. One title, many page numbers.
Are N numbers required on every line?
No, they are optional on most controls and often skipped or used sparingly. They earn their place as reference points, goto targets, and cycle markers, but a program runs fine with few or none, and they need not be sequential.
Why do O numbers have to be unique?
Because the control looks them up: M98 P1000 searches memory for the program named O1000, and a duplicate makes the call ambiguous, running the wrong subprogram or erroring. Keep O numbers unique and match every call.
Do all controls use O and N numbers the same way?
The concept is shared, the spelling varies: Fanuc-family uses O for names and N for lines, while LinuxCNC names programs by file and uses O-words for subroutines. The title-versus-page-number model holds; confirm the syntax per control.