- Joined
- Feb 22, 2017
- Messages
- 189
- Reaction score
- 16
Hi Everyone,
With my recent L1 cert in hand, I was excited to finally fly my LOC Vulcanite this past weekend at ROCstock. The test flight went ok (G80NT) - plenty stable but I had some issues with my chute release (as in it didn't) so it landed with a reefed chute from 1900' feet. Not even a scratch on the rocket, so I felt pretty good about the strength of the build. Since it was the maiden flight, it got to earn its name on that one: "Free Fall".
So on to the main event.
I had a few goals with the next flight:
- Fly my first I motor - AT I280DM. (I used the full 14 sec delay)
- Mile high or more (OR simmed 6,000'+, ThrustCurve iffy)
- Break Mach (OR iffy, ThrustCurve no way)
- Attempt GPS tracking for the first time.
I've been following a "one skill at a time" path, and tracking is next on the list of things to learn. For the most part, the flight would be mostly in visual range so it seemed a good opportunity to test out my system.
On board this flight I had:
Jolly Logic Altimeter 3
Jolly Logic Chute release (set at 400')
Altus Metrium Tele GPS tracker
For picking up the GPS signal, I'm using a Yaesu FT1XD with a 3 element Yagi Antenna.
iPhone for manually inputting GPS coordinates (google maps)
I'm still struggling a little with the HT and all of the ARPS settings, but I managed to get it working and a lock on the tracker on the pad. The gps coordinates showing up on the HT seemed to be correct for the launch site. So far so good.
It was a great looking flight. Wow I love those sparky motors. And loud! This is going to get expensive!
I could see the rocket land, so no real worry about losing it. We were able to get a good clear signal from the tracker and the supposed GPS coordinates at the landing location.
Here's a shot of the tracker's GPS coordinates on the HT. Sorry that it's barely visible.
It says N 34" 29.71' W 116" 57.64'
- First Question/problem: I could not figure out how to get these numbers into google maps to show me where the rocket is. Is there a better map app for this? Is there a standard/easy format to enter these exact coordinates into google maps? (I don't own any Android devices, so for now my understanding is I have to do it the hard way.)
I gave up on having my map take me to the rocket - not a big deal as I could see where it landed but I would have been pulling hair if I hadn't.
Upon recovery, I downloaded the flight data from the JL A3. According to the data, I went over a mile (6,654') but just came a tiny bit shy of breaking mach (757 mph). The chart in this view doesn't really show the chute release deploying at 400' but it does when I zoom in using the app. I did however find the 4fps landing speed a little unusual.
The GPS Data tells a different story. I expected the data from the GPS would not be as accurate as the altimeter, but curious to see what you all think of the considerable difference. Could the Altimeter data be wrong?
Only 3094' and 200 mph slower than my JL3 indicates. Could this perhaps have to with the fact that our launch site is 2800 feet above sea level?
That being said, based on the gps data, the last reported location seems accurate. When I plugged them into Google Earth, it made this nice flight path for me:
One strange anomaly is the straight line connecting my home in Glendale to the launch location. Must have had some data on it from when I was testing it out at home and included it as part of the flight?
So the good news is that as far as the TeleGPS goes, the tracking works great. I love how small it is and it's so far easy to use.
Second Question/Problem: The coordinates displayed on my radio don't match what I downloaded from the tracker. Close, but seemingly not the same. This confused me since the numbers on the radio were being sent by the tracker... so can anyone explain why this is? Do I have something set incorrectly on the HT?
TeleGPS N 34º 29.738574' W 116º 57.462420' vs Yaesu N 34" 29.71' W 116" 57.64'
I'm still a major noob to all things GPS, so any insight here is appreciated. I'm building a Rockety Warehouse 38 Special that will definitely need a tracker, so I'm hoping to get the bugs worked out before putting that one up.
Thanks for reading, and look forward as always to your opinions and advice.
(more flight data)
View attachment Info.pdf
(and the launch!)
[video]vimeo.com/243262804[/video]
With my recent L1 cert in hand, I was excited to finally fly my LOC Vulcanite this past weekend at ROCstock. The test flight went ok (G80NT) - plenty stable but I had some issues with my chute release (as in it didn't) so it landed with a reefed chute from 1900' feet. Not even a scratch on the rocket, so I felt pretty good about the strength of the build. Since it was the maiden flight, it got to earn its name on that one: "Free Fall".
So on to the main event.
I had a few goals with the next flight:
- Fly my first I motor - AT I280DM. (I used the full 14 sec delay)
- Mile high or more (OR simmed 6,000'+, ThrustCurve iffy)
- Break Mach (OR iffy, ThrustCurve no way)
- Attempt GPS tracking for the first time.
I've been following a "one skill at a time" path, and tracking is next on the list of things to learn. For the most part, the flight would be mostly in visual range so it seemed a good opportunity to test out my system.
On board this flight I had:
Jolly Logic Altimeter 3
Jolly Logic Chute release (set at 400')
Altus Metrium Tele GPS tracker
For picking up the GPS signal, I'm using a Yaesu FT1XD with a 3 element Yagi Antenna.
iPhone for manually inputting GPS coordinates (google maps)
I'm still struggling a little with the HT and all of the ARPS settings, but I managed to get it working and a lock on the tracker on the pad. The gps coordinates showing up on the HT seemed to be correct for the launch site. So far so good.
It was a great looking flight. Wow I love those sparky motors. And loud! This is going to get expensive!
I could see the rocket land, so no real worry about losing it. We were able to get a good clear signal from the tracker and the supposed GPS coordinates at the landing location.
Here's a shot of the tracker's GPS coordinates on the HT. Sorry that it's barely visible.

It says N 34" 29.71' W 116" 57.64'
- First Question/problem: I could not figure out how to get these numbers into google maps to show me where the rocket is. Is there a better map app for this? Is there a standard/easy format to enter these exact coordinates into google maps? (I don't own any Android devices, so for now my understanding is I have to do it the hard way.)
I gave up on having my map take me to the rocket - not a big deal as I could see where it landed but I would have been pulling hair if I hadn't.
Upon recovery, I downloaded the flight data from the JL A3. According to the data, I went over a mile (6,654') but just came a tiny bit shy of breaking mach (757 mph). The chart in this view doesn't really show the chute release deploying at 400' but it does when I zoom in using the app. I did however find the 4fps landing speed a little unusual.

The GPS Data tells a different story. I expected the data from the GPS would not be as accurate as the altimeter, but curious to see what you all think of the considerable difference. Could the Altimeter data be wrong?

Only 3094' and 200 mph slower than my JL3 indicates. Could this perhaps have to with the fact that our launch site is 2800 feet above sea level?
That being said, based on the gps data, the last reported location seems accurate. When I plugged them into Google Earth, it made this nice flight path for me:

One strange anomaly is the straight line connecting my home in Glendale to the launch location. Must have had some data on it from when I was testing it out at home and included it as part of the flight?
So the good news is that as far as the TeleGPS goes, the tracking works great. I love how small it is and it's so far easy to use.
Second Question/Problem: The coordinates displayed on my radio don't match what I downloaded from the tracker. Close, but seemingly not the same. This confused me since the numbers on the radio were being sent by the tracker... so can anyone explain why this is? Do I have something set incorrectly on the HT?
TeleGPS N 34º 29.738574' W 116º 57.462420' vs Yaesu N 34" 29.71' W 116" 57.64'
I'm still a major noob to all things GPS, so any insight here is appreciated. I'm building a Rockety Warehouse 38 Special that will definitely need a tracker, so I'm hoping to get the bugs worked out before putting that one up.
Thanks for reading, and look forward as always to your opinions and advice.
(more flight data)
View attachment Info.pdf
(and the launch!)
[video]vimeo.com/243262804[/video]