Toolholder / Recipe 2 of 2

EMC two-mode test

Alternate modes A and B; monitor the real toolholder feedback.

Read-only on open · no automatic starts or stopsInstalled firmware: UNKNOWN · declaration, not detection

Live digital echo

UNKNOWN
Command / RevPi → PCB
UNKNOWNOut1 → PLC_IN · controllable command, measured readback
Toolholder
LED / sensor: not measured
Feedback / PCB → RevPi
UNKNOWNPLC_OUT → In1 · read-only feedback
Readback UNKNOWNWaiting for a fresh controller sample.
UNKNOWN — no sampleNo sample
AcquisitionNot recording
Output stimulusNot running
Observed cyclesUNKNOWN

Completed OBSERVED cycles: UNKNOWN

No evaluation available

A ↔ B recipe

Expected levels, not firmware detection

Mode A · low

Command Out1=0 → expected feedback In1=0

Source expects white LED.

Not observed

Mode B · high

Command Out1=1 → expected feedback In1=1

Source expects green LED.

Not observed

LED expectations require physical observation; the website measures digital levels only.

Start monitoring → declare the installed EMC firmware → choose A/B dwell and cycle count → start A/B cycling. Monitor stop and output stop remain separate.

Record feedback

Capture only. Starting or stopping the recorder does not change output or stop stimulus.

Evaluation settings and capture limits

Evaluation uses ±10% of the entered dwell and response 0 to the allowance (at most half the shorter dwell). These are configurable test settings, not lab criteria. Capture gaps/read duration over 0.2 s are indeterminate; live bits older than 0.5 s are UNKNOWN.

Capture ends at the chosen duration (maximum 24 h) or the sample ceiling (3,456,000, one full day at 25 ms), whichever comes first. The recorder database cap is 16 GiB. No old evidence is deleted. Storage failures are visible. Recording and stimulus health are separate; a storage fault also makes the authorized stimulus stop at its next scheduler check.

No monitor status yet

Alternate modes A ↔ B

Writes real Out1. Release can cancel a production workflow and re-tare the load. Verify EMC firmware and wiring before starting.

Stimulus budgets and termination

Levels must last 1–120 s. The total budget is chosen cycles × (A + B + 1 s scheduling allowance), capped at 24 h. A scheduler stall over 0.5 s or lost readback requests low and ends stimulus; there is no burst catch-up or reboot resumption. Validation and stimulus cannot own outputs together. Source is EMC echo only; no automatic firmware switching or programming pulses.

No stimulus status yet

Closing this page sends no stop. Controller budgets run independently; process/hardware failure can leave output high.

Events and capture gaps

No captured events

Counts are conservative observed lower bounds, not stimulus intentions. Missing capture is indeterminate, not a fault-free PASS. Test settings are not EMC qualification.

Saved monitor records

JSON includes record, samples, evaluation and events. CSV is raw samples only, not a verdict.

Source / Copy · Read-only history

Diagnostics, coverage and captured timeline

UNKNOWN

Two digital bits cannot prove ADC operation, LEDs, reset behavior, terminal voltage or sensor health. No whole-device PASS is computed. Opening or refreshing reads status only: no automatic resumption or heartbeats.

Observed coverage

Observed cycles come from captured edges and resolved responses, not stimulus intentions or elapsed time. Missing capture and timing uncertainty remain indeterminate. The evaluator processes 1,000-sample chunks; it never counts cycles across a chunk boundary. All raw samples remain saved.

Raw events and response/dwell evidence

Current evaluation and last 100 finalized events. Event time is UTC origin plus monotonic elapsed t. Earlier faults stay latched in the coverage summary. DIO timing and glitch capture are not qualified.

Captured timeline

Latest 200 supplied samples, oldest first. Sequential reads have capture limits; polling is not acquisition and cannot prove absence of short glitches.

UTC / timeOut1In1Quality / gap