I'll explain my statement carefully then get on to your question. I don't find track maps particularly useful because they don't really tell you anything new. With GPS it's a bit better but otherwise, just a derivation from speed and lateral G's. I've always found G's valuable because it's one of the only measures we have of overall grip. It can indicate our overall cornering and braking forces, can be plotted into a rudimentary traction circle and, since making the kart go quicker is all about managing the forces on the kart, is often the only channel that records any type of force at all.
Regarding your question. With G sensors you have to be very careful. Most accelerometers, especially cheap and/or poorly configured ones are prone to high readings, especially at the peaks. Make sure to allow for this. I wouldn't bet my life on it but lower g's and quicker times could be indicative of many things:
1) Less aggressive, more precise inputs. A smoother driver. This will often show with lower peaks but a higher sustained lat G.
2) A better line through the corner. If you're finding sustained lat G's peaking at corner exit, you're probably looking at an early turn-in for example.
Plot revs/speed, lat g's and time difference (maths channel). The time difference will show whether you're gaining or losing time on the compared lap, throughout the lap. If you have it available, also plot steering position. You'll probably find that the quicker driver has smaller steering inputs, higher cornering speeds (pay close attention to corner exit speed) and lower peak but higher sustained G's.
As always though, it is really a case of "it depends". This is why dataloggers, combined with setup notes, track conditions and your own obesrvations are so valuable. You accumulate a lot of data that initially may seem useless but over time starts forming a much clearer picture of how to go quicker.
However, I cannot emphasise enough the importance of your own eyes and the stopwatch. If you can't get on the pace with just these, even if only for a session, then you're likely to get lost with data logging. Experience with data loggers can help, but only if you allow the logger do it's work (log data) and put aside any preconceptions about what "quick data" looks like.
Dave
|
|