[aprssig] Ambiguity due to GPS
Scott Miller scott at opentrac.orgThu Jan 5 23:58:08 UTC 2006
- Previous message: [aprssig] Ambiguity due to GPS
- Next message: [aprssig] New and improved APRS
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
> His transmissions amount to about 16 packets per minute, not counting > digipeats. If we had multiple stations sending this kind of > data at this > rate, the local network will quickly become unusable. > > We really need to encourage developers to prohibit these > types of abuses on > 144.39. IMO, permitting a user to send such a volume of traffic at 10 > second intervals should be reconsidered. I'm not opposed to adding more informative text to the manual, but I will not *prohibit* the user from doing anything they feel is appropriate. Sending 16 packets per minute on 144.39 is obviously excessive, and the user probably needs to be politely corrected on that. But I've personally configured a tracker to send something like 140 packets/minute, which is perfectly acceptable for telemetry applications on a dedicated channel. Won't work too well with a digipeater, though! Scott N1VG
- Previous message: [aprssig] Ambiguity due to GPS
- Next message: [aprssig] New and improved APRS
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the aprssig mailing list
