1. Once the contract is attached, the DXM Controller must provision the service using OTASP (Over-the-Air Service
Provisioning).
2. Make sure the cellular module is plugged into the DXM Controller and has its antenna properly connected.
3. On the DXM Controller LCD display select menu: System and then Provision Cell.
4. Click Enter on the Provision Cell menu.
5. The next screen will ask if you want to provision the cellular device, click Enter.
6. It will take approximately 60 seconds and will indicate when it has completed.
7. The cellular modem is ready for use.
7.3.3 DXM Cellular VPN Setup
A software VPN tunnel can be created between a DXM Controller using a cellular modem to a host PC using a private IP or
static wireless cellular plan. The instructions below outline the DXM Controller set up required to become aware of the VPN
connection. The cellular plan provider will have separate instructions for setting up the VPN on the PC side.
1. Establish VPN tunnel on your computer. Instructions should be provided from your VPN provider.
2. From within the DXM Configuration Tool, go to Settings > Network > Cellular Firewall Settings..
3. Fill in the Firewall IP address and Firewall netmask provided by your VPN provider. For M2Mair this was
included in the Routes.cmd file. It opens the device to traffic from 172.16.1.[0-255].
4. Go to Settings > Cloud Services > Network Interface.
5. Select Cell from the drop-down list and select the Enable VPN checkbox.
6. With your VPN tunnel open, select Device > Connection Settings.
7. Select TCP/IP, enter your VPN IP address, check VPN, and click Connect.
7.4 Accessing the DXM Using SMS
The DXM Controller with a cellular modem can be remotely accessed using SMS messages. Simple text messages can:
•
Force a push to the cloud
•
Reboot the controller
•
Read/write local registers
The incoming firewall provides security; only defined phone numbers are permitted to access the controller. Use the DXM
Configuration Tool to configure the SMS commanding feature. This feature requires firmware version 3.51 or later.
SMS command messages sent from approved phone numbers to the DXM Controller cause the DXM to respond. See the
examples below for SMS responses. Responses may take 20 seconds or more, depending upon the network.
A DXM Controller requires a few minutes after powering up before it can accept SMS messages. Initial cellular connection
times vary based on the wireless network. A SMS message sent to the controller while a push session is active delays any
response or the SMS message may be dropped based on the length of the push session.
7.4.1 HTTP Push
Push triggers a http push to a webserver. The DXM Controller accepts the message, executes the action, and sends an
acknowledgment text message back to the user.
Example: Texting
push
forces defined local registers to be sent to a webserver
push
<send>
DXM Controller acknowledgment text message:
Register push requested
7.4.2 Reboot
Reboot triggers the DXM Controller to reboot. The processor reloads the XML configuration file and zeroes all local register
data. This does not affect the other components of the DXM Controller (ISM radio, I/O board, cellular modem). The DXM
Controller accepts the message, executes the action, and sends an acknowledgment text message back to the user.
Example: Texting
reboot
forces the processor to reboot.
reboot
<send>
DXM Controller acknowledgment text message:
rebooting…
7.4.3 Get Register
grN gets register number
N
(DXM Local Register) and sends a text with the value back to the user. The response text
message shows the value in floating point format regardless of register number.
Example: Text
gr1
to retrieve the value for register 1.
DXM100-Bx Wireless Controller Instruction Manual
www.bannerengineering.com - Tel: 763.544.3164
57
