RevDash
In the browser
Torque Pro upload
Drive with Torque Pro and have the trips appear in RevDash. This uses the upload setting Torque has had for years. RevDash is not Torque, and uses none of its branding or plugins.
This is not the extended-PID CSV. Importing extra sensors into the RevDash app is Custom PIDs. This page is Torque’s live web-upload URL, so whole drives land in your cloud account.
Mint a URL
-
Sign in at revdash.me/app
Use the same account as the Android app. Open Account.
-
Add an uploader
Under Torque Pro, tap Add an uploader. RevDash shows a URL once and copies it if the browser allows. Only a hash is stored, so closing the dialog without copying means minting another. The URL is a password: anyone with it can upload to your account.
-
Paste it into Torque
In Torque Pro:
- Settings → Data Logging & Upload.
- Set Webserver URL to the address you just copied.
- Tick Upload to webserver.
- Under Select what to log, choose the sensors you want in the trip.
The token has to live in the path. Torque rebuilds whatever URL you give it
from the host and path alone, and silently discards the query string and the port. A
URL that looks like https://api.revdash.me/torque/<token> is the
shape that survives. Putting the secret after ? uploads to a URL with no
credential, which RevDash cannot match to you.
When a drive appears
Torque only starts uploading once it has a GPS fix and an ECU connection. There is no end-of-trip message in the protocol; RevDash closes the drive after six minutes of silence, long enough to clear a fuel stop. The trip then shows up in your list like any other recording, a few minutes after you switch the engine off.
The uploader row in Account says Waiting for its first upload until something arrives, then Last upload …. That is the diagnostic: if it stays waiting, the URL on the phone is wrong, Torque is not ticked on, or it never got GPS and ECU together.
Units
Torque sends what it displays, and says which units those are in a naming row at the start of a session, once, minutes before the car moves. RevDash keeps that row per token. Reading it wrong would make every imperial trip 61% too fast, and nothing downstream could tell. If the naming row never arrived, Torque’s own built-in table is the fallback.
Revoke
Revoke on the uploader. The app using that URL stops being able to upload. Drives already in the account are kept. Mint a new URL if you need to continue.
What this will not do
- It will not import Torque layouts, themes, or plugins into the RevDash app.
- It will not sign Torque into your account. Torque has no account field, only a URL.
-
It will not refuse a sample. Torque treats any body other than exactly
OK!as failure and queues retries into a spill file that grows to 90 MB, so RevDash answersOK!even for a drive it has decided to discard.