Diagnostics and support logs

For a problem with connecting, background operation or alerts, start with the app's diagnostic log. For an unfamiliar protocol or an incorrect reading, a raw wheel capture is more useful. A screenshot can accompany either, with the time and what you expected to see.

App diagnostic log#

Open Settings → Diagnostics, enable Diagnostic log, reproduce the problem, then choose Share log. Enable it before reconnecting if the problem happens at connection time. Android and iPhone both offer sharing and clearing the log. It records app events such as connection, background work, sensors, alerts, automatic light and automatic volume; it is separate from ride history.

Raw wheel capture on Android#

In the same section, Raw wheel log records incoming bytes and the commands LoEUC sends. It is off by default. Enable it before connecting to capture the handshake too. The app keeps the most recent 200 MB and removes the oldest data when the limit is reached. Share the file after reproducing the issue; it can also be opened in the dump player. Preparing a large file shows progress and can continue after leaving the settings screen.

There is also a service screen: long-press a device in the scanner, or open the debug screen from the dashboard menu. It exposes services and characteristics, raw packets, reassembled frames, markers and capture export. When checking an unknown wheel, include known readings from its own display or official app — voltage and speed, for example — so the bytes can be compared with measurements. Arbitrary-command controls are for protocol work on a stationary wheel.

Wheel faults and specialist screens#

On supported InMotion wheels, the wheel's diagnostics show active faults, warnings and battery status. The report can be shared. Android's P6 diagnostics also expose the raw replies for support; the iPhone fault view is a separate, simpler screen. An empty list means no decoded active faults were reported, not a comprehensive hardware inspection.

Android also has Diagnostic mode for compatible LeaperKim wheels. It shows internal controller data and charts. Enter only while stationary: ordinary dashboard readings and alerts do not work in this mode, and leaving the screen does not restore them. Restart the wheel to leave the mode.

The separate Lynx-S ADC screen on Android is for compatible diagnostic firmware: live counters, timing, raw samples and recovery events, with a report to share. It is not a stock-firmware battery or riding screen.

LeaperKim and NOSFET also have a readout of the wheel's own Event log in the dashboard menu on Android and iPhone. It reads the records stored by the wheel while ordinary telemetry continues; copy the result to send it to support. See wheel support for model and verification limits.