Tripia relay configuration

Tripia is a relay protocol used to transmit vehicle telematics data to the Tripia platform in JSON format.
The Tripia protocol supports transmission of:
— vehicle location and speed data
— trip information
— vehicle status data
— sensor readings
— GPS, ADAS, and DMS events
— CAN bus data
— driver identification information
Data is transmitted in real time.
 

How to add a relay

1. Log in to the Administration panel
2. Open the Vehicles tab
3. Locate the required vehicle, right-click it, and select Relaying from the context menu
4. In the opened window, click Add 
Tripia relay configuration
5. In the Configuration window, enter the relay settings.

Connection parameters

When creating an endpoint, use the following settings:
  Parameter
  Value
  Format
  Tripia
  Host
  64.225.12.166
  Port
  3000
  Protocol
  TCP
  Data Format
 JSON

Data transmission interval

Data is transmitted automatically:
— every 30 seconds when ignition is ON
— every 1 minute when ignition is OFF
 

Transmitted data

Provider information

The following provider information is transmitted:
• Provider Name
• Provider Code

Vehicle information

The following vehicle information is transmitted:
• Vehicle identifier
• License plate number
• Dispatcher information

Event registration data

The following timestamps are transmitted:
• Event Timestamp
• Sent Timestamp

GPS data

The following navigation parameters are transmitted:
• Latitude
• Longitude
• Speed
• Heading
• Altitude
• Number of satellites
• HDOP
• PDOP

Connection data

The following cellular network parameters are transmitted:
• Signal strength
• Mobile operator (MCC/MNC)
• Connection type
• Cell ID

Vehicle status

The following status information is transmitted:
• Ignition status
• Movement status
• Odometer
• Engine hours
• Battery voltage

GPS events

The following GPS-related events are supported:
• Battery disconnected
• Signal jamming detected
• Satellite loss
• Vehicle towing detected
• Communication signal lost
• Communication signal restored
• Harsh acceleration
• Harsh cornering
• Harsh braking
• Crash detection

GPS sensor data

The following sensor data can be transmitted:
  • Temperature sensors
  • Door and body status sensors
— Driver door
— Passenger door
— Side cargo door
— Rear cargo door
— Engine hood
  • Additional sensors
 — Panic button

Telemetry capabilities

The following subsystem availability indicators are transmitted:
• ADAS
• DMS
• Reefer
• CAN Bus
• Driver ID

ADAS events

The following Advanced Driver Assistance System (ADAS) events are transmitted:
• FCW (Forward Collision Warning)
• LDW (Lane Departure Warning)
• LDWL
• LDWR
• PCW
• PROX

DMS events

The following Driver Monitoring System (DMS) events are transmitted:
• Blocked
• Face Lost
• Distraction
• Frequent Yawning
• Looking Aside
• Smoking
• Phone Calling
• Drowsiness
• Seatbelt Violation

CAN bus data

The following CAN bus parameters are transmitted:
• Fuel level (%)
• Fuel volume (liters)
• Fuel load
• Fuel consumption
• Vehicle speed
• Odometer
• Engine hours
• Driver door status
• Passenger door status

Driver ID data

The following driver identification information is transmitted:
• Identifier type
• Identifier code
• Driver ID
• Driver name
 

Example transmitted packet structure

When sending data to Tripia, the system generates a JSON packet containing vehicle information, location data, sensor readings, events, and telemetry information.
The packet structure includes the following sections:
{
  "provider": {
    "name": "Providers Name",
    "code": "1234abc"
  },
 
  "dispatcher": {
    "name": "Dispatcher Name",
    "identifier": "1234abc",
    "licensePlate": "1234abc"
  },
 
  "registry": {
    "eventTimestamp": "2016-01-01T00:00:00Z",
    "sentTimestamp": "2016-01-01T00:00:00Z"
  },
 
  "gps": {
    "latitude": 123.456789,
    "longitude": 123.456789,
    "speed": 100,
    "heading": 123,
    "altitude": 123,
    "satellites": 12,
    "hdop": 1.2,
    "pdop": 1.2
  },
 
  "connection": {
    "signal": 85,
    "operatorMCCMNC": "Entel",
    "type": 2,
    "cellID": 123456789
  },
 
  "status": {
    "ignition": 1,
    "movement": 1,
    "odometer": 12345678.9,
    "hourMeter": 12345678.9,
    "battery": 12.2
  },
 
  "gpsEvents": {
    "batteryDisconnected": 0,
    "jamming": 1,
    "satellitesLost": 0,
    "towedVehicule": 1,
    "signalLost": 0,
    "signalRecovered": 1,
 
    "driving": {
      "harshAcceleration": 1,
      "harshTurn": 1,
      "harshBraking": 1,
      "crash": 1
    }
  },
 
  "gpsSensors": {
    "temperature1": 12.3,
    "temperature2": 12.3,
    "temperature3": 12.3,
    "temperature4": 12.3,
    "temperature5": 12.3,
    "temperature6": 12.3,
 
    "driverDoor": 0,
    "copilotDoor": 0,
    "sideLoadingDoor": 0,
    "rearLoadingDoor": 0,
    "engineHood": 1,
    "panicButton": 0
  },
 
  "telemetry": {
    "adas": 0,
    "dms": 1,
    "reefer": 0,
    "canbus": 1,
    "driverid": 0
  },
 
  "adasEvents": {
    "fcw": 1,
    "ldw": 1,
    "ldwl": 1,
    "ldwr": 1,
    "pcw": 1,
    "prox": 1
  },
 
  "dmsEvents": {
    "blocked": 0,
    "faceLost": 0,
    "distraction": 0,
    "frequentYawning": 0,
    "lookingAside": 1,
    "smoking": 0,
    "calling": 1,
    "drowsiness": 0,
    "seatbelt": 1
  },
 
  "canbusData": {
    "fuelPercent": 12,
    "fuelLiters": 128,
    "fuelLoad": 80,
    "odometer": 12345678.9,
    "speed": 123,
    "fuelConsumption": 11.12,
 
    "driverDoor": 0,
    "copilotDoor": 1,
    "engineHours": 12345678.9
  },
 
  "driveridData": {
    "type": 1,
    "codeId": "123456789",
    "driverName": "Nombre conductor",
    "driverId": "123456789"
  }
}
The JSON example shown above is provided for reference only.
The actual set of transmitted fields depends on:
— the connected hardware
— relay configuration settings
— available vehicle sensors
— supported telemetry subsystems and integrations