Semiconductors: Lithography Error Codes (Steppers, Scanners, EUV Reticle Handling, Focus/Dose/Overlay), 2026

how to recover ASML stage hot-swap alarm on long-stroke motor over-current

Q: How long does how to recover asml stage hot-swap alarm on long-stroke motor over-current typically take on Semiconductors — Lithography Error Codes (Steppers, Scanners, EUV Reticle Handling, Focus/Dose/Overlay) — 2026?

For most Semiconductors — Lithography Error Codes (Steppers, Scanners, EUV Reticle Handling, Focus/Dose/Overlay) — 2026 cells, 5 to 30 minutes including verification. Large fleet retrofits, anything touching maintenance-token rotation or safety-PLC cutover, or cross-cell parameter migrations can stretch to half a shift because you have to wait for production-window clearance, OEM re-licensing, or coordinated maintenance windows.

Q: Is there a rollback path?

Yes for most Semiconductors — Lithography Error Codes (Steppers, Scanners, EUV Reticle Handling, Focus/Dose/Overlay) — 2026 changes. Snapshot the firmware revision, photograph the parameter set, export the alarm history, and write down the maintenance token before any change. A few operations are one-way (cleared fault history past the OEM retention window, irreversible safety-PLC fuse, permanently revoked teach pendants). Check the in-controller maintenance help for the specific operation before you commit.

Q: Will this affect other cells in the Semiconductors — Lithography Error Codes (Steppers, Scanners, EUV Reticle Handling, Focus/Dose/Overlay) — 2026 fleet?

Often yes. Semiconductors — Lithography Error Codes (Steppers, Scanners, EUV Reticle Handling, Focus/Dose/Overlay) — 2026 fleets share safety-PLC policies, OEM service-contract quotas, operator rosters, and fieldbus permissions across the whole plant (one maintenance-token grant holds permissions for many cells, one safety-PLC policy covers all stations, one service-contract tier covers all members). Use the Semiconductors — Lithography Error Codes (Steppers, Scanners, EUV Reticle Handling, Focus/Dose/Overlay) — 2026 OEM alarm history and the fieldbus drop list to enumerate dependencies before changing a shared component.

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

At a glance

Controller	Semiconductors. Lithography Error Codes (Steppers, Scanners, EUV Reticle Handling, Focus/Dose/Overlay), 2026
Category	Industrial Error Codes
Guide type	Procedure
Skill level	Beginner to intermediate field service tech
Time	5 - 30 minutes including verification

how to recover ASML stage hot-swap alarm on long-stroke motor over-current on Semiconductors, Lithography Error Codes (Steppers, Scanners, EUV Reticle Handling, Focus/Dose/Overlay), 2026 comes up often enough on the shop floor and in the OEM service bulletins that there is a stable recovery pattern. My first step on any semiconductors fault is to read the alarm history before touching the reset button - last week the cell controller hit this exact alarm during a tool change and the recovery path is mostly known, the OEM manual just buries it under three layers of cross-referenced parameter tables.

What how to recover asml stage hot-swap alarm on long-stroke motor over-current 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 Nikon NSR maintenance console (Stage / RS alarm pages), ASML eDiagnostics for scanner alarms and lot-hold management, Cymer EUV source diagnostic UI for IF power and droplet metrics. 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 export overlay residual KPI from BaseLiner and check 3-sigma against 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: canon.com/lithography, ontoinnovation.com, kla.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

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.

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.

Fourth: open the OEM service bulletin index for Semiconductors, Lithography Error Codes (Steppers, Scanners, EUV Reticle Handling, Focus/Dose/Overlay), 2026 and the upstream OEM hotline release notes for the failing window. The smoking guns are an open service bulletin touching the exact alarm class you are seeing, a recent retrofit kit covering the same symptom, or an OEM safety advisory on a partial firmware regression. Cross-reference the timestamp of your first faulted run against the bulletin issue date - if they match within the firmware revision window, stop debugging the cell and subscribe to the bulletin updates. Many OEMs lag the public bulletin index behind the actual field issue by weeks; if the OEM forum and the controls-community subreddits are both lit up but no bulletin is posted yet, trust the crowd and treat it as OEM-side until proven otherwise.

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. Last week on a graveyard shift I chased a phantom Semiconductors alarm for two hours before remembering Cymer EUV source diagnostic UI for IF power and droplet metrics would have isolated the bad channel in five minutes. 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.

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 APV (Application Performance Viewer) for overlay/focus trend analysis, fall back to Onto Innovation NovaMARS overlay analysis, ASML BaseLiner overlay control and matched-machine reporting when ASML APV (Application Performance Viewer) for overlay/focus trend analysis cannot surface the answer, and keep KLA SensArray wireless wafer for dose/focus map verification 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.

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.

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

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 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 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 kla.com 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

If the Semiconductors, Lithography Error Codes (Steppers, Scanners, EUV Reticle Handling, Focus/Dose/Overlay), 2026 controller is slow, faulting on cached errors, or HMI-locked, work the cache and parameter stack in order. Cycle controller power per the OEM lockout procedure (master disconnect off, wait 60 seconds for bus discharge, master disconnect on), reboot, and re-home the axes. Clear the local fault history (most controllers expose this under Maintenance -> Clear faults, or Setup -> Reset alarms). Re-load the saved parameter set with the OEM utility (Fanuc PARAM RESTORE, KUKA archive restore) to bypass any local parameter drift. Always capture timing before the cycle: time how long the failing cycle takes three times, write it down, then repeat after the parameter restore so the delta is provable in your notes. Decision point: managed-cell issues go through your controls engineering team for a cell-wide config push; standalone-cell issues go through the OEM diagnostic utility before you escalate to the OEM hotline.

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.

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

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

