Pretends to be a TLS-350 console on a serial port, so the TLS-350 Explorer can be tested without real hardware. Deliberately supports misbehaving in specific, reproducible ways — that is the point of it.
version · internal test instrument, not for customer use
This page needs to be on the other end of a serial link from the TLS-350 Explorer. Two ways to do that:
| Virtual pair (no hardware) | Install com0com
on Windows. It creates a linked pair such as COM10 ↔ COM11.
Open one end here and the other end in the check page. |
|---|---|
| Two adapters | Two USB-to-RS232 adapters joined by a null-modem cable (TX↔RX crossed). Closer to the real thing, and it exercises the actual UART. |
Open this page and the check page in separate browser windows. A serial port can only be held by one page at a time.
| # | Product | Volume | TC Volume | Ullage | Height | Water | Temp | Delivery |
|---|
| # | Status |
|---|
| Category | Type | Device |
|---|
With no alarms listed, i101 reports all functions normal.
This is what the simulator is for. Pick a fault, choose which command it applies to and how often, then watch whether the check page detects it.
Walks through every fault in turn so the client can be left running in live monitoring mode and watched. With "behave normally between faults" ticked, each fault is followed by a clean interval — which is what an intermittent problem actually looks like.
Paste bytes captured from the real OPW console. Accepts
hex (01 69 32 30 31) or plain text (<SOH>i20100…).
Sent verbatim — no framing or checksum is added, so this reproduces the console exactly.
This is how you turn a site capture into a repeatable test.
Tests whether the client notices bytes arriving out of turn.
Download this alongside the explorer's report when raising a bug. Having both ends of the same conversation makes a disagreement obvious immediately, and both tools share a version number so a matching pair is easy to spot.