Date   
Re: TrackSoar

Barry
 

If you mean the PTT LED is alternately on for 30 sec’s and then off for 30 sec’s you have definitely have a problem. And although it’s called a PTT LED it isn’t really a true PTT LED, but actually monitors the processor activity and is basically ON all the time.

 

From my web page at http://bear.sbszoo.com/construction/traker/Tracksoar/V1-1.htm -

The PTT LED, although it becomes bright around the time of each transmission, actually indicates when the processor is awake and busy processing instructions which is why it's dimly lit between transmissions when the processor is only awake very briefly to check if it's time for another transmission each time GPS data is received and then brightens when it's time to make a transmission and the processor remains awake for much longer. After adding the 4th new feature this LED also becomes bright every 10 sec's when the processor is kept awake while checking the altitude and for a burst which makes it hard to know when a transmission actually occurs so a configuration setting was added that allows the PTT LED to be used as either a processor activity indicator or as a real PTT indicator that's only on during a transmission.

 

My web page also has a link to my modified firmware that gives one the option to make the LED a true PTT indicator as well as to add a number of other useful features (at least I found them useful.)

 

I haven’t worked with the Tracksoar since I wrote that page in 2016 and can’t remember exactly how the so called PTT LED behaves under certain conditions so can’t help much more than above and what’s on my page.

 

Are you sure that you replaced the jumper, or jumpers, that you removed to program the unit after adding your callsign etc. to the config file?

 

The one thing I meant to check out after trying to locate a landed payload and never hearing any further transmissions after it landed was whether the Tracksoar would continue to transmit, or not, the last good data received from the gps if the gps lost lock and was unable to receive any further good data.

 

Barry
VE6SBS

 

From: GPSL@groups.io [mailto:GPSL@groups.io] On Behalf Of L. Paul Verhage KD4STH
Sent: Sunday, March 31, 2019 9:56 AM
To: GPSL@groups.io
Subject: Re: [GPSL] TrackSoar

 

I'll try testing that. My D72 doesn't even break squelch, so I was thinking the TrackSoar wasn't even trying to transmit.

 

I had one suggestion to remove the comment statements and then look at debug statements. That means learning more about C for the Arduino. I can at least edit a sketch and upload it. Today I guess I'm going to learn more.

 

On Sun, Mar 31, 2019, 9:41 AM Mark Conner N9XTN <mconner1@...> wrote:

I have an older Kenwood TH-D7A that has trouble decoding packets that have a short TXD, especially when the squelch is turned on.  I don't know if the D72 has the same issues.  You can try running your D72 with open squelch and see if that helps.  If not, can the TXD for the TrackSoar be increased?

 

73 de Mark N9XTN

 

 

On Sat, Mar 30, 2019 at 7:38 PM L. Paul Verhage KD4STH <nearsys@...> wrote:

I'm testing a TrackSoar APRS tracker before near space season begins in earnest. If you haven't seen one of these, it's a small board with GPS, GPS antenna, transmitter, Arduino, and two meter antenna. It runs from 2 'AA'  cells. You program it's Audrino with your callsign and it's ready to go.

 

Anyhow, I wonder if anyone is using one as I'm having a problem with mine. I see that it has a GPS lock (the GPS LED illuminates once per second) and that it's trying to transmit ( the PTT LED illuminates for 30 seconds on and off). However, my Kenwood D72 doesn't hear anything. My D72 does decode packets from my other trackers, including a Strato Track.

 

So if you have any experience with the TrackSoar, could you let me know?

 

Thanks

Re: TrackSoar

L. Paul Verhage KD4STH
 

The LED was on constantly until I turned it off the only did was not blinking for 30 seconds.


On Sun, Mar 31, 2019, 1:17 PM Barry <barry2@...> wrote:

If you mean the PTT LED is alternately on for 30 sec’s and then off for 30 sec’s you have definitely have a problem. And although it’s called a PTT LED it isn’t really a true PTT LED, but actually monitors the processor activity and is basically ON all the time.

 

