[aprssig] PacComm Digipeater update (FREQ objects)
Bob Bruninga bruninga at usna.eduWed Feb 1 19:30:59 UTC 2012
- Next message: [aprssig] How should CAP 1.2 standard Emergency Alerts from the Google.org Alert Hub project appear in a local APRS tactical picture ?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
I just noticed that the PacComm digipeater setup info on my web pages did not include the current recommendation for local FREQ objects. The file has now been updated. As before, it is found on the http://aprs.org/fix14439.html web page. Basically it takes the two available beacons, and sets one for the digi (direct every 10 m) and the other for the FREQ object (direct every 10 minutes). Thus the local traveler gets all he needs to know in 10 minutes and since these beacons are originated at the digi that hears-all, then they add zero load to the network. We do NOT want these originated at ground level home stations. They take twice the bandwidth and can collide with other user users. So, originating them at the DIGI only is best. If your digi is not outputting your locally recommended FREQ and TONE objedct, then take a personal initiative and get'er'done. See http://aprs.org/localinfo.html With PL tones on every repeater it is painful to drive into an area and hear a QSO and not be able to join because you don't know the tone. If there is no QSO, then it is even worse, since you don't even know what repeater is there! This LOCAL INFO is fundamental to APRS. Get'er'done! Bob, Wb4APR
- Next message: [aprssig] How should CAP 1.2 standard Emergency Alerts from the Google.org Alert Hub project appear in a local APRS tactical picture ?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the aprssig mailing list
