CalAmp 3640LB Advanced Rugged Telematics Gateway Installation Guide

CalAmp 3640LB Advanced Rugged Telematics Gateway

Product Specifications

• Product Name: CalAmp HMU-3640TM
• Category: Telematics Gateway
• Connectivity: Wireless and Peripheral options
• Features: Vehicle interface technologies, GPS receiver, wireless data modem
• Networks: LTE, HSPA
• Applications: Fleet management, location tracking, monitoring, reporting

Product Usage Instructions

Installation
Before beginning the installation process, ensure you have read and agreed to the license agreement and reviewed the limited warranty and regulatory information.

1. Locate a suitable position in the vehicle for mounting the HMU-3640TM unit.
2. Connect the HMU-3640TM to the vehicle’s power supply and necessary peripherals.
3. Ensure proper network coverage for data transmission.

Setup

1. Power on the HMU-3640TM unit and allow it to establish a network connection.
2. Configure the device settings such as transmission intervals, alerts, and monitoring preferences.
3. Verify that the device is communicating data to the designated software application.

Usage

1. Monitor the vehicle and location data transmitted by the HMU-3640TM through the software application.
2. Utilize the features such as geo-fencing, speed monitoring, and exception alerts based on your fleet management needs.

Frequently Asked Questions (FAQ)

• Q: What networks does the HMU-3640TM support for data transmission?
  A: The HMU-3640TM supports LTE and HSPA networks for transmitting vehicular and location data.

• Q: Can SMS messaging be used as a backup communication method?
  A: Yes, SMS messaging can be used as an alternative or redundant communication backup when wireless network coverage is unavailable.

Q: What type of fleet applications is the HMU-3640TM designed to support?
A: The HMU-3640TM supports a range of custom fleet applications including automatic vehicle location, geo-fencing, speed monitoring, third-party security monitoring, dynamic reporting routines, and exception alerts.

HMU-3640 Hardware & Installation Guide
HMU-3640™
Hardware and Installation Guide

IMPORTANT: DO NOT INSTALL OR USE THE SOFTWARE OR DOCUMENTATION UNTIL YOU HAVE READ AND AGREED TO THE LICENSE AGREEMENT AND REVIEWED THE LIMITED WARRANTY AND REGULATORY INFORMATION.

Introduction

Welcome to the HMU-3640™ Hardware and Installation Guide. This manual is intended to give you information on the basic setup and installation of the CalAmp HMU-3640™ product(s) including hardware descriptions, environmental specifications, wireless network overviews and device installation.

About This Manual
The HMU-3640™ is a next generation telematics gateway that includes a range of wireless and peripheral connectivity options and is equipped with CalAmp’s purpose built vehicle interface technologies for heavy duty vehicles. In order to accurately describe the functionality of these units we have broken this manual into the following sections:

• System Overview – A basic description of a CalAmp HMU-3640™. This includes a description of roles and responsibilities of each of the CalAmp components as well as a brief overview of the wireless data technologies used by the HMU-3640™.
• Hardware Overview – Describes the physical characteristics and interfaces of the HMU-3640™.
• Installation and Verification – Provides guidance for the installation of the HMU-3640™ versions in a vehicle and instructions on how to verify the installation is performing adequately.

About The Reader
In order to limit the size and scope of this manual, the following assumptions have been made about the reader.

1. You are familiar with GPS concepts and terminology
2. You have some experience with installing equipment in vehicles
3. You are familiar with the use of AT Commands
4. You are familiar with the use of terminal programs such as HyperTerminal or PuTTY

About CalAmp
CalAmp (NASDAQ: CAMP) is a telematics pioneer leading transformation in a global connected economy. We help reinvent businesses and improve lives around the globe with technology solutions that streamline complex IoT deployments and bring intelligence to the edge. Our software applications, scalable cloud services, and intelligent devices collect and assess business-critical data from mobile assets, cargo, companies, cities and people. We call this The New How, powering autonomous IoT interaction, facilitating efficient decision making, optimizing resource utilization, and improving road safety. CalAmp is headquartered in Irvine, California and has been publicly traded since 1983. LoJack is a wholly owned subsidiary of CalAmp. For more information, visit calamp.com, or LinkedIn, Twitter, YouTube or CalAmp Blog.

About the CalAmp Location Messaging Unit – HMU-3640™

• The HMU-3640™ utilizes a ruggedized design to perform in arduous conditions and rugged construction equipment environment with extended temperature operation. Enhanced electrical interfaces give the HMU-3640™ a unique and versatile environment in heavy duty conditions, while delivering critical data to the end customer. The built-in ECU (Engine Control Unit) interface reads and transmits engine condition and performance data such as engine temperature and fault codes from heavy duty vehicle to provide the best possible real-time picture of vehicle health. In addition, it supports separate
• ARM (Advanced RISC Machine) cortex micro-controller to support hosted application features.
• The CalAmp HMU-3640™ is a mobile device that resides in private, commercial or government vehicles. The HMU-3640™ is a single box enclosure incorporating a processor, a GPS receiver, a wireless data modem, and a vehicle-rated power supply. The HMU-3640™ also supports inputs and outputs to monitor and react to the vehicular environment and/or driver actions.
• The HMU-3640™ collects, stores and transmits vehicular and location data over a designated wireless network including LTE and HSPA. Vehicular and location data are transmitted to a customized software application that has been designed to receive, acknowledge, process, store, and respond to this data.
• Unit location and vehicular information is sent at pre-determined intervals, on demand, or when pre-programmed vehicular conditions are met. Transmission of data are sent immediately when in wireless network coverage and stored for later transmission when out of the wireless coverage area. SMS messaging can be used as an alternative or redundant communication backup.
• The HMU-3640™ is designed to support a variety of custom fleet applications starting with basic automatic vehicle location and including applications requiring more sophisticated features such as geo-fencing, speed and mileage monitoring, third party security monitoring, dynamic reporting routines, and an array of exception alerts.
• HMU-3640™ are sold exclusively to authorized systems integrators, software firms, and service providers who have developed their offering around the capabilities of the HMU-3640™. Customers are trained by CalAmp to integrate the mobile device with their system and to assist in support and maintenance of the devices.
• Installations of HMU-3640™ are performed by CalAmp customers or contracted installers. Typical installations include hook-up to power, ignition, and ground. HMU-3640™s and the corresponding wiring are almost always hidden from view and general access. Placement of the units is usually under dashboards, in trunks or in compartments.

System Overview

Overview
The entire purpose behind a fleet management system is to be able to remotely contact a vehicle, determine its location or status, and do something meaningful with that information. This could include displaying the vehicle location on a map, performing an address look-up, providing real-time driving directions, updating the vehicles ETA, monitoring vehicle and driver status or dispatching the vehicle to its next pick up.
These functions, of course, are completely dependent on the capabilities of the vehicle management application. The role of the CalAmp HMU-3640™ is to deliver the location information when and where it is needed.
A typical fleet management system based on a CalAmp device includes the following components:

• A wireless data network
• An HMU-3640™
• Host Device (GPS NMEA only)
• An LM Direct™ communications server
• Backend mapping and reporting software which typically includes mapping and fleet reporting functions PULS™
• LMU Manager™

Component Descriptions

Back end Software
Backend software is a customer provided software application. Regardless of its purpose one of its primary functions is to parse and present data obtained from the LM Direct server. This allows the application to do any of the following:

