When you click on links to various merchants on this site and make a purchase, this can result in this site earning a commission. Affiliate programs and affiliations include, but are not limited to, the eBay Partner Network.
Non linear custom sensors are not a problem for RS2 or RS3 devices.
I would say the goals are different for different teams, drivers, and championships.
Some hardware is more capable for certain tasks than others.
That's why it's good to have choices.
__________________ -Peter Krause www.peterkrause.net www.gofasternow.com
"Combining the Art and Science of Driving Fast!"
Specializing in Professional, Private Driver Performance Evaluation and Optimization
Consultation Available Remotely and at VIRginia International Raceway
I'm more than happy to share -- the question is what format helps. The 2D table is in the Dash config file for my C125 -- to look at that you'd have to be using dash manager and I don't think I can share the config file anyway (because it has some templates in it that are licensed content). I could make a screen shot of it in the edit window?? The other element is the raw data -- I captured that in a spreadsheet. I could upload that and provide a link I imagine if that would be better. Let me know what form works best and I'll figure out how to deliver it.
Hmm, actually, I guess I made a table in both the dash config and the i2pro math channels. The one in i2pro as part of the math content can be exported to XML format if you want that.
I'm more than happy to share -- the question is what format helps. The 2D table is in the Dash config file for my C125 -- to look at that you'd have to be using dash manager and I don't think I can share the config file anyway (because it has some templates in it that are licensed content). I could make a screen shot of it in the edit window?? The other element is the raw data -- I captured that in a spreadsheet. I could upload that and provide a link I imagine if that would be better. Let me know what form works best and I'll figure out how to deliver it.
If the comms template is "licensed content," both Chris and Joe lock the addresses (they also lock it to the hardware by serial number, so the config wouldn't work in a dash not listed for this config), just look for the padlock in the comms list on the CAN.
You can take a screenshot of the 2D window or export it. The spreadsheet would allow people to adapt it or build their own 2D.
That's math channel spooge from i2pro. Being a bit lazy (and having averaged left/right recorded values anyway on the assumption that the car is symmetrical but the measurements might not show that owing to operator error ) I made a one sided 2D table. Thus first I take the normal steering wheel angle channel and take the absolute value of that so it's 0-200 degrees (I didn't measure more than that because in my car I apparently don't use more than that at the local tracks anyway). Then from there that values is fed into the 2D table that is made from the horizontal measured toe angle for various reported steering wheel angles (live view of the same channel that is recorded in the logger data). That gives me an interpolated steered wheel angle which I labeled "outside" to remind me that it's only talking about the outside wheel (relative to turn direction). [you can see in the spreadsheet that I did collect outside and inside wheel toe values but I think the inside ones aren't relevant to this exercise?? Dunno, someone may have to correct me on that ]. From there the formulas for oversteer and speed weighted oversteer are pretty standard from the usual sources (I think the speed weighted one is a Buddy Fey original??).
This is what the table looks like in i2pro:
The excel file should be available here if I did the link permissions correctly. Let me know if it doesn't work. Also, especially for Matt and Peter -- if you guys see errors in my logic or math here, please correct me!
If the comms template is "licensed content," both Chris and Joe lock the addresses (they also lock it to the hardware by serial number, so the config wouldn't work in a dash not listed for this config), just look for the padlock in the comms list on the CAN.
Right but in this case I was debugging some bits and pieces with Chris so some of the templates are not locked and not mine to share.
I'm more than happy to share -- the question is what format helps. The 2D table is in the Dash config file for my C125 -- to look at that you'd have to be using dash manager and I don't think I can share the config file anyway (because it has some templates in it that are licensed content). I could make a screen shot of it in the edit window?? The other element is the raw data -- I captured that in a spreadsheet. I could upload that and provide a link I imagine if that would be better. Let me know what form works best and I'll figure out how to deliver it.
Hey, yeah a spreadsheet s absolutely fine. I'm not picky.
That's math channel spooge from i2pro. Being a bit lazy (and having averaged left/right recorded values anyway on the assumption that the car is symmetrical but the measurements might not show that owing to operator error ) I made a one sided 2D table. Thus first I take the normal steering wheel angle channel and take the absolute value of that so it's 0-200 degrees (I didn't measure more than that because in my car I apparently don't use more than that at the local tracks anyway). Then from there that values is fed into the 2D table that is made from the horizontal measured toe angle for various reported steering wheel angles (live view of the same channel that is recorded in the logger data). That gives me an interpolated steered wheel angle which I labeled "outside" to remind me that it's only talking about the outside wheel (relative to turn direction). [you can see in the spreadsheet that I did collect outside and inside wheel toe values but I think the inside ones aren't relevant to this exercise?? Dunno, someone may have to correct me on that ]. From there the formulas for oversteer and speed weighted oversteer are pretty standard from the usual sources (I think the speed weighted one is a Buddy Fey original??).
This is what the table looks like in i2pro:
The excel file should be available here if I did the link permissions correctly. Let me know if it doesn't work. Also, especially for Matt and Peter -- if you guys see errors in my logic or math here, please correct me!
i noticed the spreadsheet tab says 991. For some reason I thought you were doing it on your GT4.
Ah yes, you are right: this is data for my GT3. I do have a set of numbers for the GT4 but I did those a less reliable way -- measuring the steering wheel turn by linear distance of the center mark from vertical and reading off the steered angle from the PCM display. That data has a fair measure of fudge because the linear distance measurement was less than precise and the PCM readout rounds pretty aggressively. Dundon wanted to borrow the GT3 for a fit test on their 991.2 splitter product so that's why that car ended up in their shop and I was able to make serendipitous use of their alignment rig for more precise measurements.
Ah yes, you are right: this is data for my GT3. I do have a set of numbers for the GT4 but I did those a less reliable way -- measuring the steering wheel turn by linear distance of the center mark from vertical and reading off the steered angle from the PCM display. That data has a fair measure of fudge because the linear distance measurement was less than precise and the PCM readout rounds pretty aggressively. Dundon wanted to borrow the GT3 for a fit test on their 991.2 splitter product so that's why that car ended up in their shop and I was able to make serendipitous use of their alignment rig for more precise measurements.
The 991 has a quicker steering rack than the 981 doesn't it?
I know, right?? The GT4 numbers I got I'd take with a pinch salt...as I say, the methodology is probably suspect trying to measure steering wheel rim mark offset from vertical/straight ahead and converting that to turn angle gives lots of opportunity for slop plus I haven't tried to examine how accurate the steered value PCM spits out is so it's possible that too is a source of variation -- I mean I assumed it's steered wheel angle shown there, given the numbers, but it's possible that assumption isn't correct.
I know, right?? The GT4 numbers I got I'd take with a pinch salt...as I say, the methodology is probably suspect trying to measure steering wheel rim mark offset from vertical/straight ahead and converting that to turn angle gives lots of opportunity for slop plus I haven't tried to examine how accurate the steered value PCM spits out is so it's possible that too is a source of variation -- I mean I assumed it's steered wheel angle shown there, given the numbers, but it's possible that assumption isn't correct.
Hmmm, hard to believe it's 30% off though. Couldnt you get the steering of AIM?
It's just a bit coincidental because supposedly the variable steering takes the ratio down to 12.7 IIRC, right in the range of what you got.
08-20-2020, 09:18 PM
) I made a one sided 2D table. Thus first I take the normal steering wheel angle channel and take the absolute value of that so it's 0-200 degrees (I didn't measure more than that because in my car I apparently don't use more than that at the local tracks anyway). Then from there that values is fed into the 2D table that is made from the horizontal measured toe angle for various reported steering wheel angles (live view of the same channel that is recorded in the logger data). That gives me an interpolated steered wheel angle which I labeled "outside" to remind me that it's only talking about the outside wheel (relative to turn direction). [you can see in the spreadsheet that I did collect outside and inside wheel toe values but I think the inside ones aren't relevant to this exercise?? Dunno, someone may have to correct me on that 
