LMUand Tethered Locator User Guide

Version 5.
0k Released March 2003
Page 1
Copyright TechnoCom Corp 2003 TechnoCom Proprietary and Confidential
INTRODUCTION _________________________________________________________________ 7 ABOUT THIS MANUAL ________________________________________________________________ 7 Revision History__________________________________________________________________ 8 ABOUT THE READER _________________________________________________________________ 8 ABOUT TECHNOCOM _________________________________________________________________ 9 SECTION 1: SYSTEM OVERVIEW _________________________________________________ 10 OVERVIEW________________________________________________________________________ 10 COMPONENT DESCRIPTIONS __________________________________________________________ 11 WIRELESS DATA PRIMER_____________________________________________________________ 13 Cellular Digital Packet Data _______________________________________________________ 13 Mobitex _______________________________________________________________________ 13 iDen __________________________________________________________________________ 15 SMS __________________________________________________________________________ 15 GPRS _________________________________________________________________________ 15 CMDA 1xRTT __________________________________________________________________ 16 Point to Multi-Point ______________________________________________________________ 16 SECTION 2: HARDWARE OVERVIEW _____________________________________________ 17 LOCATION MESSAGING UNIT (LMU) ___________________________________________________ 17 Environmental Specifications ______________________________________________________ 17 Physical Specifications ___________________________________________________________ 18 37 Pin Connector ________________________________________________________________ 19 Standard Wiring Harness _________________________________________________________ 20 GPS Receiver ___________________________________________________________________ 20 Available Radio Interfaces_________________________________________________________ 20 RF Connector___________________________________________________________________ 20 Speaker _______________________________________________________________________ 20 TETHEREDLOCATOR ________________________________________________________________ 21 Environmental Specifications ______________________________________________________ 21 Physical Specifications ___________________________________________________________ 22 37 Pin Connector ________________________________________________________________ 23 Standard Wiring Harness _________________________________________________________ 24 GPS Receiver ___________________________________________________________________ 24 Certified Wireless Devices _________________________________________________________ 24 3WATT LMU______________________________________________________________________ 25 Environmental Specifications ______________________________________________________ 25 Physical Specifications ___________________________________________________________ 25 37 Pin Connector ________________________________________________________________ 26 Standard Harness _______________________________________________________________ 27 GPS Receiver ___________________________________________________________________ 27 Available Radio Interfaces_________________________________________________________ 27 I/O DESCRIPTIONS __________________________________________________________________ 28 Outputs________________________________________________________________________ 28 Ignition and Inputs_______________________________________________________________ 28 Expanded Inputs ________________________________________________________________ 29 Analog to Digital Converter - External _______________________________________________ 30 Analog to Digital Converter Internal _______________________________________________ 30 Status LEDs ____________________________________________________________________ 30 SECTION 3: INSTALLATION _____________________________________________________ 31 INSTALLATION NOTES: ______________________________________________________________ 31 QUICK START GUIDES _______________________________________________________________ 33 QUICK START: CDPD LMU ______________________________________________________ 33
Page 2
QUICK START: QUICK START: QUICK START: QUICK START:
Mobitex LMU _____________________________________________________ 35 GPRS LMU ______________________________________________________ 37 Point To Multi-Point (PMP) LMU _____________________________________ 39 TetheredLocator___________________________________________________ 41
SECTION 4: UNIT CONFIGURATION _____________________________________________ 43 WORKING WITH HOST DEVICES _______________________________________________________ 43 More on GSD (Generic Serial Device) and Long Message Mode ___________________________ 46 REPORTING CONFIGURATION _________________________________________________________ 47 Inbound Routing ________________________________________________________________ 47 LM Exchange Access _____________________________________________________________ 48 Host Access ____________________________________________________________________ 49 Event Report Contents ____________________________________________________________ 49 Accumulator Count Look Up Table __________________________________________________ 50 Retry Scheduling ________________________________________________________________ 50 Enabling Event Reporting _________________________________________________________ 50 NETWORK CONFIGURATION __________________________________________________________ 51 Side Preference (CDPD only) ______________________________________________________ 51 Network Discriminants ___________________________________________________________ 51 Network Sleep (CDPD) ___________________________________________________________ 52 NEI Cycling ____________________________________________________________________ 52 GPS CONFIGURATION _______________________________________________________________ 53 Local LMU Time. ________________________________________________________________ 53 GPS Lost and Last Know Delay. ____________________________________________________ 53 SECTION 5 PEG OVERVIEW______________________________________________________ 54 PEG SETTINGS (A.K.A. TRIGGER PARAMETERS) ___________________________________________ 54 Moving Speed Threshold __________________________________________________________ 54 Wake Up Monitor________________________________________________________________ 54 Timer Timeouts _________________________________________________________________ 55 Time-of-Day ____________________________________________________________________ 55 Time-Distance __________________________________________________________________ 55 Input Trigger Controls____________________________________________________________ 56 Acc Max Counts _________________________________________________________________ 57 Speed Trig Controls ______________________________________________________________ 57 Input Equates ___________________________________________________________________ 57 Day Of Week. ___________________________________________________________________ 58 Zone Definitions_________________________________________________________________ 58 A/D Thresholds _________________________________________________________________ 59 PEG TRIGGERS ____________________________________________________________________ 60 Not Active______________________________________________________________________ 60 Power Up ______________________________________________________________________ 60 Wake UP ______________________________________________________________________ 60 Power Up or Wake Up____________________________________________________________ 60 Input High _____________________________________________________________________ 61 Input Low ______________________________________________________________________ 61 Input Equate____________________________________________________________________ 61 Speed Above____________________________________________________________________ 61 Speed Below____________________________________________________________________ 62 Zone Entry _____________________________________________________________________ 62 Zone Exit ______________________________________________________________________ 62 GPS Acquired __________________________________________________________________ 62 GPS Lost ______________________________________________________________________ 63 Comm Acquired _________________________________________________________________ 63 Comm Lost _____________________________________________________________________ 63 Ignition On_____________________________________________________________________ 63
Page 3
Ignition Off_____________________________________________________________________ 63 Time-Distance Update ____________________________________________________________ 64 Timer Timeout __________________________________________________________________ 64 Count Exceeded _________________________________________________________________ 64 Time Of Day____________________________________________________________________ 64 Log Buffer Full__________________________________________________________________ 65 Host Data______________________________________________________________________ 65 Log Send Failure ________________________________________________________________ 65 Wake-Up on I/O _________________________________________________________________ 65 Wake-Up on Sleep Timeout ________________________________________________________ 65 Message Sent ___________________________________________________________________ 66 Message Acknowledged ___________________________________________________________ 66 Message Send Failure ____________________________________________________________ 66 Log Report Success ______________________________________________________________ 66 Comm Shutdown ________________________________________________________________ 67 Input Transition _________________________________________________________________ 67 Any Zone Entry _________________________________________________________________ 67 Any Zone Exit___________________________________________________________________ 67 Time Elapsed ___________________________________________________________________ 68 Distance Traveled _______________________________________________________________ 68 Log Active _____________________________________________________________________ 68 Message Received _______________________________________________________________ 68 Any Message Received____________________________________________________________ 69 Environment Change _____________________________________________________________ 69 Heading Change ________________________________________________________________ 69 Special ________________________________________________________________________ 70 Moving ________________________________________________________________________ 70 Not Moving ____________________________________________________________________ 70 A/D Above _____________________________________________________________________ 70 A/D Below _____________________________________________________________________ 70 Comm Connected ________________________________________________________________ 71 Acc Below _____________________________________________________________________ 71 Any Trig _______________________________________________________________________ 71 PEG CONDITIONS __________________________________________________________________ 72 None__________________________________________________________________________ 72 Ignition On_____________________________________________________________________ 72 Ignition Off_____________________________________________________________________ 72 Moving ________________________________________________________________________ 72 Comm Available_________________________________________________________________ 72 Comm Not Available _____________________________________________________________ 73 GPS Acquired __________________________________________________________________ 73 GPS Not Acquired _______________________________________________________________ 73 Input High _____________________________________________________________________ 73 Input Low ______________________________________________________________________ 73 Timer Active____________________________________________________________________ 73 Timer Inactive __________________________________________________________________ 73 Time-Distance Active _____________________________________________________________ 74 Time-Distance Inactive ___________________________________________________________ 74 Day of Week ____________________________________________________________________ 74 Flag Set _______________________________________________________________________ 74 Flag Cleared ___________________________________________________________________ 74 Log Active _____________________________________________________________________ 74 Comm and GPS Available _________________________________________________________ 74 Environment____________________________________________________________________ 75 Environment Equate______________________________________________________________ 75 Inside Time Of Day Window _______________________________________________________ 75
Page 4
Outside Time OF Day Window _____________________________________________________ 76 PEG ACTIONS _____________________________________________________________________ 77 None__________________________________________________________________________ 77 Send Report ____________________________________________________________________ 77 Log Report _____________________________________________________________________ 77 Send-Log Report ________________________________________________________________ 77 Send Log ______________________________________________________________________ 78 Clear Log ______________________________________________________________________ 78 Stop Time-Distance ______________________________________________________________ 78 Start Time-Distance ______________________________________________________________ 78 Set Output _____________________________________________________________________ 78 Clear Output ___________________________________________________________________ 78 Blink 1Hz Output ________________________________________________________________ 79 Blink 4Hz Output ________________________________________________________________ 79 Start-Restart Timer ______________________________________________________________ 79 Stop-Pause Timer________________________________________________________________ 79 Start Resume Timer ______________________________________________________________ 79 Clear Timer ____________________________________________________________________ 79 One-shot Timer _________________________________________________________________ 80 Increment Accumulator ___________________________________________________________ 80 Clear Accumulator_______________________________________________________________ 80 Power UP GPS _________________________________________________________________ 80 Sleep Timer ____________________________________________________________________ 80 Sleep Enable ___________________________________________________________________ 81 Sleep Until Time of Day___________________________________________________________ 81 Output Word ___________________________________________________________________ 81 Start Time Accumulator ___________________________________________________________ 81 Start Distance Accumulator ________________________________________________________ 81 Stop Accumulator________________________________________________________________ 82 Stop Clear Accumulator___________________________________________________________ 82 Stop-Clear Timer ________________________________________________________________ 82 Set Flag _______________________________________________________________________ 82 Clear Flag _____________________________________________________________________ 82 Send Accumulator Report _________________________________________________________ 82 Log Accumulator Report __________________________________________________________ 82 Send-Log Accumulator Report______________________________________________________ 83 Display Position_________________________________________________________________ 83 Connect Comm__________________________________________________________________ 83 Disconnect Comm _______________________________________________________________ 83 Save Environment _______________________________________________________________ 83 Report Alert ____________________________________________________________________ 84 Send Special____________________________________________________________________ 84 Move A/D to Accumulator _________________________________________________________ 84 Send Log Status _________________________________________________________________ 84 Send Unacknowledged Report ______________________________________________________ 84 Send TAIP Report _______________________________________________________________ 84 Accumulator Start Max Speed ______________________________________________________ 85 Accumulator, Start A/D ___________________________________________________________ 85 Accumulator, Decrement __________________________________________________________ 85 Send Maintenance Report _________________________________________________________ 85 Jump__________________________________________________________________________ 85 Call __________________________________________________________________________ 85 Return ________________________________________________________________________ 86 End___________________________________________________________________________ 86 PEG SCRIPTING ____________________________________________________________________ 87 PEG Example 1 _________________________________________________________________ 87
Page 5
PEG Example 2 _________________________________________________________________ 90 PEG Example 3 _________________________________________________________________ 92 SECTION 6: TAIP INTERFACE ____________________________________________________ 97 OVERVIEW________________________________________________________________________ 97 MODES OF OPERATION ______________________________________________________________ 97 Standard Reporting ______________________________________________________________ 97 Directed Reporting_______________________________________________________________ 97 PAD Mode Reporting_____________________________________________________________ 98 MEANS OF REPORTING ______________________________________________________________ 98 SUPPORTED MESSAGE TYPES _________________________________________________________ 98 Position Velocity (PV) ____________________________________________________________ 98 Long Navigation (LN) ____________________________________________________________ 99 Input and Output (IO) ____________________________________________________________ 99 Message Options _______________________________________________________________ 100 TAIP Qualifiers ________________________________________________________________ 100 USING TAIP ____________________________________________________________________ 101 APPENDIX A: HYPERTERMINAL CONFIGURATION ______________________________ 102 APPENDIX B: INSTALL NEW MODEM ___________________________________________ 104 APPENDIX C: CONFIGURING DIAL-UP NETWORKING ____________________________ 106 Create a New Connection ________________________________________________________ 106 Configure the Connection ________________________________________________________ 107 CONNECTING TO LMU _____________________________________________________________ 109 APPENDIX D: LMU MESSAGE SIZING GUIDE_____________________________________ 110 BASIC EVENT REPORT MESSAGE SIZING ______________________________________________ 110 APPENDIX E: MOUNTING TEMPLATE ___________________________________________ 112 APPENDIX F: AT COMMAND SET________________________________________________ 113 APPLICATION COMMANDS ___________________________________________________________ 113 SYSTEM COMMANDS _______________________________________________________________ 159
Page 6
Introduction
Welcome to the LMU and TetheredLocator Users Manual. This manual is intended to give you detailed information on the usage and operation of the LMU and TetheredLocator location products. This includes hardware descriptions, environmental specifications, wireless network overviews, and programming. The appendices include information on Dial-up Networking, HyperTerminal, Message Sizing, a Mounting Template and a complete AT Command Set.
About This Manual

The LMU and TetheredLocator are two of the most flexible AVL hardware products available. In order to accurately describe the functionality of these units we have broken this manual into the following sections: ! SECTION 1: System Overview. Here we go into a description of a TechnoCom based AVL system. We describe the roles and responsibilities of each of the TechnoCom components as well as providing a brief primer on each of the wireless data technologies used by the LMU and TetheredLocator. ! SECTION 2: Hardware Overview. This section describes the physical characteristics and interfaces to the LMU and TetheredLocator, including radio options for each unit. ! SECTION 3: Installation. In his section we give you quick start guides for each version of the LMU. These describe how to get the LMU and TetheredLocator reporting information as quickly as possible. . ! SECTION 4: Unit Configuration. This section is a description of all the configuration options available in the LMU and TetheredLocator. ! SECTION 5: PEG Overview. This is a description of the Programmable Event Generator. It includes descriptions of each trigger, condition and action as well as giving several scripting examples. ! SECTION 6: TAIP Overview. This is a description of the TAIP interface to the LMU and TetheredLocator. Please be aware that this section assumes some understanding of TAIP..
Page 7
Revision History Version 4.1f 4.2a 4.3 Date 29/01/02 11/02/02 03/06/02 Author STP STP STP Description Re-write. Added 4,2a features and commands Added GPRS H/W Specs Added SMS into primer Removed Notes on Version Info Added GPRS Software features Updated AT Command specs Updated Trigger and Action lists Added PMP-LMU Specs Updated A/D LSB value Updated for 5.0c and d code release Removed LM STAT section Updated About TechnoCom Updated for 5.0k additions Updated TAIP Interface Section
5.0b
29/11/02
STP
5.0d
11/12/02 01/17/03
STP STP
5.0k
03/13/03
STP
About The Reader

