My goal
I want to build a device that shows the forces I’m experiencing now and the highest forces I’ve reached in each driving direction. I want to see acceleration, braking, and cornering on one gauge so I can understand what the car is doing during a run.
From there, I want to validate the device’s motion sensor, called an inertial measurement unit (IMU), by comparing its readings with my car’s IMU data recorded during the same run. I want to understand where the readings agree, where they differ, and whether I can use that comparison to improve the data from my device.
Once I understand its accuracy, I want to start logging runs. I see this as the first of several custom devices I want to build around my car’s performance. My next direction would be connecting through the car’s OBD-II port to build more gauges, record more data, and learn how its performance changes under different conditions.
Current progress
The basic hardware checks are complete, and I’ve been working on the gauge display. A separate firmware version is prepared for a directional peak-history outline, button controls, microSD recording, and wireless CSV downloads. That version still needs testing on the device.
The same-run comparison with the car’s IMU is planned, and the device’s measurement accuracy has not yet been established. The logging features are prepared in code; collecting validated performance data is still ahead.
Casing iterations
Casing photos and notes on what changed between versions will go here.
Planned next steps
- Refine the enclosure and the display of current and peak forces.
- Record the device and car IMU during the same run, then align the recordings for comparison.
- Use the differences to decide what to improve in my device, then repeat the comparison.
- Once I understand the accuracy, test run logging and check that the saved recordings are complete.
- Explore an OBD-II connection for additional gauges and performance data.
Lessons learned
I’ll add lessons here as I work through the build and testing.