The OBU page
Open it from Settings › OBU (ERP 2.0), or from the Drive tab › ⓘ › OBU settings. It's where you connect your OBU and check what's happening.
Status
| Item | What it shows |
|---|---|
| Title | Connected to your OBU, Searching…, Connecting…, Found an OBU, Not connected or Failed |
| Line below | While connecting, the seconds so far ("pairing usually takes 10–20 s"). Otherwise the last message time, the card balance, and how the OBU pays: by card, by backend account, or no payment method turned on |
| Connect / Disconnect | Connect goes straight to the OBU found in the last 10 minutes, or opens Connect an OBU |
| Orange line | The latest error with its time, e.g. "Connection failed: Bluetooth off (1001)". It clears once a later step works |
Kerbside reconnects by itself when the app opens, when it comes back to the front, and after a disconnect. With a plate saved for the OBU it connects by plate; otherwise it looks for the OBU by name.
Found nearby
OBUs found by the last search, kept for 10 minutes so you can connect without searching again. Shown only when you're not connected.
My OBUs
Every OBU you've connected to. Tap one to:
- give it a Name (e.g. Family car) and a Car plate. With a plate, Kerbside reconnects without searching;
- see its OBU number and when it was last connected;
- Forget this OBU: removes it from Kerbside. It stays paired with the iPhone.
Paired with this iPhone
The OBUs LTA's software has paired with this iPhone over Bluetooth. Kerbside connects to these straight away, without searching.
Setup
- Initialise SDK: checks Kerbside's LTA developer key. It runs by itself when Kerbside opens, so it's normally ticked.
- Grant OBU data permission: LTA's screen asks once for permission for Kerbside to read OBU data. It's needed before any connection.
The ⓘ lists what to do before connecting a real OBU: disconnect other OBU apps, register your iPhone's Bluetooth address with LTA, and have internet.
Event log
A list of what the OBU and Kerbside did, with times: launches, connections, charges, trip summaries and errors. The wording is technical. If you write in about a connection problem, a screenshot of the latest lines helps.