View Single Post
Old 02-18-2021, 04:41 AM   #16
Compelica
Senior Member
 
Compelica's Avatar
 
Join Date: Apr 2019
Drives: 86 GT
Location: Malaysia
Posts: 358
Thanks: 219
Thanked 205 Times in 105 Posts
Mentioned: 2 Post(s)
Tagged: 0 Thread(s)
Quote:
Originally Posted by timurrrr View Post
That's what I was asking about

Anyhow, WE DID IT!
In RaceChrono format, the parameters are:
Channel: Brake Position (%)
OBD-II header: 0x7B0
PID: 0x2141
Equation: min(100, 1.1 * max(A-10, 0))


Explanation: the min/max trick makes sure the output is in the [0%, 100%] range. The 1.1x is a multiplier that roughly matches the scale factor I previously chose for my CAN bus reader so that 100% is reported when I'm braking really hard. The -10 offset is to compensate for the default value of 10 (I've no idea why the reported value never goes below 10).

Enjoy!

Having said that, OBD-II provides a much lower refresh rate than CAN, so I still recommend investing a little time into making a DIY CAN reader as documented on my GitHub:
https://github.com/timurrrr/RaceChronoDiyBleDevice
Nice!

To add on - the brake pressure PID visible in the app shows in two units: by MPa and by voltage. And in the voltage there is always a value (about 0.1v if I'm not mistaken) even when the brakes are untouched so it correlates back to your compensation. However the MPa value does go from 0 to 10 MPa - this is with me lead-footing the pedal
Compelica is offline   Reply With Quote