- 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 email@example.com 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.
Are you saying that you have two trackers and one GS with them all set to the same frequency? If so, the trackers are both trying to transmit at exactly the same time slice and frequency, so will be causing interference with each other (and possibly corrupted packets). The normal mode for a two stage would be with two ground stations each paired with the different trackers on a different frequency.This system is still very janky. I flew multi stage again last weekend and did nothing differently from before, same rocket. Before launch I had NO confidence that it would track. I checked it at the pad, it showed connection to both trackers and the ground station, fine. When I got back to the flight line the timers on the GPS and track screen were counting up as if it had lost connection (plus several minutes). The only reason I said go to launch was if I went over to the comm screen I could see packets coming in. Track screen showed bogus data. Despite it showing no connection it detected launch and vocalized the flight.
Once on the ground the track screen showed it correctly about 4,400 feet away. Once I got under about 1,000 feet from it it started showing 39,000 some feet away. Thankfully the direction arrow continued to work because the distance was garbage data until I was right on top of it.
My theory is that my GS linked up with "root" somehow just before the launch because both Tx are showing up on the GPS screen with saved coordinates.
[I see I missed some of these posts while working in quarantine - sorry about that.]My tracker is named root "my last name" I was launching all day at mmwp but shouldn't affect anyone else there is not frequencies like the old days
Just our of curiosity, why would you need to switch to the other tracker during the flight?Yes same frequencies per the user manual.
The website says "two or more stages" not "rockets" with ONE ground station. So you're suggesting I put the trackers on different channels and then DURING THE FLIGHT go into the ground station settings, change the frequency, and see if I can pick up the other unit??
The ground station is listening on just one frequency. So it is only listening on the frequency it is set to, so it only picks up the one stage. The other stage would have none of the packets recorded. And if you set them both to the same frequency, they you get cross talk / corruption.Before the flight I verify that both trackers are up and running and have lock. Then switch to track the sustainer for the flight, since that's where the exciting telemetry is coming from. The only time I'd ever switch back to the booster tracker is when it's time to go find it. That's where the "easy switching between displays" comes in, right?
To get live data. So I have a close proximity to it's final location. It will not necessarily pick up the signal once it's on the ground. Definitely didn't last weekend until I was within a couple hundred feet.Just our of curiosity, why would you need to switch to the other tracker during the flight?
Ah I get it now. I was missing the part that Kevin just explained about it not tracking both at the same time.To get live data. So I have a close proximity to it's final location. It will not necessarily pick up the signal once it's on the ground. Definitely didn't last weekend until I was within a couple hundred feet.
There ARE frequencies and it sounds like other trackers on the same frequency will corrupt your connection. On top of that, the software doesn't warn you. Not good.My tracker is named root "my last name" I was launching all day at mmwp but shouldn't affect anyone else there is not frequencies like the old days
Yes the GS needs to be at the same frequency as the tracker. So with a two stage flight you have to have the trackers on different frequencies so with only one GS, you need to switch back and forth with the selector wheel on the GPS page. I once had the feature where you could swipe up and down on the tracking page to change rockets, but then people did it accidentally while tracking and didn't realize why they lost tracking (their other tracker wasn't even on).Doesn't the ground station need to be set up on the same frequency as the tracker in order to receive live telemetry? If not, why even set it on the GS?
I'll need to test the frequency change timing, that but the rocket transmits at 1hz and finishes that in < 0.5 seconds. then it listens for other 'community' transmissions during the second 0.5 seconds. There is also the issue if the bluetooth has any transmission issue, then the phone might think it commanded the change but it didn't actually happen and then you are listening to the wrong tracker.How quickly can the ground station switch frequencies?
Would it be possible to have a setting on a two stage flight to listen to frequency that is currently being displayed 95% of the time but have the GS automatically switch to the other stage, grab a few packets, and switch back? This would get you a last known position on the other stage in case the link was lost once it was on the ground.
I can imagine a case where I was watching the sustainer and never saw the booster after burn out. If the booster lands behind a hill or small rise it might be hard to get close enough to reestablish a connection without at least a hint where to go to. I know you have the possibility of other rockets to see the booster and relay the lost rocket signal, but this relies on another rocket going up with a Feather Weight tracker and you can't count on that.