FANUC Matrix Keypad Panel Replacement: Remapping PMC Ladder Logic and Resolving R-Address Conflicts

FANUC Matrix Keypad Panel Replacement: Remapping PMC Ladder Logic and Resolving R-Address Conflicts

Field notes by 共享屋 (Gongxiangwu) — a real panel-swap job, compiled from wechat field notes and expanded over time. Part of the 《FANUC PMC 维修学习资料》 workbook.

Swapping a FANUC matrix keypad panel — what we call a “scanned panel”, because the keys are read by a scan routine that writes their states into the R area — looks like a pure hardware job. In practice the hardware is the easy 20%. The real work is porting the PMC ladder logic so that every key on the new panel drives the same machine function as before.

This is a field record of replacing one matrix panel with another. It assumes you already know:

广告

If you only want the physical teardown, stop here — the value of this article is the address-mapping and ladder-rewrite method.


Table of Contents

1. The four-stage workflow

The whole job breaks into four stages:

  1. Collect information & back up the original PMC program.
  2. Map the old vs. new panel key addresses, and find every I/O address that collides between the two panels.
  3. Rewrite the ladder logic step by step until every section is fully modified and replaced.
  4. Download the new PMC program to the CNC and test / verify.

⚠️ Stage 1 is non-negotiable. Never touch a running ladder without a verified backup. See How to Backup and Restore a Fanuc PMC Program from LADDER-III and the full FANUC data backup & restore guide (ALL I/O / BOOT SRAM).

2. Stage 1 — Backup and information gathering

Before any change:

  • Make a complete backup of the original PMC program (and, ideally, a full ALL-I/O backup). Keep the backup file named by date and machine.
  • Record the old panel model and, critically, the CB connection-unit model it uses.

In our case the old panel used CB106 and the replacement uses CB107. That single difference changes which I/O points the panel physically occupies — and it is the root of the address conflict you will meet in Stage 3.

3. Stage 2 — Map old vs. new key addresses

Before editing anything, list the key addresses each panel occupies.

Item Old panel New panel
Connection unit CB106 CB107
Key-state storage R1280 – R1299 (20 bytes / 160 bits) R addresses that may collide with the existing machine ladder
Mapping method — one-to-one where a correspondence exists; manual, key-by-key otherwise

Key facts:

  • The original panel’s keys are scanned into R1280 through R1299 — that is 20 bytes (160 bits) of R area.
  • The new panel’s scan routine (NEW.LAD) also writes its key states into R addresses. Some of those R addresses overlap with the existing machine ladder → that is the conflict you must resolve.

Practical tip: build a cross-reference table first. For every key on the new panel, write down (a) the old R address that performed the same function and (b) the new R address the scan routine assigns. Where a clear 1:1 correspondence exists you can batch-replace; where there is none you must replace one key at a time, guided by the new panel’s function definition.

You need to be able to read the original PMC logic to do this correctly. If the ladder is undocumented, spend Stage 2 reverse-mapping each old key’s function before touching anything.

4. Stage 3 — Rewrite the ladder logic

This is the core. Two sub-steps:

(1) Neutralise the colliding addresses. Before the new panel is introduced, take every I/O point in the original ladder that uses CB107 (the new panel’s connection unit) and re-route it through an intermediate relay (an unused R/E-area address). Doing this first gives you a clean, conflict-free base to build on, and makes later edits reversible.

(2) Swap the scan routines.

广告
  • Delete the old panel scan routine from the ladder.
  • Copy the new panel scan routine (NEW.LAD) into the ladder.
  • Inside NEW.LAD, the R addresses that collide with the old machine program must already have been redirected to intermediate variables (this redirection was completed as prep work). Verify each one.

Replacement strategy recap:

  • Batch replace when the old and new key addresses have a known correspondence.
  • Manual, one-by-one replace when they do not — always against the cross-reference table from Stage 2.

Note: this stage requires you to actually understand part of the original PMC program. Blind search-and-replace across a ladder you don’t understand is exactly how panels end up “working except for these three keys”.

For the address-space conventions used here (R / E / Y / G / F / K / A), see the FANUC PMC signal address reference.

5. Stage 4 — Download and verify

6. Safety rules (never skip)

  • Keep the e-stop chain, over-travel limit and door-interlock hard-wired circuits untouched. PMC logic never replaces a hardware safety loop.
  • Test under safe, isolated conditions (remove actuator power or block travel) before any real run.
  • Run single-block / dry-run verification; do not declare the panel “ready” until every key and every interlock is confirmed.
  • An unverified ladder must never be described as “ready to use”.

