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

Sun Dec 11 23:42:36 EST 2011

"Hit hard" is a tricky thing to do.  If we're all blasting it with RF, the
transmitter may never key up because the receiver may never decode a fully
formed packet.  There's a best load level, as seen by the satellite, beyond
which things drop off rapidly.  Overloading the receiver isn't going to
help the command team in their battery-sucking objective.

Greg  KO6TH

On Sun, Dec 11, 2011 at 3:36 PM, Steve Daniels <
steve at daniels270.eclipse.co.uk> wrote:

> Latest elset is
> FAST 1
> 1 90025U 0        11344.46201349 +.00001221 +00000-0 +18129-3 0 00483
> 2 90025 071.9715 010.5435 0018442 309.0931 050.8588 14.76836683008082
>
> The request was to hit it hard this weekend to force a hard reset and the
> batteries need to be flat to do that, as one of the micro's needed it, the
> only thing that’s happening now seems to be the beacon, I did get through a
> couple of days ago.
>
> They team need to organize another day and let more people know.
> 145.825 up 437.345 down path is FAST1
>
> Steve Daniels
> G6UIM
> Torbay Freecycle Moderator
>
> -----Original Message-----
> From: aprssig-bounces at tapr.org [mailto:aprssig-bounces at tapr.org] On Behalf
> Of Andrew P.
> Sent: 11 December 2011 23:25
> To: Bob Bruninga ; aprssig at tapr.org
> Subject: Re: [aprssig] APRS Stellite active! Re: FAST1 Status?
>
> Is there an elset available for the satellite so we know when it's above
> the
> horizon?
>
> Andrew, KA2DDO
>
> Sent from my Verizon Wireless BlackBerry
>
> -----Original Message-----
> From: Bob Bruninga <bruninga at usna.edu>
> Date: Sun, 11 Dec 2011 22:51:56
> To: <aprssig at tapr.org>
> Subject: [aprssig] APRS Stellite active! Re: FAST1  Status?
>
> 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
>
> _______________________________________________
> aprssig mailing list
> aprssig at tapr.org
> https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig
>
>
> _______________________________________________
> 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/ccb79b5a/attachment.html>