LMU Users Guide 2011-01-04

8/18/2019 LMU Users Guide 2011-01-04

1/229

Copyright ©CalAmp DataCom Inc 2011 - 1 - CalAmp Proprietary & Confidential

LMUUsers Guide

8/18/2019 LMU Users Guide 2011-01-04

2/229

Copyright ©CalAmp DataCom Inc 2011 - 2 - CalAmp Proprietary & Confidential

Version 1.0.9January 2011

8/18/2019 LMU Users Guide 2011-01-04

3/229

LMU Users Guide

V1.0.9 January 4, 2011Copyright ©CalAmp DataCom Inc 2010 - 1 - CalAmp Proprietary & Confidential

Table of Contents

Table of Contents ........................................................................................................................................ 11 Introduction ......................................................................................................................................... 5

1.1 About CalAmp – Who we are… ................................................................................................. 51.2 About CalAmp – What we do… ................................................................................................. 51.3 About this Manual ....................................................................................................................... 51.4 About the Reader ......................................................................................................................... 5

2 CalAmp LMU – Hardware Overview ............................................................................................... 63 LMU Setup – Configuration Overview ............................................................................................. 8

3.1 Parameters ................................................................................................................................... 83.1.1 What are Parameters? ....................................................................................................... 8 3.1.2 How does one program Parameters? ................................................................................ 8

3.2 S-Registers .................................................................................................................................103.2.1 What are S-Registers? .......................................................................................................10

3.3 Parameter Masking .....................................................................................................................113.3.1 What is Parameter Masking? ............................................................................................113.3.2 What is a bit mapped parameter value? ...........................................................................113.3.3 How is a mask used? .........................................................................................................11

4 Working with Inputs, Outputs and Power .......................................................................................124.1 I/O Introduction ..........................................................................................................................124.2 Input Types .................................................................................................................................12

4.2.1 Digital Inputs ....................................................................................................................124.2.2 Motion Sensor Input ..........................................................................................................144.2.3 Power State Input ..............................................................................................................16 4.2.4 Battery Voltage Critical Input ...........................................................................................16 4.2.5 High Temperature Input ...................................................................................................16 4.2.6 The 1 Bit Bus .....................................................................................................................17 4.2.7 Analog to Digital Inputs ....................................................................................................18

4.3 Output Types ..............................................................................................................................194.3.1 Relay Outputs ....................................................................................................................194.3.2 External vs. Internal Power Switch ...................................................................................194.3.3 Enable / Disable Battery Charging ...................................................................................194.3.4 LED Outputs .....................................................................................................................19

4.4 Selecting the GPIO Function ......................................................................................................204.5 Working with Sleep Mode ..........................................................................................................21

4.5.1 Configuring the Input Wake-Up Monitor ..........................................................................214.5.2 Keeping the Expansion Port powered during sleep ..........................................................234.5.3 Keeping the Modem On during sleep ................................................................................234.5.4 Restoring Output States ....................................................................................................24

4.6 Working with the Status LEDs ...................................................................................................254.6.1 Input State and Satellite Count Mode ...............................................................................25

4.6.2

Alternate LED Blink Code

................................................................................................26 4.6.3 Disabling the Status LEDs ................................................................................................27 4.7 Restoring values through a power cycle .....................................................................................28

5 Working with External Serial Devices .............................................................................................305.1 Using the Host Port ....................................................................................................................31

5.1.1 Host Mode - AT Command Setup ......................................................................................315.1.2 Host Mode – NMEA Output ..............................................................................................325.1.3 Host Mode – Dial-Up Networking ....................................................................................335.1.4 MDT Mode ........................................................................................................................35

5.2 Using the Aux Port .....................................................................................................................41

8/18/2019 LMU Users Guide 2011-01-04

4/229

LMU Users Guide


5.2.1 NMEA Mode .....................................................................................................................415.2.2 MDT Mode ........................................................................................................................41

5.3 Using The Garmin NUVI or MacKenzie Labs DAD-A1214 .....................................................455.4 Using the Modem Port ...............................................................................................................46

5.4.1 Selecting a Modem Driver ................................................................................................46 5.4.2 Configuring the Modem Port’s BAUD Rate .....................................................................47 5.4.3 Setting the dial string ........................................................................................................47 5.4.4 Setting the network username and password ....................................................................48

5.5 Working with Serial Streams ......................................................................................................495.5.1 Configuring Streams .........................................................................................................50

5.6 Using the CalAmp Bluetooth Adapter (BTA) ............................................................................535.7 Using the BTA as the Host Port .................................................................................................54

5.7.1 NMEA Output ...................................................................................................................545.7.2 AT Command and Debug Output ......................................................................................545.7.3 Dial-Up Networking – Dial-Up Networking Profile .........................................................555.7.4 Dial-Up Networking – Serial Port Profile ........................................................................55

6 Working with Comm .........................................................................................................................566.1 Using a second Comm profile ....................................................................................................566.2 GPRS context switching .............................................................................................................566.3 Automatically resetting the wireless modem ..............................................................................57

6.3.1 Send fail restart .................................................................................................................57 6.3.2 Log activity restart ............................................................................................................58 6.3.3 Connection monitoring .....................................................................................................58 6.3.4 Querying the modem for network status ...........................................................................596.3.5 Socket Monitoring .............................................................................................................59

6.4 PDP Context Reset .....................................................................................................................596.5 Network selection .......................................................................................................................60

6.5.1 GPRS networks .................................................................................................................616.5.2 Frequency Selection ..........................................................................................................616.5.3 CDMA networks ................................................................................................................626.5.4 iDEN networks ..................................................................................................................62

6.6 Controlling the Data Session ......................................................................................................63

6.7

Updating the PRL

.......................................................................................................................636.8 Back Off Algorithms ..................................................................................................................646.9 Working with the Outbound Socket ...........................................................................................64

7 Controlling LMU Access ...................................................................................................................657.1 Service Enables ..........................................................................................................................657.2 Access IP Address List ...............................................................................................................667.3 Remote Host IP Address List .....................................................................................................677.4 Primary Port Password ...............................................................................................................687.5 AT Command Password .............................................................................................................68

8 Working with GPS .............................................................................................................................708.1 NMEA Messaging ......................................................................................................................708.2 GPS Timeouts ............................................................................................................................70

8.2.1 Last Known Timeout .........................................................................................................708.2.2 GPS Lost ...........................................................................................................................708.2.3 GPS Restart .......................................................................................................................71

8.3 Pinning .......................................................................................................................................718.3.1 Enable / Disable pinning ..................................................................................................718.3.2 Using Ignition to control Pinning .....................................................................................718.3.3 GPS Accuracy Threshold ..................................................................................................728.3.4 GPS Fix Quality ................................................................................................................728.3.5 The effects of Pinning ........................................................................................................72

8.4 GPS Special Functions ...............................................................................................................738.4.1 Receiver Mode ..................................................................................................................73

8/18/2019 LMU Users Guide 2011-01-04

5/229

LMU Users Guide


8.4.2 Enabling SBAS Support ....................................................................................................738.4.3 Elevation Filter .................................................................................................................738.4.4 Using Active or Passive GPS Antennas ............................................................................748.4.5 Update Rate ......................................................................................................................74

8.5 Local GPS Messaging ................................................................................................................758.5.1 Odometer Message ...........................................................................................................758.5.2 Position Update Message .................................................................................................76 8.5.3 GPS Debug Output ...........................................................................................................78

8.6 Over-The Air Real-Time GPS Updates ......................................................................................788.7 Obtaining Time ...........................................................................................................................78

9 CalAmp LMU Interface – LM Direct ..............................................................................................799.1 Using the LM Direct Protocol ....................................................................................................799.2 Inbound Settings .........................................................................................................................79

9.2.1 Message Logging ..............................................................................................................809.2.2 Working with Retry Schedules – Inbound Retries .............................................................819.2.3 Working with Retry Schedules – Log Retries ....................................................................819.2.4 Using Multiple Inbound Addresses ...................................................................................82

