Antx Messenger-W User manual

Messenger-W
User’s Guide
Version 1.1.0
July 26, 2018
Antx
3005 Glacier Pass Lane
Cedar Park, TX 78613
P: 877-686-2689
F: 512-255-8306
www.antx.com

2
Table of Contents
1 Description .............................................................................................................................5
1.1 Capabilities..................................................................................................... 5
1.2 Monitoring ..................................................................................................... 5
1.3 Host Server Communications......................................................................... 5
2 Installation and Setup .............................................................................................................8
2.1 Installation Steps ............................................................................................ 8
2.2 Unpacking the Equipment .............................................................................. 8
2.3 Mounting the Equipment ................................................................................ 8
2.4 Mounting the Antenna.................................................................................... 9
2.5 DIP Switch/Jumper Settings .......................................................................... 9
2.6 Cellular Setup ............................................................................................... 10
3 LED States ........................................................................................................................... 11
4 Channels ............................................................................................................................... 14
4.1 Defined Channels ......................................................................................... 14
4.2 Channel Data ................................................................................................ 15
5 SMS Text Commands .......................................................................................................... 17
5.1 Command Syntax ......................................................................................... 17
Table of Figures
Figure 1: Deutsch EEC Thermoplastic Enclosure Dimensions ....................................... 9

3
Copyright and Trademark Information
All Pages Copyright © 2018 Antx, All Rights Reserved.
U.S. Government Users Restricted Rights. Use, duplication, or disclosure by the Government is
subject to restrictions as set forth in applicable laws and regulations. Use of the materials by the
Government constitutes acknowledgment of Antx' proprietary rights in them. This manual may
contain other proprietary notices and copyright information that should be observed.
Information in this document is subject to change without notice. The software described in this
document is furnished under a license agreement or nondisclosure agreement. The software may
be used or copied only in accordance with the terms of those agreements. No part of this
publication may be reproduced, stored in a retrieval system, or transmitted in any form or any
means electronic or mechanical, including photocopying and recording for any purpose other
than the purchaser’s personal use without the written permission of Antx.

4
Introduction
This User’s Manual describes installation and setup of the Antx Messenger product.
The Messenger is a complete monitoring, alarm notification, and telemetry platform. It
supports monitoring of data values from on-board physical IO.
Features
The hardware feature set of this platform includes:
 Battery backed on power fail
 Power fail detection
 3 Digital Inputs (user configurable to accept a voltage or ground input)
 1 Digital Outputs (transistor closures to ground)
 1 Analog Input (10-bit, user configurable for V or ma input)
 3G or LTE cellular modem and antenna

5
1 Description
1.1 Capabilities
The Messenger is a highly configurable platform for remote monitoring and control
applications. Some of the capabilities are listed below.
 local computations from monitored conditions
 time stamping of monitored data and events
 battery backed historical data/event buffers
 automatic monitoring of max/min for analog values
 event and data logging
 telemetry of monitored conditions to host server-based applications via
cellular
 OTA programming and diagnostics
 SMS messages sent on monitored conditions
 parameter setting via SMS messages
 rate of change alarm/flow totalization on physical analog input channel
 pulse counter on all physical digital input channels
 high/low warning/alarm on all analog channels
 daily count and duration alarm on all physical digital input channels
1.2 Monitoring
All monitored values can be transmitted via cellular to a host server of the customer’s
choosing. Monitored values are transmitted based on time or notification events.
Notification events are based on rules set by the user and each event can generate an
immediate report. Telemetry includes cellular data connectivity to host server or SMS
messaging direct to user.
Monitored data values are mapped to fixed channels in the Messenger. A channel
defines a set of attributes for the monitored data for doing calculations, alarm detection,
data formatting, and reporting.
For example, the physical analog input is fixed to channel 62. For channel 62, the user
can set high/low limits to generate notifications to a host server or directly to the user
via SMS.
Table 4.1 provides a description of all the pre-defined channel numbers.
1.3 Host Server Communications
The Messenger utilizes a proprietary protocol to send notifications and to receive OTA
commands from a host server. Each notification typically consists of location,
date/time, an event code, and associated data. An event code provides a unique

6
identifier to indicate the reason that a notification is being sent – e.g. normal scheduled
update or an alarm detection event. A description of the protocol, format of messages,
and definition of event codes is available on request. Reference protocol document
“M09-PRTCLxxx”.
Some of the conditions on which notifications can be sent to the host server are listed
below:
 Any monitored value exceeding a pre-defined or user-defined limit
 A digital input changing state (on/off)
 A digital output changing state
 An analog input transitioning into a warning or alarm region
 A scheduled update
 System faults
 SMS text commands from a user or host server
 Power on or reset
