Okai protocol is supported in flespi . This topic is a changelog for this protocol. The list of supported devices: Okai ES400 Okai ES600 Okai EB100 Okai ES610 Okai ES400A Okai ES400B Okai ES700

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

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

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.

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

Okai protocol updated: added new settings for Okai ES400 device type, Actions tab: Battery Lock Electronic Bell Reboot Power Off

device types added: Okai ES600 Okai EB100

Okai protocol updated: added new setting for Okai ES400A device type, Configuration tab: Firmware update

New device types is added: Okai ES400B

[Changelog] okai protocol

EvgenyShatilo

New device types is added:

Okai ES400B

baja

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

YuryAheichyk

Okai protocol updated: added GTCTO report parsing for Okai ES400A

YuryAheichyk

Okai protocol updated: added GTVER report parsing

YuryAheichyk

Okai protocol updated: added GTITK report parsing

YuryAheichyk

Okai protocol updated: fixed payload of Network Configuration setting

omol

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

YuryAheichyk

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

YuryAheichyk

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

baja

New device model added: Okai ES700

baja

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

YuryAheichyk

Okai protocol has been updated, fixed Mode switch setting

YuryAheichyk

Added lock control commands for es600

YuryAheichyk

Added Battery Lock setting for es600

baja

GTHBD heartbeat messages are now parsed, extracting parameters:
bluetooth.unlock.password
device.self.name
protocol.version

namo

okai protocol is updated.
Now for the cases when BLE Command Password field (flespi parameter bluetooth.unlock.password) contains non-printable characters it won't cause parsing error followed by disconnect, it will be parsed as escaped HEX string instead.

bird

New device is supported: Okai ES200

bird

+RESP:GTCGT (CAN register status) report is now supported for ES400A devices. New parameters: can.configuration.status.register, can.rx.error.count, can.tx.error.count.

bird

New settings added for EB100: gtxwm_eb (Working Mode), led_eb (LED Configuration), gtecc_eb (ECU Parameters), under "Mode switch", "LED" and "ECU parameters" tabs respectively
Settings gtecc (ECU Parameters) and gtxwm (Working Mode) are now readable from ES-type devices (ES400, ES400A, ES400B) via GTRTO configuration readback
Fixed GTALS parsing crash when device responds with zero configuration items

bird

New parameters for GTULF, GTLOF, GTALM, GTALI, and GTDOG reports:

report.reason — numeric Report Type value
report.reason.description — human-readable description of the Report Type (e.g., "unlocking error or timeout", "main battery type mismatch", "continuous vibration", "periodic restart")
unlock.failure.alarm (GTULF), lock.failure.alarm (GTLOF), vibration.alarm (GTALM), device.reboot (GTDOG) — boolean event indicators