Using ZK Tool to Debug OKAI Fleet Scooter / Bike IoT
Use this guide when an OKAI scooter or e-bike does not reconnect after server configuration, or when Levy support asks for modem logs.
Tools Needed
- Windows PC.
- ZK Tool / ZK Series Manage Tool.
- OKAI IoT USB debugging cable.
- Physical access to the IoT module.
- Vehicle number, IMEI, and SIM ICCID.
Connect to the Device
- Make sure the vehicle is powered.
- Connect the IoT module to the Windows PC with the USB debugging cable.
- Open ZK Tool.
- Select the correct COM port.
- Enter the device password.
Common defaults appear below, but the vehicle page's IoT Credentials value should be treated as the source of truth.
OKAI debug fallback passwords — partner content
Sign in with your active Levy Fleets account to view.
- Click Try to Connect and wait for a success message.
- Press Ctrl + L to open RawComView.
Reboot the IoT Device
Send the reboot command from RawComView:
OKAI device-restart AT command — partner content
Sign in with your active Levy Fleets account to view.
After sending:
- Watch RawComView for reboot messages.
- Listen for the restart sound if audio is enabled.
- Wait 2 to 10 minutes for cellular reconnect.
- Check the vehicle in Levy Fleets.
Retrieve Modem Logs
If the device does not reconnect, collect modem logs.
- Stay connected in RawComView.
- Start UART modem logging with the ZK Tool
AT+UARTLOGcommand path. - Wait 5 to 10 minutes so the modem has time to attempt registration and server connection.
- Save the log text file from ZK Tool.
- Stop UART modem logging before disconnecting.
- Send the log file to Levy support with the vehicle number, IMEI, SIM ICCID, location, and test time.
Logs can contain operational identifiers
Treat modem logs as partner/internal support artifacts. Do not paste full modem logs into public tickets or public documentation.
Troubleshooting ZK Tool Connection
| Symptom | What to check |
|---|---|
| Password error | Confirm the device's per-vehicle IoT password in Levy Fleets. |
| Device wake-up failure | Confirm the IoT cable is fully seated and the vehicle has power. |
| No COM port appears | Install or reinstall the Prolific PL2303 USB serial driver. |
| ZK Tool crashes | Close other serial tools, reconnect the cable, and reopen ZK Tool. |
| Connected to previous device | Re-select the COM port through the COM wizard after switching devices. |
After Debugging
Return the IoT to normal mode before putting the vehicle back into service. If the IoT remains in TEST mode, the vehicle may not behave correctly in a live rental deployment.