AnyDDL · Android probe feasibility test

Loading…

Status: idle

Test options

HDLC client address HDLC server address Reply timeout (ms)

Also test IEC 62056-21 mode-C (this is the 9600 → 300 baud switch test) Repeat the SNRM five times to check for wedging (only if a meter answers)

Send arbitrary hex to the meter after a test has opened the device. Read-only frames only — this page never writes to a meter register.

—

Run a test to enumerate the probe.

—

L0 — which browser APIs exist. Android Chrome has WebUSB but no Web Serial.
L1 — the frames this page builds are compared to bytes captured from the desktop engine, so a hardware failure cannot be confused with a bad frame.
L2 — the phone enumerated the probe over USB OTG and its bridge chip was recognised.
L3 — Chrome claimed the USB interface. A failure here usually means an Android kernel driver already owns it.
L4 — the bridge chip accepted 9600 8N1, then switched to 300 7E1 mid-session.
L5 — bytes actually left the OUT endpoint.
L6 — a meter answered. Needs the probe coupled to a live meter; skipped otherwise.

L0–L5 pass means Android can drive the probe. L6 pass means the whole chain works end to end.