• Display location data base on reports received from the HMU-3640™ in a variety of formats. Present historic information received from the HMU-3640™ typically in a report/chart style format Request location updates from one or more HMU-3640™
• Update and change the configuration of one or more HMU-3640™

LMU Manager
LMU Manager is the primary support and configuration tool in the CalAmp system. It allows access to almost every feature available to the HMU-3640™. Unlike the backend software, it has the option of talking directly to an HMU-3640™ or making a request forwarded by the LM Direct server.

For further details on using LMU Manager, please refer to the LMU Manager Users Guide.

LM Direct Server
LM Direct is a message interface specification detailing the various messages and their contents the HMU-3640™ is capable of sending and receiving. This interface allows System Integrators to communicate directly with HMU-3640™s.
Sample code is available to system integrators upon request to aid in the development of an LM Direct Server.

Wireless Data Network
The Wireless Data Network provides the information bridge between the LM Direct server and the HMU-3640™s. Wireless data networks can take a variety of forms, such as cellular networks, satellite systems or local area networks. At this point in time, the networks available to the HMU-3640™ are:

HMU-3640™
The HMU-3640™ is 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 HMU-3640™
• A location or status request from the LM Direct server
• A location or status request 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 HMU-3640™ as a wireless modem as well as a vehicle-location device.

Wireless Data Primer
This section is meant to give an overview of the wireless data technologies employed by the CalAmp location products.