From my web page at http://bear.sbszoo.com/construction/traker/Tracksoar/V1-1.htm -

The PTT LED, although it becomes bright around the time of each transmission, actually indicates when the processor is awake and busy processing instructions which is why it's dimly lit between transmissions when the processor is only awake very briefly to check if it's time for another transmission each time GPS data is received and then brightens when it's time to make a transmission and the processor remains awake for much longer. After adding the 4th new feature this LED also becomes bright every 10 sec's when the processor is kept awake while checking the altitude and for a burst which makes it hard to know when a transmission actually occurs so a configuration setting was added that allows the PTT LED to be used as either a processor activity indicator or as a real PTT indicator that's only on during a transmission.

 

My web page also has a link to my modified firmware that gives one the option to make the LED a true PTT indicator as well as to add a number of other useful features (at least I found them useful.)

 

I haven’t worked with the Tracksoar since I wrote that page in 2016 and can’t remember exactly how the so called PTT LED behaves under certain conditions so can’t help much more than above and what’s on my page.

 

Are you sure that you replaced the jumper, or jumpers, that you removed to program the unit after adding your callsign etc. to the config file?

 

The one thing I meant to check out after trying to locate a landed payload and never hearing any further transmissions after it landed was whether the Tracksoar would continue to transmit, or not, the last good data received from the gps if the gps lost lock and was unable to receive any further good data.

 

Barry
VE6SBS

 

From: GPSL@groups.io [mailto:GPSL@groups.io] On Behalf Of L. Paul Verhage KD4STH
Sent: Sunday, March 31, 2019 9:56 AM
To: GPSL@groups.io
Subject: Re: [GPSL] TrackSoar

 

I'll try testing that. My D72 doesn't even break squelch, so I was thinking the TrackSoar wasn't even trying to transmit.

 

I had one suggestion to remove the comment statements and then look at debug statements. That means learning more about C for the Arduino. I can at least edit a sketch and upload it. Today I guess I'm going to learn more.

 

On Sun, Mar 31, 2019, 9:41 AM Mark Conner N9XTN <mconner1@...> wrote:

I have an older Kenwood TH-D7A that has trouble decoding packets that have a short TXD, especially when the squelch is turned on.  I don't know if the D72 has the same issues.  You can try running your D72 with open squelch and see if that helps.  If not, can the TXD for the TrackSoar be increased?

 

73 de Mark N9XTN

 

 

On Sat, Mar 30, 2019 at 7:38 PM L. Paul Verhage KD4STH <nearsys@...> wrote:

I'm testing a TrackSoar APRS tracker before near space season begins in earnest. If you haven't seen one of these, it's a small board with GPS, GPS antenna, transmitter, Arduino, and two meter antenna. It runs from 2 'AA'  cells. You program it's Audrino with your callsign and it's ready to go.

 

Anyhow, I wonder if anyone is using one as I'm having a problem with mine. I see that it has a GPS lock (the GPS LED illuminates once per second) and that it's trying to transmit ( the PTT LED illuminates for 30 seconds on and off). However, my Kenwood D72 doesn't hear anything. My D72 does decode packets from my other trackers, including a Strato Track.

 

So if you have any experience with the TrackSoar, could you let me know?

 

Thanks

Re: TrackSoar

L. Paul Verhage KD4STH
 

Dang speech to text. The LED was on constantly for the 30 seconds I watched it. I turned off the tracker after watching it for 30 seconds.


On Sun, Mar 31, 2019, 2:53 PM L. Paul Verhage KD4STH via Groups.Io <nearsys=gmail.com@groups.io> wrote:
The LED was on constantly until I turned it off the only did was not blinking for 30 seconds.

On Sun, Mar 31, 2019, 1:17 PM Barry <barry2@...> wrote:

If you mean the PTT LED is alternately on for 30 sec’s and then off for 30 sec’s you have definitely have a problem. And although it’s called a PTT LED it isn’t really a true PTT LED, but actually monitors the processor activity and is basically ON all the time.

 

