[amsat-bb] APRS Satellite PATHs

[Robert Bruninga]

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 <
amsat-bb at amsat.org> 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 <
> amsat-bb at amsat.org> 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 <amsat-bb at amsat.org> 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:amsat-bb-bounces at amsat.org] On Behalf Of Ryan
> > Noguchi via AMSAT-BB
> > Sent: Wednesday, July 10, 2019 12:11 PM
> > To: amsat-bb at amsat.org
> > 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 AMSAT-BB at 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
> >
> _______________________________________________
> Sent via AMSAT-BB at 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
>