how to recover ASML reticle handler RH not-ready alarm after pellicle frame mis-detect

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 recover ASML reticle handler RH not-ready alarm after pellicle frame mis-detect 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 recover asml reticle handler rh not-ready alarm after pellicle frame mis-detect 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 in my experience the most useful first-pass tools are ASML APV (Application Performance Viewer) for overlay/focus trend analysis, ASML TIS/ILIAS sensor self-check screen, KLA Archer overlay metrology analysis package. 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 export overlay residual KPI from BaseLiner and check 3-sigma against spec and check stage servo error trace during exposure scan via APV waveform view. 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: ontoinnovation.com, nikon.com/business/semi, asml.com/support. 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

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.

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

Third pass: read the alarm code and the alarm message like an x-ray of your Semiconductors, Lithography Error Codes (Steppers, Scanners, EUV Reticle Handling, Focus/Dose/Overlay), 2026 cell. Servo faults (SRVO-023 servo overcurrent, SRVO-068 overheat, SRVO-014 motor overload) point at the drive, the cable, or the motor itself - 023 = instantaneous overcurrent during accel, 014 = sustained thermal overload during a heavy duty cycle, 068 = ambient or coolant fault on the drive heatsink. Axis or motion faults (4078 absolute position lost, OT001 over-travel, EX1043 spindle alarm) point at encoder battery, hardstops, or the spindle drive. Vision faults (Cognex In-Sight 5403 timeout, 5404 illumination, 5410 acquisition) point at trigger, lighting, or the GigE link. Cross-reference the alarm code against the OEM fault-code list - SCPI instruments will return the same hex code via SYST:ERR? that the front panel shows. If the same alarm cycles between SRVO-023 and SRVO-068 over a tight loop, the duty cycle is exceeding the drive thermal envelope - back off the feedrate or add a duty-cycle dwell.

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

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. In Semiconductors work the cost of guessing is measured in scrap and downtime, so I read the Semiconductors release notes before I touch a setpoint, every time, no exceptions. 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.

Tools I actually reach for

For most Semiconductors, Lithography Error Codes (Steppers, Scanners, EUV Reticle Handling, Focus/Dose/Overlay), 2026 faults I start with Nikon NSR maintenance console (Stage / RS alarm pages), fall back to Onto Innovation NovaMARS overlay analysis, ASML TIS/ILIAS sensor self-check screen, KLA Archer overlay metrology analysis package when Nikon NSR maintenance console (Stage / RS alarm pages) cannot surface the answer, and keep ASML reticle inspection system (Lasertec MATRICS) tie-in 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.

export overlay residual KPI from BaseLiner and check 3-sigma against 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.

confirm reticle pod presence via inner pod handler (IPH) sensor state in eDiagnostics

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 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. I usually check ontoinnovation.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 canon.com/lithography 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

When the Semiconductors, Lithography Error Codes (Steppers, Scanners, EUV Reticle Handling, Focus/Dose/Overlay), 2026 controller returns intermittent alarms, cycle delays, or "something went wrong" under normal load, suspect the OEM firmware or a wiring intermittent before blaming the cell. Subscribe to the Semiconductors, Lithography Error Codes (Steppers, Scanners, EUV Reticle Handling, Focus/Dose/Overlay), 2026 OEM service bulletin RSS or hotline notification so an open bulletin lights up your inbox or Teams automatically. Cross-check the OEM Trust Center or maintenance portal for any planned firmware push covering your machine series. Listen to the OEM controls-community forum and r/semiconductors - many regressions land there 15 to 30 minutes before the formal bulletin update. Decision point: if no bulletin is open but multiple teammates in the same plant are seeing the same alarm, fail over to a sister cell (if a sister machine exists) or to a backup parameter set (if the saved archive is current) and file an OEM service ticket with the alarm history dump, the controller serial number, and the timestamp window; major OEMs all accept the controller serial number as the primary trace key. Photograph the faulting cell with the HMI and the firmware version visible before the failover - that photo is what the OEM field service engineer asks for first on any alarm or cycle-time complaint.