From my web page at http://bear.sbszoo.com/construction/traker/Tracksoar/V1-1.htm -

The PTT LED, although it becomes bright around the time of each transmission, actually indicates when the processor is awake and busy processing instructions which is why it's dimly lit between transmissions when the processor is only awake very briefly to check if it's time for another transmission each time GPS data is received and then brightens when it's time to make a transmission and the processor remains awake for much longer. After adding the 4th new feature this LED also becomes bright every 10 sec's when the processor is kept awake while checking the altitude and for a burst which makes it hard to know when a transmission actually occurs so a configuration setting was added that allows the PTT LED to be used as either a processor activity indicator or as a real PTT indicator that's only on during a transmission.

 

My web page also has a link to my modified firmware that gives one the option to make the LED a true PTT indicator as well as to add a number of other useful features (at least I found them useful.)

 

I haven’t worked with the Tracksoar since I wrote that page in 2016 and can’t remember exactly how the so called PTT LED behaves under certain conditions so can’t help much more than above and what’s on my page.

 

Are you sure that you replaced the jumper, or jumpers, that you removed to program the unit after adding your callsign etc. to the config file?

 

The one thing I meant to check out after trying to locate a landed payload and never hearing any further transmissions after it landed was whether the Tracksoar would continue to transmit, or not, the last good data received from the gps if the gps lost lock and was unable to receive any further good data.

 

Barry
VE6SBS

 

From: GPSL@groups.io [mailto:GPSL@groups.io] On Behalf Of L. Paul Verhage KD4STH
Sent: Sunday, March 31, 2019 9:56 AM
To: GPSL@groups.io
Subject: Re: [GPSL] TrackSoar

 

I'll try testing that. My D72 doesn't even break squelch, so I was thinking the TrackSoar wasn't even trying to transmit.

 

I had one suggestion to remove the comment statements and then look at debug statements. That means learning more about C for the Arduino. I can at least edit a sketch and upload it. Today I guess I'm going to learn more.

 

On Sun, Mar 31, 2019, 9:41 AM Mark Conner N9XTN <mconner1@...> wrote:

I have an older Kenwood TH-D7A that has trouble decoding packets that have a short TXD, especially when the squelch is turned on.  I don't know if the D72 has the same issues.  You can try running your D72 with open squelch and see if that helps.  If not, can the TXD for the TrackSoar be increased?

 

73 de Mark N9XTN

 

 

On Sat, Mar 30, 2019 at 7:38 PM L. Paul Verhage KD4STH <nearsys@...> wrote:

I'm testing a TrackSoar APRS tracker before near space season begins in earnest. If you haven't seen one of these, it's a small board with GPS, GPS antenna, transmitter, Arduino, and two meter antenna. It runs from 2 'AA'  cells. You program it's Audrino with your callsign and it's ready to go.

 

Anyhow, I wonder if anyone is using one as I'm having a problem with mine. I see that it has a GPS lock (the GPS LED illuminates once per second) and that it's trying to transmit ( the PTT LED illuminates for 30 seconds on and off). However, my Kenwood D72 doesn't hear anything. My D72 does decode packets from my other trackers, including a Strato Track.

 

So if you have any experience with the TrackSoar, could you let me know?

 

Thanks

Re: TrackSoar

Barry
 

Try leaving the tracker on longer. I’m going from memory, but I believe the GPS LED is simply tied to the 1 PPS output and it may blink regardless of whether the GPS has lock or not. The first time you power up the tracker I’m guessing the so called PTT LED may remain bright until the GPS gets a lock as the tracker processor will be constantly on (ie. not entering sleep mode to save power) until lock is achieved and if the GPS hasn’t been powered on for some time and doesn’t yet have a complete almanac saved this may take up to 10 to 15 minutes. After this the GPS will be able to get a lock much faster, like less than a minute.

 

Barry
VE6SBS

 

From: GPSL@groups.io [mailto:GPSL@groups.io] On Behalf Of L. Paul Verhage KD4STH
Sent: Sunday, March 31, 2019 3:04 PM
To: GPSL@groups.io
Subject: Re: [GPSL] TrackSoar

 

