@Charles_McG The VAccel data looks pretty good: Booster motor burnout at ~1.8 s, coast to ~3 s, and then sustainer motor lit at ~3 s for a short 1 s burn. The FAlt appears to have a few hiccups (surely the rocket wasn't falling at any points between 2 and 5 s), but maxes out nicely around 1800 ft. The FVeloc, on the other hand, is all over the place. What do you make of it?
I'm waiting to hear from
@cerving about some of the data calculated from the accelerometer.
I thought the accelerometer captured the motor profiles beautifully - though to be precise, you'd have to back out the drag.
I have found the Quantum to be sensitive to events, and the Proton looks the same. It looks like I'm not adequately shielding the avbay from pressure changes at the bottom of the rocket.
If you blow up my graphs, I overlaid various events with markers at the altitude. VMax (booster burnout) is at 1.48s. The discontinuities in FilterAltitude (FAlt) are mostly at Channel2 (2.36s, separation charge, programmed for 2.0s), Channel1 (2.76s, sustainer ignition, programmed for 2.4s) and the sustainer motor burnout. This was a G78 BlueStreak to E22 SmokeySam. The little E22 was nicely visible, but barely made it above the drag at ignition. Doesn't bode well for my planned G115 to F10 flight
The free fall acceleration looks reasonable -34fpss.
The OR sim acceleration looks just like this graph - very fun. OR predicted about 1900'. I got about 1740'. OR predicted staging at about 500', the flight data says about 800'. So the booster overperformed and the sustainer underperformed.
My main concern is the VelocityfromAccelerometer (VAccel). It just plain looks low to me - and it makes the AltitudefromAccelerometer (AltAccel) bend over and head down well before the baro data - in the part of the flight I'd trust the baro the most. I played with the data in Excel and tweaking the VAccel fixes the AltAccel. I haven't double-checked to see if I had the Baro/Accel crosscheck on, but if this is typical, it would need to be a wide window.
I had some trouble on the pad with the Proton, but figured out with about 4 tries. I would do the horizontal calibration, put the the rocket upright and then refresh the iPhone browser to see the vertical reading. And it would recalibrate and send the reading to 0. (Should be 1.) My workaround was to go to setting and back. That would show me the current value without accidently triggering an improper calibration.