Re: How to make a new PORT that listens to a soundcard?

Lynn Deffenbaugh
 

On 12/31/2019 8:10 AM, KD7YZ Bob wrote:
On Sat, Dec 28, 2019 at 05:16 PM, Lynn Deffenbaugh wrote:

I'm trying really hard not to comment on a WIDE1-1,WIDE3-3 path...
---------------------------------------------------------------------------------------------------------
WinMain:2019-12-28T15:36:33.513 RFtoIS:[AGWPE-TELNET ]IGated VE3FFB>CQ,RS0ISS*,RS0ISS,SGATE,WIDE2-1,qAR,KD7YZ-15:=4416.01N/07629.00W-ve3ffr@...
WinMain:2019-12-28T16:25:09.137 RFtoIS:[KWD710(Pkt)]IGated NU3S-7>APK102,KF8YK-2,WIDE1,K8UI-1,CHLSEA,KC8SDN-5*,WIDE3,qAR,KD7YZ-15:=4022.75N/08004.80W_163/002g005t041r p P000h98b10264KU2k
--------------------------------------------------------------------------------------------------------------
HERE'S MY CHANCE TO LEARN SOME MORE ABOUT PROPER APRS THEN ....

SNIPPET:

RFtoIS:[KWD710(Pkt)]IGated NU3S-7>APK102,KF8YK-2,WIDE1,K8UI-1,CHLSEA,KC8SDN-5*,WIDE3,qAR,KD7YZ-15 (location data)

was that NU3S-7 who made up the entire path ??? which includes WIDE3 ??
Yes, the packet originator comes first before the >

I "think" " qAR" KD7YZ-15 has to do with who went RF to Internet Service .. dunno the meaning of qAR though.
Yes, the callsign after the q-construct (qAR in this case) is usually, but not always, the IGate.  You can read more about q Constructs at:

http://www.aprs-is.net/q.aspx

I've never seen WIDE3 before. And the NU3S-7>APK102 ... does that mean the originating station went Program/Internet-service first ... to get the APK102 generated?
No, the >APK102 is the ToCall and identifies the source station as a Kenwood D710.  You can find the documented ToCalls at:

http://aprs.org/aprs11/tocalls.txt


And the inference of the WIDE3 as opposed to a IDE2-1 ?
Here's a deconstruction of the path from that packet:

,KF8YK-2,WIDE1,K8UI-1,CHLSEA,KC8SDN-5*,WIDE3,
KF8YK-2 is a digipeater that first copied the packet.  It appears to have reacted to an original WIDE1-1 path request from the originating station.

K8UI-1 copied that digipeated packet, presumably reacting to a WIDE3-3 component from the originating station.

CHLSEA copied that packet and likely saw a WIDE3-2 unused path component as K8UI-1 would have decremented it.

KC8SDN-5 heard CHLSEA and saw an unused WIDE3-1 which it then reacted to triggering the FIFTH time this packet was put on RF. KC8SDN-5 should have marked the WIDE3 as used (*), but that doesn't show in the packet from above.

Finally KD7YZ-15 (your station) copied the packet from KC8SDN-5 and gated it to the APRS-IS with the qAR code.

thanks for the class.
Any time.  There's a lot to know, and a lot of differences in what you'll see inside packets.


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

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