FANUC PMC Scan Time: Why Inputs Get Missed and Timers Fire Early

"Sometimes the button press does nothing." "The proximity switch is clearly actuated but the contact in the ladder flickers." "The timer fires before its set time." These intermittent, hard-to-pin-down problems almost always come back to the PMC scan cycle. Understanding scan time is what turns "the program seems random" into "which input was missed, and which result came from the previous scan." This article explains the four scan stages, four typical symptoms, and a field troubleshooting method.

Chinese version: PMC scan cycle, missed inputs and early timers; related: what a PMC is and scan time, PMC force output, PMC ladder beginner tutorial, CNC alarm number formats by brand.

11.1 What a scan cycle is: read inputs, execute, write outputs, repeat

Four stages of the PMC scan cycle

The PMC is the PLC built into every FANUC CNC. It repeats one loop continuously: sample inputs → execute the ladder top-to-bottom → refresh outputs → start again immediately. That loop is the scan cycle; the time for one loop is the scan time.

StageWhat the PMC doesField meaning
Input samplingReads all X addresses, latches current stateSampled once per cycle; changes between samples can be missed
Program executionRuns the ladder top-to-bottom, left-to-rightLower rungs see values already computed this cycle
Output refreshWrites results to Y and other outputsPhysical outputs change at cycle end, never mid-rung
RestartImmediately begins the next cycleNo idle wait — it starts over
广告

Table 1: the four stages of one scan

Remember one sentence: your logic does not see continuous time — it sees a sequence of discrete snapshots. Many “impossible” behaviours trace back to this.

11.2 How long is the scan time: read it from the control, not a manual

Reading scan time on the diagnostic screen

The common question is “what is the PMC scan time?” The right answer is not to quote a number — it is to read it on the machine’s diagnostic screen. On most FANUC systems the PMC or system diagnostic screen shows PMC execution time alongside ladder status. Record it as this machine’s baseline.

  • Scan time varies with program length and instruction complexity — bigger programs and heavier instructions mean longer cycles;
  • Different PMC models have different baselines. The “8 / 16 / 32 ms” figures circulating online are typical order-of-magnitude references only, not this machine’s measured value;
  • For a timing question, use the value you read on this machine, not one from another machine of the same model.

This site gives method and magnitude only — the specific value follows the machine’s own manual and diagnostic screen. That is the standing rule against inventing parameters and numbers.

11.3 Four typical symptoms: translate “random” into scan-cycle language

Four scan-cycle symptoms

Symptom one — a missed edge input. A short input pulse narrower than one scan can appear and disappear between two samples; the PMC never sees it. The fix is to widen the signal (move the cam or sensor) or use an input with a latching function — not to blame the ladder.

Symptom two — a DIF edge output lasts one scan. DIF / DIFU / DIFD edge outputs are valid for exactly one scan cycle. That is correct behaviour, not a fault. Wire such an output into a retentive address (R) and the one-scan pulse is latched into a permanent signal, losing all meaning.

Symptom three — a constantly ON trigger breaks a timer. If the trigger condition stays ON, the timer keeps satisfying or un-satisfying its condition and “loses accuracy.” A timer needs a stable condition with a clear edge.

Symptom four — a lower rung reads last scan’s value. The sequential program executes strictly top-to-bottom. A rung written below a timer or coil reads the value already computed this cycle. If you need the “just written” value, mind the rung order.

11.4 Address layers against the scan: when X/Y/F/G change

Address layers and scan stages

Sorting addresses by scan stage makes timing troubleshooting much clearer:

广告
AddressChanges at stageScan-cycle limitation
X (input)Input samplingLatched once per cycle; bounce across a cycle boundary may be missed
Y (output)Output refreshPhysical output changes at cycle end, never mid-rung
F (CNC to PMC)Input samplingCNC signal and ladder logic are never aligned to one instant
G (PMC to CNC)Output refreshThe CNC reads the refreshed value, with a delay
R (internal relay)Program executionThis cycle's result is used immediately by later rungs

Table 2: address groups vs scan stages

11.5 Field order: read the cycle, watch the signal, change the program last