1.3.1 Event Codes
Every message sent by the Messenger to a host-based server application is triggered by
an event. The event generates a message and the message contains an Event Code. The
Event Code uniquely identifies to the server the reason the message is being sent. Some
of the messages generated contain data, others serve as just notification that an event
has occurred.
1.3.2 Positive Acknowledgement
The Messenger can be configured to require a message acknowledgement from the host
server or to send once and forget. Message acknowledgement provides a verifiable
mechanism that a message was delivered, even during poor network conditions.
This parameter setting can be found in the CELL configuration.
1.3.3 Store and Forward Data Queue
There are several scenarios where a message may not be deliverable – network down,
host server down, poor connectivity to name a few. In the event that a message cannot
be delivered, it is stored in memory and is continually re-sent until properly
acknowledged. This store and forward memory is non-volatile and remains intact
during power off.
1.3.4 Real-Time Clock (RTC)
The RTC is used to time stamp data records and events. All messages sent to the host
server contain a time stamp to provide a chronology of data/events to the end user. The
RTC is battery backed to provide time keeping during power off. If the RTC is

7
configured to be automatically set, the Messenger will set time after every power on
and perform a time check every midnight.
The RTC can be set in one of the following ways:
Method
Description
Automatic
via Cell
This is the default setting. The
Messenger will set the RTC from an
internet NIST time server
.
Manually Set the time via the Debug port
through the Maintenance menu.
OTA/SMS Set from an OTA config command or
an SMS config command.
Some parameters in the OPTIONS and CELL configurations are used to define how the
RTC is set.
1.3.5 Specifications
Power input:
8-32 vdc
50 mA @ 24vdc
reverse polarity protection
overvoltage protection
externally fused
Digital outputs:
transistor switch to ground (current sink)
2A @ 24vdc
current limited
overvoltage protection
Digital inputs:
two modes of operation (user selectable), voltage input or ground input
current limited
overvoltage protection
Analog input:
10-bit ADC
Accuracy +/- 2% FS
user selectable input range: 0-1v, 0-5v, 0-10v, 0-20mA

8
2 Installation and Setup
This section provides information on installing the Messenger and confirming its initial
operation.
It is recommended to read the entire chapter before starting the installation.
2.1 Installation Steps
Installation consists of the following steps:
1. Unpack the Equipment.
2. Mount the Equipment.
The Messenger should be mounted in a vertical position to try and minimize
the chance of water entering through the antenna connection. The antenna wire
should have a service loop just below the antenna connector.
3. Connect Main Power.
4. Connect field signals (digital, analog, Modbus) to the appropriate wire.
2.2 Unpacking the Equipment
The Messenger is shipped with the following:
 The Messenger electronics in a Deutsch thermoplastic enclosure or a board
only product
 A Cellular antenna (magnetic mount or bulkhead)
 User’s Guide
 Optionally, a cable harness
2.3 Mounting the Equipment
The Messenger is available in an automotive grade weather resistant enclosure.
NOTE: Mount the Messenger vertically and provide a service loop for the antenna
cable to prevent water intrusion.

9
2.3.1 EEC Thermoplastic Enclosure
Figure 1: Deutsch EEC Thermoplastic Enclosure Dimensions
2.4 Mounting the Antenna
The antenna shipped with the Messenger is a cellular hockey puck style. The antenna
can be ordered with a magnetic or a screw mount base.
In general, the antenna should be mounted with an unobstructed view of the sky. If the
antenna is mounted outside and may be subject to lightning, a surge arrestor can be
inserted between the antenna and the Messenger. If the antenna is mounted inside, it
should be located near a window.
NOTE: Service loops should be provided for the antenna cabling, near the antenna
connection to minimize water ingress through the connection.
2.5 DIP Switch/Jumper Settings
The Messenger uses on-board DIP switches and jumpers to configure application
specific IO and set operational modes. DIP switches 3, 4, 5, and jumper J21 are used to
select application specific IO. DIP Switch 2 is used to set operational modes. See
Figure 3 for DIP switch locations. See Figure 4 for DIP switch IO selection settings.

10
2.6 Cellular Setup
The Messenger supports two cellular technologies, HSPA (3G) and LTE. Both of these
radio options require a wireless account with a cellular provider such as AT&T, T-
Mobile, Sprint, Verizon, Vodafone, etc.
Table 2.4: Cellular Modem Requirements
Radio Provider
Options
Account
Type
Static IP SIM APN Username
Password
Host
Server
IP/Port
HSPA
(3G)
AT&T
Kore
Data+
SMS
required required required optional required
LTE Sprint
Verizon
Data+
SMS
required required not
required
not
required
required
LTE AT&T Data+
SMS
required required required not
required
required

