Topflytech protocol has been updated, added BLE tags parsing:

  • 0x0E BLE iBeacon
  • 0x0F BLE Eddystone UID
  • 0x11 BLE Eddystone TLM
    14 days later
    a month later

    • namo

    • Post #52

    Topflytech protocol updated: event.enum parameter is added, that corresponds to the Alarm Type byte field.

    Applicable for the Topflytech TLD2-L

      6 days later

      The protocol will be affected by the change in parameter can.dtc to be installed in 2 weeks - Mar 15th, 2024: the parameter can.dtc is currently of string type and will be converted to type array with separate DTC codes.

      Added parameter can.dtc.array as an example of future implementation of can.dtc

      9 days later

      Updated parsing of 0x13 Position message and 0x14 Alarm message reports according to the latest documentation

        5 days later
        25 days later

        Fixed Detect ACC setting for TLW2-12B devices

          24 days later

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

            10 days later

            parameter collision.status renamed to crash.status

              a month later

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

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

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

                      Fixed 0x24 - Position message report parsing

                        2 months later

                        Added Detect ACC setting for TLD2-L devices

                          17 days later

                          Fixed parsing of 4G-LTE LBS parameters

                            2 months later

                            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.

                              14 days later

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

                                  a month later

                                  • namo

                                  • Post #68

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

                                    4 months later

                                    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"}]