Before any destructive step on a Semiconductors, Lithography Error Codes (Steppers, Scanners, EUV Reticle Handling, Focus/Dose/Overlay), 2026 cell, slow down and stage rollback. Snapshot the current firmware revision, the current parameter set (PARAM PUNCH OUT, KUKA archive, Cognex job export), the current ladder and HMI screens, the current I/O mapping, and the current member-roster of teach pendants registered to the cell to a notes entry first. Capture the failing photo, the Semiconductors, Lithography Error Codes (Steppers, Scanners, EUV Reticle Handling, Focus/Dose/Overlay), 2026 alarm history dump, and the timestamp window. Photograph the cell from two angles: the controller HMI showing the alarm, and the cabinet showing the drive status LEDs. Then do the destructive step (clear a parameter, swap a drive, remove a teach pendant, restore a backup) inside a maintenance mode or a sister cell first, never the production cell directly. Capture the firmware revision, the safety-PLC permissions, the connected-pendant list, the cell operator roster, and the relevant fieldbus log snapshot to your notes before the destructive step. Decision point: if the cell is under an OEM service contract, the cheapest correct path is almost always to open the OEM hotline in parallel with the rollback - the OEM service engineer can confirm whether an OEM-side firmware push is responsible while you are still staging the change, which avoids a needless parameter edit if the fix is in the next firmware revision.

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.

Automate this fix so you do not do it twice

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

Monitor + alert via Semiconductors, Lithography Error Codes (Steppers, Scanners, EUV Reticle Handling, Focus/Dose/Overlay), 2026 OEM diagnostic reports, alarm history, and plant dashboard ingestion

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

Scrape Semiconductors, Lithography Error Codes (Steppers, Scanners, EUV Reticle Handling, Focus/Dose/Overlay), 2026 controller alarm history + fieldbus log via scheduled job

For the Semiconductors, Lithography Error Codes (Steppers, Scanners, EUV Reticle Handling, Focus/Dose/Overlay), 2026, cell faults usually surface as drive alarms, fieldbus dropouts, or vision-trigger misses before a full line stoppage. A weekly scheduled job that exports the last 7 days of these events to CSV gives you a paper trail to correlate with firmware updates, parameter edits, and OEM bulletins without staring at the HMI live. Register the task via cron on a plant-floor logger PC (Linux IPC), Windows Task Scheduler (schtasks /create /XML) on an engineering workstation, or a GitHub Actions schedule against a cell-controller API, then write the CSV to a plant file share or the fab MES for retention. Subscribe a simple dashboard (Grafana with a CSV source, Ignition with a tag history, the fab MES OEE report) to the same bucket so alarm events from every Semiconductors, Lithography Error Codes (Steppers, Scanners, EUV Reticle Handling, Focus/Dose/Overlay), 2026 controller converge on a single view without per-cell HMI clicking.

# Export the controller alarm history via the OEM API (if supported)
curl -X POST https://controller.plant.local/api/v1/alarm_history \ -H "Authorization: Bearer $CONTROLLER_TOKEN" \ -H "Accept: application/json" \ -d '{"start_date":"2026-05-25","end_date":"2026-06-01"}' \ -o semiconductors-alarm-history.json
# Export the cycle history for the last 7 days
curl -G https://controller.plant.local/api/v1/cycles \ -H "Authorization: Bearer $CONTROLLER_TOKEN" \ --data-urlencode "oldest=$(date -d '7 days ago' +%s)" \ -o semiconductors-cycles.json

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 fix ASML NXE:3400 focus drift alarm after EUV mirror contamination cleanup
• how to fix ASML NXT WaferSync collision-avoidance alarm with reticle stage
• how to recover ASML stage hot-swap alarm on long-stroke motor over-current
• how to fix ASML AGI/Athena alignment color-grating signal-low after laser source aging
• how to fix ASML immersion hood water-loss alarm during scanning at high stage speed
• how to interpret ASML production-system reticle-not-on-stage waiting alarm