Installation guide

LMU Users Guide

V1.0.6 December 10 2009

- 71 - CalAmp Proprietary & Confidential

empty its log using a SEND LOG Action or a message using the Store and Forward

mechanism is introduced.

In PEG, an Action using just LOG operates in batch mode.

• Unacknowledged: Unacknowledged messages are ones that are never logged. The

LMU attempts to send the data if the network is available. Once the send has been

completed, the message is erased. If the network is not available, then the message is

immediately deleted.

Which mode is in use primarily dictated by PEG, though the log can be placed in Batch

mode on power up by setting bit 5 of S-register 140. That is:

AT$APP PARAM 1024,20,32,32

To boot the LMU in Store and Forward mode, you would clear bit 5.

AT$APP PARAM 1024,20,32,0

By default, the log of the LMU will be in Store and Forward mode.

10.2.2 Working with Retry Schedules – Inbound Retries

The Inbound Retry Schedule (Parameter 771) occurs when the LMU is using the Store and

Forward log mode. The Schedule dictates two things, the number of times the LMU will

attempt to send an LM Direct packet to the inbound IP Address and the delay between each

attempt. Up to 6 attempts may be defined with each interval ranging from 0 to 255s. Each

attempt is associated with a different Index value of Parameter 771. The values within each

Index contain the delay until the next attempt As an example, say you wish to set up three

retries growing from 5s

, to 10s and finally to 15s. The following three AT Commands

would accomplish this:

AT$APP PARAM 771,0,5

AT$APP PARAM 771,1,10

AT$APP PARAM 771,2,15

When the schedule expires, the LMU officially logs the data. That is, the Historic bit of the

Fix-Status field will be set and the Log Active PEG trigger will occur.

Please note that the LMU will stop processing the Inbound Retry Schedule when it

encounters the first 0s value.

By default the LMU is set to two attempts with a 15s delay between each.

10.2.3 Working with Retry Schedules – Log Retries

The Log Retry Schedule begins when the LMU’s log goes active and it is in Store and

Forward mode. In this mode, the LMU will attempt to send the first message in its log once

Actually 5s is a little too short for an inbound retry. You should really use 10s or greater for each attempt

you wish to define.