intermediate
OKAI
IoT
server configuration

OKAI Server Configuration

Complete guide to configuring OKAI rental vehicles (scooters and bikes) to connect to the Levy Fleets server. Learn how to update IP and port settings using Modify Mode and ZK Tool software.

Levy Fleets TeamFebruary 5, 20268 min read

OKAI Server Configuration

This guide provides step-by-step instructions for configuring OKAI scooters and e-bikes to connect to the Levy Fleets server. Whether you're switching from OKAI's default server or setting up new devices, this guide covers everything you need.

Levy Fleets Server Settings

All OKAI devices must be configured with these settings:

Using incorrect settings will prevent your vehicles from connecting to Levy Fleets.

TL;DR — The 3 Commands

If you've done this before, this is the entire process. Open ZK Tool, press Ctrl + L, and send these three commands in order:

OKAI reporting-interval AT command — partner content

Sign in with your active Levy Fleets account to view.

Sets the reporting interval.

OKAI server-switch AT command — partner content

Sign in with your active Levy Fleets account to view.

Points the device at the Levy Fleets server.

OKAI device-restart AT command — partner content

Sign in with your active Levy Fleets account to view.

Reboots the device so the new server config takes effect. Skipping this means nothing applies — the device keeps talking to OKAI.

The full step-by-step (mode switching, cable connection, verification) is below.

Common Mistakes — Read Before You Start

These are the three things operators consistently get wrong:

  1. Don't touch the "Quick Start Settings" form (Main Server IP, Main Server Port, APN fields in the main ZK Tool window). The server config is set through the Ctrl + L command pane, NOT the form. If you fill in or "Send to Device" the form, you'll overwrite the AT command settings.
  2. Don't change APN settings. The APN is pre-configured on the SIM. Changing it breaks cellular connectivity.
  3. Don't skip the restart command. The restart AT command (•••••sign in) is what actually applies the new server config. Without it, the device keeps connecting to OKAI's server even though the commands appeared to succeed.

Required Software Downloads

Download these tools before starting configuration:

FileDescription
ZK Tool (ZK105LSC Manage Tool V1.2.4)Main configuration software for reading/writing IoT settings
Modify Mode.exeSwitches IoT device between TEST and NORMAL modes
Encryp_Data.okaiEncryption data file required by Modify Mode
Prolific PL2303 USB Driver (v1.12.0)USB-to-serial driver required for Windows 11

Windows Only

Both ZK Tool and Modify Mode are Windows-only applications. The Encryp_Data.okai file must be in the same directory as Modify Mode.exe to function.

Windows 11: Prolific Driver Required

This USB driver is only for computers running Windows 11, as it won't automatically recognize the COM serial port. You must install the Prolific PL2303 USB driver before connecting the OKAI USB debugging cable.

Video: How to Use Modify Mode

Prerequisites

Before you begin, ensure you have:

  • A Windows PC (the configuration software is Windows-only)
  • The software tools above downloaded and extracted
  • IoT USB debugging cable (OKAI ZK1 series cable)
  • Access to the vehicle's IoT module

ZK1 Series Debugging Cable

Part 1: Update Server IP and Port

This is the most critical step. You'll connect to the IoT device and update its server configuration to point to Levy Fleets.

Step 1: Prepare the IoT Device

  1. Power on the vehicle and ensure the IoT device is active
  2. Press and hold the IoT device button for approximately 10 seconds to activate it
  3. The device must be in TEST mode for debugging software access

LED Status Indicators

LED 1LED 2Mode
OFFOFFINACTIVE mode
Alternating FlashingAlternating FlashingTEST mode (required for configuration)
ON (Breathing)OFFNormal operating mode
OFFFlashingECU fault detected
OFFONIoT fault detected

Step 2: Connect to the IoT Device

  1. Extract the IoT module from the vehicle housing (if necessary)
  2. Connect the USB debugging cable to the IoT device
  3. Connect the USB end to your PC
  4. Ensure no other applications are using the USB/serial port

IoT Connection Step 1

IoT Connection Step 2

Step 3: Switch to Test Mode (Modify Mode)

If your device isn't already in test mode, use the Modify Mode software:

  1. Close ZK Tool if it's running (to prevent USB port conflicts)
  2. Launch Modify Mode software
  3. Select the correct USB serial port from the dropdown
  4. Click Open Port
  5. Enter the device's IMEI number
  6. Click Confirm - the software will automatically switch the IoT to test mode
  7. Close Modify Mode when complete

Video Instructions

See the Modify Mode video tutorial at the top of this page for a walkthrough of this process.

Step 4: Configure Server Settings with ZK Tool

Now you'll update the server IP and port using ZK Tool:

  1. Launch ZK Tool software
  2. Log in with the password: •••••sign in

This is the ZK Tool desktop password — not your device's AT command password

•••••sign in only unlocks the ZK Tool software itself. The •••••sign in in the AT commands further down (•••••sign in, •••••sign in, •••••sign in) is a separate, per-device IoT password. Never use •••••sign in inside an AT command — the device will silently reject it.

ZK Tool Connected

  1. Press Ctrl + L to open the command entry page

Server Connection Settings

Screenshots Show Example Values Only

