Cargo protocol

Integration level: params + settings
Protocol used by GPS tracking devices manufactured by CarGo headquartered in Ukraine.
flespi parses the Cargo protocol messages into a JSON object with the fields listed below in the Parameters tab.
ain
number
volts
Voltage on the analog input
alarm.event
boolean
Alarm event triggered
battery.voltage
number
volts
Internal battery voltage
case.status
boolean
Case opened status
channel.id
number
ID of channel that received a message
counter.impulses
number
Impulses counter
device.configuration.id
number
Configuration profile index
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
din
number
Digital inputs bitmask
event.enum
number
Event code, full list of codes available at separate table
event.priority.enum
number
Event priority enum
external.powersource.voltage
number
volts
External power voltage
fuel.level
number
percentage
Fuel level percentage
fuel.volume
number
liters
Fuel volume
gsm.signal.level
number
percentage
GSM signal strength level
ibutton.code
string
Hexadecimal code of connected iButton
ident
string
Device unique identificator and optional password
liquid.sensor.fuel.temperature
number
celsius
Fuel temperature reported by LLS
movement.status
boolean
Current movement state
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
protocol.id
number
ID of protocol
sensor.temperature
number
celsius
Temperature sensor value
server.timestamp
number
seconds
Timestamp when server received a message
timestamp
number
seconds
Message timestamp
trailer.id
string
Trailer ID
trip.mileage
number
km
Distance driven since engine start
vehicle.mileage
number
km
Total calculated mileage
Properties
Custom command
custom
Send custom text encoded in Codec12
hex: Payload is encoded as HEX string
crlf: Add CR and LF bytes after text payload
payload: Text or hex data to send
Query device configuration
{"payload":"@info:conf@"}

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

Point your tracker to the channel's domain name: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.

It is possible to configure CarGo devices OTA using the flespi web-based configurator tool. To connect CarGo to Wialon or another platform via flespi please read this article.