Installation guide

LMU Users Guide

V1.0.6 December 10 2009

- 78 - CalAmp Proprietary & Confidential

11.1.1 SMS Event Report

The SMS Event Report is much like the LM Direct Event Report in that it is meant to

contain a useful set of location and unit status data. It should be noted that the SMS Event

Report will contain less data than the LM Direct Event Report due to message size

limitations of the SMS protocol. The message format is as follows:

!E<mobile ID><Mobile ID Type><sequence no.><time-

tag><latitude><longitude><speed><heading><number

Sats><fix status><carrier><RSSI><78omm.

state><hdop><inputs><unit status><event index><event

code><accums><list of accumulators>

The field definitions are as follows. Please note that all fields are ASCII Hex encoded. That

is, for a value of 4, the SMS Event report will encode it as 04. A value of 15 would be

encoded as 0F.

• <mobile ID> (8 bytes)

This is the Mobile ID of the LMU that originated the SMS message. The Mobile ID

is made up of numerical digits and is encoded in this field as packed BCD

• <mobile ID Type> (1 byte)

The type of Mobile ID being used by the LMU. The available types are:

0 – OFF

1 – Electronic Serial Number (ESN) of the LMU

2 – International Mobile Equipment Identifier (IMEI) or the Decimal Electronic

Serial Number (ESN-DEC) of the wireless modem

3 – International Mobile Subscriber Identifier (IMSI) of the SIM card. (iDEN and

GSM/GPRS devices only)

4 – User Defined Mobile ID

5 – Phone Number of the mobile (if available)

6 – The current IP Address of the LMU

. The

most significant digit is placed in the upper four bits of the first byte. Any bytes not

filled by the mobile ID value will contain FF. In the case where an odd number of

digits are used, a 0x0F is also used to pad the lower 4-bits of the last byte. For

example, a Mobile ID of 9043002123 would appear as 90433002123FFFFF

• <sequence no.> (2 bytes)

A 16-bit number used to uniquely identify a message. This number is initialized to 1

on a cold boot and will be incremented each time an inbound message is sent by the

LMU. The LMU remembers its current Sequence Number during sleep, though it

will eventually rollover from 65535 to 1, skipping zero.

• <time-tag> (4 bytes)

The time tag of the message in seconds, referenced from Jan 1, 1970. This would be

the same as the Update Time in an LM Direct Event Report.

Binary-coded decimal