raphael
8686654b15
clients/python: pip-installable "secsgem-client", pure Python (stubs
pre-generated from equipment.proto, import made package-relative; no
compiled extension, no SEMI knowledge, no C++ toolchain). The API the whole
effort aimed at:
eq = Equipment("localhost:50051")
eq.set(ChamberPressure=2.5); eq["WaferCounter"] = 7
eq.fire("ProcessStarted", ChamberPressure=2.75)
eq.alarm("chiller_temp_high"); eq.clear("chiller_temp_high")
@eq.on("START")
def start(cmd): ... # auto-CompleteCommand after return
eq.listen(background=True)
eq.control_state; eq.request_control_state("HOST_OFFLINE"); eq.health()
Errors raise SecsGemError carrying the daemon's message ("no variable named
..."). bool checked before int in conversion (isinstance(True, int)).
examples/mini_tool.py is a complete GEM tool in ~25 lines.
PROOF — interop/pyclient_interop.py drives the PUBLISHED package (not raw
stubs) against a live secs_gemd with secsgem-py as the fab host: 13 checks
all green on first run — set/get round-trips, item syntax, SecsGemError on
unknown names, control state, health, fire->S6F11 on the host's wire,
alarm/clear->S5F1 with correct set bit, the full command loop (host S2F41 ->
HCACK=4 -> @eq.on handler -> completion event back at the host), operator
offline. Conversion layer unit-tested standalone; both wired into
tools/run_interop.sh as the pyclient step.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
13 lines
471 B
Python
13 lines
471 B
Python
"""secsgem_client — drive a SECS/GEM equipment daemon from plain Python.
|
|
|
|
The secs_gemd daemon speaks SEMI (HSMS, GEM state machines, SECS-II) to the
|
|
fab host; this client speaks plain Python to the daemon. You never touch a
|
|
stream/function, a format code, or a numeric id — just the names from your
|
|
equipment.yaml.
|
|
"""
|
|
|
|
from ._client import Command, Equipment, Health, SecsGemError
|
|
|
|
__all__ = ["Equipment", "Command", "Health", "SecsGemError"]
|
|
__version__ = "0.1.0"
|