follow ft86club on our blog, twitter or facebook.
FT86CLUB
Ft86Club
Speed By Design
Register Garage Members List Calendar Search Today's Posts Mark Forums Read

Go Back   Toyota GR86, 86, FR-S and Subaru BRZ Forum & Owners Community - FT86CLUB > Technical Topics > Tracking / Autocross / HPDE / Drifting

Tracking / Autocross / HPDE / Drifting What these cars were built for!


User Tag List

Reply
 
Thread Tools Search this Thread
Old 02-18-2021, 03:35 AM   #15
timurrrr
Senior Member
 
timurrrr's Avatar
 
Join Date: May 2019
Drives: 2022 GR86
Location: Between Sonoma and Laguna Seca
Posts: 1,704
Thanks: 2,128
Thanked 1,292 Times in 715 Posts
Mentioned: 30 Post(s)
Tagged: 1 Thread(s)
Quote:
Originally Posted by Compelica View Post
... with the OBD Fusion app set as a Scion FRS.
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
timurrrr is offline   Reply With Quote
The Following 3 Users Say Thank You to timurrrr For This Useful Post:
Compelica (02-18-2021), EndlessAzure (05-11-2022), SCFD (01-14-2023)
Old 02-18-2021, 04:41 AM   #16
Compelica
Senior Member
 
Compelica's Avatar
 
Join Date: Apr 2019
Drives: 86 GT
Location: Malaysia
Posts: 352
Thanks: 215
Thanked 204 Times in 104 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
Old 05-11-2022, 04:08 AM   #17
EndlessAzure
Wheels for Brains
 
EndlessAzure's Avatar
 
Join Date: May 2017
Drives: '14 FR-S [37J] | Daily/Track
Location: Los Angeles
Posts: 878
Thanks: 108
Thanked 563 Times in 360 Posts
Mentioned: 14 Post(s)
Tagged: 0 Thread(s)
Garage
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
Would you have any insight on how to implement this on Harry's Lap Timer Custom PID Menu? The requested inputs are pretty different compared to what I've seen here and am used to.


Developer guide: http://www.gps-laptimer.com/LapTimer...%20Program.pdf



The input menu asks for

  • Channel
    • Lists a bunch of available channels that HLT records to. Not particularly important, just the column in the default CSV that the application records to
    • I would map it to "Brake Pressure [kPA]" and scale it to % in post processing
  • ECU
    • Defaults to "ALL" for functional calls
    • States to address a specific ECU if desired for physical calls (such as "ECM" or "TCM"), or when using custom mode $21, $22, $23 below
  • Mode
    • Mode 1
    • Mode 9
    • Mode 21
    • Mode 22
    • Mode 23
  • PID
    • 1, 2, or 3 byte hex strings
  • Request Frequency
    • Low
    • Medium
    • High
  • Formula
    • Basically C-language logic, similar to what was used in RaceChrono implementation
-------------------------

My best interpretation of the inputs that would work in HLT would be, with some feedback from the developer on a similar implementation [ http://forum.gps-laptimer.de/viewtopic.php?t=5589 ]:
  • Channel: Brake Pressure [kPA]
  • ECU:ECM
  • Mode: Mode 21
  • PID: 41
  • Request Frequency: High (probably doesn't matter from a functionality point of view)
  • Formula: =MIN(100 : (1.1 * MAX((A-10))))


Obviously, it doesn't have field to input a custom header like I'm used to seeing in applications like Torque (and RaceChrono). However, there is a way to specify a custom width for the parameter by adding leading zeroes. For example, specifying the PID as "41" allows it a width of 1 byte, but if we instead label it as 0041, it will be 2 bytes wide. Perhaps this is the way to incorporate the header?

Last edited by EndlessAzure; 07-25-2022 at 01:51 AM.
EndlessAzure is offline   Reply With Quote
Old 05-12-2022, 03:48 AM   #18
timurrrr
Senior Member
 
timurrrr's Avatar
 
Join Date: May 2019
Drives: 2022 GR86
Location: Between Sonoma and Laguna Seca
Posts: 1,704
Thanks: 2,128
Thanked 1,292 Times in 715 Posts
Mentioned: 30 Post(s)
Tagged: 1 Thread(s)
Quote:
Originally Posted by EndlessAzure View Post
Would you have any insight on how to implement this on Harry's Lap Timer Custom PID Menu?
Try ECU: 0x7B0.

If that doesn't work, you may want to ask on the HLT forum.
I know how to enter the config in RaceChrono and what underlying messages are sent over the bus, but never tried HLT, so don't know what format it wants for the OBD PID or ECU CAN ID.

Or you can try the superior CAN bus mode in RaceChrono
__________________
Follow the build thread for my GR86!
timurrrr is offline   Reply With Quote
 
Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
CAN bus PGN for steering angle and brake pressure RMP Software Tuning 0 04-09-2015 01:55 AM
best tire pressure gauge (tire pressure question) steveholt Wheels | Tires | Spacers | Hub -- Sponsored by The Tire Rack 19 03-21-2015 10:27 PM
Stock clutch+flywheel+pressure plate+ ACT lightweight flywheel & pressure plate PineappleFriedRice Transmission and Driveline 0 11-08-2013 04:54 PM
FS: FRS OEM E-Brake (Emergency Brake) Hand Brake Boot CamryDS Interior Parts (Incl. Lighting) 0 06-24-2013 11:26 PM
Redline360: Brake Lines, Brake Rotors, Brake Pads for BRZ/FRS Redline360 Brakes, Suspension, Chassis 12 01-05-2013 10:20 PM


All times are GMT -4. The time now is 05:41 PM.


Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2024, vBulletin Solutions Inc.
User Alert System provided by Advanced User Tagging v3.3.0 (Lite) - vBulletin Mods & Addons Copyright © 2024 DragonByte Technologies Ltd.

Garage vBulletin Plugins by Drive Thru Online, Inc.