Troubleshooting

Couldn’t reach adapter

The phone never got a socket. The car is not in this conversation yet.

• Bluetooth off, or the permission refused.
• Wrong radio: Classic dongle vs BLE scan, or the reverse.
• Still paired to another phone. Cheap clones often hold one connection.
• Out of range, in a pocket under a metal console, further than it looks.
• Wi-Fi: the phone is still on home Wi-Fi. Join the adapter’s access point first, accept Android’s “no internet” warning, then connect in RevDash.

Adapter OK, no ECU

The ELM answered AT commands. The car did not.

• Ignition off. Turn it on; many ECUs sleep hard.
• The port has power and no data, a blown fuse on the diagnostic circuit, or a port that is power-only.
• Protocol hunt failing. Open Diagnostics, note ATDPN, and lock that protocol on the vehicle profile.
• After a battery disconnect some cars need a few minutes awake before they will talk.

Diagnostics lists banner, ATSP, ATDPN, voltage, the failed step and the detail. Voltage around 12 V with ignition on is a live adapter; a blank voltage is often the same failure as “couldn’t reach adapter” wearing a different hat.

Gauges don’t move

• Chip is not Ready. Fix the connection first.
• The tile is a PID this ECU does not support. Remove it; it will sit stale rather than invent a number.
• Poll pace Eco with a very large dash: Fast helps, but the bus is still one PID at a time.
• Imported PID with a bad equation or the wrong header. The editor’s test-bytes box is there for this.

Consumption or CO₂ is blank or absurd

• Fuel type on the profile is wrong, or set to something that does not burn fuel. EVs stay blank on purpose.
• No MAF and no fuel-rate PID. There is nothing to divide.
• Idling in litres/100 km goes to infinity; the gauge holds off at walking pace.

Estimated gear is 0

It is RPM over speed against typical hatch ratios, not a gearbox PID. It drops out when you are stopped, clutching, or in a ratio it does not know. First gear is the usual miss. A DSG that answers Mode 22 current gear is a different tile.

Alarms did not speak

Settings → Alarms. If the phone has no speech engine, the page says so and the banner still fires. A warning that is off, or whose PID is not being polled because you never saved it, will not announce. Crossing announces once, then every 60 seconds while it stays crossed, not continuously.

Import skipped most of the CSV

That is the design: bad rows are listed with line numbers and the rest still install. Common causes are a Mode 01 override (refused), a duplicate id in the file, or an equation that does not compile. Fix the listed lines and import again; existing ids update.

Upload did not happen

• Not signed in. Settings → Cloud.
• Free cap: 20 trips this month. Recording continues; uploads wait until next month or Pro.
• The app process died before the in-process retry. Open Cloud and tap Upload now.
• Trip still recording. Stop it first.

Torque Pro drive never appears

• The URL was shown once. If you closed the dialog without copying, mint another.
• Token in the query string. Torque strips it. The secret has to be a path segment.
• Upload to webserver is not ticked, or nothing is selected under Select what to log.
• No GPS fix, or no ECU, in Torque. It will not send until it has both.
• You have not waited out the six minutes of silence that close the drive after the engine stops.
• The Account row still says Waiting for its first upload, the URL on the phone is not this uploader.

Replay has no map

• The trip has no GPS columns. Record with location granted, or live with charts only.
• The 2D map has no basemap installed on the server. Charts still draw; the page says why. 3D does not use that file.
• 3D stays off until the server has a Maps API key. Switch to 2D, or the operator sets GOOGLE_MAPS_API_KEY.

Share link 404s

Expired, revoked, or mistyped. A wrong token is indistinguishable from a missing one on purpose. Mint a new link from the trip. A link lasts 30 days by default.