Home Artists Posts Import Register
Join the new SimpleX Chat Group!

Content

Hey Patrons! Predictably, the launch of Scout E has been delayed a bit. In short, a few things happened:

- The GPS antenna on Scout's avionics assembly died/became really sad about being in an extremely confined space. Fixed now, no problem overall.

- AVA's power switch died, then telemetry radio's wires got ripped off accidentally, then I had a big axis definition problem in Sprint's codebase that carried forward too long. i.e. several hours troubleshooting a fairly simple error...

- We can leave politics out of this, but I severely underestimated how distracted I'd be by the US general election this week. Probably should have seen that coming, but it made focusing hard for a bit. 

Anyway, the photo here is the last test I did just now, a quick lift test with a UAV. That's the barometric altitude vs the filtered altitude to make sure AVA's Kalman filter is still working well. With that, and a good part of the vehicle already good to fly, I'm thinking we'll be all set to launch mid-next week. That gives us a pretty solid cushion even if something goes wrong.

Apologies for being "The Boy Who Cried Launch", we're alllllllllmost there...

Files

Comments

Anonymous

Tory... is that you? :D good luck!

Anonymous

Disappointing but understandable. It's better to take your time and not make careless mistakes trying achieve some arbitrary deadline you gave yourself. I too have been very distracted by the election. I can definitely relate to that. Best of luck, maybe next week!

Chris Silvia

Love it when the line is on the other line!

Anonymous

Distracted by the election? Yeah I totally cannot relate to that LOL

Anonymous

https://www.youtube.com/watch?v=zzl13bKioqQ&ab_channel=JoshuaBardwell

Anonymous

So I think you have the capability to do this with out a shadow of doubt in my mind and I think it would be cool if you did. Plus its 15,000 dollars so

Anonymous

Nice KF plot! Are you doing any residual monitoring/outlier rejection in your KF? I ask because it looks like the measurement spike at around T+178 sec affects the KF estimate. If you aren't, I can talk you through some techniques for doing that. Also, I assume you're using acceleration data as a control input in the filter?