In order to limit the size and scope of this manual we have made some assumptions about you, the reader. ! You are familiar with IP networking concepts such as ports, and IP addresses. ! You are familiar with GPS concepts and terminology. ! You know you to query and set values into and LMU and TetheredLocator using LMU Manager. ! You have a basic understanding of TAIP (Please see http://www.trimble.com for further details on TAIP.) ! You have some experience with installing equipment in vehicles.
Page 8
About TechnoCom
Founded in 1995 and headquartered in Los Angeles, TechnoCom Corporation provides the software, systems and services that enable our customers to implement, optimize and manage wireless location systems. Seven of the top ten carriers are TechnoCom customers. TechnoCom offers two location enabling software platforms. InterOps Safeguard Platform, a modular software-based Location Support System (LSS), is the industrys first Operational Support System designed to meet the special challenges of managing wireless location systems. TechnoComs Location Exchange Platform provides intelligent locationbased middleware that allows applications to utilize a variety of wireless networks, protocols and multi-vendor location technologies
Page 9
Section 1: System Overview

Overview
The entire purpose behind an AVL system is to be able to remotely contact a vehicle, find out its location or status, and then do something useful with that information. This could include displaying the vehicle location on a map, performing an address looking, providing real-time directions, update the vehicles ETA, monitor vehicle and driver status, or dispatch the vehicle to its next pick up. These functions, of course, are completely dependant on what your application is capable of doing. The role of the TechnoCom components is to deliver the information you are looking for when and where you want it. On average, an AVL system, based on TechnoCom devices could include the following components: ! ! ! ! ! ! ! Backend software.(e.g. mapping, dispatch, etc) LMU Manager An LM Exchange server A wireless data network An LMU or TetheredLocator with a wireless data modem or phone. MDT Laptop running LMU Status
Internet / Wireless Network LMU Manager
Mapping Application
LM Exchange Server
Network Base Station
TetheredLocator Wireless PDA MDT
LMU
Laptop
Page 10
Component Descriptions
Backend Software This is your software application. Regardless of its function, be it mapping, dispatch or otherwise, as far as the TechnoCom system is concern, its primary goal is to talk to the LM Exchange server. This allows your application to do any of the following: ! Receive real-time location reports from the LMU or TetheredLocator in a variety of formats. ! Receive logged information from the LMU or TetheredLocator ! Request location updates from LMUs and TetheredLocators ! Update and change the configuration of the LMU or TetheredLocator LMU Manager LMU Manager is the primary support and configuration tool in the TechnoCom system. It allows access to almost every feature available in the TetheredLocator and LMU. Unlike the Backend Software, it has the option of talking directly to and LMU or making request through LM Exchange. For further details on using LMU Manager please refer to the LMU Manager Users Guide. LM Exchange LM Exchange is our middleware application that provides a quick and easy means of integrating the LMU and TetheredLocator into your existing AVL applications. It provides you with one uniform interface and the complete feature set necessary to monitor, control and configure TechnoComs in-vehicle products. The core of LM Exchange is a Win32 communication library that handles all data transfers to and from the LMU and TetheredLocator, thus providing location and event reporting, messaging, unit configuration, and unit monitoring. Your primary interface to LM Exchange is via XML scripting over a TCP/IP connection. Please see the LM Exchange Users Guide for complete details.
Page 11
Wireless Data Network The Wireless Data Network provides the information bridge between the LM Exchange server and the LMUs and TetheredLocators. Wireless data networks can take a verity of forms, such as cellular networks, satellite systems or local area networks. As of this point in time the networks available to LMU and TetheredLocator are: ! Cellular Digital Packet Data (CDPD) ! Mobitex (LMU Only) ! iDen (TetheredLocator Only) ! GPRS (General Packet Radio Services) ! PMP (Point To Multi-Point) LMU and TetheredLocator The LMU and TetheredLocator are responsible for delivering the location and status information when and where it is needed. Data requests can come from any of the following sources: ! PEG Script within the LMU or TetheredLocator ! A location or status request from LM Exchange ! A location request or status from LMU Manager ! A request made from a host device such as a laptop, PDA or MDT Host Device Laptop/PDA or MDT In some cases it is necessary to run an application in the vehicle while it is being tracked by the Backend software. Such examples could include instant messaging between vehicles or a central office, in vehicle mapping or driving directions, email, or database access. In most of these cases you will be using the LMU and TetheredLocator as a modem as well as an AVL unit. This will be discussed in further detail in Unit Configuration section.
Page 12
Wireless Data Primer

This section is meant to give an overview of the wireless data technologies employed by the TechnoCom location products. Cellular Digital Packet Data Cellular Digital Packet Data (CDPD) provides wireless access to the Internet and other public packet-switched networks over the existing cellular phone systems. This includes AMPS, TDMA and CDMA networks operating in the 800 MHz band. CDPD is the original wireless IP packet data standard, its definition was started in 1992 and the first commercial service was launched in 1995. CDPD has matured into a widely available, stable wireless IP service. It has extensive coverage in the USA, Canada, Mexico, Brazil, New Zealand, Israel, China, and other locations. CDPDs always on connection to the Internet gives the user instant access to their data. CDPD service pricing plans are usually based on data transferred or as a flat rate rather than the time connected, so the costs are reasonable. CDPD communications are secure thanks to the encryption used and channel hopping, which make it extremely difficult to intercept and interpret a transmission. CDPD packets use forward error correction to reduce the effects of noise and RF interference on the data transmission. CDPD also supports IPv6. CDPD service has a data rate of 19.2 kbps, however some of this capacity is used for error correction and system overhead. The users data throughput will vary but often will be in the range of 10 kbps to 15 kbps. 1 Further information on CDPD can be found at the CTIA website http:\\www.wow-com.com Mobitex Mobitex is in some respects similar to the digital cellular technology used for today's mobile telephone systems. The network consists of interconnected cells, each of which is served by a radio base station that provides wireless access to the network for mobile users. The base stations and other network nodes are connected together by fixed links. Despite these basic similarities, Mobitex is unique in several key respects. The characteristics that define the technology and make Mobitex unique in today's market are that it is a narrowband data-only network, that it uses packet switching and that it is based on an open international standard. These key characteristics are described in greater detail below.
Excerpt taken from the Novatel Wireless Inc website http://www.novatelwireless.com/support/CDPD%20Tech.html
Page 13
The communications channels in a Mobitex network have a bandwidth of 12.5 kHz, meaning that it is a narrowband radio technology. This can be compared to the 30 kHZ carrier bandwidth used in second-generation GSM systems or the 5 MHz carrier bandwidth that will be used in thirdgeneration systems for mobile telephony. Today, with radio spectrum an increasingly scarce and expensive resource, a narrowband system has a compelling cost advantage. Mobitex is a data-only network. This means that it was designed from the start to carry data traffic and that data transfers cannot be blocked by voice calls. In fact, as many as 400 Mobitex users can share a single communications channel without any deterioration in service. Dedicated data also means that Mobitex suppliers are data experts and have extensive experience of the special prerequisites that apply for wireless data solutions and the real-world needs of wireless data subscribers. Unlike circuit-switched voice networks in which a dedicated connection must be established and maintained for the duration of the call, a packetswitched network breaks the data stream up into small packets, each of which can be sent across the network individually. No dedicated connections are needed, and network access is virtually instantaneous, because each data packet contains the destination address and can be routed dynamically as network conditions change. For subscribers, the benefits are that they are always connected and online, yet pay only for the number of packets sent, not connection time. Mobitex is an open standard available to all and administered by the Mobitex Operators Association. Currently Mobitex is available on the 400, 800 and 900 MHz bands, but because all networks are based on exactly the same specifications, Mobitex applications will work on any network anywhere in the world. Today there are some 30 Mobitex networks in operation on five continents, making Mobitex not only the largest wireless data market, but also the only truly global market. 2 It is important to note that Mobitex is NOT an IP based data network. You will need a network gateway in order to communicate between the LMU and the LM Exchange server. Further information on Mobitex can be found at the CTIA website http://www.wow-com.com
Excerpt Taken from the Ericcson Mobitex website http://www.ericsson.com/network_operators/mobitex/about.shtml
Page 14
iDen iDen is a digital wireless communications technology developed by Motorola based on TDMA principles intended to increase capacity on existing analog SMR networks. The time slot spacing allows iDen providers to offer such services as dispatch, interconnect phone, data, and text messaging. Data/Internet capable iDen mobiles offer data rates of approximately 9600 bps. Further information on iDen can be found on the Motorola website: http://www.motorola.com/LMPS/iDEN/ SMS The Short Message Service (SMS) is the ability to send and receive text messages to and from mobile telephones. The text can comprise of words or numbers or an alphanumeric combination. SMS was created as part of the GSM Phase 1 standard.3 SMS message are typically text based, though binary messages are possible and can range in size from 140 characters to 256 characters depending on the network being used. GPRS
The General Packet Radio Service (GPRS) is a new non-voice value
added service that allows information to be sent and received across a GSM mobile telephone network. It supplements today's Circuit Switched Data and Short Message Service. GPRS is NOT related to GPS (the Global Positioning System), a similar acronym that is often used in mobile contexts.4 GPRS is being deployed in its initial stages in approximately 52 countries around the world. Keep in mind that GSM frequencies change depending where you are. In Europe, GSM sits in both the 900Mhz and 1.8GHz bands. In North America is sits in the 1.9GHz band. This means, that in order to roam with your GSM/GPRS mobile between countries, it needs to be able to operate on multiple frequencies.
Excerpt taken from the GSM World website (http://www.gsmworld.com/technology/sms/intro.shtml#1) 4 Excerpt taken from the GSM World website (http://www.gsmworld.com/technology/gprs.html)
Page 15
CMDA 1xRTT CDMA2000 1X technology supports both voice and data services over a standard (1X) CDMA channel, and provides many performance advantages over other technologies. First, it provides up to twice the capacity of earlier CDMA systems (with even bigger gains over TDMA and GSM), helping to accommodate the continuing growth of voice services as well as new wireless Internet services. Second, it provides peak data rates of up to 153 kbps (and up to 307 kbps in the future), without sacrificing voice capacity for data capabilities. CDMA2000 1X phones also feature longer standby times. And because it's backwards-compatible with earlier CDMA technology, CDMA2000 1X provides an easy and affordable upgrade path for both carriers and consumers.5 Point to Multi-Point The Point to Multi-Point wireless network is a custom 900MHz solution based on radios made by FreeWave Technologies (http://www.freewave.com). This a stand alone, non-IP, Relative-Time system. The network itself consists of a base-station unit, which is connected serially to the LM Exchange server and the LMUs. Unlike realtime systems such as CDPD and GPRS, events in a PMP system must be logged and then downloaded to the base station once the LMU has come within range.
Excerpt taken from the Qualcomm website (http://www.qualcomm.com/cdma/3g.html)
Page 16
Section 2: Hardware Overview

Location Messaging Unit (LMU)
Environmental Specifications The LMU is designed to operate in environments typically encountered by fleet vehicles, including wide temperature extremes, voltage transients, and potential interference from other vehicle equipment. To ensure proper operation in such an environment, LMUs were subjected to standard tests defined by the Society of Automotive Engineers (SAE). The specific tests included temperature, shock, vibration, and EMI/EMC. These tests were performed by independent labs and documented in a detailed test report. In accordance with Appendix A of SAE J1113 Part 1, the Unit is considered a Functional Status Class B, Performance Region II system that requires Threat Level 3 Testing. The following shows the environmental conditions the LMU is designed to operate in, and the relevant SAE tests that were performed. No formal altitude tests were conducted. Temperature Operating Temperature Range: -10oC to 60 oC Storage Temperature range: -30 oC to 70 oC SAE Test: SAE J1455 Humidity 5% to 95% relative humidity, non-condensing SAE Test: SAE J1455 Altitude Operate at altitudes of up to 10000 feet. Shock and Vibration Ground vehicle environment with associated shock and vibration SAE Test: SAE J1455 Bench-Handling (Non-Operating) 4 inch pivot drops on each of the faces on which it may be placed for servicing or installation. SAE Test: SAE J1455 Electromagnetic Compatibility (EMC) EMC compliant for a ground vehicle environment SAE Test: SAE J1113 Parts 2, 12,21, and 41
Page 17
Operating Voltage Range Vehicle 12 and 24 VDC systems, including transients and vehicle electrical system noise SAE Test: SAE j145 Transient Protection Input voltage transients typical of large trucks SAE Test: SAE J1113 Part 11 Electrostatic Discharge (ESD) No damage or performance degradation after the ESD disturbance. SAE Test: SAE J1113 Part 13 Power Consumption Average: < 300mA at 13.8 VDC Peak: <600mA for 50ms transmit burst (0.1% transmit duty cycle typical) Stand By < 10mA GPS Off: < 200mA at 13.8VDC Physical Specifications Size 6 7/8 x 3 7/8 x 1 5/8 Weight 1.5 lbs
Page 18
37 Pin Connector The Serial, I/O and power interface for the LMU is provided through a standard 37-Pin D-Series connector. PIN Signal Name Description Input/Output
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 Host Rx Data Host Tx Data Mic Reserved In1 Ignition In2 In 3 Out1 Out4 Out5 AIN0 Reserved Out6 Out2 Out3 Mode Serial Interface Receive Data to Host Serial Interface Transmit Data from host Microphone (GPRS Only) Input 1 Vehicle ignition / input 0 Input 2 Input 3 LED Driver B (20mA) LED Driver C (20mA) LED Driver D (20mA) Analog Input Relay Driver 2 (tied to Out3) Relay Driver 1 (100mA) Relay Driver 2 (100mA) Serial Port Mode (Gnd = PC mode, open = MDT mode) Input 5 Power input 12VDC to 24VDC Vehicle Chassis ground Microphone (GPRS Only) Serial Interface Return Serial Interface CTS (RS-232) Serial Interface RTS (RS-232) Serial Interface DSR (RS-232) Serial Interface DTR (RS-232) Serial Interface DCD (RS-232) LED Driver A (20mA) Serial Interface Ring Indicator (RS-232) Firmware Upload Enable (Gnd = Upload, Open = Normal) Vehicle Chassis Ground Speaker (GPRS LMU Only) Speaker (GPRS LMU Only) Test Mode Activate (Gnd Pulse = Test, Gnd hold= stop test Open = normal) Input 4 Power Input 12 to 24VDC Vehicle Chassis Ground Input Output Input Input Input Input Input Output Output Output Input Output Output Output Input
18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35
Vehicle Power GND Reserved Mic + Host Return Host CTS Host RTS Host DSR Host DTR Host DCD Out0 Host RI Program GND Reserved Seaker Speaker + Test
Input -Input -Input Output Input Output Input Output Output Input
Output Output Input
36 37
Vehicle Power GND
Input
Page 19
Standard Wiring Harness

10 inches RxD TXD CTS RTS DSR DTR GND Vehicle Pwr Out Mode Gnd In 1 In 2 In 3 Out 0 Out 1 Out 2 Out 3 Out 4 Out 5 Ignition/Accessory Vehicle +12/24V Vehicle Gnd 1 2 23 24 25 26 22 36 17 31 5 7 8 28 9 15 16 10 11 6 18 19
Black Gree/White Yellow/White Orange Blue Yellow Green Black
2 3 8 7 6 4 5
RxD TXD CTS RTS DSR DTR GND
Host Port
9-Pin Female D Connector with fastening screws
15 Feet
White Red Black
Un-terminated
37-Pin Female D Connector With fastening screws Note - All wire #22 AWG Stranded
8 Additional wires for insert 1 ft un-terminated Various colors
GPS Receiver 12 Channel GPS receiver Accuracy: 10 meter CEP (with SA off) Antenna connector: SMA Note that the TechnoCom LMU requires that an antenna amplifier that operates at 3VDC. 5VDC amps will not work. Available Radio Interfaces ! ! ! ! CDPD Mobitex GPRS PMP
RF Connector The LMUs RF connector is TNC. The impedance is 50 ohms nominal. Speaker Speaker outputs SPK2 are push-pull amplifiers and can be loaded down to 50 Ohms and up to 1nF. These outputs are differential and the output
Page 20
power can be adjusted by step of 2dB. The output can be directly connected to a speaker.
TetheredLocator
Environmental Specifications The TetheredLocator is designed to operate in environments typically encountered by fleet vehicles, including wide temperature extremes, voltage transients, and potential interference from other vehicle equipment. To ensure proper operation in such an environment, TetheredLocators were subjected to standard tests defined by the Society of Automotive Engineers (SAE). The specific tests included temperature, shock, vibration, and EMI/EMC. These tests were performed by independent labs and documented in a detailed test report. In accordance with Appendix A of SAE J1113 Part 1, the Unit is considered a Functional Status Class B, Performance Region II system that requires Threat Level 3 Testing. The following shows the environmental conditions the TetheredLocator is designed to operate in, and the relevant SAE tests that were performed. No formal altitude tests were conducted. Temperature Operating Temperature Range: -10oC to 60 oC Storage Temperature range: -30 oC to 70 oC SAE Test: SAE J1455 Humidity 5% to 95% relative humidity, non-condensing SAE Test: SAE J1455 Altitude Operate at altitudes of up to 10000 feet. Shock and Vibration Ground vehicle environment with associated shock and vibration SAE Test: SAE J1455 Bench-Handling (Non-Operating) 4 inch pivot drops on each of the faces on which it may be placed for servicing or installation. SAE Test: SAE J1455 Electromagnetic Compatibility (EMC) EMC compliant for a ground vehicle environment. SAE Test: SAE J1113 Parts 2, 12,21, and 41 Operating Voltage Range Vehicle 12 and 24 VDC systems, including transients and vehicle electrical system noise. SAE Test: SAE j145 Page 21
Transient Protection Input voltage transients typical of large trucks SAE Test: SAE J1113 Part 11 Electrostatic Discharge (ESD) No damage or performance degradation after the ESD disturbance. SAE Test: SAE J1113 Part 13 Power Consumption Average: < 300mA at 13.8 VDC Stand By < 10mA GPS Off: < 200mA at 13.8VDC Physical Specifications Size 6 7/8 x 3 7/8 x 1 1/8 Weight 1.0 lbs
Page 22
37 Pin Connector The Serial, I/O and power interface for the TetheredLocator is provided through a standard 37-Pin D-Series connector. PIN Signal Name Description Input/Output
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 Host Rx Data Host Tx Data RTS2 CTS2 In1 Ignition In2 In 3 Out1 Out4 Out5 AIN0 V Batt Out6 Out2 Out3 Mode Serial Interface Receive Data to Host Serial Interface Transmit Data from host Modem Serial Interface RTS Modem Serial Interface CTS Input 1 Vehicle ignition / input 0 Input 2 Input 3 LED Driver B (20mA) LED Driver C (20mA) LED Driver D (20mA) Analog Input Battery Monitor Relay Driver 2 (tied to Out3) Relay Driver 1 (100mA) Relay Driver 2 (100mA) Serial Port Mode (Gnd = PC mode, open = MDT mode) Input 5 Power input 12VDC to 24VDC Vehicle Chassis ground Modem Serial Interface DTR Modem Serial Interface DCD Serial Interface Return Serial Interface CTS (RS-232) Serial Interface RTS (RS-232) Serial Interface DSR (RS-232) Serial Interface DTR (RS-232) Serial Interface DCD (RS-232) LED Driver A (20mA) Serial Interface Ring Indicator (RS-232) Firmware Upload Enable (Gnd = Upload, Open = Normal) Vehicle Chassis Ground Battery Return Modem Serial Interface Transmit Data Modem Serial Interface Receive Data Test Mode Activate (Gnd Pulse = Test, Gnd hold= stop test Open = normal) Input 4 Power Input 12 to 24VDC Vehicle Chassis Ground Input Output Output Input Input Input Input Input Output Output Output Input Input Output Output Output Input
18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35
Vehicle Power GND DTR2 DCD2 Host Return Host CTS Host RTS Host DSR Host DTR Host DCD Out0 Host RI Program GND GND Tx2 Rx2 Test
Input -Input Output -Input Output Input Output Input Output Output Input
Output Input Input
36 37
Vehicle Power GND
Input
Page 23
Standard Wiring Harness

DCD RXD TXD CTS RTS DSR DTR GND Mode GND RTS 2 CTS 2 DTR 2 DSR 2 GND TXD 2 RXD 2 Modem Power Enable Ignition/Accessory Vehicle +12/24V Vehicle Gnd 27 1 2 23 24 25 26 22 17 31 3 4 20 21 32 33 34 29 6 18 19 White Red Black Black Blue Orange Green Yellow Black Yellow/White Green/White Brown Green/White Yellow/White Orange Blue Yellow Green Black 1 2 3 8 7 6 4 5 DCD RXD TXD CTS RTS DSR DTR GND
Host Port
9-Pin Female D Connector 7 8 4 1 5 3 2 9-Pin Male D Connector Un-terminated RTS 2 CTS 2 DTR 2 DCD 2 GND TXD 2 RXD 2
Aux Port
37-Pin Female D Connector
Note - All wire #22 AWG Stranded
GPS Receiver 12 Channel GPS receiver Accuracy: 10 meter CEP (with SA off) Antenna connector: SMA Note that the TechnoCom LMU requires that an antenna amplifier that operates at 3VDC. 5VDC amps will not work. Certified Wireless Devices ! CDPD Modems - Novatel Wireless Lancer - Sierra Wireless MP 200 - Novatel Wireless Sage iDen Phones - i55sr - i50sx, - i80s - i85s - i90c - i2000plus - i1000plus - i700plus - i550plus - i500plus - r750plus Page 24
! !
CDPD Phones: - Ericsson R280d GPRS Phones: - Motorola Timeport
3Watt LMU
The 3-Watt LMU is a special version of the CDPD LMU based on the Novatel Wireless Lancer, which is designed to work in fringe coverage areas. Environmental Specifications Temperature Operating Temperature Range: -30oC to 70 oC Humidity 5% to 95% relative humidity, non-condensing Altitude Operate at altitudes of up to 10000 feet. Shock CDPD Standard 20G axis non-operating Vibration MIL-STD 202F and CDPD Standard 15 G six axis, 5 to 200 HZ operating Bench-Handling (Non-Operating) 4 inch pivot drops on each of the faces on which it may be placed for servicing or installation. SAE Test: SAE J1455 Operating Voltage Range Vehicle 12 and 24 VDC systems, including transients and vehicle electrical system noise. SAE Test: SAE j145 Power Consumption 2A Max draw Physical Specifications Size 8.2 x 5.27 x 2.08 Weight 2.0lbs
Page 25
37 Pin Connector The Serial, I/O and power interface for the 3 Watt LMU is provided through a standard 37-Pin D-Series connector. PIN Signal Name Description Input/Output
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 Host Rx Data Host Tx Data RTS2 CTS2 In1 Ignition In2 In 3 Out1 Out4 Out5 AIN0 V Batt Out6 Out2 Out3 Mode Serial Interface Receive Data to Host Serial Interface Transmit Data from host Lancer Serial Interface RTS Lancer Serial Interface CTS Input 1 Vehicle ignition / input 0 Input 2 Input 3 LED Driver B (20mA) LED Driver C (20mA) LED Driver D (20mA) Analog Input Battery Monitor Relay Driver 2 (tied to Out3) Relay Driver 1 (100mA) Relay Driver 2 (100mA) Serial Port Mode (Gnd = PC mode, open = MDT mode) Input 5 Power input 12VDC to 24VDC Vehicle Chassis ground Lancer Serial Interface DTR Lancer Serial Interface DCD Serial Interface Return Serial Interface CTS (RS-232) Serial Interface RTS (RS-232) Serial Interface DSR (RS-232) Serial Interface DTR (RS-232) Serial Interface DCD (RS-232) LED Driver A (20mA) Lancer Ignition Signal Firmware Upload Enable (Gnd = Upload, Open = Normal) Vehicle Chassis Ground Battery Return Lancer Serial Interface Transmit Data Lancer Serial Interface Receive Data Test Mode Activate (Gnd Pulse = Test, Gnd hold= stop test Open = normal) Input 4 Power Input 12 to 24VDC Vehicle Chassis Ground Input Output Output Input Input Input Input Input Output Output Output Input Input Output Output Output Input
18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35
Vehicle Power GND DTR2 DCD Host Return Host CTS Host RTS Host DSR Host DTR Host DCD Out0 LncrIgn Program GND GND Tx2 Rx2 Test
Input -Input Output -Input Output Input Output Input Output Output Input
Output Input Input
36 37
Vehicle Power GND
Input
NOTE: Vehicle Power and chassis Ground must also be supplied to the Lancers power connector.
Page 26
Standard Harness
Brown DCD RxD TxD CTS RTS DSR DTR GND 27 Green / White 1 Yellow / White 2 Orange 23 Blue 24 Yellow 25 Green 26 Black 22 4 GND 5 DTR 6 DSR 7 RTS 8 CTS 3 TxD 2 RxD 1 DCD
Host Serial Port
Mode GND
17 Black 31 Blue
9 Pin Female D Series Connector
RTS2 CTS2 DTR2 DSR2 GND TxD2 RxD2
3 Orange 4 Green 20 Yellow 21 Black 32 Yellow/White 33 Green/White 34
7 8 4 1 5 3 2
RTS2 CTS2 DTR2 DCD2 GND TxD2 RxD2
Lancer Serial Port
9 Pin Male D Series Connector
White Lancer Ign 29 2 4 3 Red V+ GND Ign 18 Black 19 Blue 6 37 pin Female D Series Connector
Lancer Power From Vehicle
GPS Receiver 12 Channel GPS receiver Accuracy: 10 meter CEP (with SA off) Antenna connector: SMA Note that the TechnoCom LMU requires that an antenna amplifier that operates at 3VDC. 5VDC amps will not work. Available Radio Interfaces ! CDPD
Page 27
I/O Descriptions
Outputs Pins 9, 10, 11 and 28 provide outputs designed to drive LEDs and hence can source 20mA. They are internally limited to supply 5mA at 4VDC and 20mA at 2VDC. Pins 14, 15 and 16 provide access to the LMUs and TetheredLocators 2 relay drivers. These outputs provide a high-current, open-collector driver that can sink up to 100 mA each. These drivers may be used to drive 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 circuitry can be added to source the current.
+V
100 mA
2V - 20mA
LED Outputs
Driver Outputs Connected to External Relay
Ignition and Inputs The LMU and TetheredLocator provide four vehicle-compatible inputs. These inputs are protected from typical vehicle transients and can be directly connected to most vehicle level logical inputs, from 4 volts up to the vehicle power input level (typically 12 VDC). Their input impedance is approximately 10K ". One of these inputs is dedicated to sensing the vehicles ignition status to provide for flexible power management. The other three inputs may be used to sense vehicle inputs such as cooling unit operation, a hidden driver Panic switch, or taxi on-duty/off-duty meter status. Keep in mind that the ignition input (pin 6) is pulled to ground through the 10k resistance, where the other three inputs (pins 5,7,8) are pulled to vehicle power.
Page 28
+V (+12V)
LMU
Input 3 +V (+12V)
Panic button
Door Open Detect Input 2

Door Switch Dome Light
+V (+12V) Input1 Driven through a relay
+V (+12V) IGN Ignition
Expanded Inputs As of the release of LMU firmware version 4.2a, it is possible to reassign the Test and Mode pins on the LMU and TetheredLocator into Inputs 4 and 5. This is done be an S-Register command (S140). The available settings are: 0 - Test and Mode act as normal (i.e. not as inputs). This is the default setting of the LMU and TetheredLocator. 1 - Test is mapped to Input 4 2 - Mode is mapped to input 5 3 - Test is mapped to input 4, Mode is mapped to Input 5 It is important to note that the LMU and TetheredLocator are in PC mode when the Mode pin is mapped to Input 5.
Page 29
Analog to Digital Converter - External The Analog to Digital converter is a 10 bit converter with a full scale voltage of 36.5V. The LSB voltage is approximately 38.5mV +/- 2% error, so, for instance, a 10 VDC input reading would translate to a value of 260. Analog to Digital Converter Internal The internal analog to digital converter monitors the filtered voltage supplied to the LMU/TetheredLocator. Like the external it is a 10 bit converter with an LSB of 38.5mV. Status LEDs Certain versions of LMU hardware are equipped with two Status LEDs, one for GPS and one for COMM (wireless network status). Each LED has four states. LED GPS Off
GPS receiver is off
Slow Blink
Initial search
Fast Blink
Time Sync Acquired or GPS Lost Modem is on and data session (PPP) has been established or COMM Lost
Solid
Real-Time GPS Fix Modem is on, data session (PPP) has been established and is registered to the wireless network
COMM Wireless modem

is off or not connected
Modem is on but data session (PPP) has not been established
Page 30
Section 3: Installation
Installation Notes:
When installing the LMU and TetheredLocator into a vehicle there are a few things you need to keep in mind. First of all you will want access to the following pieces of equipment: ! ! ! ! ! ! ! ! LMU or TetheredLocator GPS Antenna - Through-hole or magnetic mount Cellular/PCS Antenna (LMU only) - 3dB gain whip, with either NMO or magnetic mount Wiring harness - Standard LMU or TetheredLocator harness with DSeries-37 Pin connector Hook-up wire - 22 AWG, minimum Installation Tools Tie wraps, wire nuts and electrical tape. Laptop or PC to configure the LMU or TetheredLocator Vehicle Wiring Layout
Next, we want to make sure the power is configured correctly. It is essential that the Power input (red wire) be connected to a constant (unswitched) +12 VDC or +24 VDC supply and that the Ignition input (white wire) be connected to the vehicle ignition or another appropriate key operated line, such as ACCESSORY, (basically anything that goes low during engine cranking). Failure to do so may result in discharge of the vehicle battery. From here was can install the GPS antenna. Placement of the GPS antenna is critical to proper operation of the Unit. For the GPS receiver to accurately compute its location, its antenna must have a clear view of the sky. The best place to mount the GPS is usually on the vehicles highest point (eg the roof of a car). When installing the GPS antenna on a vehicle, make sure that there are no obstructions close to the antenna that might block the view 360# to the horizon. Things like air horns or maker lights should not block the antenna beyond 5# above the horizon. The best location is usually near the center of the roof, however it is also desirable to locate the cellular antenna as far from the GPS antenna as is practical.
Page 31
Antenna far away from lights and air horns No Blockage above 5#
Examples of good and poor GPS antenna placement The received signal levels at the GPS antenna from the satellites are very low in power (approximately -136 dBm), so any blockage of the antenna can affect the quality of the location computed by the receiver. Kinks or tight knots in the antenna cable can also prevent the GPS receiver from operating. When laying out the antenna cable, care should be taken so that the cable is not subjected to crushing or strain. Lastly we need to consider the cellular antenna. Typically, the cellular antenna used by the LMU for wireless service is a standard 3-dB gain whip. It mounts with standard mounts (i.e. through hole or magnetic mount) and requires a ground plane to work properly. If possible, it should be located at least 3 feet from the GPS antenna. Ensure that the cable does not get crushed during installation. You should now be ready to install the LMU into the vehicle. Typical installations will place the LMU and TetheredLocator under the vehicle dash board, or in the trunk. The only real item to keep in mind is to make sure you can get access to the unit afterwards. In some cases it may be necessary to add additional wires to the harness or connect the LMU/TetheredLocator to a PC or MDT. To assist in mounting the LMU and TetheredLocator, a template can be found in Appendix E Once the unit is placed, you can go ahead and hook up the antennae and harness in the following order: 1. Attach the GPS antenna to the SMA connector. 2. if youre using an LMU attach the cellular antenna to the TNC connector. 3. Finally plug in the 37 Pin D-series connector.
Page 32
Quick Start Guides

In this section we will discuss how to quickly get your LMU or TetheredLocator up and running as quickly as possible. We will take advantage of the default PEG script, so, for the time being, we will not have to worry about programming anything. This script will send an event report to the LM Exchange server every 60 seconds or every 1000 meters, whichever comes first. We are making two assumptions here in order to simplify the setup process. 1. You have a configured LM Exchange server. 2. You are using the standard wiring harness from TechnoCom. QUICK START: CDPD LMU In order to use the CDPD LMU (either the regular or the 3 Watt) you will need a CDPD account. CDPD is generally available from the local cellular carrier in most major metropolitan areas of North America. When you sign up for service you will be given an NEI (ip address) and one, possibly two DNS servers. For the initial set up process you wont need the DNS servers but keep them available as they will be used later. 1. Connect the LMU as discussed above (ie power, GPS and CDPD antennas) 2. Plug the serial cable into your laptop. 3. Open a terminal session to the LMU6 4. You should now be able to talk to the LMU via AT Commands7. Enter the following command: AT It should return a response of: OK This is just to ensure that the LMU is responding correctly. 5. First we need to program in your IP address. That is done with the following command: AT$APP ADDR MODEM <ip address> The response will be: Set Modem Addr to <ip address>
See Appendix A on how to configure HyperTerminal to talk to your LMU. For the most part we will use LMU Manager to change settings in the LMU and TetheredLocator, however, it makes more sense to use AT Command for your initial set up. We are assuming that you have some familiarity with LMU Manager.
7
Page 33
OK COMM DISCONNECTED COMM CONNECTED <ip address> There will be a several second delay between the COMM DISCONNECTED and COMM CONNECTED messages. 6. Next we want to set up where the event reports are being sent. We will need the IP address of your LM Exchange server. Enter the following command: AT$APP ADDR INBOUND <lm exchange ip> The response should be: Set Inbound Addr to <lm exchange ip> OK 7. Finally we will want to verify that the LMUs modem has registered to the CDPD network. Enter: AT$APP COMM STATUS? The response should be similar to: Registered: Yes Denied Reason: N/A Channel State: Channel Acquired Channel Acquired: Yes Link Established: Yes TEI: A30F1 Channel: 693 RSSI: -97 dBm Forward BLER: 0 %(pk) Reverse BLER: 0 %(pk) MDBS Busy: 64 %(pk) Power Level: 2 Power Product: 25 Receive Packets: 0 Transmit Packets: 0 Receive Bytes: 0 Transmit Bytes: 0 SPI: 3232 SPNI: 3232 WASI: 0 Cell ID: 52221 Area Color Code: 42 8. If the Registered value is No and there is something other than N/A in the Denied Reason, you may need to contact your CDPD provider to verify coverage and that the account is active.
Page 34
QUICK START: Mobitex LMU In order to use the Mobitex LMU, you will need to obtain a Mobitex service. 1. Connect the LMU as discussed above (ie power, GPS and Mobitex antennas) 2. Plug the harness into your LMU. 3. Plug the serial cable into your laptop. 4. Open a terminal session to the LMU 5. You should now be able to talk to the LMU via AT Commands. Enter the following command: AT It should return a response of: OK This is just to ensure that the LMU is responding correctly. 6. Mobitex service is activated over the air, so we do not need to provision anything, we will just need to set up the lm Exchange address. AT$APP ADDR INBOUND <lm exchange ip> The response should be: Set Inbound Addr to <lm exchange ip> OK 7. Finally we will want to verify that the LMUs modem has registered to the mobitex network. Enter: AT$APP COMM STATUS? The response should be similar to: Registered: Yes Denied Reason: N/A Channel State: Channel Acquired Channel Acquired: Yes Link Established: Yes TEI: A30F1 Channel: 693 RSSI: -97 dBm Forward BLER: 0 %(pk) Reverse BLER: 0 %(pk) MDBS Busy: 64 %(pk) Power Level: 2 Power Product: 25 Receive Packets: 0 Transmit Packets: 0 Receive Bytes: 0 Page 35
Transmit Bytes: 0 SPI: 3232 SPNI: 3232 WASI: 0 Cell ID: 52221 Area Color Code: 42 8. If the Registered value is No and there is something other than N/A in the Denied Reason, you may need to contact your Mobitex provider to verify coverage and that the account is active.
Page 36
QUICK START: GPRS LMU In order to use the GPRS LMU you will need a GPRS account. GPRS is generally available from the local GSM carrier in most major metropolitan areas of North America and Europe. When you sign up for service you will be given an SIM card and an APN name. The SIM must be inserted into the LMU before the provisioning process can begin. 1. Connect the LMU as discussed above (ie power, GPS and CDPD antennas) 2. Plug the serial cable into your laptop. 3. Open a terminal session to the LMU 4. You should now be able to talk to the LMU via AT Commands8. Enter the following command: AT It should return a response of: OK This is just to ensure that the LMU is responding correctly. 5. First we need to program the address of your LM Exchange server AT$APP ADDR INBOUND <lm exchange ip> The response should be: Set Inbound Addr to <lm exchange ip> OK 6. Next we need to select the Mobile ID of your unit. Generally this should be left as the serial number of your LMU. AT$APP MOBID ESN The response should be OK 7. To program in the APN use: AT$APP GPRS CONTEXT 0 IP:<apn name> Again the response should be: OK 8. Reset the LMU and wait approximately 60s 9. Lastly we will want to verify that the LMUs modem has registered to the GPRS network. Enter: AT$APP COMM STATUS? The response should be similar to: GSM Registered : Yes
For the most part we will use LMU Manager to change settings in the LMU and TetheredLocator, however, it makes more sense to use AT Command for your initial set up. We are assuming that you have some familiarity with LMU Manager.
8
Page 37
GPRS Registered : Yes Connection : Yes RSSI : -70 dBm BER : 0 Channel : 0 Cell ID : 0 Base Station ID : 0 Local Area Code : 0 Network Code : 0 Country Code : 310 IMEI (Modem S/N): 500167110060440 IMSI (SIM S/N) : 310230100521849 | Phone Number : GPRS APN : IP:INTERNET3.VOICESTREAM.COM Quality of Srvc : 1,0,0,3,0,0 GSM Class : B 10. If the Registered value is No and there GPRS APN value is correct you may need to contact your GPRS provider to verify coverage and that the account is active.
Page 38
QUICK START: Point To Multi-Point (PMP) LMU In order to use a PMP LMU be sure that LM Exchange is properly configured to support a PMP base station. LM Exchange must be running to properly complete this setup. Also be sure note of which radio network (1,2,3 or 4) the base station is set to. 1. Connect the LMU as discussed above (ie power, GPS and CDPD antennas) 2. Plug the serial cable into your laptop. 3. Open a terminal session to the LMU 4. You should now be able to talk to the LMU via AT Commands9. Enter the following command: AT It should return a response of: OK This is just to ensure that the LMU is responding correctly. 5. The only set up parameter we need to configure for a PMP LMU is the radio network. This is accomplished by: AT RADIO INIT <n> where <n> is the Radio Network number (1, 2 3 or 4). The response should be: OK < 30 second delay> FWAVE: Radio Param Setup Complete 6. Lastly we will want to verify that the LMUs modem has registered to the network. Enter: AT$APP COMM STATUS? The response should be similar to: Registered : Denied Reason : Link Established: Channel Acquired: Receive Packets : Transmit Packets: Receive Bytes : Transmit Bytes : WASI : SPNI : SPI :
Yes N/A Yes Yes 0 0 0 0 10 20 30
For the most part we will use LMU Manager to change settings in the LMU and TetheredLocator, however, it makes more sense to use AT Command for your initial set up. We are assuming that you have some familiarity with LMU Manager.
Page 39
7. If the Registered value is No you will need to verify that LM Exchange is up and running with the appropriate base station configuration.
Page 40
QUICK START: TetheredLocator For this procedure we are making the assumption that the CDPD modem or the iDen phone you are using has already been set up with an IP Address, or, in the case of iDen, enabled for internet access. 1. Connect the LMU as discussed above (i.e. power, and GPS antenna) 2. Plug the CDPD modem into the secondary serial port on the TetheredLocator. Make sure that the modem is powered. 3. Plug the harness into your TetheredLocator. 4. Plug the primary serial cable into your laptop. 5. Open a terminal session to the TetheredLocator 6. Enter the following command: AT It should return a response of: OK This is just to ensure that the LMU is responding correctly. 7. First we need to set up the TetheredLocator to talk to your specific modem. For the R280d enter: ATS120=7 For a generic GPRS Phone/Modem enter: ATS120=6 For a WaveCom GPRS Modem enter: ATS120=5 For the MP200 enter: ATS120=4 For the iDen phone enter: ATS120=3 For the Novatel Wireless Lancer or Sage use: ATS120=2 Either way, the response should be: OK 8. Next we will need to set up the address of our LM Exchange server. AT$APP ADDR INBOUND <lm exchange ip> The response should be: Set Inbound Addr to <lm exchange ip> OK 9. Finally we will want to verify that the modem/phone has registered to the wireless network. Enter: AT$APP COMM STATUS? The response should be similar to: Page 41
Registered: Yes Denied Reason: N/A Channel State: Channel Acquired Channel Acquired: Yes Link Established: Yes TEI: A30F1 Channel: 693 RSSI: -97 dBm Forward BLER: 0 %(pk) Reverse BLER: 0 %(pk) MDBS Busy: 64 %(pk) Power Level: 2 Power Product: 25 Receive Packets: 0 Transmit Packets: 0 Receive Bytes: 0 Transmit Bytes: 0 SPI: 3232 SPNI: 3232 WASI: 0 Cell ID: 52221 Area Color Code: 42 10. If the Registered value is No and there is something other than N/A in the Denied Reason, you may need to contact your service provider to verify coverage and that the account is active.
Page 42
Section 4: Unit Configuration

Now that we have the basics of getting the LMU and TetheredLocator up and running we can go into a little more detail on the variety of configurations available.
Working with Host Devices

We will start off with a discussion on how to configure the LMU to work with host devices such as Laptops, PDAs, MDTs and other serial devices (for example, card readers), though we have already seen how part of this works in the Quick Start section. All host devices work through the primary serial port, which, by default, is set up at: Baud Rate: 19200 Data Bits: 8 Parity: None Stop Bits: 1 Flow Control: Hardware It is a full 9-wire RS-232 interface. Note that the baud rate can be changed via the AT+IPR command. The serial port itself is capable of operating in one of two modes, either a PC mode, or an MDT mode. Which one it is in is determined by the state of pin 17. Shorted to ground, which is how the standard hardness is configured, is PC mode, which enables you to communicate with the LMU from a PC or a laptop. In this mode, the LMU can act like any other wireless data modem. We used this feature to configure the LMU in the Quick Start section. The other mode of operation occurs when pin 17 is left open10. This mode allows you greater configuration access to the LMU and TetheredLocators serial port. The serial port setup parameters for MDT mode are controlled through S-Registers in the LMU. S-Registers are accessed through AT Commands using the following formats: Query S Register: ATSnnn? Or AT$APP Snnn? Set an S Register ATSnnn=xxx Or AT$APP Snnn=xxx
10
The Mode pin, like the inputs, is pulled up to vehicle power through a 10k resistance.
Page 43
Where nnn represents the number of the S-register and xxx is the value of the S-register. All S-Registers queries and settings use decimal values to identify the register and its contents, even if the information is a hexadecimal or binary value such a termination character or an option enable. The following S-Registers control the serial port configuration in MDT mode: S130 Application Mode This register has 4 options 0 MDT mode. Meant for use with any standard MDT 1 GSD mode. This mode is meant for use with other intelligent serial devices. By intelligent we mean a device capable of sending and receiving message through the LMU. These messages will be sent through LM Exchange to be processed by your application. 2 Long Message mode: This mode is similar to the GSD mode, only it supports message sizes larger than 848 bytes. Keep in mind that settings in s135 and 138 are also required for this mode to function properly. 3 SLIP mode. The serial device must be capable of managing a SLIP connection to the LMU S131 Data Rate The LMU and TetheredLocator serial port can support up to 11 different data rates while In MDT mode: 0 300 1 600 2 1200 3 2400 4 4800 5 9600 6 14400 7 19200 8 28800 9 38400 10 57600 11 76800 12 - 115200 S132 Word Size This register is bit-mapped to control the Parity, Stop Bits and the Data bits: Bit 0 Bit 1: Data bits: (0 = 5bits, 1 = 6 bits, 2 = 7 bits, 3 = 8 bits) Bit 2: Stop Bits (0 = 1 bit, 1 = 2 bits) Bit 3: Parity Enable (0 = Disabled, 1, = Enabled) Bit 4: Parity Select (0 = Odd, 1 = Even) Page 44
S133 Flow Control This register currently only responds to a single bit enable: Bit 2: Termination Character Enable (0 = disabled, 1 = enabled) S134 Serial Port Termination Character This is the decimal representation of the desired message termination character. (e.g. you would enter 13 to make a Carriage Return the termination character.) S135 Serial Port Termination Length Message length in bytes coded as 0 to 212 with 4 byte LSB, maximum message length is 848 bytes, S135=212 (i.e. S135=200 sets message termination length to 800 bytes). S136 Serial Port Message Type Decimal value of the message code associated with the inbound message generated by GSD activity, 0 to 255. This register is also used to filter packets received from LM Exchange based on MsgType. S137 Serial Port Message Disposition This register defines how the LMU should handle a message 0 & 1 = Send if wireless network is available, otherwise discard the message 2 = Send if message is available, if not, put the message in the LMU or TetheredLocators log. 3 = Log the message. (i.e. do not attempt to send it) 4 255 (reserved) Note that this register is only used in GSD mode S138 Serial Port Termination Time-out This register defines the delay before the termination of inbound data. The values range from 0.1 to 25.5 seconds (1-255), and value of 0 will send the data immediately. This register is only used in Long Message Mode In addition to the S-Registers the LMU has four quick setup commands to configure the serial port: AT$APP SERIAL MDT MDT Setup (2400 baud, 7 data bits, Odd parity,1 stop bit) S130=0, S131=3, S132=10, S133=4, S134=13, S135=25 AT$APP SERIAL MAGTEK Magtek Card Reader Setup (9600 baud,8 data bit,No parity,1 stop bit) S130=1, S131=5, S132=3, S133=4, S134=13, S135=200 AT$APP SERIAL PVEND PVend Setup (2400 baud, 7 data bits, Even parity,1 stop bit)
Page 45
S130=2, S131=3, S132=26, S133=0, S134=13, S135=1, S136=1, S137=0, S138=5 AT$APP SERIAL HEAT HEAT Setup S130=3, S131=7, S132=3, S133=0, S135=0, S137=2, S138=2 AT$APP SERIAL P201 P201 MDT Setup (9600 baud,8 data bit, No parity,1 stop bit) S130=1, S131=5, S132=3, S133=4, S134=13, S135=200, S136=1, S137=1, S138=0 More on GSD (Generic Serial Device) and Long Message Mode Both GSD and Long Message modes are used for passing custom messages from a serial device to your application. This could include something simple, like a credit card transaction, to something complex, like a screen capture. The data stream received from the serial device will be transmitted directly to LM Exchange and your application without any processing or encoding11. The message type field can be used to identify a user defined message type. The GSD interface supports this field by permitting the user to select which message types are passed to the GSD and which is generated by the GSD. The LMU will only pass messages received from LM Exchange to the GSD that have a message type whose lower 8-bits match the contents of S-Register 136. Moving in the other direction, all messages generated by the LMU from the GSD byte stream will have a message type equal to the contents of S-Register 136 with the upper 8-bits set to zeroes. Additionally, the LMU can be configured to look for a configurable unique termination character in the stream, such as a Carriage Return and/or it can wait for a configurable termination length to occur to initiate the sending of the message (i.e. the value set in S135). In CDPD, for instance, the maximum size of an individual message is 848 bytes. Should you wish to use serial data streams of arbitrary lengths (greater then 848 bytes) you will need to use Long Message mode. Long messages are enabled by setting S130=2 which, when combined with S-135 and S-138, enables a type of PAD function within the LMU. All bytes received by the serial port are automatically buffered until reaching the maximum termination length set in S-135 or until the timeout set in S138 expires. As the 848 byte message buffers are filled, they are
Note that your message will be embedded in the XML messages from LM Exchange, the point here is that the message itself is not touched.
11
Page 46
automatically logged and log reporting is immediately activated to send in the message buffers as they are filled. This process continues for the entire length of the incoming message until the termination timeout expires. Thus, inbound data streams of any length may be supported as long as the internal 8 kbyte buffer within the LMU is not exceeded. The messages are received sequentially by LM Exchange and may be identified using the message type field. Each of the messages are marked with the type specified in S-136. This type number is reported as the value of [S-136 +1] if message received was sent because of a message termination timeout (S-138). For example, if a 2000 byte message is received by the LMU, followed by a 10 second period with no data, each of the first two packets received by LM Exchange will be 848 bytes long and market with the type set in S136. The third packet received will be 304 bytes in length and will be market with a type one greater that the value of S-136. As with the GSD mode, outbound messages received from LM Exchange must have a matching message type to that set into S-136 to be output to the external serial port.
Reporting Configuration
We are now going to take our first real steps inside the LMU12 move into a discussion of how our event reports are sent, where they are sent to and what their contents are. Inbound Routing To start off with we want to talk about where event reports get sent. In the Quick Start section we mentioned that this is handled by settling an Inbound IP address (i.e. the address of the LM Exchange server). In reality, you can actually set up to four different Inbound IP addresses in the LMU. One case in which you would use this feature is when you want to have a back-up LM Exchange server. This would allow you to take down the primary server to perform upgrades, yet still have event reports come in to your application.13 In LMU Manager, GET the Inbound tab. You should see the IP address you programmed in during the Quick Start at the top of the Inbound Routing List. If desired, enter the address of your back up server in the second Inbound Routing List entry and SEND it to the LMU
From here on out, the functionality of the TetheredLocator and LMU are the same. We will use LMU to reference both devices unless otherwise stated. 13 Remembering that you would need a TCP client in your application for each LM Exchange server you are using. Other than the socket itself dropping there isnt any notification message that is sent when an LM Exchange server is taken down.
12
Page 47
Now we have several options as to how to manage this list. We have an Open mode, a Static Inbound (default) mode and a Random inbound mode. In Open mode (this is with both the Static and Random inbound options unchecked in the Access Tab), the LMU will send event reports to the last LM Exchange server IP and port that it successfully queried the unit, regardless of what is in the Inbound list. So, for instance, you have a Test LM Exchange server as well as your Primary and Backup. If you make a location request from the Test server from port 2030114, the LMU will stop reporting to the Primary and begin to report to the Test. To have the LMU switch back to the Primary, you will either need to make a request from the Primary server, or take down the Test server. The LMU should then default back to the Primary. In Static Inbound mode, the LMU will always send reports to the IP addresses in the Inbound Routing list, regardless of what other servers have contacted it. Note that, when cycling through the list, the LMU will start with the first address and move to the next IP until is successfully sends a report. Remember that this is the default mode of all LMUs. In Random inbound mode, again the LMU will only send reports to the IP addresses in the inbound Routing list, but when dealing with send failures, will move through the list at random. This is done to help load balance between multiple servers. Both the Static and Random Inbound modes are enabled in LMU Managers Access Tab. Note that Static inbound takes precedence when both options are enabled. LM Exchange Access The LMU is capable of limiting which LM Exchange servers it will respond to. This is done by setting up the Service Access IP Address list with the addresses of your LM Exchange Servers. You can also limit the addresses the LMU will respond to by specifying a class B or C address in such as 207.255.255.255 or 207.199.255.255. You should always be able to access an LMU with LMU Manager regardless of the entries found in the Service Access IP Address list. Be advised that the list is populated from bottom to top15.
LM Exchange, by default uses ports 20301 to 20315 as the From port for requests made to the LMU. 15 This is because the Service Access IP list also doubled as the Inbound IP Address List, where the inbound we set from top to bottom up to the first 0.0.0.0 entry and the Service Access IPs were populated from bottom to top to the first 0.0.0.0.
14
Page 48
Host Access When using the LMU with a host serial device such as a laptop it is possible to restrict which IP addresses host applications can talk to. For example, you have a dispatching application that works on a laptop hooked to an LMU and you are paying a per byte charge on the CDPD account. You do not want to allow your driver general internet access for web-browsing, email, instant messaging etc in order to avoid a very costly bill. What you would do is set up the host IP address list with the IP of your dispatch server. Again, like the Service Access list you can specify class B or C addresses with the use of the wild card value (255). Event Report Contents The LMU can send event reports in one of two ways, either directly to the LM Exchange server (i.e. real-time) or through a log buffer16(i.e. relative time). For each case we can customize what optional data gets sent / stored. The standard contents of an event report are: ! The IP Address of the LMU submitting the report ! The time at which the report was generated ! The time of fix from the GPS receiver ! Latitude, Longitude, Speed, Heading, HDOP, and Fix-Status ! Event Index ! Event Code The optional components are: ! Altitude ! Status of the wireless modem (Comm) ! The wireless carrier identifiers ! Input and output status ! The current values of up to 16 accumulators ! The zone status of the LMU ! The environment mask status of the LMU The optional components for the real-time and relative time reports can be configured in LMU Managers Service Tab under the Inbound Send and Inbound Log options respectively. (Note that the Pseudo Range and Pseudo Random numbers are available as options, but they are not sent in the event report.
16
We will discuss how the data gets sent in the PEG section.
Page 49
Accumulator Count Look Up Table The above settings apply to every event report being logged or sent. The Accumulator Count Look Up table allows you to configure report contents based on the Event Code. For a specific event code you can specify how many of the 16 accumulators are to be reported. Up to eight different code to counts can be defined. These values are set in the Inbound Tab of LMU Manager. Retry Scheduling Since there are two ways to generate reports, there are also two retry schedules to help get those reports to the LM Exchange server. For Real-Time reports, the LMU will attempt to send the report up to six times with up to a 255 second delay between each try. This is configured on the Inbound Tab in LMU Manager. Note that the Access Tab also contains a retry schedule. This is the same schedule only the values are limited to 15 seconds between reties. If the Inbound list exists, it will always take precedence. Regardless of which list is used, the default settings have two retires with a 20 second delay between each. The log schedule works slightly different. Once the log becomes active (i.e. a report is placed in it), it will attempt to empty itself as soon as it can. The retry schedule in this case is made up of two values, the first is the number of times the LMU will attempt to send its log, the second value is the delay between events. Once the log has successfully been sent, it will be deleted. Note that you can set up two difference log retry schedules based on the state of the ignition. You can configure both states through the Service Tab in LMU Manager. Both states are defaulted to 4 retries with a 240 second delay. Enabling Event Reporting Now that we have set up how we want events to come in, we need to make sure the LMU will actually send them. There are three options we need to look at: ! PEG Active ! Events ! Inbnd Msg PEG Active turns on the event processing routines inside the LMU. This option must be checked in order to event think about having the LMU send in event reports.
Page 50
The Events option enables or disables the actual sending of reports. So the PEG could be active (i.e. timers are running, counters are counting, etc) but nothing actually is done about the state changes. Inbound Messaging enables or disables the ability to receive user messages (i.e. as discussed with the MDT, GSD and Long Message modes). Unlike the first two options, this one is not necessary if you are looking just for event reports. All three options are defaulted on and can be modified in the Service Tab of LMU Manager.
Network Configuration
There are several configurations within the LMU that can control what wireless network providers it will register to. Side Preference (CDPD only) When cellular systems were first rolled out in North American, it was decided that there would only be two carriers in a given market/city, an A side carrier and a B-side carrier. Note that A and B refer to the actual frequencies the mobile will look at. Side preference does not know who the carrier is. The side preference settings in a mobile can be one of four values: ! A-Side Only This means that the mobile will only look on the Aside frequencies for service. ! B-Side Only The mobile will only search the B-Side frequencies for service. ! A-Side preferred (DEFAULT) The mobile will first search the ASide for service, then, if it is unable to find or register to service, it will search the B-side. ! B-Side Preferred The LMU will search the B-side first, then look at the A-side. Network Discriminants Network discriminant values are used to prefer or restrict access to a particular carrier. (i.e. unlike setting a side preference, Network Discriminants look at who the carrier is as opposed to what frequencies are being used.) Depending on the network being employed up to four different discriminants can be set with the following options:
Page 51
Type: The Type is the network identifier the LMU will look at to determine who it is trying to register to. o None (All networks) The network discriminant will not be used. o SPI (CDPD & iDen) Service Provider Identifier o SPNI (CDPD only) Service Provider Network Identifier o WASI (CDPD only) Wide Area Service Identifier Condition The condition tells the LMU how it should react for the specified Type o Ignore The Value of the Type is ignored o Required The value for the specified type must the Value stored in the LMU in order to register to the wireless network. o Preferred Like side preference, the LMU will first attempt to find the wireless network that match the stored Type and Value. If it cannot find it, it will register to whatever provider is available. o Exclude. The LMU will not register to networks with the same Value for the specified Type. Value This is the numeric value of the discriminant.
Network Sleep (CDPD) Various wireless networks employ their own sleep mode protocols. These should be Disabled at all times within the LMU as they can interfere with its normal operation. If you are concerned about power management, the LMU has its own sleep mode which can be set up in the PEG script. NEI Cycling The CDPD LMU has the capability of storing up to three different IP addresses to allow it to register with three different CDPD carriers. This is used when carriers do not have roaming agreements with each other. The IP addresses are stored in indexes (0,1 and 2). You can program the IPs through the IP Prov tab of LMU Manager remember that index 0 is the default IP address of the LMU (ie the one we programmed in the Quick Page 52
Start section). Note that the CDPD modem needs to reset after each IP address is programmed. There will be a several second delay while this occurs. You cannot program any modem parameters while this process takes place. This option is enabled in the Access Tab by clicking the NEI cycle option. Finally you will need to set a timer in S-Register 129. This time is based in minutes and is defaulted to 12. When this option is enabled, the LMU will change its IP address to one in the next index value every S129 minutes. When the mobile finds a CDPD service it can register to it will stop cycling IP addresses until it once again loses service.
GPS Configuration
The LMU has several GPS options that you can configure. Local LMU Time. The LMU has its own internal clock which is synchronized to the GPS system. By default, this clock works on GMT, however this may not be the most convenient way to reference events. To get around this, the LMU can be programmed with a local time offset and daylight savings so events can be referenced in its own time-zone (i.e. if you have an LMU in California you can program events based on PST instead of adding in an 8 hour difference). Remember that these settings only apply to the LMU, reports received by LM Exchange will have their own formatting based on the LM Exchange config file. Both the local time offset and daylight savings enable are located on the Service Tab. GPS Lost and Last Know Delay. The LMU has a delay between when the GPS receiver loses lock with the GPS system and when it updates the GPS status to Last Known. There is also a delay as to when it lets the PEG know its lost GPS coverage. Both values are configured in the Service Tab of LMU Manager and are defaulted to 60 seconds.
Page 53
Section 5 PEG Overview

The Programmable Event Generator (PEG) is a software sub-system residing the in the LMU and Tethered Locator allowing integrators to customize the behavior of any TechnoCom unit. Customized behavior can include: ! Crossing boundaries such as parking lots or terminal perimeter ! Report when the state of a vehicles ignition, siren or door switch has changed ! Provide location updates based on time, distance, and heading ! Remotely trigger vehicle inputs (eg horns, radios, LEDs) PEG Events define the situation under which a certain action is to take place. For Example, send a report every 1000 meters. Each Event consists of 3 elements: ! Triggers: the cause of the event ! Condition: (optional) the state in which the event can occur ! Action: the result of the event There are currently 41 Triggers, 24 Conditions, and 44 Actions that can be used to create up to 80 Events
PEG Settings (a.k.a. Trigger Parameters)

The PEG can be programmed with a variety of thresholds and settings which can be referenced by the Triggers, Conditions and Actions of a PEG Event. Values are set in the Trig PArams tab unless otherwise noted. They are as follows: Moving Speed Threshold The Moving Speed Threshold defines when the vehicle is considered to be moving and when it is considered to be stopped. By default this is set to 3 miles per hour which takes into account any false speed readings do to GPS drift. This value is stored in the LMU in cm/s allowing for 2 decimal places of accuracy in your settings. Because the conversion is done by the LMU, the value displayed may be slightly off what you programmed (i.e. setting 4 miles per hour is reported as 3.98). This value is set in the Service Tab of LMU Manager. Wake Up Monitor The wake-up monitor is used when the LMU is employing its sleep mode. The LMU will monitor eight different hardware lines. When any one of Page 54
these lines transitions (i.e. moves from high to low or low to high) the LMU will wake up. The lines being monitored are: ! Ignition ! Inputs 1, 2 and 3 ! The Test line ! The host serial port inputs to the LMU (DTR, RTS, RxD) Be advised that it takes several seconds for the LMU to boot back up, and reacquire GPS and wireless data service. Which lines are being monitored can be configured in the Service Tab of LMU Manager. Timer Timeouts The LMU can store up to sixteen different timer values to be used in PEG Events. These are unsigned 32 bit values. The values are in second and represent a count down value. Timers must be started in order to be active. You can look at the current state of an active timer in the Stats tab of LMU Manager. By default all timers are set to 0. Time-of-Day The Time of Day settings represent a start time for an Event as well as a repeat cycle. For example, say you wanted to send a report on the hour, every hour while tracking your vehicle. In this case you would set up a time of day profile to start (say at midnight) then repeat every hour. Respectively, the values displayed in LMU manager are in seconds and hours for the time of day and cycle time. Up to four different time of day parameters can be defined. They are all defaulted to 0. Time-Distance The Time-Distance parameter uses four values, a time, a distance, a heading and a minimum timer. When a specified profile is started, it will produce a trigger either when the time value expires, the vehicle has moved the distance, or changed its heading by the heading value. The minimum timer defines the minimum time between reports. While this timer is active, the LMU is essentially blocked from detecting all other events thereby preventing them from being processed. Once the timer has expired event reports can once again be processed. This timer is restarted every time an event report is sent. Keep in mind is that this timer applies to ALL outgoing event reports, not just those triggered by the Time-Distance values. Page 55
For example, say you have a Zone defined along with the Time-Distance profile and right before we exit the zone we get a Time-Distance update kicking off the Min timer. We then leave the zone. If we return to the zone before the Min timer expires, we will get neither the Zone Exit nor the Zone Enter event (i.e. as far as the LMU is concerned, nothing has changed). If we stay outside the Zone and the Min timer expires we will get the Zone Exit event. This would once again kick off the Min timer beginning the cycle anew. This is the only trigger parameter that has a default setting other than 0. Time-Distance Parameter 0 will have the default settings of: ! 60 second timer ! 1000 meter distance ! 0 decimal degree heading ! 0 second minimum timer Input Trigger Controls These parameters allow you to apply debounce and delay timers to each of the four inputs (i.e. ignition and inputs 1-3). The values are: ! A debounce timer This timer is meant to prevent excessive input reporting if the input voltage is near the transition threshold (~2.5V). It represents the number of seconds the input line must be at a given state before the next transition will be reported. The default value for the debounce timers is 10 seconds. (i.e. a value of 5 would mean that the input line must be high for 5 seconds before the LMU will report an Input Low event) ! Input-High: the number of seconds the LMU will wait before reporting an Input High event. ! Input-Low: The number of seconds the LMU will wait before reporting an Input Low event. ! The index values of these parameters also reference the input. So Input Trigger Control 0 applies to the ignition line, input Trigger Control 1 applies to input 1, etc For example, say we set the debounce window to 10 seconds, the input high delay to 2 seconds and the input low delay to 5. The event sequencing would be as follows:
Page 56
Input Transitions High Debounce Timer Starts Input High Trigger (2s Delay)
Input trigger Controls 10 second debounce window 2 second Input high delay 5 second Input low delay
Debounce Timer Re-starts Debounce Timer Re-starts Debounce Timer Restarts Debounce Timer Restarts Input Low Trigger (5s Delay) Debounce Timer Expires Input Transistions Low Debounce Timer Starts
t=0s
t=5s
t=10s
t=15s
t=20s
t=25s
t=30s
Acc Max Counts There are sixteen accumulators in the LMU, each of them 32 bit unsigned numbers (i.e. max value of ~4.3 billion). The Max Counts parameter can assign a maximum value for each of these accumulators. When the max value is met or exceeded the LMU will generate a trigger. Like the Input Trigger Controls, the index value directly references the accumulator, so max count value 0 applies to accumulator 0. Speed Trig Controls The Speed trigger controls define up to four different speed thresholds the LMU can use to generate triggers. Like the Input Trigger Controls you can also define a debounce time, speed above delay and speed below delay. LMU Manager displays the speed values in Miles Per Hour, but they are stored in the LMU in cm/s. This allows us 2 decimal places of accuracy when defining speed thresholds. Input Equates Up to four different Input states can be defined. The decimal value of this trigger parameter represents a binary pattern where: bit 0 = input 1 Page 57
bit 1 = input 2 bit 2 = input 3 (e.g.: A value of 4 would mean that input 3 needs to be asserted and input 1 and 2 need to be de-asserted for the Trigger to activate.) Day Of Week. Up to 4 day of the week indexes can be defined. The numeric values displayed by the Trig Params tab are a binary representation of the days of the week. That is, bit0 = Sunday bit1 = Monday bit0 = Tuesday bit1 = Wednesday bit6=Thursday Bit5 = Friday bit6=Saturday (e.g. To set a trigger to activate only on Saturday and Sunday, the value displayed would be 65) The Day Of Week Trigger Parameter allows you to restrict PEG Events to occur only on specific days. Zone Definitions The LMU can create up to four geographic zones. To set up a zone, you specify the center point, then define distances to the top (North) edge of a rectangle and the distance to the right (East) edge. You can then add a debounce distance so as not to create excessive reporting from vehicles riding on the zones edge.
North Distance
East Distance Zone Boundary Center Point
Zone Definition
Page 58
A/D Thresholds The LMUs A/D can be assigned up to four threshold values. The values displayed in these fields are 32 bit numbers representing the voltage seen on the A/D. In most cases you will need to calibrate this number to your specific application. (i.e. take an A/D reading when the sensor is exposed to a known condition.)
Page 59
PEG Triggers
PEG Triggers define when an event occurs. They can either completely define event (such as Moving or Not Moving) or they require a reference to define an event (such as Speed Above Speed Trig Control 1). The following section describes each of the triggers and an example as to when they would be used. Not Active This turns the specified event off. Regardless of the Condition and Action settings, nothing will happen. Power Up This trigger occurs when the unit is powered on from a cold boot (i.e. someone has plugged in the unit for the first time). FORMAT Trigger: Power UP Trigger Parameter :None (0) EXAMPLE USAGE Turn on an LED driver (e.g. output 0) so we know the LMU has powered on. Wake UP The wake up trigger occurs when the unit comes out of sleep mode, either because the sleep timer expired or one of the wake-up lines was transitioned. FORMAT Trigger: Wake Up Trigger Parameter: None (0) EXAMPLE USAGE Send a report to the LM Exchange server so we know when the unit last woke up. Power Up or Wake Up This trigger combines the previous two, so that when ever the unit is power cycled, be it from sleep or a cold start, this event will occur. FORMAT Trigger: Power UP or Wake Up Trigger Parameter: None (0) EXAMPLE USAGE Start Time-Distance Profile 0 every time the unit is turned back on.
Page 60
Input High This trigger needs to reference an input. This trigger is fired when the specified input transitions from low to high (i.e. 0 to 12V) FORMAT Trigger: Input High Trigger Parameter: 0, or 1-3 (Ignition, Input 1, 2 or 3) EXAMPLE USAGE Say we have the door open detect circuit on input 2 we showed you in the Hardware Overview. The Input High event could be used to send a report indicating the door was closed. Input Low This trigger also requires an input line as a trigger parameter. It is fired when the specified line transitions from high (+12V) to low (0V). FORMAT Trigger: Input Low Trigger Parameter: 0 or 1-3 (Ignition, Input 1, 2 or 3) EXAMPLE USAGE Again we will use the door open detect circuit on input 2. This time, the Input Low event indicates that the door has been closed. Input Equate This trigger requires a reference to an Input Equate Trigger Parameter. It will be fired when all three inputs are in the specified states. FORMAT Trigger: Input Equate Trigger Parameter: 0-3 (Input Equate) EXAMPLE USAGE Say we have an installation in a police car of a 3W LMU with up all three input lines wired as shown in the Hardware Overview section. The relay is driven by a sensor which fires when the officers weapon is removed from the car. We want to know immediately that when the office removes his weapon, opens the door and hits the panic button. We would therefore set up input equate 0 to a value of 0 (all three lines are low for our situation). The Input Equate trigger would most likely cause an event report to be sent. Speed Above The Speed above trigger is set when the vehicle exceeds the speed reference by the Trigger Parameter. Remembering that the trigger parameter is the index value in the speed trig controls table, not the speed value itself. FORMAT Page 61
Trigger: Speed Above Trigger Parameter: 0-3 (Speed Trig Control) EXAMPLE USAGE Send a report every time the vehicle exceeds 65 miles per hour. Speed Below This trigger is fired when the vehicle speed meets or drops below the value referenced by the Trigger Parameter. FORMAT Trigger: Speed Below Trigger Parameter: 0-3 (Speed Trig Control) EXAMPLE USAGE Send a report in every time the vehicle drops below 65 miles per hour. This could be used in conjunction with the Speed Above so we know how long the vehicle was exceeding our speed limit. Zone Entry This event occurs when the vehicle enters the zone referenced by the trigger parameter. FORMAT Trigger: Zone Entry Trigger Parameter: 0-3 (Zone Definition) EXAMPLE USAGE We have defined a zone around a bus depot. When the bus returns to the depot we want the unit to stop reporting. We would most likely accomplish this by putting the LMU to sleep. Zone Exit The trigger occurs when the vehicle leaves the specified zone. FORMAT Trigger: Zone Entry Trigger Parameter: 0-3 (Zone Definition) EXAMPLE USAGE Using the same bus example as above, we would want to start our Time-Distance reporting profile when the bus left the depot. GPS Acquired This trigger occurs when the GPS receiver first synchronizes its clock with the GPS satellites. FORMAT: Trigger: GPS Acquired Trigger Parameter: None (0) EXAMPLE USAGE We have several status LEDs on the dash of the vehicle and we want to turn one on every time the LMU gains GPS coverage. Page 62
GPS Lost This trigger fires when the LMU loses GPS coverage after the GPS Lost Acq timer expires. FORMAT: Trigger: GPS Lost Trigger Parameter: None (0) EXAMPLE USAGE Using the same LED as above, we set it blinking every time we lose GPS coverage. Comm Acquired This trigger happens when the LMU has successfully registered to the wireless network. FORMAT Trigger: Comm Acquired Trigger Parameter: None (0) EXAMPLE USAGE Like the GPS, we have another LED in the vehicle to indicate wireless data coverage. It will turn solid when the LMU finds a registers to the network. Comm Lost When the modem loses the connection to the wireless network, this trigger will fire. FORMAT Trigger: Comm Lost Trigger Parameter: None (0) EXAMPLE USAGE The LED in the above example will turn off when the LMU loses its registration to the network. Ignition On This trigger will occur when the vehicles ignition line goes high. FORMAT: Trigger: Ignition On Trigger Parameter: None (0) EXAMPLE USAGE We want to start a time based accumulator when the ignition is turned on so we know how long the vehicle was operating. Ignition Off This trigger occurs when the ignition line goes low. FORMAT Trigger: Ignition Off Trigger Parameter: None (0) Page 63
EXAMPLE USAGE Using the above example we want to stop the timer counter and then send in a report with its value when the ignition turns off. Time-Distance Update This trigger occurs when either the timer, distance or heading values expire in the ACTIVE Time-Distance profile. Be advise that only one Time-Distance profile can be active at a time. FORMAT Trigger: Time-Distance Update Trigger Parameter: None (0) EXAMPLE USAGE Time-Distance Updates almost always are used to send in an event report. Timer Timeout This trigger occurs when the referenced timer reaches 0. FORMAT Trigger: Timer Timeout Trigger Parameter: 0-15 (Timer Timeouts) EXAMPLE USAGE Timer timeouts are used for a variety of purpose but one of the most common is a wait timer, say to fire a report if a vehicle has come to a stop for an extended period of time. Count Exceeded This trigger fires when an accumulator has exceeded its maximum value as specified in the Max Count Trigger Parameter. FORMAT Trigger: Count Exceeded Trigger Parameter: 0-15 (Accumulator Max Count) EXAMPLE USAGE Accumulators can be used either to count time (in seconds), distance (in meters) or the number of occurrences of other events. For this example, say youve started accumulator 1 as a distance counter and want to know every time the vehicle goes 5 km. We would set index 1 of the Max Count Trig Parameter to 5000. Time Of Day When the time of day (local to the LMU) matches the referenced Time Of Day trigger parameter this trigger will occur. FORMAT Trigger: Time-Of-Day Trigger Parameter: 0-3 (Time of Day) EXAMPLE USAGE Page 64
One use of the Time of Day trigger is to start and stop other events. For instance, you could set up two time of day trigger parameters with a 24 hour repeat. One at the beginning of a shift (say 8:00am) and one and the end (say 6:00PM). You would use two Time of Day Triggers to start and stop your time-distance profile. Log Buffer Full This trigger fires when the LMUs log is approximately 90% full. FORMAT: Trigger: Log Buffer Full Trigger Parameter: None (0) EXAMPLE USAGE Generally the Log Buffer Full trigger is used as a warning. For example you would set a PEG flag that you would use as a condition to logging any data.. Host Data This trigger is not available. Log Send Failure This trigger occurs when the LMU has tried to send its log, but has been unable to do so (i.e. the Log Send Retry schedule has expired). FORMAT: Trigger: Log Send Failure Trigger Parameter: None (0) EXAMPLE USAGE This trigger is usually used to either kick off another Log Send attempt or to clear the log. Wake-Up on I/O The wake up trigger occurs when the unit comes out of sleep mode, because on of the hardware lines was transitioned. FORMAT Trigger: Wake Up on I/O Trigger Parameter: None (0) EXAMPLE USAGE Send a report to the LM Exchange server so we know when the unit last woke up. Wake-Up on Sleep Timeout The wake up trigger occurs when the unit comes out of sleep mode, because the sleep timer has expired. FORMAT Trigger: Wake Up on Sleep Timeout Trigger Parameter: None (0) Page 65
EXAMPLE USAGE Send a report to the LM Exchange server so we know when the unit last woke up. Message Sent This trigger occurs when a User Message (not an event report) of the specified type has been sent. FORMAT Trigger: Message Sent Trigger Parameter: 0-255 (Message Type) EXAMPLE USAGE This trigger is used to confirm that a user message as successfully sent from the LMU. Typical actions would be to increment an accumulator or send in an Event Report. Message Acknowledged This trigger occurs when the User Message of the specified type has been acknowledged. FORMAT Trigger: Message Acknowledged Trigger Parameter: 0-255 (Message Type) EXAMPLE USAGE This is typically used in conjunction with the Message Sent trigger to allow you to match the number of user messages sent to the number that were successfully received (i.e. acknowledged). Message Send Failure This trigger occurs when the user message of the specified type (i.e. the Trigger Parameter) is not received by the LM Exchange server. FORMAT Trigger: Message Send Failure Trigger Parameters: 0-255 (Message Type) EXAMPLE USAGE Again we would most likely use this in conjunction with an accumulator to count the number of times a User Message was sent, but did not make it to the LM Exchange server. Log Report Success This trigger occurs when the LMU has successfully sent its entire log to the LM Exchange server. FORMAT Trigger: Log Report Success Trigger Parameter: None (0) EXAMPLE USAGE
Page 66
This trigger is used to notify your script that the Log is now empty. A typical usage would be to clear any flags set due to Log Buffer Full triggers. Comm Shutdown This trigger occurs when the LMUs wireless modem is turned off. FORMAT Trigger: Comm Shutdown Trigger Parameter: None (0) EXAMPLE USEAGE This trigger is generally used as a warning or notification to let you script know the wireless modem is off. Setting a flag is a fairly common response to this trigger. Input Transition This trigger occurs when the specified input line transitions from one state to the other (i.e. moves from low to high or high to low). FORMAT Trigger: Input Transition Trigger Parameter: 0-3 (ignition, input 1, 2 or 3) EXAMPLE Say you have a switch hooked to input 1 on the LMU. You would use this trigger to send a report every time the switch went on or off. In this case your application would keep track of which state the switch was in based on the contents of the event report. Any Zone Entry This trigger occurs when the vehicle enters any of the four defined zones. FORMAT Trigger: Any Zone Entry Trigger Parameter: None(0) EXAMPLE USAGE Your LMU is installed in a vehicle that works out of three separate depots and you have setup zones defining each of the depots. You would use the Any Zone Enter trigger to know when the vehicle to notify your application that the vehicle had arrived at one of the depots. Any Zone Exit This trigger occurs when a vehicle leaves any of the four defined zones. FORMAT Trigger: Any Zone Exit Trigger Parameter: None (0) EXAMPLE USAGE
Page 67
With the example above, we would use the Any Zone Exit trigger to know when the vehicle had left any of the depots. Time Elapsed This trigger fires when the Timer of the active time-distance profile has expired. FORMAT Trigger: Time Elapsed Trigger Parameter: None (0) EXAMPLE USAGE This trigger is used when you are only interested in when the timer expires in a time-distance profile. It is generally used to help limit the number of event reports being sent. For example, condition the time-elapsed trigger with ignition off so you only get time based update when the vehicle is parked. Distance Traveled This trigger will occur when the distance portion of the active time-distance has been exceeded. FORMAT: Trigger: Distance Traveled Trigger Parameter: None(0) EXAMPLE USAGE Like the Time Elapsed trigger, this one is typically used to help limit the number of event reports being sent from the LMU. For example this trigger could be conditioned to send a report only when the vehicle is above a certain speed. Log Active This trigger is fired when the LMUs log becomes active (i.e. it occurs when an event report is first logged.) FORMAT Trigger: Log Active Trigger Parameter: None (0) EXAMPLE USAGE Log Active is typically used as a notification. For example we would set a flag that could be conditioned to with our Time-Distance update event. This flag would prevent Time-Distance events from being sent while the log was Active. This would help conserve log space until the log can be sent. Message Received When a user message of the specified type has arrived at the LMU, this trigger will fire. FORMAT Page 68
Trigger: Message Received Trigger Parameter: 0-255 (Message Type) EXAMPLE USAGE This trigger could be used as a type of acknowledgement (i.e. you send an event report) to let your application know its message was successfully sent. Any Message Received This trigger will occur when a user message of any type has arrived at the LMU, this trigger will fire. FORMAT Trigger: Message Received Trigger Parameter: None (0) EXAMPLE USAGE Again, this trigger could be used as a type of acknowledgement (i.e. you send an event report) to let your application know its message was successfully sent. Environment Change This trigger fires when any of the states reference in the specified Environment mask has changed. FORMAT Trigger: Environment Change Trigger Parameter: 0-7 (Environment Mask) EXAMPLE USAGE The Environment Change allows you to monitor for a variety of trigger without having to specify an event for each one. For instance, if you want to know when either the ignition goes on, any of the inputs transition or when the vehicle enters a specific zone you could use the Environment change. Keep in mind your application would need to determine which state has changed from the content of the event report. Heading Change This trigger occurs when the Heading portion of the active time-distance profile has been exceeded. FORMAT Trigger: Heading Change Trigger Parameter: None (0) EXAMPLE Like the Time Elapsed and Distance Traveled triggers this one can be used to limit the number of reports being sent by the LMU. Say, for instance, you defined a zone around the downtown region of a city. You can use this zone as a condition with this trigger so you only know when the vehicle is turning corners instead of watching it sit in traffic when the timer expires. Page 69
Special This is a special case trigger whos behavior is defined by the index value. FORMAT Trigger: Special Trigger Parameter: 0-255 (Special) EXAMPLE USAGE None Moving This trigger fires whenever the vehicle exceeds the moving speed threshold. FORMAT Trigger: Moving Trigger Parameter: None (0) EXAMPLE USAGE This trigger would be use to send a report whenever the vehicle starts to move. Not Moving This trigger fires whenever the vehicle drops to or below the moving speed threshold. FORMAT Trigger: Not Moving Trigger Parameter: None EXAMPLE USAGE This trigger would be use to send a report whenever the vehicle comes to a stop. A/D Above This trigger will fire when the A/D exceeds the value in the referenced A/D Threshold. FORMAT Trigger: A/D Above Trigger Parameter: A/D Threshold (0-3) EXAMPLE Say you have a temperature sensor in your vehicle. You would run the output of the sensor to the LMUs A/D input. You could then have the LMU send a report every time a specific temperature was exceeded. A/D Below This trigger will fire when the A/D drops below the value in the referenced A/D Threshold. FORMAT Trigger: A/D Below Page 70
Trigger Parameter: A/D Threshold (0-3) EXAMPLE Using the same example as above, this trigger would be used to send a report when the temperature drops below the specific temperature. Comm Connected This trigger will fire when LMU establishes a data connection to the wireless modem. Most commonly this will be used to detect an IP address change on networks that use dynamic IP assignment. FORMAT Trigger: Comm Connected Trigger Parameter: None Acc Below This trigger will occur when specified accumulator has dropped below the value referenced in the Accumulator Max Counts table. FORMAT Trigger: Acc Below Trigger Parameter: Accumulator Max Count Any Trig The Any Trigger trigger will occur when any other trigger occurs. The any trigger is typically used with the Jump, Call, Return, and End PEG Actions. FORMAT Trigger: Any Trigger Trigger Parameter: None
Page 71
PEG Conditions
Conditions are an optional component to Events. which are used in conjunction with Triggers to define when an event occurs. (E.g. only send reports when the vehicle is moving.) Conditions, like triggers may also need an index value to complete their definition. The available conditions are listed below. Examples will provided where needed. None No condition is applied to this event. FORMAT Condition: None Condition Index None (0) Ignition On The event will only occur when the ignition line is high. FORMAT Condition: Ignition On Condition Index: None (0) Ignition Off The event will only occur when the ignition line is low. FORMAT Condition: Ignition Off Condition Index: None (0) Moving This condition only allows events to occur when the vehicle is above the Moving speed threshold. FORMAT Condition: Moving Condition Index: None (0) Comm Available This condition requires that the modem be registered to the wireless network for the event to occur. FORMAT Condition: Comm Available Condition Index: None (0)
Page 72
Comm Not Available The event will only occur when the modem is NOT registered to the wireless network. FORMAT Condition: Comm Not Available Condition Index: None (0) GPS Acquired Events with this condition will only occur if the GPS receiver has valid fix. FORMAT Condition: GPS Acquired Condition Index: None (0) GPS Not Acquired This condition will only allow events to occur when the GPS receiver does not have a valid fix. FORMAT Condition: GPS Not Acquired Condition Index: None (0) Input High The specified input line must be high to allow the event to happen. FORMAT Condition: Input High Condition Index: 0-3 (Ignition, Input 1, 2 or 3) Input Low The specified input line must be low in order for the event to occur. FORMAT Condition: Input Low Condition Index: 0-3 (Ignition, Input 1, 2 or 3) Timer Active An event with this condition will only happen if the specified timer is currently running. FORMAT Condition: Timer Active Condition Index: 0-15 (Timer Timeouts) Timer Inactive Events with the Timer Inactive condition will only occur when the referenced timer is stopped. FORMAT Condition: Timer Inactive Page 73
Condition Index: 0-15 (Timer Timeouts) Time-Distance Active The specified time distance profile must be active for an event to occur. FORMAT Condition: Time-Distance Active Condition Index: 0-3 (Time-Distance) Time-Distance Inactive Events will only occur if the referenced Time-Distance profile is stopped. FORMAT Condition: Time-Distance Inactive Condition Index: 0-3 (Time-Distance) Day of Week The day must match the references day of week trig parameter in order for the event to occur. FORMAT Condition: Day of Week Condition Index: 0-3 (Day of Week) Flag Set Events will only happen when the reference PEG flag is set. FORMAT Condition: Flag Set Condition Index: 0-7 (PEG Flag) Flag Cleared The specified PEG flag must be cleared to allow the event to occur. FORMAT Condition: Flag Cleared Condition Index: 0-7 (PEG Flag) Log Active Events with this condition will only occur if the LMU is currently sending report information to the log. FORMAT Condition: Log Active Condition Index: None (0) Comm and GPS Available Both the wireless modem and GPS receiver must be registered to their respective network for this event to occur. FORMAT Page 74
Condition: Comm and GPS Available Condition Index: None (0) Environment In order for this event to occur, all the environment conditions specified in the mask must be true. FORMAT Condition: Environment Condition Index: 0-7 (Environment Mask) Environment Equate This condition requires two environment masks be set in specific pairs (0&4, 1&5, 2&6, 3&7). The first mask (0-3) defines which parameters are being looked at. The second mask (4-7)defines the state of each of those parameters. The condition will be true when the LMU matches the state of the second environment mask. FORMAT Condition: Environment Equate Condition Index: 0-3 (Environment Mask) Inside Time Of Day Window This condition is defined by two time-of-day profiles and two day of the week profiles (X&Y). If the local time of the LMU falls between these values, the condition is true and the event will occur. Condition: Inside Time of Day window Condition Index: See below
Page 75
Outside Time OF Day Window This condition is defined by two time-of-day profiles (X&Y) and two day of the week profiles (X&Y). If the local time of the LMU outside these values, the condition is true and the event will occur. Condition: Inside Time of Day window Condition Index: See below Time Of Day Window Calculation The time of day window Condition Index is a bit mapped number representing the two Time of Day Indexes and the two Day of Week Indexes. The number is generated as follows: Bit 00-01 Represent the Start Time of Day (0-3) Bit 02-03 Represent the Start Day of Week (0-3). Bit 04-05 Represent the Stop Time of Day (0-3) Bit 06 -07 Represent the Stop Day of Week. (0-3) So for instance, say we have the following settings: ! Time-Of Day, index 3, 8am (Start) ! Time-Of Day., index 0, 6pm (Stop ! Day-of-Week, index 2, Monday (Stop) ! Day of Week, index 1, Friday (Start) Our bit mapping would therefore look like: Bit 00-01: 11 (Start TOD in Index 3) Bit 02-03: 01 (Start DOW in Index 1) Bit 04-05: 00 (Stop TOD in Index 0) Bit 06-07: 10 (Stop DOW in Index 2) So our binary number would be 1000 0111 which means our Condition Index is 135.
Page 76
PEG Actions
PEG actions define what happens when an event occurs. Like the triggers and conditions, some Actions may require some additional information (i.e. an Action Parameter) to complete their definition. For example, you would need to specify which Timer to start. None No action will be taken FORMAT Action: None Action Parameter: None (0) Send Report This action causes the LMU to send an Event Report to the LM Exchange server as specified in the Inbound table. The LMU will attempt to send this report according to the retry schedule. If the report cannot be received, it is lost. Be aware that a successful message is acknowledged by the LM Exchange server and this will add to the total byte count for wireless network transactions. You also should be aware that the LMU will only attempt to send if Comm is available (ie the modem is registered to the wireless network). If Comm is not available, the message is immediately discarded. The Action Parameter defines the Event Code. Event Codes are user definable codes that allow you to classify incoming event reports. This allows your application to know the difference between when a report is sent because the vehicle stopped moving or if it was sent because of a time-distance update. You can define up to 256 (0-255) event codes reusing them in as many events as you wish. FORMAT Action: Send Report Action Parameter: 0-255 (Event Code) Log Report This action forces an event report in the LMUs log. The action parameter again defines the Event Code contained within the event report. FORMAT Action: Log Report Action Parameter: 0-255 (Event Code) Send-Log Report This action will first attempt to send an event report to the LM Exchange server. If it fails it will then place the report in the LMUs log. Like the Log Page 77
and Send Report actions, the Action Parameter defines the Event Code. Note that the Report will be logged immediately if Comm is not available FORMAT Action: Send-Log Report Action Parameter: 0-255 (Event Code) Send Log This action will attempt to send the entire contents of the LMUs log to the LM Exchange server specified in the Inbound list. If the send attempt succeeds, the log is deleted, otherwise the contents will remain intact. FORMAT Action: Send Log Action Parameter: None (0) Clear Log This action deletes the contents of the LMUs log. FORMAT Action: Clear Log Action Parameter: None (0) Stop Time-Distance This action will stop the active Time-Distance profile. FORMAT Action: Stop Time-Distance Action Parameter: None (0) Start Time-Distance When this action occurs the time-distance profile referenced in the Action Parameter will be started. If you start a time distance profile while another one is active, the old profile will be stopped automatically. FORMAT Action: Start Time-Distance Action Parameter: 0-3 (Time-Distance) Set Output This action will set the specified output line. If a line is already set and this action is issued, it will remain set. FORMAT Action: Set Output Action Parameter: 0-5 (Output 0, 1,2,3,4, or 5) Clear Output When this action is issued the referenced output will be cleared. This will stop both the Set and Blink actions. FORMAT Page 78
Action: Clear Output Action Parameter: 0-5 (Output 0, 1,2,3,4, or 5) Blink 1Hz Output This action will blink the specified output at 1 Hz (i.e. 1 blink per second). FORMAT Action: Blink Output , 1Hz Action Parameter: 0-5 (Output 0, 1,2,3,4, or 5) Blink 4Hz Output This action will blink the specified output at 4hz (i.e. 4 blinks per second). FORMAT Action: Blink Output, 4 Hz Action Parameter: 0-5 (Output 0, 1,2,3,4, or 5) Start-Restart Timer This action will start the referenced timer. If the timer is already active it will reset to its initial value and start over. FORMAT Action: Start-Restart Timer Action Parameter: 0-15 (Timer Timeouts) Stop-Pause Timer The referenced timer will be stopped at its current value when this action occurs. It has no effect on timers that are already stopped. FORMAT Action: Stop-Pause Timer Action Parameter: 0-15 (Timer Timeouts) Start Resume Timer This action will start a timer from is current value. It has no effect on a timer that is currently active. FORMAT Action: Start-Resume Timer Action Parameter: 0-15 (Timer Timeouts) Clear Timer The timer references in the Action Parameter will be reset to its original value. FORMAT Action: Clear Timer Action Parameter: 0-15 (Timer Timeouts)
Page 79
One-shot Timer This action starts a timer. Unlike the Start/Reset or Start/Resume actions, once the timer has expired it will stop. FORMAT Action: One-shot Timer Action Parameter: 0-15 (Timer Timeouts) Increment Accumulator The referenced accumulator will be incremented by 1 when this action occurs. FORMAT Action: Increment Accumulator Action Parameter: 0-15 (Accumulator) Clear Accumulator This action will clear the accumulator referenced in the Action Parameter to 0. FORMAT Action: Clear Accumulator Action Parameter: 0-15 (Accumulator) Power UP GPS This action will power the GPS receiver. Note that the GPS receiver powers automatically when the LMU is turned on or wakes from sleep. You should only need to use this action when your script has turn the GPS receiver. FORMAT Action: Power-Up GPS Action Parameter: None (0) Sleep Timer This action will place the LMU into sleep for the duration of the timer referenced in the Action Parameter. Unlike the Start Timer actions, you can start a 0 length timer for sleep mode. This will put the LMU to sleep until one of the hardware lines are transitioned. The sleep mode of the LMU turns off the GPS receiver and Wireless modem. You will be unable to remotely communicate with the LMU until it wakes back up. It takes approximately 15 seconds to save off the LMUs current settings (accumulators, input/output states, log sata) before it will power down. Also be aware that the unit will not fall asleep if there are pending transactions (i.e. it is trying to send an event report). FORMAT Action: Sleep Timer Action Parameter: 0-15 (Timer Timeouts) Page 80
Sleep Enable The Sleep Enable action enables (Action Parameter 1) or disables (Action Parameter of 0) the sleep mode of the LMU. When sleep is disabled the LMU will not sleep regardless of the settings of the Sleep Timer action. FORMAT Action: Sleep Enable Action Parameter: 0-1 (Disable-Enable) Sleep Until Time of Day This sleep action will put the LMU to sleep until the specified time of day. FORMAT: Action: Sleep Until TOD Action Parameter: 0-3 (Time of Day) Output Word This action sets the outputs to match the number in the Action Parameter. The number itself is bit mapped as follows: Bit 0 = Output 0 Bit 1 = Output 1 Bit 2 = Output 2 Bit 3 = Output 3 Bit 4 = Output 4 Bit 5 = Output 5 Bit 6 = N/A Bit 7 = N/A FORMAT Action: Output Word Action Parameter: 0-63 (Output Word) Start Time Accumulator This will star accumulating time in the specified accumulator with a 1 seconds LSB. It will keep counting until stopped. FORMAT Action: Start Time Accumulator Action Parameter: 0-15 (Accumulator) Start Distance Accumulator This action starts counting distance (in meters) in the specified accumulator. FORMAT Action: Start Distance Accumulator Action Parameter: 0-15 (Accumulator)
Page 81
Stop Accumulator This action will stop the specified accumulator at its current value. FORMAT Action: Stop Accumulator Action Parameter: 0-15 (Accumulator) Stop Clear Accumulator This action stops the specified accumulator and clears it back to 0. FORMAT Action: Stop-Clear Accumulator Action Parameter: 0-15 (Accumulator) Stop-Clear Timer This action stops the specified timer and resets it back to its initial value. FORMAT Action: Stop-Clear Timer Action Parameter: 0-15 (Timer Timeout) Set Flag The specified PEG flag will be set to True when this action occurs. FORMAT Action: Set Flag Action Parameter: 0-7 (PEG Flag) Clear Flag This action clears the specified PEG flag to False. FORMAT Action: Clear Flag Action Parameter: 0-7 (PEG Flag) Send Accumulator Report This tells the LMU to send a special report containing a specific number of accumulators. Unlike other Send Report actions, it does not have an Event Code. FORMAT Action: Send Accumulator Report Action Parameter: 1-16 (number of accumulators) Log Accumulator Report The LMU will log an accumulator report with the first N accumulators as specified in the Action Parameter FORMAT Action: Log Accumulator Report Action Parameter: 1-16 (number of accumulators) Page 82
Send-Log Accumulator Report Like the Send-Log Report action, this one will attempt to send the accumulator report to the LM Exchange server. If it fails, the report will be placed in the LMUs log. The action parameter represents the number of accumulators to report. FORMAT Action: Send-Log Accumulator Report Action Parameter: 1-16 (number of accumulators) Display Position This action will send a position report to the host serial port. The reports formatting will be: Msg,<UTC time-of day>,POS,<Event Code>,<Fix Time17>,<Latitude(dec degrees)>,<longitude(dec degrees)>,<heading>,<Speed(mph)>,<HDOP>,<# of Satellites>,<Fix Status18> FORMAT Action: Display Position Action Parameter: 0-255 (Event Code) Connect Comm This action attempts to connect to a wireless network. It is only valid for circuit switched systems. FORMAT Action: Comm Connect Action Parameter: None (0) Disconnect Comm This action will hang up the modem from a circuit switched connection. FORMAT Action: Comm Disconnect Action Parameter: None (0) Save Environment This command saves the LMUs status as would happen right before falling asleep. The environment settings that get saved by this command are dictated by S127.. FORMAT Action: Save Environment Action Parameter: None (0)
17 18
In seconds after Jan 1, 1980 Where 0 = real time, 1 = predicted, 2 = DGPS, 4 = last known, 8 = invalid, 16=2-D, 32= historic
Page 83
Report Alert Unsupported Send Special This action sends a special application specific message FORMAT Action: Send Special Action Parameter: 0-255 (Index Value) Move A/D to Accumulator This action will send the current A/D reading to the specified accumulator. Remember you will need to calibrate your A/D reading (i.e. apply a known voltage to the A/D input so you know what scale youre dealing with). Note, simply moving the A/D value into an accumulator will not cause a Count Exceeded Trigger. It is meant so you can read the A/D value in the next event report. FORMAT Action: Move A/D to Accumulator Action Parameter: 0-15 (Accumulator) Send Log Status This action will send a Log Status report to the LM Exchange server. The Log Status report details how many records are currently in the log and how much free space is left. FORMAT Action: Send Log Status Action Parameter: None (0) Send Unacknowledged Report This action will send an Event Report that does not get acknowledged by the LM Exchange server. The message will only be sent once. If it cannot be delivered on the first try it will be lost. FORMAT Action: Send Unacknowledged Report Action Parameter: 0-255 (Event Code) Send TAIP Report This action will send a TAIP string with an optional ;EV=<eventcode> extension. The complete formatting of this message is defined by the TAIP ENABLES and TAIP MSG settings. The destination is defined by the TAIP REMOTE ADDRESS and PORT settings. Action: Send TAIP Report Action Parameter:0-255 (Event Code)
Page 84
Accumulator Start Max Speed This action will place the max speed of the LMU in the specified accumulator. Note that this value will be presented in cm/s. Action: Accumulator Start Max Speed Action Parameter:0-15 (Accumulator) Accumulator, Start A/D This action will sample the A/D reading into the specified accumulator at a rate of 1 Hz. Note that this value is based on a 38.5mV LSB Action: Accumulator Start A/D Action Parameter:0-15 Accumulator) Accumulator, Decrement This action will decrease the value in the specified accumulator by 1. Remember that the accumulator will wrap to 4294967296 if decremented past 0. Action: Accumulator Decrement Action Parameter:0-15 Accumulator) Send Maintenance Report The Send Maint. Action will send an ID Report to the address(es) listed in the Inbound Retry list from the MAINTENACE port (20210) of the LMU. This is to allow users to open up temporary holes in firewalls to submit LMU Manager requests. Action: Send Maintenance Report Action Parameter: None Jump This action will force the PEG script to jump to a specific index value. Only forward jumps are supported. Action: Jump Action Parameter:0-149 Event Index Call This action emulates a function call and requires an accompanying Return action. This will force the PEG script to jump to a specific index while remembering the index it came from. When the Return is issued the PEG script will continue processing from the CALL index. Action: Call Action Parameter:0-149 Event Index
Page 85
Return This action will force the PEG script to return to the index of the last CALL action used. Action: Return Action Parameter: None End This action will force the PEG script to stop processing its index list until the next trigger is fired.. Action: End Action Parameter: None
Page 86
PEG Scripting
Programming a PEG script is similar to programming a VCR. You have a limited number of choices of what you can do (triggers and conditions versus. start/stop times and channel numbers) and have some specific rule on when youre allowed to do them (you cant record two TV shows at once versus only being able to run on Time-Distance profile at once.) For the most part we will look at how to program PEG Scripts through example (three of them specifically) but before we begin there are two timing rules you should keep in mind. ! PEG Events are processed in index order (0-79) ! PEG Trigger Parameters/Condition Indexes are also processed in index order. (i.e. speed index 0 is looked at before speed index 1, etc) PEG Example 1 Our customer has come to us asking for an AVL solution that can do the following: ! They need to know when and where the vehicle was when the ignition goes on and off ! They only want reporting when the vehicle is on ! The LMU is to fall asleep after the vehicle is turned off ! They want updates every 60 seconds or 800 meters ! They want to know when the vehicle enters and leaves the depot ! They want to know how far the vehicle has traveled ! They want to know how long the vehicle has been on. Our first step in designing a script is to determine what data needs to be sent. Out customer is looking for 7 pieces of information. The Ignition on/off times, the time-distance updates, the zone entry/exit for his depot, how long the vehicle has been on and how far its traveled. The last two should be fairly easy to deal with since they can be stored in accumulators using the Start Time and Start Distance accumulator events. We will therefore customize our report options to send in the first 2 accumulator values (0 and 1) every time. The other five requirements can be given an event each. We can go ahead an assign each an event code before we start programming. ! Code 1: Ignition On ! Code 2: Ignition Off ! Code 3: Time-Distance ! Code 4: Zone Exit ! Code 5 Zone Entry Page 87
When we program these events we will keep them in this same order. Notice that were placing ignition on before ignition off and zone exits before zone entries since that is the order we expect them to happen during the day. Now that we know what data we are sending, we should look at what Trigger Parameters we will need. The first is the Time-Distance of 60s and 800m. We will place this in index 0. Time-Distance Index 0 - 60s, 800m, 0deg, 0s Next we will need two timers to control the sleep mode; one as a wait timer and the other as how long well sleep for. We dont want the LMU to be on very long after the vehicle turns off but we also want to make sure one more event report goes out after the vehicle has stopped. We will use a ninety second timer for the wait cycle. Since we dont want the LMU to wake up until the next day when the vehicle turns back on, we will use a 0 second timer. Timer Timeouts Index 0 90 seconds Index 1 0 seconds Our final Trigger Parameter will be the depot zone. We will use index 0 here. Remember we need to know the center point and width/length measurements of the depot. Zone Definitions Index 0 <lat>,<long>,<east>,<north>,<hysterisis> We can now start programming our script. In general it is best to group events by category just to make it easier to decipher when you look at the script later. In this case we will use three groupings 1. Event Reports 2. Event Control (ie starting and stopping timers/accumulators/profiles) 3. Power Control / Sleep Our vehicle is going to be working solely within a city so we can probably assume it wont be going out of wireless network coverage for any extended periods of time. This means we dont need to worry about logging data, thus our send events would look like:
Page 88
Index 0 1 2 3 4
Trigger Ignition On Ignition Off Time-Dist Update Zone Exit Zone Entry
Trig Param None None None 0 0
Condition None None None None None
Condition Index None None None None None
Action Send Report Send Report Send Report Send Report Send Report
Action Param 1 2 3 4 5
Next we need to set starting and stopping events for our accumulators and our Time-Distance profile. Remember that we want to stop anything critical before going to sleep. We will use the ignition events (on and off) for most of the controls with the exception of the distance accumulator in case the vehicle is moved while the ignition is off. We will skip a couple of indexes in the event list so things do not run together when we look at this in LMU Manager.
Index 7 Trigger Ignition On Trig Param None Condition None Condition Index None Action TimeDistance Start TimeDistance Stop Start Distance Acc Start Time Acc Stop Acc Action Param 0
Ignition Off
None
None
None
Power-Up or Wake Up Ignition On Ignition Off
None
None
None
10 11
None None
None None
None None
1 1
Finally we want the sleep controls put in. We will put in an extra line in case the unit wakes up on something other than the ignition.
Index 14 Trigger WakeUp Trig Param None Condition Ignition Off Condition Index None Action Timer Start Restart Timer Start Restart Sleep (Time) Action Param 0
15
Ignition Off
None
None
None
16
Timer Timeout
None
None
Page 89
PEG Example 2 In our second example our customer has asked for a PEG script set up so they can run the LMU off an external battery (they will be supplying the battery and interfacing to the LMU). The requirements are as follows: ! Need reporting every 5 minutes or every 8 kilometers only when the vehicle is in motion. ! When the vehicle is stopped they want a 20minute sleep cycle where the unit wakes up for a few minutes. If the vehicle does not start moving in those four minutes the LMU should fall back asleep. ! We would also like to know when the unit wakes up and when its about to sleep. Again we will start with what data we want to send. In this case we only have three things. ! Code 1 Unit is waking up ! Code 2 Unit is about to sleep ! Code 3 Time-Distance Next we need our Trigger Parameters. Time Distance Index 0 600s, 8000m, 0deg, 0s Sleep Timers Index 0 240s (4 minute wait time) Index 1 1200 (20 minute sleep) We will again use the same categories as last time 1. Event Reporting 2. Event Control 3. Power Control / Sleep There are a couple of things to note in this reporting scheme. First off, we want to make sure we get every time-distance update, so we use the Report Send/Log Action. We do want to know when the unit woke up, but we do not want to be consuming battery power to do it. We will give it the basic Send Report to limit the amount of time the transmitter is active. Notice that we have not put in the going to sleep report yet. This is because we have yet to deal with the sleep timer.
Index 0 1 Trigger WakeUp Time-Distt Update Trig Param None None Condition None None Condition Index None None Action Report Send Report Send/Log Action Param 1 3
Page 90
Our Event control would look like:

Index 3 4 Trigger Power UP or WakeUp Wake-Up Trig Param None None Condition None None Condition Index None None Action Time-Dist Start Start Restart Timer Start Restart Timer Action Param 0 0
TimeDistance Update
None
Moving
None
And finally our sleep controls where we send the going to sleep notification and then fall asleep.
Index 7 8 Trigger Timer Timeout Timer Timeout Trig Param 0 0 Condition Not Moving Not Moving Condition Index None None Action Report Send Sleep (time) Action Param 3 1
Page 91
PEG Example 3 For our third example we will get a little more complicated. Our customer has asked for the following requirements for their AVL solution: ! The vehicle requires a panic button ! The vehicle will be working out of a single depot, so we need to know when it enters and exits ! We want to know how long the vehicle has been on, and how long it has been off ! We would like to know how much time the vehicle has spent moving ! We need to know when/if the vehicle is speeding ! The vehicle should only sit at its scheduled stops for a certain period of time (10 minutes). We need to know if the vehicle exceeds that time. ! We want to know when the vehicle starts to move ! Want to be alerted when the GPS receiver goes in and out of coverage ! Know when the unit last powered up ! We need to know how far the vehicle has travelled ! We also need a basic Time-Distance report as well as power control on sleep. Once again we will start by making a list of the events we need to capture ! Code 1 Ignition On ! Code 2 Ignition Off ! Code 3 Time-Distance Update (Time expires) ! Code 4 Time-Distance Update (Distance exceeded) ! Code 5 GPS Lost ! Code 6 GPS Acquired ! Code 7 Alert (Input 1 High) ! Code 8 Zone Exit (Leaving Depot) ! Code 9 Zone entry (entering Depot) ! Code 10 Speeding ! Code 11 Stopped Speeding ! Code 12 Vehicle Stop (stop time exceeded) ! Code 13 Vehicle is moving ! Code 14 Power up / Reset Now onto our Trigger Parameters: First we need our time distance update. The customer hasnt given us any specifications so we will stick with the LMUs default of 60s and 1000m Time-Distance Index 0 = 60s, 1000m, 0deg, 0s Page 92
Like our first example we will use two timers to control sleep, one to countdown to sleep and the other the sleep duration. Timer Timeouts Index 0 90 seconds Index 1 0 seconds We need our speeding threshold and give it a 10 second debounce window. Speed Trig Control Index 0 65mph 10s, 0s, 0s We will need 5 accumulators: Accumulator 0 Odometer function (ie count distance) Accumulator 1 Windshield Time (i.e. how long the vehicle was moving) Accumulator 2 Vehicle On time Accumulator 3 Vehicle Off time Accumulator 4 Stop time. Because we want to know if our vehicle has sat at a stop for more than 10 minutes we will need to assign a Max Counts Trigger parameter to index 4. Remember the time accumulators count seconds. Max Counts Index 4 600 We need to define our depot borders with a zone definition: Zone Definitions Index 0 <lat>,<long>,<east>,<north>,<hysterisis> Our Alert button will be tied to input one, and will be wired in such a way that an Input High event will indicate that the button has been pressed. And finally we are going to use a flag to indicate that the vehicle has sat at a stop too long. We will condition this with our moving and an ignition off reports. This will be to ensure that we dont send out any moving events without having a corresponding stopped event. Once again we will start our PEG script with the event reports:
Page 93
Index 0
Trigger Ignition on
Trig Param None
Condition None
Condition Index None
Action Report Send / Log Report Send / Log Report Send / Log Report Send / Log Report Send / Log Report Send / Log Report Send / Log Report Send / Log Report Send / Log Report Send / Log Report Send / Log Report Send / Log Report Send / Log Report Send / Log Report Send / Log
Action Param 1
Ignition Off
None
None
None
TimeElapsed Distance Traveled GPS Lost
None
Ignition On
None
None
Ignition On
None
None
None
GPS Acquired Input High
None
Ignition On
None
None
Zone Exit
None
Zone Entry
None
Speed Above Speed Below Count Exceeded Moving
None
10
10
Ignition On
None
11
11
Ignition On
None
12
12
None
Flag Set
13
13
Ignition Off
None
Flag Set
13
14
Power-Up
None
14
There are a couple of features to note with the event reports. First we have decided to limit some of our events to where the ignition is on. This is mostly to cut down on unnecessary data traffic. However, in Event Index 11, we use it to make sure we dont send in any stop reports while Page 94
the ignition is off (i.e. because the ignition is off, we know the vehicle has come to a stop for an extended period time). The other interesting point is index 12 and 13. Note that they both share the same event code. This is because either case means the same thing as far as our customer is concerned (i.e. the vehicle has come to a stop for an extended period of time). Next we will move on to starting and stopping our timers. First we need to start and stop our time distance profile. We will use the ignition to control this.
Index 16 Trigger Ignition on Trig Param None Condition None Condition Index None Action Start TimeDistance Stop TimeDistance Action Param 0
17
Ignition Off
None
None
None
None
Next we want to start our odometer. This will be a running total so long as the LMU remains powered.
Index 18 Trigger Power Up or Wake UP Trig Param None Condition None Condition Index None Action Acc Start Distance Action Param 0
Then comes our windshield time, which uses the Moving and Not Moving triggers. Notice that we dont clear this timer, but just stop it, so we maintain a running total.
Index 19 20 Trigger Moving Not Moving Trig Param None None Condition None None Condition Index None None Action Acc Start Time Acc, Stop Action Param 1 1
Our vehicle on and off times come next. Like the Windshield time these will be running totals.
Index 21 22 23 24 Trigger Ignition on Ignition Off Ignition Off Ignition On Trig Param None None None None Condition None None Ignition On Ignition On Condition Index None None None None Action Acc, Start Time Acc, Stop Acc, Start Time Acc, Stop Action Param 2 2 3 3
Page 95
Finally we can look at the at stop accumulator. We will need to clear this timer where the vehicle comes out of a stop, or turns off. This should prevent any false stop event from being generated. Remember when we clear the accumulator we also need to clear the stop flag.
Index 25 26 27 28 29 30 31 Trigger Not Moving Count Exceeded Moving Moving Ignition Off Ignition Off Ignition On Trig Param None 4 None None None None None None None None None Condition Ignition On None Condition Index None None None None None None None Action Acc, Start Time Set Flag Acc, Stop Clear Clear Flag Acc, Stop Clear Clear Flag Acc, Start Time Action Param 4 0 4 0 4 0 4
And lastly we can program in our sleep functionality.

Index 34 Trigger Power-Up or Wake-Up Ignition Off Trig Param None Condition None Condition Index None Action Timer Start, Restart Timer Start Restart Sleep(Ti me) Action Param 0
35
None
None
None
36
Timer Timeout
None
None
Page 96
Section 6: TAIP Interface

Overview
The LMU TAIP interface was designed as a means for an LMU or TetheredLocator to provide location and status information to an application without requiring the LM eXchange middleware using formats based on the Trimble ASCII Interface Protocol. This is to allow the LMU and TetheredLocator to work as drop in hardware replacements for existing TAIP based solutions.
Modes of Operation
Standard Reporting Standard Reporting is initiated when the LMU is operational by sending a D or F qualifier message for the desired reporting message type (PV, LN, IO). Standard Reporting report messages are sent to the senders address of the last UDP packet received on the TAIP listening port. Standard Reporting will cease when the LMU is powered off or when the TAIP interface receives a null message (><) Standard Reporting will not automatically resume when the LMU is restarted. Directed Reporting Unlike Standard Reporting, Directed Reporting does not rely on receiving an initiation message from an outside source to begin operation. Once initiated, it will remain operational even after LMU restarts. Directed reporting must be disabled to stop it. To initiate Directed Reporting mode, the following must be set: ! Non-Volatile Reporting ! TAIP Remote Address (AT$APP CONFIG TAIP REMOTE ADDR <addr>) ! TAIP Remote Port (AT$APP CONFIG TAIP REMOTE PORT <port>) ! A message type must also be selected by using either a D and/or F qualifier messages or by setting the TAIP Message Select configuration parameter. (AT$APP CONFIG TAIP MSG <msg>) Directed Reporting can be disabled by sending a null message (><) to the LMUs TAIP listener port which zeros out the TAIP Msg Select configuration parameter. It can be resumed by sending a D or F qualifier message or by once again setting the appropriate bits in the TAIP Msg Select configuration parameter.
Page 97
PAD Mode Reporting Under Pad mode reporting the TetheredLocator (and only the TetheredLocator) will send the specified TAIP message to its modem serial port. It assumes that the device connected to its modem port will send the TAIP message to the desired location. That is to say, there is no delivery information provided in addition to the TAIP string(s). Unlike the other two modes of operation, this one is enabled by setting the modem selection register to 8 (ATS120=8). Also note that this mode requires directed reporting to be enabled as well as having a non-zero Remote IP address. Note that this setting has a quick setup command of: AT$APP CONFIG TAIP RADIO
Means of Reporting
Regardless of which mode the LMU or TetheredLocator is running, there are two means by which TAIP messages are generated. Note that both means can be in use at the same time. ! Frequency and Distance Reporting: Under this means, TAIP messages are generated based on the 0th Time-Distance profile. By default this means reports are sent every 60s or every 1000m. ! PEG Based Reporting: This means allows users to create a PEG script to control when TAIP reports are sent. To initiate a TAIP report users would pick the SEND TAIP Action for a given PEG event.
Supported Message Types

Position Velocity (PV) The LMU supports the full PV TAIP message. The format is as follows: >RPVAAAAACCCCCCCEEEEEEEEFFFGGGHI< Where: AAAAA = GPS Time of Day (seconds) CCCCCCC = Latitude (degrees) EEEEEEEE = Longitude (degrees) FFFF = Speed (mph) GGG= Heading (deg) H= Fix Status (0=2D GPS, 1 = 3D GPS, 6 = Directed, 9 = Unknown) I= Age (0 = No Fix, 1 >=10s, 2 <10s) Note the characters in bold imply a decimal point (i.e. MMMM = MMM.M)
Page 98
Long Navigation (LN) The LMU supports all the LN fields except the following: ! Vertical Velocity ! Number of Satellites Used ! Satellite ID ! IODE The LN format would therefore be: >RLNAAAAAAAADDDDDDDDDFFFFFFFFFFGGGGGGGGIIIIKK KKMMMMOOPPQQRRRRRRRRRRST< Where: AAAAAAAA = GPS Time (seconds) DDDDDDDDD = Latitude (deg) FFFFFFFFFF = Longitude (deg) GGGGGGGG = Altitude (feet) IIII = Speed (mph) KKKK = Vertical Speed (unsupported) MMMM = Heading (degrees) OO = Number of SVs used (unsupported) PP = SV ID (unsupported) QQ = IODE RRRRRRRRRR = Reserverd S= Fix Status (0=2D GPS, 1 = 3D GPS, 6 = Directed, 9 = Unknown) T= Age (0 = No Fix, 1 >=10s, 2 <10s) Note the characters in bold imply a decimal point (i.e. MMMM = MMM.M) Input and Output (IO) This is a modification of the TAIP spec. The IO message has the following format: >RIOAABBCCDD< Where AA = Ignition Status (FF=ON, 00=OFF) BB = Input 1 Status (FF=High, 00=Low) CC = A/D Converter reading (8 MSBs) DD = Output 0 State (FF=Active, 00=Inactive)
Page 99
Message Options The LMU supports the following optional additions to the above TAIP messages ! Append Checksum to Messages: This option attaches the twodigit hex checksum value formatted as ;*dd. ! Append ID to Messages: The four digit TAIP ID, as set by the AT$APP CONFIG TAIP ID command, is reported as ;ID=dddd ! Append <CR><LF> to end of messages: The Carriage Return and Line Feed characters are attached at the end of the TAIP message (ie after the <) ! Event code reporting: This option is an LMU specific extension to the TAIP interface and is reported as ;EV=<eventcode> where <eventcode> is the value of the Action Parameter of the Send TAIP event responsible for triggering the TAIP report. ! Input Status Reporting: This is another LMU specific extension to the TAIP interface. It is formatted as ;IN=<inputstatus> where <inputstatus> is a decimal value representing the states of input 0(ign) through input 5. The value is bit-mapped as bit0 ign (1=High, 0=Low) bit1 input 1 (1=High, 0=Low) bit2 input 2 (1=High, 0=Low) bit3 input 3 (1=High, 0=Low) bit4 input 4 (1=High, 0=Low) bit5 input 5 (1=High, 0=Low) For example, if the Ignition is on and all other inputs are low the <inputstatus> value would be reported as 1. If the inputs are in their default states (Ign Off, Input1-5=High) then the value would be 62. ! Accumulator Value Reporting: This option again is LMU specific an is formatted as ;ACC=<acc0>,<acc1>,<acc15> where <accn> is the decimal value of the nth accumulator. These settings are controlled with the AT$APP CONFIG TAIP MSG and AT$APP CONFIG TAIP ENABLES commands. TAIP Qualifiers The LMU supports the Q, F and D qualifiers for the three message types listed above. So long as the TAIP interface is enabled, Q can be used at any time to query for the desired message type. >QLN< >QPV< >QIO<
Page100
The F qualifier is used to command the TAIP interface to report the specified reporting message at the interval specified. For example, >FPV00300000< commands the LMU to report a PV message every 30 seconds. The epoch field in the F qualified sentence is not supported and is ignored. The D qualifier is used to command the TAIP interface to report the specified reporting message at the distance, max. interval and min. interval specified. For example, >DPV0010000002000060< commands the LMU to report a PV message every 60 seconds or 200 meters but not any more often than every 10 seconds. The epoch field in the D qualified sentence is not supported and is ignored. Note that while the D and the F qualifiers can be used together, the F qualifier will only modify the max interval and will not affect any other timemotion parameters set by a D qualifier or through a PEG setting.
USING TAIP
The TAIP interface creates a UDP listener on Port 21000 (default). This can be changed using the At Command AT$APP TAIP LISTEN PORT <port> or though the LM Exchange. The LMU will need to be restarted for the new listener port number to take effect. This port should be used as the destination for all incoming TAIP Qualifiers and is also used as the source for all outgoing TAIP messages. By default, TAIP reporting is implemented using the PEG Time-Distance trigger parameter, specifically profile 0. Whenever a D or F qualifier is received through the TAIP interface, the LMU will update and restart TimeDistance Profile 0. Be aware that this will override any existing PEG Time-Distance activities. Conversely, any PEG Time-Distance activities can override the TAIP D or F settings. TAIP will issue all enabled scheduled report messages whenever a PEG Time-Distance trigger is generated whether or not it was Time-Distance started by TAIP. The TAIP interface currently does not support filtering of received messages based on Vehicle ID. It does not verify the checksum of received messages. It also does not support the ability to set the Remote Address settings via the TAIP interface using an RA message.
Page101
Appendix A: HyperTerminal Configuration

Click the Start button, go to Programs, Accessories and Communications. Click the Hyper Terminal folder.
Double click the Hypertrm.exe icon
Name the connection LMU. Click OK.
Page102
Change Connect using to read Direct to ComX. Where X is the com port that the LMU is attached to. This will probably be Com1. Click OK.
Change Bits per second to read 19200. Click OK. You should now be connected directly to the LMU. Page103
Appendix B: Install New Modem

Click the Start button, go to Settings and click Control Panel. Double click the Modems icon.
Click the Add button Check Dont detect my modem; I will select it from a list.
Click the Next > button. Page104

Under Manufacturers choose: (Standard Modem Types) From Models select: Standard 19200 bps Modem.
Click Next >. Select the Communications Port that will be used by the LMU, most likely will be COM 1.
Click Next >.
When Windows has completed installing the modem, click Finish.
Page105
Appendix C: Configuring Dial-Up Networking

Create a New Connection Go to Start, Programs, Accessories, Communications, and click Dial-Up Networking. In the Dial-Up Networking window, double click the Make New Connection icon.
Name the connection LMU and select Standard 19200 bps Modem from the Select a device list.
Click Next >. Enter a Telephone number of 0. Ignore both the Area code and Country or region code.
Page106
Click Next >.
Click Finish. Configure the Connection In the Dial-Up Networking window, right click LMU and choose Properties.
Uncheck Use area code and Dialing Properties. Page107

Click the Server Types tab. Choose PPP: Internet, Windows NT Server, Windows 98 as the Type of DialUp Server. For Advanced options and Allowed network protocols, check only TCP/IP.
Click the TCP/IP Settings button. Click Server Assigned IP Address. Click Specify name server addresses19. If available, enter the Primary and Secondary DNS. Uncheck Use IP header compression.
The LMU was not intended to be an Internet access device, though it can be used as such. In order to accomplish this, at least a Primary DNS addresses is necessary. DNS addresses are generally supplied by the wireless service provider.
19
Page108
Click OK. Click OK to close the LMU window.
Connecting to LMU
In the Dial-Up Networking window, double click the LMU icon and click Connect. The User name and Password are not needed.
The connection should establish almost immediately. To verify the connection is active, look for the Dial-Up Networking icon in the Task Tray.
Page109
Appendix D: LMU Message Sizing Guide

Message exchanges fall into two categories: Inbound Request/Response and Outbound Request/Response. Messages initiated by the LMU such as Event Reports are Inbounds. Each successful Event Report Inbound exchange consists of an Event Report Request generated by the LMU plus a corresponding Acknowledge Response generated by LM Exchange. The retry logic will retransmit messages if the acknowledgement has not been received within the wait interval specified by the retry schedule. This may happen multiple times if the data link throughput is slow or unsuccessful.
Basic Event Report Message Sizing

Message Field Packet IP Header Packet UDP Header Packet Payload
Event Report Message
Byte Count 20 (overhead for all message types) 8 (overhead for all message types)
Basic Message Basic Options Mobile ID Altitude Comm Status Carrier Status Input/Output Status Extended Options Accumulator Status Zone States
Event Report Acknowledge
24 11 (Required for a dynamic IP based network) 4 4 4 4 4 (overhead if any extended options are used) 4*N (N=number accumulators reported) 4
Basic Message Basic Options Mobile ID
3 11 (Only appears if present in the Event Report Message)
The number of bytes sent for typical Event Report exchange that reported Comm Status and 1 Accumulator would be as follows: Event Report Request : 20(IP) + 8(UDP) + 24(BasicMsg) + 4(CommStatus) + 4(ExtendOptO/H) + 4(Accumulator) = -------------------------64 bytes
Page110
Acknowledge Response: 20(IP) + 8(UDP) + 3(BasicMsg)= -------------------31bytes Total Bytes = 64+31 = 95. Thus for a unit the is operational for 8 hours per day, 5 days per week, and reported a location every 15 minutes, the amount of data transferred per month would be approximately 61 Kbytes (4 messages per hour x 8 hours per day x 5 days per week x 4 weeks per month x 0.095 kilobytes per message).
Page111
Appendix E: Mounting Template
Page112
Appendix F: AT Command Set

Application Commands
Application commands are available to all LMUs. AT$APP ADDR?
This command queries the IP address of the LMU
RESPONSE: <IP Address> OK Applies to LMU Version: 3.0 and higher
AT$APP ACC SET <accumulator> <value>

Sets the accumulator <acc> to the specified value <value> <accumulator>
this value selects a specific accumulator. Values range from 0 to 7
Applies to LMU Version: 3.0 and higher
<value>
This <value> is used to set the specified accumulator. Values can range from 0 to 4294967296 RESPONSE: OK Applies to LMU Version: 3.0 and higher
AT$APP ACC?
Displays the current values in each of the 8 accumulators.

RESPONSE: Acc: <acc 0 count>, <acc 1 count>, <acc 2 count>, <acc 3 count>, <acc 4 count>, <acc 5 count>, <acc 6 count>, <acc 7 count> OK
AT$APP ADC?
This command returns the voltage of the A/D input line.
RESPONSE: ADC=<voltage> OK With an LSB of 0.0356V. The maximum range of the A/D is 36.5V
Applies to LMU Version: 4.0a and higher
Page113
AT$APP ADDR <IP Address>
Applies to LMU Version: 4.0b and higher
This command allows you to set an IP Address into the LMU or TetheredLocator. When you try to establish a Dial-Up networking session with an LMU or TetheredLocator, the PC requires an IP address. In some cases the TetheredLocator or LMU might not have an IP address (e.g.. When the TetheredLocator is not connected to a phone/modem). This command will enable you to program the LMU or TetheredLocator with a 'fake' IP address so the Dial-Up session can establish. Be aware the this IP DOES NOT change the IP of the wireless modem. Programming this IP address while the LMU or TetheredLocator has a valid IP from the wireless device will disrupt communications temporarily. <IP Address>
This is the IP address you wish to program into the LMU or TetheredLocator. RESPONSE: Addr <IP Address> OK
AT$APP ADDR INBOUND <IP Address>
Applies to LMU Version: 4.1f and higher
This command sets index 0 of the LMU's Inbound IP address list. It defaults the port to 20300. <IP Address>
The IP address of the LM Exchange. RESPONSE: Set Inbound Addr to <IP Address> OK
AT$APP ADDR INBOUND?
This command queries the IP address in index 0 of the Inbound IP Address list.
RESPONSE: Inbound Addr <IP Address> OK
Page114
AT$APP ADDR MODEM <IP Address>
This command allows you to program the wireless modem's IP address without entering pass thru mode. This command is only valid for Novatel Wireless Expedite based LMUs. <IP Address>
The IP address of the CDPD modem. RESPONSE: Set Modem Addr to <IP Address> OK COMM DISCONNECTED COMM CONNECTED <IP Address> The COMM messages indicate that the modem is being power cycled. You should not enter any modem based AT commands while this is occurring.
AT$APP ADDR?
Returns the IP address of the LMU
RESPONSE: <IP Address> OK
AT$APP CDPD?
Returns the CDPD status of the LMU.
RESPONSE: CDPD Chan:<CDPD Channel> RSSI:<signal strength> <Acquired / Not-Acquired> < Registered / Not-Registered>
AT$APP COMM CONNECT?

Queries the comm device to see if it is connected
RESPONSE: <CONNECTED / DISCONNECTED> OK
Page115
AT$APP COMM STATUS?

Gives a detailed report of the status of the CDPD modem
RESPONSE:
Registered : <Yes/No> Denied Reason : <CDPD Registration Error> Channel State : <Inactive/Active> Channel Acquired: <Yes/No> Link Established: <Yes/No> TEI : <number> Channel : <CDPD Channel number> RSSI : <signal strength> dBm Forward BLER : <FBLER %> Reverse BLER : <RBLER %> MDBS Busy : <BUSY %> Power Level : <CDPD power Level> Power Product : <CDPD Power Product> Receive Packets : <Total receive packets since last power up> Transmit Packets: <Total transmitted packets since last power up> Receive Bytes : <Total received bytes since last power up> Transmit Bytes : <Total transmitted bytes since last power up> SPI : <Provider SPI> SPNI : <Provider SPNI> WASI : <Provider WASI> Cell ID : <Cell Site ID> Area Color Code : <Cell Site Color Code> OK
AT$APP COMM?
Returns the CDPD status of the LMU.
RESPONSE: CDPD Chan:<CDPD Channel> RSSI:<signal strength> <Acquired / Not-Acquired> < Registered / Not-Registered>
AT$APP CONFIG ACCESS ENABLES?
RESPONSE: ACCESS ENABLES <enables> OK Where <enables> is a decimal representation of the follow 8 bit bit map: Bit 0: Ping Enable Bit 1: Over-the-air download enable Bit 2: Static Inbound Address Selection Bit 3: Random Inbound Address Selection Bit 4: NEI Cycle Bit 5 - Bit 7: reserved. Should be set to 0
Page116
AT$APP CONFIG ACCESS ENALBES <enables>

This command configures the LMU's access enables. <enables>
<enables> is a decimal representation of the follow 8 bit bit map: Bit 0: Ping Enable Bit 1: Over-the-air download enable Bit 2: Static Inbound Address Selection Bit 3: Random Inbound Address Selection Bit 4 : Enable NEI Cycle Bit5- Bit 7: reserved. Should be set to 0 RESPONSE: OK
AT$APP CONFIG ACCESS HOST <addresses>

This command sets the Host IP Address access list <addresses>
This field takes 4 values:
<address 0>, <address 1>, <address 2>, <address 3> Where each <address> is the hexadecimal representation of an IP Address. RESPONSE: OK
AT$APP CONFIG ACCESS HOST?

This command displays the host IP address list.
RESPONSE: ACCESS HOST <address 0>, <address 1>, <address 2>, <address 3> OK Where each <address> is the hexadecimal representation of an IP Address.
AT$APP CONFIG ACCESS SERVICE <addresses>

This command sets the Access Service IP address List <addresses>
<address 0>,<address 1>,<address 2>,<address 3> Where each <address> is the hexadecimal representation of an IP Address. RESPONSE: OK
Page117
AT$APP CONFIG ACCESS SERVICE?
RESPONSE: ACCESS SERVICE<address 0>,<address 1>,<address 2>,<address 3> OK Where each <address> is the hexadecimal representation of an IP Address.
AT$APP CONFIG CARRIER DISCRIM <discrim>
This command allows you to set up to four different carrier discriminants. <discrim>
This field takes the following format: <index>, <type>,<condition>,<id> Where index is the desired discriminant ranging from 0 to 3, <type> can be: 0 - Not Used 1 - SPI 2 - WASI 3 - SPNI <conditions can be> 0 - ignore 1 - Required 2 - Preferred 3 - Exclude and <id> is the value of the network discrim you wish to specify. RESPONSE: OK
AT$APP CONFIG CARRIER DISCRIM?

This command displays the carrier discriminator values.
RESPONSE: CARRIER CARRIER CARRIER CARRIER OK
DISCRIM DISCRIM DISCRIM DISCRIM
0,0,0,0 1,0,0,0 2,0,0,0 3,0,0,0
AT$APP CONFIG CARRIER SIDE <side pref>
This command sets the side preference of the LMU's CDPD modem <side pref>
This parameter takes a single value representing side preference: 1 - A Side Only 2 - B Side Only 3 - A Side Preferred 4 - B Side Preferred RESPONSE: OK
Page118
AT$APP CONFIG CARRIER SIDE?
This command displays the side preference used by the LMU's CDPD modem
RESPONSE: CARRIER SIDE <pref> OK Where <pref> can be: 1 - A Side Only 2 - B Side Only 3 - A Side Preferred 4 - B Side Preferred
AT$APP CONFIG CARRIER SLEEP <mode>
This command sets the CDPD sleep mode of the LMU's modem. Note, for the best operation this mode should be OFF. This command should NOT be used unless you are familiar with CDPD sleep and the sleep modes of the Novatel Wireless Expedite Wireless IP modem. <mode>
<mode> can be: 0 - Disabled 1 - Long Sleep 2 - Short Sleep 3 - Medium Sleep RESPONSE: OK
AT$APP CONFIG CARRIER SLEEP?
This command queries the current Network sleep mode of the CDPD modem. Note, for the best operation this mode should be OFF. This command should NOT be used unless you are familiar with CDPD sleep and the sleep modes of the Novatel Wireless Expedite Wireless IP modem.
RESPONSE: CARRIER SLEEP <mode> OK Where <mode> can be: 0 - Disabled 1 - Long Sleep 2 - Short Sleep 3 - Medium Sleep
AT$APP CONFIG DEFAULT
This command restores the CONFIG default parameters to Non-volatile memory.

RESPONSE: OK
Page119
AT$APP CONFIG DEFAULT ALL
This command restores all default values to non-volatile memory.

RESPONSE: OK
AT$APP CONFIG DEFAULT PARAM
This command restores the default Trigger Parameters to Non-volatile memory.

RESPONSE: OK
Page120
AT$APP CONFIG EMASK <emask>

This command will set the specified environment mask. <emask>
This parameter defines the environment mask. It is formatted as: <index/mask number>, <mask definition (32 bit hex)> From LSB to MSB the bit values for the mask are: Bit 0: Flag 0 Bit 1: Flag 1 Bit 2: Flag 2 Bit 3: Flag 3 Bit 4: Flag 4 Bit 5: Flag 5 Bit 6: Flag 6 Bit 7: Flag 7 Bit 8: Zone 0 Bit 9: Zone 1 Bit 10: Zone 2 Bit 11: Zone 3 Bit 12: Zone 4 Bit 13: Zone 5 Bit 14: Not Used Bit 15: Not Used Bit 16: Speed 0 Bit 17: Speed 1 Bit 18: Speed 2 Bit 19: Speed 3 Bit 20: DOW 0 Bit 21: DOW 1 BIT 22: DOW 2 Bit 23: DOW 3 Bit 24: Input 0 (ign) Bit 25: input 1 Bit 26: input 2 Bit 27:input 3 Bit 28: GPS Acquired Bit 29: Comm Acquired Bit 30: Log Active Bit 31: In-Motion RESPONSE: OK
AT$APP CONFIG EMASK CLEAR

This command clears all the environment masks back to 0.
RESPONSE: OK
Page121
AT$APP CONFIG EMASK SAVE
This command saves all set environment masks to non-volatile memory.

RESPONSE: OK
AT$APP CONFIG EMASK SET <emask>
This command writes the specified environment mask to volatile memory. <emask>
This parameter defines the environment mask. It is formatted as: <index/mask number>, <mask definition (32 bit hex)> From LSB to MSB the bit values for the mask are: Bit 0: Flag 0 Bit 1: Flag 1 Bit 2: Flag 2 Bit 3: Flag 3 Bit 4: Flag 4 Bit 5: Flag 5 Bit 6: Flag 6 Bit 7: Flag 7 Bit 8: Zone 0 Bit 9: Zone 1 Bit 10: Zone 2 Bit 11: Zone 3 Bit 12: Zone 4 Bit 13: Zone 5 Bit 14: Not Used Bit 15: Not Used Bit 16: Speed 0 Bit 17: Speed 1 Bit 18: Speed 2 Bit 19: Speed 3 Bit 20: DOW 0 Bit 21: DOW 1 BIT 22: DOW 2 Bit 23: DOW 3 Bit 24: Input 0 (ign) Bit 25: input 1 Bit 26: input 2 Bit 27:input 3 Bit 28: GPS Acquired Bit 29: Comm Acquired Bit 30: Log Active Bit 31: In-Motion RESPONSE: OK
Page122
AT$APP CONFIG EMASK?
This command quires the Environment mask settings of the LMU.

RESPONSE: EMASK 0,00000000 EMASK 1,00000000 EMASK 2,00000000 EMASK 3,00000000 EMASK 4,00000000 EMASK 5,00000000 EMASK 6,00000000 EMASK 7,00000000 OK Where the response format is: EMASK <index>, <mask definition (32bit hex)> From LSB to MSB the bit values for the mask are: Bit 0: Flag 0 Bit 1: Flag 1 Bit 2: Flag 2 Bit 3: Flag 3 Bit 4: Flag 4 Bit 5: Flag 5 Bit 6: Flag 6 Bit 7: Flag 7 Bit 8: Zone 0 Bit 9: Zone 1 Bit 10: Zone 2 Bit 11: Zone 3 Bit 12: Zone 4 Bit 13: Zone 5 Bit 14: Not Used Bit 15: Not Used Bit 16: Speed 0 Bit 17: Speed 1 Bit 18: Speed 2 Bit 19: Speed 3 Bit 20: DOW 0 Bit 21: DOW 1 BIT 22: DOW 2 Bit 23: DOW 3 Bit 24: Input 0 (ign) Bit 25: input 1 Bit 26: input 2 Bit 27:input 3 Bit 28: GPS Acquired Bit 29: Comm Acquired Bit 30: Log Active Bit 31: In-Motion
Page123
AT$APP CONFIG EVENT <event>

This command will write the specified event to the LMU <event>
This parameter will define the event. It's structure is as follows: <Event index>, <trigger>, <trigger index>, <condition>,<condition index>,<action>,<action parameter> RESPONSE: OK
AT$APP CONFIG EVENT CLEAR

This command clears the entire event list.
RESPONSE: OK
AT$APP CONFIG EVENT SAVE

This command saves any set events to non-volatile memory.
RESPONSE: OK
AT$APP CONFIG EVENT SET <event>
This command will set a specific event. Note that this event is stored in Volatile memory. It must be SAVED to be written to non-volatile memory <event>
This parameter will define the event. It's structure is as follows: <Event index>, <trigger>, <trigger index>, <condition>,<condition index>,<action>,<action parameter> RESPONSE: OK
Page124
AT$APP CONFIG EVENT?
This command displays the entire list of PEG events stored in the LMU.
RESPONSE: EVENT EVENT EVENT ... EVENT EVENT EVENT OK
0,00,000,00,00,00,000 1,00,000,00,00,00,000 2,00,000,00,00,00,000 72,00,000,00,00,00,000 73,00,000,00,00,00,000 74,00,000,00,00,00,000
The response structure is as follows: EVENT <Event index>, <trigger>, <trigger index>, <condition>,<condition index>,<action>,<action parameter>
AT$APP CONFIG GPSTIMERS <gpstimers>

This command allows you to set the GPS Trigger timers <gpstimers>
This field takes two values: <Loss Timer>, <Acquired Timer>
Where the <Loss timer> is the number of seconds the unit will wait before reporting a loss of GPS Acquisition and <Acquired Timer> is the number of seconds the unit will wait before reporting an GPS Acquisition RESPONSE: OK
AT$APP CONFIG GPSTIMERS?

This command displays the GPS Trigger timers.
RESPONSE: GPSTIMERS <Loss Timer>, <Acquired Timer> OK
Where the <Loss timer> is the number of seconds the unit will wait before reporting a loss of GPS Acquisition and <Acquired Timer> is the number of seconds the unit will wait before reporting an GPS Acquisition
Page125
AT$APP CONFIG INBOUND ACCUM

<accumulators >
This field takes up to 8 numbers: <value0>,<value1>,<value2>,<value3>,<value4>,<value5>,<value6>,<value7>, Where each <value> is a 16 bit number. The lower 8 bits (0-7) represent the Event Code and the upper 8 bits (8-15) represents the number of accumulators to return. RESPONSE: OK
AT$APP CONFIG INBOUND ACCUM?
RESPONSE: ACCUM <value0>,<value1>,<value2>,<value3>,<value4>,<value5>,<value6>,<value7>, OK Where each <value> is a 16 bit number. The lower 8 bits (0-7) represent the Event Code and the upper 8 bits (8-15) represents the number of accumulators to return.
AT$APP CONFIG INBOUND ADDR <addresses>

This command configures the Inbound IP Address list. <addresses>
<address 0>, <address 1>, <address 2>, <address 3> Where each <address> is the hexadecimal representation of an IP Address. RESPONSE: OK
AT$APP CONFIG INBOUND ADDR?

this
This command queries the inbound IP address list. Note that if any values appear in list they will take precedence over those found in the Service iP Address list.
RESPONSE: ADDR <address 0>, <address 1>, <address 2>, <address 3> OK Where each <address> is the hexadecimal representation of an IP Address.
Page126
AT$APP CONFIG INBOUND PORT <ports>

This command sets the inbound port list. <ports>
A port number must be specified for each of the Inbound IP addresses listed in the Inbound IP address list. <port 0> ,<port 1>,<port 2>,<port 3> Where each <port> is the port number corresponding to the IP address found in the Inbound IP Address list. (I.e. port 0 works with address 0) RESPONSE: OK
AT$APP CONFIG INBOUND PORT?
RESPONSE: PORT <port 0> ,<port 1>,<port 2>,<port 3> OK Where each <port> is the port number corresponding to the IP address found in the Inbound IP Address list. (I.e. port 0 works with address 0)
AT$APP CONFIG INBOUND RETRY <retry timers>

This command sets the retry timers logic for inbound messages <retry timers>
This field contains up to 6 timers representing the retry time (in seconds) between retry 1,2,3,4,5 and 6. <time0>, <time 1>, <time2>, <time 3>, <time4>, <time51> Where each <time> can range from 0 to 255 seconds RESPONSE: OK
AT$APP CONFIG INBOUND RETRY?
This command queries the Inbound retry timer list. Note that these values will take precedence over the Trans Retry timers.
RESPONSE: INBOUND RETRY <time0>, <time 1>, <time2>, <time 3>, <time4>, <time51> OK Where each <time> can range from 0 to 255 seconds
Page127
AT$APP CONFIG LOGRETRY <logretry>

This command sets the retry logic of the LMU. <logretry>
This value is made up of four fields: <ignition on wait time>,<ignition on retry count>, <ignition off wait timer>,<ignition off retry count> Where the Wait Timer is the amount of time (in seconds) between retries and the Retry Count is how many reties will be made. RESPONSE: OK
AT$APP CONFIG LOGRETRY?
this command displays the retry logic (i.e. how many times and how long) for sending a report before the LMU will log it.
RESPONSE: LOGRETRY <ignition on wait time>,<ignition on retry count>, <ignition off wait timer>,<ignition off retry count> OK Where the Wait Timer is the amount of time (in seconds) between retries and the Retry Count is how many reties will be made.
AT$APP CONFIG MDT <mdt>

This command sets the MDT enables. <mdt>
This is a decimal value representing a bit map of: bit0 - bit 2: inbound disposition ( 1: send, 2: send/log, 3: log, 4:alert) bit 3 Local Free Text enable RESPONSE: OK
AT$APP CONFIG MDT?

This command displays the MDT settings.
RESPONSE: MDT <value> OK
Where value is a decimal representation of a bit map as defined by: bit0 - bit 2: inbound disposition ( 1: send, 2: send/log, 3: log, 4:alert) bit 3 Local Free Text enable
Page128
AT$APP CONFIG MOVESPEED <speed>
This command allows the configuration of the moving/Not moving speed threshold. <speed>
This parameter is the moving speed threshold expressed in cm/s NOTE: 1 mph = 44.7cm/s 1 km/h = 27.8 cm/s RESPONSE: OK
AT$APP CONFIG MOVESPEED?
This command displays the moving/not moving speed threshold

RESPONSE: MOVESPEED <speed> OK Where <speed> is expressed in cm/s
AT$APP CONFIG NULLMSG <interval>

Sets the interval of the NULL Message <interval>
Applies to LMU Version: 5.0d and higher
How often, from power up, the Null Message is sent to the currnet IP and Port being used in the Inbound Routing List RESPONSE: OK
AT$APP CONFIG OPTIONS <options>

This command sets the inbound Send and Log options <options>
This parameter consists of two decimal representation of the bit mapped values <send options>,<log options>. The bit map is formatted as: Bit 0: altitude Bit 1: Sat used PRN values for inverse DGPS Bit 2: Pseudo-ranges to Sats Bit3: Comm Status (RSSI, Channel, Availability) Bit 4: Carrier Info Bit 5: I/O Status Bit 6: reserved Bit 7: extended options (i.e. enable bits 8-15) Bit 8: Zone States Bit 9 - 11: The number of accumulators to report (000 = 0, 001 = 2, 010 = 4, 011 = 8, 100 = 1, 101= 3, 110=5, 111= 6) RESPONSE: OK
Page129
AT$APP CONFIG OPTIONS?
This command displays the inbound options included in an inbound report.

RESPONSE: OPTIONS <Send Options>, <Log Options> Both <Send Options and <Log Options> take the same bit mapped format: Bit 0: altitude Bit 1: Sat used PRN values for inverse DGPS Bit 2: Pseudo-ranges to Sats Bit3: Comm Status (RSSI, Channel, Availability) Bit 4: Carrier Info Bit 5: I/O Status Bit 6: reserved Bit 7: extended options (i.e. enable bits 8-15) Bit 8: Zone States Bit 9 - 11: The number of accumulators to report (000 = 0, 001 = 2, 010 = 4, 011 = 8, 100 = 1, 101= 3, 110=5, 111= 6)
AT$APP CONFIG PASSWORD MAINT <password>
This command sets the Maintenance port password. This value can not be read back once programmed. <password>
This value is the hexadecimal representation of an IP Address RESPONSE: OK
AT$APP CONFIG PASSWORD PRIMARY
This command configures the Primary port password for the LMU. It cannot be read back once programmed. <password>
This value is the hexadecimal representation of an IP Address RESPONSE: OK
Page130
AT$APP CONFIG SERVICE <service>
This command save the specified service enables settings to non-volatile memory. <service>
This parameter specifies the service enables. It is formatted as a decimal number representing a bit mapped value. The bit mapping is: bit 0: PEG enable bit 1: event reporting bit 2: inbound messaging bit 3: TAIP Interface RESPONSE: OK
AT$APP CONFIG SERVICE?

This command displays the service enables settings of the LMU
RESPONSE: SERVICE <enables> OK Where enables is an 8 bit value specified as: bit 0: PEG enable bit 1: event reporting bit 2: inbound messaging bit3: TAIP Interface
AT$APP CONFIG TAIP ENABLES <enables>

This allows you to set the TAIP configuration of the LMU <enables>
Where <enables> is represented by a 5 bit decimal number: bit0 - Append Checksum to messages bit1 - Append ID to Messages bit2 - Echo 'Set' Commands bit3 - Frequency Reporting bit4 - Append <CR><LF> to end of messages bit5 - enable directed reporting bit6 - enable Event code reporting bit 7 - enable Input Status Reporting RESPONSE: Set TAIP Enables to <enables> OK
Page131
AT$APP CONFIG TAIP ENABLES?

Displays the current TAIP settings of the LMU
RESPONSE: TAIP Enables <enables> OK Where <enables> is represented by a 5 bit decimal number: bit0 - Append Checksum to messages bit1 - Echo 'Set' Commands bit 2 - Frequency Reporting bit 3 - Append <CR><LF> to end of messages bit4 - enable directed reporting
AT$APP CONFIG TAIP ID <id>

This command allows you to set the TAIP ID of the LMU <id>
The four digit TAIP ID you wish to program into the LMU RESPONSE: Set TAIP Msg Select to <id> OK
AT$APP CONFIG TAIP ID?

This command queries the TAIP ID of the LMU
RESPONSE: TAIP Vehicle ID <id> OK Where <id> is the four digit TAIP ID of the LMU.
AT$APP CONFIG TAIP LISTEN PORT <port>
Sets the port being used by the LMU to listen for TAIP requests. <port>
The desired port number RESPONSE: Set TAIP Listen Port to <port> OK
Page132
AT$APP CONFIG TAIP LISTEN PORT?
Queries the LMU for which port it is listening on for TAIP requests.
RESPONSE: TAIP Listen Port <port> OK
AT$APP CONFIG TAIP MSG <enables>
This command allows you to configure the type of TAIP message formatting the LMU is using. <enables>
This decimal number is defined by the following format: bit 0: Send PV messages bit 1: Send LN messages bit 2: Send IO messages bit 7: enable Accumulator Reporting RESPONSE: Set TAIP Msg Select to <enables> OK
AT$APP CONFIG TAIP MSG?
This command determines what type of TAIP message the LMU is currently using.
RESPONSE: TAIP Msg Select <enables> OK Where <enables> is a decimal representation of a 3 bit number: bit 0: Report PV messages bit 1: Report LN messages bit 2: Report IO messages
Page133
AT$APP CONFIG TAIP RADIO
Applies to LMU Version: 5.0i and higher
This command automatically configures the LMU for TAIP-PAD mode. The following settings are changed: - Set S120 to 8 - Set TAIP message type to PV - Set TAIP Remote Address to 1.1.1.1 - Enable <CR><LF> - Enable CheckSum - Enable Non-Volatile Reporting - Enable TAIP Event Code Reporting - Enable TAIP Input State Reporting - Enable TAIP Accumulator Value Reporting NOTE: The LMU must be RESET for these settings to take effect.
AT$APP CONFIG TAIP REMOTE ADDR <ip
RESPONSE: OK
This command will set the remote IP address of the LMU used for directed TAIP reporting. <ip address>
The IP address of the server you wish to send TAIP messages to. RESPONSE: Set TAIP Remote Addr to <ip address> OK
AT$APP CONFIG TAIP REMOTE ADDR?
This command queries the remote reporting address used in directed reporting.
RESPONSE: TAIP Remote Addr <ip address> OK Where <ip address> is the IP of the server you wish to send TAIP messages to.
Page134
AT$APP CONFIG TAIP REMOTE PORT <port>
This command allows you to set the port being used by the directed reporting function of the LMU <port>
The port number the remote server is using to listen for TAIP messages. RESPONSE: Set TAIP Remote Port to <port> OK
AT$APP CONFIG TAIP REMOTE PORT?
This command queries the LMU for the port being used by directed TAIP reporting.
RESPONSE: TAIP Remote Port <port> OK
AT$APP CONFIG TPARAMS <parameter>
This command writes the specified trigger parameter to non-volatile memory. <parameter>
This field defines the specific trigger parameter. It can take the following forms: TIME-DISTANCE <index>,<time(s)><distance(m)>,<heading(dec deg)>,<minimum> TOD <index>,<TOD(seconds from 0:00) >,<repeat interval (sec)> TIMER <index>,<time(s)> ACCUMULATOR <index>, <count> SPEED <index>,<speed (mph)>,<debounce (s)>, <delay above (s)>, <delay below(s)> INEQUATE <index>,<value (lsb = input 0)> ZONE <index>, <lat (deg)>, <long (deg)>, <North/South (m)>, <East/West (m)>, <hysterisis (m)> WKDAY <index>,<WkDay (lsb = Sunday> INPUT <index/input>, <debounce(s)>, <delay high(s)>, <delay low(s)> RESPONSE: OK
AT$APP CONFIG TPARAMS CLEAR

This commands clears all trigger parameters to 0.
RESPONSE: OK
Page135
AT$APP CONFIG TPARAMS SAVE
This command moves any set trigger parameters from volatile memory to non-volatile memory.
AT$APP CONFIG TPARAMS SET <parameter>

only
RESPONSE: OK
This command will write the specified trigger parameter to volatile memory. It will be moved to non-volatile memory if a save command is issued. <parameter>
This field defines the specific trigger parameter. It can take the following forms: TIME-DISTANCE <index>,<time(s)><distance(m)>,<heading(dec deg)>,<minimum> TOD <index>,<TOD(seconds from 0:00) >,<repeat interval (sec)> TIMER <index>,<time(s)> ACCUMULATOR <index>, <count> SPEED <index>,<speed (mph)>,<debounce (s)>, <delay above (s)>, <delay below(s)> INEQUATE <index>,<value (lsb = input 0)> ZONE <index>, <lat (deg)>, <long (deg)>, <North/South (m)>, <East/West (m)>, <hysterisis (m)> WKDAY <index>,<WkDay (lsb = Sunday> RESPONSE: OK
Page136
AT$APP CONFIG TPARAMS?
This command queries all of the current settings for the trigger parameters.
RESPONSE: TIME-DISTANCE 0,60,1000,0,0 TIME-DISTANCE 1,0,0,0,0 TIME-DISTANCE 2,0,0,0,0 TIME-DISTANCE 3,0,0,0,0 TOD 0,0,0 TOD 1,0,0 TOD 2,0,0 TOD 3,0,0 TIMER 0,0 TIMER 1,0 TIMER 2,0 TIMER 3,0 TIMER 4,0 TIMER 5,0 TIMER 6,0 TIMER 7,0 TIMER 8,0 TIMER 9,0 TIMER 10,0 TIMER 11,0 ACCUMULATOR 0,0 ACCUMULATOR 1,0 ACCUMULATOR 2,0 ACCUMULATOR 3,0 ACCUMULATOR 4,0 ACCUMULATOR 5,0 ACCUMULATOR 6,0 ACCUMULATOR 7,0 SPEED 0,127,0,0,0 SPEED 1,127,0,0,0 SPEED 2,127,0,0,0 SPEED 3,127,0,0,0 INEQUATE 0,0 INEQUATE 1,0 INEQUATE 2,0 INEQUATE 3,0 ZONE 0,0,0,0,0,0 ZONE 1,0,0,0,0,0 ZONE 2,0,0,0,0,0 ZONE 3,0,0,0,0,0 ZONE 4,0,0,0,0,0 ZONE 5,0,0,0,0,0 WKDAY 0,0 WKDAY 1,0 WKDAY 2,0 WKDAY 3,0 INPUT 0,0,0,0 INPUT 1,0,0,0 INPUT 2,0,0,0 INPUT 3,0,0,0 OK
Page137
AT$APP CONFIG TRAN RETRY <retry timers>

This command configures the inbound retry timers. <retry timers>
Up to 6 retry timers can be configured: <time 0>,<time 1>,<time 2>,<time 3>,<time 4>,<time 5>
Where each <time> is a 4 bit value representing the number of seconds between each retry. RESPONSE: OK
AT$APP CONFIG TRAN RETRY?
This command displays the inbound message retry timers. Note that values stored with the AT$APP CONFIG INBOUND RETRY will take precedence.
RESPONSE: TRAN RETRY <time 0>,<time 1>,<time 2>,<time 3>,<time 4>,<time 5> OK Where each <time> is a 4 bit value representing the number of seconds between each retry.
AT$APP CONFIG TZONE <tzone>
This command writes the specified timezone configuration to non-volatile memory. <tzone>
This decimal number represents a bit map of the offset from GMT and daylight savings enable. It is formatted as follows: bit 0 - bit 4: time Zone OffSet (This is a 2's compliment signing, so -8 would be encoded as 11000) RESPONSE: OK
AT$APP CONFIG TZONE?
This command queries the LMU for it's current time zone configuration
RESPONSE: TZONE <zone> OK Where <zone> is a bit mapped value representing: bit 0 - bit 4: Time Zone OffSet bit 5: daylight savings (1 = enabled, 0 = disabled)
Page138
AT$APP CONFIG WAKEMON <monitor>

This command is used to configure the wake up monitor. <monitor>
This parameter is a decimal number representation the follow 8 bit bit map: Bit 0: ignition Bit 1: Input 1 Bit 2: Input 2 Bit 3: Input 3 Bit 4: Test Input Bit 5: Host port DTR Bit 6: Host port RTS Bit 7: Host port RxD RESPONSE: OK
AT$APP CONFIG WAKEMON?
This command displays the configuration of the wake up monitor.

RESPONSE: WAKEMON <monitor> OK Where <monitor> is an 8 bit decimal value representing the following bit map: Bit 0: ignition Bit 1: Input 1 Bit 2: Input 2 Bit 3: Input 3 Bit 4: Test Input Bit 5: Host port DTR Bit 6: Host port RTS Bit 7: Host port RxD
AT$APP DEBUG <state>
This command controls the state of the application debug messages <state>
This parameter can take on two states: ON - debug messages are passed to the host serial port OFF - debug messages are not displayed RESPONSE: OK
Page139
AT$APP DEBUG?
Queries the DEBUG mode of the LMU.
RESPONSE: DEBUG ON OK or DEBUG OFF OK
AT$APP EID?
Returns the Electronic Identification (EID) of the LMU. This command is only valid for CDPD units
RESPONSE: <EID> OK
AT$APP ESN read

Read the value of the ESN
RESPONSE: ESN: not available OK or ESN:<esn> OK
AT$APP ESN?
Query the ESN of the LMU
RESPONSE: ESN: not available OK or ESN:<esn> OK
Page140
AT$APP FLAGS?
Displays the current states of the PEG FLAGS. A set Flag will have a 1 value, a cleared flag will have a 0 value.
RESPONSE: Flags: 00000000 OK A set Flag will have a 1 value, a cleared flag will have a 0 value where Flag 0 is represented by the LSB
AT$APP GPRS CONTEXT <index>
Set the type of service and Access Point Name(APN) for a GPRS mobile. Up to two different service and APNs can be programmed <index>
0 or 1.
<Service>:<APN>
<Service> = IP or PPP <APN> = MyAPN.MyGPRSOperator.Com (as supplied by the GPRS operator) RESPONSE: Query: Context 0 IP:APN1.Carrier.Com Context 1 PPP:APN2 Set: OK OK
AT$APP GPRS CONTEXT INDEX <index>

Sets the active GPRS context. <index>
0 or 1 RESPONSE: Query: Context 0 IP:APN.MyCarrier.COM Context 1 IP:APN2 OK
Page141
AT$APP GPS <state> <debug level>

Controls the power and the mode of the GPS receiver <state>
ON - turns the GPS receiver on/ resets GPS receiver OFF - turns the GPS receiver off DEBUG - enables debug messages from the GPS receiver
<debug level>
This 16 bit value represents the debug level of the GPS receiver. It is bit masked as follows: Bit 0: Enables (1) / disables (0) GPS status with odometer function BIT 1: Enables (1) / disables (0) GPS position updates Bit 2: Enables (1) / disables (0) GPS debug Bit 3: Enables (1) / disables (0) the routing of the serial port handler debug out the GPS port RESPONSE: OK Applies to LMU Version: 3.0 and higher
AT$APP GPS?
Queries the status of the GPS receiver.

RESPONSE: Lat=<latitude>, Lon=<longitude>, Alt=<altitude> Hdg=<heading> Spd=<speed> <fix status> HDOP=<HDOP> nSats=<number of satellites> OK
AT$APP ID?
and IMSI). Equivalent to ATI1
This command displays the serial numbers of the LMU, Modem and User (ie ESN, IMEI
RESPONSE: ESN: <ESN> IMEI: <IMEI or EID> IMSI: <IMSI> ICC-ID:<ICC-ID> OK
AT$APP INPUT?
Queries the state of the 4 input lines of the LMU.
RESPONSE: Input States: W,X,Y,Z W = state of input line 3 (8 = high, 0 low) X = state of input line 2 (4 = high, 0 = low) Y = state of input line 1 (2 = high, 0 = low) Z = state of ignition (input 0) (1 = high, 0 low)
Page142
AT$APP LOG CLEAR
Clears the contents of the LMU's log. The RESET response will only be displayed if Log Debug is enabled.
RESPONSE: app[17:40:14] LOG Reset OK
AT$APP LOG FILL <code> <no. events>
Fills the entire log at the rate of 10 events per second until the specified number of events has been reached. <code>
OPTIONAL Each Log entry filled with this command will be tagged with <code>. This value can range from 0 to 255
<no. events>
This value specified the number of events the log will be filled with. Up to 64 events can be requested. RESPONSE: app[17:34:30] app[17:34:30] app[17:34:30] app[17:34:30] OK
Log Store Report: Buffer=0, Byte Count=24, WriteIndex=48 Log Store Report: Buffer=0, Byte Count=24, WriteIndex=72 Log Store Report: Buffer=0, Byte Count=24, WriteIndex=96 Log Store Report: Buffer=0, Byte Count=24, WriteIndex=264 Applies to LMU Version: 4.1f and higher
AT$APP LOG QFILL <record count>
This command fills the LMU's log with the specified number of records. <record count>
The number of records to be pushed into the LMU's log. RESPONSE: OK Applies to LMU Version: 3.0 and higher
AT$APP LOG?
Quires the status of the LMU's Log.

RESPONSE: LOG Status: Inactive, Batch, AckPendTmr=0, Retry=0 OK
Page143
AT$APP MOBID <mobileIDType>

Defined which value to use for the LMU's mobile ID <mobileIDType>
ESN - LMU's serial number IMEI - Serial number of the wireless device IMSI - subscriber ID USER - user defined MIN - phone number ADDR - current IP address RESPONSE: Querry: Mobile ID: <mobileIDType> <mobileID> OK Set: OK
AT$APP MOBID MIN <phonenumber>
Sets the phone number string for Mobile ID. Note that this command only sets the MIN, it does not change which Mobile ID is in use. <phonenumber >
A 15 digit number, typically representing the phone number of the mobile. RESPONSE: OK
AT$APP MSG <length> <type>

Attempts to send an inbound message. <length>
this value specifies the length (in bytes) of the message. Sizes can range from 0 to 255
<type>
This is the Message Type value. It is user definable and can range from 0 to 255 RESPONSE: OK
AT$APP MSG LIM <type>

Sends a long inbound message with user code <value> <type>
This is the Message Type value. It is user definable and can range from 0 to 255 RESPONSE: OK
Page144
AT$APP NEI <index> <IP address>

reset the modem to allow the configuration change to take effect. <index>
The index you wish to program.
This command allows you to program an IP address into a specific index slot. It will
<IP address>
The IP address you wish to program RESPONSE: Set NEI <index> to<ip address> OK COMM DISCONNECTED COMM CONNECTED <active ip address>
AT$APP NEI Index <index>

reset
This command changes the active NEI index to the one specified. The modem will after this command is issued so the setting change will take effect. <index>
RESPONSE: Set NEI Index to <index> OK COMM DISCONNECTED COMM CONNECTED <active IP address> Note that the <active IP address> should be the same as the value in NEI Index <index>
AT$APP NEI Index?

This command displays the current active NEI index.
RESPONSE: NEI Index <index> OK
AT$APP NEI?
This command displays the three NEIs (IP Addresses) stored in the modem. It also highlights the NEI currently being used.
RESPONSE: NEI-0 <ddd.ddd.ddd.ddd> Active NEI-1 <eee.eee.eee.eee> NEI-2 <fff.fff.fff.fff> OK Where ddd.ddd.ddd.ddd, eee.eee.eee.eee and fff.fff.fff.fff are the three IP addresses currently stored in the modem.
Page145
AT$APP OUTPUT <output> <state>

This command controls the state of the LMU's output lines <output>
This parameter controls which output line is being referenced. Depending on the LMU hardware version either 6 or 7 outputs are available. They are referenced as follows: 0: Output 0 1: Output 1 2: Output 2 3: Output 3 4: Output 4 5: Output 5 6: Output 6
<state>
This parameter controls the state of the line referenced in <output> The possible states are: ON - brings the output line high OFF - drops the output line low PULSE - brings the output line high for 1 seconds RESPONSE: OK
AT$APP PAP USER <username>
Defines the username for access to the wireless network. Default value is "dummy" <username>
The username RESPONSE: PAP USER <username> OK
AT$APP PAP?
Queries the username and password used to gain access to the wireless network
RESPONSE: PAP USER <username> PAP PASSWORD <password> OK
AT$APP PEG LOGRPT <Event code>

Stores a location report in the log buffer <Event code>
This is a user definable value ranging from 0 to 255. The number is meant to be used to differentiate between various events. RESPONSE: OK
Page146
AT$APP PEG SLEEP <interval>

Puts the LMU to sleep for a specified interval <interval>
Specifies the length of time (in seconds) the unit will sleep for. RESPONSE: OK
AT$APP PEG SNDID <n>
This command will send an ID report based on the LMU's Inbound Retry List. <n>
Defines which port the ID message is sent from: 0 = LMU Primary Port (20200) 1 = LMU Maintenance Port (20210) RESPONSE: OK
AT$APP PEG SNDRPT <Event code>

Attempts to send a report to the LM Exchange server <Event code>
AT$APP PEG SNDSPCL <code>

This command attempts to send a canned message to an MDT. <code>
This parameter specifies which canned message is sent to the MDT. The values can range from 0 to 255. The actual message will depend on the MDT's programming, however a value of 255 will always send a Time Sycn message. RESPONSE: OK
AT$APP PEG SNDTAIP <n>
forces the LMU to send a TAIP message to the TAIP REMOTE IP and PORT per the TAIP configuration settings. <n>
The event code to tag to the TAIP report RESPONSE: OK
Page147
AT$APP PEG SNFRPT <Event code>
This command will attempt to send a report. If it cannot, the report will be logged. Regardless, the report will be tagged with the specified event code. <Event code>
AT$APP PEG SUNRPT <n>
Applies to LMU Version: 4.2g and higher
This command forces a Send Unacknowledge Report PEG Action with event code <n> <n>
The event code tagged to the Un-Acknowledged Event Report. RESPONSE: OK Applies to LMU Version: 3.0 and higher
AT$APP QUIT
This command attempts to shutdown the LMU application and return to the processors native OS. If one does not exist, the unit Resets
RESPONSE: Shutdown
OK
AT$APP REBOOT
This command reboots the LMU application.
RESPONSE: OK Shutdown
Page148
AT$APP S120 <modem select>
This register is used to select the various external/internal modem types supported by the LMU <modem select>
0 1 2 3 4 5 6 7 8 9 - PPP mode - no status reporting - SLIP mode - Novatel Wireless Expedite - PPP mode - Novatel Wireless Sage / Lancer - PPP mode - Motorola iDen phone (external) - PPP mode - Sierra Wireless MP200 - PPP mode - WaceCom GSM/GPRS Interga - PPP mode - generic GPRS - PPP mode - Ericsson R280d - TAIP PAD mode (requires reboot) - No Modem
RESPONSE: Query: <mode> OK Set: OK
AT$APP S125 <debug output enables>
This command turns on and off the debug messages from the LMU application <debug output enables>
This is a 2 bit bit map: Bit 0: Enable Debug messages Bit 1: When set the debug time stamp uses System Time (GMT) with a 1 second LSB. When cleared the time stamp is the time from the last power up. RESPONSE: Query <debug output enables> OK Set OK
Page149
AT$APP S129 <modem restart timer>

This command sets the modem restart timer. <modem restart timer>
This value represents the length of time the LMU will wait before resetting the CDPD modem if the mode m is not registered to the CDPD network. 0 = Off with a 1 Minute LSB RESPONSE: Query: <modem restart timer> Ok Set: OK
AT$APP S131 <serial port baud>

This register controls the BAUD rate of the serial port. <serial port baud>
This is a simple decimal representation of the BAUD rate: 0 - 300 1 - 600 2 - 1200 3 - 2400 4 - 4800 5 - 9600 6 - 14400 7 - 19200 8 - 28800 9 - 38400 10 - 57600 RESPONSE: Query: <serial port baud> OK Set: OK
Page150
AT$APP S132 <serial port word>

This register defines the serial port word. <serial port word>
This is an 5 bit representation of the serial port word with the following format: Bit0-Bit1: data bits/word size (00 = 5 bits, 01 = 6 bits, 10= 7bits, 11 = 8 bits) Bit 2: Stop bits ( 0 = 1 stop bit, 1 = 2 stop bits) Bit3: Parity enable (0 = no parity, 1 = parity enabled) Bit 4: Parity select (0 = odd, 1 = even) RESPONSE: Query: <Serial port word> OK Set: OK
AT$APP S133 <serial port misc>

This register defines several miscellaneous serial port controls <serial port misc>
This parameter uses the lower 3 bits of an 8 bit value to define: Bit 0: DTR drop on ESC // NOT SUPPORTED Bit 1: Hardware flow control //NOT SUPPORTED Bit 2: Enable Termination Character RESPONSE: Query: <serial port misc> OK Set: OK
AT$APP S134 <serial port term char>

This register defines the serial port termination character. <serial port term char>
This is the decimal representation of the ASCII termination character. RESPONSE: Query: <serial port term char> OK Set: OK
Page151
AT$APP S135 <serial port term length>

This register defines the message termination length. <serial port term length>
0 = Off LSB = 4 bytes RESPONSE: Query: <serial port term length> OK Set: OK
AT$APP S136 <msg type>

This register defines the message type. <msg type>
This is a user definable number ranging from 0 - 255 RESPONSE: Query: <msg type> OK Set: OK
AT$APP S138 <term timeout>

This register defines the serial port Termination timeout. <term timeout>
0 = off 1 = 255 x0.1 s RESPONSE: Query: <term timeout> OK Set: OK
Page152
AT$APP S140 <override>
This S-Register allows a user to change the function of both the Test and Mode pins to change them into standard inputs. Test = Input 4 Mode = Input5 Note when the Mode pin is used as input 5, the LMU is in PC mode. <override>
This is a bit mapped field with the following mapping. Bit0: (0) Test pin acts as normal (1) Test pin acts as input 4 Bit1: (0) Mode pin acts as normal (1) Mode pin acts as input 5 RESPONSE: OK
AT$APP S143 <version>
This command is meant to be a versioning tag for customer use allowing them to track PEG script revisions. <version>
This is an 8 bit value (0-255) representing a version number. RESPONSE: OK
AT$APP S145 <n>

Mobile ID Selection Register <n>
1: 2: 3: 4: 5: 6: ESN IMEI IMSI User defined MIN (ie Phone Number) IP Address
RESPONSE: OK
Page153
AT$APP S146 <baudrate>
Modem baud rate override. This command will override the default modem baud rate to the one selected in this register <baudrate>
This is a simple decimal representation of the BAUD rate: 0 - 300 1 - 600 2 - 1200 3 - 2400 4 - 4800 5 - 9600 6 - 14400 7 - 19200 8 - 28800 9 - 38400 10 - 57600 RESPONSE: OK
AT$APP S148 <baud rate selection>
Applies to LMU Version: 5.0h and higher
Host Port Buad Rate selection. This register defines the baud rate of the LMU's host port while it is in PC mode. <baud rate selection>
Baud Rate: 0 - 300 Baud 1 - 600 Baud 2 - 1200 Baud 3 - 2400 Baud 4 - 4800 Baud 5 - 9600 Baud 6 - 14400 Baud 7 - 19200 Baud 8 - 28800 Baud 9 - 38400 Baud 10 - 57600 Baud 11 - 76800 Baud 12 - 115200 Baud 255 - Use Default (19200) RESPONSE: ok
Page154
AT$APP S149 <restart count>

Send Fail Restart Count Threshold <restart count>
The number consecutive of SEND Fail events the LMU will count before hard resetting the wireless modem. A value of 0 disbales this feature RESPONSE:
AT$APP SELFTEST?
This Command Returns the state of the Self Test function of the LMU
RESPONSE: SELFTEST: Inactive OK SELFTEST: Testing OK SELFTEST: Pass OK
AT$APP SENDTO <IP>:<PORT>

The FROM port is also specified <IP>:<PORT>
The destination IP address and Port for the ID Report
Forces the LMU to send an ID Report message to the IP address and port specified.
<LMXI/LMXO/L MXM/LMSTAT/ TAIP>

The port the ID Report is sent from LMXI : 20200 LMXO: 20200 LMXM: 20210 LMSTAT: 20400 TAIP:21000 (Or Taip Local Port setting)
<n>
Optional - Query ID RESPONSE: OK
Page155
AT$APP SERIAL HEAT
Sets the LMU serial port for use with the HEAT modem (slip mode) Serial port settings are: BAUD 19200 Data bits 8 Parity none Stop Bits 1
AT$APP SERIAL MAGTEK

Sets the LMU serial port for use with a Magtek card reader. Serial port settings are: BAUD 9600 Data Bits 8 Parity none Stop Bits 1
RESPONSE: OK
AT$APP SERIAL MDT

the
RESPONSE: OK
Sets the LMU serial port for use with an Net950 or 955 MDT. Note that the input mode hardware line must be high (ie not connected) in order for MDT to function properly. The serial settings are: Baud 2400 Data bits 7 Parity Odd Stop Bits 1
AT$APP SERIAL P201

Sets the LMU serial port for use with the Netcom P201 MDT Serial port settings are: BAUD 9600 Data bits 8 Parity None Stop Bits 1
RESPONSE: OK
RESPONSE: OK
Page156
AT$APP SERIAL PVEND
Sets the LMU serial port for use with the Petro-Vend Fuel Tank Monitor Serial port settings are: BAUD 2400 Data bits 7 Parity Even Stop Bits 1
AT$APP SLEEP <timer> <monitor>

This command forces the LMU into sleep. <timer>
RESPONSE: OK
This value represents how long (in seconds) the LMU will sleep for. The range is from 0 to 65535 seconds.
<monitor>
OPTIONAL This is a 8 bit bit-masked value representing which items are being monitored for wake up. The masking is as follows: Bit 0: Ignition Bit 1: Input 1 Bit 2: Input 2 Bit 3: Input 3 Bit 4: Test input Bit 5: DTR Bit 6: RTS Bit 7: RxD (unsupported) RESPONSE: OK or 0
AT$APP TIME DAYLIGHT <state>

Enables/ disables daylight savings time. <state>
0 - daylight savings calculations are disabled. 1 - daylight savings is enabled RESPONSE: OK
Page157
AT$APP TIME OFFSET <offset>

Sets the local time offset from GMT. <offset>
The hour offset from GMT for a given timezone. RESPONSE: OK
AT$APP TIME?
time the
Displays the Time from the GPS receiver both as local and GMT. The value for LOCAL will be based on the OFFSET value stored in the LMU. Note: If a GPS fix is not available the time will be measured from the last power up of LMU.
RESPONSE: With GPS FIX: GMT : 17:50:15 Mon, 12 Nov 2001 DOY=315 Local: 17:50:15 Mon, 12 Nov 2001 DOY=315 OK Without GPS Fix: GMT : 00:00:16 Thu, 1 Jan 1970 DOY=0 Local: 00:00:16 Thu, 1 Jan 1970 DOY=0 OK
AT$APP TRAN DEBUG <debug level>

Sets the transport layer debug level <debug level>
Turns on or off debug messages regarding the transport layer in the LMU 0 <off> 1 <on> RESPONSE: OK Applies to LMU Version: 3.0 and higher
AT$APP VER?
Quires the version of the LMU app, the PIC, the GPS Receiver and the COMM device
RESPONSE: APP:<Application Version> PIC: <PIC/ Processor type/version> GPS: <GPS Receiver type and version> Radio:<COMM device software version> OK
Page158
System Commands
System level commands may or may not be available on your LMU depending on its hardware configuration. If needed, unsupported commands should be listed in the hardware release note documentation accompanying your LMU. AT HWVER? Applies to LMU Version: 3.0 and higher
This command queries the hardware version of the LMU
RESPONSE: <version> OK
AT PASSTHRU <baud rate>

the internal modem <baud rate>
The baud rate used to communicate with the wireless device/modem. RESPONSE: <none>
This command will stop the LMU application and allow users to directly interface with
AT RESET
The command resets the LMU as if it had been power cycled.

RESPONSE: <none>
AT#REPROG <baud rate>
This command sets the internal modem into it's re-programming mode so it can accept new firmware downloads. <baud rate>
The baud rate used to communicate between the host and the modem for modem firmware download. RESPONSE: <none> Applies to LMU Version: 4.2j and higher
AT&C <n>
Carrier Detect Options. Handled but not supported <n>

0-9 RESPONSE: OK
Page159
AT\APPP
This command issues a PPP Dial string to the LMU
RESPONSE: CONNECT
AT+++
Applies to LMU Version: 4.2j and higher
Data mode termination sequence.

RESPONSE: OK Applies to LMU Version: 5.0a and higher
AT+IPR?
Query LMU's host port Baud Rate

RESPONSE: +IPR: <baud rate> OK
AT+IPR= <baudrate>
Set LMU's host port boad rate. Default setting is 19200 <baudrate>
The new baud rate for the LMU's host port. Note that supported baud rates will depend on which crystal is being used in the LMU 11.0592 MHZ Supports: 2400, 4800,9600, 14400, 19200, 28800, 38400, 57600, 115200 12.28 MHz Suppoers: 2400, 4800, 9600, 19200, 38400 RESPONSE: OK Applies to LMU Version: 4.2j and higher
ATDP <n>
Pulse Dial Support. <n>

Data mode selection: 0 - PPP Mode 1 - SLIP Mode RESPONSE: CONNECT
Page160
ATDT <n>
Tone Dial Support <n>
Data mode selection <n> = 0 : PPP Mode <n> = 1 : SLIP Mode RESPONSE: CONNECT
ATDT0
This command issues a PPP dial string to the LMU

RESPONSE: CONNECT Applies to LMU Version: 3.0 and higher
ATDT1
This command issues a SLIP dial command to the LMU

RESPONSE: CONNECT Applies to LMU Version: 4.0a and higher
ATDT10.0.0.1
This command issues a PPP Dial String to the LMU

RESPONSE: CONNECT Applies to LMU Version: 3.0 and higher
ATE0V0
This command turns off Echo and Verbose mode in the LMU
RESPONSE: 0 Applies to LMU Version: 3.0 and higher
ATE0V1
This command disables the local Echo, but turns on Verbose mode.
RESPONSE: OK
Page161
ATE1V0
This command turns on local Echo, and disables verbose mode.
RESPONSE: 0
ATE1V1
This command turns both Echo and Verbose modes on in the LMU
RESPONSE: OK Applies to LMU Version: 3.0 and higher
ATH
This command does nothing.

RESPONSE: OK Applies to LMU Version: 4.0a and higher
ATI0
This command displays the software versions of the LMU App, Processor, GPS receiver and the CDPD radio.
RESPONSE: APP:<LMU Application version> PIC:<Hardware version> GPS:<GPS Receiver version> Radio:<radio f/w version> OK
ATI1
and IMSI).
This command displays the serial numbers of the LMU, Modem and User (ie ESN, IMEI
RESPONSE: ESN: <ESN> IMEI: <IMEI or EID> IMSI: <IMSI> ICC-ID: <ICC-ID> OK
Page162
ATL <n>
This command does nothing. It emmulates support for Modem Speaker Volume Adjustment. <n>
Speaker volume from 0 to 9 RESPONSE: OK Applies to LMU Version: 4.2j and higher
ATM <n>
Speaker control emmulation. Handled but not supported. <n>

Speaker Control RESPONSE: OK Applies to LMU Version: 4.2j and higher
ATQ <n>
Result code display option. Command handled but not supported <n>
0 or 1 RESPONSE: OK
ATRADIO INIT <index>
This command changes the settings of the FreeWave radio in an LMU <index>
This value represents one of four (1-4) network configurations for a FreeWave LMU. Note that the network selection must match in both the LMU and base station in order for the system to work. RESPONSE: OK Applies to LMU Version: 4.2j and higher
ATS <n>
Lower S-register support. Handled but not supported <n>

<n> = 0 <n = 7 RESPONSE: OK
Page163
ATS120 <modem select>
This register is used to select the various external/internal modem types supported by the LMU <modem select>
0 1 2 3 4 5 6 7 8 9 - PPP mode - no status reporting - SLIP mode - Novatel Wireless Expedite - PPP mode - Novatel Wireless Sage / Lancer - PPP mode - Motorola iDen phone (external) - PPP mode - Sierra Wireless MP200 - PPP mode - WaveCom GSM/GPRS Integra - PPP mode - generic GPRS - PPP mode - Ericsson R280d - TAIP PAD mode (requires reboot) - No Modem
RESPONSE: Query <mode> OK Set: OK
ATS121 <PEG Script ID>
This command is reserved for use by the customer to identify PEG scripts <PEG Script ID>
This is a user definable value ranging from 0 - 255 RESPONSE: OK
Page164
ATS122 <LMStat Enables>
This register defines the enables/disables of the various LM STAT related functions <LMStat Enables>
This is an 8 bit value bit mapped as follows: Bit0: Enable Status Updates Bit 1: Enable Pass Messages Bit2: Enable Event Reports Bit5: Enable LM STAT PEG Event Override Bit 6: Enable Debug messaging Bit 7: Enable Remote monitoring RESPONSE: Query <LMStat Enables OK or Set: OK
ATS125 <debug output enables>
This command turns on and off the debug messages from the LMU application <debug output enables>
This is a 2 bit bit map: Bit 0: Enable Debug messages Bit 1: When set the debug time stamp uses System Time (GMT) with a 1 second LSB. When cleared the time stamp is the time from the last power up. RESPONSE: Query <debug output enables> OK Set OK
Page165
ATS129 <modem restart timer>

This command sets the modem restart timer. <modem restart timer>
This value represents the length of time the LMU will wait before resetting the CDPD modem if the mode m is not registered to the CDPD network. 0 = Off with a 1 Minute LSB RESPONSE: Query: <modem restart timer> Ok Set: OK
ATS131 <serial port baud>

This register controls the BAUD rate of the serial port. <serial port baud>
This is a simple decimal representation of the BAUD rate: 0 - 300 1 - 600 2 - 1200 3 - 2400 4 - 4800 5 - 9600 6 - 14400 7 - 19200 8 - 28800 9 - 38400 10 - 57600 RESPONSE: Query: <serial port baud> OK Set: OK
Page166
ATS132 <serial port word>

This register defines the serial port word. <serial port word>
This is an 5 bit representation of the serial port word with the following format: Bit0-Bit1: data bits/word size (00 = 5 bits, 01 = 6 bits, 10= 7bits, 11 = 8 bits) Bit 2: Stop bits ( 0 = 1 stop bit, 1 = 2 stop bits) Bit3: Parity enable (0 = no parity, 1 = parity enabled) Bit 4: Parity select (0 = odd, 1 = even) RESPONSE: Query: <Serial port word> OK Set: OK
ATS133 <serial port misc>

This register defines several miscellaneous serial port controls <serial port misc>
This parameter uses the lower 3 bits of an 8 bit value to define: Bit 0: DTR drop on ESC // NOT SUPPORTED Bit 1: Hardware flow control //NOT SUPPORTED Bit 2: Enable Termination Character RESPONSE: Query: <serial port misc> OK Set: OK
ATS134 <serial port term char>

This register defines the serial port termination character. <serial port term char>
This is the decimal representation of the ASCII termination character. RESPONSE: Query: <serial port term char> OK Set: OK
Page167
ATS135 <serial port term length>

This register defines the message termination length. <serial port term length>
0 = Off LSB = 4 bytes RESPONSE: Query: <serial port term length> OK Set: OK
ATS136 <msg type>

This register defines the message type. <msg type>
This is a user definable number ranging from 0 - 255 RESPONSE: Query: <msg type> OK Set: OK
ATS138 <term timeout>

This register defines the serial port Termination timeout. <term timeout>
0 = off 1 = 255 x0.1 s RESPONSE: Query: <term timeout> OK Set: OK
Page168
ATS140 <override>
This S-Register allows a user to change the function of both the Test and Mode pins to change them into standard inputs. Test = Input 4 Mode = Input5 Note when the Mode pin is used as input 5, the LMU is in PC mode. <override>
This is a bit mapped field with the following mapping. Bit0: (0) Test pin acts as normal (1) Test pin acts as input 4 Bit1: (0) Mode pin acts as normal (1) Mode pin acts as input 5 RESPONSE: OK Applies to LMU Version: 5.0a and higher
ATS145 <n>
Mobile ID Selection Register <n>

1: 2: 3: 4: 5: 6: RESPONSE: OK ESN IMEI IMSI User defined MIN (ie Phone Number) IP Address
ATS146 <baudrate>
Modem baud rate override. This command will override the default modem baud rate to the one selected in this register <baudrate>
This is a simple decimal representation of the BAUD rate: 0 - 300 1 - 600 2 - 1200 3 - 2400 4 - 4800 5 - 9600 6 - 14400 7 - 19200 8 - 28800 9 - 38400 10 - 57600 RESPONSE: OK
Page169
ATS148 <baud rate selection>
Host Port Buad Rate selection. This register defines the baud rate of the LMU's host port while it is in PC mode. <baud rate selection>
Baud Rate: 0 - 300 Baud 1 - 600 Baud 2 - 1200 Baud 3 - 2400 Baud 4 - 4800 Baud 5 - 9600 Baud 6 - 14400 Baud 7 - 19200 Baud 8 - 28800 Baud 9 - 38400 Baud 10 - 57600 Baud 11 - 76800 Baud 12 - 115200 Baud 255 - Use Default (19200) RESPONSE: OK
ATS149 <restart count>

Send Fail Restart Count Threshold <restart count>
The number consecutive of SEND Fail events the LMU will count before hard resetting the wireless modem. A value of 0 disbales this feature RESPONSE:
ATZ
Reset default Hayes settings Echo On Verbose On Dropping DTR causes disconnect
RESPONSE: OK
Page170

LMUand Tethered Locator User Guide

Diunggah oleh

Informasi Dokumen

Judul Asli

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

LMUand Tethered Locator User Guide

Diunggah oleh

Hak Cipta:

Format Tersedia

Version 5.

0k Released March 2003

QUICK START: QUICK START: QUICK START: QUICK START:

About This Manual

About The Reader

Section 1: System Overview

Internet / Wireless Network LMU Manager

Network Base Station

TetheredLocator Wireless PDA MDT

Wireless Data Primer

Excerpt taken from the Novatel Wireless Inc website http://www.novatelwireless.com/support/CDPD%20Tech.html

Excerpt Taken from the Ericcson Mobitex website http://www.ericsson.com/network_operators/mobitex/about.shtml

Excerpt taken from the Qualcomm website (http://www.qualcomm.com/cdma/3g.html)

Section 2: Hardware Overview

Output Output Input

Vehicle Power GND

Standard Wiring Harness

RxD TXD CTS RTS DSR DTR GND

9-Pin Female D Connector with fastening screws

8 Additional wires for insert 1 ft un-terminated Various colors

Output Input Input

Vehicle Power GND

Standard Wiring Harness

37-Pin Female D Connector

Note - All wire #22 AWG Stranded

CDPD Phones: - Ericsson R280d GPRS Phones: - Motorola Timeport

Output Input Input

Vehicle Power GND

Host Serial Port

9 Pin Female D Series Connector

RTS2 CTS2 DTR2 DSR2 GND TxD2 RxD2

3 Orange 4 Green 20 Yellow 21 Black 32 Yellow/White 33 Green/White 34

RTS2 CTS2 DTR2 DCD2 GND TxD2 RxD2

Lancer Serial Port

9 Pin Male D Series Connector

Lancer Power From Vehicle

Driver Outputs Connected to External Relay

Door Open Detect Input 2

+V (+12V) Input1 Driven through a relay

+V (+12V) IGN Ignition

COMM Wireless modem

Modem is on but data session (PPP) has not been established

Quick Start Guides

Yes N/A Yes Yes 0 0 0 0 10 20 30

Section 4: Unit Configuration

Working with Host Devices

Section 5 PEG Overview

PEG Settings (a.k.a. Trigger Parameters)

East Distance Zone Boundary Center Point

Trig Param None None None 0 0

Condition None None None None None

Condition Index None None None None None

Power-Up or Wake Up Ignition On Ignition Off

Our Event control would look like:

Trig Param None

Condition Index None

TimeElapsed Distance Traveled GPS Lost

GPS Acquired Input High

Speed Above Speed Below Count Exceeded Moving

And lastly we can program in our sleep functionality.

Section 6: TAIP Interface

Supported Message Types

Appendix A: HyperTerminal Configuration