May I ask a question?

[Tookanforever]

The coordinates you are referring to is roughly the location of the away cell.. the LCO's is roughly where the rocket pasture is where my FW GS is shown..
I believe that when the anomalic event took place at 12.35? These packets were received.. but i can't correlate it to the actual flight time of the blue raven to confirm altitude etc.
As i understand it the rocket drifted for over several minutes catchingcon thermals..
But the puzzle is coming together?
Could metallic paint be a culprit?
Thanks for the continued input.
Best ,
David

 

[Adrian A]

Fellow Fliers',

I flew my Wildman Jr. at AIRfest and am attempting to understand what happened during my flight, I think, but am not certain there may have been an electrical problem..

After reporting to the RSO, and being cleared to load my Rocket by the LCO, all my electronics appeared to be working on the pad, after returning to the flight line, the Featherweight app showed Connection, and good signal strength to me.. Launch and everything goes smoothly, rockets away.. I had a visual on my rocket drifting south over the TX compound, (I believed), towards the cornfields on 80th and eden rd. When I realize i had no voice telemetry, nor connection to the FW GPS..

I only read the first few posts in this thread, but based on that, the most likely issue was a channel conflict with another user. The app only reports data from your unit, but once you walked away from the pad, another user on your channel was closer and had a stronger signal than your tracker, and so the displayed location never updated. On my developer's to-do list is to show the name of the received rocket in red at the top when that happens so that it's more obvious that the channel conflict needs to be resolved. I may also have him pop up a dialog box.

If you post the ground station log, which records all the data received from your rocket or any other rocket, we can confirm that's what happened. Look under flights, and you should see one ground station (GS) log for each day it received any data.

Edit: I see that your file "tracker anomaly" is your GS log from 10:38 AM to 11:07 AM. on 8/31. Is that when you flew? It looks like your GPS tracker was having trouble getting a GPS lock. Try running your tracker with a fully charged battery outdoors, outside of your rocket. If the GPS performance is strong there, then something in your rocket configuration was reducing the signal strength.

Edit again: Looking at your Blue Raven summary, the flight was from 11:14 to 11:17. Since the "tracker anomaly" file is missing the time of the flight, was there more to the log than what you posted? Otherwise, the GS was either turned off accidentally or lost communication with the phone.

 

[Andrew Brown]

Adrian,

Please, please, please, with sugar on top implement this. I had mine jammed several times at LDRS. Nothing is worse than sitting on the pad for an hour only to have your tracker stop working right before launch and find out someone turned theirs on with the same channel and didn't bother looking at the freq board.