Coban protocol

Integration level: params + settings
Protocol used by GPS tracking devices manufactured by Coban headquartered in China.
flespi parses the Coban protocol messages into a JSON object with the fields listed below in the Parameters tab.
acc.alarm
boolean
ACC alarm event
alarm.event
boolean
Alarm event triggered
arm.status
boolean
Device arm status (true - device armed, false - device disarmed)
battery.charging.status
boolean
Battery charging status
battery.low.alarm
boolean
Battery low alarm event
battery.voltage
number
volts
Internal battery voltage
can.dtc
string
Diagnostic trouble code read from CAN
can.engine.coolant.temperature
number
celsius
Engine coolant temperature read from CAN
can.engine.load.level
number
percentage
Calculated engine load level read from CAN
can.engine.rpm
number
rpm
Engine RPM read from CAN
can.fuel.consumption
number
liters/h
Engine fuel rate read from CAN
can.fuel.consumption.distance
number
liters/100km
Fuel consumption read from CAN
can.onboard.power.voltage
number
volts
CAN onboard power voltage
can.throttle.pedal.level
number
percentage
Throttle pedal push level read from CAN
can.total.driving.time
number
hours
Engine run time read from CAN
can.vehicle.mileage
number
km
Total vehicle mileage read from CAN
can.vehicle.speed
number
km/h
Vehicle speed read from CAN
channel.id
number
ID of channel that received a message
device.id
number
ID of device that received a message
device.name
string
Name of device that received a message
device.temperature
number
celsius
Temperature of device
device.type.id
number
ID of device type of device that received a message
door.alarm
boolean
Door alarm event
door.open.status
boolean
Door open status
engine.blocked.status
boolean
Engine blocked status, true - engine is blocked, false - engine isn't blocked
engine.ignition.status
boolean
Engine ignition status
event.code
string
Unique event identifier string
fuel.alarm
boolean
Fuel alarm event
fuel.level
number
percentage
Fuel level percentage
geofence.alarm
boolean
Geofence alarm event
gnss.status
boolean
GNSS receiver on/off status
gsm.cellid
number
GSM base station ID
gsm.lac
number
GSM location area code
gsm.mcc
string
GSM mobile country code
gsm.mnc
string
GSM mobile network code
ident
string
Device unique identificator and optional password
movement.event
boolean
Movement detected
overspeeding.event
boolean
Overspeeding detected
peer
string
IP:port from which device connecting to the channel
position.altitude
number
meters
Altitude value for position
position.direction
number
degrees
Heading angle at position detection moment
position.latitude
number
degrees
Latitude coordinate value
position.longitude
number
degrees
Longitude coordinate value
position.satellites
number
Quantity of satellites used to calculate coordinates for given position information
position.speed
number
km/h
Instant speed at position detection moment
position.valid
boolean
Is position information accurate and valid for given timestamp
power.off.alarm
boolean
Power of alarm event
protocol.id
number
ID of protocol
server.timestamp
number
seconds
Timestamp when server received a message
timestamp
number
seconds
Message timestamp
vibration.alarm
boolean
Vibration alarm event
Properties
Custom command
custom
Send custom command to device
payload: Command text to send
Set geofence
{"payload":"114,22.553276,113.903516;20.553276,114.903516"}
Set server IP:port
{"payload":"122,192.168.1.1,9000"}
Cut off oil and power
{"payload":"109"}

To connect your tracker using the Coban protocol, you need to have a coban channel created first.

Point your tracker to the channel's IP:port via SMS or configuration tool provided by the vendor.

Then create a device instance for your tracker and use a 15-character IMEI (usually specified on the tracker casing) in the ident field.

Use the Toolbox tab on the device screen to check if the messages are coming.

If the messages in Toolbox are colored red (past) or grey (future), try changing the timezone setting via the SMS command or on the Settings tab of the device screen.