ruptela2 protocol
TrackeraX decodes the ruptela2 protocol on port 6302. These are the devices that use it, the data it reports and the commands you can send to them.
- Port
- 6302
- Models
- 1
- Brands
- 1
Devices that use ruptela2
Commands you can send from TrackeraX
Available from the web platform and the apps. The custom command sends any text the device firmware accepts.
- Custom command
custom
Data reported by the ruptela2 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 - Charging
charge - Device temperature
deviceTemp - Driver ID (RFID / iButton)
driverUniqueId - Fault codes (DTC)
dtcs - Engine load
engineLoad - Fuel
fuel - Fuel consumption
fuelConsumption - Fuel level
fuelLevel - Fuel used
fuelUsed - HDOP
hdop - Ignition
ignition - Photo
image - Motion
motion - OBD odometer
obdOdometer - OBD speed
obdSpeed - Odometer
odometer - Mobile operator
operator - External power
power - RPM
rpm - Satellites
sat - Trip odometer
tripOdometer
Numbered inputs and sensors
- Analog inputs (adc1, adc2…)
- Inputs (in1, in2…)
- IO elements (io1, io2…)
- Temperature sensors (temp1, temp2…)
Alarms the protocol can report
- Accident
accident - GPS antenna cut
gpsAntennaCut - Harsh acceleration
hardAcceleration - Harsh braking
hardBraking - Jamming
jamming - Tampering
tampering - Towing
tow
Protocol-specific attributes
tagId