
83
MessengerBLE
User Guide
10.3
Enabling low power mode to conserve battery
In low power mode, the Messenger turns off the Cellular and GPS modules, stops
monitoring all inputs and puts the processor into a very low power mode. The
Messenger processor wakes up every 10 seconds to determine if the engine is running
– either from CAN activity, J1708 activity or Digital Input 1, whichever is configured to
indicate Engine Run.
The Messenger enters low power mode when the engine is not running for enterlp
seconds.
The Messenger exits low power mode every exitlp minutes to check for incoming SMS
or over the air messages.
Setting
Via SMS, OTA or Debug Port
Enable Low Power mode
SMS: <config(2,1,1)>
OTA: $TXT:<config(2,1,1)>
OTA Messenger Protocol: |258,2,1,1|
Debug Port: 2,1,1
Set time delay to enter
low power mode to 120
seconds. (enterlp)
SMS: <config(1,4,120)>
OTA: $TXT:<config(1,4,120)>
OTA Messenger Protocol: |258,1,4,120|
Debug Port: 1,4,120
Set time interval to exit
low power mode to
check for any incoming
messages to 60 minutes.
SMS: <config(1,5,60)>
OTA: $TXT:<config(1,5,60)>
OTA Messenger Protocol: |258,1,5,60|
Debug Port: 1,5,60
10.4
Setting hard acceleration/deceleration alarms
The Messenger continually evaluates the Road Speed of the vehicle based on J1939 or
J1708 data. Hard Braking and Fast Acceleration alarms are immediately reported
when the Road Speed of the vehicle exceeds either of the available limits.
The limits are specified in MPH. If the Road Speed changes by more than the specified
MPH in a second, then the condition is in alarm and it is reported with a unique event
number, the current location and time.