Re: Bad digi at my location


Lynn Deffenbaugh
 

Almost, but with the Kwd710(APRS) port type, if APRSISCE/32 ever transmits, the D710's callsign-SSID switches to the APRSISCE/32 callsign-SSID and stays that way until the next radio/TNC reset. When I was developing this mode with a loaner D710, I had code that attempted to restore the radio's MYCALL setting, but it proved unreliable in my simple tests.

Now, if I could just persuade my son to spring for a D710 for his new (used) car, I'd have one to tinker with again.

Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32

On 9/26/2013 2:52 PM, Rob Giuliano wrote:


Isn't this the "poster child" for separate SSIDs for tracker/TNC capability and APRSISce/32 copmputer instance?
It appears to me that it, "at least", shows one example of what kind of issues that setup imposes.
Robert Giuliano
KB8RCO


---------------------------------------------

*From:* Lynn W Deffenbaugh (Mr) <kj4erj@arrl.net>
*To:* aprsisce@yahoogroups.com
*Sent:* Thursday, September 26, 2013 12:13 PM
*Subject:* Re: [aprsisce] Bad digi at my location

And one final thing. I send a ?VER from KJ4ERJ-12 which is an AX.25-compatible -SSID and received both an answer and an "rej".

2013-09-26 12:06:25 EDT: AB1OC-10>APWW10,TCPIP*,qAC,T2SJC::KJ4ERJ-12:ack1
2013-09-26 12:06:25 EDT: AB1OC-10>APWW10,TCPIP*,qAC,T2SJC::KJ4ERJ-12:2013/02/13 16:50: APRSIS32 Win v6.1 b7601 p2 0.0/2.8% [Duplicate message content]
2013-09-26 12:06:36 EDT: AB1OC-10>APK102,N8VIM*,WIDE1*,WIDE2-2,qAR,W1XM::KJ4ERJ-12:rej1
Yep, you see that right. I got a response from the APRSISCE/32 instance (>APWW10) and a reject from the D710 itself (>APK102). I apparently filled up the D710's message list with unread messages gated to it via RF by other local IGates. Split personality disorder. Is AB1OC-10 a D710 or is it an APRSISCE/32 instance. Well, it's BOTH! And another example of the power struggle between the two.

Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32

On 9/26/2013 12:07 PM, Lynn W Deffenbaugh (Mr) wrote:
And even more strangeness from AB1OC-10. I sent a ?APRSS and ?IGATE to that station from KJ4ERJ-AL and just noticed that it replied, not only to KJ4ERJ-AL, but also replied to KJ4ERJ (dropped the -SSID). Go figure!

2013-09-26 11:27:52 EDT: AB1OC-10>APWW10,TCPIP*,qAC,T2SJC::KJ4ERJ-AL:Ports[1/2] 09-23 10:00:36 APRS-IS OK 2505 2580 2533 2642 2626 2421+
2013-09-26 11:27:52 EDT: AB1OC-10>APWW10,TCPIP*,qAC,T2SJC::KJ4ERJ-AL:2255 2284 /hr
2013-09-26 11:27:52 EDT: AB1OC-10>APWW10,TCPIP*,qAC,T2SJC::KJ4ERJ-AL:Ports[2/2] 09-16 07:08:00 TM-D710 (APRS) OK 662 718 669 853 925+
2013-09-26 11:27:52 EDT: AB1OC-10>APWW10,TCPIP*,qAC,T2SJC::KJ4ERJ-AL:881 738 722 /hr DX=1*KB1ZIH-11(223mi@40<0xc2><0xb0>)
2013-09-26 11:27:54 EDT: AB1OC-10>APWW10,TCPIP*,qAC,T2SJC::KJ4ERJ :Ports[1/2] 09-23 10:00:36 APRS-IS OK 2509 2580 2533 2642 2626 2421+
2013-09-26 11:27:54 EDT: AB1OC-10>APWW10,TCPIP*,qAC,T2SJC::KJ4ERJ :2255 2284 /hr [Duplicate message content]
2013-09-26 11:27:54 EDT: AB1OC-10>APWW10,TCPIP*,qAC,T2SJC::KJ4ERJ :Ports[2/2] 09-16 07:08:00 TM-D710 (APRS) OK 664 718 669 853 925+
2013-09-26 11:27:54 EDT: AB1OC-10>APWW10,TCPIP*,qAC,T2SJC::KJ4ERJ :881 738 722 /hr DX=1*KB1ZIH-11(223mi@40<0xc2><0xb0>) [Duplicate message content]
2013-09-26 11:27:56 EDT: AB1OC-10>APWW10,TCPIP*,qAC,T2SJC::KJ4ERJ-AL:IGate[1/2] MSG_CNT=127 LOC_CNT=61 DIR_CNT=22 RF_CNT=75
2013-09-26 11:27:56 EDT: AB1OC-10>APWW10,TCPIP*,qAC,T2SJC::KJ4ERJ-AL:IGate[2/2] TM-D710 (APRS)[KWD710(APRS)] Bi-Directional+
2013-09-26 11:27:56 EDT: AB1OC-10>APWW10,TCPIP*,qAC,T2SJC::KJ4ERJ-AL:DX=1*KB1ZIH-11(223mi@40<0xc2><0xb0>)
2013-09-26 11:27:58 EDT: AB1OC-10>APWW10,TCPIP*,qAC,T2SJC::KJ4ERJ-AL:Ports[1/2] 09-23 10:00:36 APRS-IS OK 2513 2580 2533 2642 2626 2421+
2013-09-26 11:27:58 EDT: AB1OC-10>APWW10,TCPIP*,qAC,T2SJC::KJ4ERJ-AL:Ports[2/2] 09-16 07:08:00 TM-D710 (APRS) OK 668 718 669 853 925+

A ?VER just now did the same thing:

2013-09-26 12:05:23 EDT: AB1OC-10>APWW10,TCPIP*,qAC,T2SJC::KJ4ERJ-AL:2013/02/13 16:50: APRSIS32 Win v6.1 b7601 p2 0.0/2.8%
2013-09-26 12:05:25 EDT: AB1OC-10>APWW10,TCPIP*,qAC,T2SJC::KJ4ERJ :2013/02/13 16:50: APRSIS32 Win v6.1 b7601 p2 0.0/2.8% [Duplicate message content]
2013-09-26 12:05:26 EDT: AB1OC-10>APWW10,TCPIP*,qAC,T2SJC::KJ4ERJ-AL:2013/02/13 16:50: APRSIS32 Win v6.1 b7601 p2 7.3/2.8%

Strangenesses abound...

Lynn (D) - KJ4ERJ -Author of APRSISCE for Windows Mobile and Win32

On 9/26/2013 11:56 AM, Lynn W Deffenbaugh (Mr) wrote:
Further information from further investigation. First, all of the raw RF packets for AB1OC-10 from my logs of that packet at that time:

