On Sat, Jul 4, 2009 at 9:46 AM, Curt, WE7U<[email protected]> wrote: >>> The FCC assigned callsign is embedded in a packet that gets sent every >>> 10 minutes for all you armchair lawyers. > > Speaking of armchair lawyers, don't you only have send it every 30 > mins? You're not as restrictive as we are down here...
Yeah, yeah... again, written for the silly 'mericans! When I first set up the W7VOI Bogus Basin digipeater timing for Mike W7MJR, I worked out a timing scheme that would allow the use of a tactical callsign, yet still meet the FCC requirements of sending the assigned callsign on a 10 minute schedule. We could stretch it out to 30 minutes in Canada, but I'm happy with a 10 minute net cycle time for infrastructure. Keeping it consistent across the continent means less confusion for the end users. Mike had tried to set up a proportional path timing concept, but like most of the people trying to do so at the time, he missed a crucial concept. Here's the original configuration that Mike had, with my comments about the settings... http://members.shaw.ca/jewen/aprs/Shafer.htm This was quite a common implementation at that time. My first concept of proportional paths, and D7/D700 optimized screens can be seen here... http://members.shaw.ca/jewen/aprs/SHAFEROPT.htm Obviously we have refined things even more since then. Curt, you'll remember back in late 2003, early 2004 when the NWAPRS group started playing with using a traceable outgoing path, and then into 2005 when we went through all the discussion about implementing the New WIDEn-N Paradigm settings. It was interesting trying to get Bob Bruninga to understand the timing/distance concept I laid out for Shafer... Bob wasn't interested, but a year later, we changed the whole APRS network to not only use the proportional path/timing settings, but also made the default APRS behaviour to be traceable... http://groups.yahoo.com/group/nwaprs/message/2817 Any progress is good progress! James VE6SRV