9.3 Maintenance Settings .................................................................................................................859.3.1 Maintenance Delivery .......................................................................................................859.3.2 Maintenance Configuration ..............................................................................................859.3.3 Maintenance Interval ........................................................................................................85

9.4 Null Messaging ...........................................................................................................................859.5 Changing the Local Port .............................................................................................................86

10 CalAmp LMU Interface – SMS ........................................................................................................8710.1 Reporting Data via SMS .............................................................................................................87

10.1.1 SMS Event Report .............................................................................................................88 10.1.2 SMS Text Status Message ..................................................................................................9110.1.3 SMS Text Message ............................................................................................................9410.1.4 SMS GPS Status Message .................................................................................................9510.1.5 SMS Comm Status Message ..............................................................................................96

10.2 SMS Request Messages ..............................................................................................................9810.2.1 Unit Request Messages .....................................................................................................98

10.2.2

SMS Parameter Message

................................................................................................10010.2.3 Serial Message Request ..................................................................................................10011 CalAmp LMU Interface – TAIP .....................................................................................................101

11.1 TAIP Sentences ........................................................................................................................10111.1.1 General Sentence Structure ............................................................................................10111.1.2 PV (Position Velocity) Sentence Structure ......................................................................10211.1.3 LN (Long Navigation) Sentence Structure ......................................................................10211.1.4 IO (Input / Output) Sentence Structure ...........................................................................10311.1.5 Optional Fields ...............................................................................................................103

11.2 TAIP Settings ...........................................................................................................................10611.2.1 Enabling TAIP ................................................................................................................106 11.2.2 Message Selection ...........................................................................................................107 11.2.3 Message Destination .......................................................................................................107 11.2.4 Local Port .......................................................................................................................107

11.3 TAIP Reporting ........................................................................................................................10711.3.1 Scheduled Reporting – Standard Mode ...........................................................................108 11.3.2 Scheduled Reporting – Directed .....................................................................................108 11.3.3 PEG Reporting ................................................................................................................108 11.3.4 SMS Reporting ................................................................................................................109

12 LMU Maintenance ...........................................................................................................................11012.1 Mobile ID .................................................................................................................................11012.2 Firmware Versioning ................................................................................................................11112.3 Configuration Versioning .........................................................................................................111

8/18/2019 LMU Users Guide 2011-01-04

6/229

LMU Users Guide


12.4 Downloading Firmware ............................................................................................................11212.5 Downloading Firmware – Locally ............................................................................................112

12.5.1 Local Firmware Upgrade ...............................................................................................11212.5.2 Local Firmware Upgrade – LMU-1000™ ......................................................................113

12.6 Downloading Firmware – Remotely ........................................................................................11412.6.1 Remote Firmware Upgrade – LMU 1000™ ...................................................................114

13 LMU Programming Examples ........................................................................................................11513.1 LMU Programming – Delivery Fleet .......................................................................................116

13.1.1 Project Overview ............................................................................................................116 13.1.2 Project Proposal .............................................................................................................116 13.1.3 LMU Setup – Planning ....................................................................................................117 13.1.4 LMU Setup – Development .............................................................................................118

13.2 PEG Programming – Long Haul Trucks ..................................................................................12213.2.1 Project Overview ............................................................................................................12213.2.2 Project Proposal .............................................................................................................12213.2.3 LMU Setup – Planning ....................................................................................................12313.2.4 LMU Setup – Development – LMU 4200™ ....................................................................12413.2.5 LMU Setup Development – LMU-1110™ .......................................................................124

13.3 LMU Programming – Taxi System ..........................................................................................12513.3.1 Project Overview ............................................................................................................12513.3.2 Project Proposal .............................................................................................................12513.3.3 LMU Programming – Planning ......................................................................................126 13.3.4 LMU Setup – Development .............................................................................................127

Appendix A — Parameter Definitions .....................................................................................................131Appendix B — S-Register Settings .............................................................................................................. 1Appendix C — ASCII Chart ....................................................................................................................... 1

Hexadecimal to ASCII ............................................................................................................................... 1Decimal to ASCII ...................................................................................................................................... 1

Appendix D – HyperTerminal Setup .......................................................................................................... 2Appendix E - Windows Vista – Putty Setup ............................................................................................... 5

Logging data to file with PuTTY ............................................................................................................... 7Appendix F - Pairing to the LMU Using Windows Mobile ....................................................................... 9

Appendix G - Adding a Modem Driver .....................................................................................................10Windows Vista .........................................................................................................................................10Windows XP .............................................................................................................................................17Windows Mobile 5.0 ................................................................................................................................23

Appendix H – Creating a Dial-Up Networking Session ...........................................................................24Windows Vista .........................................................................................................................................24Windows XP .............................................................................................................................................32Windows Mobile ......................................................................................................................................40

8/18/2019 LMU Users Guide 2011-01-04

7/229

LMU Users Guide


1

1.1

Introduction

Founded in 1981, CalAmp stands at the forefront of technology evolution as a result ofstrategic collaborations with forward thinking customers. By anticipating technology andindustry trends, we rapidly develop cutting-edge solutions to help our customers effectivelyrealize time and cost savings. Based on our long history of successful product deployment

we help our customers by managing the entire product lifecycle - from design tomanufacturing to implementation.

About CalAmp – Who we are…

1.2 We are a recognized and trusted leader in satellite DBS technology, wireless networks,software application development, embedded computing and enterprise mobility. We areconsidered the solution industry’s foremost specialist in networking applications, wireless

technologies, digital multimedia delivery, residential broadband data delivery, healthcare andmedical and public safety.

About CalAmp – What we do…

1.3 This guide is meant to be a comprehensive description of all features of the CalAmp FleetManagement and Vehicle Tracking product lines and their associated peripherals. The onlyexceptions are features having to do with PEG or LM Direct. These features are describedin the PEG™ Programming Guide and LM Direct Reference Guide. All hardware,activation and installation information can be found in the corresponding InstallationGuides.

About this Manual

When a feature is common to all products the device will be referenced as the CalAmpLMU, or just LMU. When a feature is device specific, the full version of the device (LMU-4200™, LMU-2600™, LMU-1200™, etc…) will be used. Users should, however, refer tothe compatibility tables in Appendix A and B if feature availability is in question.

1.4 This document is intended for any personnel who are required to activate, configure andinstall an LMU. It is expected that the reader has some familiarity with vehicle hardware as

well as basic knowledge of the Windows ™ operating systems, specifically knowledge ofHyperTerminal and Windows Dial-Up Network is required.

About the Reader

8/18/2019 LMU Users Guide 2011-01-04

8/229

LMU Users Guide


2 In today's competitive market place, many companies rely on telemetrics in their business toremove or minimize the risks associated with vehicle investment, improving efficiency,

productivity and reducing their overall transportation costs. CalAmp products offer easysolutions to a wide range of markets.

CalAmp LMU – Hardware Overview

• LMU-4200™CalAmp’s flagship LMU-4200™ product has the features, expandability, andflexibility with the intelligence to meet all customer’s ever changing needs in fleetmanagement. The LMU-4200™ offers a full set of features, comprehensive I/Osystem and expandable accessories that make it an industry leading valueproposition.

• LMU-4100™ Cutting-edge location technology in an affordable device with the intelligence to help

meet customer's ever changing needs.• LMU-2600™ The LMU-2600 fleet tracking unit offers leading edge technology including a new 3Daccelerometer for measuring driver behavior and vehicle impacts while offering highreliability fleet customers demand.

• LMU-2500™ This ultra-sensitive tracking device is unrivaled in its class with next generation GPStechnology at an economical price.

• LMU-1200™ This economical, full-featured device was designed for easy and reliable installationand features an internal back-up battery

• LMU-1100™, LMU-1110™, LMU-1150™, LMU-1190™ The LMU-11xx™ series are economical, fully sealed vehicle tracking productsdesigned for easy and reliable installation in recreational vehicles. The LMU-11xx™series are ideal solutions for asset monitoring and theft recovery for motorcycles,snowmobiles and other outdoor recreational vehicles.

• RMU-900™ The RMU-900™ is an economical remote monitoring unit designed for simple andreliable remote monitoring and control applications.

