Just edit your VCDS measuring block lookup for reference pvdr_w.
GolfR will have this setup stock, so use that to reference.
This is only for ACTUAL boost in vcds. ASM required to make REQUEST read higher.
That's why you need ASM. VCDS is probably still reading pvdkds_w or something.
In ME9 pvdr_w get converted to pvd_w then onwards (doubled) to the 2550 limited vars.
There's notes on here to get the blocks to measure what you want I think.
Another idea is can you log the sensor voltage? If so you can work out the boost value fairly easily.
Back to the subject.
All of the ME9 ECUs read pvdr_w through measuring blocks, don´t they?
I checked both my original binary and Golf R (1K8907115F) binary and they both have the same variables in measuring block 115 (plsol & pvdr_w).
When I checked the address for measuring block variable 77 / 4Dh with IDA, both of the binaries have identical function.
The value range is specified to min 12h (18) and max FAh (250) in both cases, just as the measuring block description in FR says for pvdr_w.
Also when checking the DSVDGRAD & DSVDOFFS functions they too are identical between the binaries.
According to FR both of these maps access pvdr_w so I could get the DRAM variable address from there.
However would making a custom function to read the raw pvdr_w change anything if it is limited to 250 max anyway?
