On Thu, Feb 7, 2013 at 9:10 PM, Scott Miller <scott@...> wrote:

> My proposed format is variable-length, more efficient, and lets you
> specify profiles for metadata - either a standard pre-defined profile
> (e.g., T3 profile with 1 temperature, 1 count, and 5 voltage readings)
> or a profile you'd create yourself on the site.  Because from what I've
> seen, most folks don't need equations and labels on the air, they just
> want the data presented nicely online.

The base-91 has the variable length concept...

The metadata sounds like the existing parameter definitions just with
a different coat of paint. Sounds like you are advocating defining the
metadata directly on aprs.fi via the web interface. You define the
metadata currently via APRS with a few APRS messages sent to the
specific callsign. Do that once every few years to keep aprs.fi up to
date and you're there.

I'm game to hear different though... what about defining it on the
wiki where it can be discussed and documented rather than just in an
email? It's kind of out of the scope of what the reflector is about.

--
James
VE6SRV

I wrote up a sheet about it some time back.  If I can figure out where I
put it, I'll post it to the wiki.

Scott


On 2/7/2013 10:32 PM, James Ewen wrote:
> On Thu, Feb 7, 2013 at 9:10 PM, Scott Miller scott@...
> <mailto:scott%40opentrac.org>> wrote:
>
>  > My proposed format is variable-length, more efficient, and lets you
>  > specify profiles for metadata - either a standard pre-defined profile
>  > (e.g., T3 profile with 1 temperature, 1 count, and 5 voltage readings)
>  > or a profile you'd create yourself on the site. Because from what I've
>  > seen, most folks don't need equations and labels on the air, they just
>  > want the data presented nicely online.
>
> The base-91 has the variable length concept...
>
> The metadata sounds like the existing parameter definitions just with
> a different coat of paint. Sounds like you are advocating defining the
> metadata directly on aprs.fi via the web interface. You define the
> metadata currently via APRS with a few APRS messages sent to the
> specific callsign. Do that once every few years to keep aprs.fi up to
> date and you're there.
>
> I'm game to hear different though... what about defining it on the
> wiki where it can be discussed and documented rather than just in an
> email? It's kind of out of the scope of what the reflector is about.
>
> --
> James
> VE6SRV
>
>

On Fri, Feb 8, 2013 at 8:00 PM, Eric Fort <eric.fort@...> wrote:

> 1.   I really  do not need a bunch of excess clutter on the nuvi screen.
> How can I limit the stations tracked and displayed to only those from a
> predetermined list (i.e. only the HIBAL and chase teams)?
>
> 2.  It would be useful to see not just lat/lon but altitude of the HIBAL
> as well.  How might this best be displayed?

Are you limiting the equipment used in the chase to just the radio,
OT2, and Nuvi350? Will you have a laptop along as well?

The best you can do is set a waypoint limit so you can only see
stations within a specified distance of your station. I don't think
you can get altitude of the payload displayed on the Nuvi.

You could get the altitude of the payload displayed on an AvMap GPS
connected to the OT2 though.

If you attach a laptop, and run APRSISCE/32, you can have everything
you want, and have it displayed on a much larger screen.

--
James
VE6SRV

If you attach a laptop, and run APRSISCE/32, you can have everything you want, and have it displayed on a much larger screen.

Shrieks (formerly SkyWarn)
APRSISCE/32 parses any !<nonwhitespace>! from comments and groups (up to 32 of) them into a View / Shrieks submenu. This allows event coordinators to pick a suitable !EVENT! for stations to put in their beacon comment to provide easy on-screen filtering of only the stations participating in the event. The Spotter Network requires their users to put !SN! in their comment, so you can expect to see !SN! in the View / Shrieks menu if any such stations are in your range.

!Shriek!s are also parsed from nickname comments EVEN if the nickname or comment is not enabled! This allows you to nickname your favorite stations with a !WATCHME! comment and then View / Shrieks / !WATCHME! to see ONLY those stations! You could even nickname stations as !VIEW1!, !VIEW2!, !VIEW3!, and so forth to build your own local MultiTrack views of specific stations. A single station can even have multiple !VIEWn! tags in the comment to put them on multiple views.