Dang speech to text. The LED was on constantly for the 30 seconds I watched it. I turned off the tracker after watching it for 30 seconds.

 

On Sun, Mar 31, 2019, 2:53 PM L. Paul Verhage KD4STH via Groups.Io <nearsys=gmail.com@groups.io> wrote:

The LED was on constantly until I turned it off the only did was not blinking for 30 seconds.

 

On Sun, Mar 31, 2019, 1:17 PM Barry <barry2@...> wrote:

If you mean the PTT LED is alternately on for 30 sec’s and then off for 30 sec’s you have definitely have a problem. And although it’s called a PTT LED it isn’t really a true PTT LED, but actually monitors the processor activity and is basically ON all the time.

 

From my web page at http://bear.sbszoo.com/construction/traker/Tracksoar/V1-1.htm -

The PTT LED, although it becomes bright around the time of each transmission, actually indicates when the processor is awake and busy processing instructions which is why it's dimly lit between transmissions when the processor is only awake very briefly to check if it's time for another transmission each time GPS data is received and then brightens when it's time to make a transmission and the processor remains awake for much longer. After adding the 4th new feature this LED also becomes bright every 10 sec's when the processor is kept awake while checking the altitude and for a burst which makes it hard to know when a transmission actually occurs so a configuration setting was added that allows the PTT LED to be used as either a processor activity indicator or as a real PTT indicator that's only on during a transmission.

 

My web page also has a link to my modified firmware that gives one the option to make the LED a true PTT indicator as well as to add a number of other useful features (at least I found them useful.)

 

I haven’t worked with the Tracksoar since I wrote that page in 2016 and can’t remember exactly how the so called PTT LED behaves under certain conditions so can’t help much more than above and what’s on my page.

 

Are you sure that you replaced the jumper, or jumpers, that you removed to program the unit after adding your callsign etc. to the config file?

 

The one thing I meant to check out after trying to locate a landed payload and never hearing any further transmissions after it landed was whether the Tracksoar would continue to transmit, or not, the last good data received from the gps if the gps lost lock and was unable to receive any further good data.

 

Barry
VE6SBS

 

From: GPSL@groups.io [mailto:GPSL@groups.io] On Behalf Of L. Paul Verhage KD4STH
Sent: Sunday, March 31, 2019 9:56 AM
To: GPSL@groups.io
Subject: Re: [GPSL] TrackSoar

 

I'll try testing that. My D72 doesn't even break squelch, so I was thinking the TrackSoar wasn't even trying to transmit.

 

I had one suggestion to remove the comment statements and then look at debug statements. That means learning more about C for the Arduino. I can at least edit a sketch and upload it. Today I guess I'm going to learn more.

 

On Sun, Mar 31, 2019, 9:41 AM Mark Conner N9XTN <mconner1@...> wrote:

I have an older Kenwood TH-D7A that has trouble decoding packets that have a short TXD, especially when the squelch is turned on.  I don't know if the D72 has the same issues.  You can try running your D72 with open squelch and see if that helps.  If not, can the TXD for the TrackSoar be increased?

 

73 de Mark N9XTN

 

 

On Sat, Mar 30, 2019 at 7:38 PM L. Paul Verhage KD4STH <nearsys@...> wrote:

I'm testing a TrackSoar APRS tracker before near space season begins in earnest. If you haven't seen one of these, it's a small board with GPS, GPS antenna, transmitter, Arduino, and two meter antenna. It runs from 2 'AA'  cells. You program it's Audrino with your callsign and it's ready to go.

 

Anyhow, I wonder if anyone is using one as I'm having a problem with mine. I see that it has a GPS lock (the GPS LED illuminates once per second) and that it's trying to transmit ( the PTT LED illuminates for 30 seconds on and off). However, my Kenwood D72 doesn't hear anything. My D72 does decode packets from my other trackers, including a Strato Track.

 

So if you have any experience with the TrackSoar, could you let me know?

 

