Connect legacy equipment to your host through SECS/GEM
The MST SECS/GEM gateway sits in front of an existing tool and speaks HSMS or SECS-I to the fab host with a full E30 GEM state model. The tool keeps its RS-232, Modbus, TCP or PLC interface; the host sees a GEM-compliant equipment.
- HSMS (E37) and SECS-I (E4)
- E30 GEM state model
- Alarms · events · recipes · data collection
- US$4,500 per unit
- Runs inside your own network
Who this is for
- Fabs and OSATs with 200 mm tools that never had a host interface, or whose vendor no longer supports one
- Equipment makers whose customers demand SECS/GEM compliance and who do not want to build the protocol stack
- Integrators bridging RS-232, ASCII, Modbus, OPC UA or PLC-style tools into an MES or a GEM300 host
- Teams that need alarms, events and recipe management on the host before the next audit
How the first tool gets onto the host
- 130-minute scoping call
Equipment type, current controller and protocol, target host, one representative scenario. Non-confidential; no logs or manuals needed yet.
- 2Equipment model agreed
We map the tool's states, alarms, events, variables and recipes to the E30 GEM model and send you the mapping sheet for sign-off.
- 3Gateway installed
Installed on a computer on your equipment network. Web configuration and status view.
- 4Host connection and dry run
HSMS or SECS-I to your host, S1/S2/S5/S6/S7 streams exercised, normal, timeout, disconnect and recovery scenarios recorded.
- 5Acceptance checklist
You sign off against the scenario list. Per-unit licence with one year of updates; mapping for further tools is quoted per tool.
The integration schedule is confirmed after reviewing the equipment protocol, model mapping, host testing and acceptance scope. Proprietary protocols and special state machines require separate assessment.
Questions buyers ask
Is the gateway GEM300 compliant, or GEM only?
The gateway implements the E30 GEM state model over HSMS (E37) and SECS-I (E4), which is what a 200 mm host expects. The E40/E87/E90/E94 GEM300 job, carrier, substrate and control-job models are quoted per project; tell us on the scoping call whether your host is GEM300.
Our tool only has RS-232, Modbus or a PLC. Can it still be SECS/GEM?
Yes. That is the case the gateway is built for: it talks to the tool on its existing interface and presents a GEM equipment to the host. The equipment model maps the tool's real states and signals; nothing is changed on the tool controller.
How can an OEM add SECS/GEM without writing the protocol stack?
Ship the gateway with the machine, on the machine's own computer or a small industrial PC. Your firmware keeps its interface; the gateway carries HSMS, the GEM state model, alarms, events and recipes. One licence per machine, updates for one year.
What exactly does US$4,500 include?
One gateway licence for one tool: HSMS and SECS-I, the E30 GEM state model, alarms, events, recipes and data collection, the web configuration and one year of updates. The equipment-model mapping for the first tool is quoted separately.
How do we prove it works before the fab accepts it?
Every scenario in the acceptance list is exercised against your host and recorded: connection, communication state, alarms, events, recipe upload and download, timeout and recovery. You sign off against that list, not against a demo.
Does any data leave our site?
No. The gateway runs on your network, on your own hardware. There is no cloud dependency and no telemetry.
Read the protocol first
MST publishes the SECS/GEM guides most engineers find on Google. They explain the protocol; this page sells the gateway.
Order the gateway
Choose the licence and the number of tools. MST confirms the order, the mapping quote for the first tool, delivery and invoice terms by email before anything is charged.
Per-unit licence · delivery and support confirmed in the quote