Installation guide

LMU Users Guide

V1.0.6 December 10 2009

- 119 - CalAmp Proprietary & Confidential

various messages stored so we can create activity reports on the back end later. For the

disposition we will therefore use Send/Log.

ATS137=1

Once the type of message is selected, our next step is to determine the User Messaging

mode, that is, do we need to support Long Message mode. Given the messages we’re

sending fit well within the 802 byte limit on User Messages, we can keep things in standard

mode, giving:

ATS130=1

Next we need to setup the serial connection. The Net955 generally uses 9600 BAUD, 8 Data

Bits, No Parity and 1 Stop Bit. The LMU’s Host Port should be configured to match:

ATS131=5

ATS132=3

The messages from the Net955 will be in plain text and thus we can make use of a

Termination Character. The developer of the Net955’s application had made this Line Feed.

(Actually they made it Carriage Return and Line Feed but since the LMU can only deal with

one character, we must pick the last that appears.)

ATS133=4

ATS134=10

Since we are using a termination character, we can turn the other message creation limits off

(i.e. time and size)

ATS135=0

ATS138=0

We should also turn off the Message Count Filter:

ATS141=0

We need to select a User Message ID value. Remember that this setting has two purposes,

first any message created on the Host Port will be tagged with this type, and second it is used

as a filter. That means any message sent to the LMU intended for the Host Port must have

the same User Message ID value. For our Host Port we are going to use a value of 1.

ATS136=1

Our last step is to actually ensure that the Host Port is in MDT mode. This is done by

running a jumper wire from pin 2 to pin 3 on the ioPOD. Keep in mind that this should

only be done after all the host port setup commands have been completed as AT

Commands are not processed while the LMU is in MDT mode.