Maxtrack protocol, devices, parameters. Maxtrack protocol parser.

Below is the list of parameters that can appear in the messages received by the channel via maxtrack 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
alarm.event	boolean		Alarm event triggered
antitheft.event	boolean		Antitheft event triggered
battery.charging.status	boolean		Battery charging status
battery.status	string		Battery status
channel.id	number		ID of channel that received message
device.id	number		ID of device that received message
device.model	string		Device model ID string
device.name	number		Name of device that reveiced message
device.temperature	number	celsius	Temperature of device
device.type.id	number		ID of device type of device that recevied message
driver.id	string		Driver identification card id
engine.ignition.status	boolean		Engine ignition status
engine.motorhours	number	hours	Total calculated engine motorhours
event.enum	number		Event code, full list of codes available at separate table
event.seqnum	number		Unique event sequence number
external.powersource.voltage	number	volts	External power voltage
gnss.antenna.status	boolean		GNSS receiver antenna status
gnss.vehicle.mileage	number	km	Vehicle mileage calculated by global navigation system (GNSS)
gsm.cellid	number		GSM base station ID
gsm.jamming.event	boolean		GSM signal jamming detected
gsm.lac	number		GSM location area code
gsm.mcc	string		GSM mobile country code
gsm.mnc	string		GSM mobile network code
gsm.network.status	boolean		Registration in GSM network
ident	string		Device unique identificator and optional password
message.buffered.status	boolean		Black box message
movement.status	boolean		Current movement state
overspeeding.event	boolean		Overspeeding detected
peer	string		IP:port from which device connecting to the channel
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.speed	number	km/h	Instant speed at position detection moment
power.on.status	boolean		Power-on device status
protocol.id	number		ID of protocol
server.timestamp	number	seconds	Timestamp when server received message
sleep.mode.status	boolean		Device is in sleep mode
timestamp	number	seconds	Message timestamp
total.idle.seconds	number	seconds	Total time that vehicle was in idling state

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 flespi.io account.

Title	Name	Description	Properties
Custom command Examples	custom	Send custom command to device, message type 0x33	payload: Parameter value. Variable length. Depends on parameter_id parameter_id: HEX representation of number that defines which parameter to change
Activate output 2 (see SPC_OUTPUT_MACRO3 command) `{"payload":"02FFFFFFFFFFFF","parameter_id":"57"}` Activate output 1 for 5 seconds in 2 cycles (see SPC_OUTPUT_MACRO3 command) `{"payload":"010005FFFF0002","parameter_id":"57"}`