[aprssig] BIG-TALL digis that hear FAR too MUCH!
aprs at kd4rdb.com
Tue Dec 14 21:57:45 CST 2004
I'm doing somewhat the same.... I got one of the locals to setup his home digi
on 144.99/39 and I transmit at a rate of 12seconds via RELAY. This bounces me
off the 144.99 onto 144.39 and into the local IGATE. Using this method I'm
very clearly able to see the boundaries of coverage for his digipeater. No
hidden transmitter problems to contend with. Of course this high beacon rate
_must_ be used with 0 or 1 hop, and NO more... and it's only for a
_short_term_test_ to find the boundaries. Later we'll test coverage with two
other stations in the area and determine who will end up being the best choice
for the alt input digipeater. Since you should only have one per area,
location is pretty important.
The temporary high beacon rate allow me to map out holes in coverage that used
to take a month of trending to see.
I even created a GEO file of our town with an actual map of the town, and a 2nd
geo file with just a blank map. This allows me to pull multiple queries from
findu and easily overlay all of our mobile tracks onto one copy of the map. As
far as I know, findu does not allow multiple callsigns in a track query.
something to try tonight....
More information about the aprssig