teltonika

The protocol for Teltonika GPS tracking devices.
Here are some issues with Teltonika trackers that flepsi can fix:

  • Confusing parameters ID mapping. Parameter IDs for different models and firmware versions point to different settings — flespi uses unified protocol description technology to automatically resolve IDs into meaningful names.
  • Tricky firmware updates. Older configurators might not be able to update to the latest firmware release — flespi universal online configuration tool works for multiple manufacturers and adapts to device type and firmware capabilities.
  • Difficulties sending commands via SMS. Changing tracker parameters via text messages requires compliance with command syntax — flespi configurator helps generate SMS content as per the protocol specification.

In order to connect Teltonika to Wialon or other platform via flespi please read this article.

Below is the list of parameters that can appear in the messages received by the channel via teltonika 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
absolute.acceleration number g Module of accelerometer vector
agro.vehicle.state.bitmask number Agricultural machinery flags
ain number volts Voltage on the analog input
alarm.event.trigger boolean Alarm event triggered
battery.current number amperes Battery current
battery.level number percentage Internal battery level
battery.temperature number celsius Internal battery temperature
battery.voltage number volts Internal battery voltage
can.adblue.level number percentage Adblue level reported by CAN
can.adblue.volume number liters Adblue volume reported by CAN
can.axle.weight number kg Weight on the axle reported by CAN
can.engine.load.level number percentage Engine load level reported by CAN
can.engine.motorhours number hours Total engine motorhours reported by CAN
can.engine.rpm number rpm Engine RPM reported by CAN
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
can.fuel.level number percentage Fuel level in tank reported by CAN
can.liquid.sensor.fuel.volume number liters Fuel volume in tank reported by LLS CAN
can.lvc.module.control.bitmask number LVC control state flags
can.module.id number CAN module ID
can.position.speed number km/h Instant speed reported by CAN
can.program.id number CAN program number
can.throttle.pedal.level number percentage Throttle pedal push level reported by CAN
can.vehicle.mileage number km Total vehicle mileage reported by CAN
counter.impulses number Impulses counter
device.configuration.id number Configuration profile index
din number Digital inputs
dout number Digital outputs
engine.ignition.status boolean Engine ignition status
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
geofence.event.enter boolean Entered geofence
geofence.event.exit boolean Exited geofence
gnss.antenna.cut.status boolean GNSS antena is not present
gnss.receiver.sleep.mode.status boolean GNSS receiver is in sleep mode
gnss.status boolean GNSS receiver on/off status
grain.moisture.level number percentage Grain moisture
grain.mowing.efficiency.meters2_h number m^2/h Mowing efficiency
grain.mowing.volume.kg number kg Mown volume
gsm.cellid number GSM base station ID
gsm.lac number GSM location area code
gsm.mnc number GSM mobile network code
gsm.network.roaming.status boolean GSM network in roaming mode
gsm.signal.level number percentage GSM signal strength level
gsm.sim.imsi string IMSI of SIM card
gsm.sim.status boolean SIM card is active
harsh.acceleration.event.trigger boolean Harsh acceleration detected
harsh.braking.event.trigger boolean Harsh braking detected
harsh.cornering.event.trigger boolean Harsh cornering detected
harvest.area number m^2 Area of harvest
harvest.drum.gap number mm Gap under harvesting drum
harvest.drum.rpm number rpm Harvesting drum RPM
harvest.duration number seconds Harvesting time
ibutton.code string Hexadecimal code of connected iButton
ibutton.event.authorize boolean Authorized iButton connected
ibutton.event.connect boolean iButton connected
ident string Device unique identificator and optional password
liquid.sensor.fuel.temperature number celsius Fuel temperature reported by LLS
liquid.sensor.fuel.volume number liters Fuel volume reported by LLS
lvc.security.state.bitmask number LVC security state flags
movement.status boolean Current movement state
overspeeding.event.trigger boolean Overspeeding detected
payload.hex string HEX Payload received from device
payload.text string Text Payload received from device
pcb.temperature number celsius PCB temperature
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.pdop number Position dilution of precision
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
rfid.code string Hexadecimal code of connected RFID
segment.can.fuel.consumed.liters number liters Fuel volume consumed by vehicle on the last segment using CAN data
segment.can.vehicle.mileage number km Vehicle mileage on the last segment using CAN data
segment.vehicle.mileage number km Segment mileage
sensor.temperature number celsius Temperature sensor value
sleep.mode.status boolean Device is in sleep mode
tacho.driver.card.code string Driver identification card id for tacho
tacho.driver.card.status boolean Tacho driver card presence
tacho.driver.continuous_driving.duration number seconds Driver continuous driving time
tacho.driver.cumulative_break.duration number seconds Driver cumulative break time
tacho.driver.cumulative_driving.duration number seconds Driver cumulative driving time
tacho.driver.current.activity.duration number seconds Current driver activity duration
tacho.driver.work.state.enum string Driver work state
tacho.position.speed number km/h Instant speed reported by tacho
tacho.vehicle.mileage number km Total mileage calculated by tacho
timestamp number seconds Message timestamp
trip.event.begin boolean Trip started event
trip.event.end boolean Trip stopped event
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
AVL12 command generic.codec12 Send command encoded in AVL12 codec hex: Payload is encoded as HEX string

crlf: Add CR and LF bytes after text payload

payload: Text or hex data to send
Get configuration param generic.getparam Get configuration parameter by it's number param: Param number
Set configuration param generic.setparam Set configuration parameter by it's number param: Param number

value: Param value