• baja

  • Post #7
  • Edited

we've added a logic to correctly parse wrong timestamps caused by GPS Rollover problem
This problem is caused because GPS date is defined by 10-bit week number which results to max 1024 number. So when this number overflows to 0 then tracker (with firmware algorithms not covering this) starts to send time as it is in the beginning of the 1024 week period which is August 21, 1999.

    14 days later

    • namo

    • Post #8

    Concox protocol updated: JV200: timestamp parsing fixed: timezone shift is not applied.

      4 days later
      a month later

      • namo

      • Post #10

      New device supported for concox protocol: Concox JC200

        • namo

        • Post #11
        • Edited

        Concox protocol is updated:

        • Information types 0x7 and 0x8 are supported for Data Transfer Common Packet (protocol number 0x94)
        • Device information settings are added for Concox JC200

        Protocol number 0xAA is supported in concox protocol. Text payload that is contained in 0xAA packet is saved into payload.text parameter.
        Applicable for Concox JC200

          • namo

          • Post #13
          • Edited

          New settings are added for Concox WeTrack2 device:

          • tab Tracking: GPS Data Upload
          • tab Configuration: Delayed Defense, SOS Numbers, Center Number
          • tab Alarm: Overspeeding Alarm, Vibration Alarm
          • tab Actions: Restart Device

          See WeTrack2 User Manual for more details.

            4 days later

            Concox protocol updated: protocol number byte is now stored as protocol.number parameter.

              12 days later

              Concox protocol updated: implemented Transparent transmission protocol (protocol number 0x9B) for receiving the data from external devices connected to RS232.
              Applicable for Concox X3 device.

                13 days later

                • namo

                • Post #19

                Concox protocol updated: parameter oil.electric.connection.status is renamed to engine.blocked.status.
                Both old and new parameters are registered now, old parameter will be removed 31-jan-2020.

                  8 days later

                  namo
                  Concox protocol updated: old parameters removed after renaming.

                      a month later

                      Concox X3 device received two more settings:

                      • Transparent Transmission, Configuration tab:

                      • Restart Device, Actions tab:

                      10 days later

                      namo
                      Concox JC200: several settings were deleted because they didn't worked with JC200 properly:

                      • Actions tab: Upload, Reboot, Reset, Upgrade
                      • Configuration tab: APN, Server Setup

                      Please contact us in support chat if you need these or any other settings to be implemented in flespi telematics hub.

                        Bugfix: engine.blocked.status boolean parameter parsing fixed: reverted to correct values: true when engine is blocked and false if engine is unblocked.

                          2 months later
                          a month later

                          Concox protocol updated: internal implementation changed.