[aprssig] KPC3+ WIDE setup

Christopher K. Greenhalgh chris at n8wct.com
Sat Jan 31 11:02:26 EST 2009

>I see you are creatively deviating from the www.aprs.org/fix14439.html
recommendations apparently so that you can have more local objects. 


> If these objects are useful, then your settings do make sense.  Buf first,
there is no need to have the FREQ both in the object name and in the object

;146.760-V*111111z3957.42N/08259.90Wr146.760MHz T123 R40m W8RXX


;146.760-V*111111z3957.42N/08259.90WrT123 R40m W8RXX...........

Makes sense.

>Also, we can improve on the timing somewhat.. instead of having the random
walk of packets from 4 different timers as you do here...

I purposely mad it random...seems many other stations "schedule" their
transmissions at 10, 20, 30, ect minute intervals, starting at 00:00:00 or
the like. This causes collisions, delays, and lost data.

>Which would fit perfectly (28 bytes) onto the D700 display.  If you do keep
the ">" STATUS format, then there is no need for the null 111111z field.
That is not needed in a STATUS packet.  


>The problem of having both a STATUS packet and a position packet is that
they overwrite each other on all the mobiles (D7, D700, D710, VX8R) and so
you never see them both.  I'd say combine them.  Then use the START
parameter in the BLT's so that you can get all your beacons on a standard
synchronized cycle like this:

> 1 EVERY 00:20:00 START 00:00:00  (direct
> 2 EVERY 00:20:00 START 00:05:00  (direct
> 3 EVERY 00:20:00 START 00:15:00  (direct
> 4 EVERY 00:20:00 START 00:10:00  (via 1 hop

20 minutes is too long for a repeater object. If the repeater range is 40
miles, and a mobile station drives through town at 70 mph, he could drive
over 20 miles before "seeing" the object. Even 17 minutes might be too long,
but I don't really want to go any lower to alleviate QRM.

Chris Greenhalgh, N8WCT

More information about the aprssig mailing list