MobileCollect EVO + Mitutoyo U-WAVE

SVEND should integrate with the MobileCollect receiver rather than implement the Mitutoyo wireless protocol. MicroRidge documents compatibility with U-WAVE-T, U-WAVE-TM, and U-WAVE-TC transmitters. The base receives the radio measurement and presents it to the computer as keyboard input or through a USB virtual serial port.

This preserves the installed transmitter and cable investment while giving SVEND a manufacturer-supported host interface. Native MobileCollect transmitters may share the same receiver, but this document is intentionally limited to the U-WAVE path.

The SVEND Gage R&R bench already accepts the standard keyboard-wedge behavior: the receiver types a numeric value into the highlighted row and sends Enter. SVEND advances to the next row in the randomized run order, returns to skipped rows, rejects non-numeric input, and records submitted readings as an append-only history.

The proposed production path is a small local SVEND collector on the inspection PC. It reads the EVO virtual COM port, keeps a durable queue during network interruptions, and forwards authenticated measurement events to the correct organization and active study.

The collector would preserve the original frame, normalize its fields, and prevent retry duplicates. The server rather than the collector would resolve the expected part, appraiser, trial, and randomized row. Initial pilots should require the operator to accept each pending reading before it joins the study record.

A U-WAVE radio measurement packet contains its measurement, Group ID, and channel. It does not contain the transmitter's full ten-character Device ID. During individual-channel pairing, the MobileCollect base receives and remembers that ID and exposes its last six characters as the Module ID. Global pairing supplies the measurement without an identifier.

The documented EVO API supports fifteen individual channels, A through O, plus the global channel. Its All Data output can include measurement, channel, Module ID, Base ID, label, units, radio-health fields, event number, and read gap. Because the native U-WAVE packet contains less information than a MobileCollect transmitter packet, the pilot must establish which fields are actually populated for each U-WAVE transmitter family.

Before SVEND labels identified serial capture available, a real receiver and each available U-WAVE transmitter family must produce parser fixtures. The pilot must verify exact delimiters, signs, decimal precision, units, Module ID behavior, duplicate handling, disconnect/reconnect, queued delivery, and the fields left blank by U-WAVE-originated packets.

Acceptance requires 1,000 consecutive transmissions without unexplained loss or duplication and an identical Gage R&R result when the captured readings are compared with the same values entered manually.