I have an OBD II dongle that can transmit full OBD info such as diagnostic codes and engine parameters (boost being one) over either wifi or Bluetooth which can e read on an android or iOS device.
I have an OBD II dongle that can transmit full OBD info such as diagnostic codes and engine parameters (boost being one) over either wifi or Bluetooth which can e read on an android or iOS device.
I don't think DashCommand is pulling the actual boost pressure since that's in VW-specific OBD messages. It's probably displaying its "CALC.BOOST_PRESSURE" PID which is an estimate based on various values you need to specify correctly in the car's profile. If those numbers aren't configured right, the calculation is off.
At least that's how it works in my R, unless the recent DashCommand update made it read the VW-specific PIDs.
Yes, OBDII boost info is useless on these cars -- laggy, inaccurate, and capped. Doesn't matter if you're using Torque, a P3 gauge, or something else that uses OBDII. If you use a P3 gauge, use a boost tap.