how to clear Onto Innovation Atlas overlay illumination-intensity-low fault

By Sai Kiran Pandrala · Last verified: 2026-06-01 · Source: controls-community forums (r/PLC, r/Robotics, r/CNC, r/Fanuc, r/KUKA, r/Cognex, r/labview), OEM service bulletins and changelogs, OEM service manuals, in-controller diagnostic help

When how to clear Onto Innovation Atlas overlay illumination-intensity-low fault hits you on Semiconductors, Metrology Equipment Error Codes (KLA-Tencor SP-Series, Hitachi CD-SEM, Bruker AFM, Onto Innovation), 2026 mid-shift, the first instinct is to cycle power on the controller or hit the master reset. Most of the time you do not have to. The steps below are what a maintenance engineer would do at the cell panel before escalating to the OEM hotline - I keep a fault-history notebook per machine so the working state and parameter set are always reproducible.

What how to clear onto innovation atlas overlay illumination-intensity-low fault actually involves on Semiconductors, Metrology Equipment Error Codes (KLA-Tencor SP-Series, Hitachi CD-SEM, Bruker AFM, Onto Innovation), 2026

On Semiconductors, Metrology Equipment Error Codes (KLA-Tencor SP-Series, Hitachi CD-SEM, Bruker AFM, Onto Innovation), 2026 when this lands in my queue the tools I lean on first are KLA-Tencor MetroLink data analysis client, KLA SensArray temperature/dose wireless wafer, Bruker AFM laser-alignment guide and SUM/DEFLECTION meter. Each of these surfaces a different layer of the fault - keep at least the first one in your fault-history notebook so the next time this happens you do not start cold.

For verification on Semiconductors, Metrology Equipment Error Codes (KLA-Tencor SP-Series, Hitachi CD-SEM, Bruker AFM, Onto Innovation), 2026, the methods that survive contact with a real second-shift production workload are validate metrology tool floor vibration with PCB Piezotronics scan < 100 micro-g RMS and run KLA SP-series qualification wafer (PSL) and confirm capture rate against gold record. Anything less than that and you are shipping on vibes.

Authoritative sources for Semiconductors, Metrology Equipment Error Codes (KLA-Tencor SP-Series, Hitachi CD-SEM, Bruker AFM, Onto Innovation), 2026 that I cross-reference before committing to a fix: semi.org/standards, ontoinnovation.com, hitachi-hightech.com. OEM marketing brochures and trade-press writeups are signal, not ground truth.

The rest of this page is the structured fix path. Start with diagnose, then remediation, then the automation options so you do not have to do this by hand the next time it surfaces. Verify and safety sections at the end are the discipline that keeps the fix from regressing the next time you open the cabinet.

Diagnose first, fix second

Eighth: diff the Semiconductors, Metrology Equipment Error Codes (KLA-Tencor SP-Series, Hitachi CD-SEM, Bruker AFM, Onto Innovation), 2026 setup against its last known good state. Ask the obvious question - what changed in the 72 hours before the fault started? Did the controller take a firmware update overnight (check the About panel for the firmware revision vs the previous version you wrote down in your notes)? Did you swap a drive, a motor, an encoder cable, or a fieldbus drop? Did you change a tool offset, a work offset, a vision job, or a recipe? Did the maintenance team push a new PM checklist, swap a lube reservoir, or change a coolant concentration? Use the in-controller audit trail (Fanuc PARAM history, KUKA KRC log, Cognex In-Sight job version) to anchor "before vs after" so you are not guessing. Cross-check the OEM service bulletin and the OEM community forum for the exact firmware revision - if a regression hit a batch of cells in the same week, the community catches it before the official bulletin admits it. Record the suspect ranking, then disprove suspects one at a time with the cheapest test first (parameter restore before drive swap, encoder battery check before encoder swap).

Seventh: run the dedicated diagnostic option for whichever subsystem the Semiconductors, Metrology Equipment Error Codes (KLA-Tencor SP-Series, Hitachi CD-SEM, Bruker AFM, Onto Innovation), 2026 alarm points at. Drive suspected? Force a servo discharge and re-energize from the drive panel, then check the drive status LEDs for the green ready signal and the last-fault timestamp. Encoder suspected? Power down fully (lockout-tagout), check the encoder battery voltage at the back of the controller, re-home the axis on power-up. Cable suspected? Pin-check the encoder cable continuity end-to-end with a meter (EtherCAT or Profinet drop = use a cable tester, look for an LED link light at both ends). Each of these surfaces config that the controller silently inherits from a previous session, and 90 percent of "this used to work yesterday" reports trace to a stale parameter or a vibrated-loose connector. Capture the result of each step in your notes alongside the timestamp so you do not redo the discovery the next time.

