Data Logger with Web Interface
 

Hello guys :)

INTRO TO THE PROJECT
I wanted to share with you the current state of my data logger project with its web interface. I know there are other projects like this on this forum or the test logger but I wanted to make my own version. I wanted a way to record and see the data without the need to bring a laptop to the track. So I made this ESP32-based data logger and a web processor / interface that can display the data of the runs in a clear way. And since it's web-based, you can see your data on your phone, tablet or laptop/desk computer.

HARDWARE
So here is the latest version of the data logger. There will be a post below with earlier development versions.
The data logger and SD card holder with a Yokomo wrench. Driver input (steering and throttle/brake) and motor sensor wires. No accelerometers / gyros plugged.
https://images2.imgbox.com/9d/04/oDMsU11M_o.png

The car fully equipped during a club race. Two accelerometers / gyros front and back. The Y harness plugged in the receiver takes too much space. I'll figure something to make it less messy.
https://images2.imgbox.com/38/33/B1Yu8CqM_o.png

https://images2.imgbox.com/87/9b/y5I6oTbm_o.png

CHANNELS
The currently recorded channels are:

• Throttle / Brake
• Steering
• Motor RPM
• Accelerometer X, Y and Z x2
• Gyro Gx, Gy and Gz x2

Current sampling frequency is 400Hz. I find that's it's enough to capture everything with enough fidelity without making the recorded datafile unecessarly big.

The currently inferred / maths channels are:

• Vehicle speed
• Understeer / Oversteer
• Corner Radius
• Steering Speed
• Attitude
• Understeer Angle
• Difference of Lateral acceleration (Front vs Rear)

Future recorded channels could include:

• Tire temperature x4 (already have the sensor and tried it on a previous version)
• Time of flight / ride height sensor
• Damper Pot / Suspension travel sensor

INTERFACE
And now, some screenshots of the web interface and its different features:

0. Here is the frontpage. It's where you drag and drop your recorded data file. You can input the final gear ratio of you car. It will be useful to compute your car's speed. You can also select in which way you run on you track and your average laptime of your session. This will be useful for later :)
https://images2.imgbox.com/0e/cc/JxA476E3_o.png


1. You can see the effect of the filter on each recorded channels.https://images2.imgbox.com/3c/18/lnyGdGYL_o.png

2. Now, let's focus on the data processing part. The web interface automatically detect the window of time where you were actually driving, not when the car is turned "on" in the stands, or sitting at the border of the track. This way, it only keeps and analyze the relevant part of what is recorded.
https://images2.imgbox.com/a2/2f/dAAHInsP_o.png

3. The interface will detect periodicity in your recorded data. In other words, without the need for any track beacon set at the side of the track the algorithm is able to detect laptimes in your recorded channels.
https://images2.imgbox.com/53/00/4y2M3tbu_o.png

Here is a comparison I made on Excel of the actual lap times by a genuine MyLaps RC4 timing system (left column) and the laptimes found by the web interface (for a previous session). The results : less than 1% of error. Maybe it's not precise enough to be a timing system on its own but at least your clearly know which lap is which and it's pretty close to the real thing. I'm pretty proud of that results NGL. It only took 5 different version of the lap detection algorithm. :)
https://images2.imgbox.com/d0/9d/jYupWGoq_o.png


4. The interface will then display a list of the laps it found:
https://images2.imgbox.com/de/7a/16PQ295N_o.png

5. Now that we have our laps, let's draw the circuit ! You can color the trajectory with the channel of you choice, and select the lap you want to see.
https://images2.imgbox.com/0b/8a/Wp0MB5i8_o.png


And for the selected lap, you can see you throttle/brake and speed as well as the steering and lateral acceleration. Here it's pretty smoothed-out because the average lap is selected.
https://images2.imgbox.com/a6/df/Wba8pKTJ_o.png


6. You can overlay two channels to see them for the lap you chose:
https://images2.imgbox.com/be/52/J1yZDGoH_o.png


