[amsat-bb] Standard for AMSAT status board observations of FS-3

[Ryan Noguchi]

 The pass I just got on had a much more sedate downlink, with a roughly-estimated average of about one PFS3-1 or PFS3-11 undecoded packet about every 4 seconds or so over the course of the pass. Despite seeing a bunch of beacon and message traffic by WD9EWK and KB6LTY and completing a QSO with WD9EWK, I was able to get that My Message indication for the first time in quite a while, and see my beacons and messages get sent with no more than a second or two delay.  A huge change from the past couple of days, with no change in my configuration. 

I can certainly report FS-3 was Blue for this pass. Thanks for the QSO, Patrick! It seemed like you got a steady stream of traffic on AO-91 just before, enough that I couldn't get through myself, which is my typical experience on the FM birds during daylight hours. 

73, Ryan AI6DO

    On Friday, June 1, 2018, 12:31:01 PM PDT, Patrick STODDARD (WD9EWK/VA7EWK) <amsat-bb at wd9ewk.net> wrote:  
 
 John,

Normally, working FalconSat-3 should be the same as any
other orbiting digipeater, where you would see a "My
Message" or "My Position" notification on your HT's screen
when you are digipeated. FalconSat-3 sends down so much
data, that it is possible your HT misses the digipeated
packet, or it received it with a series of other packets
so fast you miss the on-screen notification. That's why
I find myself checking the listing of stations heard and
message listings during a FalconSat-3 pass, in case I
missed something.