Where is "S8RY4Q" generated?


KD7YZ Bob <kd7yz@...>
 

Somewhere in all the wonderful links I have bookmarked on my iPad, from y.all, I have lost where those APWWD10-Like, I guess, "rig identifiers" , are generated.

I ask because, in the last few days, I am seeing this from a parallel Rx here via RTL/SDR on 144.390

---------------------------------------------------------------------------------------------
2:Fm KD7YZ-15 To S8RY4Q Via WIDE2-2 <UI pid=F0 Len=6 >[07:53:26] LTM 0
--------------------------------------------------------------------------------------------------

thanks for the help.

--
KD7YZ Bob EM88LL KWD D710GA ad stacked M2 2m Loops at 50' on a ridgeline, in Appalachian hinterlands


Randy Love
 

That's a Mic-E compressed packet. What you're seeing is part of the posit information. 

I don't have it readily available, but Google APRS Mic-E encoding and you should find the document. It's definitely part of the APRS spec document. 

Randy
WF5X 

On Fri, Jan 24, 2020, 8:01 AM KD7YZ Bob <kd7yz@...> wrote:
Somewhere in all the wonderful links I have bookmarked on my iPad, from y.all, I have lost where those APWWD10-Like, I guess,  "rig identifiers" , are generated.

I ask because, in the last few days, I am seeing this from a parallel Rx here via RTL/SDR on 144.390

---------------------------------------------------------------------------------------------
2:Fm KD7YZ-15 To S8RY4Q Via WIDE2-2 <UI pid=F0 Len=6 >[07:53:26]  LTM 0
--------------------------------------------------------------------------------------------------

thanks for the help.

--
KD7YZ Bob EM88LL KWD D710GA ad stacked M2 2m Loops at 50' on a ridgeline, in Appalachian hinterlands




KD7YZ Bob <kd7yz@...>
 

On Fri, Jan 24, 2020 at 08:34 AM, Randy Love wrote:


APRS Mic-E encoding
I tried various searches relating to that, Mic-E, and do not see how to break-out the S8RY4Q ... nor the

2:Fm N4PWH-10 To APDW15 Via KD7YZ-15,WIDE1*,WIDE2-1 <UI pid=F0 Len=57 >[06:27:56]
!3819.85NI08258.30W#RasPi I-Gate/Digipeater in Grayson KY


APDW15, which I believe means he used DireWolf

I haven't a copy of the one I usually saw on my packets ...something akin to APWWD10-ish as I am using a KWD D710 .. but, at that time I had seen other KWD users and theirs, being 700's, had something similar which included the 700.

I am guessing I have changes a setup in the D710GA or in APRS32-Devel version, that altered what I was sending.

I guess it doesn't really matter as I am getting out; am rx'ing and otherwise Digipeat and iGating ...

just that I was curious what the CallSign TO APWDW10 or TO S8RY4Q breaks down to ... no joy on several googles this morning.

--
KD7YZ Bob EM88LL


KD7YZ Bob <kd7yz@...>
 

for example, looking on Findu, for KD7YZ-15, 5 mins ago, I see I have 2 "TO"'s


KD7YZ-15>S8RY4Q,WIDE2-2,qAR,KG4DVE-1:'oY"l -/]Greenup County 900' MSL Stacked Loops 50'=
KD7YZ-15>APWW10,TCPIP*,qAC,T2OSAKA:T#422,100,048,093,128,000,10100000
KD7YZ-15>APWW10,TCPIP*,qAC,T2OSAKA:T#423,100,048,093,128,000,10100000
KD7YZ-15>APWW10,TCPIP*,qAC,T2OSAKA:<IGATE,MSG_CNT=2,LOC_CNT=3,DIR_CNT=3,RF_CNT=4
KD7YZ-15>S8RY4Q,WIDE2-2,qAR,KG4DVE-1:'oY"l -/]=
--
--
KD7YZ Bob EM88LL


Randy Love
 

So, just to be clear, the D710 is sending beacons position and other type packets using Dire Wolf the same call-SSID (KD7YZ-15) ?

What you're seeing is two different uses of the TO call field. 

The S8RY4Q is from a Mic-E encoded packet which used the TO call to send part of the position information. In that case, the TO call doesn't ID the type of equipment/ software used.  

The APWW10 in the TO call field is an equipment/software identifier. If you look closely at the packets that have that in the TO field, you will notice that they are not position packets,  so they don't need to use the TO call field for that information.

Sorry, I'm on my phone so I can't get to the links directly, but if you go to aprs.org and search the page for APRS spec, you will find in .pdf file that it downloads a definition of Mic-E encoding scheme. On that same page is a link to the APRS 1.1 addendum page which has a link on it to the tocall.txt with the TO call definitions.

The thing to understand here is that the TO call field isn't always used to identify equipment/ software being used, but also can be used as part of the location information when position data is sent in Mic-E format, even in the same equipment/software.

Randy 
WF5X 


On Sat, Jan 25, 2020, 6:57 AM KD7YZ Bob <kd7yz@...> wrote:
for example, looking on Findu, for KD7YZ-15, 5 mins ago, I see I have 2 "TO"'s


KD7YZ-15>S8RY4Q,WIDE2-2,qAR,KG4DVE-1:'oY"l  -/]Greenup County 900' MSL Stacked Loops 50'=
KD7YZ-15>APWW10,TCPIP*,qAC,T2OSAKA:T#422,100,048,093,128,000,10100000
KD7YZ-15>APWW10,TCPIP*,qAC,T2OSAKA:T#423,100,048,093,128,000,10100000
KD7YZ-15>APWW10,TCPIP*,qAC,T2OSAKA:<IGATE,MSG_CNT=2,LOC_CNT=3,DIR_CNT=3,RF_CNT=4
KD7YZ-15>S8RY4Q,WIDE2-2,qAR,KG4DVE-1:'oY"l  -/]=
--
--
KD7YZ Bob EM88LL




KD7YZ Bob <kd7yz@...>
 

"""So, just to be clear, the D710 is sending beacons position and other type packets using Dire Wolf the same call-SSID (KD7YZ-15) ?"""

That's a digipeat from/or through, me, from a friend of mine who is quite blocked from easy RF transmission in my direction ... to his North. He uses DW, I use APRSIS32-Develop

that tocall.txt seems familiar. I'll try to find it here or on the I-Net

thanks again

--
--
KD7YZ Bob EM88LL