Order Tray | Contact Us | Home | SIG Lists

[aprssig] Need help solving an IGate problem

Keith VE7GDH ve7gdh at rac.ca
Wed Oct 31 23:12:32 UTC 2012


John AB0OO wrote...

> I seem to have a packet-delaying station somewhere in North Georgia...

2012-10-30 19:44:09 UTC:
KD4K-9>S4QP9V,WIDE1-1,WIDE2-1,qAR,N4NE-1
:`p_~l#;>/"8*}Tony from Cumming, GA

2012-10-30 19:46:49 UTC:
KD4K-9>S4QP9V,N4NE-1,WIDE1,W4GR-10,WIDE2*,qAR,KG4MUW
:`p_~l#;>/"8*}Tony from Cumming, GA [Duplicate position packet]

The second copy was delayed by about 2 minutes 40 seconds.

It could have been either N4NE-1 or W4GR-10 if it was
delayed by a digi, or could have been KG4MUW if it was
delayed by the IGate.

However, N4NE-1 was the IGate the first time around. Assuming
that N4NE-1 the digi and N4NE-1 the IGate are one and the same
station, and that the delayed copy was digipeated first by N4NE-1,
it would tend to rule N4NE-1 out as being responsible. That
leaves W4GR-10  or KG4MUW. Based on other evidence I
see, I would put my money on KG4MUW.

However...

2012-10-30 19:55:11 UTC:
KD4K-9>S4QP6S,WIDE1-1,WIDE2-1,qAR,N4NE-1
:`p_mmJ*>/"7{}Tony from Cumming, GA

2012-10-30 19:57:40 UTC:
KD4K-9>S4QP6S,N4NE-1*,WIDE1*,W4GR-10*,WIDE2*,qAR,N4NE-1
:`p_mmJ*>/"7{}Tony from Cumming, GA [Duplicate position packet]

That's a 2 minute 29 second delay. This one is interesting
because it was heard direct and gated by N4NE-1 first,
and apparently also digipeated by it, and then later gated
by N4NE-1 again. That leaves it appearing that W4GR-10
caused the delay.

That leads me to conclude that there's more than one source of
delays in your area.

PS - if KD4K-9 didn't send out "Tony from Cumming, GA"
with every single beacon, it would increase his chances of
success and leave more time slots available for others. It
doesn't change, so he could send it e.g. just every 10 beacons.

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




More information about the aprssig mailing list