7. You can see the G-Force (G-G) chart of your run. You can also color it with the channel you want.
https://images2.imgbox.com/8d/b3/8NAKGwJc_o.png


8. Here you can compare a channel on two different laps. You can see the time delta (where you gained or lost time) for the two laps compared. There is a slider to offset and superpose the two laps at anypoint you want on the track (for example at the start of corner 4).
https://images2.imgbox.com/6a/f6/Wg3Z2YJ1_o.png


This is my first coding project I'm pretty new to this. I've been at work on this for the past few months, I hope you'll like it. I posted it on the on-road section because this is my main and only class I run and I wanted the opinion of the guys I read the most.

Thank you for reading all the way and feel free to tell me what you think of this. If there is enough interest I could make this available to everyone in a commercial version of the project.

PREVIOUS VERSIONS / development boards

v1 [2019]: First ever version was a full size arduino UNO directly bolted to the trunk part of my body-shell. :lol:


v2 [AUGUST 2021]: Second version based on a TEENSY 4.1. Faster logging rates, 1 Accelerometer and Gyro. Tire temperature sensor.
https://images2.imgbox.com/7c/26/K3fZXyuH_o.png


v3 [OCT 2024] : Third version. TEENSY 4.1, better internal code, better accelerometer/gyro and messier wiring. Also, motor RPM logging added.
https://images2.imgbox.com/a5/eb/N5G4WwvL_o.png

v4 [DEC 2024] : Current version (first post). ESP32-S3. 2 Accelerometers / Gyro. RPMs and Driver Input.
https://images2.imgbox.com/9d/04/oDMsU11M_o.png

Looking good, I'll be following this.

Wow that is really impressive! Especially recognising laps from noisy data. Well done, and I am sure in the right hands this will be really a help to improve one's driving. I love data driven analysis, and this is really cool.
For a project where I have different data with different sampling frequency and time offset, I would need similar code. What's the basis for yours? Did you use some kind of library?
Sad I didn't meet you at Axxelerate Arena. Where will you drive outdoor? I'll be mostly in Dintikon AG.

Thank you! For the architecture of my code : I made a backend (Python for now, it could maybe be faster with another programming language) for the heavy processing and a frontend (CSS JS HTML). I use several libraries such as numpy, scipy and mathplotlib. I really recommend them to you they are super useful! I don't really have a track outdoor as of now (it closed down). I mostly run indoors now at IRCR (near Lausanne).

Really like this project! I've been wanting to do something like this so I could get some accelerometer data off of my cars, partly just out of curiosity, but I don't know very much about coding and this even goes above and beyond what I originally thinking of. Would love to give this a go myself if you're ever willing to share the code and material list needed.

I like it! It is always great seeing others coming up with fun projects. Of course now two people have their data loggers, guess that means I don't have to make mine anymore.

I like it too, but there's always room for more :)

Love all the analysis you're doing in the web interface. Would like to see the track map function and the lap comparison combined. Seems it would be a much easier visualization to figure out where on the track you're loosing time.

Look at this RaceBox Micro - DIY GPS Data for the Driven by Race Box — Kickstarter

As far as I could see. the Race Box Micro doesn't log driver inputs, does it?

Andi

No direct inputs but due a precise GPS location sensor it can give you all movements of the car and calculate speed.

This project looks super amazing, seems like it would open a whole new world for RC racing comparing racing lines and data analysis!

You finally could tell with certainty in which corners you win or loose and if a changed setup is quicker and in which part of a corner...

Would personally be interested in a commercial version

UPDATE

Hi, I wanted to share a little update on the interface.

1. To save time and going back and forth, you can now view and change the lap's start/finish line position during the file analysis with the help of a little map of the track.
https://images2.imgbox.com/1e/03/AcJYIugR_o.png

2.You can now compare two runs on a dedicated page.
https://images2.imgbox.com/0a/21/nHyLQEEd_o.png

Like the Celero TS1 from Motonica in 2012 Roelof you had a telemetry system designed too, correct?