• LMU-900™ The LMU-900™ device is an ideal solution for automotive insurance, stolen vehicle, vehicle finance, auto rental and other automotive tracking applications.

• LMU-700™ The LMU-700™ is an economical vehicle tracking product designed for easy andreliable installation in automobiles. The LMU-700™ is an ideal solution forautomotive insurance, stolen vehicle, vehicle finance, auto rental and otherautomotive tracking applications.

• MTU-100™ This fully sealed mobile tracker is ideal for monitoring person assets such as patients, work force, VIPS and pets or mobile equipment and containers

8/18/2019 LMU Users Guide 2011-01-04

9/229

LMU Users Guide


Full details for each product can be found in their corresponding installation guide.

8/18/2019 LMU Users Guide 2011-01-04

10/229

LMU Users Guide


3 This section describes how the LMUs store their configuration data and how they areprogrammed. The meaning of each parameter will be touched upon in the sections that

follow. A complete listing of parameters and S-registers can be found in Appendix A and Brespectively.

LMU Setup – Configuration Overview

3.1

3.1.1 What are Parameters?

Parameters

Parameters are how the LMU stores any of its configuration items thus; any setting that canbe changed is contained within a Parameter.

Parameters are made up of three settings, an ID, an Index and a Value.

The Parameter ID describes what the Parameter is, how many Indexes are available and what data the Value should contain. As an example, the Inbound Address Parameter (ID of768) contains 4 Indexes and stores an IPv4 address.

In many cases there are multiple Values associated with a given Parameter ID, for examplethere are 16 possible PEG Timers. The Parameter Index indicates which of the Values youare attempting to access or program. Indexes start from 0 and range to N-1 where N is thetotal number of available Values. For example, the 16 PEG Timers would range from Index0 (the 1st timer) to Index 15 (the 16 th Timer). When programming parameters, it is veryimportant to make sure you do not exceed the maximum index value for a given Parameteras this may cause unexpected behaviors in the LMU.

The last piece of a Parameter is the Value. The Value contains the actual setting of theParameter such as 15s for a Timer. Some Parameters support Values with multiple parts.

The PEG Zone Parameter is a good example of this. The Value of a PEG zone is split into6 parts: a latitude, a longitude, 2 distance values, a spare value and a hysteresis value. Thecontents of the Value of a Parameter are defined by the Parameter ID.

Appendix A of this document contains a complete listing of Parameter IDs, their Indexranges and the Value definitions. It is important to note that not all LMUs support allParameters or index ranges. These variances between LMUs are also described in Appendix

A and throughout this document.

There is, however, one configuration item that is not stored in a Parameter, namely Geo-Zones (i.e. the point zones and polygon zones). Geo-Zones have their own separateprogramming interface which is discussed in the PEG Programmers Guide and the LMDirect Reference Guide.

3.1.2 How does one program Parameters?Parameters are programmed in one of three ways, either via AT Commands using the

AT$APP PARAM, via an LM Direct™ Parameter Message or via an SMS Parameter

8/18/2019 LMU Users Guide 2011-01-04

11/229

LMU Users Guide


Message. This manual will always use the AT Command based means of programmingParameters. The LM Direct™ Parameter Message is described in the LM Direct™Reference Guide. The SMS Parameter Messages are described later in this document.

3.1.2.1 AT Commands The AT$APP PARAM commands can be used to query or set Parameter Values. The setcommand generally looks like:

AT$APP PARAM , ,

It should be noted that there can be more than one field depending on theParameter’s definition. Each sub-Value should be separated by a comma.

The query command takes two forms, a query for a single Value of a specific Index or aquery for all Values.

To query a specific Value, you need to reference which Parameter Index you are looking for. The command would look as follows:

AT$APP PARAM? ,

If the field is not provided, the LMU will responds with the 1 st

The response will look like:index (i.e. index 0).

, , OK

To query all Values of a Parameter a wild card character is used in place of the Index. Thiscommand would look as follows:

AT$APP PARAM? , *

The response will look like:

, , , , . . ., ,

OKFor Parameters with a large number of Indices, such as the PEG Event list, it may not bepossible to display all Parameters.

Like the programming command there may be more than one field for a givenparameter. Each sub-value is separated by a comma. The one exception is masks. Mask

8/18/2019 LMU Users Guide 2011-01-04

12/229

LMU Users Guide


values are not displayed in the query response but they are required in the programmingcommand. Masks are discussed later in this document.

The LMU does support several other AT Commands to query and change the values ofparameters. The most common ones are mentioned through-out this document, though allsupported AT Commands can be found in the CalAmp AT Command Set.

A terminal program such as HyperTerminal 1

3.1.2.2 Parameter Messages

is generally used to issue AT Commands to theLMU. Please refer to Appendix D for instructions on establishing a connection.

Parameter Messages are a means of remotely changing the parameter values of an LMU. They can be sent in one of two ways: either via SMS or via an LM Direct™ Parametermessage. SMS Parameter Messages are discussed in detail later in this document. LMDirect™ Parameter Messages are discussed in the LM Direct Reference Guide.

3.2

3.2.1 What are S-Registers?

S-Registers

S-Registers are a standard means of configuring and programming Hayes compatiblemodems. Any modem, or any modem like device typically supports some range of S-Registers. While the LMU does support S-Registers, it does not support any of the morecommon lower S-Registers (such as S-Register 0, which is typically used as the number ofrings to wait before answering an incoming call). The LMU’s S-Registers begin at S-Register120.

S-Registers are accessed through Parameter ID 1024. S-Registers, however, differ from otherParameters in two ways: first, their Values tend not to change once the LMU is fullyconfigured. For instance, S-Register 120 is used to select what type of wireless modem theLMU is using. The other difference is they have an alternate AT Command that can be usedto set and query their values. The commands are:

Set:ATS=

Query:ATS?

Query Response:

OK S-Registers programmed via this command cannot be masked. To take advantage of

masking, the Parameter command described above must be used. Masking is describedbelow.

1 HyperTerminal is owned and supported by Hilgraeve, Inc. Any issues with HyperTerminal should bedirected to Hilgraeve support.

8/18/2019 LMU Users Guide 2011-01-04

13/229

LMU Users Guide


The available S-Registers, their settings and LMU compatibility are listed in Appendix B.

S-Registers start at S-120 for the Parameter commands (or messages) this corresponds to thefirst Index of 0 therefore, the Index of an S-Register is the S-Register number minus 120.

3.3

3.3.1 What is Parameter Masking?

Parameter Masking

Parameter masking is a means of programming select parts of a Parameter’s Value. Thistypically only applies to Parameter Values that are bit mapped. The one exception is that

ALL S-registers must be masked when they are programmed via the Parameter ATCommand. When using the ATS command a full mask value (i.e. all bit areprogrammed) is automatically assumed. PULS™ also assumes a full mask for any bitmapped value it changes.

3.3.2 What is a bit mapped parameter value?Bit mapped Parameter Values are ones where each bit controls a different setting within theLMU. That is, each bit tends to turn on or off a particular feature (say the TAIP interface)depending if the bit is set or cleared. Bit mapping of values is most common in S-Registers,though there are some other Parameters that support it.

3.3.3 How is a mask used? A Mask allows a programmer to select which bits of a Value to change. That is, if bit 0 in themask is set, then the value of bit 0 can be changed. The mask value has the same range as the

Value. That is a 1 byte Value (range of 0-255) will have a 1 byte mask (also ranging from 0-255).

8/18/2019 LMU Users Guide 2011-01-04

14/229

LMU Users Guide


4

Instructions describing the basic setup and configuration of an LMU can be found in itscorresponding Hardware and Installation Guide. This section describes the variousconfiguration settings that can be used beyond the basic setup.

Working with Inputs Outputs andPower

4.1 The CalAmp LMU products offer a range of inputs and outputs to enable a wide variety of vehicle and asset tracking applications. For a complete description of what types of inputsand outputs are supported by a given device, please refer to its Hardware and InstallationGuide.

I/O Introduction

4.2

