meitrack

This protocol is used by all Meitrack GPS tracking devices

Below is the list of parameters that can appear in the messages received by the channel via meitrack 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
battery.voltage number volts Internal battery voltage
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.type.id number ID of device type of device that received a message
din number Digital inputs bitmask
dout number Digital outputs bitmask
engine.motorhours number hours Total calculated engine motorhours
event.enum number Event code, full list of codes available at separate table
external.powersource.voltage number volts External power voltage
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
gsm.signal.dbm number dbm Strength of GSM signal
ident string Device unique identificator and optional password
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.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.valid boolean Is position information accurate and valid for given timestamp
protocol.id number ID of protocol
rfid.code string Hexadecimal code of connected RFID
server.timestamp number seconds Timestamp when server received a message
timestamp number seconds Message timestamp
vehicle.mileage number km Total calculated mileage

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 GPRS command custom_gprs Send custom command to device via GPRS connection parameters: Comma-separated parameters (optional)

command_type: 3 symbols command code
Real-Time Location Query via GPRS connection
{"command_type":"A10"}
Setting a Heartbeat Packet Reporting Interval to 10 minutes via GPRS connection
{"parameters":"10","command_type":"A11"}
Custom SMS command custom_sms Send custom command to device via SMS password: 4 digit device password. Default is 0000

parameters: Comma-separated parameters (optional)

command_type: 3 symbols command code
Setting the Scheduled Tracking to 10 seconds via SMS with PIN=1234
{"password":"1234","parameters":"10","command_type":"A12"}