Start by capturing the exact failure signal in writing before you change a single thing on your Semiconductors, Metrology Equipment Error Codes (KLA-Tencor SP-Series, Hitachi CD-SEM, Bruker AFM, Onto Innovation), 2026 setup. On the controller HMI that is the alarm code, the alarm message text, the timestamp, the controller hour-meter, and the part-count when the alarm hit. On the OEM diagnostic interface that is the fault-history dump (Fanuc alarm history, KUKA KSS log, Cognex In-Sight event log) plus the running program block number at the moment of fault. Photograph the HMI screen with the alarm panel open. Do not paraphrase. Most OEM service workflows will not even route the warranty case without the controller serial number, the alarm history dump, and the fault timestamp - the field service engineer pastes the alarm code straight into the OEM diagnostic tool and the first response is "we see the fault, here is what the controller logged."

Field notes from real Semiconductors, Metrology Equipment Error Codes (KLA-Tencor SP-Series, Hitachi CD-SEM, Bruker AFM, Onto Innovation), 2026 callouts

For Semiconductors jobs I keep a battered field notebook of "what bit me on Semiconductors and how I cleared it", writing it down the first time has saved me a dozen overnight returns. My standing rule on any Semiconductors ticket is to baseline with KLA SensArray temperature/dose wireless wafer before touching a single wire, half the "failed" parts I have replaced over the years were not actually failed.

Vendor portals like spie.org are a starting point for Semiconductors questions, never the final word. The integrator forums are where the ugly edge cases actually get diagnosed. Last week on a graveyard shift I chased a phantom Semiconductors alarm for two hours before remembering Bruker NanoScope Analysis software for AFM scan review would have isolated the bad channel in five minutes. On any Semiconductors fault inside Semiconductors, the first three questions I ask are: which firmware rev, which I/O card, and what was the last commissioning change. Defaults drift between releases.

Tools I actually reach for

For most Semiconductors, Metrology Equipment Error Codes (KLA-Tencor SP-Series, Hitachi CD-SEM, Bruker AFM, Onto Innovation), 2026 faults I start with KLA Archer/Atlas overlay self-cal screen, fall back to Onto Discover defect-source-analysis (DSA) tool, Bruker AFM laser-alignment guide and SUM/DEFLECTION meter, KLA SensArray temperature/dose wireless wafer, Hitachi CG-series CD-SEM service console (column vacuum / beam page) when KLA Archer/Atlas overlay self-cal screen cannot surface the answer, and keep Onto Innovation NovaScan recipe editor and fit-quality viewer handy for the cases where neither answers. That ordering is not academic - it matches the layers of the fault as they tend to surface, so the cheapest signal lands first and the heavier tooling only comes out when the simpler answer does not hold up. My muscle-memory shortcut for this is to run the first tool while the alarm screen is still open, not after I have already cycled controller power.

Verification I run before I call it fixed

Before I mark a Semiconductors, Metrology Equipment Error Codes (KLA-Tencor SP-Series, Hitachi CD-SEM, Bruker AFM, Onto Innovation), 2026 fault resolved, the verification loop below is what I actually run. Each step proves a different layer is green, and the order matters - the cheaper checks gate the more expensive ones.

verify CD-SEM beam-current within +/- 2% via Faraday-cup calibration step

If that one comes back clean, move to the next check. If it does not, stop and dig in there before layering more verification on top of a red signal.

confirm CD-SEM stage repeatability via cross-wafer 9-point measurement on golden wafer

If that one comes back clean, move to the next check. If it does not, stop and dig in there before layering more verification on top of a red signal.

check AFM laser sum signal > 3 V on cantilever-detector alignment screen

Only when every line above runs clean do I close the loop and update my fault-history notebook with the timestamps.

Where I check first when the docs disagree

When two sources contradict each other on a Semiconductors, Metrology Equipment Error Codes (KLA-Tencor SP-Series, Hitachi CD-SEM, Bruker AFM, Onto Innovation), 2026 detail, the disambiguation order I lean on is stable. I usually check semi.org/standards for the ground-truth view on this part of Semiconductors, Metrology Equipment Error Codes (KLA-Tencor SP-Series, Hitachi CD-SEM, Bruker AFM, Onto Innovation), 2026. I usually check ontoinnovation.com for the ground-truth view on this part of Semiconductors, Metrology Equipment Error Codes (KLA-Tencor SP-Series, Hitachi CD-SEM, Bruker AFM, Onto Innovation), 2026. I usually check kla.com for the ground-truth view on this part of Semiconductors, Metrology Equipment Error Codes (KLA-Tencor SP-Series, Hitachi CD-SEM, Bruker AFM, Onto Innovation), 2026. OEM marketing brochures and trade-press writeups are signal, not ground truth, and I treat them as such until the references above either confirm or contradict the claim.

