How this works
Each virtual ATE drops raw log files into a converter's watch folder at a configurable tempo, mimicking a real test station. The client's converter pipeline then processes the files exactly as if a real ATE had produced them — validate, convert, queue, submit — so this exercises the full pipeline (including yield monitor input). Nothing is written to the WATS server directly.
Target folders are discovered from …. Add
converters in the Configurator first; refresh this window with Reload config
after changes.
ATEs
No ATEs yet — click Add ATE.
Status
Idle
Not running.
Available converter targets
Loading…
Converter Playground — coming in Phase 2.
Pending Queue Inspector — coming in Phase 3.
API Fault Injector — coming in Phase 3.
Direct Submit — coming in Phase 4.
Log Stream — coming in Phase 4.