12 days later

Concox protocol has been updated, added 0x000A Charging voltage and 0x000B Battery temperature status id parsing from JM-LL301, JM-LL302, JM-LL303, JM-LL701, JM-LL702 devices

    Concox protocol has been changed, added Speed parameter parsing for Report of alarm and driving behavior data 0x03 report from JM-VL502

    25 days later

    Concox protocol has been updated, added battery.level parameter for JM-LL01, JM-LL02 devices

      7 days later

      Update parsing #gsm.signal.dbm parameter for the type 0x70. Previously, the calculation was performed incorrectly without taking into account the sign of the value. This parameter shows the cellular signal strength in dbm. Such values must be presented in negative form. The change has been agreed upon with the hardware manufacturer.
      Example: previous value 50, now it will be -50 dbm.

        22 days later

        Fixed date and time parsing of 0xA0 - GPS Location Packet (UTC, 4G Base Station Data) report from JM-VL512

          4 days later

          • namo

          • Post #108

          Concox protocol updated: fixed Working Mode settings, Traking tab for Jimi IoT AT1

            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

            • New device type model is added: Qbit-M
            • The algorithm for calculating the value of the #gsm.signal.dbm parameter has been changed, which shows the value in dbm of the cellular signal level. Previously it was calculated incorrectly. The value must be negative. The current value is now multiplied by -1. It was 65, now -65. The change applies to packets 0xA1, 0xA2.
            • Fixed server response for package 0xA5. was previously incorrect.

            All changes were applied in accordance with the manufacturer's recommendations.

              14 days later

              YuryAheichyk changes have been applied, the can.dtc parameter type changed to array

                  • namo

                  • Post #112

                  Concox protocol updated:

                  • fixed parsing of response of Vibration Alarm setting for Jimi IoT WeTrack2
                  • disabled sending server ack for terminal's reply to server command (packet number 0x15), as server ack is not needed according to the protocol documentation
                    2 months later

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

                      a month later

                      Concox protocol updated: parameter vehicle.type.enum is renamed to vehicle.type.
                      Please, use new parameter name in your integrations.
                      For backward compatibility, both new and old parameters will be registered until 2024-Jun-27.

                      The updated is applicable for the following Jimi IoT (Concox) device types: VG502, JC181, JC450, JM-VL502

                        12 days later

                        Concox protocol updated: fixed parsing of parameter gnss.realtime.status for protocol number 0x10.

                          Concox protocol updated: fixed parsing of command response for JM-VL103

                            Added Wakeup query action setting for JC181 devices

                              3 months later

                              Changes have been made to the concox protocol, for JC181 and JC450 devices. Now the Time zone setting fields will not be updated when receiving a timezone value in a telematic message and if this value has not changed

                                Added settings for BL11 device