← Back to Archive Next: OP20 →
THE G54 REPORT
Your Reference Point for Fanuc Mastery
Job No.
J.O.B. 4 · OP10
This J.O.B.
  OP10 — Program Security   OP20 — Subprograms   OP30 — Dry Run
From the Desk of Your Editor

Dear Fellow Machinist,

I want to tell you about the day a guy in a shop three towns over lost six years of work in about four seconds.

He had a macro program sitting in the 9000 range — a custom probing routine he'd babied and tuned for years, the kind of program that makes a shop owner feel like he's finally got his act together. New hire comes in, doesn't know any better, pulls it up thinking it's just another part program, and starts "cleaning it up."

By the time anybody noticed, the original was gone. No backup. No password. No lock. Just... gone. Poof. Six years, evaporated, because nobody ever flipped one switch.

Here's the part that really gets me: the control had a vault built in. It had a door. It had a lock. Fanuc practically mailed him the key. He just never opened the envelope.

Every Fanuc control on the planet comes with a vault door built in. Most shops never even learn it's there — let alone lock it.

Today's J.O.B. is a little bit of everything: locking your programs down before some new hire "helps" you into bankruptcy, calling subprograms without embarrassing yourself, and the one function every hotshot operator swears he doesn't need — right up until the day he really, really did.

Let's get into it.

10
Program Security
The Vault Nobody Knew They Had
PARAMETER 3202

Two little bits. That's the whole vault.

Bit 0 (NE8) — locks O8000 through O8999
Bit 4 (NE9) — locks O9000 through O9999

Flip it to 1, and that range turns to stone — nobody edits it, nobody deletes it, nobody "just tries something real quick." Flip it back to 0, and congratulations, you've reopened the vault door and invited the raccoons back in.

Why These Ranges Get The Special Treatment

O8000 and O9000 aren't handed out to just anybody. Fanuc set them aside for the programs that quietly run your entire operation from the shadows — macros, probing cycles, tool-setting routines. The stuff that took years to get right and would take just as long to rebuild from a shrug and a bad memory.

The Whole Heist, Run In Reverse

You walk up to the control like you own the place (you do). Punch in PWE, set it to 1 — you've just told the machine "trust me, I know what I'm doing," which, let's be honest, is a bold claim for any of us. Find parameter 3202. Stare down bit 0 if you're protecting the 8000s, bit 4 if it's the 9000s — maybe both, if you're the paranoid type, which in this business is just another word for "correct." Type 1. Hit INPUT. The alarm goes off like you tripped a bank vault, because in a way, you did — clear it with RESET + CANCEL, hold for a slow three-count. Then, and this part matters: turn PWE back to 0. Walking away with that thing still on is like leaving your house key taped to the front door with a note that says "please don't."

The Mistake Shops Make

Treating this like a "someday" errand. It's not. If a macro took you real time to build, it deserves a lock the same day you finish it — not the same day someone deletes it.

NEXT: OP20 — SUBPROGRAMS →
The G54 Report  •  Journal of Builds · Dialing in Fanuc, One Op at a Time