If nicknames are enabled, and a station has a nickname, and that nickname overrides the comment, then ONLY the comment's Shrieks are used. The comment received from the station will be ignored completely for Shriek purposes. After these conditions are no longer met, a new packet from the station must be received to get a proper !Shriek! for the station.

(So, why "Shriek"? Search for Shriek at Wikipedia)

It seems to be the same problem with power control when digi as for aprs
message.
I am using my excellent tracker as a digipeater but the power relay stays on
after sending out the packet
Firmware: 56330

Thomas SM0YOS

On Fri, Feb 8, 2013 at 9:54 PM, Eric Fort <eric.fort@...> wrote:

>> Are you limiting the equipment used in the chase to just the radio,
>> OT2, and Nuvi350? Will you have a laptop along as well?
>
>
> I'd rather just use the nuvi 350 and t2-301, otherwise what's the
> advantage of the t2-301 nuvi combo?  If I need a laptop I might as well just
> run soundmodem on the laptop and attach that to a radio.

You tell me what the advantage is... The only advantage I see is less
equipment in the vehicle, but you are limited to the capabilities of
the equipment chosen. I love the OpenTracker line. I have over a dozen
OTUSB/OT2/OT3 units, and an R-Trak HAB as well... they all have their
own specialized purposes. However I run my Kenwood D710 and AvMap G6
in the truck because the capabilities available in those devices
provide me with the desired functionality. I also run a TH-D72 as my
handheld unit. The two Kenwood devices and the AvMap give me
everything I need to be able to chase and recover HAB payloads. I
can't achieve the same level of functionality with the OT line and the
Nuvi350.

When chasing balloons however, I add on the laptop (or WebDT366) so
that I get an even larger screen, a historic track of the payload
path, packet logs, and a bunch more functionality that I can't get out
of the Kenwood and AvMap G6.

> What about using some creative scripting on the t2 to limit what the nuvi
> sees?  Any possibilities there?

Not that I can think of. We don't have access to manipulating the
incoming data stream. That would take a fair bit of processor power,
and a lot of memory to be able to provide enough commands to parse out
packets and manipulate them based on your own criteria.

>> You could get the altitude of the payload displayed on an AvMap GPS
>> connected to the OT2 though.
>
> AvMap?  what are you referring to?

Uh, the AvMap GPS line... The current production model is the AvMap
G6. http://www.geosat.us/ It is a GPS built in Italy, but it has
firmware custom designed to support APRS built in. No other GPS
manufacturer supports APRS. The closest anyone else comes is Garmin,
and that's only because Scott has manipulated their Fleet Management
Interface into believing that APRS data is FMI data. We all know how
interested Garmin is in making the FMI mode work properly to support
live data from the APRS network.

The AvMap G6 is the latest in the AvMap line to support APRS. The G4
and G5 units also supported APRS functionality. With the G6, I can
tell the unit to follow a specified target (the balloon payload), and
I can have three windows open on the map screen showing me specific
data on that payload (I like speed, heading, and altitude when
chasing). I can tell the GPS to calculate a route to the payload (not
a good idea while the balloon is in flight, you want to head to where
it is going to land, not where it is currently), but when the payload
is on the ground, the GPS can direct you to the area.

>> If you attach a laptop, and run APRSISCE/32, you can have everything
>> you want, and have it displayed on a much larger screen.
>>
>
> I'll consider that as an option, but then doesn't that defeat the entire
> point of the nuvi/t2-301 combo?

That all depends on what the point of the T2-301 and Nuvi is... If you
want a small minimal component count APRS station with the ability to
see incoming icons on the screen, and the ability to send and receive
messages on screen, then you've probably got the right package.

If you want to be able to limit the incoming display to just a single
specific station, or group of stations, and to be able to see the
altitude of a specific station on screen, then you probably don't have
the right package.

Ham radio is a niche market. APRS is a niche market in the ham radio
niche market. HAB tracking is a niche market in the APRS niche market
of the ham radio niche market. Most manufacturers aim to position
their products to hit the largest market possible. The fact that AvMap
is producing a product that supports APRS is amazing, and then they
also have features that cater to the HAB niche is even more amazing.