Thanks

Re: TrackSoar

L. Paul Verhage KD4STH
 

After an hour there still was no transmission.


On Sun, Mar 31, 2019, 5:04 PM Barry <barry2@...> wrote:

Try leaving the tracker on longer. I’m going from memory, but I believe the GPS LED is simply tied to the 1 PPS output and it may blink regardless of whether the GPS has lock or not. The first time you power up the tracker I’m guessing the so called PTT LED may remain bright until the GPS gets a lock as the tracker processor will be constantly on (ie. not entering sleep mode to save power) until lock is achieved and if the GPS hasn’t been powered on for some time and doesn’t yet have a complete almanac saved this may take up to 10 to 15 minutes. After this the GPS will be able to get a lock much faster, like less than a minute.

 

Barry
VE6SBS

 

From: GPSL@groups.io [mailto:GPSL@groups.io] On Behalf Of L. Paul Verhage KD4STH
Sent: Sunday, March 31, 2019 3:04 PM
To: GPSL@groups.io
Subject: Re: [GPSL] TrackSoar

 

Dang speech to text. The LED was on constantly for the 30 seconds I watched it. I turned off the tracker after watching it for 30 seconds.

 

On Sun, Mar 31, 2019, 2:53 PM L. Paul Verhage KD4STH via Groups.Io <nearsys=gmail.com@groups.io> wrote:

The LED was on constantly until I turned it off the only did was not blinking for 30 seconds.

 

On Sun, Mar 31, 2019, 1:17 PM Barry <barry2@...> wrote:

If you mean the PTT LED is alternately on for 30 sec’s and then off for 30 sec’s you have definitely have a problem. And although it’s called a PTT LED it isn’t really a true PTT LED, but actually monitors the processor activity and is basically ON all the time.

 

From my web page at http://bear.sbszoo.com/construction/traker/Tracksoar/V1-1.htm -

The PTT LED, although it becomes bright around the time of each transmission, actually indicates when the processor is awake and busy processing instructions which is why it's dimly lit between transmissions when the processor is only awake very briefly to check if it's time for another transmission each time GPS data is received and then brightens when it's time to make a transmission and the processor remains awake for much longer. After adding the 4th new feature this LED also becomes bright every 10 sec's when the processor is kept awake while checking the altitude and for a burst which makes it hard to know when a transmission actually occurs so a configuration setting was added that allows the PTT LED to be used as either a processor activity indicator or as a real PTT indicator that's only on during a transmission.

 

My web page also has a link to my modified firmware that gives one the option to make the LED a true PTT indicator as well as to add a number of other useful features (at least I found them useful.)

 

I haven’t worked with the Tracksoar since I wrote that page in 2016 and can’t remember exactly how the so called PTT LED behaves under certain conditions so can’t help much more than above and what’s on my page.

 

Are you sure that you replaced the jumper, or jumpers, that you removed to program the unit after adding your callsign etc. to the config file?

 

The one thing I meant to check out after trying to locate a landed payload and never hearing any further transmissions after it landed was whether the Tracksoar would continue to transmit, or not, the last good data received from the gps if the gps lost lock and was unable to receive any further good data.

 

Barry
VE6SBS

 

From: GPSL@groups.io [mailto:GPSL@groups.io] On Behalf Of L. Paul Verhage KD4STH
Sent: Sunday, March 31, 2019 9:56 AM
To: GPSL@groups.io
Subject: Re: [GPSL] TrackSoar

 

I'll try testing that. My D72 doesn't even break squelch, so I was thinking the TrackSoar wasn't even trying to transmit.

 

I had one suggestion to remove the comment statements and then look at debug statements. That means learning more about C for the Arduino. I can at least edit a sketch and upload it. Today I guess I'm going to learn more.

 

On Sun, Mar 31, 2019, 9:41 AM Mark Conner N9XTN <mconner1@...> wrote:

