Ooops. I may have an explanation for my problem.
When I set up my 100 mile filter on the socal.aprs2.net
INET interface, I used rounded LAT/LON numbers,
which put the center of my filter 20 to 30 miles away
from me. The stations I was missing were within 100
miles of me but maybe not the center
On Aug 24, 2007, at 4:56 PM, Curt, WE7U wrote:
On Wed, 22 Aug 2007, Craig Anderson wrote:
Or is it that Xastir marks a site as being from the TNC
because it is first seen by the TNC?
I believe if it is heard by the TNC at all (doesn't have to be
first?) the flag gets set. Xastir treats RF-
On Wed, 22 Aug 2007, Craig Anderson wrote:
> Or is it that Xastir marks a site as being from the TNC
> because it is first seen by the TNC?
I believe if it is heard by the TNC at all (doesn't have to be
first?) the flag gets set. Xastir treats RF-heard stations as a
higher priority than INET-hea
Yup, I have the callpass and I get no complaints.
I find it very strange. I see a lot of activity in my area
but a whole lot of sites that only show up through the
TNC. Some of these sites are digipeaters that show
up in the path on many NET sites. They are all within
my 100 mile filter and sh
Did you enter in the passcode for connecting to the server? This code
(numeric) is generated based on your callsign. There's a small
program that generates it (I believe it's called callpass although
someone may correct me).
The tier2 servers run the same software as the tier1 servers do -
there
Hi all,
I was trying to IGate into socal.aprs2.net
and it wasn't working. After investigating, I think
the aprs2.net machines want "Q codes" to be
included in the packets. Is this what is preventing
my packets to be included in the aprs2.net info?
Can Xastir IGate to these machines?
Tha