You can't sit in a rowboat in the middle of a corn field in Nebraska
and wonder why you're not flying to London. Sometimes you need
specialized equipment to perform a specialized task. :)

As Brian suggested, perhaps using a unique frequency would give you
the ability to limit the stations heard. Hopefully you are aware that
once your payload is aloft, there is no need to run an outgoing path.
With the payload over 1000' AGL, asking for digipeats is a waste of
time. Your payload will transmit much further than any ground based
digipeater around. Moving to a frequency with no digipeaters available
does not affect your ability to track. You can have ground based
stations switch to the unique frequency and i-gate your packets so
they appear on the APRS-IS stream.

Many HAB groups run paths at altitude, which just causes all kinds of
unnecessary noise on the ground. Dozens to hundreds of digipeaters end
up repeating packets that are easily copied by every station on the
ground already. Even worse people run with WIDE1-1 as a path request,
causing not only every digipeater to act upon the packet, but every
home fill-in digipeater as well.

If you are running a quality HAB APRS tracking payload, you'll have
the ability to change paths based on profile switching. Set up your
profile switching to use no path on one profile, and then once the
payload has dropped below something like 5000 feet, add an outgoing
path to ask for help from the digipeaters. If you land somewhere a
long distance from an i-gate, and your chase teams have managed to not
keep up with the payload, a digipeat *might* help you get closer.

Many people feel that if the payload can't be heard on the ground via
the APRS-IS stream, that there's no possible way of recovering the
payload. That is not the case. We've had payloads stop being gated at
20,000 feet AGL and still been able to find them on the ground. You
simply extrapolate the flight path based on the winds seen on the way
up and go to the projected area. If need be set up a search grid and
search until you can hear your payload.

If you have a frequency agile payload, you can have the unit switch
back and forth between your unique frequency and 144.390, and get the
best of both worlds.

--
James
VE6SRV

It was always assumed in the design that you wouldn't use power control
with a digi, since it can't receive packets to digipeat when it's turned
off...

Scott

On 2/9/2013 2:11 AM, Thomas wrote:
> It seems to be the same problem with power control when digi as for aprs
> message.
> I am using my excellent tracker as a digipeater but the power relay
> stays on after sending out the packet
> Firmware: 56330
>
> Thomas SM0YOS
>
>

--- In tracker2@yahoogroups.com, Scott Miller  wrote:
>I understand the reason for that design. I am using the OT as an unattended
tracker and let the OT power up my radio when it's time for a beacon. In
attended mode I power on my radio manually and turn on the digi function. When I
go back to unattended mode I have to "power down" the relay with the power off
command or switch the power off and on to the tracker.
Otherwise I leaves my radio with the power on.
But I can handle the situation know when I am aware of the design.

Thanks
/Thomas

> It was always assumed in the design that you wouldn't use power control
> with a digi, since it can't receive packets to digipeat when it's turned
> off...
>
> Scott
>
> On 2/9/2013 2:11 AM, Thomas wrote:
> > It seems to be the same problem with power control when digi as for aprs
> > message.
> > I am using my excellent tracker as a digipeater but the power relay
> > stays on after sending out the packet
> > Firmware: 56330
> >
> > Thomas SM0YOS
> >
> >
>

Been running Argent gear for a long time.

My T2-301 and nuvi 350 has been a super package. Been looking and making some
gear changes and I need some info on the T3-135 for the Alinco.

Can it be connected to the New AvMap 6 and will messaging and all other features
work?

Will it display weather data ect on the AvMap. like it would when connected to a
Kenwood?

I see the it is currently out of stock, any idea to when it may be back in
stock?

Thanks

Scott KB7DZR

On Mon, Feb 11, 2013 at 3:10 PM, Tony VE6MVP <tony@...> wrote:
>
> Can the GTRANS cable, when hooked up to the Nuvi 350 and the D710, allow you
to do the same things?  I see there is mention of firmware upgradeable and 20
Mhz CPU.
>
> If that capability isn't there can such be added?  Note that Lynn D, author of
APRSIS32, knows how to do this programmatically.   And actually I could probably
send you folks a log of the commands he sends the D710.

