[aprssig] How should this work -> TRACE WIDE2-2
Herb Gerhardt hgerhardt at wavecable.comThu Sep 15 04:54:30 UTC 2005
- Previous message: [aprssig] How should this work -> TRACE WIDE2-2
- Next message: [aprssig] How should this work -> TRACE WIDE2-2
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Here in the Seattle Area we have a station that sends out this automated bulletin over RF to our APRS network to try to inform travelers of the path requirement. Granted a "smart" tracker that can accept messages is required to read these bulletins, but it is an attempt of informing our travelers. KA7PBI-12 BLNA 37 09/14 07:30 path=WIDE1-1,WIDE2-1 for mobiles --tnx Herb, KB7UVC NW APRS Group, West Sound Coordinator Our WEB Site: http://www.nwaprs.info > -----Original Message----- > From: aprssig-bounces at lists.tapr.org > [mailto:aprssig-bounces at lists.tapr.org]On Behalf Of N0YXV - Stan Coleman > Sent: Wednesday, September 14, 2005 9:10 PM > To: 'TAPR APRS Mailing List' > Subject: RE: [aprssig] How should this work -> TRACE WIDE2-2 > > > I've also taken the liberty to send messages to passing travelers that > our area is now WIDEn-N. That way they can make changes for the next > trip.
- Previous message: [aprssig] How should this work -> TRACE WIDE2-2
- Next message: [aprssig] How should this work -> TRACE WIDE2-2
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the aprssig mailing list