2013-09-26 10:22:44 AB1OC-10>APWW10,N8VIM,WIDE1*,WIDE2-1,qAR,AB1OC-10:@261422z4229.14N/07116.31WLI <mailto:AB1OC-10:@261422z4229.14N/07116.31WLI> see you!
2013-09-26 10:22:44 AB1OC-10>APWW10,WIDE1-1,WIDE2-1,qAo,KB1TSO:@261422z4229.14N/07116.31WLI <mailto:KB1TSO:@261422z4229.14N/07116.31WLI> see you!
2013-09-26 10:22:43 AB1OC-10>APWW10,WIDE1-1,WIDE2-1,qAR,KB1TSO:@261422z4229.14N/07116.31WLI <mailto:KB1TSO:@261422z4229.14N/07116.31WLI> see you!
2013-09-26 10:22:44 AB1OC-10>APWW10,KB1TSO*,WIDE1*,WIDE2-1,qAR,KB1TSO:@261422z4229.14N/07116.31WLI <mailto:KB1TSO:@261422z4229.14N/07116.31WLI> see you!
2013-09-26 10:22:45 AB1OC-10>APWW10,KB1TSO*,WIDE1*,N1EXT-5*,WIDE2*,qAR,KB1TSO:@261422z4229.14N/07116.31WLI <mailto:KB1TSO:@261422z4229.14N/07116.31WLI> see you!
2013-09-26 10:22:46 AB1OC-10>APWW10,N8VIM*,WIDE1*,AB1OC-10*,WIDE2*,qAR,KB1TSO:@261422z4229.14N/07116.31WLI <mailto:KB1TSO:@261422z4229.14N/07116.31WLI> see you!
2013-09-26 10:22:43 AB1OC-10>APWW10,KB1TSO*,WIDE1*,WIDE2-1:@261422z4229.14N/07116.31WLI <mailto:WIDE2-1:@261422z4229.14N/07116.31WLI> see you!
2013-09-26 10:22:43 AB1OC-10>APWW10,W1MRA*,WIDE2-1,qAR,N1OMJ:@261422z4229.14N/07116.31WLI <mailto:N1OMJ:@261422z4229.14N/07116.31WLI> see you!
2013-09-26 10:22:46 AB1OC-10>APWW10,W1MRA*,WA1PLE-15*,WIDE2*,qAR,N1OMJ:@261422z4229.14N/07116.31WLI <mailto:N1OMJ:@261422z4229.14N/07116.31WLI> see you!
2013-09-26 10:22:52 AB1OC-10>APWW10,W1MRA*,WA1PLE-15*,WIDE2*,qAR,WA1PLE-5:@261422z4229.14N/07116.31WLI <mailto:WA1PLE-5:@261422z4229.14N/07116.31WLI> see you!

Sure looks like AB1OC-10 transmitted that packet. Especially interesting is the 10:22:46 packet that shows AB1OC-10 digipeating it's own packet! This is a known bug in the TM-D710 digipeater logic as discovered during the Golden Packet attempts. And this fits, because ?IGATE to AB1OC-10 reveals that it's running a Kwd710(APRS) port called TM-D710. Given that this port type doesn't support digipeating in APRSISCE/32, and the fact that APRSISCE/32 will not (at least should not) digipeat a copy of one of it's own packets, the digipeater portion of the TM-D710 must be enabled.

Consider the following map carefully (from my KJ4ERJ-AL full feed instance):



Note that it shows a point down in Bedford which is the one you inquired about, but it also shows a point to the NW of it's most recent location. I suspect it beaconed another "strange' packet payload that caused it to move there. I searched my raw RF logs for the past few days and failed to find any packet to explain that dot. However, it may be the grid-square in his status report beacon, but I'm not sure (see PS below).

However, even though I didn't find any posit to explain the dot, I did find a bunch of apparently truncated packets ostensibly beaconed by AB1OC-10. I've included them below, but have no explanation for them. Given the number of stations reporting the truncated packets for each instance, they obviously were on the air in that form.

It's interesting to note that AB1OC-10 seems to have the posit beacons disabled or at least not passing to the APRS-IS. http://aprs.fi/?c=raw&;call=AB1OC-10 shows a status report with
FN42er, but the only posits (outside of the bogus ones) are Mic-E
formatted which APRSISCE/32 doesn't support but the D710 does natively.