The LMU products offer the following input types. Please note that not all inputs aresupported by all products.

Input Types

4.2.1 Digital InputsDigital inputs are meant to detect on/off behaviors such as ignition on/off or dooropened/closed.

The LMU’s digital inputs are protected from typical vehicle transients and can be directlyconnected to most vehicle level logical inputs from 6 volts up to vehicle power. Their inputimpedance is approximately 10 k Ω .

For the most part, each LMU will have at least 1 digital input (Ignition / Input 0), thoughthe more flexible devices offer up to 7 more (Inputs 1 – 7). When present, the Ignition Inputis biased low (i.e. held at GND thru a resistance). Depending on the LMU, the other inputscan be biased high or low or be switched between the two. For example, Input 1 on theLMU-1100™ is biased high, Input 1 on the LMU-2500™ is biased low and Input 1 on theLMU-1200™ can be configured with a high or low bias.

The diagrams below show some typical connections to the inputs in both a high- and low-biased configuration:

8/18/2019 LMU Users Guide 2011-01-04

15/229

LMU Users Guide


Figu re 1 Sam ple Digi tal Input Wiring

8/18/2019 LMU Users Guide 2011-01-04

16/229

LMU Users Guide


4.2.1.1 Changing the Input BiasFor some LMU products, the input Bias can be controlled by S-Register 158 (or Parameter1024, Index 38). Each bit of this register is assigned to a specific input. If the associated bit isset, then the input is biased high, if the bit is cleared, then the input is biased low. The input

to bit mapping is as follows:Bit Input S-Register Mask0 Not Used1 Input 1 22 Input 2 43 Input 3 84 Input 4 165 Input 5 326 Input 6 647 Input 7 128

For example, to bias inputs 1, 3, 5 and 7 high and bias 2, 4 and 6 low, you would use the

following 7 commands:

AT$APP PARAM 1024, 38, 2, 2AT$APP PARAM 1024, 38, 4, 0AT$APP PARAM 1024, 38, 8, 8AT$APP PARAM 1024, 38, 16, 0AT$APP PARAM 1024, 38, 32, 32AT$APP PARAM 1024, 38, 64, 0AT$APP PARAM 1024, 38, 128, 128

Alternatively you could have used a single command of:

ATS158=170 ( i . e. 128+32+8+2)

4.2.2 Motion Sensor Input The LMU uses a 3 axis MEMs Accelerometer as its motion sensor input. This input can be used in one of three ways, first as a simple digital input where the input isin the high state if motion is detected, second it can be used as an additional check on thePEG Moving Trigger and lastly, it can be used for Tilt detection. The sensitivity of themotion sensor input is controlled by S-Registers 175 and 176.

These S-Registers are divided into 5 different settings:• S-175, Bits0-3: These bits define a threshold setting for the accelerometer. The