7. Related reading on CNCShare

8. To be updated — notes for later

This article is a living note. Details to be added as the job progresses:

  • [ ] Photos of the old / new panel and the CB106 / CB107 wiring.
  • [ ] The full cross-reference table (old R → new R) as an appendix.
  • [ ] The complete NEW.LAD routine listing.
  • [ ] Any model-specific quirks found during verification.

This tutorial was first compiled from wechat field notes and will be expanded over time. It belongs to the 《FANUC PMC 维修学习资料》 series.

Got a problem this article doesn’t answer? Leave a comment below — this article will be updated based on the real questions and cases readers report.

Where to go next

  • FANUC Troubleshooting — the full guide library: alarms, diagnosis numbers, servo, spindle, PMC and electrical faults, organised by symptom.
  • CNC Repair Tools — which instrument measures what: multimeters, clamp meters, insulation testers and oscilloscopes, with the specification that actually matters.
  • Remote Technical Support — have the readings reviewed with you: alarm reverse lookup, PMC ladder analysis and servo tuning advice by call. Repair companies and integrators welcome.

Read the guide, get the right instrument, or walk the diagnosis through with someone — pick whichever you need.

© 版权声明
THE END
喜欢就支持一下吧
点赞13赞赏 分享
评论 抢沙发

请登录后发表评论

    暂无评论内容

CNC电气调试问题解答 | 数控机床电气工程师资料共享屋
CNC电气调试问题解答 | 数控机床电气工程师资料共享屋
CNC电气调试问题解答 | 数控机床电气工程师资料共享屋
CNC电气调试问题解答 | 数控机床电气工程师资料共享屋
CNC电气调试问题解答 | 数控机床电气工程师资料共享屋
CNC电气调试问题解答 | 数控机床电气工程师资料共享屋
图片-CNCShare | 数控电气技术中心
图片-CNCShare | 数控电气技术中心
图片-CNCShare | 数控电气技术中心
图片-CNCShare | 数控电气技术中心
图片-CNCShare | 数控电气技术中心
图片-CNCShare | 数控电气技术中心
CNC Alarm Number Formats by Brand: FANUC vs SINUMERIK vs Mitsubishi vs HEIDENHAIN-CNCShare | 数控电气技术中心
CNC 报警号形态识别卡:FANUC / SINUMERIK / 三菱 M80 / HEIDENHAIN 位数、前缀与号段对照(30 秒定位该翻哪本手册)-CNCShare | 数控电气技术中心
Fanuc Gravity-Axis Brake: Release Sequence, 24V Wiring and Diagnosing Z-Axis Drop-CNCShare | 数控电气技术中心
FANUC 重力轴(垂直轴)抱闸怎么查?上电/断电时序 + 抱闸 24V 与到位确认 + Z 轴下落/掉刀的四层定位-CNCShare | 数控电气技术中心
Fanuc Emergency Stop Circuit: *ESP, G8.4, X8.4 and Why the Servo Never Gets Ready-CNCShare | 数控电气技术中心
FANUC 急停回路怎么查?*ESP / G8.4 / X8.4 信号链 + 24V 安全链 + 主接触器 MCC 与「复位了还是没就绪」的定位顺序-CNCShare | 数控电气技术中心
Fanuc Servo Resonance and Notch Filter Setup: Finding the Frequency with Servo Guide-CNCShare | 数控电气技术中心
FANUC 伺服共振 / 啸叫怎么抑制?陷波滤波器(频率·带宽·衰减)参数设定 + Servo Guide 扫频定位全流程-CNCShare | 数控电气技术中心
Fanuc Threading G32 / G92 / G76: Fixing Pitch Errors and Spindle Sync Problems-CNCShare | 数控电气技术中心
FANUC 车螺纹乱牙 / 螺距不对怎么查?G32/G92/G76 主轴同步链路 + 一转信号 + G96 恒线速与 G50 限速设置-CNCShare | 数控电气技术中心
FANUC Matrix Keypad Panel Replacement: Remapping PMC Ladder Logic and Resolving R-Address Conflicts-CNCShare | 数控电气技术中心
三菱 M80 PLC 编程软件用哪个?GX Works3 / GX Developer 官方下载路径 + 版本对应表 + 安装与连机常见坑-CNCShare | 数控电气技术中心
文章精选
专心做好一件事
打造更优雅的WordPress主题-CNCShare | 数控电气技术中心
专心做好一件事
打造更优雅的WordPress主题