• Edited

We enhanced support of 02 - Error report messages for StarLink devices (up to Version 2.32, March, 2019).
Descriptions for all 24 error types available at the moment are stored in error.type.description parameter.

6 days later

02 - Error report: parsing of additional information added for Error number 20: Cellular signal degradation

6 months later
  • Edited

Parameter renaming in erm protocol: vehicle.battery.health parameter is renamed into battery.health.
Both parameters will be registered during one week. 17-Apr-2020 old parameter vehicle.battery.health will be removed.

  • namo replied to this.
    • Edited

    Erm protocol is updated - new dynamic parameters are added:

    • JAM (Jamming detection state) - parameter gsm.jamming.alarm.status
    • LOCA (Location accuracy, meters) - parameter location.accuracy
    • LOCS (Location source) - parameter location.source
    • LOCF (Location filter reason) - parameter location.filter.reason
    • NC (Network code) - parameters gsm.mcc and gsm.mnc
      5 days later

      namo
      Erm protocol updated: old parameter vehicle.battery.health is removed after renaming

        2 months later

        Announcement:
        Command get_location will be deleted from ERM protocol in a week, 25-Jun-2020.
        Please, use custom command instead, see examples here

          10 months later
          • Edited

          Next Monday, 03-May-2021, message parameter "gsm.signal.level" parsed from the #CSS# dynamic tag will be renamed to "gsm.signal.dbm".
          Currently, we're registering the same value for both parameters, and in a week the old name "gsm.signal.level" will be removed.

          • kial replied to this.

            We've added the read-only setting "Dynamic parameters" to all StarLink devices.
            setting

            That setting is used to preserve dynamic parameters format (parameter 177) between device connections, to correctly parse dynamic events.
            If you will change that parameter through the device configurator - please remove that setting in the flespi device Settings to trigger its re-reading.

            If you will not create a device (i.e. you're working on the channel-level only) - the command to read dynamic parameters format (parameter 177) will be sent to the device at the beginning of every connection.

            7 days later

            kial parameter "gsm.signal.level" renamed to "gsm.signal.dbm"

              7 months later

              Extra field for Event number 18 is stored as report.reason parameter

              7 days later

              Next Thursday, 23-Dec-2021, message parameter "location.accuracy" parsed from the #LOCA# dynamic tag will be renamed to "position.accuracy".
              Currently, we're registering the same value for both parameters, and in a week the old name "location.accuracy" will be removed.

                7 days later

                kial Old parameter name removed

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

                    a year later

                    ERM protocol has been changed. gsm. network.type parameter parsed from the #NT# dynamic tag was added.

                      7 months later
                      3 months later

                      parameter renaming announcement which will happen in a week (May 22):
                      parameter total.idle.seconds will be renamed to total.idle.time

                        5 months later

                        Added #FIX# and #CU# parameters parsing (flespi parameters: position.fix.type, transmition.channel)

                          Write a Reply...