Cattron Messenger BLE User manual

Messenger BLE
User’s Guide
Version 1.0.38
September 30, 2020

2
MessengerBLE
User Guide

3
MessengerBLE
User Guide
Table of Contents
1 Description .............................................................................................................................7
1.1 Capabilities..................................................................................................... 7
1.2 Monitoring ..................................................................................................... 7
1.3 Host Server Communications......................................................................... 7
2 Installation and Setup ........................................................................................................... 11
2.1 Installation Steps .......................................................................................... 11
2.2 Unpacking the Equipment ............................................................................ 11
2.3 Mounting the Equipment .............................................................................. 11
2.4 Mounting the Antenna.................................................................................. 12
2.5 DIP Switch/Jumper Settings ........................................................................ 13
2.6 DIP Switch 3 Decode ................................................................................... 14
2.7 IO Connections ............................................................................................ 15
2.8 Cellular Setup ............................................................................................... 18
2.9 Bluetooth Setup ............................................................................................ 18
3 LED States ........................................................................................................................... 19
4 IO Architecture .................................................................................................................... 20
5 Channels ............................................................................................................................... 21
5.1 Pre-Defined Channels .................................................................................. 21
5.2 Channel Data ................................................................................................ 29
6 SMS Text Commands .......................................................................................................... 31
6.1 Command Syntax ......................................................................................... 31
7 Modbus ................................................................................................................................ 34
7.1 RTU Slave .................................................................................................... 34
7.2 RTU Master.................................................................................................. 34
8 Debug Menu......................................................................................................................... 35
9 Configuration ....................................................................................................................... 36
9.1 Debug Configuration Commands ................................................................. 38
9.2 OTA Configuration Commands ................................................................... 42
9.3 Site Configuration – Type 1 ......................................................................... 43
9.4 Options Configuration – Type 2................................................................... 45
9.5 CELL Configuration – Type 3 ..................................................................... 47
9.6 FTP Configuration – Type 4 ........................................................................ 50
9.7 GeoFence Configuration – Type 5 ............................................................... 52
9.8 Serial Port Configuration – Type 6 .............................................................. 53
9.9 Reporting Configuration – Type 7 ............................................................... 55
9.10 Engine Configuration – Type 8 .................................................................... 57
9.11 Channel Configuration – Type 9 .................................................................. 59
9.12 Report Flag Configuration – Type 12 .......................................................... 63
9.13 Date/Time Read/Write – Type 16 ................................................................ 65
9.14 MODBUS Configuration – Type 18 ............................................................ 66
9.15 Analog Input Configuration – Type 11 ........................................................ 69
9.16 Digital Input Configuration – Type 17 ......................................................... 70
9.17 Digital Output Configuration – Type 13 ...................................................... 71

4
MessengerBLE
User Guide
9.18 EVAL Expression Configuration – Type 10 ................................................ 72
9.19 J1939 PGN Configuration – Type 15 ........................................................... 75
9.20 J1939 SPN Configuration – Type 14 ........................................................... 76
9.21 PEER Poll Configuration – Type 28 ............................................................ 78
9.22 PEER Push Configuration – Type 29 ........................................................... 79
9.23 Bluetooth Nordic Configuration – Type 52 ................................................. 81
10 How-To............................................................................................................................ 82
10.1 Setting reporting rates when moving and stationary .................................... 82
10.2 Computing Engine Hours from Engine Run ................................................ 82
10.3 Enabling low power mode to conserve battery ............................................ 83
10.4 Setting hard acceleration/deceleration alarms .............................................. 83
10.5 Using a Digital Input to Determine Engine On ............................................ 84
10.6 Using the Analog Input for Fuel Level ........................................................ 86
12 Appendix A – Monitored Engine Parameters .................................................................. 87
13 Appendix B – Data Registers ........................................................................................... 91
Table of Figures
Figure 1: Deutsch EEC Thermoplastic Enclosure Dimensions ..................................... 12
Figure2 - Messenger with Enclosure End-Cap Attached ............................................... 13
Table of Tables
Table 1: DIP Switch 3 Decode ...................................................................................... 14
Table 2: Cellular Modem Requirements ........................................................................ 18
Table 3: Pre-Defined Channels ...................................................................................... 21
Table 4: Action Commands ........................................................................................... 31
Table 5: Configuration Line Types ................................................................................ 37
Document References
Protocol document “M09-PRTCLxxx”
“Messenger MODBUS Slave Register Map”

