OK then, collecting data is one end goal of what you’re doing, learning what to collect and how being another. The question is then what data should you be collecting ? What is it you need to know to make a perfect jump or to diagnose the jump you just had the car do ? I’ll start (as a given) you’ll want the position of the car at various moments in time and the orientation (where the car is “pointing” in pitch, yaw and roll) of the car at those times as well. If you were going to make an animation of what the car did, you certainly need those data items. Other related data items (ie - speed and acceleration of the car) might be collected as well, or deduced from the aforementioned.
Since you’ve ruled out video capture as a method to know the car’s position and I’ll rule out GPS as an alternative (too inaccurate, too expensive), what are you left with ? I suppose other, external to the car, methods could be proposed but I think you’re stuck on in-car measurements so let me suggest a wheel sensor to start with. You sense the rotation of the wheel, perhaps the easiest way is to count each rotation of the wheel. If the wheel doesn’t spin, you’ve got a direct measurement of how far the car has travelled from the start line. If you assume the car travels in a straight line you’ve also go it’s position vs time and thus it’s speed and acceleration vs time. You don’t have it’s orientation but while it’s still on the ground I suspect that doesn’t matter.
So all is good (at first glance) until you get into the air. At that point the wheel sensor doesn’t tell you much in the way of useful info. Given the speed of the car and geometry of the jump ramp and a good model of the car, I could tell you where the car went and it’s orientation because at that point the car is in freefall, following a ballistic trajectory (at the expected speeds I think we can safely ignore air drag). But if you don’t have that good a model for the car, say all you have is it’s weight, then you might want to supplement that prediction with some measurements. I’ll negate the possibility of some in-car radar ( :mrgreen: ) to measure distance to the ground and assume you’ll want some inertial measurements that you can use to estimate the cars position and orientation while “in flight”. Given the car is in freefall a 3 axis accelerometer, used as a tilt sensor (Google it), won’t give you a direct measurement of the orientation. You’ll need use gyros to measure the rate at which any orientation change occurs but I’ll opine this will be hard to make accurate in your usage. That said you can get both 3 axis accels and gyros and see what both say. I’ll assume that the car is electric and so adding a compass or magnetometer is probably useless.
So you need to decide what the expected range of these data items are; how fast can the car go, how much acceleration can it have, how quickly can it rotate, so you can decide on what sensors are best suited to your application. I think an accelerometer than peaks at +/- 2Gs is about right and I don’t know what to say re: a gyro except that I’d expect low rotation rates, so a gyro that can handle 2000 deg/sec will probably have too little resolution.
Then you need to figure out how often the data must be collected. How many samples/second of each data item is needed to reconstruct the path/jump and meet some TBD accuracy requirement. This, along with the resolution of the sensors, will figure into the data rate (bits/second) that you must either transmit or record. This will also play into what flavor Arduino is best to use. Or perhaps you can find an IMU that has, in a single package, the gyros and accels and a microcontroller that you can program to do all you need to do.
With the sensors all chosen, you can determine how to pack the data into a single serial stream, to be sent to either an RF link or perhaps to an onboard data logger. In fact if you do the latter, you might be able to forgoe any data manipulation. You need to decide whether onboard collection (and post jump reduction) is sufficient for your needs (and budget). I suspect it’s both easier to do and less $$s than to do an RF link of some sort.