lower the setting, the higher the sensitivity. The lsb will depend on the settings of bit6 and 7. The lsb will be in mG (1 mG is 0.001 G (Gravity acceleration at earth'ssurface)

• S-175, Bits4-5: These bits define the High Pass filter setting (0=Filter Off, 1=2Hz,2=1Hz, 3=0.5Hz, 4=0.25Hz). Increasing the HPF frequency decrease the sensitivity.

This field uses a default value of 4 (0.25Hz).

8/18/2019 LMU Users Guide 2011-01-04

17/229

LMU Users Guide


• S-175, Bit 6: This bit defines the scale used by the threshold. When this bit is cleareda +/- 2.3g scale is used, if it is set then a +/- 9g scale is used.

• S-175, Bit 7: This bit is used to modify the scale of the threshold setting (i.e. S-175bits 0-3). When bit7 is set, an 8x multiplier is applied to the threshold value,otherwise a x1 scale is used.

• S-176: This register defines the sample duration used by the accelerometer with a10mS lsb. For example, the default value of 3 means a 30mS duration.

Threshold lsb values:Sensitivity Scale: +/- 2.3g +/-9g

Threshold Scale x1: 18mg 72mg Threshold Scale x8: 144mg 576mg

For example, the default value of 3 with Bit 6 cleared and Bit 7 set would produce athreshold of 56mg (3*2.3*8).

The LMU must be reset to apply the new S-register setting.

4.2.2.1 Accelerometer – Moving Filter To use the LMU’s accelerometer as a filter on the Moving PEG Trigger, bit4 of S-Register156 should be set. This will require that a positive motion detection from the accelerometerbefore PEG will declare the LMU as ‘Moving’. This check is in addition to the GPS speedexceeding the Moving Speed Threshold.

GPS speed is still the only discriminant for determining ‘Not Moving’.

4.2.2.2 Accelerometer - Tilt Detection The LMU-800™, LMU-900™, LMU-1150™, and LMU-1200™ support Tilt Detection. This feature is controlled by two S-Registers.

S-Register 160 determines motion detector sampling rate in 10mS increments. A value of 0set to this register disables tilt detection.

S-Register 161 defines tilt detection angle X in 98 * cos(X) units. Negative values use 256compliment i.e. -1 = 255,... -127 = 129. The table below shows registers values for somecommon tilt angles:

Tilt Angle Register 161 value

20 9240 7560 4980 1790 0100 239120 207140 181160 164

8/18/2019 LMU Users Guide 2011-01-04

18/229

LMU Users Guide


A PEG 'Special' Trigger with a modifier of 100 is generated when tilted over the configuredthreshold. The initial position from which the tilt angle is calculated is set after board resetor if tilt detection was not enabled, after enabling the tilt detection. The system retains theoriginal initial position after disabling and re-enabling tilt detection.

It is important to note that these S-Registers have a different meaning in other LMU types.Configurations created for the LMU-800™, LMU-900™, LMU-1150™, and LMU-1200™should therefore be considered to be incompatible with other LMU products.

4.2.2.3 Accelerometer – Impact Detection The LMU-2600™ application now supports the ability to detect and collect impacts (largeaccelerations) using its 3-axis MEMS accelerometer. In this implementation, the impactdetection feature uses some of the same resources used by the motion detector and somotion detection and impact detection are mutually exclusive. This will change in thefuture.

To configure the device for detecting impacts, S-Register 175 needs to be configured for theacceleration threshold. See above for how to configure S-Register 175.

When the acceleration exceeds the threshold, the device begins storing acceleration vectors(x, y, and z axis values) into an LM Direct Application message. Up to 472 vectors can bestored. When the Application message buffer is full or the accelerations drop below thethreshold for 1 second, the LMU posts a PEG Trigger ('Special' Trigger with Modifier equalto 0). The trigger can be used by the script to send the Application message to the serverusing the 'Send Special' PEG Action with a modifier of 5. A 5-second blackout is imposedto prevent further acceleration vector collection while the Application message is sent. GPS

Time-of-Fix, Latitude and Longitude are stored in the Application message at the beginningof the data collection. Refer to the LMDirect Reference Guide (v8.8.c.1 or later) for theformat of the Acceleration Report App Message.

4.2.3 Power State InputCertain LMU products can detect if they are using external power or if they are using theirinternal back-up battery. If they are using external power, this input will be in the Low state.If they have switched to the internal battery, then the input will register in the High state.

4.2.4 Battery Voltage Critical Input The LMU-11xx™ and LMU-1200™ have a built in low battery threshold of 3500mV, which

is tied to a discreet input. If the battery level is above the threshold, then the input is in theLow state. If the battery level is below the threshold, the input will be in the High state.

4.2.5 High Temperature Input The LMU-11™ and LMU-1200™ have a built in high temperature threshold of 60 °C. Ifthe internal temperature of the LMU is above this value, then the input will be in the Highstate. If the LMU’s temperature is below this value, then the input will be in the Low state.

8/18/2019 LMU Users Guide 2011-01-04

19/229

LMU Users Guide


4.2.6 The 1 Bit Bus The 1-Bit-Bus allows the LMU-4200™, LMU-4100™, LMU-2600™, LMU-2500™ andLMU-1190™ to be connected to a variety of 1-Wire® Devices. The LMU-4100™ supportsonly the iButton Driver ID products and where the other LMUs support both the iButtonDriver ID and Temperature Sensor products.

To connect an iButton DS9202 Probe to the LMU you would connect the Black wire toGround and connect the Grey wire to the 1-Bit Bus as shown below for the LMU-2500/2600™and LMU-4100™.

Figure 2 Sam ple 1 Bit Bus Wiring

On the LMU-4100™ and LMU-1190™, the 1-Bit Bus interface must be enabled by settingBit 0 of S-Register 171.

Enable 1-Bit Bus Input/ Disable Output 0:AT$APP PARAM 1024, 51, 1, 1

Disable 1-Bit Bus Input / Enable Output 0AT$APP PARAM 1024, 51, 1, 0

On the LMU-4200™, LMU-2600™, LMU-2500™ and LMU-1190™, you must select which device the LMU is using (i.e. iButton Driver ID tag or Temperature Sensor) on the 1-Bit Bus interface using Bit 6 of S-Register 171. The temperature sensor is enabled when Bit 6is set and the ID tag is enabled when Bit 6 is cleared.

Enable Temperature Sensors:AT$APP PARAM 1024, 51, 64, 64

Enable ID Tag

http://www.maxim-ic.com/products/1-wire/http://www.maxim-ic.com/products/1-wire/http://www.maxim-ic.com/products/1-wire/http://www.maxim-ic.com/products/1-wire/

8/18/2019 LMU Users Guide 2011-01-04

20/229

LMU Users Guide


AT$APP PARAM 1024, 51, 64, 0

When supported, the LMU™ can work with up to eight (reference 0-7) Maxim DS28EA001-wire temperature sensors in a chain configuration interconnected by a 3-wire bus. Uponboot-up, the LMU executes a discovery procedure to detect the number of connectedDS28EA00 devices. The LMU assigns each sensor a reference number starting with zero (0)for the sensor closest to the LMU in the sensor chain and incrementing for each sensordown the chain up to seven (7). During operation, the LMU sequentially polls each sensorfor its temperature reading; one sensor every 10 seconds. If all eight sensors are deployed,each sensor will be polled every 80 seconds. A poll involves commanding the sensor toperform the temperature conversion and 1-sec later reading the results of the conversion.

The LMU can also support the DS18B20 temperature sensor, but only in single sensormode.

4.2.7 Analog to Digital Inputs

The LMU’s Analog to Digital (ADC) Inputs are used to convert an analog signal into adiscrete voltage value. The meaning of the discrete voltage value will depend on the type ofdevice being used.

All of the LMU’s Analog to Digital inputs store values with a 1mV lsb. For example, if the Analog to Digital Input reads a 12000, it means the input signal was measured as 12.000V.

4.2.7.1 Voltage Monitors The Voltage Monitor ADCs are generally used to monitor the LMU’s supply voltage. The ADCs are read with a 1mV lsb. For example, a typical vehicle power supply reads as 13.8V while in operation. The corresponding voltage monitor ADC (typically ADC 0) would readas 13800mV.

4.2.7.2 GPS Antenna Monitor The GPS Antenna ADC (ADC2) on the LMU-2500™ and LMU-2600™ measures the voltage at the GPS Antenna to determine if a short or open circuit condition is present. The voltage reported is in mV and, in normal situations, should be between 2900mV and2960mV(i.e. 3VDC). If the voltage is below 2900mV, then the antenna is in a SHORTcircuit condition. If the voltage is above 2960, the antenna is in a OPEN circuit condition

The LMU-4200™ also offers this feature, but uses ADC7 instead of ADC2.

8/18/2019 LMU Users Guide 2011-01-04

21/229

LMU Users Guide


4.3

4.3.1 Relay Outputs

Output Types

The LMU’s outputs are designed to drive external relays. These outputs provide a high-current, open-collector driver that can sink up to 150 mA each. These drivers may be used todrive external relays that can then control vehicle functions such as door locks, fuel shut-off

valves, sirens and lights. If additional current is required to drive the relays, external circuitrycan be added to source the current. This diagram shows a typical relay connection to one ofthe LMU’s outputs.

Vehicle Power(+12VDC)

RelayCoil

RelayContacts

Relay

Ground

LMU

85

86 87

30

Output 0

Figure 3 Sample Re lay Outpu t Wir ing

4.3.2 External vs. Internal Power Switch This output allows the LMU to switch between power sources when certain conditions aremet (e.g. low power on the currently selected supply). If this output is set then the LMU willuse its internal battery as its power supply. If this output is cleared, the LMU will use theexternal power supply.

By default, this output is cleared so the LMU will operate off external power.

4.3.3 Enable / Disable Battery Charging This output allows the LMU to enable or disable the charging of its internal battery. If thisoutput is set then the LMU will stop charging the internal battery. If this output is clearedthe LMU will charge the internal battery.

By default, this output is cleared (i.e. battery charging enabled)

4.3.4 LED Outputs The LED outputs mirror the behavior of the Comm and GPS Status LEDs. These allow aninstaller to remote the LEDs from the LMU™ so they can be observed to verify an install.

8/18/2019 LMU Users Guide 2011-01-04

22/229

LMU Users Guide


4.4 Certain pins on the LMU can be used as either an Input or an Output. These lines aretypically referred to as GPIOs (Generic Purpose Input or Output). The input or outputfunctionality of a GPIO pin is controlled by S-Register 159. Like the input bias controls,each bit is associated with a different GPIO. If the bit is set, then the GPIO will act as anoutput. If the bit is cleared, the GPIO will act as an input. The following bit mappings areavailable:

Selecting the GPIO Function

Bit Input S-Register Mask0 GPIO 1 11 GPIO 2 2

For example to set GPIO 1 as an output and GPIO 2 as an input you would use:

AT$APP PARAM 1024, 39, 1, 1

AT$APP PARAM 1024, 39, 2, 0Or you could use the single command of

ATS157 = 1

8/18/2019 LMU Users Guide 2011-01-04

23/229

LMU Users Guide


4.5 For the most part, the LMU’s Sleep functions are controlled by PEG and thus, users shouldrefer to the PEG Programming Guide for a more detailed description. The features belowrelate specifically to the setup of the and generally do not change the operation of the PEGengine.

Working with Sleep Mode

4.5.1 Configuring the Input Wake-Up Monitor The LMU’s digital inputs have an additional feature besides simple On/Off detection whichis to wake the LMU out of its sleep mode. The LMU is capable of filtering which input(s)can wake it from sleep based on Parameter 1029. Like S-Registers 157 and 158, each bit ofParameter 1029 is associated with a specific input. If the bit associated with that input is set,then the LMU will wake up on any high to low or low to high transition of that input. If thebit is cleared, the LMU will ignore any transitions for that input and will remain sleeping.

A host device can also be used to wake the LMU from sleep via a wired serial connectionusing the Serial Cable, ioPOD or TetheredLocator adapters. The expansion port on theLMU-4200™ and LMU-4100™ must also be set NOT to power down to support thisfeature. The LMU cannot be woken using the Bluetooth Adapter.

The bit mappings for the Wake-Up Monitor are as follows:

Input Bit MaskIgnition/Input 0 0Input 1 1 2Input 2 2 4Input 3 3 8Input 4 4 16

Input 5 5 32Input 6 6 64Input 7 7 128

How the LMU enters sleep and how to monitor for wake up events is discussed in the PEGProgramming Guide. Please refer to that document for details.

8/18/2019 LMU Users Guide 2011-01-04

24/229

LMU Users Guide


4.5.1.1 Working with the LMU-4200™’s Input Wake Up Monitor The LMU-4200™ supports 2 indexes for the Input Wake Up Monitor (Parameter 1029) tosupport the ability to wake up from a Motion detection (eg Input 8). In this scheme, Index 0

of Parameter 1029 behaves as described above. Index 1 is used to enable the use of Input 8.In this case, the mapping would be as follows:

Input Index Bit MaskIgnition/Input 0 0 0 1Input 1 0 1 2Input 2 0 2 4Input 3 0 3 8Input 4 0 4 16Input 5 0 5 32Input 6 0 6 64Input 7 0 7 128Input 8 1 0 1

For example, to enable the use of Input 8 (LMU-4200™ Motion Sensor) you would use:

AT$APP PARAM 1029, 1, 1, 1

To disable it, you would use:

AT$APP PARAM 1029, 1, 1, 0

8/18/2019 LMU Users Guide 2011-01-04

25/229

LMU Users Guide


4.5.2 Keeping the Expansion Port powered during sleep The expansion port is the 16 pin connection on the back of the LMU-4200™ and LMU-4100™ where peripheral devices are plugged in. This port can actually remain powered whilethe LMU is sleeping. This would be done to allow any of the following:

• Keep Inputs and Outputs on the ioPOD in the High/Low or Set/Cleared states• Allow the LMU to wake up on inputs connected to the ioPOD• Allow the LMU to wake up based on host port activity

The power of the expansion port is controlled by bit 6 of S-Register 140. If this bit is set,then the expansion port remains powered while the LMU is sleeping. If this bit is cleared,the expansion port will be powered down when the LMU goes to sleep.

To keep the port powered on, you would use:

AT$APP PARAM 1024, 20, 64, 64

To power it off during sleep you would use:

AT$APP PARAM 1024, 20, 64, 0

Keep in mind that leaving the expansion port powered will increase the current draw of theLMU during sleep.

4.5.3 Keeping the Modem On during sleepIn some installations it may be desirable to be able to wake the LMU from sleep remotely.

The LMU can support this by being configured to leave its radio on while sleeping.

To enable this feature you need to set Bit 2 of S-Register 171.

Enable Radio-On Sleep ModeAT$APP PARAM 1024, 51, 2, 2

Disable Radio-On Sleep ModeAT$APP PARAM 1024, 51, 2, 0

In this mode, the LMU will wake when it receives any SMS message.Be advised that the LMU will draw noticeably more power using this sleep mode.

8/18/2019 LMU Users Guide 2011-01-04

26/229

LMU Users Guide


4.5.4 Restoring Output StatesIt is possible for the LMU to automatically restore its last known Output states after wakingfrom sleep. This feature is enabled by setting but 2 of S-Register 177.

AT$APP PARAM 1024, 59, 2, 2

To disable this feature you would use:

AT$APP PARAM 1024, 59, 2, 0

8/18/2019 LMU Users Guide 2011-01-04

27/229

LMU Users Guide


4.6 By default, the Status LEDs work as described in the Hardware and Installation Guides,however, it is possible to override the default behaviors on the LMU-2500™, LMU-2600™,LMU-4100™ and LMU-4200. Specifically, the Comm LED can be over-ridden to reportInput Status for inputs 0-4 and the GPS LED can be over-ridden to provide satelliteinformation.

Working with the Status LEDs

4.6.1 Input State and Satellite Count ModeIn this mode, the Comm LED (Orange) will alternate between Comm Status and InputStatus every 5s. The Comm Status behavior is described in the Install Guides. Whenreporting the Input states, it will blink with a single pulse when the input is low and twopulses when the input is high. After 500mS it reports the next input. The inputs are reportedsequentially starting with Input 0 and finishing with Input 4. For example, if Comm wasacquired, ignition (i.e. input 0) was on and all other inputs were low, you would see thefollowing pattern:

Figu re 4 Alternate Comm LE D Blink Pat tern

8/18/2019 LMU Users Guide 2011-01-04

28/229

LMU Users Guide


For the GPS LED (Yellow) the GPS LED will indicate OFF (LED off), ON (slow blink)and TIME-SYNC (fast blink) as it always has. When the GPS is acquired, it reports thenumber of satellites being tracked by going on for 500mS, off for 500mS and then for eachsatellite being tracked, on for 125mS and off for 125 mS. After 5-sec, the pattern repeats.:For example, an LMU tracking 6 satellites would have a blink pattern similar to thefollowing:

Figu re 5 Alternate GPS LED Blink Pat tern

This mode is enabled by setting bit 3 of S-Register 171.

AT$APP PARAM 1024, 51, 8, 8

To return the LEDs to their normal behavior, you would use:

AT$APP PARAM 1024, 51, 8, 0

4.6.2

Alternate LED Blink Code This mode also reports input status along with Comm and GPS Status.

The GPS LED will be off if the Ignition is off or if the LMU does not have a GPS fix.Otherwise, the GPS LED will report the number of satellites by blinking ‘n’ times after asingle long blink. (i.e. similar to the pattern described above).

The COMM LED behavior is a little more complicated. When the Ignition is off, the COMM LED will blink at a 1Hz rate (1 blink per second). When the Ignition is on but the LMU does not have Comm and no other inputs are ‘active’,the COMM LED will blink at a 4Hz rate (1 blink every ¼ of a second).

If the Ignition is on with no other inputs ‘active’ and the LMU does have Comm, theCOMM LED will be solid.If the Ignition is on and other inputs are 'active', the COMM LED will blink the number oftime corresponding to the first 'active' Input's designation followed by a pause and then thenumber of times corresponding to the next 'active' Input's designation.

An 'active' Input is one whose state does not match the corresponding bias setting in S-158.

8/18/2019 LMU Users Guide 2011-01-04

29/229

LMU Users Guide


For example, let us assume that all inputs are biased low. If Ignition is On, and Inputs 2 and4 are high then the COMM LED will blink twice, followed by a pause, followed by 4 moreblinks.

This mode is enabled by setting both Bits 3 and 5 of S-Register 171. To enable this mode, you would use:

AT$APP PARAM 1024, 51, 40, 40

To return the LEDs to their normal behavior, you would use:

AT$APP PARAM 1024, 51, 40, 0

4.6.3 Disabling the Status LEDsIn some installations it may be desirable to disable the status LEDs, for instance when theinstallation is covert and drivers/end users should not be able to easily locate the LMU.

Turning the status LEDs off is controlled by bit 3 of S-Register 140. If this bit is set, thenthe Comm and GPS LEDs are disabled and turned off. If this bit is cleared, then the Command GPS LEDs will behave as normal.

To disable the LEDs you would use:

AT$APP PARAM 1024, 20, 8, 8

To re-enable them, you would use:

AT$APP PARAM 1024, 20, 8, 0

8/18/2019 LMU Users Guide 2011-01-04

30/229

LMU Users Guide


4.7 The LMU is capable of storing some of its values to non-volatile memory so that they can berestored after a power cycle. The following values may be stored:

Restoring values through a power cycle

• The values of all 16 Accumulators• The states of all 16 PEG Flags• The state (inside or outside) of all 32 PEG Zones• Last known GPS position• The current value of the PEG State variable (see PEG Programming Guide for

details)

These values can optionally be saved at two points

• Before a soft reset (i.e. AT$APP QUIT AT Command or the Application RestartPEG Action)

• On ignition off

This feature is collectively known as an Environment Restore and is controlled by S-Register127. Bits 0-3 control which values are saved where each bit is associated to a specific value.If the bit is set, the associated value is saved. If it is cleared, the associated value is not saved.

The bit-mappings for bits 0-3 are as follows:

• Bit 0 = The values of all 16 Accumulators• Bit 1 = The states of all 16 PEG flags• Bit 2 = The state (inside or outside) of all 32 PEG Zones• Bit 3 = Last known GPS position

Bits 6 and 7 of S-Register 127 control when these values are saved. If bit 6 is set, then the values are saved on a soft reset. If bit 7 is set, then the values are saved on an ignition off.

For example to save all four values on just ignition off, you would use the followingcommands:

Save Accumulators:AT$APP PARAM 1024, 7, 1, 1

Save PEG flags:AT$APP PARAM 1024, 7, 2, 2

Save PEG Zones:AT$APP PARAM 1024, 7, 4, 4

Save the last known GPS position:AT$APP PARAM 1024, 7, 8, 8

8/18/2019 LMU Users Guide 2011-01-04

31/229

LMU Users Guide


Do no save on a soft reset:AT$APP PARAM 1024, 7, 64, 0

Save on ignition offAT$APP PARAM 1024, 7, 128, 128

8/18/2019 LMU Users Guide 2011-01-04

32/229

LMU Users Guide


5 While all of the LMU products have a host port to allow users to issue AT Commands toconfigure, debug and control the device, only the LMU-4100™, LMU-2600™, LMU-

2500™, LMU-1200™ and LMU-900™ supports external serial devices as a peripheral.

Working with External Serial Devices

The CalAmp LMU-4100™, LMU-2600™ and LMU-2500™ supports three external serialports for use with other devices, though only two can be available at the same time. Theserial ports are:

• The Host Port (LMU-4100™, LMU-2600™, LMU-2500™, LMU-1200™ andLMU-900™)

• The Modem Port (LMU-4100™)• The Aux Port(LMU-4100™ and LMU-2600™)

The LMU-1200™ and LMU-900™ only support the Host Port in AT Command Mode orMDT mode.

These ports are generally accessed through a specific accessory for the LMU. Please refer tothe CalAmp accessory guide for details.

The following sections describe how each of these ports can be used. Using serial ports viathe Bluetooth Adapter is described in its own section.

8/18/2019 LMU Users Guide 2011-01-04

33/229

LMU Users Guide


5.1 The Host Port of the LMU-4100™, LMU-2600™, LMU-2500™, LMU-1200™ and LMU-900™ can be accessed in one of two ways, either in Host mode, which is meant for use withlaptops, and PDAs or MDT mode, which is meant for use with serial mobile data terminals,bar-code readers, magnetic-card readers and other ‘dumb’ serial devices. In Host mode, ahost device can issue AT Commands, receive NMEA data or establish a Dial-UpNetworking session

Using the Host Port

2. In MDT 3

5.1.1 Host Mode - AT Command Setup

mode, the LMU will act as a message pass-thru for the dumbserial device. That is, it will send any messages it receives from the serial device to thebackend system and vice-versa via LM Direct User Messages.

To issue AT Commands to the LMU, you would need some measure of terminal programsuch as HyperTerminal. Instructions on how to set HyperTerminal up for use with theLMU™ can be found in the Appendix D of this document.

The default settings for the Host port are:

• 115200 BAUD• 8 Data Bits• No Parity• 1 Stop Bit

The only setting that can be changed is the BAUD rate. This can be done with one of two AT Commands:

AT+I PR=ATS148=

The Host port BAUD rate will change instantly after the AT+IPR command is issued. TheLMU™ must be reset for the BAUD rate to change after using the S148 command. Bothchanges are non-volatile and thus the BAUD rate will remain unchanged during subsequentpower cycles. The following BAUD rates are supported:

BAUD Rate S148 Value600 11200 22400 34800 49600 519200 728800 838400 957600 10

2 LMU-4200™ and LMU-4100™ only3 MDT stands for Mobile Data Terminal. This mode is also known as Generic Serial Device mode or GSD.The documentation uses both notations.

8/18/2019 LMU Users Guide 2011-01-04

34/229

LMU Users Guide


76800 11115200 12Default 255

Please note that the LMU-2600™ and LMU-2500™ do not support 300 BAUD. The LMU-

4100™ does not support 300, 600, 1200, 2400, 14400, 28800 or 76800 BAUD.DO NOT use values that are not on this list as it may cause unexpected behaviors within theLMU. It is also very important to make sure your Host device supports the selected BAUDrate before making any changes to the LMU.

Changing the BAUD rate setting will have an effect on the NMEA output and the Dial-UpNetworking functions of the Host Port.

5.1.2 Host Mode – NMEA OutputNMEA messages are generally used by in-vehicle navigation applications to plot the current

position of the vehicle and compute real-time driving directions. The LMU can outputseveral NMEA sentences over its Host Port to support these applications. The availablesentences are:

• GGA (GPS Fix Data)• GLL (Geographic Position, Latitude / Longitude)• GSA (GNSS4• GSV (GNSS Satellites in View)

DOP and Active Satellites)

• RMC (Recommended Minimum Specific GNSS Data)• VTG (Course Over Ground and Ground Speed)• ZDA (Date and Time)• UBX,00 (uBlox Proprietary Lat/Long Position Message)

Please refer to your application’s documentation as to which messages it needs to operateproperly.

S-Register 128 is used to control which messages are sent to the serial port. Each message isassociated with a specific bit of this register. If the bit is set, then the message will be sent tothe host port. If the bit is cleared the message will not be sent. The bit mapping of S-128 isas follows:

• Bit 0 – Enable/Disable GGA Message• Bit 1 – Enable/Disable GLL Message• Bit 2 – Enable/Disable GSA Message• Bit 3 – Enable/Disable GSV Message• Bit 4 – Enable/Disable RMC Message• Bit 5 – Enable/Disable VTG Message

4 Global Navigation Satellite System, which could refer to GPS, GLONASS, Galileo, etc…

8/18/2019 LMU Users Guide 2011-01-04

35/229

LMU Users Guide


• Bit 6 – Enable/Disable ZDA Message• Bit 7 – Enable/Disable UBX,00 Message

For example, to enable the GGA and RMC messages you could use:

ATS128=17

Alternatively you could use two Parameter commands:

Turn on GGAAT$APP PARAM 1024, 8, 1, 1

Turn on RMCAT$APP PARAM 1024, 8, 16, 16

For the LMU-2500™, 2600™, 4100™ and 4200™ users can alter the update rate between1Hz and 4 Hz by setting or clearing bit 7 of S139. For example, to set the LMU to a 4Hzupdate rate, you would use:

AT$APP PARAM 1024, 19, 128, 128

To return the LMU to a 1Hz GPS update rate, you would use:AT$APP PARAM 1024, 19, 128, 0

5.1.3 Host Mode – Dial-Up Networking The LMU-4200™’s and LMU-4100’s™ Host Port can be used by a laptop or PDA toestablish a Dial-Up Networking session. This is to allow the laptop or PDA access to theInternet to enable such applications as email and web-browsing.

There are two basic steps to accomplish this:

1. Install a modem driver2. Create the Dial-Up Networking session

The details on each of these steps are described in the Adding a Modem Driver and Creatinga Dial-Up Networking Session Appendixes of this document.

Depending on the wireless networking technology employed by the LMU, there are severalother steps you should take to ensure uninterrupted operation.

5.1.3.1 Disable Connection Monitoring The Connection Monitor is used by the LMU to ensure that the data session with the wireless modem is still valid. In some cases, this may reduce the stability of Dial-UpNetworking session. The connection monitor is controlled by two S-Registers, 152 and 154.S-Register 152 should be set to 0 and for S-Register 154 bit 2 should be cleared and bit 3should be set. The two commands you would use to accomplish this are:

8/18/2019 LMU Users Guide 2011-01-04

36/229

LMU Users Guide


ATS152=0AT$APP PARAM 1024, 34, 12, 8 5

Please note that the connection monitor is described in detail later in this document.

5.1.3.2 Disable Network Status QueriesFor the Kyocera based CDMA LMU-4100™ it is advisable to disable any KMIP 6

polling, asany missed KMIP messages may cause the LMU to reset the modem. A modem reset wouldthen cause the Dial-Up Networking session to be torn down. KMIP polling is controlled byS-Register 153. To disable KMIP polling you would use:

ATS153=0

To re-enable KMIP polling you would use:

ATS153=10

KMIP Polling is described in detail later in this document.

5 One question that may arise is why not use ATS154=8 instead of the PARAM command. The basicanswer is so that we do not interfere or change any settings we do not absolutely need to. We will makeheavy use of parameter bit masking through-out this document for that reason.6 KMIP is a protocol the LMU-4100™ uses to talk to the Kyocera M200 CDMA modem. It is used to pullmodem information such as carrier id and RSSI.

8/18/2019 LMU Users Guide 2011-01-04

37/229

LMU Users Guide


5.1.4 MDT ModeMDT Mode allows a dumb serial device to pass messages through the LMU-4100™, LMU-2600™, LMU-2500™, LMU-1200™ and LMU-900™ to the back-end system using LMDirect User Messages. The backend system may also send a User Message to the LMU, thecontents of which should be forwarded to the serial device.

For the LMU-4100™ MDT mode can be enabled on either the Serial Adapter peripheral oron the ioPOD peripheral by means of a jumper.

The Host Port’s MDT mode settings are controlled by S-Registers 130 thru 138 and S-Register 141. Please note that S141 is not supported by the LMU-1200™ or LMU-900™

5.1.4.1 MDT Sub-Modes – LMU-4100™ The Host Port’s MDT mode supports two sub-modes, Generic Serial Device Mode andLong Message Mode.

In Generic Serial Device mode, the LMU- will accept only single messages from the genericserial device that are up to 804 bytes or 64 bytes in length depending on which LMU is used.

The LMU-1200™ and LMU-900™ only support 64 byte messages. The other LMU’ssupport the longer 804 bytes. Any excess data received will be truncated. The LMU willpackage all bytes in a single user message.

In Long Message Mode, the LMU will break-up messages longer than 804 into multiple UserMessages. Each User Message will contain up to 804 bytes of data. It is up to the receivingapplication (i.e. the backend) to re-assemble the original message from each of the usermessages.

In either mode, the backend system can only send messages to the LMU of 848 bytes or less.

Which mode is in use is controlled by S-Register 130. A value of 1 enables Generic-SerialDevice Mode and a value of 2 enables Long Message Mode. All other values are undefinedand should not be used. That is, to enable Generic Serial Device mode you would use:

ATS130=1

To enable long message mode you would use:

ATS130=2

8/18/2019 LMU Users Guide 2011-01-04

38/229

LMU Users Guide


5.1.4.2 MDT Modes – LMU-900™, LMU-1200™, LMU-2500™ andLMU-2600™

The LMU-900™, LMU-1200™, LMU-2500™ and LMU-2600™ only support the Generic

Serial Device mode. This mode is enabled by setting S-Register 130 to 129. In this mode theLMU will be in Host Port mode for the first 30s after power up. After that, the LMU-switches to Generic Serial Device mode. After a wake-up, the LMU immediately entersGeneric Serial Device mode.

To enable Generic Serial Device mode on the LMU-900™, 1200™, 2500™ and 2600™,you would use:

ATS130=129

To disable this mode, you would use:

ATS130=0

5.1.4.3 MDT Mode – Serial Port settings The MDT Mode serial port settings are independent from the Host Port Host Modesettings. The MDT mode settings are controlled by 2 S-Registers, 131 and 132. Theseregister control the BAUD Rate, Data Bits, Parity and Stop Bits settings for MDT mode.

These changes do not affect the settings of S-148 or the +IPR command (i.e. the host portbaud rate).

The MDT mode BAUD Rate is controlled by S-Register 131 and supports the followingdata rates:

• 300 BAUD (ATS131=0)• 600 BAUD (ATS131=1)• 1200 BAUD (ATS131=2• 2400 BAUD (ATS131=3)• 4800 BAUD (ATS131=4)• 9600 BAUD (ATS131=5)• 14400 BAUD (ATS131=6)• 19200 BAUD (ATS131=7)• 28800 BAUD(ATS131=8)• 38400 BAUD (ATS131=9)• 57600 BAUD (ATS131=10)• 76800 BAUD (ATS131=11)• 115200 BAUD (ATS131=12)

Please note that the LMU-2600™ and LMU-2500™ do not support 300 BAUD. The LMU-4100™ does not support 300, 600, 1200, 2400, 14400, 28800 or 76800 BAUD.

8/18/2019 LMU Users Guide 2011-01-04

39/229

LMU Users Guide


To change the Data Bits, Parity and Stop Bit settings, you would use S-Register 132. Thefollow table describes each of the available combinations:

Data Bits Parit y Stop Bits S-132 Settin g8 None 2 7

8 None 1 38 Even 2 318 Even 1 278 Odd 2 158 Odd 1 117 None 2 67 None 1 47 Even 2 307 Even 1 267 Odd 2 147 Odd 1 106 None 2 56 None 1 16 Even 2 296 Even 1 256 Odd 2 136 Odd 1 95 None 2 45 None 1 05 Even 2 285 Even 1 245 Odd 2 125 Odd 1 8

5.1.4.4 MDT Mode – Termination Character The LMU can optionally detect a ‘Termination Character’ in the data sent from the serial

device over the MDT port. This character is meant to denote the end of the message andthat LMU should send the contents to the back-end system.

The Termination Character is meant for use when the serial device is sending ASCIIencoded text. When using serial devices that produce binary messages, it is best not to use a

Termination Character.

Two S-Registers control the Termination Character, one to enable it (S-133) and one todefine it (S-134).

To enable use of a Termination Character, you would need to set bit 2 of S-133. This is doneas follows:

AT$APP PARAM 1024, 13, 4, 4

To disable the Termination Character, you would clear bit 2 using:

AT$APP PARAM 1024, 13, 4, 0

8/18/2019 LMU Users Guide 2011-01-04

40/229

LMU Users Guide


The Termination Character to use is defined in S-134. S-134 is set to the decimal ASCII value of the desired character. For instance, to use a Carriage Return, you would set S-134 to13. That is:

ATS134=13

An ASCII chart can be found in Appendix C of this document.

5.1.4.5 MDT Mode – Message Termination Length As an alternative to using a Termination Character, the LMU can be configured to send UserMessages based on the amount of data it receives from the serial device. That is, the LMU

will buffer a certain number of bytes and once it reaches the limit it will package the entirebuffer into a User Message and send it to the back-end system. The size limit of the buffer isdefined by S-Register 135. The value of S-135 is scaled in 4 byte increments up to amaximum 804 bytes. The range of S-135 is therefore 1-201. For instance, to package 200byte User Messages you would use:

ATS135=50

By setting the value of S-135 to 0 disables the termination length feature.

5.1.4.6 MDT Mode – Message Termination Timeout The last option to define when to build a User Message is the Termination Timeout. In thiscase, the LMU will collect data from the serial device for a specific period of time. Whenthat time has elapsed, the LMU will package the data into a User Message and send it to theback-end system. Please note that the LMU will still obey its maximum buffer size (804bytes) even if the Termination Length is undefined.

The Termination Timeout is controlled by S-Register 138 and ranges from 1 to 255ms.For instance, to set the timeout for 120ms you would use:

ATS138=120

Like the Termination Length, setting S-register 138 to 0 will disable the Termination Timeout feature.

5.1.4.7 MDT Mode – User Message ID The User Message ID field serves two purposes for User Messages. First, the LMU will tagany inbound (LMU to server) User Messages with the defined Message ID. This will appearin the User Message ID field of the LM Direct packet. The second function is to act as afilter on any outbound (server to LMU) User Messages. If the outbound User Message doesnot have the same ID as the LMU, then the contents of the User Message will not be sent tothe serial device. The Message Received PEG Trigger however, will work regardless ofmatching User Message IDs.

8/18/2019 LMU Users Guide 2011-01-04

41/229

LMU Users Guide


The Message ID can range from 0 to 255 and is defined in S-Register 136. For instance, todefine a User Message ID of 4, you would use:

ATS136=4

This feature is always enabled, so it is very important to co-ordinate this setting with whoever is responsible for your LM-Direct implementation.

5.1.4.8 MDT Mode – Message Disposition The message disposition defines how the LMU’s log will handle the User Messages. Thereare six options:

• Attempt to send the User Message immediately. The message will be logged if thesend fails or if the log is already active.

• Immediately log the User Message•

Immediately send the User Message using the Unacknowledged service and place acopy in the LMU’s log. (i.e. Priority Message)• Send the User Message using the Unacknowledged service (i.e. message is never

logged)• Route the User Message (contents only) to the SMS Destination Address• Route the User Message (contents only) to the last phone number of an incoming

SMS message

With the last two options the contents of any incoming SMS messages will be routed to theserial device.

The message disposition is controlled by S-Register 137. The settings are as follows:• 1 or 2 = Send Message, Log if Send Fails• 3 = Log Message• 4 =

Documents

LMU Users Guide 2011-01-04