[aprssig] Coverage in the National Parks
Robert Bruninga bruninga at usna.eduThu Apr 7 13:50:15 UTC 2005
- Previous message: [aprssig] UIDIGI and the New Paradigm - WARNING - LONG!
- Next message: [aprssig] Coverage in the National Parks
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
>>> jdw at eng.uah.edu 4/7/05 8:55:16 AM >>> >If most digis already support WIDE1-1, why don't we >skip the WIDE1-1,WIDE2-1 step and go directly to >WIDE2-2? Sure, WIDE2-2 also works everywhere and is the number one main recommendation for everyone that will work everywherer as a minimum path. The only reason that WIDE1-1,WIDE2-1 was added as an option was for those rurual areas of the country that have lots of FILL-IN "relay-only" digis. Those areas are suffering a seer dupe problem caused by the use of the RELAY path, and so changing RELAY to WIDE1-1 completely solves all that while still providing the same performance for those users... >And why WIDE2-1 instead of a second WIDE1-1? Because when using the 2 hop path of WIDE1-1,WIDE2-1 the first hop has already been accounted for so the second hop should already be decremented by one. And as was widely discussed here, just like one should ever use RELAY in any position other than the first, the same goes for its new substitute, WIDE1-1. It should never be anywhere but the start of a packet. Otherwise it has the potential to cause QRM from all the FILL-IN digis that support it. Bob, WB4APR -Jason kg4wsv _______________________________________________ aprssig mailing list aprssig at lists.tapr.org https://lists.tapr.org/cgi-bin/mailman/listinfo/aprssig
- Previous message: [aprssig] UIDIGI and the New Paradigm - WARNING - LONG!
- Next message: [aprssig] Coverage in the National Parks
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the aprssig mailing list
