Rocketjunkie
Addicted to APCP
- Joined
- Jan 19, 2009
- Messages
- 5,394
- Reaction score
- 1,724
Last weekend, I used a Perfectflite MAWD for controlling deployment in my rockets.
On Saturday, I launched my Motoreater on a K550. Deployment and recovery were normal, the altimeter was beeping out 4031 feet on recovery. That evening, I downloaded the data to my laptop. Everything was normal - until the results came up on the screen. The peak altitude was only 1700 feet. Looking back, this was the data from the previous flight of the altimeter (in August - Cyclotron on I200).
I thought this was a fluke and flew the altimeter again in my Cyclotron on an I300. Due to error on my part, the rocket suffered an extremely hard landing (RIP). However, the altimeter checked out OK. I then flew it in my upscale Deuce on J420's. Again, deployment and recovery were nominal. This time the altimeter was beeping out 2032 feet. Downloading proved that the August data was still there.
Any explanation?
This altimeter had given 6 previous flights with good data downloads before this.
On Saturday, I launched my Motoreater on a K550. Deployment and recovery were normal, the altimeter was beeping out 4031 feet on recovery. That evening, I downloaded the data to my laptop. Everything was normal - until the results came up on the screen. The peak altitude was only 1700 feet. Looking back, this was the data from the previous flight of the altimeter (in August - Cyclotron on I200).
I thought this was a fluke and flew the altimeter again in my Cyclotron on an I300. Due to error on my part, the rocket suffered an extremely hard landing (RIP). However, the altimeter checked out OK. I then flew it in my upscale Deuce on J420's. Again, deployment and recovery were nominal. This time the altimeter was beeping out 2032 feet. Downloading proved that the August data was still there.
Any explanation?
This altimeter had given 6 previous flights with good data downloads before this.