Sale ends todayGet 30% off any course (excluding packages)

Ends in --- --- ---

Professional Motorsport Data Analysis: Analyse Reliability

Watch This Course

$197 USD

Or 8 weekly payments of only $24.63 Instant access. Easy checkout. No fees. Learn more
Course Access for Life
60 day money back guarantee

Analyse Reliability


00:00 - After each outing on track, the first thing to check is anything that relates to reliability.
00:05 This means not only the obvious things in the powertrain but also the reliability of the sensors we're using to measure our performance.
00:14 It's important to download each run individually.
00:17 This helps keep the data organised and makes it easier to review afterwards because it means you have a single log file for each change made to the car or driver.
00:27 Take some time to add some details to the log file to help with identifying it later.
00:32 Each logging system will have different input fields available at the time you download the logger.
00:38 At minimum you should include a sequential download number which might look like DL1, DL2, DL3 and onwards.
00:46 You should also add the session the data was recorded, driver name and anything else that'll help you when you're reviewing.
00:53 Like the setup change you tried on this run, the tyre choice, or if it was wet this session.
00:59 When checking for reliability between sessions, unless you find something that stands out, you don't typically need to go through the logged data.
01:07 Instead, you should make use of channel reports.
01:09 Most logging systems have some form of automatic highlighting built into the channel reports to show maximum and minimum values for each channel.
01:18 Which is helpful in allowing you to see any values that stand out.
01:22 For the powertrain, you should review all the relevant temperatures, pressures, voltages and currents to make sure everything looks to be in the nominal range.
01:31 Things like oil pressure and temperature, inlet temperatures, fuel pressure, wide open throttle lambda and battery voltage.
01:39 You'll want to do a similar review of the relevant readings for the performance related sensors.
01:44 This is more to catch a sensor that has started to fail or needs attention so it can be rectified as soon as possible.
01:51 Skipping this step, can lead to making some of your data unusable should it now be caught as early as possible.