[aprssig] IGate wildcards/Telpac data
A.J. Farmer (AJ3U) ajfarmer at spenet.comTue Feb 15 17:19:12 UTC 2005
- Previous message: [aprssig] IGate wildcards/Telpac data
- Next message: [aprssig] IGate wildcards/Telpac data
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
>Guess we should also force trackers to have speakers in the >vehicles (and be visible) so the operator is a good "steward" of the >network and doesn't transmit too often or get stuck on or uses too long >of a path or etc. etc. etc. You're missing the point. Nobody has to force anybody to do anything (except the FCC - hi) but monitoring your equipment makes you a responsible operator. I'm not talking about 24x7 monitoring and having a speaker on your tracker. That is silly. I'm talking about just checking on things now and then. I thought this was common sense. This includes IGates, Digi's, trackers - any transmitter. If you set up any transmitter and *never* spot check it now and then to make sure it is operating properly, then that is irresponsible. -----Original Message----- From: aprssig-bounces at lists.tapr.org [mailto:aprssig-bounces at lists.tapr.org] On Behalf Of AE5PL Lists Sent: Tuesday, February 15, 2005 11:47 AM To: TAPR APRS Mailing List Subject: RE: [aprssig] IGate wildcards/Telpac data > -----Original Message----- > From: A.J. Farmer (AJ3U) > Posted At: Tuesday, February 15, 2005 10:31 AM > Subject: RE: [aprssig] IGate wildcards/Telpac data > > I don't think we should stray from the AX.25 specs for > convenience or filtering purposes. > > Should we start prefixing weather stations with WX- , > balloons with BA- , Digi's with DI- , etc. ? Of course not. You could and it wouldn't hurt a thing (other than findu). Don't get hung up on the AX.25 spec when it comes to APRS-IS. We do not use AX.25 on APRS-IS. We use text/binary strings that loosely follow the TNC-2 monitor mode format. As Bob points out, that has always been assumed to mean ANY 9 characters for a callsign-SSID. > As far as IGate wildcards, I also agree that it should be > discouraged. By restricting the use of wildcards, it > encourages IGate operators to monitor and attend to their > stations which is part of network stewardship. To many "set > it and forget it" abilities when dealing with the tremendous > amount of data on the APRS-IS combined with an unattended > IGate just opens up the network to potential problems. Maybe so. Guess we should also force trackers to have speakers in the vehicles (and be visible) so the operator is a good "steward" of the network and doesn't transmit too often or get stuck on or uses too long of a path or etc. etc. etc. Most of the APRS RF bandwidth is consumed by these types of problems, not IGate operators "set it and forget it" abilities. Many IGates are similar to digipeaters: located in places where "set it and" (more accurately) don't change it is not only desirable but necessary. 73, Pete Loveall AE5PL mailto:pete at ae5pl.net _______________________________________________ aprssig mailing list aprssig at lists.tapr.org https://lists.tapr.org/cgi-bin/mailman/listinfo/aprssig
- Previous message: [aprssig] IGate wildcards/Telpac data
- Next message: [aprssig] IGate wildcards/Telpac data
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the aprssig mailing list
