14 days later

Timestamp parsing logic change. Several models when connected initially store invalid timestamp in the packet (invalid means that 0th month and 0th day). These packets caused parsing error resulting in new attempts from device to deliver it. Such timestamps now don't stored at all (filtered out), which results in the message being stored with the timestamp = server.timestamp

    5 days later
    5 days later

    Okai protocol updated: added GTVER report parsing

      15 days later

      Okai protocol updated: added GTITK report parsing

        a month later

        Okai protocol updated: fixed payload of Network Configuration setting

          11 days later

          • omol

          • Post #17

          Okai protocol has been updated: added LED setting for ES devices family.

          14 days later

          Okai protocol has been updated, added GTNFC, GTOTK reports parsing

            2 months later

            Okai protocol has been updated, fixed ECU Info item parsing from EB100 devices and added GTALC report parsing

              a month later
              20 days later

              Parsing for ES400A and ES400B updated: ECU parameters max.battery.temperature, min.battery.temperature and peak.battery.current added

                23 days later

                Okai protocol has been updated, fixed Mode switch setting

                  5 months later

                  Added lock control commands for es600

                    11 days later

                    Added Battery Lock setting for es600

                      Write a Reply...