Thanks for the help. I am 100%/Mac and don't have parallels or whatever to run windows, but yesterday I fired up my son's old gaming PC/windows laptop and took a look at the scene file (can't edit maths channels on a Mac...) and I think I found a few minor issues (although I really only know enough to be dangerous). I made some tweaks and need to do some more testing in the car to see if the issues are resolved. Will report back after the weekend!
Thanks,
Tom

 

That's GOOD (knowing just enough to be dangerous ).

The Windows VBOX Setup is a must option for setting up maths, but not the "fake brake" long g indicator. Let us know!

 

THAT is cool stuff!

 

You should see the rest of the data setup on that car... two loggers (one just for the engine), 20 analog channels (still want more!)...

 

... and I thought I was the only crazy one. I use shock potentiometers to measure ride height and therefore lift and downforce (on a 911 there is mostly lift) and from the data found out that the springs on my car were not correct as advertised by the seller (they were far off, which explained a lot of other issues). People struggle with stuff for years without knowing what they are actually chasing if you don't have detailed data logging capability and (in my case) help interpreting the data.

 

Where is the “love” button for this post?

Seriously, the validation of baseline and verification of a given setup really helps guide progress and save incredible amounts of time.

What few people realize is that capturing data when things are working well is one of the greatest benefits, so you can see what’s happening when it’s really right. The ideal baseline.

 

I have not had good luck with those units as ride height. I have some laser units that do work really well, but they are more than $12.

What channels do you find most valuable? Depending on the day, I have about 100 channels of data and really have found the value to depend no some different things. After engine health, throttle position, brake position, and steering position, I've the TPMS to give the most value, followed by tire temp, brake temp, then suspension travel.

Absolutely. It's way easier to measure what you want to know and make informed decisions. But then I'm preaching to a guy with a good data setup

 

Well, I went out once with the IR sensors, but that was Indy, and other things went wrong... so no data sets to eval. If they work, they'll save me a lot of trouble (working the ride heights through the shock pots). If they don't... yeah, I'll have to look into the laser setups. Care to share what you're using?

Most valuable - this really gets to what my focus is at the time. Engine health for sure is high; for me and my car, driver mod is relatively low in the order, driver will drive to what the car is capable of, so brake and TPS aren't so critical except occasionally in reference to other things (like monitoring engine performance, mixture during accel, that kind of thing). Shock pot data, if we're chasing that. Tire temps would be a nice add, but a big incremental bump we haven't been able to justify yet.

So then it's ride heights, since, in addition to making/keeping the engine healthy, high on our list is getting the aero optimized, and we're still trying to work on filling in our aero map data, figure out how to get the height and rake dialed at speed for optimal downforce. We were making progress, then made base chassis changes which resulted in a spring change, which screwed up all our dynamic/at speed settings, so we're trying to figure out how to get back to that point, to get the car at the right attitude when she's at speed. Would be a lot easier if we had a third spring setup, but no capability to readily engineer that in on the rear, where we really need it. Limitations of the suspension design, unfortunately...

 

I've run/sell a sensor from Banner. I get very good pricing and have the wiring control figured out. Ita a good setup and gives good data.