New parameters are supported for Navteletcom protocol: 1-byte, 2-bytes, 4-bytes and 8-bytes user-defined values. Mapping to flespi parameters is the following:

  • flex ids 207 - 222 User-defined 1 byte parameters - sensor.uint8.value.1 - sensor.uint8.value.16
  • flex ids 223 - 237 User-defined 2 bytes parameters - sensor.uint16.value.1 - sensor.uint16.value.15
  • flex ids 238 - 252 User-defined 4 bytes parameters - sensor.uint32.value.1 - sensor.uint32.value.15
  • flex ids 253 - 255 User-defined 8 bytes parameters - sensor.uint64.value.1 - sensor.uint64.value.3
6 months later
6 days later

  • namo

  • Post #17

Navtelecom 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
    2 months later
    a month later

    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).

      11 days later

      Navtelecom protocol updated: the following parameters are renamed:

      • liquid.sensor.fuel.volume.1 - liquid.sensor.fuel.volume.16 are renamed into rs485.lls.value.1 - rs485.lls.value.16 correspondingly
      • liquid.sensor.fuel.temperature.1 - liquid.sensor.fuel.temperature.16_ are renamed into rs485.lls.temperature.1 - rs485.lls.temperature.16 correspondingly
      • rs485.fuel.sensor.frequency.1 - rs485.fuel.sensor.frequency.16 are renamed into rs485.lls.frequency.1 - rs485.lls.frequency.16 correspondingly
      • liquid.sensor.fuel.volume is renamed into rs232.lls.value
      • liquid.sensor.fuel.temperature is renamed into rs232.lls.temperature

      For backward compatibility, both old and new parameters will be registered until 13-Jun-2022.
      13-Jun-2022 we will remove old parameters. Please make sure you code is fully transfered to the new parameters names until the mentioned date.

        24 days later

        namo
        Navtelecom protocol is updated: old parameters are removed after renaming.

            7 months later

            • baja

            • Post #23

            custom command can be sent via SMS using text parameter now.

            custom command will be remastered in 1 week January 4th: You will be able to send it using anyOf rule: binary command payload may be sent inside hex field as hex-formatted string, text command may be sent using text field.

              7 days later

              • baja

              • Post #24

              baja update installed

                  a year 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

                    17 days later
                    2 months later

                    parameter renaming announcement which will happen in a week (May 22):
                    parameter device.model.enum will be renamed to device.model

                      4 months later

                      Fixed Input/Output - Line2 setting response parsing

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

                          14 days later

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

                              Write a Reply...