we're going to be looking at some Motorsport data analysis fundamentals so I'm just going to walk you guys through some of the founding principles whether that's about selecting a logger about maybe a little bit about setting it up and certainly we're going to dive into quite a lot of basic analysis looking at driver inputs how to interpret the data how to make use of some of the tools within the user interface inside the software so the first thing probably we want to talk about is talking about the different options you've got available when it comes to logging now there is a huge range like there are in in many parts of the Motorsport aftermarket world whether it's spending as little as 500 US dollars right up to many many thousands of dollars as far as Motorsport logging goes Motorsport logging is one of those things where I think it's really underrated uh there are a lot of people that probably don't uh feel that they've got the skills or not really quite sure how they how to get started and I think that's one of the barriers along with all the technical elements with when it comes to things like choosing a loggers to actually understand uh what's going to work for you and what's going to work best for your situation so you've got um at the basic end of the spectrum say that in the 500 US dollar Mark you've got basic little units like something that's aim sport which is a little usually Dash mounted unit it's about this sort of big it's it's main well I just guess its primary function is to work as a gps-based lap timer but some of those models have also got the ability to log extra data from the car so whether that's coming over the can bus and via the OBD2 port so things like throttle position uh brake position depending on the sensors you've got in your car it also gives you live feedback in terms of your reference lap time your Delta to that which we'll get into later in today's webinar as well but I guess my point I want to make it just a relatively small price point there's a huge amount of information you can already learn from the car and certainly from your driving and with those sorts of loggers you've also got the ability to use software to download that data and be able to analyze it in the same way that we'll be going through today we'll be using a slightly different system but the principles are going to be exactly the same then you move up into something more something like an advanced Dash logger which is I've got an example just here which I'll just bring under the overhead again so this particular example is motec c125 it's a really serious piece of Kit really um even though it's I guess aimed at the mid midpoint of the market so as you see here we've got a fuller full color to screen we've got a series of LEDs along the top and all of this is super super flexible as far as being fully configurable this particular model uh has this sort of I think it's called amp style connector on the back they're also available with an Auto Sport connector depending on the application that you're using they've got things like onboard G sensors a huge amount of log potential logging capacity lots of options you can choose from they can do onboard math they can do uh yeah all sorts of clever stuff whether it's controlling outputs on your car and controlling systems with different logic so this is this particular Dash is something we're going to be fitting the same model to we're going to be upgrading the logging system in our racecraft GT86 shop car from an earlier model motek that doesn't allow us to do onboard math and that's one of the main reasons we're upgrading to this this unit so that's a really good example of what I would say typically represents a dashlogger albeit probably at the upper end of the scale of the price scale uh then moving on from something like a dash logger you've got something like a standalone logger which essentially you can treat as a black box uh it's something you tend to it doesn't have a screen or anything that's typically bolted in the car in the same way like a power distribution module or an ECU would uh it's something that typically tends to be used in really high ends of racing they've usually got much higher specs things like the ability to do multiple log really multiple high frequency signals so whether it's being able to do things in the thousands of Hertz range depending on the systems you're trying to log or having massive configurability or lots of log file capacity stuff like that so it's something that you'd expect to see in a factory built race car whether it's like a WRC car or an FIA GT3 or a prototype these are the kind of applications you would tend to see a standalone logger attached to the car you've also got the option of using some cases of using an aftermarket ECU it's a lot of aftermarket ecu's these days are including onboard logging as part of them they're probably the biggest restriction with a lot of those is they don't tend to have a lap trigger which is when you're doing Motorsport data analysis which is definitely one of the most important metrics we need we need to be able to automatically trigger lap by lap whether that's happening from a beacon that we've got set up on the side of the track whether that's happening by GPS it's a really important thing to be able to do to understand when each lab's starting and finishing so we can back to backlabs and compare them so that's definitely a restriction to keep in mind if you're planning on using your ECU for your logging analysis so I just want to switch across my laptop screen here I'm just going to bring up our the software I'm going to use for today's demonstration just to give you guys a little bit of a work through a walkthrough of it so this particular software is motex I2 software it's what you'd use if you've got any Motif Pro sorry any motec logging project product product this is the software that you typically use I'll give you guys this is what I'm going to do the demonstration on today to give you guys a bit of a walk through and I want to start by just introducing you guys to some of the channels that we might get out of uh might get out of the logger so I'm just going to create a new worksheet here and I'll give you I will give you guys a bit more of a tour through the UI once I've got some displays showing up on here so it's a super flexible piece of software you can as we'll see today there's all sorts of displays you can show and they're all heavily configurable um this is the software that I'm uh I'm quite am quite familiar with it's what I've used and a lot of a lot of my career amongst other different systems but I think it's a really powerful system everything we're talking about today is going to be applicable to uh different systems so it's it's going to be General it's not just going to be about motek so what I'm going to do here is to start with a simple time distance graph and we'll go through what what that is a little bit as we go I'm just going to add a channel here which in this case I'm going to add the core speed which in motek land is simply means the corrected Speed Channel so that's taking uh in this case this car has got a wheel speed sensor on all four corners of the car and the software is using some algorithms to get rid of things but we'll try it as much as possible get rid of things like wheel lockups and wheels slip from the drive wheels looking at the different conditions and using the algorithms to try and ignore those things to try and give you the best approximation for the car speed that you can so all the data I'm going to go through today is just from a race event that was from a generic GT car just to give you an idea of what it is there's two drivers that have been involved in a different skill levels so I will go through that and we'll show you uh how we do some basic driver analysis of the car but just I want to um I'm going to build up this basic time distance plot so we've got here I've got added the corrected Speed Channel and along the bottom we have in this case time A Time axis so this is as the car moves to the lap as we are getting into the high speeds we end up at the top of the Sawtooth and as the car breaks and then goes through corners we slow down and then see it accelerates again this is the pattern that goes on through the lap so we've got these sections uh these sections of the lapse here these are the corners so that mid corner here this area down town here is what the uh that's giving us the apex of the corner and these top big Peaks here uh the top speed that the car is getting to before it breaks for the next corner so I'm just going to go through and I'll show you guys how you can build up a couple more channels so just by going to the properties here let's add in a couple more channels so add in the throttle which is a pretty typical but we want to add in so we'll add in throttle pedal we'll add a brake pressure we'll use this one here and I should say as well um as I add the next one we've got all of the different log channels all of the channels that we've configured in our logger to log will be available to look at in any time distance plot like this so in this case if I scan down here you see these little symbols where this little little yellow liners that's indicating that this was a log channel it's something that's been measured inside the logger these uh little calculated looking symbols are what we call math channels so these I'll get into that into a future webinar in a bit more detail but essentially that's taking the logging channels doing some manipulation on those channels with some a lot and some math that we defined in our software and then it spits it out as a new channel that we can use that might be more useful to us inside the analysis but that's just what that symbol means but as I scroll down this list these are all the different channels either I've logged or of calculating in the background and by searching through here uh this list so in this case next one I'm going to add a steering trace it just Narrows down the angle for me here so it Narrows down the selection for me here to help me see what's going on I'll also add in a gear a gear Channel as well so if I add those in now we've got all of those showing so this is showing how the throttle the brake the steering and the gear as well as the speed are progressing throughout the lap this is a pretty typical layout that you might see on engineer's screen these are the kind of typical driver channels that we're using a lot of the time when you've got these channels available logged in the car to analyze what's hitting both with the car and also what the driver's doing as well so I'll just get an extra plot in here on the side we've also got the ability to actually no I won't I'll go a little bit more in depth on the time distance plot before we jump into that so one of the things that's really important to understand about a time distance plot is that it's called time distance because you've got the option to display the XS x-axis as at the time or distance in this case by default it's shown as time we can see that because the axis along the bottom is showing these time values we've got the option at the top of the bar here to click this across the distance and now we can see this changes uh to a distance scale so this is a really important point that I want to I want to labor on a little bit because that difference between time and distance is really critical to get right when it comes to particularly comparing two different laps to each other so one of the concepts that's really important to understand is the concept of an overlay so in the left hand sidebar here you can see I've got all my different laps laid out here and I've got all the different lap times laid out here and the thread uh this little red circle indicates the primary lap so the main lap that I want to analyze so I can go and with whether I'm using keyboard shortcuts or click on the laps I can move between them and what I can also do is add an overlay lap so in this case I'm going to add a lap from earlier in the race so if I click this section here that gives me the main piece of data is showing in color and the reference set or the set i'm comparing to is shown all in white so that's what I see in each one of these sections of the plot we've got now a white section added and added into it as well so the important one of the really important things to understand here is that there is quite a big difference in lap time between these two drivers we can see the way just looking at the speed Trace you can see the cars being driven quite differently between these two and uh the important thing to understand about a time the difference between looking at in terms of time or distance is if you're looking if you're looking at the plot in terms of a distance you're comparing the position of the car in the same position on track so regardless of one if one driver is faster than the other when we're looking at this data if we're looking at it on a distance scale it means that each the car is at the same position throughout the lap even though it's taking more time to get there you're comparing the position of the car on track which is usually the most important thing we're looking at it particularly in terms of driver and car performance metrics you also have the option if I flick back to a time scale here of looking at it in terms of distance sorry looking to it in terms of time so if we're looking at things in terms of time now we're comparing all of this data at the same time into the lab as in the time since the car last passed the lap trigger Beacon so because we've got a big difference in the time between two drivers here we can see that whereas before we had the two speed traces even though there were differences in them vertically you can see the shape of them were matching up at the same features were matching up in the same position track because the car the cars are being driven around the same piece of track so you're going to expect even if the differences in how well the car is being driven vertically you're going to see the car following the same features in this case we're seeing offset developing which at the start of the lap when the performance is quite similar these features for when they get on the brakes are quite similar even through turn one which is a really long turn at this track which is why you see this big Plateau here it's relatively similar and then as the White driver loses time we see all of these features are slowly slipping and that slip is getting further and further and further into the lap so this makes it really difficult if not impossible to make any meaningful uh driving analysis between these two drivers because what we want to compare is what you were doing at this point on truck on track not when you were doing it so we'll almost always I'm just going to flick this back to our distance plot will almost always be comparing these things in terms of lap distance there are certainly times when there are times when the time scale is relevant usually it's often looking at reliability or powertrain metrics much more so than actual driver analysis so I just want to give you guys a little bit more of a walkthrough of the UI here so we've got the ability to zoom so if I particularly pick a particular part on track I can zoom in and out like this by going up and down the keyboard if I want to look at a certain spot on track I've got shortcuts in this case in motix I2 it's w for zooming back to a full lap I can also double click and highlight a certain certain piece of track to look at it more detail obviously if I hover the cursor over I can drag this along with my mouse and we see the value in the top left of each Legend here on the screen if as I drag this through we can see these values given to us live both for the primary which is the main over the main piece of data and also the white which is the overlay and really handy sometimes as well is it's giving you an addition to giving you the values it'll give you the difference between them so we can see at this point here we've got basically Full Throttle on the main piece of data only 83 on the overlay and that's the 17 17 difference which is it just stops you having to do that math in your head all the time you've also got the option of showing uh some statistics which are just brought up in the top right here so what that's showing us is some basic statistics for what we've got showing on the screen at the moment so if I just zoom back out to a full lap we can see for the main piece of data this little symbol here means minimum so the lower speed on track was 54. the maximum was 241 and the average was 149 and it's the same the same statistics computed for the overlay as well so often if you're interested in looking at a maximum or a minimum you can either look at it at the whole race so by pressing F2 I can zoom out to the whole race or we're pressing W I can just get back to our whole lap so depending on the things you're interested in using these little tools can really save you a lot of time if you're looking to complete an ever looking for an average or maximum minimum particularly in terms of our reliability channels that can be a really uh useful way of looking at things some of the other things I want to point out which is typical to most data analysis packages is the position of the cursor on the screen will usually give you some statistics about well some some basic readouts of what's happening at the bottom or somewhere it'll be shown bottom somewhere it'll be shown on the screen so in this case I've got the where I position the cursor so just to be clear about it I'm talking about down here I've got the time reading out and the distance and the Really trick thing about that is if I want to compare two things so in this case I'm going to zoom to the section of the track I've got the throttle position here I've got the faster driver is staying on the throttle for longer the slower driver is lifting off so if I just position the cursor at where the slower driver is done they lift off press spacebar and come across it gives me a second cursor that comes up that gives me the ability to measure between those two points and where that's shown is down here in the bottom so it's showing it's showing me there are 0.3 seconds difference between those two events happening and that there are 23 meters of difference so that means that the Pro driver is in this case is going 23 meters later into the turn than the amateur drivers which is a really good way of being able to communicate that to uh when you're talking about differences between drivers and you're trying to help one driver with their driving relative to your faster driver of course video also comes into this it's a really useful tool uh but particularly and um when you don't have video uh being able to read the distance out in terms of that it gives them a relative change particularly into something like a braking Zone there's usually number boards on the side of the track so they can relate that distance you give them about how much deeper they need to do or go or what they need to do a different position on track that gives them a relative reference for how far they need to move along so that is the basics of the Delta function we've also got I want to dig in a little bit into how the overlays work here you see um as we move through the lap we've got the ability to look at the way the throttle is being used where the brakes being used and we can see really clearly uh differences and techniques so if I just skip forward a little bit here I'm just going to go to a really obvious part so here we've got it's really obvious the Pro driver is using a lot more brake pressure than the amateur drivers obviously they're the way they're ramping that up is much more aggressive the Peaks much higher where you've got the amateur driver here being yeah relatively quite a lot slower getting to the peak pressure and a little bit different in their release Behavior as well we'll dig into that a little bit later into the webinar so one of the things in addition to our performance aspects which is one of the things we're often really concentrating on uh in terms of Motorsport data analysis the other one is reliability so obviously if you've got a reliability problem it doesn't really matter how fast you're driving how good your driver is what how great your setup is if you've got a reliability problem whether it's in powertrain or tire pressures or anything like that that's going to stop you maximizing your performance before you even get the chance to so looking at reliability Matrix is one of the main things you need to start with when looking at your data analysis it's the primary thing you need to take care of before you can get to look at the performance and I want to show you guys a couple of ways we can make use of a typical data analysis package to make sure that everything's safe in the car so I'm going to open a new worksheet here and the first thing I want to start with is looking at a time distance plot in a similar way to what we did with the driver performance metrics so I'm just going to add a time distance plot here and let's add some engine parameters so I'm going to put engine oil temp I'll add another one for engine oil pressure and let's see what other temperature channels we've got here that we might want to put in we have coolant temperature for example so I'm just going to zoom out to a full lap and I'm going to get rid of the overlay for now just look at this main lap now if I sorry if I zoom out to a full race distance we can see the evolution and how these temperatures are changing throughout the race so at the top here we've got our engine oil temperature engine oil pressure and our coolant temperature now we can see straight away that there are some some big differences in the trends that are happening over the race and that's one of the really important things to understand about zooming over a whole race is it really gives you a good understanding of the trends that are happening are things slowly getting hotter or colder over a race have you got dips anywhere interesting features and one of the things I quite often like to do when I'm looking at a time distance plot for reliability channels it's actually at the Speed Channel in there because it gives you a lot more context about what was happening at that point on track I'll show you what I mean by that if I add the corrected speed again and I usually just pop that at the top so we'll add move the group up as well just so it's really clear so we can see here as the car moves through uh moves through the race this is quite a long race in this case it's about a three hour race we can see all of the features you can see those patterns as the car moves through the lap you can see that the patterns repeating over and over and over again so you can sort of see each lap in addition to each one of these little red lines which indicates a lat but you we see this trend in the coolant temperature there's something different really different happening same in the oil pressure and actually same in the oil oil temperature as well you see that same feature of something changing in the middle of the race we can see here in the speed trace it gives us a lot of information about what's happening in this case uh it looks like a safety card period uh where that will occurs slow down on track so they can clear an accident or a car that's uh not running anymore and the cars will need to drive around slowly for a while and order before they restart the race in order to collect that car off track so that's what's happening here so again you can just see how that speed traps gives you a lot more context we can also see these dips that are happening in the race we can in this case we can see the cars coming to a stop and this means for us this is uh during a pit stop so we can see the car doing its last inlap we can see the this constant speed here which was in in the car is in the pit Lane on its pit limiter traveling at a constant speed stopping in the box and then taking off again and continuing on for the rest of the race so for me that's that speed Trace really tends to give you a lot of useful information now there are limitations to using a time distance plot we're looking for reliability if you're looking for reliability issues or spikes or differences or maximum minimums and averages it can mean because when you look over the whole race distance like this there's often small features that you don't pick up because they're just too small especially if the car's been on track for quite a long run the other option is to go through lap by lap which is incredibly time consuming so in this case I've just zoomed to a particular lap early in the race and I can use there's lots of different shortcuts every different software will have different shortcuts for motix I2 it's in for next lap and you can see down the side here the selection of the lap is moving down as I go next lap it's going to the next lap so you can see how going through lap by lap especially long race it's a really tedious experience I'm going through if you're looking for a spike or a minimum or an average or something this is going to take you a long time particularly when you look through I'm only looking through a couple of really basic engine parameters here by the time you're looking for egts and lambdas diff temperature coolant pressure whatever it is whatever you're looking for it's a really time consuming process there is absolutely a value in using a time distance plot but I'll come back to that a little bit in a little bit I want first I want to talk about uh another another tool we can use to understand these parameters and that's a channel report so I'm just going to add one of these underneath and give us a chance to compare them so if I go to the UI here and uh add in a channel report now we've got the option to down in the bottom of this particular software we can add the channels that we want to report on so it'll become clearer once I make it what this is so I'm just going to add the same channels that we've got shown in our time distance plot so we're going to put our engine oil temp and engine oil pressure sorry I pressed the wrong button there to get out of that let me try that again engine oil temp engine oil pressure and we'll also add in our coolant temp now we've got the option here to have the software automatically complete uh it's automatically calculate sorry all the the different statistics for this channel so we've got uh minimums maximum the ranges which is how much it changes over a certain time period averages absolute values start in change standard deviations all sorts of different things and all these tools are there to help crunch the numbers for you and make your job a lot quicker by not having to look through all of these things manually so let's let's select some statistics to automatically calculate these things for us so for the engine oil temp one of the things would often be interesting is the maximum obviously we want to know uh when and where that happened and what it was uh the engine oil pressure would often be interested in the minimum and let's argument's sake let's say we're also interested in the average and the coolant temperature let's say we want the maximum and the minimum so I'll press ok now straight away uh that doesn't look quite right we have we're only showing it for the selected lap so I'll just go back into configuration and change it for everything we see that makes a bit more sense so if I just bring this out like this what we've got here I'll explain what we're actually seeing so like we've got a table here and along the top of here each one of these columns is a different lap that we're looking at throughout the race and we see the lap times are associated and these lap times match up with what we see in the lap selection column here as well and then on the other axis we've got our channels we're reporting on and whether it's a maximum just from this channel here so in this section here it shows us whether it's maximum the average one of the other functions that's really important are really useful is we've got the option to do some automatic highlighting so in this case and you this is user configurable but in this case by default it will show minimums with blue and maximums with red and on the scale here at the bottom we can scan through the whole race and we can see those maximum elements being highlighted for us in the same way uh the same exactly the same information is being reported on here and a little uh report graph so exactly the same values that are shown in this table are reported on here so we've got engine oil a maximum oil temp we've got our oil pressure evolving throughout the race and we've got our maximum and minimum coolant temperature evolving throughout the race so one of the beauties of using a channel report like this is it allows you to see what's happening sort of from a bird's eye view without having to dig into the detail of a lap by lap analysis so we can see here uh different spikes and different features in the same way that we saw by looking at the main data stuff I just go back to the full race you can see some of the features being replicated there but let's say there's a feature we're interested in so let's say we're interested in this oil pressure dip that's shown here if I click on that at this point uh in the graph it tells us it's lap 48. now if I want to go to lap 48 on here I can one there's lots of different ways I can do that but in motex I2 if I just zoom in a little bit further sorry that's not right that's lap 44 that's showing sorry I have got the right let by mistake I thought I had the wrong one I got the right one so this is showing us giving us an opportunity to dig into that in more detail so what I the point of what I'm trying to make is we've seen an anomaly something we're not quite sure what's going on in the channel report which is again just giving us that bird's eye view once we we can quickly scan the channel report if we see anything we're not sure about that's the point where you can go uh use something like a time distance plot to dig into the detail of what's happening so if we want to look at the oil pressure in this case it's fine there's nothing else going on but if we wanted to compare it to another lap with something was fine again we could bring up a reference and we could just see the difference in the different lines and how the oil pressure was evolving throughout the lap so in this particular case there's nothing actually wrong with what we see I just wanted to show you guys how you can make use of something like a channel report to really cut down the time particularly when it comes to things like reliability channels there's definitely performance applications you can use them for as well particularly when you get into heavy math channels and stuff but particularly from a performance perspective making use of Channel reports is a massive Time Saver when you're on track so uh the next thing I want to show you guys is uh discussing the time variants Channel which is something we use a lot and particularly from a performance perspective in Motorsport data analysis so again back over on my laptop screen uh we've got our same channels I built up for you guys before in the time distance plot if we want to compare the performance of two different laps one of the ways one of the obvious ways if I turn the overlay back on we can do that is by looking at the difference is difference in this case in the speed Trace so the way I normally configure this I'll just tweak this a little bit further the uis are usually quite configurable you can modify things and overlay things as much as you like I usually make the speed Trace a little bit larger just to give myself so I can see a little bit more detail because it's one of the primary metrics which is obviously controlling our performance on track uh I've got I can see these really clear differences in speed which are obviously going to be making massive differences in the lap time we can see here there's a big loss we can see here there's a big loss we can see here there's a big loss one of the other ways to visualize that that's really useful is by looking at something called the time variance or which is often also referred to as a Delta function so every software package every modern software package certainly includes this in motec you can press F3 to bring it up but there's also a button along the top you can use to bring up the time variants as well essentially what this is showing us is how much time slip we have along the lap so the places where the time variance is changing the most are the places where the most differences between those two laps those are the times when the differences between those two laps are the most so what I mean by that is if we look at the section of track here where we've got the colored driver compared to the White driver having a massive difference in their performance we can see the time variance has this big spike so this big change in gradient is indicating there's a big time loss happening for the reference driver and we can see how it sort of evolves throughout the lap we've got some sort of steady losses happening as we move throughout the lap but we have got these dips happening which are indicating our biggest losses the ones that we want to attack first so the way we yeah the way we use the time variance channel is usually by saying okay we've got a difference between either between two sit-ups on the car or between two different drivers or between the same driver and looking at one day to the other or maybe some different driving Styles or different ways you're driving the course you can see you want to look for these biggest spikes in the time variants these are giving us the low hang fruit the part the parts we want to attack first and really it's a case of with the Motorsport data analysis there's never enough time to attack everything it's usually a case of going through attacking uh a few maybe two or three positions of a track rather than trying to fix everything at once it's just not doable you want to look for the biggest losses first and take those first so in this particular case it's indicating and this particular track is turn one is a big loss there's another uh decent sized Spike here through a really fast section of the track which in this particular track is is a really high speed Corner which should be almost flat through there and then later in the lap we've got the spike and I'll come back and we'll actually dig into more of that data a little bit later I just want to go through a couple more things and we'll come back and look at the dig into some of the actual data and look at the reasons why we've got some of those performance losses this is a really good place to mention the webinar that if you guys have got any questions about anything you've seen so far Chuck those in the chat and Luke will Chuck those through to me and uh after I've gone through this last part of the demonstration I will get into some live q a and uh hopefully you guys have had some questions that have come up throughout the webinar so as far as using uh the time distance plot uh to actually understand these differences so let's take this difference at uh turn one which is a really obvious example so I'm just going to zoom into this part of the track I'm going to get rid of the variance channel for SEC just to make the the displays a little bit bigger as we see uh we looked at actually earlier in the webinar we've got the the first thing that's uh that stands out to us is how much earlier the uh one driver is lifting off the throttle compared to the other and again we can use that that Delta function so if I use the space bar at the point where he's lifting versus the other one we can we see down here it's about 20 meters so one driver is lifting about 20 meters later than the other uh which is obviously going to give us a pretty big difference in the speed trace the other really interesting thing here is actually the the braking position where the one driver is pressing the brakes compared to the other isn't actually uh that different but the brake pressure the is quite different so in this case we've got the slower driver which is shown in the white lines is using more pressure initially so they're actually slowing the car more heavily and in this particular part of the track and with this particular car you don't actually need a massive braking event there this is uh he's overflowing the car here and that's what's happening with this big we see if we line these two points up on the on the map we can see this extra brake pressure is really over overflowing the car which is one of the things that's contributing to this difference in Pace we also see something a little bit worrying uh this is a bit of an unusual corner it's it's two corners quite close to each other but it's a little bit worrying that he's coming all the way off essentially all the way off the brake and then coming on with one big stab again at the end where the Pro driver in this case is using a little bit more consistent it's not this isn't a particularly uh typical style of brake Trace because it's these uh fast bus top corners that are quite close to each other that are coming on to a long Corner following but you can see nonetheless that the braking technique difference between those two drivers is really different also the way if we look back up to the exit of the corner so the White driver here has lost a whole lot of time on Corner entry and by the time they start settling into this corner and they're coming back onto the throttle uh they're doing that quite a lot later and we also see uh this is a this particular corner is a long 180 degree corner and we can see the driver with that's driving with the white lines is really stabbing quite aggressively on on the throttle so as they're going through that corner they're realizing that uh they're too slow in the corner they know it we've probably already talked about it in a previous session that they've got it in their head that they're trying to work on that but they're giving these stabbed on the throttle and this is really not a great approach you'll often see a lot of unsteadiness throughout the throughout the section of both the drivers there's a lot of unsteadiness on the pedal there's always bumps in the track it's you're never able to be perfectly smooth on on the pedals but these these stabs we're seeing here these like these positions here and here and and this one as well these are a really bad sign in terms of uh unsettling the car so if the car was actually closer to the Limit if he was driving it in a way more like the color driver here uh that would be almost certainly unsettling the car enough uh to cause it to lose control so that's uh straight away a technique problem we see in the car now if we Zoom back out to the whole lap and we'll bring up our variants Channel again just to make the point so we've got this uh section up here we want to analyze we've got this relatively steep dip now if I'll just zoom back in here so there's a couple of obvious things going on here and the differences in the speed Trace we can see in this particular part of the track and I can actually bring up a track map for you to make it a bit more obvious so this is uh the car is coming up and uh going through this fast left-hand Corner which is happening up at this point up here we can see as I move the cursor the Little Dot moves on the track map there in this case the color driver is staying on the throttle which is shown and this is the part I'm looking at here it's staying on the throttle much longer whereas the White driver is completely lifting off the throttle and coasting through the Section this is something you'll often see in the difference particularly in high speed Corners between two drivers are quite different skill levels you've got one driver that's quite scared and is lifting off the throttle and the other driver which is getting back staying on Full Throttle longer and as a result that's why we see this big big difference in the in the speed Trace here which again if I bring the variance back in uh we can see that's the start point where these two speed traces start to diverge is the point where the variant starts to creep up as well so that is a really basic uh look through of the uh sorry a really basic look through of the um how you would go through do a driver analysis uh using some log data that's it where I'm going to leave it here for the lesson part of today's webinar there's we will be coming back and doing some more uh the next following webinars after this are going to also be a motorsport data analysis but for now I'm going to jump across to the uh questions and I'll start going through some of those one thing to remember is that we've got our courses uh so as I mentioned before we've got our Advanced Data analysis course coming out soon if you guys haven't if you're not already looking at our introduction or our data analysis fundamentals course which covers a lot of what I've gone through today but also a whole lot more a lot of detail about choosing loggers a lot of detail about driver analysis how to set up and configure your loggers and a really great six step process to help help you work through that if you're not if you're interested in this stuff you should definitely go check that out if you're not already on that course and remember also if you are a gold a racecraft gold member if you're not watching this live you can always jump across to our Forum if you've got questions that have come up from watching today's video you can also always jump onto the Forum and I'll be there answering questions along with a whole lot of other experts and uh the rest of our racecraft community so I will jump across now to the questions and answers and see what we've got what you guys have asked okay so Jackson has asked could you please recover the difference between the time and distance plot okay yeah so what Jackson's asking there is talking about when I describe the difference between looking at a time scale or a distance scale along a timing a time distance axis so if we're looking at on a time scale it's measuring the position of the cursors that I'm looking at at that position on track it's looking at how long into that lap something occurred so it's a time since we passed the last let Beacon or we started the this current let if I look at it on a distance scale is how far the car has gone so quite a lot or most of the time in uh performance when we're looking at performance aspects whether it's to do with chassis performance or whether it's do with the way the driver's driving the car we're almost always looking at things from a distance perspective we want to compare what the driver was doing at that position on track compared to the other driver we're not uh usually interested so much in the time because there's always a time difference between them and because those two events happened at different a different time into the lap not a different distance it makes it much more difficult to Overlay things and get anything useful out of it so when it comes to Performance aspects uh you're almost always looking at a distance scale I would say um have a have a play around if you can get a chance to play around with some data analysis software most of the manufacturers of data analysis systems give away this software for free and it's usually pretty easy to get some example data either from the manufacturer themselves or that you can find online and have a play around with yourself that's the best way to really get a good handle on that I know that when people are starting out with Motorsport data analysis sometimes it can be a little bit confusing and just actually playing around with the data yourself and flicking between the time and distance scales is the best way to understand that for yourself okay miles is asking is damping analysis a part of the fundamentals course no miles we don't actually well we do discuss uh yeah let me Backtrack on that little a damper analysis is discussed in the fundamentals course as far as talking about an introduction to it saying uh the damper potentiometers this is how they work this is why we use them but we don't really dive into any of the analysis on that that saved for the advanced course where we really get into using that stuff for understanding uh it's definitely I guess the reason we're saving it for I should say first the reason we're saving for the advanced course it's not typically a sensor that you are using for uh at when you're an entry level maybe you've just bought your first logger or you're just doing a casual bit of racing on the weekend you don't typically have uh damp sensors on the car it's a lot more overhead it's a lot more expensive it's a bit more overhead involved with setting them up and calibrating them and stuff it's not something you tend to have at the entry level but as you're moving on and want to understand more things about both your damping and your chassis and your ride height it's a really useful thing the advanced course goes through uh actual like damping histograms understanding bump and rebound settings the implications it's going to have on the car how you can use the damper position sensors to understand suspension stiffness differences and they expect what you expect to see based on different adjustments to the car so there's quite a lot of information that's going to be going in the advanced course it's not the fundamentals course because we don't think it fits very well with the people that are just sort of starting out in their analysis Flynn has asked how do you deal with pit stops affecting the Channel reports when they're giving you bad values yeah so what Flynn's asking there is so when we went through those channel the channel report example I did in the webinar it's uh you've got these sections of data where you might have a minimum let's say you might have a minimum oil pressure now if that minimum oil pressure happens during a pit stop because let's say the engine is Switched Off during the pit stop then that's going to give you an erroneous value let's say if the engine Switched Off obviously you're going to have zero oil pressure the sensor's value dropped to zero when you're scanning through that channel report obviously the minimum value you're going to have throughout that log file is a zero we don't care that it's we've had a zero during the pit stop we're interested in the minimum position the minimum oil pressure that we've had somewhere on track so there's lots of ways you can deal with that whether it's dealing there's some different analysis systems have different ways of what we call cleansing the data so looking and one of the ways that motec does it is they call them untrusted laps so laps whether they're either been a lot slower than the fastest lap time or where you've clearly entered the pit lane or something like that these are often what we refer to as untrusted laps we don't want to usually for some cases we don't want to include them in all of our analysis so you can use the algorithms built into the software to help cleanse that out which in that case would mean it would ignore the oil pressure when the car was in the pit Lane only look at when the car was on track and that way the highlighting function that we've got in the channel report would come back into play and be useful for us now that little blue Highlight is going to show us the minimum oil pressure we had on track rather than the pit Lane because in the pit Lane we don't care about it we just want we actually want to look at what the minimum was on track the other way to deal with that is by using math channels so you can cleanse the data with your own custom conditions whether it's by looking at when the car is in the pit lane or only within sometimes you're only interested in elect within a certain percentage of your fastest lap or whatever it is you've got an enormous capability to customize the channels and then you can take this customized Channel customized channels that you you've defined with math and report on those rather than the log channels and that's something we'll get into in some of the future members webinars going through how to define some of those math channels and how you can make the best use of them so hopefully that answered your question Flynn Elijah could you clarify the difference between logged and Telemetry data yeah no problem uh so the difference between uh Elijah's asking the difference between logged and Telemetry data log data is what we have when we we've got our actual logger in the car uh this is recording every sensor that's writing to this whether it's physically connected to it with a wire or whether it's getting to over a can bus everything that the is going inside the log is being recorded inside its little chip inside and when the car comes into the pit Lane we usually take a download cable and plug into it and we pull all of the data from that the last since the last time the car was run on track will be uploaded to a laptop or our server or whatever system you've got on track so that's the log data uh the Telemetry data and the convention for describing in Motorsport and the Motorsport context is that the Telemetry data is coming live either over a radio frequency or often these days over the cellularly network so the 4G or I'm sure in the future the 5G Network so that means you've it's as simple as having essentially like a modem a cellular modem in the car and a cellular modem in the pits and you've got live data coming from the car back to your that you can watch on track sorry you can watch on your screen live as the car moves around the track so often you're looking at uh reliability stuff you're definitely looking at some performance stuff so you can do live driver coaching by doing live overlays with what's happening on track at the moment compared to what uh your fastest slap odds or any other lap that you're interested in so you can coach the driver through whether it's settings on the car or driving technique you can also uh you're obviously always looking out for reliability issues and settings on the cars that using the Telemetry the the stuff that you're sending over Telemetry and the stuff that you're logging inside the logger it's actually all the same data the source of it's all the same it's all coming from the same sensors on the cars usually the biggest difference is the stuff we're sending over Telemetry is usually a bit more stripped down so typically we don't tend to send everything that's being sent from that's being recorded by the logger over Telemetry as well we're usually only sending uh the bare minimum that we know we're going to need during the race and usually we're sending that stuff at a much lower frequency and the reason is you usually bandwidth limited so regardless of whether you're using cellular cellular or radio frequency to send that data over Telemetry there's always a limit on the bandwidth there's only so much there's only so much bandwidth you can use I think as we see uh Motorsport 5G tiliency come on board that may well change the the potential difference particularly attracts with good coverage we may well see uh us being able to see send full a full set of equivalent log data over Telemetry and it may even get to the point where we don't even need to download the cars because we're able to get it all real time and able to use that for our analysis without without even needing the log data it's probably probably still a wee while away from being exactly at that because often race tracks are at places where you don't necessarily necessarily have great coverage obviously uh there's still going to be value for a long time and plugging into the car and getting that really high frequency high quality data but I think we will see start to send Evolution as 5G coverage rolls out and as it becomes uh more available at race circuits I think we'll get to the position whether to limit the difference between the Telemetry and the log data will be almost indistinguishable Jason is asking uh can you talk about some typical screen layouts for data analysis yeah sure no problem Jason so if I uh head back over to my laptop screen here so what Jason's asking is how do you lay out your data analysis uh package I've only gone through really today I've only really gone through the time distance plot and channel report I haven't really gotten to any other displays I'll definitely be going into that in a future webinar diving into the different types of displays we've got but if I've got an example here of a typical display that I would use myself during a race weekend if I just get back out to a full lap View so obviously we've got our time distance plot that we're already familiar with we've got our track map here so as I move throughout the lap we've got the cursor moving around the track which just helps us orientate where we are on track in this particular situation I've got my tire pressures showing up here as well so I can track how those are evolving throughout the race and throughout the lap I've got some basic stuff about car settings whether it's about whether the pit limit is on the rain lights on if the radio is being switched on or off which can be a good diagnosis thing if you're having Communications with your driver you can see if they're flicking the radio button on and off got our traction control ABS settings some basic reliability stuff so engine oil temperatures pressures fuel pressure stuff like that and this is a typical layout that I would have when I was watching the Telemetry live obviously if I'm going through post session I'll be looking at lateral longitudinal GeForce diagrams I'll be looking at the tire pressures in more detail we'll go through all that stuff more in future webinars but there's an enormous amount there's lots of different ways you can lay out your Telemetry or your log data but this is typically how I look at it there's also a couple of extra channels that we've got showing on here if I just press so if I bring up the legend it'll just make a little more obvious what we've got here so these are all obviously color coded I've got engine RPM the speed that we already looked through I've got a setting for when the traction control is active I've got the throttle and the brake overlaid with each other which I like to do because usually only using the throttle or the brake once at a time you're not usually using not usually using both the advantage in that if I overlay them allows me to save some screen space and I can make all of the other displays a little bit bigger as a result which I find an advantage to see more detail I've got some information about brake bias here so I'm looking often in Motorsport you've got the option to change the brake price on the go in the car so that just gives me a way to compare the different brake biases the drivers were using we've got our steering input here and our gears like zeko like we had when we went through the example before so that's how a typical way of how I have made Telemetry laid out in future webinars will go through some different layouts for more for different types of particularly chassis analysis so we've got our last question here from will what are your thoughts on the aim solo 2 DL so yeah the aim solo is a a great little product it's something that's uh more or less what I was describing at the top of the show talking about uh really basic more entry level loggers so that's something uh it's a it's a little self-contained unit it's got a little screen on the front of it it's got the ability to not only act as a lap timer and give you that time Delta so that that variance plot that we looked at at time Delta or time variance plot that we looked at uh during some of that analysis I was going through that data is also available live to the driver so that's something I really should have talked about earlier on as well where you've got the ability to see whether you're doing better or worse than the reference laptop and rather than being shown as a plot like we had in the time variants it's being shown as a number so whether you're above or under the number anyone who's done a little bit of sim racing whether it's on eye racing or a set of Corsa or something like that will probably already be familiar with the concept of the time variants you can see whether you're gaining or losing time relative to your fastest time it's the same idea that's able to be shown on something like the aim solo that's a really great Advantage a really great driving tool uh you also have the ability on the DL model to input vehicle data so in the in the in addition to having all of that awesome online on log data you've already got within but inbuilt accelerometer and the time distance plots all about stuff you can do you can also uh if you've got the ability to pull it out of your car from the can bus you can also do uh the accelerator and Brake and steering or anything else you've got available uh depending on your car and what's available so it's definitely a lot of a really great value for money as far as an entry level kit it's really overhead to fit and maintain uh it's definitely one of those units that's a great entry level unit so guys that's all I've got for today's uh there's no more questions there so that's all I've got for today's uh webinar there are some really great questions there uh I hope you guys learned a lot out of it and I will see you guys in the next webinar which will also be on data analysis where we will dig in a little further thanks guys that was just a toast of what we put on every week for our HPA Gold members our Gold members are able to watch these live and ask questions and get answers while we're presenting after the webinars have been hosted live they're added into our webinar archive where our Gold members can re-watch them at their Leisure we've currently got over 240 hours of existing webinar content covering topics on engine building engine tuning and wiring this is one of the fastest ways to expand your knowledge on a wide range of topics as well as to stay up to date with the latest tools Trends and techniques in the performance industry our goal members also get access to our private members only Forum which is the best place to get fast answers to your specific questions gold membership can be purchased for just 19 US dollars per month however you'll also receive three months of free access with the purchase of any of our courses click the link in the description to learn more