And now for the Pice de rsistance (http://tinyurl.com/2yddue): The Kwd710(APRS) mode, as has been discussed here in the past, is an ongoing contest of the wills between APRSISCE/32 an the D710 when it comes to transmitting. Using undocumented (by Kenwood) TNC commands, APRSISCE/32 temporarily switches modes in the D710 whenever it wants to transmit. When it does this, some of the changed parameters do not go back to the originally configured internal settings in the D710 until the next time the radio is power-cycled (or so it seems). I can't say that this explains the things we're seeing without seeing AB1OC-10's enabled Transmit Trace Log.

This is why I really don't like this particular operating mode (Kwd710(APRS)). If you're going to use the intelligence of the D710, then turn off APRSISCE/32 or make it Receive-Only. If you want the APRSISCE/32 intelligence, then put the D710 into KISS mode and let the program have control. The power struggle always seems to introduce some level of confusion into the picture. (Yes, I've put on my fire-dragon-scale armor to deflect the inevitable flames that I've just solicited).

Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32

PS. I also don't recommend beaconing a grid-square in your status report if the same station is beaconing a real posit. This can cause some APRS client applications to ping-pong the station's location between the less-accurate grid-square and the more accurate posit. APRSISCE/32 avoids this issue by ignoring position reports (be they grid-squares or ambiguous locations) if a more accurate location is currently known. Other APRS clients aren't as paranoid about visual dichotomies.

PPS. Here's the set of packets that appear to have been truncated, well, not truncated, but the beginning of their payload is missing and the end is present:

2013-09-25 00:33:38 AB1OC-10>APWW10,KB1TSO*,WIDE1*,WIDE2-1: Operational
2013-09-25 00:33:38 AB1OC-10>APWW10,WIDE1-1,WIDE2-1,qAR,KB1TSO: Operational
2013-09-25 00:33:38 AB1OC-10>APWW10,WIDE1-1,WIDE2-1,qAR,KB1TSO: Operational
2013-09-25 00:33:39 AB1OC-10>APWW10,N8VIM,WIDE1*,WIDE2-1,qAR,AB1OC-10: Operational
2013-09-25 00:33:39 AB1OC-10>APWW10,N8VIM,WIDE1*,WIDE2-1,qAR,AB1OC-10: Operational
2013-09-25 00:33:39 AB1OC-10>APWW10,W1MRA*,N1EDF-1*,WIDE2*: Operational
2013-09-25 00:33:39 AB1OC-10>APWW10,W1MRA*,WIDE2-1,qAR,N1EDF-1: Operational
2013-09-25 00:33:39 AB1OC-10>APWW10,W1MRA*,WIDE2-1,qAR,N1EDF-1: Operational
2013-09-25 00:33:39 AB1OC-10>APWW10,W1MRA*,WIDE2-1,qAR,N1OMJ: Operational
2013-09-25 00:33:39 AB1OC-10>APWW10,W1MRA*,WIDE2-1,qAR,N1OMJ: Operational
2013-09-25 00:33:39 AB1OC-10>APWW10,WIDE1-1,WIDE2-1,qAo,KB1TSO: Operational
2013-09-25 00:33:39 AB1OC-10>APWW10,WIDE1-1,WIDE2-1,qAo,KB1TSO: Operational
2013-09-25 00:33:40 AB1OC-10>APWW10,W1MRA*,W1MHL*,WIDE2,qAR,KB1VCZ-10: Operational
2013-09-25 00:33:40 AB1OC-10>APWW10,W1MRA*,W1MHL*,WIDE2,qAR,KB1VCZ-10: Operational
2013-09-25 00:33:40 AB1OC-10>APWW10,W1MRA*,W1MHL*,WIDE2,qAR,N1EDF-1: Operational
2013-09-25 00:33:40 AB1OC-10>APWW10,W1MRA*,W1MHL*,WIDE2,qAR,N1EDF-1: Operational
2013-09-25 00:33:40 AB1OC-10>APWW10,W1MRA*,W1MHL*,WIDE2,qAR,N1OMJ: Operational
2013-09-25 00:33:40 AB1OC-10>APWW10,W1MRA*,W1MHL*,WIDE2,qAR,N1OMJ: Operational
2013-09-25 00:33:40 AB1OC-10>APWW10,W1MRA*,WA1PLE-15*,WIDE2*,qAR,AB1PH-5: Operational
2013-09-25 00:33:40 AB1OC-10>APWW10,W1MRA*,WA1PLE-15*,WIDE2*,qAR,AB1PH-5: Operational
2013-09-25 00:33:40 AB1OC-10>APWW10,W1MRA*,WA1PLE-15*,WIDE2*,qAR,N1EDF-1: Operational
2013-09-25 00:33:40 AB1OC-10>APWW10,W1MRA*,WA1PLE-15*,WIDE2*,qAR,N1EDF-1: Operational
2013-09-25 00:33:40 AB1OC-10>APWW10,W1MRA*,WA1PLE-15*,WIDE2*,qAR,N1OMJ: Operational
2013-09-25 00:33:40 AB1OC-10>APWW10,W1MRA*,WA1PLE-15*,WIDE2*,qAR,N1OMJ: Operational
2013-09-25 00:33:41 AB1OC-10>APWW10,KB1TSO*,WIDE1*,WIDE2-1,qAR,KB1TSO: Operational
2013-09-25 00:33:41 AB1OC-10>APWW10,KB1TSO*,WIDE1*,WIDE2-1,qAR,KB1TSO: Operational
2013-09-25 00:33:41 AB1OC-10>APWW10,KB1TSO,WIDE1*,WIDE2-1,qAR,AB1OC-10: Operational
2013-09-25 00:33:41 AB1OC-10>APWW10,KB1TSO,WIDE1*,WIDE2-1,qAR,AB1OC-10: Operational
2013-09-25 00:33:41 AB1OC-10>APWW10,W1MRA*,N1EDF-1*,WIDE2*,qAR,N1OMJ: Operational
2013-09-25 00:33:41 AB1OC-10>APWW10,W1MRA*,N1EDF-1*,WIDE2*,qAR,N1OMJ: Operational
2013-09-25 00:33:42 AB1OC-10>APWW10,KB1TSO*,WIDE1*,W1CLA-1*,WIDE2*,qAR,KB1VCZ-10: Operational
2013-09-25 00:33:42 AB1OC-10>APWW10,KB1TSO*,WIDE1*,W1CLA-1*,WIDE2*,qAR,KB1VCZ-10: Operational
2013-09-25 00:33:42 AB1OC-10>APWW10,KB1TSO,WIDE1,N8VIM,WIDE2*,qAR,AB1OC-10: Operational
2013-09-25 00:33:42 AB1OC-10>APWW10,KB1TSO,WIDE1,N8VIM,WIDE2*,qAR,AB1OC-10: Operational
2013-09-25 00:33:42 AB1OC-10>APWW10,W1MRA*,WA1PLE-15*,WIDE2*,qAR,WA1PLE-5: Operational
2013-09-25 00:33:42 AB1OC-10>APWW10,W1MRA*,WA1PLE-15*,WIDE2*,qAR,WA1PLE-5: Operational
2013-09-25 00:33:43 AB1OC-10>APWW10,KB1TSO*,WIDE1*,AB1OC-10*,WIDE2*,qAR,KB1TSO: Operational
2013-09-25 00:33:43 AB1OC-10>APWW10,KB1TSO*,WIDE1*,AB1OC-10*,WIDE2*,qAR,KB1TSO: Operational
2013-09-25 00:33:43 AB1OC-10>APWW10,N8VIM*,WIDE1*,AB1OC-10*,WIDE2*,qAR,KB1TSO: Operational
2013-09-25 00:33:43 AB1OC-10>APWW10,N8VIM*,WIDE1*,AB1OC-10*,WIDE2*,qAR,KB1TSO: Operational
2013-09-25 00:33:46 AB1OC-10>APWW10,KB1TSO*,WIDE1*,W1CLA-1*,WIDE2*,qAR,WA1PLE-5: Operational
2013-09-25 00:33:46 AB1OC-10>APWW10,KB1TSO*,WIDE1*,W1CLA-1*,WIDE2*,qAR,WA1PLE-5: Operational
2013-09-25 08:48:47 AB1OC-10>APWW10,N8VIM,WIDE1*,WIDE2-1,qAR,AB1OC-10:al
2013-09-25 08:48:47 AB1OC-10>APWW10,N8VIM,WIDE1*,WIDE2-1,qAR,AB1OC-10:al
2013-09-25 08:48:47 AB1OC-10>APWW10,W1MRA*,N1EDF-1*,WIDE2*:al
2013-09-25 08:48:47 AB1OC-10>APWW10,W1MRA*,WIDE2-1,qAR,N1EDF-1:al
2013-09-25 08:48:47 AB1OC-10>APWW10,W1MRA*,WIDE2-1,qAR,N1EDF-1:al
2013-09-25 08:48:47 AB1OC-10>APWW10,W1MRA*,WIDE2-1,qAR,N1OMJ:al
2013-09-25 08:48:47 AB1OC-10>APWW10,W1MRA*,WIDE2-1,qAR,N1OMJ:al
2013-09-25 08:48:47 AB1OC-10>APWW10,WIDE1-1,WIDE2-1,qAR,WB2OSZ-5:al
2013-09-25 08:48:47 AB1OC-10>APWW10,WIDE1-1,WIDE2-1,qAR,WB2OSZ-5:al
2013-09-25 08:48:48 AB1OC-10>APWW10,W1MRA,UNCAN,WIDE2*,qAR,AB1OC-10:al
2013-09-25 08:48:48 AB1OC-10>APWW10,W1MRA,UNCAN,WIDE2*,qAR,AB1OC-10:al
2013-09-25 08:48:49 AB1OC-10>APWW10,N8VIM*,WIDE1*,AB1OC-10*,WIDE2*,qAR,KB1TSO:al
2013-09-25 08:48:49 AB1OC-10>APWW10,N8VIM*,WIDE1*,AB1OC-10*,WIDE2*,qAR,KB1TSO:al
2013-09-25 08:48:49 AB1OC-10>APWW10,W1MRA*,N1EDF-1*,WIDE2*,qAR,N1OMJ:al
2013-09-25 08:48:49 AB1OC-10>APWW10,W1MRA*,N1EDF-1*,WIDE2*,qAR,N1OMJ:al
2013-09-25 08:48:55 AB1OC-10>APWW10,WB2OSZ-5*,W1CLA-1*,WIDE2*,qAR,KB1TSO:al
2013-09-25 08:48:55 AB1OC-10>APWW10,WB2OSZ-5*,W1CLA-1*,WIDE2*,qAR,KB1TSO:al
2013-09-25 08:48:55 AB1OC-10>APWW10,WB2OSZ-5*,W1CLA-1*,WIDE2*,qAR,KB1VCZ-10:al
2013-09-25 08:48:55 AB1OC-10>APWW10,WB2OSZ-5*,W1CLA-1*,WIDE2*,qAR,KB1VCZ-10:al
2013-09-25 08:48:55 AB1OC-10>APWW10,WB2OSZ-5*,W1CLA-1*,WIDE2*,qAR,N1OMJ:al
2013-09-25 08:48:55 AB1OC-10>APWW10,WB2OSZ-5*,W1CLA-1*,WIDE2*,qAR,N1OMJ:al
2013-09-25 08:48:55 AB1OC-10>APWW10,WB2OSZ-5*,WIDE2-1,qAR,AB1OC-10:al
2013-09-25 08:48:55 AB1OC-10>APWW10,WB2OSZ-5*,WIDE2-1,qAR,AB1OC-10:al
2013-09-25 08:48:55 AB1OC-10>APWW10,WB2OSZ-5*,WIDE2-1,qAR,KB1TSO:al
2013-09-25 08:48:55 AB1OC-10>APWW10,WB2OSZ-5*,WIDE2-1,qAR,KB1TSO:al
2013-09-25 08:49:05 AB1OC-10>APWW10,WB2OSZ-5*,W1CLA-1*,WIDE2*,qAR,WA1PLE-5:al
2013-09-25 08:49:05 AB1OC-10>APWW10,WB2OSZ-5*,W1CLA-1*,WIDE2*,qAR,WA1PLE-5:al
2013-09-25 17:29:01 AB1OC-10>APWW10,KB1TSO*,WIDE1*,WIDE2-1:tional
2013-09-25 17:29:01 AB1OC-10>APWW10,WIDE1-1,WIDE2-1,qAR,KB1TSO:tional
2013-09-25 17:29:01 AB1OC-10>APWW10,WIDE1-1,WIDE2-1,qAR,KB1TSO:tional
2013-09-25 17:29:02 AB1OC-10>APWW10,KB1TSO*,WIDE1*,WIDE2-1,qAR,KB1TSO:tional
2013-09-25 17:29:02 AB1OC-10>APWW10,KB1TSO*,WIDE1*,WIDE2-1,qAR,KB1TSO:tional
2013-09-25 17:29:02 AB1OC-10>APWW10,W1MRA*,WIDE2-1,qAR,N1OMJ:tional
2013-09-25 17:29:02 AB1OC-10>APWW10,W1MRA*,WIDE2-1,qAR,N1OMJ:tional
2013-09-25 17:29:02 AB1OC-10>APWW10,W1MRA*,WIDE2-1,qAR,W1XM:tional
2013-09-25 17:29:02 AB1OC-10>APWW10,W1MRA*,WIDE2-1,qAR,W1XM:tional
2013-09-25 17:29:03 AB1OC-10>APWW10,N8VIM,WIDE1*,WIDE2-1,qAR,AB1OC-10:tional
2013-09-25 17:29:03 AB1OC-10>APWW10,N8VIM,WIDE1*,WIDE2-1,qAR,AB1OC-10:tional
2013-09-25 17:29:03 AB1OC-10>APWW10,W1MRA*,W1CLA-1*,WIDE2*,qAR,AB1PH-5:tional
2013-09-25 17:29:03 AB1OC-10>APWW10,W1MRA*,W1CLA-1*,WIDE2*,qAR,AB1PH-5:tional
2013-09-25 17:29:03 AB1OC-10>APWW10,W1MRA*,W1CLA-1*,WIDE2*,qAR,KB1VCZ-10:tional
2013-09-25 17:29:03 AB1OC-10>APWW10,W1MRA*,W1CLA-1*,WIDE2*,qAR,KB1VCZ-10:tional
2013-09-25 17:29:03 AB1OC-10>APWW10,W1MRA*,W1MHL*,WIDE2,qAR,AB1PH-5:tional
2013-09-25 17:29:03 AB1OC-10>APWW10,W1MRA*,W1MHL*,WIDE2,qAR,AB1PH-5:tional
2013-09-25 17:29:03 AB1OC-10>APWW10,W1MRA*,W1MHL*,WIDE2,qAR,KB1VCZ-10:tional
2013-09-25 17:29:03 AB1OC-10>APWW10,W1MRA*,W1MHL*,WIDE2,qAR,KB1VCZ-10:tional
2013-09-25 17:29:03 AB1OC-10>APWW10,W1MRA*,W1MHL*,WIDE2,qAR,N1EDF-1:tional
2013-09-25 17:29:03 AB1OC-10>APWW10,W1MRA*,W1MHL*,WIDE2,qAR,N1EDF-1:tional
2013-09-25 17:29:03 AB1OC-10>APWW10,W1MRA*,W1MHL*,WIDE2,qAR,N1OMJ:tional
2013-09-25 17:29:03 AB1OC-10>APWW10,W1MRA*,W1MHL*,WIDE2,qAR,N1OMJ:tional
2013-09-25 17:29:03 AB1OC-10>APWW10,W1MRA*,W1MHL*,WIDE2,qAR,WA1PLE-5:tional
2013-09-25 17:29:03 AB1OC-10>APWW10,W1MRA*,W1MHL*,WIDE2,qAR,WA1PLE-5:tional
2013-09-25 17:29:05 AB1OC-10>APWW10,W1MRA*,W1CLA-1*,WIDE2*,qAR,WA1PLE-5:tional
2013-09-25 17:29:05 AB1OC-10>APWW10,W1MRA*,W1CLA-1*,WIDE2*,qAR,WA1PLE-5:tional
2013-09-25 17:29:06 AB1OC-10>APWW10,W1MRA*,WA1PLE-15*,WIDE2*,qAR,WA1PLE-5:tional
2013-09-25 17:29:06 AB1OC-10>APWW10,W1MRA*,WA1PLE-15*,WIDE2*,qAR,WA1PLE-5:tional
2013-09-25 17:29:08 AB1OC-10>APWW10,DERRY*,WIDE2-1,qAR,AB1OC-10:tional
2013-09-25 17:29:08 AB1OC-10>APWW10,DERRY*,WIDE2-1,qAR,AB1OC-10:tional
2013-09-25 17:29:08 AB1OC-10>APWW10,DERRY*,WIDE2-1,qAR,KB1TSO:tional
2013-09-25 17:29:08 AB1OC-10>APWW10,DERRY*,WIDE2-1,qAR,KB1TSO:tional
2013-09-25 22:44:10 AB1OC-10>APWW10,W1MRA*,N1EDF-1*,WIDE2*:ollis, NH iGate Operational
2013-09-25 22:44:10 AB1OC-10>APWW10,W1MRA*,WIDE2-1,qAR,N1EDF-1:ollis, NH iGate Operational
2013-09-25 22:44:10 AB1OC-10>APWW10,W1MRA*,WIDE2-1,qAR,N1EDF-1:ollis, NH iGate Operational
2013-09-25 22:44:10 AB1OC-10>APWW10,W1MRA*,WIDE2-1,qAR,N1OMJ:ollis, NH iGate Operational
2013-09-25 22:44:10 AB1OC-10>APWW10,W1MRA*,WIDE2-1,qAR,N1OMJ:ollis, NH iGate Operational
2013-09-25 22:44:11 AB1OC-10>APWW10,N8VIM,WIDE1*,WIDE2-1,qAR,AB1OC-10:ollis, NH iGate Operational
2013-09-25 22:44:11 AB1OC-10>APWW10,N8VIM,WIDE1*,WIDE2-1,qAR,AB1OC-10:ollis, NH iGate Operational
2013-09-25 22:44:11 AB1OC-10>APWW10,W1MRA*,W1MHL*,WIDE2,qAR,AB1PH-5:ollis, NH iGate Operational
2013-09-25 22:44:11 AB1OC-10>APWW10,W1MRA*,W1MHL*,WIDE2,qAR,AB1PH-5:ollis, NH iGate Operational
2013-09-25 22:44:11 AB1OC-10>APWW10,W1MRA*,W1MHL*,WIDE2,qAR,KB1VCZ-10:ollis, NH iGate Operational
2013-09-25 22:44:11 AB1OC-10>APWW10,W1MRA*,W1MHL*,WIDE2,qAR,KB1VCZ-10:ollis, NH iGate Operational
2013-09-25 22:44:11 AB1OC-10>APWW10,W1MRA*,W1MHL*,WIDE2,qAR,N1EDF-1:ollis, NH iGate Operational
2013-09-25 22:44:11 AB1OC-10>APWW10,W1MRA*,W1MHL*,WIDE2,qAR,N1EDF-1:ollis, NH iGate Operational
2013-09-25 22:44:11 AB1OC-10>APWW10,W1MRA*,W1MHL*,WIDE2,qAR,N1OMJ:ollis, NH iGate Operational
2013-09-25 22:44:11 AB1OC-10>APWW10,W1MRA*,W1MHL*,WIDE2,qAR,N1OMJ:ollis, NH iGate Operational
2013-09-25 22:44:11 AB1OC-10>APWW10,W1MRA*,WIDE2-1,qAR,N1OMJ:ollis, NH iGate Operational
2013-09-25 22:44:11 AB1OC-10>APWW10,W1MRA*,WIDE2-1,qAR,N1OMJ:ollis, NH iGate Operational
2013-09-25 22:44:13 AB1OC-10>APWW10,W1MRA*,N1EDF-1*,WIDE2*,qAR,N1OMJ:ollis, NH iGate Operational
2013-09-25 22:44:13 AB1OC-10>APWW10,W1MRA*,N1EDF-1*,WIDE2*,qAR,N1OMJ:ollis, NH iGate Operational
2013-09-25 22:44:14 AB1OC-10>APWW10,W1MRA*,W1MHL*,WA1PLE-15*,qAR,N1EDF-1:ollis, NH iGate Operational
2013-09-25 22:44:14 AB1OC-10>APWW10,W1MRA*,W1MHL*,WA1PLE-15*,qAR,N1EDF-1:ollis, NH iGate Operational
2013-09-25 22:44:14 AB1OC-10>APWW10,W1MRA*,W1MHL*,WA1PLE-15*,qAR,N1OMJ:ollis, NH iGate Operational
2013-09-25 22:44:14 AB1OC-10>APWW10,W1MRA*,W1MHL*,WA1PLE-15*,qAR,N1OMJ:ollis, NH iGate Operational
2013-09-25 22:44:14 AB1OC-10>APWW10,W1MRA*,W1MHL*,WIDE2,qAR,WA1PLE-5:ollis, NH iGate Operational
2013-09-25 22:44:14 AB1OC-10>APWW10,W1MRA*,W1MHL*,WIDE2,qAR,WA1PLE-5:ollis, NH iGate Operational
2013-09-25 22:44:19 AB1OC-10>APWW10,W1MRA*,W1MHL*,WA1PLE-15*,qAR,WA1PLE-5:ollis, NH iGate Operational
2013-09-25 22:44:19 AB1OC-10>APWW10,W1MRA*,W1MHL*,WA1PLE-15*,qAR,WA1PLE-5:ollis, NH iGate Operational
2013-09-26 00:19:12 AB1OC-10>APWW10,KB1TSO*,WIDE1*,WIDE2-1:tional
2013-09-26 00:19:12 AB1OC-10>APWW10,WIDE1-1,WIDE2-1,qAR,KB1TSO:tional
2013-09-26 00:19:12 AB1OC-10>APWW10,WIDE1-1,WIDE2-1,qAR,KB1TSO:tional
2013-09-26 00:19:12 AB1OC-10>APWW10,WIDE1-1,WIDE2-1,qAR,W1XM:tional
2013-09-26 00:19:12 AB1OC-10>APWW10,WIDE1-1,WIDE2-1,qAR,W1XM:tional
2013-09-26 00:19:13 AB1OC-10>APWW10,KB1POR-2*,KB1FDA-1*,WIDE2*,qAR,K9UDX:tional
2013-09-26 00:19:13 AB1OC-10>APWW10,KB1POR-2*,KB1FDA-1*,WIDE2*,qAR,K9UDX:tional
2013-09-26 00:19:13 AB1OC-10>APWW10,KB1POR-2*,KB1FDA-1*,WIDE2*,qAR,N1XED-1:tional
2013-09-26 00:19:13 AB1OC-10>APWW10,KB1POR-2*,KB1FDA-1*,WIDE2*,qAR,N1XED-1:tional
2013-09-26 00:19:13 AB1OC-10>APWW10,KB1POR-2*,WIDE2-1,qAR,KB1TSO:tional
2013-09-26 00:19:13 AB1OC-10>APWW10,KB1POR-2*,WIDE2-1,qAR,KB1TSO:tional
2013-09-26 00:19:13 AB1OC-10>APWW10,KB1TSO*,WIDE1*,WIDE2-1,qAR,KB1TSO:tional
2013-09-26 00:19:13 AB1OC-10>APWW10,KB1TSO*,WIDE1*,WIDE2-1,qAR,KB1TSO:tional
2013-09-26 00:19:13 AB1OC-10>APWW10,N8VIM,WIDE1*,WIDE2-1,qAR,AB1OC-10:tional
2013-09-26 00:19:13 AB1OC-10>APWW10,N8VIM,WIDE1*,WIDE2-1,qAR,AB1OC-10:tional
2013-09-26 00:19:13 AB1OC-10>APWW10,W1MRA*,N1EDF-1*,WIDE2*:tional
2013-09-26 00:19:13 AB1OC-10>APWW10,W1MRA*,WIDE2-1,qAR,AB1OC-10:tional
2013-09-26 00:19:13 AB1OC-10>APWW10,W1MRA*,WIDE2-1,qAR,AB1OC-10:tional
2013-09-26 00:19:13 AB1OC-10>APWW10,W1MRA*,WIDE2-1,qAR,N1EDF-1:tional
2013-09-26 00:19:13 AB1OC-10>APWW10,W1MRA*,WIDE2-1,qAR,N1EDF-1:tional
2013-09-26 00:19:13 AB1OC-10>APWW10,W1MRA*,WIDE2-1,qAR,N1OMJ:tional
2013-09-26 00:19:13 AB1OC-10>APWW10,W1MRA*,WIDE2-1,qAR,N1OMJ:tional
2013-09-26 00:19:14 AB1OC-10>APWW10,W1MRA*,W1MHL*,WIDE2,qAR,AB1PH-5:tional
2013-09-26 00:19:14 AB1OC-10>APWW10,W1MRA*,W1MHL*,WIDE2,qAR,AB1PH-5:tional
2013-09-26 00:19:14 AB1OC-10>APWW10,W1MRA*,W1MHL*,WIDE2,qAR,KB1VCZ-10:tional
2013-09-26 00:19:14 AB1OC-10>APWW10,W1MRA*,W1MHL*,WIDE2,qAR,KB1VCZ-10:tional
2013-09-26 00:19:14 AB1OC-10>APWW10,W1MRA*,W1MHL*,WIDE2,qAR,N1EDF-1:tional
2013-09-26 00:19:14 AB1OC-10>APWW10,W1MRA*,W1MHL*,WIDE2,qAR,N1EDF-1:tional
2013-09-26 00:19:14 AB1OC-10>APWW10,W1MRA*,W1MHL*,WIDE2,qAR,N1OMJ:tional
2013-09-26 00:19:14 AB1OC-10>APWW10,W1MRA*,W1MHL*,WIDE2,qAR,N1OMJ:tional
2013-09-26 00:19:14 AB1OC-10>APWW10,W1MRA*,W1MHL*,WIDE2,qAR,WA1PLE-5:tional
2013-09-26 00:19:14 AB1OC-10>APWW10,W1MRA*,W1MHL*,WIDE2,qAR,WA1PLE-5:tional
2013-09-26 00:19:14 AB1OC-10>APWW10,W1MRA*,WA1PLE-15*,WIDE2*,qAR,N1EDF-1:tional
2013-09-26 00:19:14 AB1OC-10>APWW10,W1MRA*,WA1PLE-15*,WIDE2*,qAR,N1EDF-1:tional
2013-09-26 00:19:14 AB1OC-10>APWW10,W1MRA*,WA1PLE-15*,WIDE2*,qAR,N1OMJ:tional
2013-09-26 00:19:14 AB1OC-10>APWW10,W1MRA*,WA1PLE-15*,WIDE2*,qAR,N1OMJ:tional
2013-09-26 00:19:16 AB1OC-10>APWW10,N1NCI-3*,WIDE1*,W1UWS-1*,WIDE2*,qAR,K9UDX:tional
2013-09-26 00:19:16 AB1OC-10>APWW10,N1NCI-3*,WIDE1*,W1UWS-1*,WIDE2*,qAR,K9UDX:tional
2013-09-26 00:19:16 AB1OC-10>APWW10,W1MRA*,N1EDF-1*,WIDE2*,qAR,N1OMJ:tional
2013-09-26 00:19:16 AB1OC-10>APWW10,W1MRA*,N1EDF-1*,WIDE2*,qAR,N1OMJ:tional
2013-09-26 00:19:17 AB1OC-10>APWW10,W1MRA*,AB1OC-10*,WIDE2*,qAR,KB1TSO:tional
2013-09-26 00:19:17 AB1OC-10>APWW10,W1MRA*,AB1OC-10*,WIDE2*,qAR,KB1TSO:tional
2013-09-26 00:19:21 AB1OC-10>APWW10,W1MRA*,WA1PLE-15*,WIDE2*,qAR,WA1PLE-5:tional
2013-09-26 00:19:21 AB1OC-10>APWW10,W1MRA*,WA1PLE-15*,WIDE2*,qAR,WA1PLE-5:tional
2013-09-26 02:59:16 AB1OC-10>APWW10,WIDE1-1,WIDE2-1,qAR,W1XM:ional
2013-09-26 02:59:16 AB1OC-10>APWW10,WIDE1-1,WIDE2-1,qAR,W1XM:ional
2013-09-26 02:59:17 AB1OC-10>APWW10,KB1POR-2*,KB1FDA-1*,WIDE2*,qAR,K9UDX:ional
2013-09-26 02:59:17 AB1OC-10>APWW10,KB1POR-2*,KB1FDA-1*,WIDE2*,qAR,K9UDX:ional
2013-09-26 02:59:17 AB1OC-10>APWW10,KB1POR-2*,KB1FDA-1*,WIDE2*,qAR,N1XED-1:ional
2013-09-26 02:59:17 AB1OC-10>APWW10,KB1POR-2*,KB1FDA-1*,WIDE2*,qAR,N1XED-1:ional
2013-09-26 02:59:17 AB1OC-10>APWW10,N8VIM,WIDE1*,WIDE2-1,qAR,AB1OC-10:ional
2013-09-26 02:59:17 AB1OC-10>APWW10,N8VIM,WIDE1*,WIDE2-1,qAR,AB1OC-10:ional
2013-09-26 02:59:17 AB1OC-10>APWW10,W1MHL*,N1EDF-1*,WIDE2*:ional
2013-09-26 02:59:17 AB1OC-10>APWW10,W1MHL*,WIDE2-1,qAR,AB1PH-5:ional
2013-09-26 02:59:17 AB1OC-10>APWW10,W1MHL*,WIDE2-1,qAR,AB1PH-5:ional
2013-09-26 02:59:17 AB1OC-10>APWW10,W1MHL*,WIDE2-1,qAR,KB1VCZ-10:ional
2013-09-26 02:59:17 AB1OC-10>APWW10,W1MHL*,WIDE2-1,qAR,KB1VCZ-10:ional
2013-09-26 02:59:17 AB1OC-10>APWW10,W1MHL*,WIDE2-1,qAR,N1EDF-1:ional
2013-09-26 02:59:17 AB1OC-10>APWW10,W1MHL*,WIDE2-1,qAR,N1EDF-1:ional
2013-09-26 02:59:17 AB1OC-10>APWW10,W1MHL*,WIDE2-1,qAR,N1OMJ:ional
2013-09-26 02:59:17 AB1OC-10>APWW10,W1MHL*,WIDE2-1,qAR,N1OMJ:ional
2013-09-26 02:59:18 AB1OC-10>APWW10,KB1POR-2*,K2DLL-12*,WIDE2*,qAR,K3SD-1:ional
2013-09-26 02:59:18 AB1OC-10>APWW10,KB1POR-2*,K2DLL-12*,WIDE2*,qAR,K3SD-1:ional
2013-09-26 02:59:18 AB1OC-10>APWW10,KB1POR-2*,W1MHL*,WIDE2,qAR,AB1PH-5:ional
2013-09-26 02:59:18 AB1OC-10>APWW10,KB1POR-2*,W1MHL*,WIDE2,qAR,AB1PH-5:ional
2013-09-26 02:59:18 AB1OC-10>APWW10,KB1POR-2*,W1MHL*,WIDE2,qAR,KB1VCZ-10:ional
2013-09-26 02:59:18 AB1OC-10>APWW10,KB1POR-2*,W1MHL*,WIDE2,qAR,KB1VCZ-10:ional
2013-09-26 02:59:18 AB1OC-10>APWW10,KB1POR-2*,W1MHL*,WIDE2,qAR,N1EDF-1:ional
2013-09-26 02:59:18 AB1OC-10>APWW10,KB1POR-2*,W1MHL*,WIDE2,qAR,N1EDF-1:ional
2013-09-26 02:59:18 AB1OC-10>APWW10,KB1POR-2*,W1MHL*,WIDE2,qAR,N1OMJ:ional
2013-09-26 02:59:18 AB1OC-10>APWW10,KB1POR-2*,W1MHL*,WIDE2,qAR,N1OMJ:ional
2013-09-26 02:59:18 AB1OC-10>APWW10,KB1POR-2*,W1MHL*,WIDE2,qAR,WA1PLE-5:ional
2013-09-26 02:59:18 AB1OC-10>APWW10,KB1POR-2*,W1MHL*,WIDE2,qAR,WA1PLE-5:ional
2013-09-26 02:59:18 AB1OC-10>APWW10,KB1POR-2,KB1AEV-15*,WIDE2,qAR,WB2ZII-13:ional
2013-09-26 02:59:18 AB1OC-10>APWW10,KB1POR-2,KB1AEV-15*,WIDE2,qAR,WB2ZII-13:ional
2013-09-26 02:59:18 AB1OC-10>APWW10,W1MHL*,W1CLA-1*,WIDE2*,qAR,KB1VCZ-10:ional
2013-09-26 02:59:18 AB1OC-10>APWW10,W1MHL*,W1CLA-1*,WIDE2*,qAR,KB1VCZ-10:ional
2013-09-26 02:59:18 AB1OC-10>APWW10,W1MHL*,W1MRA*,WIDE2,qAR,N1EDF-1:ional
2013-09-26 02:59:18 AB1OC-10>APWW10,W1MHL*,W1MRA*,WIDE2,qAR,N1EDF-1:ional
2013-09-26 02:59:18 AB1OC-10>APWW10,W1MHL*,W1MRA*,WIDE2,qAR,N1OMJ:ional
2013-09-26 02:59:18 AB1OC-10>APWW10,W1MHL*,W1MRA*,WIDE2,qAR,N1OMJ:ional
2013-09-26 02:59:18 AB1OC-10>APWW10,W1MHL*,WIDE2-1,qAR,WA1PLE-5:ional
2013-09-26 02:59:18 AB1OC-10>APWW10,W1MHL*,WIDE2-1,qAR,WA1PLE-5:ional
2013-09-26 02:59:18 AB1OC-10>APWW10,W1MHL,W1MRA*,WIDE2,qAR,AB1OC-10:ional
2013-09-26 02:59:18 AB1OC-10>APWW10,W1MHL,W1MRA*,WIDE2,qAR,AB1OC-10:ional
2013-09-26 02:59:19 AB1OC-10>APWW10,N1NCI-3,WIDE1*,WIDE2-1,qAR,AB1OC-10:ional
2013-09-26 02:59:19 AB1OC-10>APWW10,N1NCI-3,WIDE1*,WIDE2-1,qAR,AB1OC-10:ional
2013-09-26 02:59:19 AB1OC-10>APWW10,W1MHL*,N1EDF-1*,WIDE2*,qAR,N1OMJ:ional
2013-09-26 02:59:19 AB1OC-10>APWW10,W1MHL*,N1EDF-1*,WIDE2*,qAR,N1OMJ:ional
2013-09-26 02:59:20 AB1OC-10>APWW10,KB1POR-2*,WA1PLE-15*,WIDE2*,qAR,AB1PH-5:ional
2013-09-26 02:59:20 AB1OC-10>APWW10,KB1POR-2*,WA1PLE-15*,WIDE2*,qAR,AB1PH-5:ional
2013-09-26 02:59:20 AB1OC-10>APWW10,KB1POR-2*,WA1PLE-15*,WIDE2*,qAR,N1EDF-1:ional
2013-09-26 02:59:20 AB1OC-10>APWW10,KB1POR-2*,WA1PLE-15*,WIDE2*,qAR,N1EDF-1:ional
2013-09-26 02:59:20 AB1OC-10>APWW10,KB1POR-2*,WA1PLE-15*,WIDE2*,qAR,N1OMJ:ional
2013-09-26 02:59:20 AB1OC-10>APWW10,KB1POR-2*,WA1PLE-15*,WIDE2*,qAR,N1OMJ:ional
2013-09-26 02:59:20 AB1OC-10>APWW10,W1MHL*,W1CLA-1*,WIDE2*,qAR,WA1PLE-5:ional
2013-09-26 02:59:20 AB1OC-10>APWW10,W1MHL*,W1CLA-1*,WIDE2*,qAR,WA1PLE-5:ional
2013-09-26 02:59:21 AB1OC-10>APWW10,KB1POR-2*,KB1AEV-15*,WIDE2*,qAR,KC2WDZ-1:ional
2013-09-26 02:59:21 AB1OC-10>APWW10,KB1POR-2*,KB1AEV-15*,WIDE2*,qAR,KC2WDZ-1:ional
2013-09-26 02:59:24 AB1OC-10>APWW10,KB1POR-2*,WA1PLE-15*,WIDE2*,qAR,WA1PLE-5:ional
2013-09-26 02:59:24 AB1OC-10>APWW10,KB1POR-2*,WA1PLE-15*,WIDE2*,qAR,WA1PLE-5:ional
2013-09-26 04:19:20 AB1OC-10>APWW10,N8VIM,WIDE1*,WIDE2-1,qAR,AB1OC-10:ional
2013-09-26 04:19:20 AB1OC-10>APWW10,N8VIM,WIDE1*,WIDE2-1,qAR,AB1OC-10:ional
2013-09-26 04:19:20 AB1OC-10>APWW10,TCPIP*,qAC,T2SJC:ional
2013-09-26 04:19:20 AB1OC-10>APWW10,TCPIP*,qAC,T2SJC:ional
2013-09-26 04:19:23 AB1OC-10>APWW10,DERRY*,WIDE2-1,qAR,AB1OC-10:ional
2013-09-26 04:19:23 AB1OC-10>APWW10,DERRY*,WIDE2-1,qAR,AB1OC-10:ional
2013-09-26 04:19:23 AB1OC-10>APWW10,DERRY*,WIDE2-1,qAR,KB1TSO:ional
2013-09-26 04:19:23 AB1OC-10>APWW10,DERRY*,WIDE2-1,qAR,KB1TSO:ional
2013-09-26 04:19:24 AB1OC-10>APWW10,DERRY,UNCAN,WIDE2*,qAR,AB1OC-10:ional
2013-09-26 04:19:24 AB1OC-10>APWW10,DERRY,UNCAN,WIDE2*,qAR,AB1OC-10:ional
2013-09-26 04:19:24 AB1OC-10>APWW10,N8VIM*,WIDE1*,AB1OC-10*,WIDE2*,qAR,KB1TSO:ional
2013-09-26 04:19:24 AB1OC-10>APWW10,N8VIM*,WIDE1*,AB1OC-10*,WIDE2*,qAR,KB1TSO:ional
2013-09-26 04:19:30 AB1OC-10>APWW10,DERRY,N1EDU-2*,qAR,AB1OC-10:ional
2013-09-26 04:19:30 AB1OC-10>APWW10,DERRY,N1EDU-2*,qAR,AB1OC-10:ional
2013-09-26 05:54:24 AB1OC-10>APWW10,WIDE1-1,WIDE2-1,qAo,KB1TSO:onal
2013-09-26 05:54:24 AB1OC-10>APWW10,WIDE1-1,WIDE2-1,qAo,KB1TSO:onal
2013-09-26 06:04:23 AB1OC-10>APWW10,WIDE1-1,WIDE2-1,qAR,W1XM:ate Operational
2013-09-26 06:04:23 AB1OC-10>APWW10,WIDE1-1,WIDE2-1,qAR,W1XM:ate Operational






On 9/26/2013 11:20 AM, Lynn W Deffenbaugh (Mr) wrote:
Probable cause:

2013-09-26 10:22:43 EDT: AB1OC-10>APWW10,WIDE1-1,WIDE2-1,qAo,KB1TSO:@261422z4229.14N/07116.31WLI <mailto:KB1TSO:@261422z4229.14N/07116.31WLI> see you! [Location changes too fast (adaptive limit)]

compared to your:

2013-09-26 10:22:36 EDT: *N7FMH-10 <http://aprs.fi/?c=raw&;limit=&call=N7FMH-10>*>APWW10,TCPIP*,qAC,WE7U-F1:@261422z4229.14N/07116.31WLI <mailto:WE7U-F1:@261422z4229.14N/07116.31WLI> see you!
Interesting that the comments are the same?

qAo is defined as "*qAo* - (letter O) Packet was received via a client-only port, the FROMCALL does not match the login, and the packet contains either a ,I or qAR construct where the indicated IGate matches the login.".

KB1TSO is also an APRSISCE/32 instance:

2013-09-26 10:22:35 EDT: KB1TSO>APWW10,TCPIP*,qAC,N5JXS-F1:@142236h4242.77N/07113.26W#PHG73604 <mailto:N5JXS-F1:@142236h4242.77N/07113.26W#PHG73604> / iGate/Digi Methuen, MA
But I have no idea where the N5JXS-F1 APRS-IS server is, so I cannot determine what port that instance is connected to. However, I suspect it's a "client-only" port which is not the same as an "IGate port" which is typically 14580. I suspect a mis-configured APRS-IS server or that KB1TSO is using a port on that server that it shouldn't be using.

But that doesn't explain how the body of (apparently) your packet got placed behind the header of someone else's packet on the APRS-IS.

According to the raw RF logs from KB1TSO, it can hear AB1OC-10:

2013-09-26 10:22:36 KB1TSO>APWW10,WIDE1-1,qAR,KB1TSO:@142236h4242.77N/07113.26W#PHG73604 <mailto:KB1TSO:@142236h4242.77N/07113.26W#PHG73604> /
iGate/Digi Methuen, MA
2013-09-26 10:22:41 KB1TSO>APWW10,DERRY*,qAR,KB1TSO:@142236h4242.77N/07113.26W#PHG73604 <mailto:KB1TSO:@142236h4242.77N/07113.26W#PHG73604> / iGate/Digi Methuen, MA
2013-09-26 10:22:42 KB1TSO>APWW10,AB1OC-10*,WIDE1*,qAR,KB1TSO:@142236h4242.77N/07113.26W#PHG73604 <mailto:KB1TSO:@142236h4242.77N/07113.26W#PHG73604> / iGate/Digi Methuen, MA
2013-09-26 10:22:43 AB1OC-10>APWW10,WIDE1-1,WIDE2-1,qAR,KB1TSO:@261422z4229.14N/07116.31WLI <mailto:KB1TSO:@261422z4229.14N/07116.31WLI> see you!
2013-09-26 10:22:44 AB1OC-10>APWW10,KB1TSO*,WIDE1*,WIDE2-1,qAR,KB1TSO:@261422z4229.14N/07116.31WLI <mailto:KB1TSO:@261422z4229.14N/07116.31WLI> see you!
2013-09-26 10:22:45 AB1OC-10>APWW10,KB1TSO*,WIDE1*,N1EXT-5*,WIDE2*,qAR,KB1TSO:@261422z4229.14N/07116.31WLI <mailto:KB1TSO:@261422z4229.14N/07116.31WLI> see you!
2013-09-26 10:22:46 AB1OC-10>APWW10,N8VIM*,WIDE1*,AB1OC-10*,WIDE2*,qAR,KB1TSO:@261422z4229.14N/07116.31WLI <mailto:KB1TSO:@261422z4229.14N/07116.31WLI> see you!
2013-09-26 10:22:52 KB1CHU-9>TRQX2Y,W1MRA*,WIDE2-1,qAR,KB1TSO:`c)Hl"u&#92;`"4<}Steves F-150_"
2013-09-26 10:22:53 KB1CHU-9>TRQX2Y,W1MRA*,AB1OC-10*,WIDE2*,qAR,KB1TSO:`c)Hl"u&#92;`"4<}Steves F-150_"

And AB1OC-10 also appears to be a digipeater that can copy KB1TSO. Now, the question is still how KB1TSO apparently copied AB1OC-10 direct at 10:22:43 with a packet body that was your beacon string? To answer that, I'd have to get a copy of KB1TSO's APRSIS32*.LOG file that covers that time range and then it would only be helpful if sufficient Trace Logs were actually enabled, especially the Port and Transmit logs.

AB1OC-10's Transmit log contents at that time would also be good to see in order to determine if that station actually transmitted the packet that KB1TSO appears to have received (and digipeated). Well, further evidence from AB1OC-10's raw RF logs:

2013-09-26 10:22:41 KB1TSO>APWW10,DERRY*,qAR,AB1OC-10:@142236h4242.77N/07113.26W#PHG73604 <mailto:AB1OC-10:@142236h4242.77N/07113.26W#PHG73604> / iGate/Digi Methuen, MA
2013-09-26 10:22:44 AB1OC-10>APWW10,N8VIM,WIDE1*,WIDE2-1,qAR,AB1OC-10:@261422z4229.14N/07116.31WLI <mailto:AB1OC-10:@261422z4229.14N/07116.31WLI> see you!
2013-09-26 10:22:45 VE2VL-9>TU3S7S,VE2PCQ-3,WIDE1,W1UWS-1,N1NCI-3,WIDE2*,qAR,AB1OC-10:`eG9lTJv/"4C}

Note that 10:22:44 packet? Apparently AB1OC-10 copied (ostensibly) it's own packet via the N8VIM digipeater. Now, the question still remains if AB1OC-10 actually transmitted that packet with the payload from N7FMH-10 or if it was originally transmitted by some other station? And how/why?

Interesting question and I've got a vested interest in tracking down what happened since all of the involved stations seem to be running APRSIS32! The real key is lurking in some station's Transmit trace log, assuming it was enabled at the time of the strange packet.

Lynn (D) - KJ4ERJ -Author of APRSISCE for Windows Mobile and Win32



On 9/26/2013 10:53 AM, Fred Hillhouse wrote:

Best regards,
Fred N7FMH




Yahoo! Groups Links







Join APRSISCE@groups.io to automatically receive all group messages.