Embedded / 2026
Arduino Speed-Tracking Experiments
Exploratory work on speed measurement: processing personal run data into CSV files, trying Arduino-based tracking, and identifying possible test cases.
Context
The problem
Turn a broad interest in athlete monitoring into a test that can actually be run: choose the measurement, identify suitable sensors, and define what starts and stops a trial.
How it fits together
Architecture & approach
This is exploratory work related to the research story, not a second completed monitoring product. Sensor activation, test conditions, and validation guidelines are still being developed.
- QuestionSpeed / timing
- Sensor choiceUnder study
- Trial planIn development
- EvidenceEarly experiments
My contribution
What I worked on
- Created CSV files from personal run data.
- Experimented with tracking speed using Arduino.
- Used draft-combine 40-yard dash data to identify benchmark-based test cases and consider sensor activation and test conditions.
Technical choices
The choices behind the work
A benchmark time can help define a test case, but it cannot establish the accuracy of the device taking the measurement.
GPS, heart-rate, inertial, and infrared sensing are being studied for different roles. Identifying an appropriate sensor is separate from integrating and validating a complete system.
Looking back
Results & current status
Early experiments completed. Repeatable test procedures, sensor selection, and numerical validation are still in development.
Testing and evidence
A personal-run CSV workflow and an Arduino speed-tracking experiment have been carried out. A repeatable multi-sensor protocol, activation sequence, and numerical validation results are not complete.
What I learned & what comes next
Before adding more sensors, document one test end to end: start condition, stop condition, sensor activation, recorded fields, units, and a reference measurement. Those guidelines remain in development.
Keep exploring