Fleet maintenance-license + OEM token rotation via OEM admin

Rotating a maintenance access token on one Semiconductors, Lithography Error Codes (Steppers, Scanners, EUV Reticle Handling, Focus/Dose/Overlay), 2026 controller by hand is fine; rotating across a fleet of cells is how you end up with twelve different tokens, four expired ones, and an unknown blast radius across the plant. Drive rotation through the Semiconductors, Lithography Error Codes (Steppers, Scanners, EUV Reticle Handling, Focus/Dose/Overlay), 2026 OEM admin SDK or REST under a service account with the rotation scope only, store the new token in a plant-wide password manager (1Password, Bitwarden, OEM secrets manager) with versioning enabled, and roll the consumer scripts one cell at a time with a health check between each. Pin the API version explicitly during rotation so a coincident OEM firmware push does not look like a rotation failure.

# Rotate the controller maintenance token (regenerate via the OEM utility, capture in 1Password)
op item create --vault Plant --category "API Credential" \ --title "semiconductors controller token 2026-06-01" \ password="$NEW_CONTROLLER_TOKEN" notes="Rotated $(date -Iseconds)"
# Capture the old token as deprecated so cutover is reversible
op item create --vault Plant --category "API Credential" \ --title "semiconductors controller token OLD 2026-06-01" \ password="$OLD_CONTROLLER_TOKEN" notes="Old token marked deprecated"

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()

Common pitfalls and what to watch for

Read-only validation before any write is the single step most Semiconductors, Lithography Error Codes (Steppers, Scanners, EUV Reticle Handling, Focus/Dose/Overlay), 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, Lithography Error Codes (Steppers, Scanners, EUV Reticle Handling, Focus/Dose/Overlay), 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, Lithography Error Codes (Steppers, Scanners, EUV Reticle Handling, Focus/Dose/Overlay), 2026. A persistent SRVO-023 is often a workpiece-level change pushed by the production team rather than a Semiconductors, Lithography Error Codes (Steppers, Scanners, EUV Reticle Handling, Focus/Dose/Overlay), 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, 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

How long does how to recover asml stage hot-swap alarm on long-stroke motor over-current typically take on Semiconductors: Lithography Error Codes (Steppers, Scanners, EUV Reticle Handling, Focus/Dose/Overlay), 2026?

For most Semiconductors. Lithography Error Codes (Steppers, Scanners, EUV Reticle Handling, Focus/Dose/Overlay), 2026 cells, 5 to 30 minutes including verification. Large fleet retrofits, anything touching maintenance-token rotation or safety-PLC cutover, or cross-cell parameter migrations can stretch to half a shift because you have to wait for production-window clearance, OEM re-licensing, or coordinated maintenance windows.

Is there a rollback path?

Yes for most Semiconductors: Lithography Error Codes (Steppers, Scanners, EUV Reticle Handling, Focus/Dose/Overlay), 2026 changes. Snapshot the firmware revision, photograph the parameter set, export the alarm history, and write down the maintenance token before any change. A few operations are one-way (cleared fault history past the OEM retention window, irreversible safety-PLC fuse, permanently revoked teach pendants). Check the in-controller maintenance help for the specific operation before you commit.

Will this affect other cells in the Semiconductors. Lithography Error Codes (Steppers, Scanners, EUV Reticle Handling, Focus/Dose/Overlay), 2026 fleet?

Often yes. Semiconductors: Lithography Error Codes (Steppers, Scanners, EUV Reticle Handling, Focus/Dose/Overlay), 2026 fleets share safety-PLC policies, OEM service-contract quotas, operator rosters, and fieldbus permissions across the whole plant (one maintenance-token grant holds permissions for many cells, one safety-PLC policy covers all stations, one service-contract tier covers all members). Use the Semiconductors. Lithography Error Codes (Steppers, Scanners, EUV Reticle Handling, Focus/Dose/Overlay), 2026 OEM alarm history and the fieldbus drop list to enumerate dependencies before changing a shared component.

What if my firmware revision or parameter set does not match these steps?

OEM defaults move between releases. The steps in this page reflect mainstream defaults as of 2026-06-01 but the underlying recovery patterns do not change as fast. If a path differs on your firmware, fall back to the in-controller maintenance help, the Semiconductors: Lithography Error Codes (Steppers, Scanners, EUV Reticle Handling, Focus/Dose/Overlay), 2026 OEM service bulletin history, or the OEM community forum - those almost always still work.

Where do I get OEM support if I am still stuck?

If you have a paid OEM service contract, open a case via the OEM hotline with: the exact verbatim alarm string, the failing photo, the cell or controller serial number, your maintenance-account email, the firmware revision, and your reproduction steps. The Semiconductors. Lithography Error Codes (Steppers, Scanners, EUV Reticle Handling, Focus/Dose/Overlay), 2026 OEM community forum and r/PLC are the no-cost public alternatives - search there first; 80 percent of common Semiconductors: Lithography Error Codes (Steppers, Scanners, EUV Reticle Handling, Focus/Dose/Overlay), 2026 alarms already have a working answer voted to the top.

References

OEM service manual for Semiconductors. Lithography Error Codes (Steppers, Scanners, EUV Reticle Handling, Focus/Dose/Overlay), 2026 (official service bulletins, alarm code reference, safety case)
Controls-community forums (r/PLC, r/Robotics, r/CNC, r/Fanuc, r/KUKA, r/Cognex, r/labview, OEM community)
In-controller diagnostic help and the Semiconductors: Lithography Error Codes (Steppers, Scanners, EUV Reticle Handling, Focus/Dose/Overlay), 2026 firmware release notes
OEM service-status portals and OEM hotline post-mortem reports

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