how to clear Nikon NSR-S631E scanner reticle stage RS over-travel limit alarm

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

Running into how to clear Nikon NSR-S631E scanner reticle stage RS over-travel limit alarm on Semiconductors, Lithography Error Codes (Steppers, Scanners, EUV Reticle Handling, Focus/Dose/Overlay), 2026 is one of the more common 2am callouts I see when the line is in the middle of a hot run and the controller suddenly faults out. My standard pattern for this is to pull the alarm history first, then walk the fix below - here is what actually clears the alarm when the OEM service manual is too generic and you do not have time to wait for a field service engineer to drive in.

What how to clear nikon nsr-s631e scanner reticle stage rs over-travel limit alarm actually involves on Semiconductors, Lithography Error Codes (Steppers, Scanners, EUV Reticle Handling, Focus/Dose/Overlay), 2026

On Semiconductors, Lithography Error Codes (Steppers, Scanners, EUV Reticle Handling, Focus/Dose/Overlay), 2026 on a fresh callout the tools I crack open first are Nikon NSR maintenance console (Stage / RS alarm pages), ASML TIS/ILIAS sensor self-check screen, ASML eDiagnostics for scanner alarms and lot-hold management. 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, Lithography Error Codes (Steppers, Scanners, EUV Reticle Handling, Focus/Dose/Overlay), 2026, the methods that survive contact with a real second-shift production workload are verify EUV source IF power log trend over last 24 hours via Cymer UI and run ASML TIS calibration and verify TIS-A vs TIS-B sensor agreement within nm spec. Anything less than that and you are shipping on vibes.

Authoritative sources for Semiconductors, Lithography Error Codes (Steppers, Scanners, EUV Reticle Handling, Focus/Dose/Overlay), 2026 that I cross-reference before committing to a fix: nikon.com/business/semi, kla.com, canon.com/lithography. 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

Sixth: pin down the timing and reliability envelope on the Semiconductors, Lithography Error Codes (Steppers, Scanners, EUV Reticle Handling, Focus/Dose/Overlay), 2026 cell under real working conditions. Run a long-duration sanity test by executing the failing program 10 times over 15 minutes, logging the timestamp and the result (cycle complete / alarm code / which axis or station faulted) per attempt to a notes file. Watch for the breakpoint where the cycle success rate dips below 80 percent - that is your real signal that something is wrong, not the one-off alarm that prompted the callout. If you are on a marginal supply (low ambient temp, brownout, dirty 3-phase, contaminated coolant), run the same test on a known-good supply or a sister cell before assuming the controller is the problem. Capture the breakpoint in your personal notes next to the firmware version, the parameter set, and the controller serial number - the next time this happens to a teammate, the notes are gold.

Start by capturing the exact failure signal in writing before you change a single thing on your Semiconductors, Lithography Error Codes (Steppers, Scanners, EUV Reticle Handling, Focus/Dose/Overlay), 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."

Second pass: open the Semiconductors, Lithography Error Codes (Steppers, Scanners, EUV Reticle Handling, Focus/Dose/Overlay), 2026 controller diagnostic panel and read the alarm history or fault stack for the failing window. Most modern industrial controllers surface a fault trail (the controller alarm history, the OEM diagnostic interface, the fab MES event log, the cell controller PLC fault table). The alarm history tells you whether the fault was a real condition, a teammate changing a parameter or DI mapping in the same minute, or an OEM-side firmware quirk. Many SRVO or AXIS faults trace to a parameter-level change pushed in the same engineering session in the previous hour - the fault trail makes that obvious without guesswork.

Field notes from real Semiconductors, Lithography Error Codes (Steppers, Scanners, EUV Reticle Handling, Focus/Dose/Overlay), 2026 callouts

Whenever a control room operator radios me about a Semiconductors fault, I will not climb the ladder until I have Nikon NSR maintenance console (Stage / RS alarm pages) powered up and the last-known-good readings in front of me. 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. After every Semiconductors repair I run `compare CD-SEM measured CD against scanner dose-mapper control point` to confirm the loop actually held, it takes thirty seconds and has saved me at least one callback per month.

Tools I actually reach for

For most Semiconductors, Lithography Error Codes (Steppers, Scanners, EUV Reticle Handling, Focus/Dose/Overlay), 2026 faults I start with ASML reticle inspection system (Lasertec MATRICS) tie-in, fall back to Onto Innovation NovaMARS overlay analysis, KLA SensArray wireless wafer for dose/focus map verification, KLA Archer overlay metrology analysis package when ASML reticle inspection system (Lasertec MATRICS) tie-in cannot surface the answer, and keep ASML eDiagnostics for scanner alarms and lot-hold management 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, Lithography Error Codes (Steppers, Scanners, EUV Reticle Handling, Focus/Dose/Overlay), 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.

run ASML TIS calibration and verify TIS-A vs TIS-B sensor agreement within nm spec

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.

validate alignment WGA signal strength on every alignment mark color before lot release

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.

compare CD-SEM measured CD against scanner dose-mapper control point

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 stage servo error trace during exposure scan via APV waveform view

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, Lithography Error Codes (Steppers, Scanners, EUV Reticle Handling, Focus/Dose/Overlay), 2026 detail, the disambiguation order I lean on is stable. I usually check kla.com for the ground-truth view on this part of Semiconductors, Lithography Error Codes (Steppers, Scanners, EUV Reticle Handling, Focus/Dose/Overlay), 2026. I usually check semi.org/standards for the ground-truth view on this part of Semiconductors, Lithography Error Codes (Steppers, Scanners, EUV Reticle Handling, Focus/Dose/Overlay), 2026. I usually check asml.com/support for the ground-truth view on this part of Semiconductors, Lithography Error Codes (Steppers, Scanners, EUV Reticle Handling, Focus/Dose/Overlay), 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, Lithography Error Codes (Steppers, Scanners, EUV Reticle Handling, Focus/Dose/Overlay), 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, Lithography Error Codes (Steppers, Scanners, EUV Reticle Handling, Focus/Dose/Overlay), 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, Lithography Error Codes (Steppers, Scanners, EUV Reticle Handling, Focus/Dose/Overlay), 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.

