Designed & Made in the USA Since 1983
The MC-M3E-UNIV-24 is the dedicated connection cable for using OpenGage Mode on the Mini Mobile Module M3E. It connects any device that outputs data via UART at 9600-N-8-1 — Arduino, ESP32, custom sensors, torque gauges, environmental sensors, and end-of-line test fixtures — to the M3E, enabling wireless transmission over the RM2.4 industrial wireless network without custom RF hardware.
A 4-conductor cable with color-coded wires for UART data, Read Button trigger, Read Request handshake, and ground. Readings can be initiated by pressing the Read Button on the M3E or by the host device pulling the Read Button line low — supporting fully automated, software-triggered data collection workflows.
Note: Requires the Mini Mobile Module M3-EVO and a MobileCollect Base Receiver. OpenGage Mode must be enabled on the M3E via the Xpress Setup Program or Extended Setup Program before use.
Transmitter Family – Mini Mobile Module EVO (M3E)
Connector Variant – M3E (2×4, 8-Pin)
Standard Cable Length – 24″
Communication Protocol – UART 9600-N-8-1
Max Input Voltage – 3.35V
Conductors – 4 (Read Button, Read Request, UART Data, Ground)
3-Wire Configuration – Supported (Read Button wire optional)
SKU – MC-M3E-UNIV-24
Required Hardware – Mini Mobile Module EVO (M3E) and MobileCollect Base
Connector IP Rating – N/A
Gage Brand – Mitutoyo
$115.00
The MC-M3E-UNIV-24 is the interface cable between your UART host device and the Mini Mobile Module M3E. It plugs into the M3E’s internal connector port and provides four signal lines to your host device: UART data input, a Read Button trigger output, a Read Request handshake input, and ground.
When connected and OpenGage Mode is enabled on the M3E, the system works as follows: a read event is initiated either by pressing the Read Button on the M3E or by the host device pulling the Read Button line low. The M3E pulls the Read Request line low to signal the host device that it is ready to receive. The host device then sends its data packet over UART within 500 milliseconds of the Read Request signal. The M3E receives the packet and transmits it wirelessly over RM2.4 to the paired MobileCollect Base Receiver — and from there into any PC application or SPC software.
The result: wireless industrial data transmission from any 3V UART device, with no custom RF hardware required.
Any device that can output data via UART at 9600-N-8-1 with 3V logic levels is a candidate:
If your device outputs 3V UART data at 9600-N-8-1, it can transmit wirelessly over the RM2.4 industrial network using the MC-M3E-UNIV-24 and M3E.
The MC-M3E-UNIV-24 is a 4-conductor cable with the following wire assignments:
Wire Color | Signal | Direction | Description |
|---|---|---|---|
Green | Read Button | Output from M3E | Pull low (25–50 ms) to trigger a read event from the host device |
White | Read Request | Input to host device | M3E pulls low when ready to receive data; host sends data within 500 ms |
Black | UART Rx / Data | Input to M3E | Connect to TX on host device; UART 9600-N-8-1 |
Blue | Ground | Common | Shared ground between host device and M3E |
The M3E accepts data packets from the host device with the following structure:
{CR} — Hex \x0d — required to terminate every packetOptional unit suffix: To include units with your measurement, insert the following two-byte sequence immediately before the End-of-Packet byte, followed by the unit character:
Unit Character | Unit Displayed |
|---|---|
I | inch |
M | mm |
N | meter |
F | foot |
D | degree |
G | gram |
L | pound |
H | kilogram |
Unit prefix bytes: \xff\xe0 (Hex 255, 224)
Examples:
HELLO WORLD\x0d → displays as: HELLO WORLD1.23456\xff\xe0D\x0d → displays as: 1.23456 deg9.87654321\xff\xe0I\x0d → displays as: 9.87654321 inchTwo methods are available to initiate a read event:
1. Host Device Triggered (4-wire configuration) The host device pulls the Green (Read Button) line low for 25–50 milliseconds. The M3E pulls the White (Read Request) line low to signal readiness. The host device sends the data packet via UART within 500 milliseconds of the Read Request signal going low. This enables fully automated, software-triggered data collection without operator input.
2. Manual Read Button (4-wire or 3-wire configuration) The operator presses the Read Button on the M3E. The M3E pulls the Read Request line low, the host device sends its data packet, and the M3E transmits it wirelessly. No host-side triggering logic required.
The MC-M3E-UNIV-24 can be used in a 3-wire configuration by leaving the Green (Read Button) wire disconnected. In this configuration, all reads must be initiated by pressing the Read Button on the M3E — host-side triggering is not available.
Note: switching between 4-wire and 3-wire configurations requires powering down both the M3E and the UART host device before changing the wiring. In the 3-wire configuration, a failed read will produce a Warm Start LED sequence on the M3E rather than the standard “Could not get gage reading” 2-blink code.
If the M3E does not receive a valid data packet from the host device, it will display one of two LED codes depending on the state of the Read Button line:
Read Button line held HIGH by host device: The M3E displays the standard failed read code — 2 red blinks from the Gage Read LED. Most commonly caused by the absence of data from the host device or a missing End-of-Packet byte.
Read Button line LOW: The M3E assumes the host device has powered down or been disconnected and performs a Warm Start. Warm Start LED sequence: both green LEDs blink once → both red LEDs blink once → 4 red/green railroad blinks.
The MC-M3E-UNIV-24 requires the M3E to be configured in UART 9600-N-8-1 mode before use. This mode is set via the MobileCollect Xpress Setup Program or Extended Setup Program and is the setup software designation for OpenGage Mode. Ensure both setup programs are updated to the latest version before configuring. For full wiring diagrams, data packet timing, and code examples, see the OpenGage Mode Feature Guide.
The M3E must also be paired with a MobileCollect Base Receiver before use. Pairing can be completed via Pair-on-the-Fly, Xpress Setup, or Extended Setup Program.
The MC-M3E-UNIV-24 and M3E connect your UART device to the same RM2.4 industrial wireless network used by the entire MobileCollect product line — the same 32-bit encrypted, 140-foot range, IEEE 802.15.4-based protocol that has been deployed on production floors across automotive, aerospace, medical device, and precision manufacturing for decades. No custom RF design. No proprietary data logger. No Bluetooth interference issues. For a detailed look at why RM2.4 outperforms Bluetooth in manufacturing environments, see Why Bluetooth Fails in Manufacturing.
The MC-M3E-UNIV-24 and an M3E running OpenGage Mode can operate alongside any other MobileCollect transmitter on the same system — standard digital gage M3Es, Command Mobile Modules, RS-232 Mobile Modules, and Digital Remotes all pair to the same Base Receiver simultaneously. A single workstation can collect data from a Mitutoyo caliper, a Mahr micrometer, and a custom Arduino sensor fixture all at once, routing every reading into the same PC application or SPC software. No additional hardware or network configuration is required to run mixed transmitter types on the same RM2.4 system.
Can I use OpenGage Mode alongside my existing MobileCollect gages on the same system?
— Yes. An M3E running OpenGage Mode with the MC-M3E-UNIV-24 is fully compatible with all other MobileCollect transmitters on the same RM2.4 network. Standard digital gage transmitters, Command Mobile Modules, RS-232 Mobile Modules, and Digital Remotes all pair to the same Base Receiver simultaneously. Your UART device and your existing gages can feed data into the same PC application or SPC software without any additional hardware or configuration.
What devices can I connect with the MC-M3E-UNIV-24?
— Any device that outputs data via UART at 9600-N-8-1 with 3V logic levels. This includes Arduino, ESP32, and other microcontroller platforms, custom test fixtures, torque gauges, environmental sensors, load cells, barcode readers, and any MCU-based measurement device with a 3V UART output. Maximum input voltage is 3.35V. For full wiring and integration details, see the OpenGage Mode Feature Guide.
Does OpenGage Mode need to be enabled separately?
— Yes. OpenGage Mode must be configured on the M3E using the Xpress Setup Program or Extended Setup Program before the MC-M3E-UNIV-24 will function. Both programs should be updated to the latest version prior to setup. See the OpenGage Mode Feature Guide for complete implementation details including wiring, timing, and data packet format.
Can the host device trigger readings automatically without someone pressing the Read Button?
— Yes. In the standard 4-wire configuration, the host device can pull the Green (Read Button) line low for 25–50 milliseconds to initiate a read event. This enables fully automated, software-triggered data capture without operator input.
What is the 3-wire configuration?
— The Read Button (Green) wire can be left disconnected, reducing the cable to 3 active conductors. In this configuration, all reads must be initiated by pressing the Read Button on the M3E. Switching between 4-wire and 3-wire configurations requires powering down both devices first.
What is the maximum data packet size?
— 41 bytes total: 40 bytes of ASCII data plus a required Carriage Return End-of-Packet byte (\x0d). Packets shorter than 40 bytes are supported — just ensure the End-of-Packet byte is included.
Can I include units with my measurement data?
— Yes. Insert the two-byte sequence \xff\xe0 followed by a unit character immediately before the End-of-Packet byte. Supported units: inch (I), mm (M), meter (N), foot (F), degree (D), gram (G), pound (L), kilogram (H).
Is the MC-M3E-UNIV-24 compatible with the original Mini Mobile Module M3?
— No. The MC-M3E-UNIV-24 uses the new 8-pin connector interface and is designed exclusively for the Mini Mobile Module M3E. OpenGage Mode is an M3E-only feature and is not available on the original M3.
Is the M3E still compatible with my existing standard gage connectors when using this cable?
— The MC-M3E-UNIV-24 replaces the internal gage connector in the M3E for OpenGage Mode use. When you want to return to standard digital gage operation, swap back to the appropriate M3 gage connector. All existing 6-pin MC-M3-xxx connectors remain fully compatible with the M3E.
What Base Receiver do I need?
— OpenGage Mode requires an EVO series Base Receiver.
MC-M3E-UNIV-24 Specs | |
|---|---|
Transmitter Family | Mini Mobile Module EVO (M3E) |
Connector Variant | M3E (2×4, 8-Pin) |
Standard Cable Length | 24 inches |
SKU | MC-M3E-UNIV-24 |
Conductors | 4 (Read Button, Read Request, UART Data, Ground) |
Transmitter Compatibility | Mini Mobile Module M3-EVO only |
Communication Protocol | UART 9600-N-8-1 |
Baud Rate | 9600 |
Data Bits | 8 |
Parity | None |
Stop Bits | 1 |
Max Input Voltage | 3.35V |
High Voltage Threshold | 2.1V |
Low Voltage Threshold | 0.9V |
Read Trigger | Host device (pull Read Button line low, 25–50 ms) or M3-EVO Read Button |
Read Request Window | Host must send data within 500 ms of Read Request low signal |
Min Gap Between Packets | 150 ms |
Max Data Packet Size | 41 bytes (40 data + 1 CR end-of-packet) |
3-Wire Configuration | Supported (Read Button wire optional) |
Required Hardware | Mini Mobile Module EVO (M3E) & MobileCollect EVO Base Receiver |
Wire Colors | Green = Read Button, White = Read Request, Black = UART Data, Blue = Ground |
Country of Origin | Designed & Made in the USA |