11
3 LED States
There are 8 LEDs used to indicate various system conditions (LED locations). Specific
information is conveyed to the user via LED blink patterns. Blinking of LEDs can be
disabled via a configuration setting (OPTIONS Configuration). On power-up, an LED
test is performed by blinking all LEDs every second for 3 seconds. Following the LED
test, the LEDs blink based on the following conditions:
 LED 1 (GRN) - System
State
Rate
Definition
Blink 1 blink every 5
seconds
Sleep Mode
Blink
1 bli
nk every second
CPU Run
-
Normal
Blink 5 blinks every
second
Boot Loader Mode
(all other LEDs off)
On or Off
Solid
System
Failure
 LED 2 (RED) - Cell Registration
State
Rate
Definition
Blink Rapid blink, then off Ok - Rx/Tx Activity w/CELL
Modem
Blink 1 blink every second Not Registered
Check APN
Verify valid cellular account
Off
Solid
Ok
-
Registered
 LED 3 (RED) - Cell Status
State
Rate
Definition
Blink 10 blinks every
second
No SIM card or communications
failure with modem
On
Solid
Not Ready/Fau
lt
Blink
1 blink every second
Error
Off
Solid
Ok

12
 LED 4 (RED) - CAN
State
Rate
Definition
On Solid Fault, no engine bus activity
detected
Blink 2 blinks every
second
OBD traffic detected, but no
response to
data
queries
Blink 1 blink every second Engine bus not selected, check DIP
Switch 2
Off Solid No Faults, engine bus activity
detected
 LED 5 (RED) - GPS
State
Rate
Definition
Blink
1
blink every second
No Fix
Off
Solid
Fix
 LED 6 (RED) - Modbus
State
Rate
Def
inition
Blink
Rapid (burst)
Ok
-
Rx/Tx Activity
o
n Port 2 or 3
On
Solid
Fault
(
comm.
timeout
error)
Off
Solid
Ok
-
No Faults
 LED 7 (RED) - USR1
State
Rate
Definition
Blink 1 blink every second Lithium Coin Cell battery is low or
RTC has stopped
On Solid If DIN1, DIN2, DIN3, or DIN4 are
configured as pulse counter inputs,
this LED will light when any input
is
activated
, off when
all inputs idle
Off
Solid
No Faults

13
 LED 8 (RED) – CELL Signal Strength
(Enabled from OPTIONS Setup – default is Enabled)
Rate
Definition
OFF
Not registered or n
ot detectable
1
blink
, 1.2
sec
pause
signal strength <6
,
weak
2
blinks
, 1.
2 sec
pause
signal strength <
=
12
3 blinks, 1.2
sec
pause
signal strength <
=
18
4
blinks
, 1.2
sec
pause
signal strength <
=24
5
blinks
, 1.
2 sec pause
signal strength >24
,
strong

14
4 Channels
The Messenger maps all monitored conditions into channels. Each channel has data
storage and configuration parameters. Data storage holds current value, max/min
values, and other run time data values. Configuration consists of user settable
parameters that define rules on how the data values are to be processed (Channel
Configuration).
Every channel in the Messenger is referenced by a fixed channel number, e.g. analog
input channels is always channel 62. There is a set of pre-defined channels (numbers 1-
300) and a set of Modbus channels (numbers 301-380). The Modbus channels are user
configurable for reading/writing digital or analog values from a Modbus RTU slave
device.
4.1 Defined Channels
The following channels are pre-defined in the Messenger:
Table 4.1: Pre-Defined Channels
Channel
Number
Channel
Name
Type Description
Start Digital Channels (data values are ‘0’ or ‘1’)
1 Cell Digital
(System)
Status of cellular modem operation
 1=fault

0=normal
2 Comm Digital
(System)
Status of any serial port used for
communications with external device
(MODBUS Master, Slave, or proprietary)
 1=fault

0=normal
4 User DIN1
(used for
power fail
detection)
Digital If SWX4-1 closed:
 0=input open
 1=input voltage < 1vdc
If SWX4-1 open:
 1=input open

0=input voltage > 3vdc
21 User DIN2 Digital If SWX4-2 closed:
 0=input open
 1=input voltage < 1vdc
If SWX4-2 open:
 1=input open

0=input voltage > 3vdc
5 User DIN3 Digital If SWX4-3 closed:

0=
input
open

15
Channel
Number
Channel
Name
Type Description
 1=input voltage < 1vdc
