You may be right. Bob Bruninga mentioned a scenario where the ARISS path becomes PSAT, ARISS* because the satellite inserts the call sign. 73 Robert MacHale. KE6BLR Ham Radio License. http://spaceCommunicator.club/igates . Supporting Boy Scout Merit Badges in Radio, Robotics, and Space Exploration
On Tuesday, July 16, 2019, 8:20:01 AM PDT, Ryan Noguchi via AMSAT-BB amsat-bb@amsat.org wrote:
I admit I am not very familiar with the packet format, but that feed seems to identify the satellite that digipeated (or originated) each packet. Yesterday, Christy KB6LTY and I exchanged messages on AISAT, which can be seen in that packet stream, even though I used only the path ARISS. And KE4AZZ had packets digipeated by PSAT2. What am I missing?
73, Ryan AI6DO
On Monday, July 15, 2019, 1:31:37 PM PDT, KE6BLR Robert ke6blr.robert@gmail.com wrote:
Just a thought -- one of the benefits of using the actual call sign (RS0ISS, PSAT, PSAT2) rather than ARISS or APRSAT is for the record. For example, I am calculating the Az/El of each contact based on the digipeated (PSAT*) path. When the digipeated path is ARISS or APRSAT there is no good way to clarify which satellite participated in the packet. http://www.spacecommunicator.club/igates/
See the Az/El columns for PSAT; I plan to add Az/El for others sometime soon.
As a consumer of the data, I prefer seeing the individual call sign. As the user of the radio, I can see how using APRSAT for everything is more convenient. 73
_______________________________________________ Sent via AMSAT-BB@amsat.org. 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