Thanks for the suggestion - I'll re-run VCDS tomorrow with the CAN sniffer and see exactly what it's doing.
From memory in pure OBD2 mode VCDS only displays the PIDs from the standard set that VW implements (so no MAP boost). If I recall correctly it runs the 01x0 Support PID queries upon connection and filters the list of available PIDs based upon the ECU's response, without using any extra 'smarts' that RossTech might have gleaned over the years.
I *think* that it gets boost by using the $7DF CAN format and initialising a 2 way session with the ECU in the other communication modes, or perhaps it's in a measuring block from one of those direct ECU responses. Of course I'm more than happy to be wrong, as if VCDS can obtain MAP boost using an extended PID then we can do so too.
As an aside, MAP boost via OBD2 works on the Mk4 Golf - for some reason VW dropped it from the supported PID list for the Mk5 generation when the OBD2 connection switched to the CAN protocol.
For now, at least, we've decided not to include any interpolated or calculated boost values in the app. Partly because DashSketch is more about being a 'connected vehicle' product rather than a pure 'gauge and readout' app, partly because there are other vehicle makes that do support the MAP boost PID, and partly because we've got an awesome CANBus Adapter waiting in the wings that will read pretty much anything...
Bookmarks