Featherweight Tracker Build 87

Kevin and I just released a new build of the Featherweight GPS Tracker app and firmware, build 87. Based on feedback from users after the last forced update, (and particularly because we weren't able to get everything done and tested before Friday afternoon), we're making this update optional. However, I do strongly recommend updating to this build because it fixes an issue that we discovered last weekend that could result in dropping packets during the flight. Just go to the TestFlight and push the button for the FIP build 87.

On the fun side, this also adds the ability to track to rockets found by over-the-horizon relay, and it has a first draft of voice telemetry, with your choice of voice selections.

Kevin and I don't have local launches this weekend, so I'll be interested to hear how it goes with the new build.

What triggers voice tracking? Does it need a G event to initiate it? Just tried tracking it on the ground but nothing happened voice wise...

yes, there is some check for vertical velocity and maybe delta altitude. I need to check the specifics again - once we realized the tracking issue from the last launch, we were more focused on fixing that. specifically you want to be on the track page (which you normally would be) when the rocket launches. it should announce 'launched' and then give updates as it climbs, at apogee give the max altitude and then descent and speed. my wife says it talks too much (WHAT?!?!) so I may want to reduce the readouts. on the way up, it tries to just give round K ft numbers if this 1 Hz altitude is > 1 K above the last. on the way down, it just gives readouts such as "below 13000 at 90" (descent rate of 90) and then again below 12000, etc. below 1000, it is supposed to go into 1Hz readouts.

note there is an issue I will fix - if you leave the track tab (like go to the GPS tab) then it messes up the variable keeping track of flight state. I was going to fix that but the COMM being dropped was more important...

Thanks!

/kjs

In one of the next builds there will be a simulation that you can run on-board, which will provide realistic dynamics to try out the recording, pointing, and voice features. We have been using that in our internal builds to do development of the logging and liftoff detection algorithms, but there are some glitches in the real-time display so we're not making it available just yet.

For updating the firmware, it is best to start with all units off, install the iFIP update, then power up one unit and let it complete the update on that unit before acknowledging it complete and then power up the next unit. there is an issue if currently if the phone detects multiple units to update at once. if you encounter that issue (if the OTA update hangs) then power all units off and restart FIP and then power them up sequentially allowing each to complete it's update before proceeding. This weekend I'm going to look into setting up a queue for updates so the phone handles the serialization of the updates.

Thanks!

All great news! so many voices to choose from! In the field i use one tracker in my rocket and the other is used attached to my daughters quad so I have a chance to find her when she is stuck somewhere. There is no major vertical trigger for that reading- minor item as it will still lead me to her. Keep up the good work!

warnerr said:

All great news! so many voices to choose from! In the field i use one tracker in my rocket and the other is used attached to my daughters quad so I have a chance to find her when she is stuck somewhere. There is no major vertical trigger for that reading- minor item as it will still lead me to her. Keep up the good work!

Click to expand...

that brings up an interesting use case... we could probably provide a way to put a tracker for your daughter in 'lost rocket' (lost daughter?) mode and then you would get updated locations from your daughter each time someone launched a rocket with another Featherweight Tracker...

Android!