The existing toolholder sequence, using live RevPi I/O.
Source declaration only; installed firmware UNKNOWN.
No active validation
Start opens evidence capture. It does not change Out1 or flash firmware. Use recipe 2 for EMC mode cycling.
Release can cancel the workflow and re-tare the current load. Guide navigation never changes output.
Stop has not been requested.
Run limit 10 min · high limit 120 s · link timeout 30 s. Reload loses ownership; closing this page is not a guaranteed stop.
Preview: choose a stage. Start validation to record checks.
No observations recorded
Selecting a step is navigation only. Skipped steps remain untested.
Reseat → reset high → release low. Requires a recorded correct-tool/red-latch observation; no output write on entry.
Missing steps stay untested. Capture gaps stay indeterminate. No whole-device PASS is computed.
Observed status UNKNOWN
Requested output: UNKNOWN — no request recorded in this controller instance.
Checking validation connection…
Only an explicitly started browser session sends connection heartbeats (every 5 seconds). A 30-second timeout or lost readback ends the run and requests Out1=0. Overall run limit: 10 minutes; maintained high: 120 seconds. Heartbeats never extend those limits. Reload does not resume ownership. Process/OS failure can leave output high.
Sequential process-image reads. Acquisition intervals include storage/runtime jitter. No guaranteed minimum detectable pulse width. Network polling does not perform acquisition. Two bits do not prove terminal voltage, tool identity, LEDs, sensor health or a whole-device PASS.
| Controller UTC | Out1 | In1 | Quality / gap | Interval (s) |
|---|
The default is reviewed Production 1.02 / 1.0.2-rc.1. Choose the exact reviewed source declaration; this does not establish what was programmed. Installed firmware remains UNKNOWN. Active and saved runs retain their recorded source contract. Demo is not PLC-driven; EMC uses recipe 2. Source loop counts and LED timing are not physically qualified.