• Edited

Motion data report GTMDR is supported for okai protocol. The following flespi parameters are registered:

  • Device Name - device.self.name
  • VIN - vehicle.vin
  • QR Code - qr.code
  • Total Sample Number - motion.data.count
  • Longitude - position.longitude.1 - position.longitude.99
  • Latitude - position.latitude.1 - position.latitude.99
  • Scooter Speed - position.speed.1 - position.speed.99
  • Left Brake Value - left.brake.1 - left.brake.99
  • Right Brake Value - right.brake.1 - right.brake.99
  • Speed Handle Value - speed.handle.1 - speed.handle.99
  • Generated Time - timestamp

The following reports are supported for okai protocol:

  • GTCFU ECU error code update report. Mapping to flespi parameters:

    • Device Name - device.self.name
    • VIN - vehicle.vin
    • QR Code - qr.code
    • ECU Error Code - ecu.error.code
    • GPS Accuracy - position.hdop
    • Speed - position.speed
    • Azimuth - position.direction
    • Altitude - position.altitude
    • Longitude - position.longitude
    • Latitude - position.latitude
    • GPS UTC Timestamp - position.timestamp
    • MCC - gsm.mcc
    • MNC - gsm.mnc
    • LAC - gsm.lac
    • Cell ID - gsm.cellid
    • CSQ - network.signal.rssi & gsm.signal.quality
    • Network Type - gsm.network.type
    • Motion State - movement.status
    • Power Supply (main power vs backup battery) - backup.battery.status
    • Main Power Voltage - battery.voltage, volts
    • Backup Battery Voltage - backup.battery.voltage, volts
    • Backup Battery Percentage - backup.battery.level
    • ECU Error Type - ecu.error.type
    • Alive - alive.status
    • ECU Lock State - ecu.lock.status
    • ECU Info - various ecu.* parameters
    • Scooter Battery Percentage - battery.level
  • GTADR Acceleraion data report. Mapping to flespi parameters:

    • Device Name - device.self.name
    • VIN - vehicle.vin
    • QR Code - qr.code
    • Total Frames - frames.count
    • Data - acceleration.array
2 months later

Fixed Report setting is added for Okai ES400, Tracking tab.
The setting allows to configure GRFRI report sending parameters.

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

    BugFix: The protocol now acknowledges the device correctly.

    Feature: For AT+ Commands you can choose whether will command need to wait for ACK packet to be sent or not with "WAIT ACK" switch.

      2 months later
      • Edited

      The following reports are supported for okai protocol:

      • GTCFL - ECU firmware lost report. Mapping to flespi parameters:

        • Device Name - device.self.name
        • VIN - vehicle.vin
        • QR Code - qr.code
        • Report Type: Hardware version of ECU - ecu.hardware.version
        • ECU Error Code - ecu.error.code
        • GPS Accuracy - position.hdop
        • Speed - position.speed
        • Azimuth - position.direction
        • Altitude - position.altitude
        • Longitude - position.longitude
        • Latitude - position.latitude
        • GPS UTC Timestamp - position.timestamp
        • MCC - gsm.mcc
        • MNC - gsm.mnc
        • LAC - gsm.lac
        • Cell ID - gsm.cellid
        • CSQ - network.signal.rssi & gsm.signal.quality
        • Network Type - gsm.network.type
        • Motion State - movement.status
        • Power Supply (main power vs backup battery) - backup.battery.status
        • Main Power Voltage - battery.voltage, volts
        • Backup Battery Voltage - backup.battery.voltage, volts
        • Backup Battery Percentage - backup.battery.level
        • ECU Error Type - ecu.error.type
        • Alive - alive.status
        • ECU Lock State - ecu.lock.status
        • Task Id - task.code
        • ECU Info - various ecu.* parameters
        • Scooter Battery Percentage - battery.level
      • GTCID - report for ICCID real time operation. Mapping to flespi parameters:

        • Device Name - device.self.name
        • VIN - vehicle.vin
        • QR Code - qr.code
        • Task Id - task.code
        • ICCID - gsm.sim.iccid
      3 months later

      Okai protocol updated: added new settings for Okai ES400 device type, Actions tab:

      • Battery Lock
      • Electronic Bell
      • Reboot
      • Power Off

      4 months later
      3 months later
      22 days later
      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

              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