If SWX4-3 open:
 1=input open

0=input voltage > 3vdc
6 User DIN4 Digital If SWX4-4 closed:
 0=input open
 1=input voltage < 1vdc
If SWX4-4 open:
 1=input open

0=input voltage > 3vdc
30 User DOUT1 Digital state of digital output 1
 0=not energized

1=energized
Start Analog Channels
(data values are floating point, precision is user configurable)
62 User Analog Analog on-board analog input, 10-bit ADC
can be configured for 0-1, 0-5, 0-10vdc,
or 0
-
20mA
154 Daily Flow
Volume
Derived Accumulated flow volume for the day
(
flow rate from ADC input
)
155 Running
Flow
Volume
Derived Accumulated flow volume since last volume
reset (
flow rate from ADC input
)
4.2 Channel Data
All values read from physical IO or from a Modbus slave device are continually
updated and tested as defined by the configuration parameters. For each channel, based
on its type (analog or digital), there is a basic set of data collected. For purposes of
discussion, the term “not normal” is used to indicate an analog value that has violated a
limit threshold or a digital value that does not match its configured ‘normal’ state.
Basic Data Set -
For analog channels:
 Current value
 Max/min values (daily and trip)
For digital channels:
 Current value
 Previous value
 Count of transitions to not normal (counts)
 Accumulated time in not normal state (duration)

16
There are a few channels that can be configured for special functions. All the physical
digital input channels can accept pulse inputs (e.g. from a flow meter) and the physical
analog input can be used to totalize volume when the input is flow rate. These channels
have an extended data set.
Extended Data Set -
For the analog channel:
 Daily total volume (available on separate channel, 154)
 Continuous running total volume (available on separate channel, 155)
For the digital channels:
 Flow rate
 Daily total volume
 Continuous running total volume
The Messenger also maintains a set of daily data.
The daily data set is a separate set of current and max/min values that span the 24 hour
period from midnight to midnight, UTC time. At midnight, an end of day report is
generated from this data.
Because Modbus channel data is polled, Modbus digital channels do not maintain count
or duration values.

17
5 SMS Text Commands
The Messenger can receive and execute SMS commands to perform several functions.
The SMS command set includes:
 CONFIG – used to modify configuration parameters
 ACTION – on-demand action request
5.1 Command Syntax
The commands can be upper case, lower case, or combination.
 <CONFIG(x,<i,>y,zzzz)> - used to modify configuration parameters. See
Configuration for details on specific configuration types.
x = configuration line type code
<i,> = optional index value
y = parameter code
zzzz = parameter value
 <ACTION(x)> - request to execute action identified by action number.
x = action number
Table 5.1: Action Commands
A
ction
N
umber
Action Description
Response
1 Generate on-demand standard report to host
server
ack+
report
2
Send
status to sender
status
3
Force cell modem reset
ack
4
Clear all stored data records
ack
5
Send
Cell config to sender
cell
config
6
Force digital output 1 on
ack
7
Force digital output 1 off
ack
8 Generate on-demand end of day report to host
server
ack+
report
10
Return a subset of channel data values to sender
data values
13
Clear oldest data record
ack
26
Force exit of mini
-
ping mode
ack
28
Zero all non
-
volatile counter data
ack
30
Return SIM card info
SIM info
32
Clear ADC channel daily
flow
totals
ack
33
Clear ADC channel running
flow
totals
ack

18
Action Responses:
ack text:
v: r: c
status text:
VID(v)-CELL(i s)-REG(r g)-RSSI(#)-GPS(p)-JBUS(j m n)-DATAQ(d e f)-
OUTP(a b)-SWX(x)-MSGS(f c)-VER(v#.#.# date prot modem jbus)
VID
v = vehicle ID
CELL
i = init state
s = current state
REG
r = tower registration
g = data registration
RSSI
# = signal strength
GPS
p = 1 for fix, 0 for no fix
JBUS
j = J1939, J1708, OBD2
m
n
DATAQ
d = count in queue
e = deleted from queue
f = failed
OUTP
A
B
SWX
MSGS
f = failed
c = count
VER
prot = protocol (Antx, Rastrac, other)
modem = type of modem, jbus = type of bus

19
SIM info text:
VID(v)-MSISDN(s)-ICCID(g)-IMSI(u)-IMEI(p)
data text:
VID v-Running: s-52 RPM: r-x Hours: h- CoolTemp: x-Battery -OilPress -
Odometer o
generator control text:

20
3005 Glacier Pass Lane
Cedar Park, TX 78613
P: 512-255-2800
F: 512-255-8306
www.antx.com