Solution-focused remediation path

For Semiconductors, Metrology Equipment Error Codes (KLA-Tencor SP-Series, Hitachi CD-SEM, Bruker AFM, Onto Innovation), 2026 cells where duty-cycle limits or thermal envelopes are suspect, read the in-controller hints honestly. "Servo overcurrent" usually means you hit the peak current envelope of the drive during accel. "Motor overload" is the sustained-thermal signal on the motor winding. "Drive overheat" is the heatsink thermistor signal. Each is telling you the exact same thing in a Semiconductors, Metrology Equipment Error Codes (KLA-Tencor SP-Series, Hitachi CD-SEM, Bruker AFM, Onto Innovation), 2026-specific dialect. Apply duty-cycle dwell for repeated-cycle programs (insert a 500ms dwell between high-load moves), reduce the rapid feedrate, and chunk a long cycle into smaller passes. Decision point: if you are hitting the thermal limit sustained rather than in bursts, the cell is undersized for the workpiece - upgrade the drive amperage rating or request a thermal margin review from the OEM with a written duty-cycle analysis; without it, dial back the throughput at the cell. Replay the failing program against a fresh test workpiece at half the feedrate to confirm the new safe envelope before pushing to the production cell.

Start by sorting the Semiconductors, Metrology Equipment Error Codes (KLA-Tencor SP-Series, Hitachi CD-SEM, Bruker AFM, Onto Innovation), 2026 fault into one of three buckets, because roughly 80% of cases fall here. Bucket one is electrical / drive: instantaneous overcurrent, sustained overload, drive overheat, bus undervoltage, or a phase-loss event. Bucket two is mechanical / motion: encoder battery low, absolute position lost, over-travel, hardstop hit, or a vibrated-loose cable. Bucket three is recipe / parameter / I/O: the program calls a tool that is not loaded, the work offset is wrong, a DI is mapped to a disconnected sensor, or a vision job version has drifted. Pick the bucket first, then act. Before you act, capture a baseline photo of the alarm screen plus the controller hour-meter so you can prove whether the fix actually moved the needle. Decision point: if the alarm is intermittent and the cell is under an OEM service contract, open the OEM hotline first - OEM phone support beats hours of speculative debugging on cost and on liability if the alarm recurs and trips a safety-related shutdown.

When the Semiconductors, Metrology Equipment Error Codes (KLA-Tencor SP-Series, Hitachi CD-SEM, Bruker AFM, Onto Innovation), 2026 fault tracks to communications failures, fieldbus drops, or vision-trigger misses from the upstream station (the upstream PLC, the cell controller, the vision system), treat the integration plane as suspect. Open the fieldbus log on the upstream controller (the PLC EtherCAT diagnostic, the Profinet device status, the cell controller IO scan) and read the link status the Semiconductors, Metrology Equipment Error Codes (KLA-Tencor SP-Series, Hitachi CD-SEM, Bruker AFM, Onto Innovation), 2026 node actually returned - most "vision did not trigger" reports are actually "trigger fired but the vision job rejected the part and the PLC stalled waiting for a Pass." Verify the connected node is still online (the OEM diagnostic shows green link), the trigger event is what you think it is, and the cycle interlocks are not blocking on a stale handshake. Decision point: if the trigger is firing but Semiconductors, Metrology Equipment Error Codes (KLA-Tencor SP-Series, Hitachi CD-SEM, Bruker AFM, Onto Innovation), 2026 is missing it, throttle the cycle (bump the dwell timer, slow the conveyor, add a debounce in the PLC) and re-run. Verify the connected fieldbus drop is the right one - a common foot-gun is the sister-station drop being patched to the wrong port at the cabinet.

Automate this fix so you do not do it twice

Automate Semiconductors, Metrology Equipment Error Codes (KLA-Tencor SP-Series, Hitachi CD-SEM, Bruker AFM, Onto Innovation), 2026 parameter + I/O mapping snapshots via OEM utility or API

