[Changelog] topflytech protocol

baja

This topic will be used to post changes in topflytech protocol implementation.

Topflytech

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

baja

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

baja

parameter external.powersource.voltage parsing fixed

baja

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

baja

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

baja

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

baja

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.

namo

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

baja

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

baja

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

namo

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

namo

Topflytech protocol updated, _BLE Message _ parsing improved:
- for BLE Data Code 0x0004 - BLE Temperature, humidity and illuminance sensors: temperature value parsing fixed
- added parsing of Data Code 0x0005 - BLE Door sensor

namo

Topflytech protocol updated: parsing of DTC packet (0x2626 0x09) is fixed.

namo

New Topflytech devices are supported: TLW2-12B and TLP2-SFB

namo

BLE Relay setting is added for Topflytech TLP2-SFB device, Actions tab:

namo

BLE Data Code 0x06 is supported for BLE Message.
Mapping of the packet fields to flespi parameters is the following:

BLE Relay ID - ble.relay.id
Sensor Battery voltage - ble.sensor.battery.voltage
Sensor Battery percentage - ble.sensor.battery.level
Temperature - ble.sensor.temperature
Relay Status - ble.relay.status
RSSI - ble.asset.rssi

If packet 0x270x270x10 BLE Message received from the device contains information about several BLE Relays, flespi will register parameters for subsequent relays with indexes, starting from 1.
For example, in such case message will contain parameters: ble.relay.id="AAAAAAAAAAAA", ble.relay.id.1 = "BBBBBBBBBBBB", ble.relay.id.2 = "CCCCCCCCCCCC" and so on. Same for the other parameters.

The update is applicable for Topflytech TLP2-SFB

namo

Topflytech protocol updated, parameters tyre.pressure and tyre.temperature are renamed to tire.pressure and tire.temperature.

Old parameters will be registered until 05-Jan-2022 together with the new ones. Old parameters will be removed 05-Jan-2022.

namo

New device type added: Topflytech TLP1-SF

namo

Topflytech protocol updated: added parameter message.buffered.status=true, that indicates that this is a historical (block box) message. For real-time messages parameter message.buffered.status is not registered.

namo

Topflytech protocol updated: Data and GNSS Status byte is now parsed as follows:

bit0-bit4: parameter position.satellites
bit5: parameter gnss.status with possible values true (GNSS is in working mode) or false (GNSS is in sleeping mode)
bit6: parameter message.type with possible values gnss or lbs
bit7: parameter message.buffered.status with possible values true (blackbox message) or false (real-time data)

The logic with message.buffered.status parameter that is described in the post namo is no longer applied.

namo

Topflytech protocol updated: removed position.valid=true parameter, that was mistakenly registered together with GNSS data.