# Front Wheel Speed Sensor - Utilize Data gathered from the Kart

How or What are the points that can be analysed from the data gathered from a Front Wheel Speed Sensor?
Is there any guidance video or documentation on it?

Before the Mychron 5, wheel speed sensors were more common. With the built in GPS you can now easily get your MPH. I think most were looking at/for wheel lock up or slip. Unless you’re doing a deep dive on data analysis or don’t have a Mychron 5 wheel speed sensors probably aren’t necessary.

If you REALLY want to geek out, there’s some talk about speed sensors in this topic. GPS has it’s merits, but wheel speed still has a place, depending how deep you want to go.

Hi Morgan,

Interesting thread on gps. I would venture to say the accuracy is within inches relative to data points taken within a few seconds in either direction. The government intentionally makes gps slightly inaccurate, otherwise it would always be within inches. The inaccuracy they impose is accurate relative to other readings within a few minutes. So you may notice some slight inaccuracies from one run to the next. But data points within a single run should be perfectly accurate. Bottom line, all this will really screw up is if you try to overlay your run over a google map image. If you are simply looking at data it is perfectly accurate for your run. If it was even close to being meters off the data would be 100% useless and would not be represented by smooth curves.

Putting a wheel speed sensor on the front can get you some better info on vehicle speed than your GPS, but you’ll need to write a math channel first. You need one math channel calculating corner radius, and a second one that calculates the vehicle’s speed at the centerline while accounting for the changing radius of the corners on the track. This is because your measured wheel speed will always go higher when the sensor is on the outside and lower when the sensor is on the inside of the turn.

With your corrected centerline vehicle speed math channel you can either lay the RPM trace directly over the top to see wheel spin, or you can create a math channel that takes the corrected vehicle speed and divides it by (RPM / 1000). This outputs a number that is constant under zero slip, decreases during wheel spin, and increases during under rotation.

That hasn’t been in use since 2007 says https://www.gps.gov/systems/gps/modernization/sa/

I am referring to how the signal can be intentionally degraded. I know its published that it no longer is degraded but the whole point of it was national security so i really doubt its still not degraded. The system is very accurate so something is being done to make it as much as 25’ off. The important takeaway is that the data points are very accurate relative to each other but the entire data set or session from one day might be several meters off from another day.

I disagree, it may be dependent on location or system but certainly with the mychron 5 i’ve had the privilege to work with top drivers in X30 or Rotax and there is no way they are 3ft different in raceline from lap to lap.

Given the choice I’d prefer a ebox with with g sensors and wheel speed sensors. Ricky Flynn Motorsport (one of the top teams in Europe) still use out of production PI dataloggers (that never had GPS, and I have no idea how he gets them) and Tonykart use their Dakton datalogger which has never had GPS.

@Stealth
It depends on what you are trying to find. You can use two wheel speed sensors, one on back and one on the front, to determine if your rear wheels are slipping more then they should be (you should be aiming for about 8% to get optimum acceleration or braking grip) or you can use rear wheel speed vs engine speed to determine clutch slip. Alternatively if you are running shifter you could have two front wheel speed sensors to determine braking performance across the front.

1 Like