- Feb 21, 2019
- Reaction score
As did mine this weekend
Revisiting this; it ended up that the two firmware updates mentioned above both were both well understood (build 134 was the fix for one user and the other user had serial numbers 11 and 49 which was a pre-release version that I was going to have to update manually anyway.Yes although I may do a build 135 tonight that has firmware updates turned off so I can verify there isn't an issue with 134. I've had two users who had problems. One was update from firmware > 1 year old, but one was more recent firmware.
Dave - can you send me an email at firstname.lastname@example.org and we can try to get this figured out? Thanks!My tracker lost connectivity during boost and I didn't pick it up again until 1,000' agl Fortunately it did keep the connection all they way down so I was able to retrieve my rocket. But once on the ground I lost connectivity again.
When I returned home I tried for about half an hour to re-connect to the tracker but it never connected.
You can see in the log that there are all "0"s where data should be during the launch. Then afterword there was spiritic data logged.