For a suspected timing problem, work in this order to avoid wasted edits:

  1. Read the scan time: record this machine’s PMC execution time on the diagnostic screen as a baseline;
  2. Watch the signal: use the signal status screen or a meter to confirm input pulse width and any bounce;
  3. Classify the symptom: match against the four in section 11.3 — missed input, edge, timer, or rung order;
  4. Change the program last: fix signal quality first (widen the pulse, remove bounce); only then adjust the ladder if truly needed.

Editing the ladder first is the most common wrong order. Scan-cycle problems rarely get fixed by program edits — the cause is not wrong logic but a mismatch between signal and sampling timing.

Frequently Asked Questions

Is a shorter PMC scan time always better?

It is not a freely adjustable “smaller-is-better” parameter — it is set mainly by program size and PMC model. The field goal is to make critical signals much wider than the scan cycle, not to “tune down” the cycle.

Why does wiring an edge output to a retentive relay fail?

Because the edge output is valid for only one scan; once latched into a retentive address it becomes permanently ON and loses the meaning of “edge.” To trigger an action from an edge, use a set/reset or a counter input.

How do I confirm an intermittent fault is a scan-cycle issue?

Read the machine’s scan time, then measure the suspect signal’s pulse width. If the width approaches or falls below one scan cycle, that is essentially confirmation. Intermittent, patternless behaviour that changes after a restart is the classic signature.

Last updated: 2026-11-17

Where to go next

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

Also available in Chinese: FANUC PMC 扫描周期怎么导致信号漏采、定时器提前:中文现场排查
The original Chinese version — same procedure, with the full field notes.
© 版权声明
THE END
喜欢就支持一下吧
点赞9赞赏 分享
评论 抢沙发

请登录后发表评论

    暂无评论内容

CNC电气调试问题解答 | 数控机床电气工程师资料共享屋
CNC电气调试问题解答 | 数控机床电气工程师资料共享屋
CNC电气调试问题解答 | 数控机床电气工程师资料共享屋
CNC电气调试问题解答 | 数控机床电气工程师资料共享屋
CNC电气调试问题解答 | 数控机床电气工程师资料共享屋
CNC电气调试问题解答 | 数控机床电气工程师资料共享屋
图片-CNCShare | 数控电气技术中心
图片-CNCShare | 数控电气技术中心
图片-CNCShare | 数控电气技术中心
图片-CNCShare | 数控电气技术中心
图片-CNCShare | 数控电气技术中心
图片-CNCShare | 数控电气技术中心
FANUC PMC Scan Time: Why Inputs Get Missed and Timers Fire Early-CNCShare | 数控电气技术中心
FANUC PMC 扫描周期怎么导致信号漏采、定时器提前:中文现场排查-CNCShare | 数控电气技术中心
Schematic ↔ I/O Table ↔ PMC Ladder: Three-Way Cross-Reference Fault Tracing-CNCShare | 数控电气技术中心
电气原理图 ↔ I/O 分配表 ↔ PMC 梯形图三方对照:从报警反查到端子和元件的完整路径-CNCShare | 数控电气技术中心
数控电气调试软件与官方手册哪里下载?FANUC / 西门子 / 三菱 / 海德汉 官方入口与版本对应-CNCShare | 数控电气技术中心
SINUMERIK 828D G290 vs G291: DIN and ISO Mode Side by Side-CNCShare | 数控电气技术中心
SINUMERIK 828D G290 G291 怎么切?DIN 写法与 ISO 写法逐行对照-CNCShare | 数控电气技术中心
SINUMERIK 840D sl to S7-1500: NCVAR Selector, PROFINET Names and Alarm 150202-CNCShare | 数控电气技术中心
SINUMERIK 840D sl 与 S7-1500 怎么通讯?PROFINET 设备名 + NCVAR Selector 从 PLC 读写 MD 全流程-CNCShare | 数控电气技术中心
CNC Alarm Message Chinese Reference: 120 Common English Phrases and a 30-Second Triage Method-CNCShare | 数控电气技术中心
Five Peripheral Alarm Clusters on CNC Machines: Coolant, Lubrication, Chip Conveyor, Air and Hydraulics - From English Alarm Text to PMC Feedback to Action-CNCShare | 数控电气技术中心
数控机床英文报警中文对照(120 条句式样例)+ 看到英文报警后 30 秒定位该查哪个点-CNCShare | 数控电气技术中心
文章精选
专心做好一件事
打造更优雅的WordPress主题-CNCShare | 数控电气技术中心
专心做好一件事
打造更优雅的WordPress主题