First boot and the orange key#

Power the board from the car’s USB port. A new board starts on CarMind R.E.V and opens on Home.

What Home shows#

Home screen in the light theme: Economy card with WAITING, No car yet and Search, analogue clock, System card and the All apps button

Home, light theme, before a car is connected. Host render of the 2.0.0 screen code with example values.

  • Status bar: the time, Bluetooth, Wi-Fi and the battery voltage (4.20 V here). Inside an app it also shows CPU, AI, MIPS (millions of instructions per second) and the power source.

  • Economy: your fuel economy while you drive. Before a car connects it says “No car yet” and offers Search.

  • Clock: an analogue clock. It shows the right time once you set the clock (see Settings).

  • System: how busy each of the two cores is, in % and MIPS, and the power source. “USB current is not measured” is expected.

  • All apps: opens the app pages.

The orange key is Home#

Press the orange Function key once to go to Home from any app. If the screen is off, the same press wakes it first. If a critical-fault banner is showing, the press clears the banner.

A press counts when you let go within 1 second. A longer hold does nothing.

Before the first drive#

  1. Check that Settings > FIRMWARE AND BOARD shows OpenCarMind EdgeOS 2.1.0.

  2. Wait about a minute after the start. The top right of the Board page then says “Parked, health good” in green. See Health checks and messages if it says something else.

  3. Check that Settings > MODEL shows R.E.V.

  4. Set the clock. Join Wi-Fi, or use Settings > Set clock. The clock line then says “From Wi-Fi” or “Set by hand”.

  5. Open Files and check that the storage bar shows the 128 MB NAND.

  6. Plug the adapter into the OBD-II port and switch the ignition on. The first time, the board asks before it pairs (see below). Tap Use this adapter.

  7. Within about a minute the Drive app shows speed and rpm. If it does not, open Settings > OBD ADAPTER and tap Find OBD adapter.

Pairing your OBD adapter#

The board pairs with one adapter, and after that it connects to it by itself. It never saves an adapter without asking you.

  1. Plug the adapter in, switch the ignition on and keep the board in the car, near the adapter.

  2. The board offers only an adapter with a strong signal, -70 dBm or better. An adapter in a car parked next to yours is usually weaker, so it is not offered.

  3. When an adapter answers, a sheet asks “OBD adapter found: <name>, signal strong. Use this adapter?” A weaker one says “signal good”. Under it you see “Nothing is saved unless you choose.” and the seconds left.

  4. Tap Use this adapter. The events say “OBD adapter paired: <name>”.

  • Not this one: the board skips that adapter until its next start

  • No answer in 30 s: nothing is saved, and the events say “OBD adapter not paired”. The board does not offer that adapter again until you tap Find OBD adapter or restart.

  • Switching to another adapter: open Settings > OBD ADAPTER and tap Find OBD adapter. For the next 90 s the board offers a new adapter with a strong signal, even though one is paired. The automatic search never replaces your paired adapter.

  • At the edge of range: once paired, your adapter also connects at a weaker signal, down to -90 dBm

This pairing sheet is new in 2.0.0. It is built and checked on a computer, not yet tested on the board.

When the adapter looks different, or asks to pair again#

After pairing, the board remembers a fingerprint of your adapter: its name, what it advertises, its serial line and its answers to two identity questions. It keeps no VIN and shows no address. Two more questions can then appear, in the same sheet as the pairing question, with 30 s to answer.

  • “This adapter looks different. Use it?” The adapter at your adapter’s address does not match the fingerprint. Under the question you see “Its data is kept apart until you choose.” The drive is still logged but marked, and the learning gets none of it.

    • Use it: the board learns this adapter as yours. Tap it after a firmware update of the adapter, for example.

    • Not this one: the link is dropped, and the board leaves that address alone for 10 minutes.

    • No answer: the data stays apart until the link ends. The next link is checked again.

    • While driving the link is never cut and the question waits until you park.

  • “The adapter asks to pair again. Allow?” Your adapter refused the saved key and wants a new one. That is normal after an adapter reset, and suspicious otherwise. No data flows while the question is open.

    • Allow: the new key is kept and the board goes on.

    • Don’t allow, or no answer: the old key stays, the link is dropped, and the board waits 10 minutes.

    • While driving the board refuses at once, keeps the link and marks the rows. The events say “Re-pair refused (driving)”.

These two questions are built and checked on a computer, not yet tested on the board.