If the Semiconductors, Lithography Error Codes (Steppers, Scanners, EUV Reticle Handling, Focus/Dose/Overlay), 2026 symptom started after an overnight firmware update, a drive swap, or a parameter edit, treat firmware and parameter set as the prime suspect. Roll the controller back to the previous firmware if the Semiconductors, Lithography Error Codes (Steppers, Scanners, EUV Reticle Handling, Focus/Dose/Overlay), 2026 OEM supports rollback (most do via the maintenance bootloader). Restore the saved parameter set from your last known good backup (Fanuc all-parameter PUNCH OUT, KUKA archive, Cognex In-Sight job export) and rerun the program. If both rolled-back firmware and restored parameter set still fault with the same alarm and the same drive, you have a hardware-level or wiring issue. Decision point: if the rolled-back firmware still faults and the cell is under an OEM service contract, open the OEM hotline with the alarm history dump; on an out-of-warranty cell the path is the OEM forum or r/semiconductors with a minimal reproduction. Save the working firmware revision to your notes so the next rollback is a one-line "pin to firmware X."

Automate this fix so you do not do it twice

Automate Semiconductors, Lithography Error Codes (Steppers, Scanners, EUV Reticle Handling, Focus/Dose/Overlay), 2026 parameter + I/O mapping snapshots via OEM utility or API

On the Semiconductors, Lithography Error Codes (Steppers, Scanners, EUV Reticle Handling, Focus/Dose/Overlay), 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, Lithography Error Codes (Steppers, Scanners, EUV Reticle Handling, Focus/Dose/Overlay), 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()

Codify the firmware revision pin and rollback as a single notes entry

Once a stable firmware revision is identified for the Semiconductors, Lithography Error Codes (Steppers, Scanners, EUV Reticle Handling, Focus/Dose/Overlay), 2026, write the revision string, the build hash, and the parameter set state to a fault-history notebook entry with the date in the title. Reproducible rollback is then a single OEM utility load plus a parameter restore. Pin the parameter set state explicitly so an OEM-side default change does not silently shift behavior under you. Stage the notebook entry next to a checklist that lists the failing photo, the Semiconductors, Lithography Error Codes (Steppers, Scanners, EUV Reticle Handling, Focus/Dose/Overlay), 2026 alarm history dump (if any), and the OEM case number; the second time the cell faults at 9 a.m. you do not want to be rediscovering which firmware revision was actually green.

# Fault-history notebook template (semiconductors)
Date: 2026-06-01
Controller: semiconductors
Working firmware: 30iB-Plus 02.20 (Build hash: a1b2c3d)
Cell: Line 4 Cell B
Machine serial: SN-semiconductors-12345
Failing photo: ~/notes/semiconductors-2026-06-01.jpg
OEM case: OEM-semiconductors-12345
Rollback path: load previous firmware from OEM utility, master OFF, restore parameter archive, power up

Common pitfalls and what to watch for

The deepest trap with Semiconductors, Lithography Error Codes (Steppers, Scanners, EUV Reticle Handling, Focus/Dose/Overlay), 2026 cells is treating a recurring class of alarm as a one-off incident. A drive overheat or a vision-trigger miss burst gets papered over with a power-cycle or a parameter reset, the cell runs for two weeks, and the exact same signature returns because the root cause was never identified. Codify every case in a fault-history notebook per machine, save the working firmware revision (the About panel) in the same note, and write the exact parameter set, I/O mapping, and fieldbus drop list into a checklist. After any major firmware update on Semiconductors, Lithography Error Codes (Steppers, Scanners, EUV Reticle Handling, Focus/Dose/Overlay), 2026 review the parameter set and the I/O mapping explicitly, since OEMs silently change defaults or add new safety interlocks between major releases.

The second half of this pitfall is confirming the fix on a single cell when the cell is part of a fleet. If you and three teammates run the same Semiconductors, Lithography Error Codes (Steppers, Scanners, EUV Reticle Handling, Focus/Dose/Overlay), 2026 controller on the same production line, an OEM-side firmware push tends to bite a whole batch within the same shift. Verify on every cell that runs the failing recipe, log the result and the firmware revision per attempt, and only then declare the class closed.

Verify the fix worked

• Reproduce the original faulting cycle against Semiconductors, Lithography Error Codes (Steppers, Scanners, EUV Reticle Handling, Focus/Dose/Overlay), 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, Lithography Error Codes (Steppers, Scanners, EUV Reticle Handling, Focus/Dose/Overlay), 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, Lithography Error Codes (Steppers, Scanners, EUV Reticle Handling, Focus/Dose/Overlay), 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, Lithography Error Codes (Steppers, Scanners, EUV Reticle Handling, Focus/Dose/Overlay), 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 ASML scanner dose-mapper out-of-control limit on a critical poly layer
• how to interpret ASML production-system reticle-not-on-stage waiting alarm
• how to recover ASML stage hot-swap alarm on long-stroke motor over-current
• how to clear scanner-to-track interface handoff fault between TEL Clean Track and ASML
• how to debug an EUV reticle pod contamination alert at the inner pod handler
• how to fix ASML NXT WaferSync collision-avoidance alarm with reticle stage