The IP, port, and APN values shown in the screenshots on this page are illustrative examples only — they are not the values you should enter. Always use the Levy Fleets values called out in this guide:

Do not copy the values from any screenshot.

  1. Send the following commands to configure the server:

How to Tell a Command Worked

After sending each command, look at the Operation Log pane in ZK Tool. A successful command echoes back the command itself followed by an OK line. If you don't see OK, the command didn't take — recheck the IMEI, mode (must be TEST), and cable.

The AT password in these commands is per-device

•••••sign in is the OKAI factory default for most ES400-family IoT modules, but some devices ship with a different per-device password (for example •••••sign in). If a command echoes back without OK, look up the device's actual AT password under IoT Credentials on its vehicle page in the Levy Fleets dashboard (visible to super-admins), and substitute that for the default in every command on this page.

Fixed-Time Reporting Configuration

OKAI reporting-interval AT command — partner content

Sign in with your active Levy Fleets account to view.

This sets the device to report its position every 60 seconds during active operation.

Expected Operation Log output:

OKAI reporting-interval expected output — partner content

Sign in with your active Levy Fleets account to view.

IP and Port Switch Command

OKAI server-switch AT command — partner content

Sign in with your active Levy Fleets account to view.

This is the critical command that points the device to the Levy Fleets server.

Expected Operation Log output:

OKAI server-switch expected output — partner content

Sign in with your active Levy Fleets account to view.

The log should echo back the IP and port — if it doesn't, your command got truncated and you need to resend it.

Verify the IP and Port

Double-check that you entered:

Incorrect values will prevent the device from connecting.

Do Not Change APN Settings

Do not modify APN settings for this setup. The APN is pre-configured on the SIM card and changing it will break cellular connectivity. Leave APN values untouched — only the server IP and port need to be updated.

APN Configuration

Step 5: Restart the Device — Required

Do Not Skip This Step

The previous commands only stage the new server config. The restart command (•••••sign in) is what makes it take effect. Without the restart, your device will keep talking to OKAI's server even though every command above returned OK. This is the #1 reason operators think the configuration "didn't work."

Send the restart command via Ctrl + L:

OKAI device-restart AT command — partner content

Sign in with your active Levy Fleets account to view.

Note: unlike the other AT commands, this one has no FFFF$ suffix.

Configuration Send Confirmation

The device will reboot and attempt to connect to the Levy Fleets server. You'll know it succeeded when the device appears online in your Levy Fleets dashboard within 30–90 seconds (see Part 2 below).

Part 2: Verify Connection

After restarting, the device should connect to Levy Fleets:

  1. Wait 30-90 seconds for the device to reconnect (time varies based on cellular signal strength)
  2. Log in to your Levy Fleets Dashboard
  3. Navigate to Vehicles or IoT Devices
  4. Verify the device appears online with updated telemetry

Troubleshooting Connection Issues

IssueSolution
Device not appearing onlineWait up to 5 minutes, check cellular signal
Device shows offlineVerify IP and port settings, check battery level
Commands not respondingEnsure device is in TEST mode, check USB connection
AT command echoes without OKThe default •••••sign in in the example may be wrong for this device. Look up the per-device AT password under IoT Credentials on the vehicle page in the Levy Fleets dashboard and resend with that value.

Part 3: Return to Normal Mode

Once configured and verified, switch the IoT back to normal operating mode:

  1. Connect via ZK Tool with password •••••sign in (this is the ZK Tool desktop login — not your device's AT command password)
  2. Press Ctrl + L
  3. Send the mode switch command:

OKAI normal-mode AT command — partner content

Sign in with your active Levy Fleets account to view.

If •••••sign in echoes back without OK, substitute the device's per-device AT password (visible under IoT Credentials on the vehicle page) and resend.

The device will switch from TEST mode to NORMAL mode for regular operation.

Quick Reference: All Commands

PurposeCommand
Switch to Levy Server•••••sign in
Set Reporting Interval•••••sign in
Restart Device•••••sign in
Switch to Normal Mode•••••sign in

Port Reference

Device TypeServer IPPort
Omni (Generic)•••••sign in•••••sign in
Segway•••••sign in•••••sign in
OKAI•••••sign in•••••sign in
Queclink (ZK600)•••••sign in•••••sign in
ZIMO MQTT•••••sign in•••••sign in

Common Issues

Device Was Never Connected to OKAI Server

If the device never communicated with OKAI's original server, it requires physical access to configure:

  1. Charge the vehicle fully
  2. Verify the SIM card is activated and has data
  3. Check the IoT module is properly connected to the ECU
  4. Follow the configuration steps above

Device Has 0% Battery

Devices with completely depleted batteries cannot receive configuration commands remotely:

  1. Charge the vehicle until the IoT module powers on
  2. Once online, follow the configuration steps above
  3. For bulk deployments, OKAI may be able to queue the IP switch command to execute when the device comes online

Multiple Devices to Configure

For fleets with many vehicles, contact Levy Fleets support at support@levyelectric.com to discuss:

  • Bulk configuration options
  • Remote configuration assistance from OKAI
  • Pre-configured device procurement

Need Help?

Contact support@levyelectric.com with:

  • Device IMEI
  • Current device status (LED indicators)
  • Any error messages

For OKAI-specific hardware issues, contact OKAI technical support directly.