I have an older Kenwood TH-D7A that has trouble decoding packets that have a short TXD, especially when the squelch is turned on.  I don't know if the D72 has the same issues.  You can try running your D72 with open squelch and see if that helps.  If not, can the TXD for the TrackSoar be increased?

 

73 de Mark N9XTN

 

 

On Sat, Mar 30, 2019 at 7:38 PM L. Paul Verhage KD4STH <nearsys@...> wrote:

I'm testing a TrackSoar APRS tracker before near space season begins in earnest. If you haven't seen one of these, it's a small board with GPS, GPS antenna, transmitter, Arduino, and two meter antenna. It runs from 2 'AA'  cells. You program it's Audrino with your callsign and it's ready to go.

 

Anyhow, I wonder if anyone is using one as I'm having a problem with mine. I see that it has a GPS lock (the GPS LED illuminates once per second) and that it's trying to transmit ( the PTT LED illuminates for 30 seconds on and off). However, my Kenwood D72 doesn't hear anything. My D72 does decode packets from my other trackers, including a Strato Track.

 

So if you have any experience with the TrackSoar, could you let me know?

 

Thanks

Re: TrackSoar

Clif Brown
 


There are two versions of the Tracksoar.

They are very different designs (and run different f/w) so you need to be sure with one you have.

I've flown version one, it worked fine without much fuss.

I recently purchased version two, and am experiencing the problems that KD4STH described.

I contacted Tracksoar and they suggested I add "delay(500) to line 61 of the sketch.