5
MessengerBLE
User Guide
VERSION DATE NOTES
1 5/14/2020 Initial release
Copyright and Trademark Information
All Pages Copyright © 2020 Cattron. 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 Cattron’s 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 Cattron.

6
MessengerBLE
User Guide
Introduction
This User’s Manual describes installation and setup of the Messenger-BLE product.
Throughout this document, Messenger-BLE and Messenger are used interchangeably.
The Messenger is a complete monitoring, alarm notification, and telemetry platform.
The intended markets include (but not limited to) water/wastewater utility, off-road
heavy construction equipment, on-road semi-trucks, oil and gas, and standby power
generators. It supports monitoring of data values from on-board physical IO, the J1939
SAE engine bus topology, the industry standard Modbus RTU serial protocol, and
support of custom serial communications to external devices.
Features
The hardware feature set of this platform includes:
 ARM 32-bit Cortex -M4 Core w/FPU
 2 MB of on-board FLASH memory, 8MB of external FLASH
 640kB of on-board SRAM memory, 512kB of external battery-backed SRAM
 Real Time Clock (battery-backed)
 2 Serial Ports (RS485 only)
 4 Digital Inputs (user configurable for voltage or grounded input)
 3 Digital Outputs (open-collector transistor closures to ground)
 3 Analog Inputs (12-bit, user configurable for V or I input)
 1 CAN Interface, compliant to Bosch CAN Protocol v2.0 A/B
 Cellular modem, HSPA (3G) or LTE (4G)
 GPS receiver, providing location services using multiple GNSS constellations
 3-axis Accelerometer
 SuperCap for brown-out protection
 Separate Bluetooth engine for wireless connection to hand-held devices
 Deutsch EEC automotive grade enclosure

7
MessengerBLE
User Guide
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.
 virtual real-time transfer of monitored conditions
 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
 continuous monitoring of J1939 bus data
 event and data logging
 telemetry of monitored conditions to server applications via cellular
 OTA programming and diagnostics, cellular and Bluetooth
 SMS messages sent on monitored conditions
 parameter setting via SMS messages
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 connectivity and GPS for asset location.
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, RPM is fixed to channel 52. For channel 52, the user can set limits on
RPM for notification when RPM gets too high, and how to report the RPM values to a
host server.
Table 4.1 provides a description of all the pre-defined channels and channel numbers.
Appendix A identifies the set of SAE defined PGNs and SPNs for data values being read
from the engine bus. User can also configure for other engine values as needed.
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 sent typically consists of location,

8
MessengerBLE
User Guide
date/time, an event code, and associated data. An event code provides a unique
identifier to indicate the reason that notification is being sent – e.g. normal scheduled
update or an engine diagnostic message received. 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
 Any diagnostic message received from the engine bus
 A digital input changing state (on/off)
 A digital output changing state (on/off)
 An analog input transitioning into a warning or alarm region
 An analog input changing by user defined delta
 A scheduled/periodic update
 End of day
 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 a
particular event has occurred. Protocol document “M09-PRTCLxxx” contains a list of all
event codes.
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

9
MessengerBLE
User Guide
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 timestamp data records and events. All messages sent to the host
server contain a timestamp to provide a chronology of data/events to the end user.
This timestamp is UTC time. All timestamps viewed from the debug menu are local
time based on the configured time zone.
The RTC is battery backed to provide time keeping during power off. If the RTC is
configured to be automatically set, the Messenger will set time after every power on
and perform a time check every midnight. If the RTC time differs from actual time by
more than 30 seconds, the RTC time will be adjusted.
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.
Automatic
via GPS
The Messenger will set the RTC from
the date/time read from the GPS
module.
Manually Set the time via the Debug port
through the Maintenance menu.
OTA/SMS
The RTC is set from an OTA config
command or an SMS config
command.
Configuration settings are available to define how the RTC is set.
1.3.5 Packaging
The Messenger is packaged in an automotive grade Deutsch enclosure. There are 2
antenna connections, one SMA connection for the GPS and one SMA-RP (reverse
polarity) connection for cellular. The enclosure end-cap provides 2 circular M12, 8-pin
connectors for power and IO.

