Thanks for the good info, Scott! You helped me learn something today.
Steve AI9IN
On 2019-12-03 9:42 pm, Scott via AMSAT-BB wrote:
Hey Steve!
The sites like FINDU and APRS.fi scan the APRS internet stream for digipeated packets and scan for certain things.
In the case of ISS digipeats, a site would be looking for packets with "RS0ISS*" in the digipeat path.
However, the APRS-IS system as a whole rejects "duplicate" packets. It's first-come, first-serve if more than one i-Gate hears your packet. Normally that's not an issue but unfortunately it's possible to have packets heard directly on the ground "win" the race and report what they hear on up into the APRS-IS system. Packets gated directly onto the internet won't include the "RS0ISS*" marker that those websites are looking for, but rather will be marked "TCPIP".
So, here's your packet from tonight's pass on the system (as seen at https://aprs.fi/?c=raw&call=AI9IN), but as you can see there's no mention of the ISS:
2019-12-03 20:07:04 CST: AI9IN>CQ,TCPIP*,qAC,T2USANW:=3921.15N/08512.30W-CQ de AI9IN EM79 Oldenburg IN {UISS53}
... and there are many other examples that affect others, too:
2019-12-03 20:11:05 CST: N1RCN>APRS,TCPIP*,qAR,KE4AZZ-4:=2701.15N/08202.30Wy de n1rcn via iss 2019-12-03 20:11:29 CST: N1RCN>APRS,TCPIP*,qAR,KE4AZZ-4: de n1rcn (live) [Unsupported packet format] 2019-12-03 20:11:51 CST: N1RCN>APRS,TCPIP*,qAR,KE4AZZ-4:=2701.15N/08202.30Wy de n1rcn via iss 2019-12-03 20:12:23 CST: N1RCN>APRS,TCPIP*,qAR,KE4AZZ-4:=2701.15N/08202.30Wy de n1rcn via iss 2019-12-03 20:13:01 CST: N1RCN>APRS,TCPIP*,qAR,KE4AZZ-4: de n1rcn (live) [Unsupported packet format] 2019-12-03 20:13:29 CST: N1RCN>APRS,TCPIP*,qAR,KE4AZZ-4:=2701.15N/08202.30Wy de n1rcn via iss
2019-12-03 20:10:23 CST: K4KDR-6>CQ,TCPIP*,qAR,KE4AZZ-4::N1RCN :Heard you via ISS in Montpelier, VA FM17es
2019-12-01 13:34:51 CST: WE4B>SRQX1W,TCPIP*,qAR,KE4AZZ-4:'r(<0x1d>l
<0x1c>S>WE4B EM62 LIVE OP
... so, it's just an issue of which iGate is able to get your digipeated (or heard directly on the ground) packet into the system first. If an iGate is hearing you directly because they live down the street, then the hope would be that the operator there would help out by filtering out your traffic & giving your digipeated packets a chance to make it onto the system (instead of the locally heard packet).
In the case of packets that ARE digipeated by the ISS, but still win the race onto the network and are mis-tagged as "TCPIP*", I can only imagine that that's a configuration issue. The majority of iGates, upon hearing a digipeat from the ISS, forward it onto the APRS network in a way that you'd find it on those websites. I can't say that I know exactly how packets heard from space could get re-tagged as instead digipeated via "TCPIP".
-Scott, K4KDR
========================
On Tue, Dec 3, 2019 at 9:19 PM AI9IN via AMSAT-BB [email protected] wrote:
I just successfully digipeated through the ISS, or so it seemed. My packet came back and showed on my screen on UISS. But it didn't register on the findu.com site for the space station. Why might that happen? I do not believe that has ever happened to me before.
Steve AI9IN
Oldenburg IN
Grid EM79
Sent via [email protected]. AMSAT-NA makes this open forum available to all interested persons worldwide without requiring membership. Opinions expressed are solely those of the author, and do not reflect the official views of AMSAT-NA. Not an AMSAT-NA member? Join now to support the amateur satellite program! Subscription settings: https://www.amsat.org/mailman/listinfo/amsat-bb