Greetings,
According to http://www.aprs.org/iss-faq.html WHAT PATH DO I USE? All APRS satellites and the ISS support the generic paths of ARISS or APRSAT. Since all of these satellites supports the same generic paths (when properly configured), this means you can operate either ISS or PCsat or PSAT without reconfiguring your TNC! Just set your UNPROTO path to APRS VIA ARISS and it should work with all APRS birds.
And: http://aprs.org/psat2.html Sister APRS Satellites: Other APRS transponder satellites on orbit or in work all share a common uplink, a generic digipeter alias (APRSAT and ARISS) and a common downlink (145.825 MHz) so all user traffic appears on the live APRS satellite downlink page and ISS downlink page. The graphic below shows how the commonality of all this operaation integrates together with worldwide users and the internet linked ground stations.
Are these statements really true? If so, why would I consider using the PATH of PFS3-1 for FalconSAT-3 or RS0ISS for ISS?
Thank you!
Best regards, Fred N7FMH
--- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus
FalconSat-3 is a different beast: 9600 bps vs. 1200 bps, and crossband at different frequencies than the 1200 bps packet satellites. If you want to be digipeated by FalconSat-3, you need to use the PFS3-1 PATH.
73, Ryan AI6DO
On Wednesday, July 10, 2019, 6:53:47 AM PDT, Fred Hillhouse via AMSAT-BB [email protected] wrote:
Greetings,
According to http://www.aprs.org/iss-faq.html WHAT PATH DO I USE? All APRS satellites and the ISS support the generic paths of ARISS or APRSAT. Since all of these satellites supports the same generic paths (when properly configured), this means you can operate either ISS or PCsat or PSAT without reconfiguring your TNC! Just set your UNPROTO path to APRS VIA ARISS and it should work with all APRS birds.
And: http://aprs.org/psat2.html Sister APRS Satellites: Other APRS transponder satellites on orbit or in work all share a common uplink, a generic digipeter alias (APRSAT and ARISS) and a common downlink (145.825 MHz) so all user traffic appears on the live APRS satellite downlink page and ISS downlink page. The graphic below shows how the commonality of all this operaation integrates together with worldwide users and the internet linked ground stations.
Are these statements really true? If so, why would I consider using the PATH of PFS3-1 for FalconSAT-3 or RS0ISS for ISS?
Thank you!
Best regards, Fred N7FMH
Regardless of the other operational requirements of FalconSAT-3, you are saying FalconSAT-3 will not digipeat using the generic paths. That means the text in the links provided is incorrect. Or is there some other qualifier I have missed?
PSAT2 is also a different beast apparently. The text in the link imply APRS uplinks are narrowband. From the PSAT2 link:
Uplinks: 145.825 MHz narroband [sic] FM packet and 29.4815 MHz SSB PSK31 User Station Software Configuration: First bullet - Radios must be in Narrowband and track to 1 KHz Doppler on the uplink.
The reason for asking is to be able to make as few changes to an HT (D72) as possible. And the main use is to achieve a digipeat. When a satellite is the only APRS network available it could be a useful way to get information out.
Best regards, Fred N7FMH
-----Original Message----- From: AMSAT-BB [mailto:[email protected]] On Behalf Of Ryan Noguchi via AMSAT-BB Sent: Wednesday, July 10, 2019 12:11 PM To: [email protected] Subject: Re: [amsat-bb] APRS Satellite PATHs
FalconSat-3 is a different beast: 9600 bps vs. 1200 bps, and crossband at different frequencies than the 1200 bps packet satellites. If you want to be digipeated by FalconSat-3, you need to use the PFS3-1 PATH.
73, Ryan AI6DO
On Wednesday, July 10, 2019, 6:53:47 AM PDT, Fred Hillhouse via AMSAT-BB [email protected] wrote:
Greetings,
According to http://www.aprs.org/iss-faq.html WHAT PATH DO I USE? All APRS satellites and the ISS support the generic paths of ARISS or APRSAT. Since all of these satellites supports the same generic paths (when properly configured), this means you can operate either ISS or PCsat or PSAT without reconfiguring your TNC! Just set your UNPROTO path to APRS VIA ARISS and it should work with all APRS birds.
And: http://aprs.org/psat2.html Sister APRS Satellites: Other APRS transponder satellites on orbit or in work all share a common uplink, a generic digipeter alias (APRSAT and ARISS) and a common downlink (145.825 MHz) so all user traffic appears on the live APRS satellite downlink page and ISS downlink page. The graphic below shows how the commonality of all this operaation integrates together with worldwide users and the internet linked ground stations.
Are these statements really true? If so, why would I consider using the PATH of PFS3-1 for FalconSAT-3 or RS0ISS for ISS?
Thank you!
Best regards, Fred N7FMH
_______________________________________________ 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
--- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus
Yes, that's correct. FalconSat-3 doesn't digipeat using the generic ARISS or APRSAT paths.
Agreed, it's a pain to have to keep changing PATH, baud rate, and data band between FalconSat-3 and the other packet satellites. At least there are only two configurations to have to toggle between. Once you've done it a couple dozen times, it becomes second nature.
Yes, PSAT2 (and apparently also AISAT) may need to use Narrow FM mode, but the mode can be easily programmed into memory channels. I just set up a different set of memory channels for PSAT2 and AISAT to set that mode and enable (crude) Doppler correction. I haven't used them yet so don't know if 5 kHz steps will cut it.
73, Ryan AI6DO
On Wednesday, July 10, 2019, 10:14:18 AM PDT, Fred Hillhouse via AMSAT-BB [email protected] wrote:
Regardless of the other operational requirements of FalconSAT-3, you are saying FalconSAT-3 will not digipeat using the generic paths. That means the text in the links provided is incorrect. Or is there some other qualifier I have missed?
PSAT2 is also a different beast apparently. The text in the link imply APRS uplinks are narrowband. From the PSAT2 link:
Uplinks: 145.825 MHz narroband [sic] FM packet and 29.4815 MHz SSB PSK31 User Station Software Configuration: First bullet - Radios must be in Narrowband and track to 1 KHz Doppler on the uplink.
The reason for asking is to be able to make as few changes to an HT (D72) as possible. And the main use is to achieve a digipeat. When a satellite is the only APRS network available it could be a useful way to get information out.
Best regards, Fred N7FMH
-----Original Message----- From: AMSAT-BB [mailto:[email protected]] On Behalf Of Ryan Noguchi via AMSAT-BB Sent: Wednesday, July 10, 2019 12:11 PM To: [email protected] Subject: Re: [amsat-bb] APRS Satellite PATHs
FalconSat-3 is a different beast: 9600 bps vs. 1200 bps, and crossband at different frequencies than the 1200 bps packet satellites. If you want to be digipeated by FalconSat-3, you need to use the PFS3-1 PATH.
73, Ryan AI6DO
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
On Wed, Jul 10, 2019 at 11:38 AM Ryan Noguchi via AMSAT-BB < [email protected]> wrote:
Yes, that's correct. FalconSat-3 doesn't digipeat using the generic ARISS or APRSAT paths.
Agreed, it's a pain to have to keep changing PATH, baud rate, and data band between FalconSat-3 and the other packet satellites. At least there are only two configurations to have to toggle between. Once you've done it a couple dozen times, it becomes second nature.
Yes, PSAT2 (and apparently also AISAT) may need to use Narrow FM mode, but the mode can be easily programmed into memory channels. I just set up a different set of memory channels for PSAT2 and AISAT to set that mode and enable (crude) Doppler correction. I haven't used them yet so don't know if 5 kHz steps will cut it.
73, Ryan AI6DO
On Wednesday, July 10, 2019, 10:14:18 AM PDT, Fred Hillhouse viaAMSAT-BB [email protected] wrote:
Regardless of the other operational requirements of FalconSAT-3, you are saying FalconSAT-3 will not digipeat using the generic paths. That means the text in the links provided is incorrect. Or is there some other qualifier I have missed?
PSAT2 is also a different beast apparently. The text in the link imply APRS uplinks are narrowband. From the PSAT2 link:
Uplinks: 145.825 MHz narroband [sic] FM packet and 29.4815 MHz SSB PSK31 User Station Software Configuration: First bullet - Radios must be in Narrowband and track to 1 KHz Doppler on the uplink.
The reason for asking is to be able to make as few changes to an HT (D72) as possible. And the main use is to achieve a digipeat. When a satellite is the only APRS network available it could be a useful way to get information out.
Best regards, Fred N7FMH
-----Original Message----- From: AMSAT-BB [mailto:[email protected]] On Behalf Of Ryan Noguchi via AMSAT-BB Sent: Wednesday, July 10, 2019 12:11 PM To: [email protected] Subject: Re: [amsat-bb] APRS Satellite PATHs
FalconSat-3 is a different beast: 9600 bps vs. 1200 bps, and crossband at different frequencies than the 1200 bps packet satellites. If you want to be digipeated by FalconSat-3, you need to use the PFS3-1 PATH.
73, Ryan AI6DO
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
Actually, when you use ARISS or APRSAT then the signal comes down as RS0ISS* if it went via ISS, and comes down as PSAT,ARISS* or PSAT2,ARISS* if it went via one of those. Yes, it is a parsing pain, but a simple rule. If you see ARISS*, then simply find the actual satellite in the previous field.
On Mon, Jul 15, 2019 at 4:31 PM KE6BLR Robert via AMSAT-BB < [email protected]> 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
On Wed, Jul 10, 2019 at 11:38 AM Ryan Noguchi via AMSAT-BB < [email protected]> wrote:
Yes, that's correct. FalconSat-3 doesn't digipeat using the generic
ARISS
or APRSAT paths.
Agreed, it's a pain to have to keep changing PATH, baud rate, and data band between FalconSat-3 and the other packet satellites. At least there are only two configurations to have to toggle between. Once you've done
it
a couple dozen times, it becomes second nature.
Yes, PSAT2 (and apparently also AISAT) may need to use Narrow FM mode,
but
the mode can be easily programmed into memory channels. I just set up a different set of memory channels for PSAT2 and AISAT to set that mode and enable (crude) Doppler correction. I haven't used them yet so don't know
if
5 kHz steps will cut it.
73, Ryan AI6DO
On Wednesday, July 10, 2019, 10:14:18 AM PDT, Fred Hillhouse viaAMSAT-BB [email protected] wrote:
Regardless of the other operational requirements of FalconSAT-3, you are saying FalconSAT-3 will not digipeat using the generic paths. That means the text in the links provided is incorrect. Or is there some other qualifier I have missed?
PSAT2 is also a different beast apparently. The text in the link imply APRS uplinks are narrowband. From the PSAT2 link:
Uplinks: 145.825 MHz narroband [sic] FM packet and 29.4815 MHz SSB PSK31 User Station Software Configuration: First bullet - Radios must be in Narrowband and track to 1 KHz Doppler on the uplink.
The reason for asking is to be able to make as few changes to an HT (D72) as possible. And the main use is to achieve a digipeat. When a satellite
is
the only APRS network available it could be a useful way to get
information
out.
Best regards, Fred N7FMH
-----Original Message----- From: AMSAT-BB [mailto:[email protected]] On Behalf Of Ryan Noguchi via AMSAT-BB Sent: Wednesday, July 10, 2019 12:11 PM To: [email protected] Subject: Re: [amsat-bb] APRS Satellite PATHs
FalconSat-3 is a different beast: 9600 bps vs. 1200 bps, and crossband
at
different frequencies than the 1200 bps packet satellites. If you want to be digipeated by FalconSat-3, you need to use the PFS3-1 PATH.
73, Ryan AI6DO
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
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
That is good to know!
In the radio there are two settings; Network and Packet Path.
Does the "Network" stay "APRS"? Or should it be set to "ARISS"? I assume the Packet Path becomes "ARISS" or "APRSAT". Correct?
Thank you!
Best regards, Fred N7FMH
-----Original Message----- From: AMSAT-BB [mailto:[email protected]] On Behalf Of Robert Bruninga via AMSAT-BB Sent: Sunday, July 14, 2019 5:26 PM To: KE6BLR Robert; amsat bb Subject: Re: [amsat-bb] APRS Satellite PATHs
Actually, when you use ARISS or APRSAT then the signal comes down as RS0ISS* if it went via ISS, and comes down as PSAT,ARISS* or PSAT2,ARISS* if it went via one of those. Yes, it is a parsing pain, but a simple rule. If you see ARISS*, then simply find the actual satellite in the previous field.
On Mon, Jul 15, 2019 at 4:31 PM KE6BLR Robert via AMSAT-BB < [email protected]> 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
On Wed, Jul 10, 2019 at 11:38 AM Ryan Noguchi via AMSAT-BB < [email protected]> wrote:
Yes, that's correct. FalconSat-3 doesn't digipeat using the generic
ARISS
or APRSAT paths.
Agreed, it's a pain to have to keep changing PATH, baud rate, and data band between FalconSat-3 and the other packet satellites. At least there are only two configurations to have to toggle between. Once you've done
it
a couple dozen times, it becomes second nature.
Yes, PSAT2 (and apparently also AISAT) may need to use Narrow FM mode,
but
the mode can be easily programmed into memory channels. I just set up a different set of memory channels for PSAT2 and AISAT to set that mode
and
enable (crude) Doppler correction. I haven't used them yet so don't know
if
5 kHz steps will cut it.
73, Ryan AI6DO
On Wednesday, July 10, 2019, 10:14:18 AM PDT, Fred Hillhouse viaAMSAT-BB [email protected] wrote:
Regardless of the other operational requirements of FalconSAT-3, you
are
saying FalconSAT-3 will not digipeat using the generic paths. That means the text in the links provided is incorrect. Or is there some other qualifier I have missed?
PSAT2 is also a different beast apparently. The text in the link imply APRS uplinks are narrowband. From the PSAT2 link:
Uplinks: 145.825 MHz narroband [sic] FM packet and 29.4815 MHz SSB PSK31 User Station Software Configuration: First bullet - Radios must be in Narrowband and track to 1 KHz Doppler
on
the uplink.
The reason for asking is to be able to make as few changes to an HT
(D72)
as possible. And the main use is to achieve a digipeat. When a satellite
is
the only APRS network available it could be a useful way to get
information
out.
Best regards, Fred N7FMH
-----Original Message----- From: AMSAT-BB [mailto:[email protected]] On Behalf Of Ryan Noguchi via AMSAT-BB Sent: Wednesday, July 10, 2019 12:11 PM To: [email protected] Subject: Re: [amsat-bb] APRS Satellite PATHs
FalconSat-3 is a different beast: 9600 bps vs. 1200 bps, and crossband
at
different frequencies than the 1200 bps packet satellites. If you want
to
be digipeated by FalconSat-3, you need to use the PFS3-1 PATH.
73, Ryan AI6DO
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
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
_______________________________________________ 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
--- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus
yes, network stays APRS. Path is ARISS
On Mon, Jul 15, 2019 at 7:08 PM Fred Hillhouse via AMSAT-BB < [email protected]> wrote:
That is good to know!
In the radio there are two settings; Network and Packet Path.
Does the "Network" stay "APRS"? Or should it be set to "ARISS"? I assume the Packet Path becomes "ARISS" or "APRSAT". Correct?
Thank you!
Best regards, Fred N7FMH
-----Original Message----- From: AMSAT-BB [mailto:[email protected]] On Behalf Of Robert Bruninga via AMSAT-BB Sent: Sunday, July 14, 2019 5:26 PM To: KE6BLR Robert; amsat bb Subject: Re: [amsat-bb] APRS Satellite PATHs
Actually, when you use ARISS or APRSAT then the signal comes down as RS0ISS* if it went via ISS, and comes down as PSAT,ARISS* or PSAT2,ARISS* if it went via one of those. Yes, it is a parsing pain, but a simple rule. If you see ARISS*, then simply find the actual satellite in the previous field.
On Mon, Jul 15, 2019 at 4:31 PM KE6BLR Robert via AMSAT-BB < [email protected]> 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
On Wed, Jul 10, 2019 at 11:38 AM Ryan Noguchi via AMSAT-BB < [email protected]> wrote:
Yes, that's correct. FalconSat-3 doesn't digipeat using the generic
ARISS
or APRSAT paths.
Agreed, it's a pain to have to keep changing PATH, baud rate, and data band between FalconSat-3 and the other packet satellites. At least
there
are only two configurations to have to toggle between. Once you've done
it
a couple dozen times, it becomes second nature.
Yes, PSAT2 (and apparently also AISAT) may need to use Narrow FM mode,
but
the mode can be easily programmed into memory channels. I just set up a different set of memory channels for PSAT2 and AISAT to set that mode
and
enable (crude) Doppler correction. I haven't used them yet so don't
know
if
5 kHz steps will cut it.
73, Ryan AI6DO
On Wednesday, July 10, 2019, 10:14:18 AM PDT, Fred Hillhouse viaAMSAT-BB [email protected] wrote:
Regardless of the other operational requirements of FalconSAT-3, you
are
saying FalconSAT-3 will not digipeat using the generic paths. That
means
the text in the links provided is incorrect. Or is there some other qualifier I have missed?
PSAT2 is also a different beast apparently. The text in the link imply APRS uplinks are narrowband. From the PSAT2 link:
Uplinks: 145.825 MHz narroband [sic] FM packet and 29.4815 MHz SSB
PSK31
User Station Software Configuration: First bullet - Radios must be in Narrowband and track to 1 KHz Doppler
on
the uplink.
The reason for asking is to be able to make as few changes to an HT
(D72)
as possible. And the main use is to achieve a digipeat. When a
satellite
is
the only APRS network available it could be a useful way to get
information
out.
Best regards, Fred N7FMH
-----Original Message----- From: AMSAT-BB [mailto:[email protected]] On Behalf Of Ryan Noguchi via AMSAT-BB Sent: Wednesday, July 10, 2019 12:11 PM To: [email protected] Subject: Re: [amsat-bb] APRS Satellite PATHs
FalconSat-3 is a different beast: 9600 bps vs. 1200 bps, and crossband
at
different frequencies than the 1200 bps packet satellites. If you want
to
be digipeated by FalconSat-3, you need to use the PFS3-1 PATH.
73, Ryan AI6DO
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
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
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
This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus
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
Ah, makes sense. Thanks for sharing! 73 Robert MacHale. KE6BLR Ham Radio License. http://spaceCommunicator.club/igates . Supporting Boy Scout Merit Badges in Radio, Robotics, and Space Exploration
On Monday, July 15, 2019, 2:27:34 PM PDT, Robert Bruninga via AMSAT-BB [email protected] wrote:
Actually, when you use ARISS or APRSAT then the signal comes down as RS0ISS* if it went via ISS, and comes down as PSAT,ARISS* or PSAT2,ARISS* if it went via one of those. Yes, it is a parsing pain, but a simple rule. If you see ARISS*, then simply find the actual satellite in the previous field.
On Mon, Jul 15, 2019 at 4:31 PM KE6BLR Robert via AMSAT-BB < [email protected]> 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
On Wed, Jul 10, 2019 at 11:38 AM Ryan Noguchi via AMSAT-BB < [email protected]> wrote:
Yes, that's correct. FalconSat-3 doesn't digipeat using the generic
ARISS
or APRSAT paths.
Agreed, it's a pain to have to keep changing PATH, baud rate, and data band between FalconSat-3 and the other packet satellites. At least there are only two configurations to have to toggle between. Once you've done
it
a couple dozen times, it becomes second nature.
Yes, PSAT2 (and apparently also AISAT) may need to use Narrow FM mode,
but
the mode can be easily programmed into memory channels. I just set up a different set of memory channels for PSAT2 and AISAT to set that mode and enable (crude) Doppler correction. I haven't used them yet so don't know
if
5 kHz steps will cut it.
73, Ryan AI6DO
On Wednesday, July 10, 2019, 10:14:18 AM PDT, Fred Hillhouse via AMSAT-BB [email protected] wrote:
Regardless of the other operational requirements of FalconSAT-3, you are saying FalconSAT-3 will not digipeat using the generic paths. That means the text in the links provided is incorrect. Or is there some other qualifier I have missed?
PSAT2 is also a different beast apparently. The text in the link imply APRS uplinks are narrowband. From the PSAT2 link:
Uplinks: 145.825 MHz narroband [sic] FM packet and 29.4815 MHz SSB PSK31 User Station Software Configuration: First bullet - Radios must be in Narrowband and track to 1 KHz Doppler on the uplink.
The reason for asking is to be able to make as few changes to an HT (D72) as possible. And the main use is to achieve a digipeat. When a satellite
is
the only APRS network available it could be a useful way to get
information
out.
Best regards, Fred N7FMH
-----Original Message----- From: AMSAT-BB [mailto:[email protected]] On Behalf Of Ryan Noguchi via AMSAT-BB Sent: Wednesday, July 10, 2019 12:11 PM To: [email protected] Subject: Re: [amsat-bb] APRS Satellite PATHs
FalconSat-3 is a different beast: 9600 bps vs. 1200 bps, and crossband
at
different frequencies than the 1200 bps packet satellites. If you want to be digipeated by FalconSat-3, you need to use the PFS3-1 PATH.
73, Ryan AI6DO
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
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
_______________________________________________ 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
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 [email protected] 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
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 [email protected] 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 [email protected] 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 [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
If so, why would I consider using the PATH of PFS3-1 for FalconSAT-3 or
RS0ISS for ISS?
Here is the APRS satellite Sujmmary: See http://aprs.org/sats.html
FALCONSAT is not a generic APRS satellite on 145.825 like the others And was only turned over to APRS digipeating after it finished it original mission. It has a different frequency, a different modem (9600 baud) and is full duplex and is not identified as being a "generic" digipeater with those aliases. But it is a great new capability for Mobiles (the only 9600 baud APRS satellite).
The APRSAT and ARISS aliases will work with ISS as long as the kenwood radio is acting as the TNC because it can support multiple aliases. But sometimes, the backup TNC is used (going back a decade) and in that case, it only supports the RS0ISS call and not the added APRSAT and ARISS aliases.
Hope that helps. Bob
-----Original Message----- From: AMSAT-BB [email protected] On Behalf Of Fred Hillhouse via AMSAT-BB Sent: Wednesday, July 10, 2019 9:51 AM To: [email protected] Subject: [amsat-bb] APRS Satellite PATHs
Greetings,
According to http://www.aprs.org/iss-faq.html WHAT PATH DO I USE? All APRS satellites and the ISS support the generic paths of ARISS or APRSAT. Since all of these satellites supports the same generic paths (when properly configured), this means you can operate either ISS or PCsat or PSAT without reconfiguring your TNC! Just set your UNPROTO path to APRS VIA ARISS and it should work with all APRS birds.
And: http://aprs.org/psat2.html Sister APRS Satellites: Other APRS transponder satellites on orbit or in work all share a common uplink, a generic digipeter alias (APRSAT and ARISS) and a common downlink (145.825 MHz) so all user traffic appears on the live APRS satellite downlink page and ISS downlink page. The graphic below shows how the commonality of all this operaation integrates together with worldwide users and the internet linked ground stations.
Are these statements really true? If so, why would I consider using the PATH of PFS3-1 for FalconSAT-3 or RS0ISS for ISS?
Thank you!
Best regards, Fred N7FMH
--- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus
_______________________________________________ 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
participants (5)
-
Fred Hillhouse -
KE6BLR Robert -
Robert Bruninga -
Robert MacHale -
Ryan Noguchi