On the Semiconductors, Metrology Equipment Error Codes (KLA-Tencor SP-Series, Hitachi CD-SEM, Bruker AFM, Onto Innovation), 2026, regular parameter and I/O snapshots catch silent parameter drift, recipe edits, and stale safety-PLC permissions well before the cell starts faulting in prod. Pair OEM health checks (the OEM diagnostic SDK, the controller users API, the fieldbus device listing) with a license-validity check so both OEM-side and cell-side issues land in one folder. Run the scheduled task on a control-plane logger PC (a hardened IPC at the cell, a GitHub Actions runner against the cell-controller VPN, a small Linux box at the line) under a tightly scoped service account that mirrors the maintenance role.

# List cell operator roster + safety-PLC roles
curl -H "Authorization: Bearer $CONTROLLER_TOKEN" \ https://controller.plant.local/api/v1/operators \ > semiconductors-operators.json
# List active fieldbus drops + their last-link-up timestamp
curl -H "Authorization: Bearer $CONTROLLER_TOKEN" \ https://controller.plant.local/api/v1/fieldbus_drops \ > semiconductors-fieldbus.json
# Validate the maintenance license token itself
curl -H "Authorization: Bearer $CONTROLLER_TOKEN" \ https://controller.plant.local/api/v1/me \ > semiconductors-me.json

Multi-cell rate-limit + retry policy via shared client wrapper

When the Semiconductors, Metrology Equipment Error Codes (KLA-Tencor SP-Series, Hitachi CD-SEM, Bruker AFM, Onto Innovation), 2026 integration runs across multiple cells or controller types, every consumer needs the same backoff, jitter, and idempotency behavior or one noisy cell will starve the rest of the MES poller. Wrap the OEM SDK or fetch call in a thin client that reads the rate-limit headers (X-RateLimit-Remaining, Retry-After, x-ratelimit-reset), applies full jitter (base 200ms, cap 30s, max 5 retries), and de-dupes writes by a stable key (the controller cycle id, the fieldbus drop external id, the destination MES record id). Emit simple log lines tagged with the cell id so a fieldbus burst on one cell shows up in the same log as the downstream cascade.

# Python - semiconductors controller API wrapper with full-jitter retry
from tenacity import retry, wait_random_exponential, stop_after_attempt, retry_if_exception_type
import requests class RateLimited(Exception): pass @retry( wait=wait_random_exponential(multiplier=0.2, max=30), stop=stop_after_attempt(5), retry=retry_if_exception_type(RateLimited),
)
def call_semiconductors(method, path, token, payload=None): r = requests.request(method, f"https://controller.plant.local{path}", headers={"Authorization": f"Bearer {token}"}, json=payload, timeout=10) if r.status_code == 429: raise RateLimited(r.headers.get("Retry-After")) r.raise_for_status() return r.json()

Monitor + alert via Semiconductors, Metrology Equipment Error Codes (KLA-Tencor SP-Series, Hitachi CD-SEM, Bruker AFM, Onto Innovation), 2026 OEM diagnostic reports, alarm history, and plant dashboard ingestion

For the Semiconductors, Metrology Equipment Error Codes (KLA-Tencor SP-Series, Hitachi CD-SEM, Bruker AFM, Onto Innovation), 2026, the most useful long-running telemetry is the OEM diagnostic reports + alarm history shipped to a plant dashboard (Grafana with a CSV source, Ignition with a tag history, the fab MES OEE per SEMI E10, a Notion database via the API) and graphed on a single view. Pair that with synthetic monitoring (a small script that triggers the failing cycle or runs the failing test sequence every 5 minutes from at least two cells) so a fleet-level regression lights up before teammates report it. Subscribe the on-call inbox or a private Teams channel to the Semiconductors, Metrology Equipment Error Codes (KLA-Tencor SP-Series, Hitachi CD-SEM, Bruker AFM, Onto Innovation), 2026 OEM service bulletin (Atom/RSS or vendor portal webhook) plus the OEM service-status handle so an open bulletin self-correlates with the synthetic failures.

# Tiny synthetic monitor - hit the Semiconductors, Metrology Equipment Error Codes (KLA-Tencor SP-Series, Hitachi CD-SEM, Bruker AFM, Onto Innovation), 2026 controller health endpoint every 5 minutes
while true; do curl -s -o /dev/null -w "%{http_code} %{time_total} $(date -Iseconds)\n" \ -H "Authorization: Bearer $TOKEN" \ https://controller.plant.local/api/v1/me \ >> /var/log/semiconductors-synth.log sleep 300
done

Common pitfalls and what to watch for

