[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: "Mike Edwards" <medwards@atlantic.net>
- Date: Mon, 27 Sep 1999 21:57:38 -0400
- 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>
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: lyris.ao16aprs@tapr.org
To unsubscribe send a blank email to leave-ao16aprs-833L@lists.tapr.org