SMS (Short Message Service)
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.(Excerpt taken from the GSM World website (http://www.gsmworld.com/technology/sms/intro.shtml#1))
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.

LTE (Long-Term Evolution)
Long-term evolution (LTE) is the latest and rapidly growing global data transmission technology. Based on GSM and UMTS/HSPA standards, LTE is a standard of high-speed wireless data transmission and communication. Continuously evolving, LTE advancements continue to push data capacity and user experience on a global scale. With a peak downlink rate of 300 mbps, uplink rate of 75 mbps, LTE sits in 1.4 MHz to 20 MHz bands, while also supporting FDD, TDD, and not sacrificing data capability.
“Both LTE FDD and TDD offer very high data rates, low latency, and seamless interworking with 3G, as well as between FDD and TDD networks. They also leverage common core network.” (Excerpt taken from the Qualcomm website (https://www.qualcomm.com/invention/technologies/lte))
LTE is the most current and advanced data technology network for MDT’s (mobile data terminals) and other mobile devices, and an upgrade over GSM/UMTS and CDMA. LTE frequency bands vary internationally, so it is important to note device configuration will dictate proper functionality.

Hardware Overview

Location Messaging Unit-HMU-3640™
HMU-3640™ Handling Precautions

Electrostatic Discharge (ESD)
Electrostatic discharge (ESD) is the sudden and momentary electric current that flows between two objects at different electrical potentials caused by direct contact or induced by an electrostatic field. The term is usually used in the electronics and other industries to describe momentary unwanted currents that may cause damage to electronic equipment.
WARNING: This product can expose you to chemicals including carbon black, nickel, & bisphenol A, which are known to the State of
California to cause cancer and birth defects or other reproductive harm. For more information go to https://www.P65Warnings.ca.gov.

ESD Handling Precautions
ESD prevention is based on establishing an Electrostatic Protective Area (EPA). The EPA can be a small working station or a large manufacturing area. The main principle of an EPA is that there are no highly charging materials in the vicinity of ESD sensitive electronics, all conductive materials are grounded, workers are grounded, and charge build-up on ESD sensitive electronics is prevented. International standards are used todefine typical EPA and can be obtained for example from International Electro-technical Commission (IEC) or American National Standards Institute (ANSI).
This ESD classification of the sub assembly will be defined for the most sensitive component, therefore the following classifications apply:

• Class 1B – Human Model (< 1 kV)
• Class M1 – Machine Model (< 100V)

When handling the HMU-3640™’s™ main-board (i.e. sub assembly) by itself or in a partial housing proper ESD precautions should be taken. The handler should be in an ESD safe area and be properly grounded.

GPS Ceramic Patch Handling
When handling the sub assembly it may be natural to pick it up by sides and make contact with the antenna boards. In an uncontrolled ESD environment contact with the center pin of ceramic patch antenna can create a path for electrostatic discharge directly to the GPS Module. The GPS Module is very sensitive to ESD and can be damaged and rendered non-functional at low levels of ESD.
One should avoid contact with the center pin of the patch during handling.

Packaging
Anytime the sub assembly is shipped and it is not fully packaged in its final housing it must be sealed in an ESD safe bag.

Electrical Over-Stress (EOS)
The GPS receiver can be damaged if exposed to an RF level that exceeds its maximum input rating. Such exposure can happen if a nearby source transmits an RF signal at sufficiently high level to cause damage.

Storage and Shipping
One potential source of EOS is proximity of one HMU-3640™ GPS Antenna to another HMU-3640™ GSM Antenna. Should one of the units be in a transmit mode the potential exists for the other unit to become damaged. Therefore any HMU-3640™ GPS Antenna should be kept at least four inches apart from any active HMU-3640™ GSM Antenna or any other active high power RF transmitter with power greater than 1 Watt.

Battery Back-up devices
Please properly dispose of the battery in any of the CalAmp products that utilize one, do not just throw used batteries, replaced batteries, or units containing a back-up battery into the trash. Consult your local waste management facility for proper disposal instructions.

Physical and Environmental Specifications
The HMU-3640™ is designed to operate in environments typically encountered by heavy duty fleet vehicles, including wide temperature extremes, voltage transients, and potential interference from other vehicle equipment.
To ensure proper operation in such an environment, HMU-3640™s 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.
The following shows the environmental conditions the HMU-3640™ is designed to operate in and the relevant SAE tests that were performed. No formal altitude tests were conducted.

Dimensions

• 7.0”(L) x 3.0”(W) x 1.6”(H)
• 178mm (L) x 76mm (W) x 41mm (H)

Weight
8.8oz (250g)
Ingress Protection Rating – IP66, IP67

Temperature
Operating Temperature Range: -30o C to 75o C
Storage Temperature Range: -40o C to 85o C
Battery Charging Range: 0o C to 40o C

Humidity
95% relative humidity, 50° non-condensing

Altitude
Operates at altitudes of up to 10,000 feet and can be stored safely up to 40,000 feet

Shock and Vibration
Ground vehicle environment with associated shock and vibration
SAE Test: SAE J1455
Mil Standard 202G, 810F

Bench-Handling (Non-Operating)
4 inch pivot drops on each of the faces on which it may be placed for servicing or installation.

Electromagnetic Compatibility (EMC)
EMC compliant for a ground vehicle environment

Operating Voltage Range
12/24 VDC Vehicle Systems
9-32 VDC (start-up, operating)
7-32 VDC (momentary)

Battery Pack
Battery Capacity: 500 mAh
Battery Technology: Nickel-Metal Hydride, NiMH
Charging Temperature: 0° to +40° C

Transient Protection
Input voltage transients typical of large trucks

Electrostatic Discharge (ESD)
No damage or performance degradation after the ESD disturbance.

Power Consumption
<350 uA @ 12V (deep sleep)
20 mA @ 12V (idle on network)
150 mA @ 12V (active tracking with VBUS active)

GNSS

• 55 channel GPS receiver (with SBAS; WAAS, EGNOS, MSAS)
• GPS, GLONASS Capable (only two GNSS systems can run concurrently)
• Tracking Sensitivity: -167dBm
• Acquisition Sensitivity:
• -148dBm Cold Start
• -156dBm Hot Start
• Location Accuracy: Up to 2.0 CEP Open Sky (24 hours static)
• Anti-jamming
• AGPS/Location assistance capable

Cellular Communications (Comm)
North America Variant
LTE Cat 1 – 1900 (B2)/AWS 1700 (B4)/850 (B5)/700 (B12) MHz
HSPA/UMTS – 850 (V)/1900 (II) MHz

Cellular Communications (Comm) Global Variant
HSPA/UMTS – 800 (VI)/850 (V)/900 (VIII)/1800 (III)/1900 (II) MHz
GSM/GPRS – 850/900/1800/1900 MHz

HMU-3640™ Connectors
The HMU-3640™ offers connectors to access VBUS, I/O, other expansion capabilities. These connectors are:

• 12 Pin VBUS, I/F Power, I/O Mini-Deutsch Connector
• Battery Applicator
• SIM Card Port

I/O Connector

Operating range of 9 to 32 VDC
7| GND| Main power input connected to negative terminal of vehicle battery. Operating range of 9 to 32 VDC.
8| ADC 1| Analog Input
9| OUT 0| Digital Output
10| RS232 RX| RS232 Data Input to HMU3640
11| RS232 CTS| RS232 CTS Output from HMU3640
12| CAN Low| J1939 CAN communication

Hardware options exist to swap in RS-485, K-line, or an additional general purpose input.

12 Pin Orientation
Accessories
*Refer to Section 2.6 (https://puls.calamp.com/wiki/Harness_Diagrams#V-Series_.28VDK-3641.29_and_LMU-3640%7C) of the Harness Diagrams page for more information on appropriate accessories for the HMU-3640™.

GPS Receiver

• 56 channel GNSS receiver (with SBAS)
• Accuracy: 2.0m CEP (50%)
• Tracking Sensitivity: -162dBm
• Acquisition Sensitivity: -147dBm

Descriptions

• The HMU-3640™ provides the following logical mapping of inputs and outputs (I/O):

Digital Inputs

• Input 0: Ignition Sense (Always biased low)
• Input 1: In-1 sel Generic Digital Input (Biased high or low/ S-158 Bit 1)
• Internal Inputs
• Input 8: Motion Sensor (low = no motion, high = motion)
• Input 9: VBUS Active
• Input 10: Pwr State (low = main power, high = battery power)
• Input 11: Vbatt Low
• Input 12: Not Used
• Input 13: Batt Virt Ign
• Input 14: Pure Virt Ign
• Input 15: Radio Ring Wake
• Input 16: DB Wake
• Input 17: Vbus Wake
• Input 18: Not Used
• Input 19: Crank Detect

Analog to Digital Inputs

• A/D 0: External Power Supply Monitor (VIN1)
• A/D 1: Ext ADC1 Generic External Analog to Digital Input
• A/D 2: Not Used
• A/D 3: HW Config
• A/D 4: Not Used
• A/D 5: Not Used
• A/D 6: GPS Antenna Monitor
• A/D 7: μP Temperature (internal use only)
• A/D 8: Vref
• A/D 9: Battery

Outputs:

• Output 0: Out-0

Internal Outputs

• Output 8: Chrg Disable

Axis Accelerometer Input
The HMU-3640™ supports an internal 3 Axis Precision Accelerometer as one of its discreet inputs. When the HMU is moved in any direction, the associated input will be in the High state. If the HMU’s accelerometer does not detect motion, then the input will be in the Low state. No external connections are required for this functionality to be operational.

Ignition and Inputs
The HMU-3640™ provides up to 5 inputs. These inputs are protected from typical vehicle transients and can be directly connected to most vehicle level logical inputs from 0 volts up to the vehicle power input level (typically 12 VDC). One of these inputs is dedicated to sensing the vehicle’s ignition status to provide for flexible power management. The other 4 inputs may be used to sense vehicle inputs such as cooling unit operation, a hidden driver “Panic” switch, taxi on-duty/off-duty meter status or many others.
The ignition input is pulled to ground through the 268k resistance, where the other inputs can be configured to be normally High (i.e. pulled to+6v through a 210k resistor) or Low (i.e. pulled to ground through a 43k resistor). The diagrams below show how to connect the inputs in both a high- and low-biased configuration:

The HMU’s outputs are designed to drive external relays. These outputs provide a high-current, open-collector driver that can sink up to 150 mA each. These drivers may be used 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. This diagram is a typical use of an output to drive a relay.

Serial Streams

Status LEDs
The HMU-3640™ is equipped with 4 Status LEDs; one for GPS, one for COMM (wireless network status), one for VBUS and one for WiFi. The LEDs use the following colors to indicate service:

Status LEDs

Configuration of the Vehicle Bus Interface
The VBU2 Vehicle Bus Interface embedded in the HMU-3640 is designed to support Heavy Duty (trucks and buses) vehicles. Detection of operating mode today is primarily based on the correct selection of the cable for the vehicle type.

• In order to avoid vehicle interference from the device, ensure the correct cable is selected for the specific vehicle that the device is installed into

The Heavy Duty vehicle mode emulates the CalAmp JPOD2 accessory for vehicles with Heavy Duty vehicle bus interfaces. In this mode, the VBU2 interface will operate and communicate with heavy duty vehicles using the J1939 protocol. For detailed JPOD2 information, refer to the JPOD2 Tutorial.
Refer to the steps below to properly install, configure and run VBU2 interface of the HMU-3640.

VBU2 Mode Configuration and Testing Instructions

1. The HMU-3640 firmware with the correct app id should be preinstalled on the device.
2. To configure HMU in forced JPOD2 (Heavy Duty) configuration:

Configuration and Activation
This section details how to quickly get an HMU-3640™ provisioned and configured to point at a specific server. It is assumed that a PEG script has already been created and is being managed through LMU Manager or PULS™, the CalAmp Maintenance System.
We are making three assumptions to simplify the setup process:

• You have created, installed and configured an LM Direct™ Server to receive messages from the HMU-3640™. (See LM Direct™ Reference Guide for details)
• You are using the standard wiring harness from CalAmp and the serial port expansion harness.
• You have created a HyperTerminal or Putty session.
• You have contacted the CalAmp sales team regarding the network availability of the HMU-3640™.

Quick Start – General Config
All HMU-3640™s must go through a common step during the configuration and provisioning process. Specifically, this is pointing the HMU to your LM Direct™ server, either via IP or a URL.
This configuration process is accomplished via a series of AT Commands:

1. Power up the HMU-3640™ and connect a serial cable from the HMUto your laptop
2. Open a terminal session to the HMU-3640™
3. Enter the address of the LM Direct™ server: Where ddd.ddd.ddd.ddd is the publicly addressable IPV4 address of your LM Direct™ server and ppppp is the UDP port number.
4. Alternatively if a URL has been set up for your LM Direct™ server, the HMU may be programmed with: Where myURL.MyCompany.com is the URL assigned to the server.
5. Enter ATIC to verify the correct settings are displayed for your Inbound Server.

This configuration process is accomplished via a series of SMS Commands:

1. Power up the HMU-3640™ and your handset
2. From the handset, send an SMS message to the HMU-3640™ phone number: Where ddd.ddd.ddd.ddd is the publicly addressable IPV4 address of your LM Direct™ server and ppppp is the UDP port number
   Alternatively if a URL has been set up for your LM Direct™ server, the HMU may be programmed with: Where myURL.MyCompany.com is the URL assigned to the server
   Verify your settings by sending the commands:

Activating LTE Using AT Commands
There are two variants of LTE modems; LTE AT&T and LTE Verizon. Both variants require a SIM card to be inserted.
If you get an HMU without a SIM card (which is the typical case), the operator will simply ask for the IMEI of the HMU . The IMEI
(International Mobile Equipment Identifier) is printed on the label of the HMU. Again, DO NOT give the operator the CalAmp ESN of the HMU.
The operator will provide you with a SIM card for each account activated. If they are especially nice (or you are especially persistent) they will also give you a list tying the IMSI (International Subscriber Identifier) of the SIM to the phone number assigned to it. Please note that the operator will likely tie the IMSI (i.e. the SIM) to a specific IMEI. Making sure the specific SIM matches to the right IMEI isn’t strictly necessary, but it will keep everyone’s book-keeping a little cleaner. You may also obtain this information by running a CSV report in PULS (after the devices have connected to the network and sent in their first ID Report). See the PULS Users Guide for more information.
If you do happen to have a SIM card, the operator will ask for the IMSI and ICC-ID (Integrated Circuit Card Identifier) along with the IMEI of the HMU. Again, in return you should get a list of IMSIs and Phone Numbers.
The IMEI, IMSI and ICC-ID are all available through the ATI1 command. The IMEI should also be printed on the label of the HMU.

Operators can offer more than one type of APN and can even set up a custom APN just for your devices. The rates they charge will vary depending on the APN service you want. Operators may also request you use a blank APN. With the APN, you may also receive a username and password combination.
The last item an operator may provide is a SIM PIN. The PIN is effectively a password to the device. The main difference here is that the PIN will restrict all the capabilities of the device, where the SPC is used just for configuration.
The activation sequence for an LTE AT&T modem would therefore look as follows:

To clear the APN, the following command can be used:

Only enter this next command if you have been given a non-zero PIN as any errors may lock you out of the modem.

You can confirm activation by watching the Comm LED to see if it goes solid. You may also confirm activation by entering AT command

The activation sequence for an LTE Verizon modem would therefore look as follows:
The HMU must be registered on the Verizon network. Having the device roaming or in poor Verizon coverage will not allow the execution of the activation process.
The activation is an automatic process where Verizon pushes the APN to the modem.
In some cases, there might be a delay up to 15 minutes until the unit gets activated and is able to make a data call.
For Verizon LTE, parameter 2306 (APN) is currently disabled.
You can confirm activation by watching the Comm LED to see if it goes solid. You may also confirm activation by entering AT command

Preparing for Installation

Be sure you have received all the HMU components you need. This must include:

• The HMU to be installed
• A power harness
• 12 Pin deutch I/O connector
• Optional Components:
• Input and output cables
• Relays
• HMU peripherals (i.e. Serial adapter, jPOD, TetheredLocator)
• Host serial devices (e.g. PDAs, laptops, other serial devices)

Plan The Installation
Verify Power, Ground and Ignition. Be sure to check each source (power, ground and ignition) to ensure that the proper signaling exists. This is typically accomplished with a multi-meter.

Before drilling any holes or running any wires, decide where each hardware component will be located (HMU, antennas, peripherals, etc.). Be sure that the cables to the HMU are not bent or constricted in any way. Also make sure that the HMU is kept free from direct exposure to the elements (sun, heat, rain, moisture etc…).
Be advised that an installation that violates the environmental specifications of the HMU will void the warranty.
The best way to ensure a trouble-free installation is to consider your options and make some decisions before you start. Take a look at the vehicle and determine how to best install the HMU for the following purposes:

• Accurate data gathering and simulation of how customers actually use your solution
• Ongoing monitoring and maintenance of HMU equipment
• Accidental or intentional alteration of the equipment or cable connections

The following sections cover some of the issues to consider when planning your HMU installation.

Size and Placement of LMU Unit
The dimensions of the LMU should be taken into account, particularly when installing in a vehicle:
Whether you intend to place the LMU under a seat or into a cavity behind the vehicle’s interior molded trim, be sure the LMU will fit before drilling any holes or running cable

• Be certain that the cables running to the LMU will not be bent or constricted. Damage to the cables may impede the LMU’s performance.
• Be certain that the installation point will not violate any of the LMU’s environmental specification (temperature, moisture, etc…) as improper installation of the LMU may void the warranty.

See the LMU Environmental Specifications for the exact measurements and specifications of the HMU-3640™.
Typical installations will place the LMU under the vehicle dash board, or in the trunk. Make sure you can get access to the unit afterwards as under some circumstances it may be necessary to add additional wiring or connections to the LMU.

Access to the SIM (Subscriber Identity Module) Card
When used in a LTE, each LMU uses a Subscriber Identity Module (SIM) card, which should be inserted before you install the LMU for the first time. The SIM card is attached to the main-board inside the housing of the LMU unit.
At some future time, you might need or want to replace the SIM card with a different one, so try to install the LMU in such a way that the cover can be removed to make the SIM card accessible.

Protection from Heat
It is best not to place the LMU unit in an unusually warm location such as directly near heater vents, near hot engine components or in direct sunlight. The maximum temperature that can be tolerated by the LMU is described in the LMU Environmental Specifications section.

Visibility of Diagnostic LEDs
Status LED lights on the front of the LMU unit can provide valuable information about the operation of the LMU. When feasible, attempt to install the LMU in such a way that these lights can be seen with reasonable ease.
You may find it useful to be able to view the LEDs periodically to make sure that the LMU is operating properly. If at any time you should encounter a problem with the LMU, you may need to read the LEDs in order to troubleshoot the problem. If you cannot fix the LMU yourself, you will need to provide the LED information to CalAmp customer support.
For information about how to interpret the LEDs, see the Status LED Behavior section.

Cable Length
Do not cut cables. Instead, coil any excess length, making sure not to crimp or flatten any cable.

Moisture and Weather Protection
The LMU unit must be located where it will not be exposed to moisture or water. In a typical installation inside a vehicle this is not commonly thought to be a concern; however, it might be best to avoid locating the LMU below a car’s cup holders, or where rain might easily splash into the compartment when a door is opened.

Preventing Accidental or Unauthorized Modification
If you anticipate that fleet drivers or others might interfere with the LMUs once they are installed, take steps to be sure that it is not easy to remove the LMU from its power source, or disrupt internal antenna interference.
Two common methods are the use of Tamper Proof Sealant or creation of PEG Script to detect power loss or GPS antenna disconnections.

Installing the LMU in a Vehicle
This section provides instructions for installing an LMU in a vehicle.
Be sure to consider the design decisions described in the previous sections. When you are ready to begin installing the LMU, follow these steps:

Place the HMU-3640 in the vehicle.
The HMU-3640 contains an internal battery, and thus should be oriented with the label facing upwards towards the sky. LMUs with internal antennas should be placed directly under a thick panel to maximize their performance and protect from external elements. A typical location include under the dash close to the front wind-shield.
Attach the LMU to the solid body of the vehicle, not to plastic panels. The LMU can be placed out of sight by removing interior trim and molding to expose available space, then replacing the trim once the LMU is in place.

Connect power, ignition, and ground.
The power input (red wire) must be connected to a constant (un-switched) +12 VDC or +24 VDC supply; preferably, connected directly to the vehicle battery terminal or as close to it as possible. This connection point should be fuse protected to not more than 5 Amps.
The ignition input (white wire) must be connected to the vehicle ignition or another appropriate key operated line, such as ACCESSORY, ensuring that power to the ignition wire is available only when the vehicle ignition is on.
The ground line (black wire) must be connected to chassis ground.
Failure to connect these lines in the manner described may result in discharge of the vehicle battery.
For best results, it is strongly recommended that the LMU connection be on its own circuit. Connect the power input directly to the vehicle battery if possible and protect the circuit with an inline fuse. If you must connect through the fuse box, use standard commercial wiring practices to create a permanent installation rather than using press-in fuse clips or other temporary measures.
DO NOT connect the power cable to the LMU at this time.

Typical Connection Sequence

• Connect any peripherals to the LMU
• Plug in the power harness.

The physical installation of the LMU hardware is now complete.

Installation Verification
In many cases it is desirable to verify that an installed HMU-3640™ is working properly. That is, installers should verify that the GPS and communications functions of the HMU-3640™ are working properly before departing the installation site. In more robust cases, some key configuration settings such as the Inbound Address and URL should also be verified.
Note that these processes are all based on issuing AT Commands to the HMU-3640™. It is expected that installers will have access to a serial port expansion cable and a laptop or PDA capable of a terminal connection. Alternatively, an SMS message can be sent to an HMU-3640™ to obtain its current status.

Comm Verification
Installers should first verify that the HMU-3640™ has been acquired and has registered to the wireless network. This may be verified in one of two ways. First, installers may look at the Comm LED (i.e., the one closest to the SMC antenna connector). If this LED is solid, then the LMU has  registered to the network and established a data session.
If the LED is not visible, then Comm may be verified using an AT Command:

Depending on the wireless network being used something similar to what is shown below will be displayed. It is important to verify that ‘Yes’ values are displayed at the top for Data and Network registration and the correct APN is displayed.

If any of the responses return Not-Acquired or Not-Registered (and the APN is correct), the wireless network operator should be contacted for further troubleshooting.
Please note that it may take several seconds (or longer) for the HMU-3640™ to communicate with the modem and acquire the wireless network.

GPS Verification
The next step is to verify that the GPS receiver is seeing enough satellites to obtain a valid GPS position. Again, installers have two choices on how to perform this verification. First, like the Comm Verification, there is a GPS status LED (i.e., the one closest to the SMA connector). If this LED is solid, then the LMU has found GPS service.
If the LED is not visible then GPS service may be verified using an AT Command:

The response should be similar to:

Installers are looking for the 3D-RTIME setting along with a valid Lat, Long pair (i.e. something other than 0). If the GPS receiver does not have a valid lock within 2-3 minutes.

Inbound Verification
The last item to verify is that the HMU-3640™ is sending data to the correct server. In general, this is a two-step process that will need the aid of an observer on the back end. That is, a technician will have to be logged in so they can monitor data coming into the backend mapping/vehicle management application.
First, verify that the HMU-3640™ is using the correct Inbound IP address by using:

• AT$APP INBOUND?

The response should be similar to:

The installer will need to verify with a backend technician that the, URL (myURL.myCompany.com ), IP address (ddd.ddd.ddd.ddd) and port () are correct.
The second step is to verify that the HMU-3640™ is sending data. The best way to do this is to force the HMU-3640™ to send in an unacknowledged Event Report (i.e., its current GPS location) with the following command:

The HMU-3640™ will respond with: OK
The backend monitor must then be contacted to confirm that they received an Event Report with Event Code 255. Assuming that all three sections have passed, the installation can be considered to be complete.

Verification via SMS
The current Comm, GPS and Inbound status of a GSM LMU can be obtained via SMS provided you have access to an SMS capable phone or PDA.
Using your handset, send the following SMS Message to the LMU:

• R0

Within a few minutes, the LMU should return a response in the following format:

APP:

• < App ID>:
  The Application ID value of the LMU indicating the host platform and the wireless networking technology of the LMU.

• < Firmware Version>:
  The current firmware version in use by the LMU

• COM:

  • < RSSI>:
    This is the signal strength the wireless modem sees from the network. In general the LMU is at least scanning for the network if the RSSI is not -113.

  • [./d/D]:
    If the character ‘D’ is present, it indicates the LMU had a data session established when it responded to the status request. For the 8-Bit product line an upper case ‘D’ indicates both the Inbound and Maintenance sockets are ready. The lower case ‘d’ indicates that only the Maintenance socket is ready. A ‘.’ indicates no sockets are ready.

  • [./a/A]:
    This field indicates if the LMU has received an Acknowledgement from the Inbound server. This field will be empty if the LMU has never received an ACK. The lower case ‘a’ will be present if it has received an ACK since the last cold boot (i.e. power cycle) but not the last warm boot (App Restart or Sleep). The upper case ‘A’ will be present if the LMU has received an ACK since the last warm boot. A ‘.’ Indicates no acknowledgement has been received.

  • [./L]:
    This field indicates if the LMU’s log is currently active. An ‘L’ indicates that the log is currently in use (i.e. one or more records have been stored) where a ‘.’ indicates the log is inactive.

  • [IP Address]:
    This is an optional field if and is only present if the LMU has established a valid data session. This field will contain the current
    IP address of the LMU as assigned by the wireless network. Note that if you see a value of 192.168.0.0, this is an indication that the LMU has not been able to establish a data session.

  • [ ]
    The current Access Point Name in use by a GSM LMU.

• GPS:

  • [Antenna <Short/Open/Off>]:
    This field, if present, indicates a problem with the LMU’s GPS antenna. A value of Short indicates that the antenna cable has likely been crushed. A value of Open indicates that the antenna cable is either cut or disconnected. A value of Off indicates that the LMU’ GPS receiver is off.

  • [No Time Sync]:
    If this field is present, it indicates that the LMU’s GPS receiver has not been able to find even a single GPS satellite. This would likely been seen in conjunction with the above antenna error, or if the LMU GPS antenna is otherwise blocked.

  • [ ]:
    If these fields are present it indicates that the LMU has, or had a valid GPS solution. The field indicates how many GPS satellites are currently in use by the LMU. The field indicates the type of fix. The Fix Status types are detailed in the LM Direct Reference Guide.

• INP:

  • < input states>:
    This field details the current state of each of the LMU’s discreet inputs. This field is always 8 characters long. The left most character represents the state of input 7 where the right most represents the state of input 0 (i.e. the ignition). A value of 1 indicates the input is currently in the high state. A value of 0 indicates it is currently in the low state.

  • < vehicle voltage>:
    This field will contain the current reading of the LMU’s internal A/D. This will be the supply voltage provided to the LMU in mV.

• MID:

  • < mobile ID>:
    This will be the current mobile ID in use by the LMU.

  • < mobile ID type>:
    This will be the type of Mobile ID in use by the LMU. The available types are, Off, ESN, IMEI, IMSI, USER, MIN and IP ADDRESS.

• INB:

  • < inbound IP address>:
    This is the current IP address in use by the LMU. This value should match the IP address of your LM Direct™ server.

  • < inbound port>:
    This is the current UDP port the LMU will use to deliver its LM Direct™ data. This value should match UDP port you are using on your LM Direct™ server. It is typically 20500.

  • < Inbound Protocol (LMD/LMX)>:
    This is the current UDP/IP messaging protocol in use by the LMU. In general it should be LMD.

CalAmp Locations

CalAmp’s Corporate headquarters is located in Irvine, CA, with many divisional and satellite locations across the United States as well as

Corporate Headquarters

15635 Alton Parkway, Suite 250

Irvine, CA 92618

Additional Locations
1401 North Rice Avenue Oxnard, CA 93030
6483 City West Parkway Eden Prairie, MN 55344
2177 Salk Avenue, Suite 200

Carlsbad, CA 92008

40 Pequot Way

Canton, MA 02021

13655 Dulles Technology Drive, Suite 200

Herndon, VA 20171

5th Floor Five Lamps Place

77-80 Amiens, Street Dublin 1 D01 A7V2 Republic of Ireland internationally.

Regulatory Information
Human Exposure Compliance Statement Pursuant to 47 CFR § 24.52 of the FCC Rules and Regulations, personal communications services (PCS) equipment is subject to the radio frequency radiation exposure requirements specified in § 1.1307(b), § 2.1091 and § 2.1093, as appropriate.
CalAmp DataCom Inc. certifies that it has determined that the HMU-3640™ complies with the RF hazard requirements applicable to broadband PCS equipment operating under the authority of 47 CFR Part 24, Subpart E of the FCC Rules and Regulations. This determination is dependent upon installation, operation and use of the equipment in accordance with all instructions provided.
The HMU-3640™ is designed for and intended to be used in fixed and mobile applications. “Fixed” means that the device is physically secured at one location and is not able to be easily moved to another location. “Mobile” means that the device is designed to be used in other than fixed locations and generally in such a way that a separation distance of at least 20 cm is normally maintained between the transmitter’s antenna and the body of the user or nearby persons. The HMU-3640™ is not designed for or intended to be used in mobile applications (within 20 cm of the body of the user) and such uses are strictly prohibited.
To ensure that the HMU-3640™ complies with current FCC regulations limiting both maximum RF output power and human exposure to radio frequency radiation, a separation distance of at least 20 cm must be maintained between the unit’s antenna and the body of the user and any nearby persons at all times and in all applications and uses. Additionally, in mobile applications, maximum antenna gain must not exceed 3.2 dBi.
FCC Rules and Industry Canada (IC) regulatory information Compliance Statement (Part 15.19) The equipment device complies with Part 15 of the FCC Rules. Operation is subject to the following two conditions:

1. This device may not cause harmful interference, and
2. This device must accept any interference received including interference that may cause undesired operation.

Warning (Part 15.21) Changes or modifications not expressly approved by TransCore Amtech Systems could void the user’s authority to operate the equipment. Manufacturer is not responsible for any radio or TV interference caused by unauthorized modifications to this equipment. Compliance Statement (Part 15.105(b))

Note: This equipment has been tested and found to comply with the limits for a Class B digital device, pursuant to part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference in a residential installation. This equipment generates, uses and can radiate radio frequency energy and, if not installed and used in accordance with the instructions, may cause harmful interference to radio communications. However, there is no guarantee that interference will not occur in a particular installation. If this equipment does cause harmful interference to radio or television reception, which can be determined by turning the equipment off and on, the user is encouraged to try to correct the interference by one or more of the following measures:

• Reorient or relocate the receiving antenna.
• Increase the separation between the equipment and receiver.
• Connect the equipment into an outlet on a circuit different from that to which the receiver is connected.
• Consult the dealer or an experienced radio/TV technician for help.

This device complies with Industry Canada license-exempt RSS standard(s). Operation is subject to the following two conditions: (1) this device may not cause interference, and (2) this device must accept any interference, including interference that may cause undesired operation of the device. Le présent appareil est conforme aux CNR d’Industrie Canada applicables aux appareils radio exempts de licence. L’exploitation est autorisée aux deux conditions suivantes :(1) l’appareil ne doit pas produire de brouillage, et (2) l’utilisateur de l’appareil doit accepter tout brouillage radioélectrique subi, même si le brouillage est susceptible d’en compromettre le fonctionnement. Class B digital device notice “CAN ICES-3 (B)/NMB-3(B)” RF Radiation Exposure Statement This equipment complies with the FCC/IC radiation exposure limits set fourth for mobile transmitting devices operation in an uncontrolled environment. End users must follow the specific operating instructions to satisfy RF exposure compliance. The equipment should only be used where there is normally at least 20cm separation between the antenna and all person/user. This transmitter must not be co-located or operation in conjunction with any other antenna or transmitter. Any changes or modifications not expressly approved by the party responsible for compliance could void the user’s authority to operate this equipment.
FOR SOFTWARE, APPLICATION PROGRAMING INTERFACES (APIs) & DOCUMENTATION IMPORTANT: DO NOT INSTALL OR USE THE SOFTWARE OR DOCUMENTATION UNTIL YOU HAVE READ AND AGREED TO THIS LICENSE AGREEMENT. This is a legal agreement between you, the Customer, and CalAmp DataCom Incorporated (“CalAmp”). By installing and/or using the software or documentation, you are consenting to the terms of this License. If you do not agree to the terms of this non-exclusive License Agreement, DO NOT INSTALL OR USE THE SOFTWARE, APIs OR DOCUMENTATION. For a full refund, return the unused media package and all accompanying materials within seven (7) days to CalAmp. Where there is no packaging or media, use of the software and/or documentation constitutes acceptance.
Definitions: As used in this License Agreement, “Software” means CalAmp’s LM Direct ™, LMU Manager™, LapTop Locator™, LMU
Application/Programmable Event Generator™, CDMA LMU Provisioning Tool, GPRS LMU Provisioning Tool, LMU Status, Clone Config, Hex Dump, LM Exchange™ Traffic Monitor, Freewave Base Station Config, Remote Serial Port, App Watcher Service and/or other software products licensed by CalAmp for use in computer applications development or integration including the computer programs, libraries and related materials either contained on the media provided to you by or from CalAmp, or which you have received or downloaded electronically. “Application” means a compiled or executable software program created by Developer that uses some or all of the functionality of the Software. “Software Copies” means the actual copies of all or any portion of the Software including backups, updates, merged or partial copies permitted hereunder or subsequently licensed to you. “Documentation” means the non- Software information contained on the media provided with this package or downloaded and which is used with and describes the operation and use of the Software. “Documentation Copies” means the actual copies of all or any portion of the Documentation including backups, updates, merged or partial copies permitted hereunder or subsequently provided to you. “Related Materials” means all other materials and whatever is provided by or from CalAmp, and the non- Software and non-Documentation contained on the media supplied, downloaded, or otherwise supplied by or from CalAmp for use with the Software and Documentation. “Server” means a single, networked computer that is accessible to other client machines on the network. “User” means (i) a single person using an Application for his/her internal, use or (ii) a single terminal or a single workstation of a computer used only by a person (and not accessed otherwise) for accessing an Application. “Use License” means limited rights granted by CalAmp for deployment of a single Application to a User. “Developer” means a single programmer developing an Application. “Developer License” means the grant of certain limited rights to use and maintain the Software, Software Copies, Documentation, Documentation Copies and Related Materials in development of Applications.
Background: A Developer License is required for each Developer who uses the Software in building Application(s). A Use License is required and must be purchased by Customer for each User to which Customer provides access to an Application (unless a Server or Site license for unlimited or a specified number of users has been purchased). Each Use License is specific to one client-side Application only and may not be used for any other client-side Application. Each Server license is limited to Server-based Applications deployed on that Server for which the license has been purchased as specified in a CalAmp License Certificate. The Software is licensed on a per Developer, and on a per User, per Application basis. In order to preserve and protect its rights under applicable law, CalAmp is not selling you ownership rights to Software or Documentation (owned by or licensed to CalAmp). CalAmp specifically retains title to all CalAmp Software, Documentation and Related Materials and CalAmp licensors retain title to items owned by them.
Duration: This License Agreement is effective from the day you install or start using the Software, or receive or download it electronically, and continues until terminated. If you fail to comply with any provision of the License, termination is automatic, without notice from CalAmp and without the necessity for recourse to any judicial authority. Upon termination, you must destroy the Related Materials, the Software, Documentation and all Software and Documentation copies. CalAmp can also enforce its other legal and equitable rights.
Developer License Only—Uses Permitted: Software and Documentation may be used for the sole purpose of developing Applications and only by a licensed Developer. Software and Documentation may be installed onto a hard disk drive or a Server, access to which is restricted to Developers for which a Developer License has been purchased and may also be stored or installed on a storage device such as a network server, used only to install or access the Software or Documentation on your other computers over an internal network; however, you must have acquired a license for each separate computer on which the Software or Documentation is installed or accessed from the storage device. A Developer License may not be shared or used concurrently on different computers. One backup copy may be made for each legally obtained media copy or electronic copy you have received, provided that all CalAmp and third party licensor information — including copyright notices — are maintained and possession of the copy is retained in a secure location. In addition, you agree to use reasonable efforts to protect the Software and Documentation from unauthorized use, reproduction, distribution or publication. All rights not specifically granted in this License are reserved by CalAmp.
Customer agrees to include the notice “Copyright © 1999 – 2009 CalAmp DataCom Inc., All Rights Reserved” in Applications developed with the Software. Customer agrees to include the following CalAmp Copyright and Government Restricted Use notice in all documentation and in any Application on-line help or readme file.
“Portions of this computer program are owned by CalAmp DataCom Inc., Copyright © l999 – 2009, CalAmp DataCom Inc., All Rights Reserved. Use, duplication or disclosure by the Government is subject to restrictions as set forth in subparagraph ©(1)(ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013 or subparagraphs ©(l) and (2) of the Commercial Computer Software-Restricted Rights at 48 CFR 52.227-19, as applicable. Manufacturer is CalAmp DataCom Inc., 1401 North Rice Ave. Oxnard, CA 93030. Rights are reserved under copyright laws of the United States with respect to unpublished portions of the Software.”
Developer(s) License—Uses Not Permitted: Unless Otherwise Agreed To In Writing with CalAmp, You May Not (1) Make derivative works including but not limited to translations, adaptations, arrangements or any other alteration (each of which would become the property of CalAmp or its licensors, as applicable) or make copies of the Software or Documentation except as permitted above; (2) Make copies of the Related Materials; (3) Use any CalAmp product to translate the product of another licensor unless you have the legal right to do so; (4) Allow a greater number of Developers to access the Software at any one time than the total number of Developer licenses for which you have paid; (5) Rent, lease, sublicense or lend the Software, Software Copies, Documentation, Documentation Copies, Related Materials or your rights under this License or allow access to the Software for unlicensed users; (6) Alter, decompile (except to the limited extent that decompilation by the licensed Developer only is necessary as the only available way to achieve interoperability with other programs and, in that situation, any resulting information cannot be used in developing, producing or marketing any software substantially similar in expression to the Software), disassemble or reverse engineer the Software; (7) Make any attempt to unlock or bypass any initialization system or encryption techniques utilized by the Software or Documentation; (8) Alter, remove or obscure any proprietary legend, copyright or trademark notice contained in or on Software, Documentation or Related Materials; or (9) use the Software to create an Application intended solely to duplicate functionality of an existing CalAmp end user software product.
Use Licenses: For each Server or Site License purchased, CalAmp grants the Customer the right to distribute Applications on a single Server or at a single Site, as the case may be, accessible to the number of individual users (not concurrent users) for which the Server or Site License has been purchased as evidenced by a CalAmp License Certificate. For each Use License purchased, as evidenced by a CalAmp License Certificate, CalAmp grants the Customer the right to distribute a single Application to a single User. In no circumstance may Customer distribute an Application under a site license or concurrent use license unless a comparable license has been purchased for the Software as evidenced by a CalAmp License Certificate. Customer agrees that distribution of an Application to a User will in all cases be accompanied by a license agreement containing at a minimum terms and conditions substantially similar to and at least as restrictive as the following:
The User may not (1) Make derivative works including but not limited to translations, adaptations, arrangements or any other alteration of the Application or make copies of the Application, except one backup copy may be made for each legally obtained copy of the Application, provided that all CalAmp and third party licensor information — including copyright notices — are maintained and possession of the copy is retained in a secure location; (2) Allow access to the Application for unlicensed users; (3) Rent, lease, sublicense or lend the Application or its rights under the license; (4) Alter, decompile, disassemble or reverse engineer the Application; (5) Make any attempt to unlock or bypass any initialization system or encryption technique utilized by the Application; or (6) Alter, remove or obscure any proprietary legend, copyright or trademark notice contained in or on the Application.
The User agrees to use reasonable efforts to protect the Application from unauthorized use, reproduction, distribution or publication.
Audit: Customer shall keep records of all transactions involving Software for five (5) years after the transaction. CalAmp shall have the right upon written notice to audit Customer’s records to verify compliance with this License including the number of Use Licenses granted by Customer. Audit may take place at Customer’s place or business during normal working hours. In the event that there is a discrepancy in excess of five percent (5%) between the number of Use Licenses granted and the number paid for, Customer shall pay all costs related to performing the audit in addition to remitting payment for those licenses granted in excess of those paid for as evidenced by a CalAmp License Certificate.
General: This Agreement represents our entire understanding and agreement regarding the Software, Software Copies, Documentation, Documentation Copies and Related Materials and supersedes any prior purchase order, communication, advertising or representation and may only be modified in a written amendment signed by an authorized CalAmp representative or by a specific prior or subsequent written agreement between the parties. If any provision of this Agreement shall be unlawful, void or for any reason unenforceable, that provision shall be deemed severable from, and shall in no way affect the validity or enforceability of, the remaining provisions.
[edit]2 Limited Warranty
Covering the Physical Media and Printed Materials: CalAmp warrants to you, the original licensee, that the media on which the Software is recorded are free from defects in materials and workmanship under normal use and service FOR A PERIOD OF NINETY (90) DAYS FROM THE DATE OF DEVELOPER LICENSE PURCHASE. CalAmp’s entire liability and your exclusive remedy as to defective media, Documentation or Related Material(s) shall be replacement of the media, Documentation or Related Material(s) by CalAmp. Each defective item, along with proof of license purchase and date, must be sent in a traceable manner to: CalAmp DataCom Inc., 1401 North Rice Ave. Oxnard, CA 93030.
Disclaimer Regarding the Software, Documentations and Related Materials: THE SOFTWARE, DOCUMENTATION AND RELATED MATERIALS ARE PROVIDED “AS IS.” EXCEPT AS MAY OTHERWISE BE EXPRESSLY SET FORTH HEREIN, CALAMP MAKES NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR IMPLIED, WITH RESPECT TO THE SOFTWARE, DOCUMENTATION OR RELATED MATERIALS INCLUDING BY WAY OF EXAMPLE, AND NOT LIMITATION, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. BY WAY OF FURTHER EXAMPLE AND NOT LIMITATION, CALAMP MAKES NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR IMPLIED, WITH RESPECT TO THE ACCURACY, RELIABILITY OR COMPLETENESS OF THE DOCUMENTATION OR THE RELATED MATERIALS. THE ENTIRE RISK AS TO THE USE OF THE SOFTWARE, DOCUMENTATION AND RELATED MATERIALS IS ASSUMED BY YOU. IN NO EVENT SHALL CALAMP BE LIABLE TO YOU OR ANY OTHER PERSON, REGARDLESS OF THE CAUSE, FOR THE EFFECTIVENESS OR ACCURACY OF THE SOFTWARE, DOCUMENTATION OR RELATED MATERIALS OR FOR ANY SPECIAL, INDIRECT, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING FROM OR OCCASIONED BY YOUR USE OF THE SOFTWARE, DOCUMENTATION OR RELATED MATERIALS, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. IN THE EVENT THE FOREGOING IS FOUND BY A COURT OF COMPETENT JURISDICTION TO BE INEFFECTIVE, YOU HEREBY AGREE THAT CALAMP’S MAXIMUM LIABILITY FOR ANY CLAIM ARISING IN CONNECTION WITH THE SOFTWARE, DOCUMENTATION AND/OR RELATED MATERIALS (WHETHER IN CONTRACT, TORT, INCLUDING NEGLIGENCE, PRODUCT LIABILITY OR OTHERWISE) SHALL NOT EXCEED THE LICENSE FEES PAID BY YOU WITH RESPECT TO THE SOFTWARE, DOCUMENTATION AND/OR RELATED MATERIALS AT ISSUE. SOME STATES DO NOT ALLOW THE LIMITATION OR EXCLUSION OF INCIDENTAL OR CONSEQUENTIAL DAMAGES, SO THE FOREGOING PROVISION, WITH RESPECT TO EXCLUDING OR LIMITING SUCH DAMAGES, MAY NOT APPLY TO YOU.
Acknowledgement: You acknowledge that you have read this LIMITED WARRANTY, understand it and agree to be bound by its terms and conditions. You also agree that: (1) No oral or written information or advice given by CalAmp, its dealers, distributors, agents or employees shall in any way increase the scope of this Limited Warranty and you may not rely on any such information or advice; (2) Unless a written governing agreement signed by you and CalAmp exists, this License Agreement is the complete and exclusive statement of agreement between CalAmp and you regarding the licensing of the Software, Documentation and Related Materials and supersedes all proposals, oral or written, and any other communications you may have had prior to purchasing your license; (3) Except for the price and delivery terms agreed upon by both parties, the terms and conditions of this License Agreement shall supersede those set forth in any purchase order where the purchase order conflicts or is inconsistent with or adds to the terms and conditions of this License and those superseded purchase order terms and conditions shall be null and void; (4) You agree to assure that copies of this License Agreement are distributed, read and agreed to by each Developer using the Software and/or Documentation.
Governing Law: This Agreement shall be governed by the laws of the State of California, United States, excluding its conflicts of law principles and excluding the United Nations Convention on Contracts for the International Sale of Goods. You agree to exclusive jurisdiction of California State federal and state courts, Ventura County, for resolution of any dispute related to this Agreement.
U.S. Government Protected Rights: The Software Documentation and Related Materials are provided with RESTRICTED RIGHTS. Use, duplication or disclosure by the Government is subject to restrictions as set forth in subparagraph ©(1)(ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013 or subparagraphs ©(1) and (2) of the Commercial Computer Software-Restricted Rights at 48 CFR 52.227-19, as applicable. Manufacturer is CalAmp DataCom Inc., 1401 North Rice Ave. Oxnard, CA 93030. Rights are reserved under copyright laws of the United States with respect to unpublished portions of the Software.
[edit]3 Regulatory Information
Human Exposure Compliance Statement Pursuant to 47 CFR § 24.52 of the FCC Rules and Regulations, personal communications services (PCS) equipment is subject to the radio frequency radiation exposure requirements specified in § 1.1307(b), § 2.1091 and § 2.1093, as appropriate.
CalAmp DataCom Inc. certifies that it has determined that the HMU-3640™ complies with the RF hazard requirements applicable to broadband PCS equipment operating under the authority of 47 CFR Part 24, Subpart E of the FCC Rules and Regulations. This determination is dependent upon installation, operation and use of the equipment in accordance with all instructions provided.
The HMU-3640™ is designed for and intended to be used in fixed and mobile applications. “Fixed” means that the device is physically secured at one location and is not able to be easily moved to another location. “Mobile” means that the device is designed to be used in other than fixed locations and generally in such a way that a separation distance of at least 20 cm is normally maintained between the transmitter’s antenna and the body of the user or nearby persons. The HMU-3640™ is not designed for or intended to be used in mobile applications (within 20 cm of the body of the user) and such uses are strictly prohibited.
To ensure that the HMU-3640™ complies with current FCC regulations limiting both maximum RF output power and human exposure to radio frequency radiation, a separation distance of at least 20 cm must be maintained between the unit’s antenna and the body of the user and any nearby persons at all times and in all applications and uses. Additionally, in mobile applications, maximum antenna gain must not exceed 3.2 dBi.

FCC Rules and Industry Canada (IC) regulatory information Compliance Statement (Part 15.19) The equipment device complies with Part 15 of the FCC Rules. Operation is subject to the following two conditions:

1. This device may not cause harmful interference, and
2. This device must accept any interference received including interference that may cause undesired operation.

Warning (Part 15.21) Changes or modifications not expressly approved by TransCore Amtech Systems could void the user’s authority to operate the equipment. Manufacturer is not responsible for any radio or TV interference caused by unauthorized modifications to this equipment. Compliance Statement (Part 15.105(b)) Note: This equipment has been tested and found to comply with the limits for a Class B digital device, pursuant to part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference in a residential installation. This equipment generates, uses and can radiate radio frequency energy and, if not installed and used in accordance with the instructions, may cause harmful interference to radio communications. However, there is no guarantee that interference will not occur in a particular installation. If this equipment does cause harmful interference to radio or television reception, which can be determined by turning the equipment off and on, the user is encouraged to try to correct the interference by one or more of the following measures: —Reorient or relocate the receiving antenna. —Increase the separation between the equipment and receiver. —Connect the equipment into an outlet on a circuit different from that to which the receiver is connected. —Consult the dealer or an experienced radio/TV technician for help. This device complies with Industry Canada license-exempt RSS standard(s). Operation is subject to the following two conditions:

1. This device may not cause interference, and
2. This device must accept any interference, including interference that may cause undesired operation of the device.

Class B digital device notice “CAN ICES-3 (B)/NMB-3(B)” RF Radiation Exposure Statement This equipment complies with the FCC/IC radiation exposure limits set fourth for mobile transmitting devices operation in an uncontrolled environment. End users must follow the specific operating instructions to satisfy RF exposure compliance. The equipment should only be used where there is normally at least 20cm separation between the antenna and all person/user. This transmitter must not be co-located or operation in conjunction with any other antenna or transmitter. Any changes or modifications not expressly approved by the party responsible for compliance could void the user’s authority to operate this equipment

References

• Fleet Management Software Solutions | CalAmp
• P65Warnings.ca.gov
• p65warnings.ca.gov/
• 4G LTE | Carrier Aggregation | Qualcomm

Read User Manual Online (PDF format)

Read User Manual Online (PDF format)  >>

Download This Manual (PDF format)

Download this manual  >>