jvp

Sean gave me a set of his AIM Solo data from one of his Summit Point runs last year. I took a few laps and, using RaceRender, overlaid it on top of another one of my drives. What you'll watch here may cause a bit of a disconnect: it's my drive to a restaurant, while I use Sean's data as an overlay. Don't pay attention to the actual drive, more the layout of the stuff. Specifically the data and the rear view camera.


The more I work with the PDR camera, the less I like it. Scaling it up to 1080p/60 FPS just looks cruddy compared to the GoPro Session 4's native 1080p/60 FPS. And of course that's what you'd expect: creating frames out of nothing. But, what do folks think of the data presentation and layout?

And no, I can't drive Summit as fast as Sean. But this does give me an idea.... >;-)

Michael A

I like the layout. How are you getting the braking information? Is it just coming from the GPS, or is there some sort of brake signal coming in?

I still have yet to see a G-meter as good as the PDR on any of these systems. The PDR G-meter is nice and large, and is very stable.

Michael

jvp

Thanks. I'm working on improving the template even further. Here's a screen shot of what I have so far:



The brake data is coming via the ODB2 port; the AIM sees it as "BRK_PRES_SMO". It's not perfect, but close enough to represent the driver pressing on the brake pedal.

The display of the G-meter can be done in any sort of way the software you're using allows. RaceRender (what I'm using) has a ton of different G-meters. The data itself is a bit tougher because the device gathering it isn't as tightly connected physically to the car as the car's built-in sensor. So little bumps or whatever can throw the sensor off.

Poor-sha

The aim data should have both the car's G sensor data and the internal sensor from the unit. I don't know if I trust the car sensors either though as they read really high.

jvp

I couldn't find the longitudinal sensor reading, just the lateral. Perhaps it's named differently.