10
MessengerBLE
User Guide
1.3.6 Specifications
Power input:
8-36 vdc
26 mA @ 24vdc (avg)
reverse polarity protection
overvoltage protection
internal solid-state fuse
Digital outputs (3 ea):
Open-collector transistor switch to ground (current sink)
500mA @ 12vdc
current limited
overvoltage protection
Digital inputs (4 ea):
two modes of operation, DC voltage input or grounded input (user selectable)
high-speed pulse counter inputs (user selectable)
current limited
overvoltage protection
Analog inputs (3 ea):
12-bit ADC
accuracy: +/- 2% FS
input ranges: 0-10vdc, 0-20mA, 4-20mA (user selectable)
CAN input (1 ea):
termination resistor (user selectable)
spike suppression
Serial RS485 inputs (2 ea):
termination resistor (user selectable)
current limited
overvoltage protection
Bluetooth (1 ea):
internal chip antenna (external available, contact factory)
application available for hand-held devices
Operating Temperature Range:
-40 to +85 degC

11
MessengerBLE
User Guide
2 Installation and Setup
This section provides information on installing the Messenger and confirming its initial
operation.
WARNING
It is recommended to read this entire chapter before starting 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 connections. The antenna
wires should have a service loop just below the antenna connectors.
3. Connect Main Power.
4. Connect to engine bus - J1939.
5. Confirm that the Amber LED indicates normal CAN activity when the engine is
started. If it does not, check the following:
a. Confirm there is proper termination on the main CAN bus trunk.
b. Double check the bus connections and signal polarity.
2.2 Unpacking the Equipment
The Messenger is shipped with the following:
 The Messenger electronics housed in a Deutsch thermoplastic enclosure
 A Cellular/GPS dual antenna (magnetic mount or bulkhead screw mount)
 User’s Guide (available electronically)
 Cable harnesses providing access to all Messenger IO
2.3 Mounting the Equipment
The Messenger is housed in an automotive grade weather resistant enclosure. The
entire enclosure with mated connectors is rated to IP55.
CAUTION

12
MessengerBLE
User Guide
Mount the enclosure in a vertical orientation and provide service loops for each
antenna and IO cable to prevent water intrusion.
2.3.1 EEC Thermoplastic Enclosure
Figure 1: Deutsch EEC Thermoplastic Enclosure Dimensions
When mounting the enclosure to vibrating equipment, it is recommended to use
rubber dampeners to isolate the unit. Stainless mounting hardware is preferred and
the use of lock washers is highly recommended.
2.4 Mounting the Antenna
The antenna shipped with the Messenger is a hockey puck style, combination cell and
GPS. The GPS antenna frequency is 1575.42MHz. The cell is a dual band antenna,
880MHz- 960MHz and 1710MHz-1990MHz. 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. The
GPS side works best when it can see the horizon. If the antenna is mounted outside
and may be subject to lightning, a surge arrestor can be inserted between the
Messenger antenna SMA connection and the antenna. If the antenna is mounted
inside, it should be located near a window.

13
MessengerBLE
User Guide
CAUTION
Service loops should be provided for the antenna cabling, near the antenna connections to minimize
water ingress through the SMA RF coax connections.
2.5 DIP Switch/Jumper Settings
The Messenger uses an on-board DIP switch and jumpers to configure application
specific IO and set operational modes. DIP SW3 is used to set operational modes. See
Figure 3 for switch/jumper locations. See Figure 4 for IO selection settings.
Figure 2: Messenger with Enclosure End-Cap Attached

14
MessengerBLE
User Guide
2.6 DIP Switch 3 Decode
DIP Switch 3 is a 4-position dip switch located on the left side of the board (Figure 3). If
any switch 3 position is changed, the power must be cycled for the new switch
positions to be read.
Table 1: DIP Switch 3 Decode
Position 1 2 3 4 Description
Function
Enter BOOT
Loader    
Used for code
download via
internal debug
port - RS232,
57600,8,1,N
Factory
Default
Settings
   
Key:  = switch in “OFF” position,  = switch in “ON” position
NOTE: Switch positions 1 and 2 will override any other settings for Ports 2, 3, or 4.

15
MessengerBLE
User Guide
2.7 IO Connections
The Deutsch EEC enclosure has a water tight end-cap fitted with one M12x8 MALE
connector (JR2-PRI), one M12x8 FEMALE connector (JR1-SEC), one SMA JACK GPS
antenna connector, and one SMA-RP JACK CELL antenna connector. See figure x.
Figure 3: Messenger IO Connectors
Depending on the customer input/output requirements, there may be 1 or 2 cable
harnesses supplied for the customer to connect to his field signals. The IO signals
available in the Messenger are diagrammed below indicating how to connect field
signals to the Messenger using these cables. Custom cable configurations can be made
to facilitate field wiring. Contact the factory for assistance.
There are 3 IO signals that are user definable via on-board jumpers. The options for
these user IO signals are shown below.

