Contact Us

    If you still have questions or prefer to get help directly from an agent, please submit a request.
    We’ll get back to you as soon as possible.

    Please fill out the contact form below and we will reply as soon as possible.

    • Digital Matter Site
    • Contact Us

    CalAmp Support

    Written by Matthew Clark-Massera

    Updated at January 27th, 2023

      Contact Us

      If you still have questions or prefer to get help directly from an agent, please submit a request.
      We’ll get back to you as soon as possible.

      Contact Support
      • Home
      • Telematics Guru
      • Third Party Devices

      Table of Contents

      CalAmp Hardware Setup: Calamp record to TG value mapping: Event Code Mapping: Accumulator Mapping:

      Telematics Guru (TG) now has a basic implementation of the CalAmp’s LM Direct protocol. 

      It is not possible to configure the device via TG. 

      CalAmp Hardware Setup:

      • The device must use UDP
      • Send messages to your TG server, port 8995. Server URLs for your region shown below
      • It is important that the device be set to send messages in chronological sequence from oldest to newest. To make sure that this happens, all messages should be set to the same priority.
      • Set the device up to report it's IMEI, and use this as the Serial when creating the asset in Telematics Guru.
      Region Device URL IP Address*
      APAC01 device-apac01.telematics.guru 40.82.219.2
      APAC02 device-apac02.telematics.guru 40.82.219.4
      APAC03 device-apac03.telematics.guru 40.82.219.106
      APAC04 device-apac04.telematics.guru 40.82.220.205
      EMEA01 device-emea01.telematics.guru 52.179.86.26
      EMEA02 device-emea02.telematics.guru 40.119.147.99
      EMEA03 device-emea03.telematics.guru 40.119.152.46
      EMEA04 device-emea04.telematics.guru 40.119.153.184
      AMER01 device-amer01.telematics.guru 20.185.104.80

      Calamp record to TG value mapping:

      The following three CalAmp message types are implemented:

      • Event Report (2)
      • Locate Report (8)
      • User Data with Accumulators (9)

      When possible these records have the following values mapped:

      • Log Reason (event code, see Event Code Mapping table below)
      • Sequence Number
      • Date Time
      • Altitude
      • GPS Fix OK
      • GPS Fix 3D
      • Speed KmH
      • Heading
      • Latitude
      • Longitude
      • Inputs (from LMU Status)
      • Analogues (as in Accumulator Mapping table below)

      Event Code Mapping:

      Event Code Log Reason
      0 If Ignition on then “Distance Travelled” else “Heartbeat”
      20 End of Trip
      21 Start of Trip
      31, 32 Heartbeat
      55 Driver ID Read
      [60, 81] Input Changed
      [90, 97] Speed Change
      110 Harsh Acceleration
      111 Harsh Brake
      112, 113 Harsh Cornering
      Other If Ignition on then “Heading Change” else “Elapsed Time”

      Accumulator Mapping:

      Accumulator ID TG Meaning
      0 Analog 1 (External Voltage)
      1 Analog 2 (Battery Voltage)
      2 Analog 3 (Device Analog 1 if present)
      6,7 Driver Id Mapped as IButton
      8 Analog 9 (RSSI ASU)
      Other Ignored
      help desk calamp aid

      Was this article helpful?

      Yes
      No
      Give feedback about this article

      Related Articles

      • Setup For Pivotel Smartone devices
      • Teltonika Device Setup
      • JDLink - Telematics Guru

      Subscribe to Partner News

      Subscribe to our mailing list to receive Digital Matter news, product and tehnical updates, and more.

      Subscribe

      Copyright © Digital Matter . All Rights Reserved.

      Privacy Contact Support

      Knowledge Base Software powered by Helpjuice

      DM Logo
      Expand