Semi E118.1

SEMI E118.1 defines the exact SECS-I/SECS-II message set for a wafer-ID reader — the specific status variables (SVIDs), collection-event IDs (CEIDs), and S6F11/S2F13-class message formats a reader uses to report a read attempt, read success, read failure, and decoded wafer-ID string to the host — rather than the general reporting behavior E118's interface standard establishes. E118 says a wafer-ID reader has to report success, failure, and the decoded string through a defined interface; E118.1 is the protocol-binding companion that pins down precisely which SECS messages and variable IDs carry that information over the wire, the same relationship E99.1 has to E99 and E116.1 has to E116.

SEMI E118 says: report read status and decoded ID
A behavioral requirement, not a wire-level message set
SEMI E118.1 — SECS-I/SECS-II protocol bindingFixes the actual SVID/CEID/message set
Defined SVIDs for read-status and decoded-ID string
Same variable IDs across every compliant reader
Defined CEIDs and message formats for read events
No vendor-specific interpretation of the report structure
Host's GEM driver parses any vendor's wafer-ID report identically
No per-vendor translation layer for read events

The reason E118 needed its own protocol-binding companion is the same gap E99/E99.1 and E116/E116.1 each closed: a standard that defines reporting behavior in prose still leaves the SVID numbers, CEID numbers, and message format open to each vendor's own implementation choices, so two E118-compliant readers can report the same successful read using different variable IDs that the host has to reconcile manually. E118.1 removes that gap by fixing the SECS-I/SECS-II message set itself, so a host integrator can write one GEM driver against E118.1's defined SVID/CEID scheme and have it work against any wafer-ID reader on the floor, rather than maintaining a separate mapping table per reader vendor.

SEMI E118.1 — Fixing the SVID/CEID Numbers, Not Just the Behavior "report success/failure/ID" still leaves the variable numbering open SEMI E118 "Report read status and decoded ID to the host" Behavioral requirement SEMI E118.1 Fixed SVID/CEID numbers, defined message format Wire-level protocol binding Two E118-compliant readers can still use different variable numbers E118.1 is what makes their reports byte-for-byte interchangeable

E118.1 completes the wafer-ID reader standard the same way its companions complete theirs: E118 defines what the reader has to communicate, and E118.1 is the fixed SECS-I/SECS-II message set that makes that communication identical across vendors, so a fab's host software never has to special-case a reader by brand to get a usable wafer ID out of it.

Take SEMI E118.1 further

Ask the copilot about this term, or have our engineers assess it against your process.

Ask CFSGPT about this → Request a technical assessment → Open the CFS app