Update Monitoring Overview
Update Monitoring Overview
There are three methods by which the Enabler on the MX3X can communicate with the Mobile Device Server running on the
host machine.
l Wired via a serial cable between the Mobile Device Server PC and the MX3X.
l Wired via a USB connection, using ActiveSync, between the Mobile Device Server PC and the MX3X.
l Wirelessly via the MX3X 2.4GHz radio and an access point
After installing the Enabler on the MX3X the Enabler searches for a Mobile Device Server, first by polling all available serial
ports and then over the wireless network.
The Enabler running on the MX3X will attempt to access COM1, COM2, and COM3. “Agent not found” will be reported if the
Mobile Device Server is not located or a serial port is not present or available (COM port settings can be verified using the LXE
scanner applet in the Control Panel on the MX3X).
Note: Refer to the MX3X reference guide for communication details as there may be differences in capabilities. For
example, LXE recommends serial communication with an MX3X be performed using the serial port on the MX3X endcap
rather than using a docking cradle serial port.
The wireless connection is made using the default wireless [radio] interface on the mobile device therefore the MX3X must be
actively communicating with the network for this method to succeed.
If a Mobile Device Server is found, the Enabler automatically attempts to apply all wireless and network settings from the
active profile. The Enabler also automatically downloads and processes all available packages.
If the Enabler does not automatically detect the Mobile Device Server, the IP address of the Mobile Device Server can be
entered on the Connect tab of the Enabler setup. Please see Enabler Configuration for details.
E-EQ-MX3XRG-W-ARC [ 153 ] MX3X Reference Guide
