Strong wind but nice skies. I went for it and launched. The rocket landed upwind about a mile, too much tilt on rail. That said, it was a beautiful launch.
All charges fired. Analysis looks like dual deployment code worked - drogue delayed (not sure by how much - yet), main right on mark. I now have a lot of data to review.
Added this to the main description, but put it as a comment so you see the update.
Summary:
Drogue deployment was delayed and fired within a tenth of a second of backup deployment (about 2 seconds late total). This was caused by me forgetting about the new Android power management sleep cycle. I have corrected my code so it will work properly next time.
When drogue deployed, it got stuck on a tail fin. This caused a high speed but stable descent between 100 to 114 mph.
During descent, the drogue freed itself, causing a temporary spike in velocity as it flipped around in free-fall before drogue inflated. This triggered my emergency curved max velocity based on altitude to act and deploy main at 2000 feet.
Overall, for a first flight, the results are promising. I should have caught the android power management issue with drogue during testing.
I have added additional sanity checks to my code as well, to reduce the chances of early deployment from odd atmospheric conditions.
Hopefully I'm able to test the updated version of my software at SRA this month, provided the weather cooperates.
Added this to the main description, but put it as a comment so you see the update.
Summary:
Drogue deployment was delayed and fired within a tenth of a second of backup deployment (about 2 seconds late total). This was caused by me forgetting about the new Android power management sleep cycle. I have corrected my code so it will work properly next time.
When drogue deployed, it got stuck on a tail fin. This caused a high speed but stable descent between 100 to 114 mph.
During descent, the drogue freed itself, causing a temporary spike in velocity as it flipped around in free-fall before drogue inflated. This triggered my emergency curved max velocity based on altitude to act and deploy main at 2000 feet.
Overall, for a first flight, the results are promising. I should have caught the android power management issue with drogue during testing.
I have added additional sanity checks to my code as well, to reduce the chances of early deployment from odd atmospheric conditions.
Hopefully I'm able to test the updated version of my software at SRA this month, provided the weather cooperates.
launch180210_114612_963.csv 
Comments
Good to see that it landed nice in an open field...
Hope to do analysis this weekend.
Added this to the main description, but put it as a comment so you see the update.
Summary:
Drogue deployment was delayed and fired within a tenth of a second of backup deployment (about 2 seconds late total). This was caused by me forgetting about the new Android power management sleep cycle. I have corrected my code so it will work properly next time.
When drogue deployed, it got stuck on a tail fin. This caused a high speed but stable descent between 100 to 114 mph.
During descent, the drogue freed itself, causing a temporary spike in velocity as it flipped around in free-fall before drogue inflated. This triggered my emergency curved max velocity based on altitude to act and deploy main at 2000 feet.
Overall, for a first flight, the results are promising. I should have caught the android power management issue with drogue during testing.
I have added additional sanity checks to my code as well, to reduce the chances of early deployment from odd atmospheric conditions.
Hopefully I'm able to test the updated version of my software at SRA this month, provided the weather cooperates.