Hardware
What to plug in: a K-Line cable, key ON, 10400 8N1, and which phone can open it.
Choosing a cable
You need a USB K-Line (KKL) cable built on an FTDI, CP210x or CH340 chip. It must speak 10400 baud 8N1 and be able to hold the line LOW for the wake (a serial-break, or an FTDI bit-bang). A plain USB-UART with no K-Line transceiver will not work: the bus is one wire, half-duplex, and the cable echoes every byte you send. The session strips that echo.
Prefer an FTDI cable when you can. A bit-bang of TXD LOW for 70 ms is the wake the bench uses; a Shindengen box that was just switched to key ON answers that on the first try. OS break (what the desktop adapters do) is 70 ms and is enough for Keihin. The Android adapter cannot bit-bang, so its wake is shorter (see below).
The bike supplies the ECU. USB power on the computer side does not.
Connector
The Honda diagnostic connector carries three signals the cable needs. Match the cable's leads to those signals. This page does not publish a pin diagram.
| Signal | Role |
|---|---|
| K-Line | the single ISO 9141 data wire |
| GND | bike ground, common with the cable ground |
| +12 V | bike battery. Present with the key ON. Powers the ECU. |
Key ON, engine off, is the normal workshop state. Key OFF means the ECU is unpowered and connect ends in ECU_SILENT.
Serial settings
| Setting | Value |
|---|---|
| Baud | 10400 |
| Data bits | 8 |
| Parity | none |
| Stop bits | 1 |
| Flow control | none |
The shipped adapters set this. If you open the port yourself and pass it to fromSerialPort, the baud must be 10400 and the frame 8N1, or you get BAD_PORT. fromDuplex does not check: set the port before you wrap it. Idle level on the bus is high.
Drivers
| OS | What you install |
|---|---|
| Windows | The chip's Virtual COM Port driver. FTDI cables use FTDI VCP. The port shows up as COM3 (the number varies). |
| macOS | Nothing for a genuine FTDI FT232: the system driver does 10400. Open /dev/cu.usbserial-…, not the tty node. |
| Linux | The kernel driver (ftdi_sio for FTDI) creates /dev/ttyUSB0. The user needs permission on that node (group dialout on most distros). |
CP210x and CH340 cables need that vendor's driver on the desktop. Unplug other serial devices while you find the path. SerialPort.list() (Node) and SerialPort.availablePorts (Flutter desktop) print it.
Android (USB-OTG)
The phone must be the USB host. Use an OTG adapter. A charge-only cable enumerates nothing.
smongrot_sdk_usb_serial speaks FTDI, CP210x, CH34x and CDC. UsbSerial.listDevices() then device.create() asks for permission; call create() from a running screen (a button), not during process start.
The chip has no break control. The adapter wakes by dropping to a low baud and sending one 0x00, which holds the line LOW for about 45 ms, then returns to 10400. Most Keihin boxes answer it. A Shindengen box fresh off key ON may ignore it; connect still tries 4 times. If you have a native FTDI bit-bang, pass it as atomicWake and the adapter uses that instead.
Why iOS cannot use a cable
iOS does not give an app a USB-serial port, so no K-Line cable can be opened. v0.2 reaches the bike through the SMR board over Bluetooth LE, which works on iOS. There is no iOS cable adapter in v0.1.
Next: Safety