This topic will be used to post changes in topflytech protocol implementation. The list of supported devices: Topflytech T8608D OBDII Topflytech T8808+ Topflytech TLD1-A Topflytech TLD1-DA Topflytech TLW1-10A Topflytech TLW1-4A Topflytech TLW1-8A Topflytech TLW2-12B Topflytech TLW2-2BL Topflytech TLW2-6BL Topflytech TLW2-12BL Topflytech TLP1-LM Topflytech TLP1-P Topflytech TLP1-SM Topflytech TLP1-SF Topflytech TLP2-SFB Topflytech SolarGuard X100 Topflytech SolarGuard X200 Topflytech HeroX 100 Topflytech KnightX 100 Topflytech KnightX 300 Topflytech PioneerX 100 Topflytech TLD2-L Topflytech TorchX 100 Topflytech WarriorX 100 Topflytech WarriorX 300 Topflytech PioneerX 101

response from server for 0x04 packet type fixed. Alarm type as last byte was missing.

parameter external.powersource.voltage parsing fixed

TLP1 series device types added: Topflytech TLP1-LM Topflytech TLP1-P Topflytech TLP1-SM

Analog inputs as parameters ain.1 and ain.2 parsing added for TLW-series and T8808+ deivce

can.engine.ignition.status parameter renamed to engine.ignition.status We've also added validation position, speed and voltage parameters to exclude parsing errors and invalid coordinates

We've added parsing for BLE message type (TLW and TLD device series) and OBD message type (TLD device series). Fixed a bug with the GNSS/LBS bit parsing.

Topflytech protocol updated: event.enum parameter is added. Parameter's value corresponds to the alarm code, described in TLP1 series devices' User Manual (downloadable on the official Topflytech website ) Applicable for the following devices: Topflytech TLP1-LM Topflytech TLP1-P Topflytech TLP1-SM

We've added message parameter position.valid to messages with valid position latitude, longitude and altitude

Message type 0x06 - Driver Behavior via Acceleration Message parsing added.

Topflytech protocol updated - digital input 1 is registered in bit0 of parameter din .

[Changelog] topflytech protocol

YuryAheichyk

Fixed Detect ACC setting for TLW2-12B devices

YuryAheichyk

Fixed parsing of 0x13, 0x14 reports in case of missing coordinates

baja

parameter collision.status renamed to crash.status

EvgenyShatilo

BLE ELA TAG support has been extended to specification 2.0.
Added Alert data parsing, parameters: alert.level and alert.status.

namo

Topflytech protocol is updated: Message type 0x27 0x27 0x25 Alarm message is supprted

namo

namo
Topflytech protocol is updated: fixed parsing of message type 0x27 0x27 0x25 Alarm message

YuryAheichyk

Added BLE ELA ANG tag parsing

YuryAheichyk

Fixed 0x24 - Position message report parsing

YuryAheichyk

Added Detect ACC setting for TLD2-L devices

YuryAheichyk

Fixed parsing of 4G-LTE LBS parameters

baja

Parameter rename schedule: on November 5th array-type parameter ble.sensros will be renamed to ble.beacons. Inside each object of the array, the field mac will be renamed to id. Currently both ble.sensors and ble.beacons are registered. Switch your usage to ble.beacons, because ble.sensors will be removed.

baja

baja update installed. No more ble.sensors, just ble.beacons

namo

Topflytech protocol is updated: fixed parsing of BLE Driver Identification Data Type field of BLE Message report (0x10)

YuryAheichyk

The OBDII DTC codes registration is planned to be changed. Currently, error codes are stored in the can.dtc parameter as an array of strings. To unify with other diagnostic protocol types, errors will be stored as an array of objects.

The changes will be applied in 2 weeks, on May 8, 2025.

For reference, two additional parameters have been added:

can.dtc.strings - contains errors in the current format (will be removed in 1 month, on May 24, 2025)
can.dtc.objects - contains errors in the new format (will be removed in 2 weeks, on May 8, 2025)

can.dtc.strings example:
["P0020","U0001"]
can.dtc.objects example:
[{"standard":"OBDII","code":"P0020"},{"standard":"OBDII","code":"U001"}]

YuryAheichyk

YuryAheichyk changes applied, can.dtc array contain objects now.

For reference, two additional parameters added:

can.dtc.strings - contains errors in the old format (will be removed on May 24, 2025)
can.dtc.objects - contains errors in the new format (will be removed on May 24, 2025)

can.dtc.strings example:
["P0020","U0001"]
can.dtc.objects example:
[{"standard":"OBDII","code":"P0020"},{"standard":"OBDII","code":"U001"}]

YuryAheichyk

YuryAheichyk changes applied, can.dtc.strings and can.dtc.objects parameters removed

YuryAheichyk

Added 0x18 Alarm message report parsing

YuryAheichyk

Added 0x16 Position message report parsing