Semi E130

SEMI E130 defines a reference prober model for a 300 mm wafer-probe environment — PSEM300 — a standardized description of the mechanical, electrical, and software interfaces a wafer prober presents so that probers from different vendors can be integrated into the same 300 mm fab automation scheme without each one requiring custom integration work. A wafer prober sits at the boundary between front-end fab automation (wafer handling, carrier interfaces, factory scheduling) and the test floor's electrical measurement equipment, and without a shared model for what a prober's own automation surface looks like — its wafer-handling geometry, its coordinate system, its load/unload sequencing, its status and control signals — every prober integration becomes a one-off engineering exercise repeated per vendor, per fab.

Each prober vendor exposes automation differently
Different coordinate systems, load sequencing, status signaling
SEMI E130 — PSEM300 reference prober modelStandardized mechanical, electrical, and software interface description
Common wafer-handling geometry and coordinate reference
A fixed frame of reference every prober maps to
Standardized load/unload sequencing and status/control signals
One integration contract instead of vendor-specific wiring
A 300 mm prober integrates into fab automation without custom engineering per vendor
Host software and AMHS interact with one model, not N vendor variants

The reason a dedicated prober model was needed, rather than relying on E30's general GEM/SECS-II equipment communication model alone, is that a prober has physical and procedural details — probe-card alignment, chuck movement, die-by-die stepping across a wafer map — that no generic equipment model captures. GEM/SECS-II (E30) standardizes the communication protocol layer, but it says nothing about what a prober's wafer-handling geometry looks like, how its chuck coordinate system relates to the wafer map, or what sequence of events constitutes a normal load-align-step-unload cycle; E130 fills that gap by defining the PSEM300 model specifically for 300 mm probers, so host software written against PSEM300 can drive a probe step sequence, interpret chuck position, and track wafer-map progress consistently regardless of which vendor built the prober underneath it.

SEMI E130 — The Prober Model GEM/SECS-II Doesn't Cover E30 standardizes the wire protocol; E130 standardizes what a prober actually does on it SEMI E30 — GEM/SECS-II Generic equipment communication: message framing, state model, alarms, remote commands Says nothing about: chuck geometry, wafer-map stepping, probe-card alignment sequencing SEMI E130 — PSEM300 Prober-specific model built on top: chuck/coordinate reference frame, load-align-step-unload sequencing, wafer-map progress tracking Same vendor-neutral integration regardless of prober manufacturer

E130 is what lets a 300 mm fab treat wafer probers as interchangeable automation participants rather than vendor-specific black boxes — by defining PSEM300's wafer-handling geometry, coordinate reference, and load/step/unload sequencing on top of the generic GEM/SECS-II communication layer E30 already provides, it closes the gap between "the prober can talk to the host" and "the host actually understands what the prober is doing."

Take SEMI E130 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