16
MessengerBLE
User Guide
Figure X: Messenger IO Signals
JR1 (Sec)
WHT
BRN
GRN
YEL
GRY
PNK
BLU
RED
PWR IN
CAN L
CAN H
P1-RS485B
P1-RS485A
DIN 1
AIN 1
GND
GND
DIN 3
DIN 4
DIN 2
AIN 2
USER IO 1
USER IO 3
USER IO 2
USER IO 1 – DOUT 1 or P2-RS485A
USER IO 2 – DOUT 2 or P2-RS485B
USER IO 3 – DOUT 3 or AIN 3
JR2 (Pri)
WHT
BRN
GRN
YEL
GRY
PNK
BLU
RED
MessengerBLE
IO Harness
Flying Lead
8-Pin Female M12
8-Pin Male M12 WHT
WHT
RED
RED
BRN
BRN
GRN
GRN
BLU
BLU
YEL
YEL
PNK
PNK
GRY
GRY
V+ (8-36vdc)
GND
CAN-L
CAN-H
Cables
PVC Jacket
PVC Conductor Insulation
8x22
2A, 60VAC, 75VDC
Temp: -40C to 105C
Protection: NEMA 1,3,4,6P,
IP68 and IP69K
USER IO 3
USER IO 2
USER IO 1
DIN 3
AIN 2
DIN 2
GND
DIN 4
DIN 1
AIN 1
P1-RS485B
P1-RS485A
1
2
3
4
5
6
7
8
1
2
3
4
5
6
7
8
Table 5: User IO 1 Jumper Selection – J11
User IO 1 J11
DOUT 1
1
-
2
P2
-
RS485A
2
-
3
Table 6: User IO 2 Jumper Selection – J10
User IO 2 J10
DOUT 2
1
-
2
P2
-
RS485B
2
-
3
Table 7: User IO 3 Jumper Selection – J9
User IO 3 J9
DOUT 3
1
-
2
AIN3
2
-
3

17
MessengerBLE
User Guide
Figure 4: User IO Jumper Location
If digital outputs (DOUT1, DOUT2, or DOUT3) are to be used in the application

18
MessengerBLE
User Guide
2.8 Cellular Setup
The Messenger supports two cellular technologies, HSPA (3G) and LTE (4G). The
current offering for HSPA is a 3G penta-band capable radio. For LTE, it is a 4G, dual-
band radio. Both of these radio options require a wireless account with a cellular
provider such as AT&T or Verizon.
Table 2: Cellular Modem Requirements
Radio Provider
Options
Account
Type
Static IP SIM APN Username/
Password
Server
IP/Port
HSPA
(3G)
AT&T
Verizon
Data+
SMS
required
required
required
optional
required
LTE
(
4
G)
AT&T
Verizon
Data+
SMS
required
required
r
equired
optional
required
2.9 Bluetooth Setup
The Messenger uses a dedicated processor for facilitating Bluetooth Low Energy
connections. The hardware offers two antenna options: a chip antenna enabled by
default and requiring no further hardware, and a U.FL connector for connecting
external antennas for the potential of greater RF performance.

19
MessengerBLE
User Guide
3 LED States
There is one tri-color LED visible to the user to indicate various system conditions.
These conditions are conveyed to the user via LED color and 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:
The number of blinks will range from 1 to 3. The general philosophy when deciding
behavior will be:
 1 blink will convey a state that the module is expected to be in most often
(the “OK” state)
 3 blinks are to convey that there is an issue that may need attention
 2 blinks are used as needed to convey a state that may be of interest to the
user
 no blinks (LED solid on or off) indicates the system is no longer functioning
(verify option to turn LED off is disabled - contact factory for assistance)
Status LED Behavior
The Status LED will cycle through blinking each color the appropriate number of times
to convey the state of the corresponding module. There is a pause between color
changes.
Table 3: LED Color/Blink Patterns
Module Color 1 Blink 2 Blinks 3 Blinks
Power Green Power OK ----
Power fail
(On Supercap)
Cell Red Data Queue Empty
Data
Queue Not
Empty
Fault / Failed to
initialize modem
Bluetooth Blue Advertising On
Device
Connected
Not advertising /
No comms to nRF
CAN
Amber
CAN OK
----
No CAN

20
MessengerBLE
User Guide
4 IO Architecture
The IO architecture is shown in the diagram below. Each of the physical IO entities has
a configuration that is set based on user requirements. Based on that configuration,
the values sampled are stored in their respective data registers. These data registers
are used to reference the corresponding value for use in channel creation or in
expressions used to compute values. The complete list of available data registers can
be found in Appendix B.
Figure 5: IO Architecture Diagram