castel protocol

TrackeraX decodes the castel protocol on port 6086. These are the devices that use it, the data it reports and the commands you can send to them.

Port
6086
Models
31
Brands
2

Devices that use castel

Commands you can send from TrackeraX

Available from the web platform and the apps. The custom command sends any text the device firmware accepts.

  • Engine stop engineStop
  • Engine resume engineResume
  • Custom command custom

Data reported by the castel protocol

Parameters the server decodes from this protocol. In TrackeraX you turn them into sensors, alerts and reports. Each model reports the ones its firmware and wiring allow.

  • Battery voltage battery
  • Device temperature deviceTemp
  • Fault codes (DTC) dtcs
  • Fuel consumption fuelConsumption
  • G-sensor gSensor
  • Ignition ignition
  • Odometer odometer
  • External power power
  • Satellites sat
  • Trip odometer tripOdometer

Numbered inputs and sensors

  • Analog inputs (adc1, adc2…)
  • Temperature sensors (temp1, temp2…)

Alarms the protocol can report

  • Accident accident
  • Fatigue driving fatigueDriving
  • Harsh acceleration hardAcceleration
  • Harsh braking hardBraking
  • Harsh cornering hardCornering
  • High RPM highRpm
  • Idling idle
  • Lane change laneChange
  • Low power lowPower
  • Overspeed overspeed
  • Power off powerOff
  • Power on powerOn
  • Tampering tampering
  • Temperature temperature
  • Towing tow
  • Vibration vibration

Protocol-specific attributes

fault · pid

All protocols · Watch live demo