Why the G-sensor samples on its own
G-force is genuinely useful on track: launch for acceleration, braking for deceleration, cornering for grip. Where the number comes from decides whether you can trust it.
Two Ways to Do It
Section titled “Two Ways to Do It”Read the car’s data. Use the acceleration values the factory computer puts out. The problem: an old ECU may not even have that channel, and on a car with a swapped or reflashed ECU the protocol may have changed.
A sensor of its own. A 3-axis MEMS accelerometer inside the cluster, sampling and calculating locally.
This cluster does the second one.
Three Things That Buys You
Section titled “Three Things That Buys You”- It just works. It doesn’t care whether the factory computer supports it. Modified cars are fine.
- It stays off the bus. The data never touches the vehicle protocol, so it adds no load to CAN and doesn’t compete with other devices for a channel.
- Stable rate. 100 Hz — a hundred readings a second, fast enough for the dot to keep up with real acceleration.
Choosing a Range
Section titled “Choosing a Range”| Range | Where it fits |
|---|---|
| ±2g | Street driving — normal acceleration and cornering |
| ±4g | Track, hard braking, high lateral load |
The smaller the range, the finer the resolution at the same acceleration. ±2g reads more smoothly on the street; switch to ±4g on track so it doesn’t clip.
What It Doesn’t Do
Section titled “What It Doesn’t Do”G-force here is display only. No lap timing, no logging. If you want lap analysis and data replay, that’s a separate recorder.
Better to say that up front than have someone buy it and find out they can’t export anything.
