[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
[ao16aprs] Re: Path Statement
- To: "TAPR AO-16 APRS Special Interest Group" <ao16aprs@lists.tapr.org>
- Subject: [ao16aprs] Re: Path Statement
- From: "Tim Cunningham" <tim_cunningham@mindspring.com>
- Date: Mon, 27 Sep 1999 21:23:22 -0500
- List-Owner: <mailto:owner-ao16aprs@lists.tapr.org>
- List-Software: Lyris Server version 3.0
- List-Subscribe: <mailto:subscribe-ao16aprs@lists.tapr.org>
- List-Unsubscribe: <mailto:leave-ao16aprs-833L@lists.tapr.org>
How to set the PATH to Digipeat via the PACSAT's:
Depending on what method you use, the following will work
for digipeating your BTEXT or beacon text setting:
UNPROTO APRS VIA PACSAT-1
The example above applies to AO-16. For LO-19 and
IO-26 replace PACSAT-1 with LUSAT-1 or ITMSAT-1
respectively.
When I am mobile I use the following path in case there is
a link from a SATGATE to a terrestrial path:
UNPROTO APRS VIA PACSAT-1,WIDE,WIDE
If you are using a TNC that supports the APRS mode of
operation using a GPS, you will need to set the LPATH
much like the UNPROTO path for your location path
beacons. For example:
LPATH APRS VIA PACSAT-1
This would send your location information to APRS via
PACSAT-1. I am using the PacComm v5.0 firmware in
an MFJ-1270 and typically use the following LPATH setting
from my Jeep:
LPATH APRS VIA PACSAT-1,WIDE,WIDE
I hope this helps everyone set the path correctly to digipeat
those APRS beacons via the PACSAT's. Just remember
UNPROTO is used to set the path for your beacon text or
BTEXT. LPATH is used to set the path for your location
beacons.
There are other forms of APRS support with other firmware,
but I have only given examples for the PacComm firmware
which may closely match other vendor implementations.
73's and happy APRS packeting,
Tim - N8DEU
Huntsville, Alabama
-----Original Message-----
From: Mike Edwards <medwards@atlantic.net>
To: TAPR AO-16 APRS Special Interest Group <ao16aprs@lists.tapr.org>
Date: Monday, September 27, 1999 8:58 PM
Subject: [ao16aprs] Re: Path Statement
>De Tim N8DEU:
>
>The callsign to digipeat APRS beacons on the birds
>is as follows:
>
>AO-16 PACSAT-1
>
>LO-19 LUSAT-1
>
>IO-26 ITMSAT-1
>
>(de Mike)
>
>I imagine you'd want that as the first hop (APRS VIA PACSAT-1), since
you're
>transmitting directly to the Sat on an isolated frequency (not the 144.39
>APRS frequency)..
>
>Mike KE4YGT
>
>
>-----Original Message-----
>From: Bob Hart <rahart@hctc.com>
>To: TAPR AO-16 APRS Special Interest Group <ao16aprs@lists.tapr.org>
>Date: Monday, September 27, 1999 6:00 PM
>Subject: [ao16aprs] Path Statement
>
>
>>I guess I must have been totally absorbed in finding parts in my junk box,
>>etching a board and wiring the $2 mod into my TNC. I either failed to take
>>note or it hasn't been stated what the path statement is to digi via the
>>satellites. Someone pleas give me and example of how to digi through
>AO-16.
>
>
>
>---
>You are currently subscribed to ao16aprs as: tim_cunningham@mindspring.com
>To unsubscribe send a blank email to leave-ao16aprs-833L@lists.tapr.org
>
---
You are currently subscribed to ao16aprs as: lyris.ao16aprs@tapr.org
To unsubscribe send a blank email to leave-ao16aprs-833L@lists.tapr.org