Skip to content

Latest commit

 

History

History
67 lines (52 loc) · 3.55 KB

File metadata and controls

67 lines (52 loc) · 3.55 KB

Protocol Reference Index

Each supported meter family has its own wire protocol documented under docs/research/<family>/reverse-engineered-protocol.md. Those per-family documents are the authoritative reference for transport, framing, mode tables, flag bytes, command encoding, and hardware-verified behavior.

UNI-T

Voltcraft

Shared infrastructure

Families that use a 0xAB 0xCD header share a framing skeleton but differ in the details: UT61+/UT161, UT8803, VC880, and VC890 use a 1-byte length plus a 16-bit big-endian sum checksum, while UT171 and UT181A use a 2-byte little-endian length (counting payload + checksum) plus a 16-bit little-endian sum. UT8802 uses a 0xAC single-byte header with BCD frames and no checksum, and UT803/UT804 carry proprietary structured data inside FS9721-style framing — see the per-family docs for the exact wire format.

The UART byte stream is transport-agnostic within each family. Three HID bridge chips appear across the supported devices:

  • CP2110 (Silicon Labs) — bidirectional HID-to-UART, used by UT61+/UT161 and the UCI bench DMMs (UT8802/UT8803).
  • CH9329 (WCH) — bidirectional, driverless, found on newer UT-D09 cables for UT181A / UT171 / UT243, and reported on a UT61B+.
  • CH9325 (QinHeng / HE2325U) — receive-only HID bridge used by UT803/UT804 and some UT-D04 cables. Can stream meter data to the host but cannot send commands back.

See each per-family doc for the HID report layout and any chip-specific initialization sequence.

For how the library works out which family is on the wire from the bytes it sends, see detection-design.md.

For verification status and the outstanding hardware-testing backlog, see verification-backlog.md.

External reference implementations

These third-party implementations are useful cross-references when extending the UT61E+ family support, but are not consumed by the clean-room research docs under research/ — cite them in review discussion, not in the spec files.