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
- Parameters:
- 26
- Commands:
- 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 commandcustom
[ 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 voltagebattery
- Chargingcharge
- Device temperaturedeviceTemp
- Driver ID (RFID / iButton)driverUniqueId
- Fault codes (DTC)dtcs
- Engine loadengineLoad
- Fuelfuel
- Fuel consumptionfuelConsumption
- Fuel levelfuelLevel
- Fuel usedfuelUsed
- HDOPhdop
- Ignitionignition
- Photoimage
- Motionmotion
- OBD odometerobdOdometer
- OBD speedobdSpeed
- Odometerodometer
- Mobile operatoroperator
- External powerpower
- RPMrpm
- Satellitessat
- Trip odometertripOdometer
Numbered inputs and sensors
- Analog inputs (adc1, adc2…)
- Inputs (in1, in2…)
- IO elements (io1, io2…)
- Temperature sensors (temp1, temp2…)
[ Alarms the protocol can report ]
- Accidentaccident
- GPS antenna cutgpsAntennaCut
- Harsh accelerationhardAcceleration
- Harsh brakinghardBraking
- Jammingjamming
- Tamperingtampering
- Towingtow
[ Protocol-specific attributes ]
di · tagId