I'm not sure what commands specifically you are talking about, but I'm
not aware of any that the D710 accepts over its 2.5mm GPS interface.
TNC commands must be issued to the serial port on the back of the
control head, and CAT commands are issued through the serial port on
the back of the radio (next to the antenna port).

Tom KD7LXL

On Mon, Feb 11, 2013 at 4:15 PM, Tom Hayward <tom@...> wrote:

> I'm not sure what commands specifically you are talking about, but I'm
> not aware of any that the D710 accepts over its 2.5mm GPS interface.

You can access the messaging interface over the GPS port.

> TNC commands must be issued to the serial port on the back of the
> control head, and CAT commands are issued through the serial port on
> the back of the radio (next to the antenna port).

And that one you have bang on... all the commands Tony is alluding to
are accessible via the com port on the back of the control head, not
on the GPS port.

--
James
VE6SRV

> You can access the messaging interface over the GPS port.

Not with the GTRANS you can't.  If there's messaging support on the GPS
port, it's for the AvMap.  I don't think that was implemented when I got
my D710.  Is there an update?

Scott

I did implement AvMap support - it ought to be in the development built
at least, but I haven't gotten around to documenting it yet.  I'll be
happy to jump on that if someone wants to do some beta testing.

I saw a few in stock today.  Some of them look a little different than
the pictures - we just got a new board revision in that's about 1/3
smaller and has the USB connector on the side to avoid having to route
the cable at an odd angle, but otherwise it works the same.

Scott

On 2/11/2013 9:39 AM, offtracks1 wrote:
> Been running Argent gear for a long time.
>
> My T2-301 and nuvi 350 has been a super package. Been looking and making
> some gear changes and I need some info on the T3-135 for the Alinco.
>
> Can it be connected to the New AvMap 6 and will messaging and all other
> features work?
>
> Will it display weather data ect on the AvMap. like it would when
> connected to a Kenwood?
>
> I see the it is currently out of stock, any idea to when it may be back
> in stock?
>
> Thanks
>
> Scott KB7DZR
>
>

On 2/11/2013 8:08 PM, Scott Miller wrote:
>> You can access the messaging interface over the GPS port.
> Not with the GTRANS you can't.  If there's messaging support on the GPS
> port, it's for the AvMap.  I don't think that was implemented when I got
> my D710.  Is there an update?

And documentation?  Especially if said messaging interface appears on
the GPS port of the D72 in some future firmware update!

Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32

Do you have documentation on the AvMap messaging interface protocol?  If
it is open, I could implement such an interface to the D710 and have it
ready if they ever support it on the D72's GPS/RS-232 port.

Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32

On 2/11/2013 8:37 PM, Scott Miller wrote:
> I did implement AvMap support - it ought to be in the development built
> at least, but I haven't gotten around to documenting it yet.  I'll be
> happy to jump on that if someone wants to do some beta testing.
>
> I saw a few in stock today.  Some of them look a little different than
> the pictures - we just got a new board revision in that's about 1/3
> smaller and has the USB connector on the side to avoid having to route
> the cable at an odd angle, but otherwise it works the same.
>
> Scott
>
> On 2/11/2013 9:39 AM, offtracks1 wrote:
>> Been running Argent gear for a long time.
>>
>> My T2-301 and nuvi 350 has been a super package. Been looking and making
>> some gear changes and I need some info on the T3-135 for the Alinco.
>>
>> Can it be connected to the New AvMap 6 and will messaging and all other
>> features work?
>>
>> Will it display weather data ect on the AvMap. like it would when
>> connected to a Kenwood?
>>
>> I see the it is currently out of stock, any idea to when it may be back
>> in stock?
>>
>> Thanks
>>
>> Scott KB7DZR
>>
>>
>
> ------------------------------------
>
> Yahoo! Groups Links
>
>
>
>

On Mon, Feb 11, 2013 at 6:08 PM, Scott Miller <scott@...> wrote:

