Semi E123.1

SEMI E123.1 defines the exact SECS-II message set for HSEM — the specific status-variable IDs (SVIDs), report IDs (RPTIDs), and collection-event IDs (CEIDs) a device handler uses to report output-bin sort results, tray/tube fill level, pick-and-place cycle status, and jam/alarm conditions over the wire — rather than the general handler-vocabulary concept E123 establishes. E123 says an HSEM-compliant handler has to expose bin-sort, fill-level, and cycle-state information through a defined vendor-neutral vocabulary; E123.1 is the protocol-binding companion that fixes precisely which SECS-II messages and variable numbers carry that vocabulary, the same relationship E122.1 has to E122 — now the handler side of the test cell gets the same wire-level guarantee the tester side already has.

SEMI E123 says: expose bin sort, fill level, cycle/jam status
Defined vocabulary, but no fixed wire-level message set
SEMI E123.1 — SECS-II protocol binding for HSEMFixes the actual SVID/RPTID/CEID numbers
Defined SVIDs for bin sort, tray/tube fill, cycle state
Same variable numbers across every compliant handler
Defined CEIDs for pick/place cycles and jam/alarm events
No vendor-specific interpretation of the report structure
Host's GEM driver parses any handler's HSEM report identically
No per-vendor translation layer for bin/fill/jam reporting

The reason E123 needed its own protocol-binding companion is the identical gap E122.1 closed for TSEM: a defined vocabulary in prose still leaves the SVID, RPTID, and CEID numbers open to each handler vendor's own implementation, so two E123-compliant handlers can report the same output-bin sort using different variable IDs the host has to reconcile by hand. E123.1 removes that gap by fixing the SECS-II message set itself, so a fab's test-floor host software can write one GEM driver against E123.1's defined numbering scheme and have it work against any handler implementing HSEM, rather than maintaining a per-vendor mapping table for bin, fill, and jam data.

SEMI E123.1 — Fixing HSEM's Wire-Level Numbers the handler side now gets the same guarantee TSEM already has SEMI E123 (HSEM) "Expose bin sort, fill level, cycle/jam status" Vocabulary, numbering left open SEMI E123.1 Fixed SVID/RPTID/CEID numbers for every field Wire-level protocol binding Two E123-compliant handlers can still number their bin SVIDs differently E123.1 is what makes their reports byte-for-byte interchangeable

E123.1 completes HSEM the same way E122.1 completed TSEM: E123 defines what a handler has to communicate, and E123.1 is the fixed SECS-II numbering scheme that makes that communication identical across vendors, so a fab's test-cell host software now has the same plug-and-play guarantee on both the tester side and the handler side.

Take SEMI E123.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