Order Tray | Contact Us | Home | SIG Lists

[aprssig] who hears my station - now reading raw data

Keith - VE7GDH ve7gdh at rac.ca
Sun Dec 25 01:34:30 UTC 2005


Joe N3HGB wrote on Dec 24 2005

> I have no problem with my tracker, which is on my boat. I was just
> wondering if I can see all the digis that have picked it up on the
> first try.

See this site for the raw data from N3HGB-5 (or substitute whatever
callsign-SSID you are interested in)
www.findu.com/cgi-bin/raw.cgi?call=N3HGB-5&time=1

The following tells you only that you have been through one WIDEn-n
digi and that KB2M gated your beacon. The digipeater unfortunately
didn't identify itself.
20051224003711,N3HGB-5>SX5Y2W,WIDE3-2,qAO,KB2M:`h-"l Y/

The following tells you that you went through WX2NJ-13 & W1NLC-15
(apparently both WIDEn-n digis) and that you were gated by N1OFZ-15.
As the path is down to WIDE3, my reading on that would be that one
more WIDEn-n digi was involved, but unfortunately it did not identify
itself. Your path was "all used up" but you made it to an IGate.
20051224031550,N3HGB-5>SX5Y2W,WX2NJ-13,W1NLC-15,WIDE3*,qAR,N1OFZ-15:`h-"l
Y\

The following tells you that you went through WB4APR-1 (that callsign
sounds familiar) & W3GXT-2 and that you could have gone "one more hop"
if another WIDEn-n digi heard W3GXT-2
20051224230444,N3HGB-5>SX5Y2V,WB4APR-1,W3GXT-2*,WIDE3-1,qAo,N3GXH-1:`h-"l
Y/

As I mentioned earlier, not all digipeaters properly inject their
callsign. Try and talk the digi operators in your area to upgrade the
settings in their digipeaters. See the following for the reasons for
the "new" settings. www.ew.usna.edu/~bruninga/aprs/fix14439.html
The NWAPRS site at www.nwaprs.org might be helpful for the actual TNC
settings.

73 es cul - Keith VE7GDH
--
"I may be lost, but I know exactly where I am!"





More information about the aprssig mailing list