I have been busy editing the video footage from Oulton Park and uploading it to YouTube.
We have now done quite a few track days and you would think that I have things worked out well to video track sessions and use the data collected - but no it is a mess.
I have a coupe of GoPros, one for the front and one for the rear. These work well and only rarely do I forget to turn the camera on. I have a third GoPro which now comes along to track days as spare camera incase there are any issues with SD cards or the camera just decides not to work. I always have a few spare batteries but the cameras are powered from cables in to the 12v socket so when the engine is running the camera batteries get charged. The video part of things is all good.
I use Race Render to put the video and the other data together. To make the videos more interesting it is always nice to see some useful data, that way you can get an idea of what speed the car is doing, and whether it is accelerating or braking. This is the issue that has been bugging me for the past year.
I started out recording track days with a GoPro and Harry's Lap Timer on my phone. It worked well when it worked but every now and then Harry's Lap Timer would crap out and miss laps, or a session, or the GPS would go wild and not record the car moving round the track. I had used a cheap OBD2 adapter to get some data from the car with this set up. I thought I would try something else as this set up was not working.
Then I found out about RaceBox and bought a RaceBox mini. This is a standalone GPS box that records the GPS data from a track session and is super accurate, but it does not interface with car data available from the OBD2 port. RaceBox is great and I am now used to comparing track sessions that I do with Ethan on the RaceBox phone app to see where he has braked or carried more speed through corners. It is a really useful gadget with a very good app. The downside to the RaceBox hardware and app is that it does not pull any data from the car and cannot interface with the OBD2 port.
When RaceBox brought out some new hardware I bought their RaceBox Mini S. It is a box that you connect to with your phone and tell it to record track sessions, then you disconnect and it will just keep recording when it notices you are on track. You do not need to prompt it to record each time you go out and it is sensible enough to know when you are just sat in the paddock. It can record up to 2 hours worth of track time - time in the paddock does not count towards this 2 hour time limit. So after a few sessions I can use the phone app to connect to it and download the track data, tell it to watch out for any more track sessions, then disconnect from the RaceBox Mini S. The phone does not need to be connected to the RaceBox Mini S all the time.
I got a more expensive OBD2 earlier this year, a OBDLinkMX+. It is a bluetooth device that pulls data from the car's CAN network. The CAN network is limited but can provide essential data like speed, RPM, throttle position, selected gears. The CAN network does not provide any brake pedal data. I thought that a great track day set up would be:
- Use the RaceBox Mini S to record the GPS data of each track session
- Use the RaceBox Mini to connect to Harry's Lap Timer for a fast and accurate GPS reading, in addition to using Harry's Lap Timer to read the OBD2 data from the CAN network
- Use the GoPro cameras to record the video
I tried this set up at Oulton. For reasons that I do not understand Harry's Lap Timer does not want to work with my phone. It sometimes records the GPS data, other times is does not get a GPS fix which is odd because when the RaceBox Mini hardware connects to the RaceBox app it has always been perfect. Also, on the data side of things it was very hit and miss when it would capture good consistent car data and when it would record some or have delayed data.
Some of the footage from Oulton Park has the video, GPS data and some of the OBD2 car data. Most of the footage is just video and GPS data. This is Ethan's best session in the car where you can see the GPS data but not any of the OBD2 data.
Track days are about having fun, but after the track day has ended I do like to look at the data.
I looked at the Track Addict app I do not think that it works with my OBD2 dongle. I could look at RaceChrono.
I have looked at some solutions but I think I might just use a really old app called DashCommand to pull the data from the CAN network, use the RaceBox Mini S to record the GPS data and keep on using the trusty GoPros for the video. DashCommand is very old but it can read a lot of data from the car including coolant temperature, inlet temperature in addition to gear selected, RPM.
With another trip to Snetterton in two weeks I will see if DashCommand is an improvement over Harry's Lap Timer.