flespi telematics hub supports istartek protocol. The list of supported devices iStartek VT200L iStartek VT200 iStartek VT202 iStartek VT100 iStartek VT100L iStartek VT203 iStartek VT600 iStartek PT60

New device types added: Istartek VT600 Istartek PT60

New device types added: Istartek VT900-G Istartek VT900-L New parsing scheme for alarm code 53 added, 3 options available based on peripherial connected: ibutton.code rfid.code driver license data: citizen.card.type, driver.gender, driver.id, citizen.card.province

istartek protocol has been updated, fixed checksum calculating for devices: iStartek PT60 iStartek VT100 iStartek VT100L iStartek VT200 iStartek VT200L

[Changelog] istartek protocol

baja

flespi telematics hub supports istartek protocol.

Istartek

The list of supported devices

baja

New device types added:

baja

New device types added:

New parsing scheme for alarm code 53 added, 3 options available based on peripherial connected:

ibutton.code
rfid.code
driver license data: citizen.card.type, driver.gender, driver.id, citizen.card.province

namo

New device type is added: iStartek VT203

baja

New device type is added: iStartek VT100

baja

The protocol will be affected by the change in type of parameters gsm.mcc and gsm.mnc to be installed in 2 weeks - May 23rd, 2022: both parameters that now have type "string" will be stored as "number". The possible leading zeroes in MNC will be ignored (e.g. the value "01" will be stored as 1).

YuryAheichyk

istartek protocol has been updated, fixed checksum calculating for devices:

EvgenyShatilo

TLS support is added for the protocol. You can enable it in channel configuration and use this instruction to configure custom certificates for the channel and AT+QSSLCFG instruction to sync this configuration on the device. Or just use provided flespi.gw builtin certificate with minimum configuration.

YuryAheichyk

istartek protocol has been updated, added obd parameters: can.battery.voltage, can.vehicle.mileage, can.fuel.consumed, can.trip.mileage, can.trip.fuel.consumed, can.vehicle.speed, can.trip.max.speed, can.trip.max.rpm, can.engine.ignition.status

baja

parameter can.trip.time renamed to trip.duration
parameter can.trip.max.rpm renamed to trip.max.rpm

YuryAheichyk

Added Set sms password action setting for VT100 series, VT200 series, PT60 devices

bird

Fixed fuel.flow.meter.fuel.consumed parsing for values exceeding 65535 (uint16 overflow)
Fixed OBD encoding for can.intake.air.temperature and can.engine.coolant.temperature — standard OBD-II +40 offset now applied (values decrease by 40°C)
Fixed OBD encoding for can.fuel.consumption — L/h×10 scaling now applied (values decrease by 10×)
Fixed command response parsing for "Unsupport" and "Failed" responses causing disconnections
Improved tolerance for extra trailing fields in position packets

bird

0x0704 Position Data Batch Upload message is now supported for all istartek device types.

EvgenyShatilo

Tachograph live activity parameters standardization

To make tachograph data consistent across all flespi protocols, we introduced unified tachograph driver parameters (per card slot, .1 / .2) for VT200-NXT CAN data:

tacho.driver.card.code - driver card id inserted into the tachograph slot
tacho.driver.activity.state.enum - current activity: 0 - rest, 1 - work, 2 - drive, 3 - available, 4 - not available, 5 - error
tacho.driver.activity.state - the same as text: rest / work / drive / available / not available / error

The following parameter is deprecated and will be removed on 01.11.2026:

tacho.driver.work.state.enum -> tacho.driver.activity.state.enum (attention: enum values differ from the old ones)

Please update your expressions, calculators, plugins and streams before the removal date.

bird

Alarm code 56 (Diagnostic Trouble Code) is now parsed into can.dtc and alarm code 57 into low.speed.alarm for VT200-family devices; messages with unknown alarm codes are no longer rejected.