[aprssig] APRS Stellite active! Re: FAST1 Status?

[Greg Dolkas]

Hi Bob,

Downlink is 437.345.  Both Carl and I were able to digipeat through it last
week, but not since.  Either something's changed on the satellite, or we
have so many folks trying to get through it that it only hears overlapping
packets, which won't work either.  Will try again tonight, if I can.

Greg  KO6TH


On Sun, Dec 11, 2011 at 2:51 PM, Bob Bruninga <bruninga at usna.edu> wrote:

> I just realized that maybe the APRS sig was not made aware of the FAST1
> satellite that has been turned over for APRS digipeating this weekend and
> onward (maybe).  There is lots of emial chatter, but I just noticed it is
> on the AMSAT-BB and maybe APRSSIG people are not aware of it.
>
> Uplink is on 145.825 and downlink is on 437???.  My wife has guests coming
> in a few mintes, so I dont have time to look it up and post it.  I believe
> the digipeating callsign is FAST1.
>
> SO jump in!  In fact, they are actually hoping that we can overload it and
> run the batteries down so that they can get a new reset for some other
> functions.
>
> Bob, WB4APR
>
>
> ---- Original message ----
> >Date: Sun, 11 Dec 2011 10:56:08 -0800
> >From: amsat-bb-bounces at amsat.org (on behalf of "Greg D." <
> ko6th_greg at hotmail.com>)
> >Subject: [amsat-bb] Re: FAST1  Status?
> >To: <w8krf at w8krf.net>,<amsat-bb at amsat.org>
> >
> >
> >Hi Carl,
> >
> >Well, same results here.  Success early in the week, but nothing since.
>  I wonder if our collective traffic has reset something up there?
> >
> >However, on my last try (last night), I copied one beacon clearly -
> decoded and forwarded to IS - but I also heard a few other weak packets by
> ear that were not decoded.  I could tell that they were not beacon packets
> (the long string of G's is very distinctive), so either I was hearing
> somebody uplinking on the downlink, or perhaps other satellite activity on
> 145.825.
> >
> >There was also a portion of the pass where the FM noise would suddenly
> drop for a second and then return a few times.  I suspect that was 9600
> baud traffic from the satellite.  I'm not set up to receive 9600 packet,
> but if that was the case, perhaps we'll have more success digipeating at
> 9600.  Of course, that won't keep the transmitter as occupied - the packets
> are so much shorter - but it would indicate that the satellite is still in
> active digipeat mode.
> >
> >Greg  KO6TH
> >
> >
> >Date: Sun, 11 Dec 2011 07:31:54 -0500
> >From: w8krf at w8krf.net
> >To: amsat-bb at amsat.org
> >Subject: [amsat-bb] FAST1  Status?
> >
> >Has there been a change to FAST1 since Thursday? During two passes on
> >Thursday, I was able to digipeat through it using AGWPE (set to 1k2),
> >UISS, and SatPC.  I have included  a portion of my log below.  Both
> >yesterday (12/10) and this morning (12/11) I was not able to digi
> >through it although I was receiving the beacon.
> >
> >----------------------------------------------------------------
> >[UISS Auto-Log date - Mode: Only Digipeated Packets - 12/8/2011]
> >----------------------------------------------------------------
> >{snip}
> >
> >
> >_______________________________________________
> >Sent via AMSAT-BB at amsat.org. Opinions expressed are those of the author.
> >Not an AMSAT-NA member? Join now to support the amateur satellite program!
> >Subscription settings: http://amsat.org/mailman/listinfo/amsat-bb
>
> _______________________________________________
> aprssig mailing list
> aprssig at tapr.org
> https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.tapr.org/pipermail/aprssig_lists.tapr.org/attachments/20111211/2d901170/attachment.html>