Official word from Adreian: Loose connection in apogee wiring or ematch. The Raven lost continuity on the apogee channel at motor burn out then reacquired continuity when the main fired and subsequent high G event.
Solution: I'll fly this rocket on another altimeter and fly that suspect Raven in another rocket as a backup till it proves itself. Thankfully at this stage of the game I have multiples of each. But my goal was to keep one or two flight computers in each rocket.
Reset to stock configuration, do the baro deployment for apogee, select your main opening altitude. Could do the calibration process for the accelerometer but if using baro for deployments this might not be necessary. Might help if your looking at data off the accel though. Put ematches on the main and apogee channels and do a sacrificial test.
When done, fly in a beater rocket with a motor combo that's not going to send it too high. If it works, you're in business.
I will share I bought a new Raven one time and decided to use a carpenter's clamp to hold to large capacitor to the board while the epoxy dries. Clamp slipped, smacked the board and the altimeter function became intermittent. What I mean is have it running and give the board the tiniest of twist or torsion and it reset! Some component got whacked when the clamp slipped. Looking on with a high magnification
scanner revealed nothing that could be easily seen too. $155.00 down the toilet.
That said, I have an old Parrot altimeter that survived a ballistic flight and after replacing the onboard battery and testing it out, it technically looks good.
Flight was human error when one arm of the apogee ematch was incorrectly connected (ie. missed the hole). Main blew but harness broke. Charge tested 18 months later after it was returned to me and blew. (Landowner found it in 5 days so it didn't sit out in the field for that long and escaped the weather.)
Nonetheless, if I fly it, it's going into an armored "beater" rocket. Kurt