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

    • Edited

    parameter external.powersource.voltage parsing fixed

      6 days later

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

        7 days later

        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

        a month later

        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.

          3 months later
          a month later

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

          5 days later

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

            6 months later

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

              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

                3 months later

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

                  6 months later
                  5 months later
                  a month later

                  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

                  a month later

                  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.

                  a month later

                  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.

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