[aprssig] ID requirements...
scott at opentrac.org scott at opentrac.orgSun Nov 7 20:44:44 UTC 2004
- Previous message: [aprssig] ID requirements...
- Next message: [aprssig] ID requirements...
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
It's not illegal, I just think that as far as APRS goes, it's impolite to not send an ID along with the same path as your data. If bandwidth is a concern, just do the full-path ID less often, if your tracker will support it. Even if you only send it every 30 or 60 minutes, at least I can look on FindU and see who's responsible for a tracker if it's causing a problem. Scott N1VG -----Original Message----- From: aprssig-bounces at lists.tapr.org [mailto:aprssig-bounces at lists.tapr.org]On Behalf Of Mike Yetsko Sent: Sunday, November 07, 2004 12:43 PM To: ron.stordahl at digikey.com; TAPR APRS Mailing List Subject: Re: [aprssig] ID requirements... Just remember that there is NO requirement that ANY transmission of an ID has to go anywhere. It just has to be made 'on the air' by the actual transmitting station. Along with that, a repeater does NOT fulfull the requirement if it broadcast an 'inputs' ID. However, an 'input' signal CAN send and ID for itself, AND for the repeater. I know of a case where one of the 'tin cop' OOs issued warnings to individuals when they either ran out of coverage of a local repeater, or the repeater 'timed out' and shut down. This little tin cop thought he was being cool with 'official warnings' until he was shown the rules. That's not to say the people didn't break the rules. But just because you can't hear an ID through the repeating device does NOT mean it's a violation. _______________________________________________ aprssig mailing list aprssig at lists.tapr.org https://lists.tapr.org/cgi-bin/mailman/listinfo/aprssig
- Previous message: [aprssig] ID requirements...
- Next message: [aprssig] ID requirements...
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the aprssig mailing list
