This protocol is used by ATrack GPS tracking devices. Please also read our guide on how-to connect ATrack device to flespi in few mouse clicks.

Below is the list of parameters that can appear in the messages received by the channel via atrack protocol. In most parameters, the name consists of tags split by dots: tag1.tag2.tag3.tag4... Each tag defines a certain area of an application, e.g. any parameter that contains mileage data has the 'mileage' tag in the name and any parameter related to fuel control contains the 'fuel' tag. By default JSON fields of the message received by a channel via this protocol can only contain the below-specified parameters. Any additional parameter will be prefixed by the "custom" tag, e.g. "custom.unspecified-name".

Name Type Unit Description
ain number volts Voltage on the analog input
air.consumption number Mass Air Flow Rate in 0.01grams/sec
autogeofence.status boolean Auto Geo-Fence Area status
backup.battery.voltage number volts Backup battery voltage
battery.low.status boolean Battery low status
can.engine.temperature number celsius Engine temperature reported by CAN
can.fuel.consumed.liters number liters Fuel volume totally consumed by vehicle reported by CAN
counter.impulses number Impulses counter
din number Digital inputs
dout number Digital outputs
driver.message string Driver text message content
engine.event.status boolean Engine event status
external.powersource.status boolean External power source connection status
external.powersource.voltage number volts External power voltage
fuel.level number percentage Fuel level percentage
fuel.sensor.status boolean Fuel sensor event status
gsm.cellid number GSM base station ID
gsm.lac number GSM location area code
gsm.mcc number GSM mobile country code
gsm.mnc number GSM mobile network code
gsm.signal.dbm number dbm Strength of GSM signal
gsm.signal.level number percentage GSM signal strength level
gsm.state.enum number GSM module state
gsm.state.enum.description string GSM module state description
harsh.acceleration.status boolean Vehicle harsh acceleration event status
ibutton.code string Hexadecimal code of connected iButton
ident string Device unique identificator and optional password
message.buffered.status boolean Black box message
movement.status boolean Current movement state
overspeeding.status boolean Overspeeding detected
position.altitude number meters Altitude value for position
position.direction number degrees Heading angle at position detection moment
position.hdop number Horizontal dilution of precision
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.timestamp number seconds Timestamp when coordinates where calculated
segment.max.acceleration number g Maximum acceleration value that occured on the segment
segment.max.braking.acceleration number g Maximum braking acceleration value that occured on the segment
segment.max.cornering.acceleration number g Maximum cornering acceleration value that occured on the segment
segment.max.engine.load.level number percentage Maximum engine load percentage on segment
segment.max.engine.rpm number rpm Maximum engine RPM on segment
segment.max.position.speed number km/h Maximum speed on segment
segment.max.throttle.pedal.level number percentage Maximum throttle pedal push level on segment
segment.max.vertical.acceleration number g Maximum vertical acceleration value that occured on the segment
send.timestamp number seconds Message send timestamp
sensor.temperature number celsius Temperature sensor value
timestamp number seconds Message timestamp
vehicle.idle.event.status boolean Vehicle idle event status
vehicle.mileage number km Total calculated mileage string VIN of vehicle

Below is the list of commands that can be sent to devices to change their configuration or to send signals to various outputs. When sending a command you can specify the transport type defining how the command will be delivered - the address parameter can take values connection (via network connection once the device goes online), sms (via SMS message), push (via PUSH notification). A comprehensive format of each command with all possible parameter values, parameter types, default values, etc. can be found in the REST API documentation in your account.

Title Name Description Properties
AT Command Send AT Command cmd: Command