Hello,
I’ve tried setting boost on a gauge using all boost and map availabilities on the app but nothing works can anyone help me as Torque pro it works
I’m using a OBD 2 I Car Pro S2 Vgate I believe
Audi TT MK2 tfsi 2.0 2007
Is anyone able to assist please and thanks
Hi Alex — since Torque Pro shows boost, let’s check which data RealDash is receiving. Torque can estimate boost from airflow on VW/Audi cars, so its working boost gauge doesn’t necessarily mean the standard manifold pressure reading is available.
RealDash also has an airflow-based calculation when manifold pressure isn’t received, but it needs live MAF and RPM readings and the correct engine settings.
Keep a calculated boost gauge on your dashboard and, with the car stationary and the engine running, open Settings → Application → Debug → Debug Data View → ENGINE. Could you share whether RPM, Manifold Absolute Pressure and MAF g/s appear and update, along with your RealDash version? A screenshot is fine; please mention any missing readings.
If RPM and MAF work but manifold pressure is unavailable, check ENGINE SIZE and VOLUMETRIC EFFICIENCY in Garage’s engine settings. The engine size field uses cc or cid, as shown on screen, not litres like Torque’s profile. Don’t adjust volumetric efficiency just to force the two apps to match.
Also check whether boost updates in the CALCULATED tab. If it updates there but not on the dashboard, we can focus on the gauge’s input, range or Gauge Math rather than the OBD connection.
Hello,
Thank you for the reply.
It seems like boost,maf is not working, I’ve sent a debug log to developers if that helps.
Bellow are images if what I’m seeing. I have fully set up the car specs Inc VE.
For some unknown reason I cannot get boost, manifold ect to read. I have tried body and calculated.
Thanks Alex, the screenshots help a lot.
They show that RealDash is talking to the ECU fine (RPM, speed, throttle, temperatures, lambda and barometric pressure all come through), but two readings are missing from the ENGINE tab: Manifold Absolute Pressure and MAF. That’s why no boost gauge works:
- Manifold pressure: on the 2.0 TFSI with the MED9.1 ECU, the standard OBD2 manifold pressure PID (0x0B) isn’t supported by the ECU, so a direct boost reading isn’t available over generic OBD2. Other TT owners have reported the same thing (ttforum thread).
- Calculated boost: without manifold pressure, RealDash can estimate boost from airflow, but that needs the MAF reading. Since MAF isn’t arriving either, the calculated boost has nothing to work from. Your engine size and VE settings are fine; they just can’t be used without MAF.
MAF should normally be available on this car, so let’s see if we can get it through. Could you try this:
- Open the settings of your OBD2 connection in Garage and turn off USE MULTIPID REQUEST and REQUEST ONLY FIRST REPLY.
- Reconnect, start the engine and check the ENGINE tab in Debug Data View again. Does MAF g/s (or Engine Load) show up now?
Also, in Torque Pro, which sensor are you using for boost (for example “Turbo Boost & Vacuum Gauge”), and does Torque show a Mass Air Flow value for your car? That tells us what Torque is actually reading.
We’ll also go through the debug log you sent; it shows exactly which readings your ECU reports as supported.
Hello,
Thank you for the support so far. I will give this a go tomorrow.
So far i did try USE MULTIPID REQUEST (OFF)
With TorquePro i belive it was the Turbo Boost gauge however in OBD2 settings i can select to either read boost from MAP or MAF either one i select it reads. I unplugged my MAF sensor and MAF mode didnt work but MAP did if that helps. In the active list of pid gauges i could not see MAF on torque pro.
Im also going to try the XML i edited to try force a connection
realdash_obd2.xml (4.0 KB)
Thanks for the log. It was started while RealDash was already connected, so it’s missing the connection setup part, which is exactly where RealDash asks your ECU which PIDs it supports. From what’s there, RealDash never requests manifold pressure (PID 0B) or MAF (PID 10) at all. It only polls RPM, speed, timing, throttle, O2/lambda, coolant, intake temp and barometric pressure, and all of those answer normally.
Your Torque test is a good one. If its MAP-based boost still works with the MAF unplugged, the ECU may well report manifold pressure, so my earlier comment that PID 0B isn’t supported may be wrong. We need the startup part of the log to know for sure.
Could you capture a new log like this:
- Make sure your boost gauge is on the dashboard, using Manifold Absolute Pressure (or calculated boost).
- Enable debug logging in Settings, then fully close RealDash (swipe it away from recent apps).
- Start RealDash again and let it connect to the car with the engine running. Give it about a minute, rev the engine a bit, then send the log.
Please do this with the default OBD2 settings, not the edited realdash_obd2.xml, so we see what the ECU reports on its own. The log will show the supported PIDs list and whether RealDash drops manifold pressure or MAF as unsupported.
1 Like
Hello,
So turning both off has made no effect.
With the custom XML above in debug it will show maf, lambda mad is stuck at 0 and manifold is stuck at 100.
Ive also tried to assign a gauge boost manifold ect with no joy.
I don’t understand why torque pro will read just fine and real dash will not I assume it’s a pid issue?
Hello,
This has just been done thanks
Thanks, this log has what we needed. Your ECU (MED9.1) tells RealDash it does not support Manifold Absolute Pressure (PID 0B) or MAF (PID 10), so RealDash doesn’t request them. That’s why both stay empty and calculated boost doesn’t work. Your multi-PID and custom XML settings aren’t the problem.
Test 1: Some ECUs answer a PID anyway. Add this to your custom OBD2 XML and remove any other 010b line:
<command send="010b" skipCount="0" targetId="31" keepInRotation="true"></command>
keepInRotation="true" makes RealDash keep requesting it even though the ECU says it’s not supported.
Test 2: In Torque, which sensor does your boost gauge use? Long-press the gauge → sensor details. If it’s a custom PID, you can add it to your custom XML like this, replacing the capitals with Torque’s values:
<command send="PID" header="atshHEADER" skipCount="0" targetId="31" units="kPa" conversionABC="EQUATION"></command>
For example, PID 221234, header 7E0 and equation (A*256+B)/100 (formula written the same way as Torque’s equation. A is the first byte of the reply, B the second, and so on.) would be send="221234" header="atsh7e0" conversionABC="(A*256+B)/100". targetId="31" feeds the value into Manifold Absolute Pressure, which should be absolute pressure in kPa (about 100 with the engine off). If Torque’s equation gives psi, bar or relative boost, post the details and we’ll help convert it.
1 Like
Hello,
Custom XML did not work.
In torque pro you cannot see details all I could see was this
Thank you
Thanks for the Torque screenshots, they explain it.
The [ff1202] next to “Turbo Boost & Vacuum Gauge” means it’s a value Torque calculates itself, not a reading from the car. Your log confirms the ECU doesn’t offer manifold pressure (PID 0B) or MAF (PID 10). That’s why the XML test didn’t work, so Torque must be working out boost from something else.
It’s most likely engine load (PID 04), which your ECU does support. At idle Torque shows -10.95 psi, which is about 26 kPa absolute. That’s about 25% of atmospheric pressure, roughly the engine load you’d expect at idle. It also explains why Torque’s MAP mode kept working with the MAF unplugged.
You can do the same in RealDash. Add this to your custom OBD2 XML and remove the 010b and 0110 lines:
<command send="0104" skipCount="0" targetId="31" units="kPa" conversion="V*101/255" keepInRotation="true"></command>
This feeds an estimated manifold pressure into Manifold Absolute Pressure, so the boost gauges will work from it. 101 is your barometric pressure in kPa, which your ECU reported.
One catch: the OBD2 standard caps engine load at 100%, so this estimate maxes out at about 0 psi. It shows vacuum fine but won’t show positive boost. Could you check in Torque whether its boost gauge goes above 0 when you accelerate hard? If it does, Torque is using something else and we’ll dig further. If it stops at about 0, that’s the limit of what generic OBD2 can give on the MED9.1. Real boost pressure would need Audi-specific diagnostic data, which generic OBD2 adapters and apps don’t read.
1 Like
Hello Niko,
Thanks for the help, it’s so mind bobbling to figure out. So Torque pro reads boost above 0 and shows vaccume accurately and boost shows 1.5-1.7 bar my map is set to 1.5bar on low boost so it’s accurate as possible I guess. I also have a mechanical gauge that’s accurately showing 1.5 too.
Thanks for the help so far appreciate the support