Read-only validation before any write is the single step most Semiconductors, Metrology Equipment Error Codes (KLA-Tencor SP-Series, Hitachi CD-SEM, Bruker AFM, Onto Innovation), 2026 fixes skip, and it is the step that lets you roll back when a fix backfires. Photograph every existing parameter page (the axis parameters, the spindle parameters, the safety parameters, the I/O mapping, the recipe library), capture the failing photo in a notes entry, export the relevant log to CSV if the controller supports it (the OEM diagnostic tool fault-history export, the PMC log download), and photograph the HMI alarm history showing the failing window before any change. On Semiconductors, Metrology Equipment Error Codes (KLA-Tencor SP-Series, Hitachi CD-SEM, Bruker AFM, Onto Innovation), 2026 cells with multiple operating modes (manual jog, MDI, auto) record the firmware revision, the parameter state, and the I/O mapping in each before toggling anything, because a "fix" pushed only to manual mode is a known regression vector when auto mode has a different interlock set.

The mirror-image mistake is confusing a cell-level symptom with an OEM fault on Semiconductors, Metrology Equipment Error Codes (KLA-Tencor SP-Series, Hitachi CD-SEM, Bruker AFM, Onto Innovation), 2026. A persistent SRVO-023 is often a workpiece-level change pushed by the production team rather than a Semiconductors, Metrology Equipment Error Codes (KLA-Tencor SP-Series, Hitachi CD-SEM, Bruker AFM, Onto Innovation), 2026 bug. A "program not loading" can be a renamed program rather than a deleted one. A "trigger not firing" is frequently a vibrated-loose sensor cable or a contaminated lens rather than an OEM-side regression.

Verify the fix worked

• Reproduce the original faulting cycle against Semiconductors, Metrology Equipment Error Codes (KLA-Tencor SP-Series, Hitachi CD-SEM, Bruker AFM, Onto Innovation), 2026 on the same cell AND a sister cell with the same recipe. If the alarm or fault code still surfaces on any cell, you have not fixed it.
• Watch for 24 to 48 hours via the Semiconductors, Metrology Equipment Error Codes (KLA-Tencor SP-Series, Hitachi CD-SEM, Bruker AFM, Onto Innovation), 2026 controller alarm history + the fieldbus log + your fault-history notebook. Cached fault states and stale fieldbus link state mask slow-burn drift and intermittent fieldbus issues.
• Smoke-test under realistic load: replay the cycle against a test workpiece for at least 30 minutes at your normal production feedrate, log success / alarm and the timestamp per attempt to a notes file.
• Capture the new state in a fault-history notebook entry so the next time this happens you do not rediscover it. Note firmware revision + parameter set + I/O mapping + failing photo + verbatim alarm string + fix applied. Push to a plant-wide maintenance wiki if your plant uses one.
• If the fix involved a maintenance-token rotation or a parameter set change, commit the new token to your password manager and photograph the parameter dump for archival.

Safety, rollback, blast radius

• Test in a Semiconductors, Metrology Equipment Error Codes (KLA-Tencor SP-Series, Hitachi CD-SEM, Bruker AFM, Onto Innovation), 2026 maintenance mode or on a sister cell first before any change that touches the production cell. Snapshot the firmware revision, the parameter set, the I/O mapping, and the safety-PLC permissions before changing anything.
• Apply the principle of least surprise when granting teach-pendant access or safety-PLC permissions. Review the operator roster against the people who actually need access - extra teach pendants are extra blast radius.
• Use idempotent cycles where the Semiconductors, Metrology Equipment Error Codes (KLA-Tencor SP-Series, Hitachi CD-SEM, Bruker AFM, Onto Innovation), 2026 controller supports it (the OEM cycle-id de-dupe, external id keys on MES records) so a re-run cycle does not double-count parts or duplicate scrap records.
• Know your rollback path. Firmware rollback is a one-line OEM utility load; a maintenance-token rotation is reversible if you kept the old token in the password manager during cutover; a parameter set change is reversible only if you saved the previous archive.
• For cell-wide or plant-wide changes, line up a maintenance window with production scheduling before pushing through the OEM utility.

FAQ

Related fixes

Related guides worth a look while you sort this one out:

• how to clear Hitachi CD-SEM stage-XY-not-at-target alarm after emergency stop
• how to clear KLA SP haze TIR clipping flag at the wafer edge exclusion zone
• how to clear KLA SP5 wafer pre-align mark-not-found alarm on production lot
• how to debug KLA Archer overlay measurement no-signal on a critical layer mark
• how to fix KLA SP3 dark-field scan laser-power-low warning before sensitivity run
• how to fix Onto Innovation NovaScan film-thickness ellipsometry fit-error R-squared low