Telematics & Immobilsation
      Back to home
      1. Coastr Help Centre
      2. How to guides
      3. Telematics & Immobilsation

      Coastr - Telematics Installation Guide

      Contents

      1 Scope & Purpose 

      2 Functional Requirements 

      2.a Reporting Events 

      2.b Data Accumulation 

      2.c IO mapping 

      2.d VPOD2 / OBDII interface 

      2.e Starter Disable Functionality 

      3 Add vehicle trackers to Coastr (for third-party installers) 

      1. Scope & Purpose


      This document defines the solution requirements and implementation of PEG script and CTC functionality on LMU2640 for Coastr application.  

      The purpose of this document is to provide a description of implemented core features and functions.


      2. Functional Requirements 


        1. Reporting Events

      Title

      Event#

      Requirements 

      POWUP

      0

      A “Connection Event” is sent when the device detects a transition from internal battery to external battery. 

      ALIVE

      1

      An ‘Alive’ event is an event that is always sent once every 24 hours.

      IGON

      2

      The LMU’s Ignition input (white wire) has transitioned from low to high.

      IGOFF

      3

      The LMU’s ignition input (white wire) has transitioned from high to low.

      START

      4

      The LMU’s speed is equal to or has exceeded the Moving Speed Threshold Parameter and the LMU was previously not moving. Default is speed > 5 mph for 10 seconds.

      STOP

      5

      The LMU’s speed has dropped below the Moving Speed Threshold Parameter. Default is speed < 5 mph for 120 seconds.

      PRIOD

      6

      Periodic or “Breadcrumb” events are sent only during an Ignition On state. This event sends every 1-minute or 45-degree heading change, or 1000m travelled (whichever is first).

      SPEED 

      7

      A ‘Speeding Start’ event is sent when the GPS speed exceeds 85 mph. 

      NOSPD

      8

      A ‘Speeding End’ event is sent when the GPS speed falls below 85 mph after a ‘Speeding Start’ event.

      GPSY 

      9 

      GPS Acquired – The GPS receiver acquired a fix. 

      GPSN 

      10 

      GPS Lost – The GPS receiver has lost its fix. 

      CGAIN 

      11 

      Comm Up – The wireless modem connected to the data network. 

      CLOSS 

      12 

      Comm Down – The wireless modem lost its data connection. 

      INxHI, INxLO 

      14 - 17 

      Input Transition – A Digital Input (x) transitioned its state to High or Low. 

      PND_DISCONNECT

      18

      Reported when a PND device is disconnected from AUX-2

      PND_CONNECT

      19

      Reported when a PND device is connected to AUX-2

      ACCEL 

      20 

      This is a Driver Behavior event known as “Hard Braking”. If the device detects an exceeding deceleration of 0.28g for a minimum of 800ms, this will send.

      DECEL 

      21 

      This is a Driver Behavior event known as “Hard Acceleration”. If the device detects an exceeding acceleration of 0.30g for a minimum of 650ms, this will send.

      TOWING_START 

      28 

      Movement has been detected in a powered device with its ignition off. 

      TOWING_STOP 

      29 

      Movement has stopped in a powered device with its ignition off. 

      HARD_CORNERING_LEFT 

      30 

      This is a Driver Behavior event known as “Hard Right Cornering”.  If the device detects an exceeding right cornering of 0.32g for a minimum of 650ms, this will send.

      HARD_CORNERING_RIGHT 

      31 

      This is a Driver Behavior event known as “Hard Left Cornering”.  If the device detects an exceeding left cornering of 0.32g for a minimum of 650ms, this will send.

      LONG_IDLE 

      34 

      Ignition On with no movement for longer than the configured threshold time period. 

      Starter Disabled

      80

      Sent when Output was set to disable the starter

      Starter Enabled

      81

      Sent when Output was set to enable the starter

      Location of Disabled Asset

      82

      Sent at Ignition Off if starter was disabled.

      Driver Pairing Buzzer ON

      85

      Driver Pairing Buzzer has been turned ON

      Driver Pairing Disassociated

      86

      Driver Disassociated on Device, will buzz at next ignition On requiring new KeyFob swipe.

      BPWUP 

      200 

      Battery Power On – Indicates that a battery powered device has switched to operating on its own battery power. It has been disconnected from external power. 

      BPOSN 

      201 

      Position. This is the periodic location update for a device on internal battery power or an externally powered device that is moving with its ignition off (being towed). 

      BMOTN 

      202 

      Motion – Indicates the detection of motion in the Ignition Off state (i.e., towing). 

      BBATLO 

      203 

      Battery Low – The voltage provided by the internal battery in a device has fallen below its threshold of 3400 millivolts. 

      BBATOK 

      204 

      Battery OK – The voltage provided by the internal battery in a device has been restored to below its threshold of 3400 millivolts. 

      VBATLO

      205

      Low Battery Alert is sent if a vehicle battery is less than 11.49v at Ignition Off

      VBATOK

      206

      Battery OK Alert is sent if a vehicle battery is more than 11.49v at Ignition Off

      Config Update Complete

      220

      LMU Configuration OTA Update is completed.

      OBD FW Update Complete

      221

      OBDII Firmware OTA Update is completed.

      OBD DB Update Complete

      222

      OBDII Database OTA Update is completed.

      LMU FW Update Complete

      223

      LMU Firmware OTA Update is completed.

       

      b. Data Accumulation

      The LMU sends the following vehicle bus accumulated data in each of the event report packets. 

      Accum Label

      Accum Index

      Description

      Unit (PEG Behavior in CTC)

      GPSOdometer

      0

      GPS distance traveled running total

      m

      VBSpeed

      6

      Speed read from vehicle OBDII interface

      mi/hr

      VBOdometer

      7

      Odometer read from vehicle OBDII interface

      mi

      ADC ExternalPowerVoltage

      15

      Vehicle Battery Voltage Reading

      mV

      ADC DevicePowerVoltage

      16

      Internal Device Battery Reading

      mV

      EngineHours

      17

      Lifetime Engine HRs – Calculated On Device Ign On/Off. OBDII is not the source.

      s

      VBEngineSpeed

      18

      OBDII Engine Speed (RPM)

      r/min

      IdleHours

      19

      Lifetime (of the device) idle time reading. Calculated While GPS Acquired.

      s

      VBThrottlePosition

      20

      OBDII Engine Throttle Position

      %

      VBFuelPercent

      25

      OBDII Fuel %  read from the vehicle

      %

       

      c. IO mapping 

      The Input and Output pins definitions for LMU-2640 are as follows:

      Pin

      Signal Name 

      Description 

      5C908 Harness Colour 

      Input or Output 

      1 

      GND 

      Ground 

      Black 

      Ground 

      2 

      OUT-0 

      Output 0 

      Green 

      Output 

      3 

      IN-1 

      Input 1 – Digital Input 

      Blue 

      Input 

      4 

      SER_IN 

      Serial Input 

      Blue 

      Input 

      5 

      ADC-1 

      Analog to Digital Input 1 

      Pink 

      Input 

      6 

      IN-3 

      Input 3 – Digital Input 

      Violet 

      Input 

      7 

      IN-4 

      Input 4 – Digital Input 

      Grey 

      Input 

      8 

      IN-0 

      Ignition 

      White 

      Input 

      9 

      VDD 

      VDD Reference Output (20-25mA Max) 

      Orange 

      Output 

      10 

      OUT-1 

      Output 1 – Digital Output (Open Collector) 

      Brown 

      Output 

      11 

      OUT-2 

      Output – 2 Digital Output (Open Collector) 

      Yellow 

      Output 

      12 

      IN-2 

      Input 2 – Digital Input 

      Orange 

      Input 

      13 

      SER_OUT 

      Serial Output 

      Green 

      Output 

      14 

      VCC 

      Primary Power Input 

      Red 

      Power 

      15 

      GND 

      Primary Ground 

      Black 

      Ground 

      16 

      1BB-GND 

      1 Bit Bus Ground 

      Black 

      Ground 

      17 

      1BB-D 

      1-Bit Bus Data 

      White/Blue 

      Input / Output 

      18 

      Aux - TxD 

      Aux Port 2 - Transmit Data 

      White/Orange 

      Input 

      19 

      Aux -GND 

      Aux Port 2 - Ground 

      Black 

      Ground 

      20 

      Aux - RxD 

      Aux Port 2 - Receive Data 

      White/Yellow 

      Output 


      d. VPOD2 / OBDII interface

      The VPOD2 adapter carries out the OBDII functionality in the solution to read OBDII PIDs from the vehicle bus systems. The OBDII data collected will be added to the accumulators as listed above. 

      For connecting the VPOD2 adapter, the OBDII connector is to be connected to the vehicle’s OBDII port and the 5-pin connector P1 should be connected to the AUX1 connector of the 5C908 harness cable. The VPOD2 white wire should be left open (non connected). 


      e. Starter Disable Functionality

      The starter disable function is carried out by LMU Outputs and relays. The Starter Disable Relay (p/n 5C875) is used when the LMU will need to immobilize the vehicle.  This relay doesn’t stop the vehicle, it limits the vehicle from re-starting.

      For the Coastr solution, the Relay is controlled by Output 1 (brown wire) of the LMU, as this is used with the desired triggers in the device configuration for correct CTC event reporting. The Starter Disable (SD) is critically dependent on correct wiring of output relays and also on correct the vehicle immobilization installation to disable the starting of the vehicle. It is highly advised that the immobilization installation cut is done on the vehicle starter wire and not on the ignition cut or fuel pump as it can lead to serious vehicle disruption. CalAmp recommends that the professional vehicle system installation experts should carry out starter disable installations as they would have the skills, expertise and knowledge of vehicle specific installations.

      Below image shows a typical installation example with SD relay. There are many ways to wire a disable relay in the vehicle loom as can be advised by professional vehicle installers.


      Starter Disable functionality summary: 

      • SD state is set by param-write CTC API command 1052,2, FFFFFFFF80000000
      • SD state is cleared by param-write CTC API command 1052,2, FFFFFFFF00000000
        • API commands sent to the device are shown on CTC device history as DeviceCommandEvent message type
        • DeviceCommandEvent messages are external commands and are not device configuration related such as AVL report types. These can only be sent via APIs by the CTC users with their individual account credentials.
      • SD state set event report type is code 80 with label STARTER_DISABLED
      • SD state cleared event report type is code 81 with label STARTER_ENABLED
      • If the starter is disabled, the device will send an event report with label Location of Disabled Asset at key on ignition and ignition off.
      • When an API command is sent to the device to set SD state, it will wait till the device is in ignition off and non-moving state (Default is speed < 5 mph for 120 seconds) to set Output 1 i.e. disable vehicle from re-starting. 
      • If the device is in mid-journey when the SD command is sent, it will wait until the device is in ignition off and non-moving state to set Output 1 i.e. disable vehicle from re-starting.
      • When the device has lost GSM comms or it is not available, it will not be able to actively process the API commands sent OTA at that time. It will queue the message until the device obtains Comms connection and then set SD state at following Ignition Off trigger event.
      • When the device wakes up and the SD state was already set following Ignition Off, it will retain the SD set state.
      • When the device wakes up and SD is cleared, it will retain SD clear state.

      Starter Disable control from CTC API:

      API Post command: /devicecommands/device/{id}/parameterconfig/{parameterid}/{index}/{value}


      Set PEG Enables 127 which in-turn will set Output 1 to immobilize and send a report with label ‘starter disabled’.

      Example:

      https://connect.calamp.co.uk/connect/services/devicecommands/device/79922/parameterconfig/1052/2/0xFFFFFFFF80000000?v=2.0 


      Clear PEG Enables 127 which in-turn will clear Output 1 to remove immobilizer and send report with label ‘starter enabled’.

      Example: 

      https://connect.calamp.co.uk/connect/services/devicecommands/device/79922/parameterconfig/1052/2/0xFFFFFFFF00000000?v=2.0 



      3. Add vehicle trackers to Coastr (for third-party installers) 

      How to add new vehicles and activate vehicle trackers on the Coastr platform (for third-party installers) 

      • Open your Web Browser (preferably Google Chrome) and login at tenant.coastr.com using the username (email) and password you’d have received from support@coastr.com (Please send an email to this email address if you do not have login details)

      • Once logged in, you’ll see the Dashboard. On the left navigation menu, click on Fleet and then Fleet Inventory.

      • Next, click on the ‘Add A Vehicle’ button on the top-right corner of the page and then enter the Vehicle Registration Number in the Search box and click on the Search button.



      • This will bring up and fill all the vehicle details from the DVLA vehicle database

      • Next, click on the Frog Diagram box below the Transmission Type box and select an appropriate frog diagram corresponding to the body type of the vehicle from the options in the dropdown list

      • Enter the ESN number (from the telematics device fitted in this vehicle) into the Telematics Device ID field which is below the vehicle model name field

      • Once this is done, click on the yellow ‘Add Vehicle’ button on the top to add this vehicle to the fleet inventory

      • If the vehicle already exists in the Fleet Inventory, then click on the vehicle to continue and then directly enter the ESN number into the Telematics Device ID field



      • Scroll down the page and click on the Save button to save the ESN number to this vehicle

      • Refresh the page to confirm if the ESN number was saved successfully

      • Now, click on Fleet Dashboard on the left navigation menu  to confirm the visibility of the vehicle on the map

      • You can enter and select the Vehicle Registration Number in the ‘Registration No.’ field to find and highlight the vehicle on the map



      • Click on the vehicle icon of the selected vehicle to access/bring up the vehicle detail panel on the right using which the  immobilisation/mobilisation function can be tested