Featherweight Tracker Update - Build 130+

The Rocketry Forum

Help Support The Rocketry Forum:

jotdown

New Member
Joined
May 29, 2017
Messages
4
Reaction score
0
I had an issue with my tracker during a launch this weekend. Just before the launch button was pushed my GS lost connection with "John Tx" (my tracker). Much later after a futile search for the rocket, I noticed that there is a tracker named "root", that I didn't add, in iFIP. The software saved the location of each transmitter. I plotted the locations in google maps. Image john is my tracker out on the Pad. Image root is the GPS location iFIP stored which is where all the cars were parked on the side of the road. 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. However, it's odd that "root" has a negative serial number and no channel. One last note, I downloaded the new firmware earlier that morning from my house. At the field all I did was turn both units on after the rocket was loaded onto the launch rail.

It's entirely possible I screwed this up, but I'm curious to know what happened. Appreciate any and all feedback.
 

Attachments

Locksmith

Well-Known Member
TRF Supporter
Joined
Feb 15, 2017
Messages
209
Reaction score
53
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
 

ChicagoDave

Well-Known Member
TRF Supporter
Joined
Jun 22, 2019
Messages
115
Reaction score
105
Location
Illinois
I updated the firmware before my flight on Saturday @ Mini Midwest Power. That seemed to go well, but then things went down hill.

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.

Here's the plot of the data I did get:
LOC_Sandhawk_L2.jpg

Is there some way to reset the tracker and start over again?
 

Attachments

jotdown

New Member
Joined
May 29, 2017
Messages
4
Reaction score
0
Thanks Locksmith, the problem is most likely something on my end that I don't recall, as this tracker has performed very well in the past.
 

kjs

Well-Known Member
TRF Supporter
Joined
Jan 22, 2013
Messages
206
Reaction score
57
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.
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.

I recommend using build 134 that includes a firmware update for the Cypress. We will not be releasing a build 135 with updates disabled. I will continue developing off the build 134 source.

Thanks!
 

kjs

Well-Known Member
TRF Supporter
Joined
Jan 22, 2013
Messages
206
Reaction score
57
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.
Dave - can you send me an email at small@here-and-beyond.com and we can try to get this figured out? Thanks!
 

micro

Well-Known Member
Joined
Apr 29, 2014
Messages
141
Reaction score
103
Last weekend I flew my trackers for the first time, on a 2 stage flight. Before launch I could see both trackers had good GPS fix. It did not detect launch, so had no voice callouts and did not record the flight. But it kept a good fix on both units and pointed me right to them for recovery. What do I need to do differently?
 
Last edited:
Top