That seemed to help (the led's are operating more or less like my version 1), and I can hear the squelch tripped on my handheld with PTT goes bright, but I don't hear the FSK data.

I put it aside at that point as I'm also trying to get a DIY LoRa tracker working, and I have Version 1 to use.

Be very interested if someone gets Version 2 working.

-Cliff

Re: TrackSoar

L. Paul Verhage KD4STH
 

I am using V2.


On Mon, Apr 1, 2019, 7:10 AM Clif Brown <cliff.brown@...> wrote:

There are two versions of the Tracksoar.

They are very different designs (and run different f/w) so you need to be sure with one you have.

I've flown version one, it worked fine without much fuss.

I recently purchased version two, and am experiencing the problems that KD4STH described.

I contacted Tracksoar and they suggested I add "delay(500) to line 61 of the sketch.

That seemed to help (the led's are operating more or less like my version 1), and I can hear the squelch tripped on my handheld with PTT goes bright, but I don't hear the FSK data.

I put it aside at that point as I'm also trying to get a DIY LoRa tracker working, and I have Version 1 to use.

Be very interested if someone gets Version 2 working.

-Cliff

Re: TrackSoar

L. Paul Verhage KD4STH
 

I am looking at the sketch and see that it doesn't number it's lines. I assume I just count code lines and not blank or comment lines?


On Mon, Apr 1, 2019, 7:10 AM Clif Brown <cliff.brown@...> wrote:

There are two versions of the Tracksoar.

They are very different designs (and run different f/w) so you need to be sure with one you have.

I've flown version one, it worked fine without much fuss.

I recently purchased version two, and am experiencing the problems that KD4STH described.

I contacted Tracksoar and they suggested I add "delay(500) to line 61 of the sketch.

That seemed to help (the led's are operating more or less like my version 1), and I can hear the squelch tripped on my handheld with PTT goes bright, but I don't hear the FSK data.

I put it aside at that point as I'm also trying to get a DIY LoRa tracker working, and I have Version 1 to use.

Be very interested if someone gets Version 2 working.

-Cliff

Re: TrackSoar

Barry
 

In the Arduino ISD showing line numbers is one of the options that can be set on or off.

 

Barry
VE6SBS

 

From: GPSL@groups.io [mailto:GPSL@groups.io] On Behalf Of L. Paul Verhage KD4STH
Sent: Monday, April 01, 2019 9:04 AM
To: GPSL@groups.io
Subject: Re: [GPSL] TrackSoar

 

I am looking at the sketch and see that it doesn't number it's lines. I assume I just count code lines and not blank or comment lines?

 

On Mon, Apr 1, 2019, 7:10 AM Clif Brown <cliff.brown@...> wrote:


There are two versions of the Tracksoar.

They are very different designs (and run different f/w) so you need to be sure with one you have.

I've flown version one, it worked fine without much fuss.

I recently purchased version two, and am experiencing the problems that KD4STH described.

I contacted Tracksoar and they suggested I add "delay(500) to line 61 of the sketch.

That seemed to help (the led's are operating more or less like my version 1), and I can hear the squelch tripped on my handheld with PTT goes bright, but I don't hear the FSK data.

I put it aside at that point as I'm also trying to get a DIY LoRa tracker working, and I have Version 1 to use.

Be very interested if someone gets Version 2 working.

-Cliff

Re: TrackSoar

Clif Brown
 

There is a way to turn the line numbers on, but the delay(500); was added just under the call to sensors_setup(); 

just before if (APRS_SLOT >= 0)  .......

Re: TrackSoar

Clif Brown
 

In the Arduino IDE, you can turn on line numbers under FILE->Preferences.  Its a checkbox that says "Display line numbers"   

FI - On the tracksoar, there is a GPS LOCK led that will flash at one second intervals once GPS lock is attained.  I've seen it take as long as 10 mins to achieve lock in both versions.  Helps to have a clear view of the key (i.e. outdoors).


I believe this LED flashes independently of the micro, but the sketch will not send out a fix until lock has been achieved.


-Cliff
KW4CL

Re: LightAPRS Tracker

Hank Riley
 

Mustafa,

I wrote you a private email through the groups.io system within this GPSL list.  That was about a week and a half ago.  I inquired about the LightAPRS Tracker you were telling us about in March.

Wondering if you got that email and if you read it yet.  I can't find an email for you on QRZ or anywhere else.

Please reply to GPSL or to me directly at n1ltv at yahoo dot com.  The reason for not writing the email the regular way is that web-only users will not be able to see my address.  Group.io suppresses all terms that look like an email address (the presence of the @ symbol is the main clue for the server).

Hank

What do you use for tracking?

Bruce Coates
 

Hi

I'm working with a group at the University of Saskatchewan who want to start flying balloons as part of one of their grad student programs.  One of the items on their to-do list is to build up a dedicated tracking station.  They've had a Kenwood TM-D710G suggested to them as an option.  As much as I like these, there are some caveats like needing a 12v power source, limited funtionality if only using the front panel display, sheer complexity for non hams, and not least of all, needing to disable transmit so it can be used by non-hams. Rather than sink that much money into a single dedicated piece of gear, my thought are they could get a lot more functionality for less.  I'm throwing the door open for suggestions of good solutions or crazy ideas. 

To start with, what do you use for tracking?   I use:

TM-D710 in the car.
Garming GPS Map 60CX for both a gps source and plotting positions.
Windows laptop connected to the D710 via serial
I could run with Dire Wolf for sound card decoding like I do at home
APRSIS/32
My own Balloon Telemetry program (it announces balloon position via pc speaker or the car radio via AUX input)

TH-D72 for tracking on foot.

Doppler RDF antenna and receiver for homing in on a CW beacon if necessary. 

73, Bruce - VE5BNC
SABRE - http://ve5aa.dyndns.org/balloon

Re: What do you use for tracking?

AE5IB (Kip)
 

It depends on what you want to do, and how much you want to spend.

If you only want to receive the track, then a cheap $25 Baofeng UV5R HT will receive the APRS Signals. Use a good magnetic mount antenna on your car. 

I use a cheap USB GPS. I got mine from China for $15. It took a month, but it was $15. It has a mag mount, so I put it out the window on the roof, and tape it down with the blue masking tape.  It also works on the dash, but there is nothing metal for it to stick to, and the GPS signal is not as good, but it works. 

You can use a Raspberry Pi and a TNC-X or TNC-Pi, or I have also used a Winbook $89 tablet PC with TNC-X.  

I connect the computer to the WiFi on my phone, and become an I-gate, so the information can be seen on aprs.fi, or a phone application like APRSdroid. That way people without a license or who do not have an APRS receiving system can also see the balloon system. 

I use a mobile radio at 25W, and both I-gate and Digipeat. It helps everyone when the balloon is on the ground and the antenna is lying horizontally on the ground. If I am closest and get the packet, everyone else can get it also.  

Kip


 

On Wed, Apr 10, 2019 at 11:09 PM Bruce Coates <bruce.coates@...> wrote:
Hi

I'm working with a group at the University of Saskatchewan who want to start flying balloons as part of one of their grad student programs.  One of the items on their to-do list is to build up a dedicated tracking station.  They've had a Kenwood TM-D710G suggested to them as an option.  As much as I like these, there are some caveats like needing a 12v power source, limited funtionality if only using the front panel display, sheer complexity for non hams, and not least of all, needing to disable transmit so it can be used by non-hams. Rather than sink that much money into a single dedicated piece of gear, my thought are they could get a lot more functionality for less.  I'm throwing the door open for suggestions of good solutions or crazy ideas. 

To start with, what do you use for tracking?   I use:

TM-D710 in the car.
Garming GPS Map 60CX for both a gps source and plotting positions.
Windows laptop connected to the D710 via serial
I could run with Dire Wolf for sound card decoding like I do at home
APRSIS/32
My own Balloon Telemetry program (it announces balloon position via pc speaker or the car radio via AUX input)

TH-D72 for tracking on foot.

Doppler RDF antenna and receiver for homing in on a CW beacon if necessary. 

73, Bruce - VE5BNC

Re: LightAPRS Tracker

Hank Riley
 

We're in touch now.

Call for GPSL Presentations

Mike, n0mpm
 

GPSL 2019 is June 13,14,15 in Pella, IA.
 It is time to start developing a presentation you would like to share with the group.  There has been a lot of ballooning activity over the past year and I am excited for you share your experiences, results, successes and failures!  
Key Presentation Topics that would be of interest include:
1.  Education and STEM outreach
2.  ARHAB experiments and results
3.  Pico Ballooning 
4.  Advances in tracking systems
5.  Other interesting stuff !!
Please Email me with your Topic and estimated time required.  If possible, presentations should be on PowerPoint so we can share them to all participants.
The success of GPSL depends on YOU !  Thanks for taking the time that will make 2019 GPSL one to remember!
73,
Mike N0MPM
Pella Explores Near Space

GPSL 2019 Registration Reminder

Mike, n0mpm
 

GPSL is just around the corner.  Things are shaping up for a great weekend, but we need your registration information soon.  Please register on the  Superlaunch.org web page.
Also, get your hotel reservations soon.  The preferred pricing is expires as follows:
Country Inn and Suites:  May 12
Super 8 Motel:  May 12
AmericInn and Suites:  May 1
You can find Hotel Information under the Venue tab on the Superlaunch.org web page.

Looking forward to seeing everyone in Pella...
Mike N0MPM

Tinytrak or Opentracker for sale?

Michael
 

Hi all,

Our team is flying Paul V's flight computer for GPSL2019. We need a backup tracker...anyone have a Tinytrak or Opentracker to sell? 

Thanks,
Mike KD0MEQ

Re: Tinytrak or Opentracker for sale?

Zack Clobes W0ZC
 

I have one ArduinoTrack left in stock.  It's set up for the Australian APRS frequency but I do have an extra 144.39 module here if you would prefer.  



Zack


On Tue, Apr 30, 2019, 8:41 AM Michael <moody.michael@...> wrote:
Hi all,

Our team is flying Paul V's flight computer for GPSL2019. We need a backup tracker...anyone have a Tinytrak or Opentracker to sell? 

Thanks,
Mike KD0MEQ

2019 GPSL Hotel Registration

Mike, n0mpm
 

Just a reminder that preferred prices for the Country Inn/Suites and the Super 8 hotels expires on May 12.  If you haven't made your room reservations yet, NOW is the time...
Looking forward to seeing you all in Pella...
mike