>> You can access the messaging interface over the GPS port.
>
> Not with the GTRANS you can't.  If there's messaging support on the GPS
> port, it's for the AvMap.  I don't think that was implemented when I got
> my D710.  Is there an update?

Back up the train... I'm not sure where my head was when I wrote that!
I think it might have been wishful thinking or something. The AvMap
supports messaging via specific sentences, and Kenwood does not
support them.

I plead too many toys and not enough brain cells!

I sure would like it if Kenwood would make a liar out of me though!

--
James
VE6SRV

But why the heck is Australia so strict on HAB activity, with similar
land area to the US and 1/10th the population?

Scott

On 2/10/2013 5:28 PM, Matthew Cook wrote:
> I'll second James comments regarding the PATH in your APRS payload...
> Here in Oz we use custom HAB hardware and firmware
> (http://rfhead.net/?p=476) that has no path included in the out going
> fraome until the balloon has burst and is on decent and dropping below
> 3000' ASL..  We used to run WIDE2-1 but that as James suggests causes
> alot of noise on the ground...   Using the wides means we do get some
> assistance from other digi's and iGates, but keep in mind there are only
> 3 iGates and 8 or so digi's in the entire of South Australia we don't
> have the same sort of population densities found elsewhere... out where
> our balloons land we need to use at least one digi to skip over a
> mountain range and back into Adelaide to hit the iGates... although
> there will be rPi in the truck soon running my own Rx only iGate, yes we
> have better mobile coverage out this far in the country that we do
> repeaters at times...  Unless we're flying one on the balloon that is...
>
> In all of our launches we use two telemetry systems with ARPS as the
> backup.  The primary system is a 25mW RTTY 70cm module that sends
> continuous data.  It's the same one the guys in the UK use check out
> http://www.spacenear.us/tracker for more details.
>
> In the car we use the D710 and on foot you can't beat the D72's.  In the
> car the D710 is in the front seat where I can see it, we also have a
> bluetooth dongle on the serial port for feeding to our telemetry systems
> (with bigger screens) in the back seat.  You can see most of the gear in
> the truck (toyota hilux) here..
> (http://projecthorus.org/?page_id=2224).. Yours truly is the one with
> the beard.  Having custom gear helps recover all of your payloads...
> We've only truly lost one, sacrifced three out of 30 launches.  We've
> also flown 3D cameras worth more than our trucks.
>
> Since we fly with primary 70cm and backup 2m APRS telemetry we've not
> "lost" communciation with our balloons for quite some time..  The
> Australian Civil Aviation and Safety Authority (CASA) are rightfully
> quite strict on who can fly HAB payloads here in Australia (we're
> actually licensed to do so with our own Balloon Airport in the Adelaide
> Hills) and we are required to keep in contact with our balloons at all
> times..  We've also got a couple of "restricted zones" we're not allowed
> to fly into (north of Adelaide) which makes life fun (read on).
>
> However we also run the CUSF HAB prediction software on where flights
> and roughly know where they are likely to go ie
> (http://www.projecthorus.org/predict/)..   We've found that using the
> CUSF predictor (and some knowledge about the balloons you're using) that
> our payloads drop within a 50km radius of the predicted landing site,
> once we have the wind data on accent this narrows to only 5km.  We
> usually run scenarios on the weather in the week leading up to the
> launch.   Being able to get within 5kms of the general landing area
> means we can find any 25mW signal with a 7el beam and a good receiver.
> If you poke around the Project Horus site you'll find many videos (ie
> Horus 7) of where we've launched, driven and then watched/video'd the
> balloon land, all simply based on the predictions.
>
> 73's
>
> Matthew
> VK5ZM
>
> On 11 February 2013 04:36, James Ewen <ve6srv@...
> <mailto:ve6srv@...>> wrote:
>
>     __
>
>     On Fri, Feb 8, 2013 at 9:54 PM, Eric Fort eric.fort@...
>     <mailto:eric.fort%40gmail.com>> wrote:
>
>      >> Are you limiting the equipment used in the chase to just the radio,
>      >> OT2, and Nuvi350? Will you have a laptop along as well?
>      >
>      >
>      > I'd rather just use the nuvi 350 and t2-301, otherwise what's the
>      > advantage of the t2-301 nuvi combo? If I need a laptop I might as
>     well just
>      > run soundmodem on the laptop and attach that to a radio.
>
>     You tell me what the advantage is... The only advantage I see is less
>     equipment in the vehicle, but you are limited to the capabilities of
>     the equipment chosen. I love the OpenTracker line. I have over a dozen
>     OTUSB/OT2/OT3 units, and an R-Trak HAB as well... they all have their
>     own specialized purposes. However I run my Kenwood D710 and AvMap G6
>     in the truck because the capabilities available in those devices
>     provide me with the desired functionality. I also run a TH-D72 as my
>     handheld unit. The two Kenwood devices and the AvMap give me
>     everything I need to be able to chase and recover HAB payloads. I
>     can't achieve the same level of functionality with the OT line and the
>     Nuvi350.
>
>     When chasing balloons however, I add on the laptop (or WebDT366) so
>     that I get an even larger screen, a historic track of the payload
>     path, packet logs, and a bunch more functionality that I can't get out
>     of the Kenwood and AvMap G6.
>
>
>      > What about using some creative scripting on the t2 to limit what
>     the nuvi
>      > sees? Any possibilities there?
>
>     Not that I can think of. We don't have access to manipulating the
>     incoming data stream. That would take a fair bit of processor power,
>     and a lot of memory to be able to provide enough commands to parse out
>     packets and manipulate them based on your own criteria.
>
>
>      >> You could get the altitude of the payload displayed on an AvMap GPS
>      >> connected to the OT2 though.
>      >
>      > AvMap? what are you referring to?
>
>     Uh, the AvMap GPS line... The current production model is the AvMap
>     G6. http://www.geosat.us/ It is a GPS built in Italy, but it has
>     firmware custom designed to support APRS built in. No other GPS
>     manufacturer supports APRS. The closest anyone else comes is Garmin,
>     and that's only because Scott has manipulated their Fleet Management
>     Interface into believing that APRS data is FMI data. We all know how
>     interested Garmin is in making the FMI mode work properly to support
>     live data from the APRS network.
>
>     The AvMap G6 is the latest in the AvMap line to support APRS. The G4
>     and G5 units also supported APRS functionality. With the G6, I can
>     tell the unit to follow a specified target (the balloon payload), and
>     I can have three windows open on the map screen showing me specific
>     data on that payload (I like speed, heading, and altitude when
>     chasing). I can tell the GPS to calculate a route to the payload (not
>     a good idea while the balloon is in flight, you want to head to where
>     it is going to land, not where it is currently), but when the payload
>     is on the ground, the GPS can direct you to the area.
>
>
>      >> If you attach a laptop, and run APRSISCE/32, you can have everything
>      >> you want, and have it displayed on a much larger screen.
>      >>
>      >
>      > I'll consider that as an option, but then doesn't that defeat the
>     entire
>      > point of the nuvi/t2-301 combo?
>
>     That all depends on what the point of the T2-301 and Nuvi is... If you
>     want a small minimal component count APRS station with the ability to
>     see incoming icons on the screen, and the ability to send and receive
>     messages on screen, then you've probably got the right package.
>
>     If you want to be able to limit the incoming display to just a single
>     specific station, or group of stations, and to be able to see the
>     altitude of a specific station on screen, then you probably don't have
>     the right package.
>
>     Ham radio is a niche market. APRS is a niche market in the ham radio
>     niche market. HAB tracking is a niche market in the APRS niche market
>     of the ham radio niche market. Most manufacturers aim to position
>     their products to hit the largest market possible. The fact that AvMap
>     is producing a product that supports APRS is amazing, and then they
>     also have features that cater to the HAB niche is even more amazing.
>
>     You can't sit in a rowboat in the middle of a corn field in Nebraska
>     and wonder why you're not flying to London. Sometimes you need
>     specialized equipment to perform a specialized task. :)
>
>     As Brian suggested, perhaps using a unique frequency would give you
>     the ability to limit the stations heard. Hopefully you are aware that
>     once your payload is aloft, there is no need to run an outgoing path.
>     With the payload over 1000' AGL, asking for digipeats is a waste of
>     time. Your payload will transmit much further than any ground based
>     digipeater around. Moving to a frequency with no digipeaters available
>     does not affect your ability to track. You can have ground based
>     stations switch to the unique frequency and i-gate your packets so
>     they appear on the APRS-IS stream.
>
>     Many HAB groups run paths at altitude, which just causes all kinds of
>     unnecessary noise on the ground. Dozens to hundreds of digipeaters end
>     up repeating packets that are easily copied by every station on the
>     ground already. Even worse people run with WIDE1-1 as a path request,
>     causing not only every digipeater to act upon the packet, but every
>     home fill-in digipeater as well.
>
>     If you are running a quality HAB APRS tracking payload, you'll have
>     the ability to change paths based on profile switching. Set up your
>     profile switching to use no path on one profile, and then once the
>     payload has dropped below something like 5000 feet, add an outgoing
>     path to ask for help from the digipeaters. If you land somewhere a
>     long distance from an i-gate, and your chase teams have managed to not
>     keep up with the payload, a digipeat *might* help you get closer.
>
>     Many people feel that if the payload can't be heard on the ground via
>     the APRS-IS stream, that there's no possible way of recovering the
>     payload. That is not the case. We've had payloads stop being gated at
>     20,000 feet AGL and still been able to find them on the ground. You
>     simply extrapolate the flight path based on the winds seen on the way
>     up and go to the projected area. If need be set up a search grid and
>     search until you can hear your payload.
>
>     If you have a frequency agile payload, you can have the unit switch
>     back and forth between your unique frequency and 144.390, and get the
>     best of both worlds.
>
>     --
>     James
>     VE6SRV
>
>
>
>
> --
> Matthew
> VK5ZM
> 0487 653 245
>
>

How are you turning on and off the digi function?  You could probably
set up a script to do what you want.

Scott

On 2/11/2013 6:29 AM, Thomas wrote:
>
>
> --- In tracker2@yahoogroups.com <mailto:tracker2%40yahoogroups.com>,
> Scott Miller wrote:
>  >I understand the reason for that design. I am using the OT as an
> unattended tracker and let the OT power up my radio when it's time for a
> beacon. In attended mode I power on my radio manually and turn on the
> digi function. When I go back to unattended mode I have to "power down"
> the relay with the power off command or switch the power off and on to
> the tracker.
> Otherwise I leaves my radio with the power on.
> But I can handle the situation know when I am aware of the design.
>
> Thanks
> /Thomas
>
>  > It was always assumed in the design that you wouldn't use power control
>  > with a digi, since it can't receive packets to digipeat when it's turned
>  > off...
>  >
>  > Scott
>  >
>  > On 2/9/2013 2:11 AM, Thomas wrote:
>  > > It seems to be the same problem with power control when digi as for
> aprs
>  > > message.
>  > > I am using my excellent tracker as a digipeater but the power relay
>  > > stays on after sending out the packet
>  > > Firmware: 56330
>  > >
>  > > Thomas SM0YOS
>  > >
>  > >
>  >
>
>

I am using the USEALIAS 1 ON/OFF command, good idea to set up a script
I will try that

Thomas

--- In tracker2@yahoogroups.com, Scott Miller  wrote:
>
> How are you turning on and off the digi function?  You could probably
> set up a script to do what you want.
>
> Scott
>
> On 2/11/2013 6:29 AM, Thomas wrote:
> >
> >
> > --- In tracker2@yahoogroups.com ,
> > Scott Miller wrote:
> >  >I understand the reason for that design. I am using the OT as an
> > unattended tracker and let the OT power up my radio when it's time for a
> > beacon. In attended mode I power on my radio manually and turn on the
> > digi function. When I go back to unattended mode I have to "power down"
> > the relay with the power off command or switch the power off and on to
> > the tracker.
> > Otherwise I leaves my radio with the power on.
> > But I can handle the situation know when I am aware of the design.
> >
> > Thanks
> > /Thomas
> >
> >  > It was always assumed in the design that you wouldn't use power control
> >  > with a digi, since it can't receive packets to digipeat when it's turned
> >  > off...
> >  >
> >  > Scott
> >  >
> >  > On 2/9/2013 2:11 AM, Thomas wrote:
> >  > > It seems to be the same problem with power control when digi as for
> > aprs
> >  > > message.
> >  > > I am using my excellent tracker as a digipeater but the power relay
> >  > > stays on after sending out the packet
> >  > > Firmware: 56330
> >  > >
> >  > > Thomas SM0YOS
> >  > >
> >  > >
> >  >
> >
> >
>

Anyone on the forum have a LM355Z connected to an analog channel(CN4 pins 3 thru
6)? If yes, I would like to take a look at the raw telemetry data on aprs.fi

Thanks
John N9TKF

That's probably best.  Even if I was to add power control to digi
transmissions, it would be on a transmission-by-transmission basis and
wouldn't do what you want.  You can just define a macro, or use profile
switching to alternate between attended and unattended operation.

Scott

On 2/13/2013 6:09 AM, Thomas wrote:
>
>
> I am using the USEALIAS 1 ON/OFF command, good idea to set up a script
> I will try that
>
> Thomas
>
> --- In tracker2@yahoogroups.com <mailto:tracker2%40yahoogroups.com>,
> Scott Miller wrote:
>  >
>  > How are you turning on and off the digi function? You could probably
>  > set up a script to do what you want.
>  >
>  > Scott
>  >
>  > On 2/11/2013 6:29 AM, Thomas wrote:
>  > >
>  > >
>  > > --- In tracker2@yahoogroups.com <mailto:tracker2%40yahoogroups.com> ,
>  > > Scott Miller wrote:
>  > > >I understand the reason for that design. I am using the OT as an
>  > > unattended tracker and let the OT power up my radio when it's time
> for a
>  > > beacon. In attended mode I power on my radio manually and turn on the
>  > > digi function. When I go back to unattended mode I have to "power down"
>  > > the relay with the power off command or switch the power off and on to
>  > > the tracker.
>  > > Otherwise I leaves my radio with the power on.
>  > > But I can handle the situation know when I am aware of the design.
>  > >
>  > > Thanks
>  > > /Thomas
>  > >
>  > > > It was always assumed in the design that you wouldn't use power
> control
>  > > > with a digi, since it can't receive packets to digipeat when it's
> turned
>  > > > off...
>  > > >
>  > > > Scott
>  > > >
>  > > > On 2/9/2013 2:11 AM, Thomas wrote:
>  > > > > It seems to be the same problem with power control when digi as for
>  > > aprs
>  > > > > message.
>  > > > > I am using my excellent tracker as a digipeater but the power relay
>  > > > > stays on after sending out the packet
>  > > > > Firmware: 56330
>  > > > >
>  > > > > Thomas SM0YOS
>  > > > >
>  > > > >
>  > > >
>  > >
>  > >
>  >
>
>

Thanks Scott

I may be looking into setting a new system in the next few months.

Scott KB7DZR

--- In tracker2@yahoogroups.com, Scott Miller <scott@...> wrote:
>
> I did implement AvMap support - it ought to be in the development built
> at least, but I haven't gotten around to documenting it yet.  I'll be
> happy to jump on that if someone wants to do some beta testing.
>
> I saw a few in stock today.  Some of them look a little different than
> the pictures - we just got a new board revision in that's about 1/3
> smaller and has the USB connector on the side to avoid having to route
> the cable at an odd angle, but otherwise it works the same.
>
> Scott
>
> On 2/11/2013 9:39 AM, offtracks1 wrote:
> > Been running Argent gear for a long time.
> >
> > My T2-301 and nuvi 350 has been a super package. Been looking and making
> > some gear changes and I need some info on the T3-135 for the Alinco.
> >
> > Can it be connected to the New AvMap 6 and will messaging and all other
> > features work?
> >
> > Will it display weather data ect on the AvMap. like it would when
> > connected to a Kenwood?
> >
> > I see the it is currently out of stock, any idea to when it may be back
> > in stock?
> >
> > Thanks
> >
> > Scott KB7DZR
> >
> >
>