| |
CX2SA > SATDIG 10.12.18 18:54l 629 Lines 23939 Bytes #999 (0) @ WW
BID : AMSATBB13412
Read: GUEST
Subj: AMSAT-BB-digest V13 412
Path: IW8PGT<IR2UBX<SR1BSZ<SV1CMG<ON0AR<OZ5BBS<CX2SA
Sent: 181210/1643Z @:CX2SA.SAL.URY.SOAM #:59878 [Salto] FBB7.00e $:AMSATBB13412
From: CX2SA@CX2SA.SAL.URY.SOAM
To : SATDIG@WW
Today's Topics:
1. AO-95 (Fred Castello)
2. Re: AO-95 (Andrew Glasbrenner)
3. Re: AO-95 (John Brier)
4. Re: AO-95 (Jerry Buxton)
5. ESEO (Ross Biggar)
6. Re: ESEO (JoAnne K9JKM)
7. Re: AO-95 (Don KB2YSI)
8. AO-95 (Chris Bouck)
9. Re: AO-95 (Sean Kutzko)
10. Re: AO-95 (Paul Stoetzer)
11. Re: AO-95 (Zach Metzinger)
----------------------------------------------------------------------
Message: 1
Date: Sun, 9 Dec 2018 19:17:07 -0500
From: Fred Castello <fredcastello@?????.???>
To: AMSAT bbs <amsat-bb@?????.???>
Subject: [amsat-bb] AO-95
Message-ID: <5c0db083.1c69fb81.3ab9e.e22c@??.??????.???>
Content-Type: text/plain; charset="utf-8"
I am just curious why we are not discussing the apparent failure of the
receiver of AO-95. Do we know anything more about the issue?
Thanks all,
Fred ? KF4FC
------------------------------
Message: 2
Date: Sun, 9 Dec 2018 19:47:24 -0500
From: Andrew Glasbrenner <glasbrenner@??????????.???>
To: Fred Castello <fredcastello@?????.???>
Cc: AMSAT bbs <amsat-bb@?????.???>
Subject: Re: [amsat-bb] AO-95
Message-ID: <145D8969-6BEC-4A54-B920-17C8A8942C3B@??????????.???>
Content-Type: text/plain; charset=utf-8
Fred,
Perhaps because there is little useful to be done or said at this point. We
don?t know, and may never know for sure what the exact failure is. Many of
those involved are also in some state of grieving right now after the years
of effort put into this little satellite. Space is hard, and we do the best
we can.
Rest assured that we will continue to monitor the satellite for any changes,
and when the will to work the problem is a little stronger we will seek out
some mega-erp EME stations to try to wiggle the RSSI to further diagnose the
problem. Continued submission of telemetry is very important to this end.
73, Drew, KO4MA
AMSAT VP Operations
> On Dec 9, 2018, at 7:17 PM, Fred Castello <fredcastello@?????.???> wrote:
>
> I am just curious why we are not discussing the apparent failure of the
receiver of AO-95. Do we know anything more about the issue?
> Thanks all,
> Fred ? KF4FC
>
>
> _______________________________________________
> Sent via AMSAT-BB@?????.???. 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: http://www.amsat.org/mailman/listinfo/amsat-bb
------------------------------
Message: 3
Date: Sun, 9 Dec 2018 21:42:59 -0500
From: John Brier <johnbrier@?????.???>
To: Andrew Glasbrenner <glasbrenner@??????????.???>
Cc: AMSAT BB <amsat-bb@?????.???>, Fred Castello
<fredcastello@?????.???>
Subject: Re: [amsat-bb] AO-95
Message-ID:
<CALn0fKOT6fBpUdNeJFaOHKsv-+VOf8pjyQCpCvTqi4Yee=2WJA@????.?????.???>
Content-Type: text/plain; charset="UTF-8"
Very sorry to all the engineers and others who worked on/with AO-95.
Thanks for your service to the community.
73, John Brier KG4AKV
On Sun, Dec 9, 2018, 19:48 Andrew Glasbrenner <glasbrenner@??????????.???
wrote:
> Fred,
>
> Perhaps because there is little useful to be done or said at this point.
> We don?t know, and may never know for sure what the exact failure is. Many
> of those involved are also in some state of grieving right now after the
> years of effort put into this little satellite. Space is hard, and we do
> the best we can.
>
> Rest assured that we will continue to monitor the satellite for any
> changes, and when the will to work the problem is a little stronger we will
> seek out some mega-erp EME stations to try to wiggle the RSSI to further
> diagnose the problem. Continued submission of telemetry is very important
> to this end.
>
> 73, Drew, KO4MA
> AMSAT VP Operations
>
>
> > On Dec 9, 2018, at 7:17 PM, Fred Castello <fredcastello@?????.???>
> wrote:
> >
> > I am just curious why we are not discussing the apparent failure of the
> receiver of AO-95. Do we know anything more about the issue?
> > Thanks all,
> > Fred ? KF4FC
> >
> >
> > _______________________________________________
> > Sent via AMSAT-BB@?????.???. 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: http://www.amsat.org/mailman/listinfo/amsat-bb
>
> _______________________________________________
> Sent via AMSAT-BB@?????.???. 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: http://www.amsat.org/mailman/listinfo/amsat-bb
>
------------------------------
Message: 4
Date: Mon, 10 Dec 2018 01:01:40 -0600
From: Jerry Buxton <n0jy@?????.???>
To: amsat-bb@?????.???
Subject: Re: [amsat-bb] AO-95
Message-ID: <f2484a8b-26cd-acb3-b9d1-9d23d428e692@?????.???>
Content-Type: text/plain; charset=utf-8
On 12/9/2018 18:17, Fred Castello wrote:
> I am just curious why we are not discussing the apparent failure of the
receiver of AO-95. Do we know anything more about the issue?
> Thanks all,
> Fred ? KF4FC
>
Hi Fred,
I'm not sure if you were referring to We the amsat-bb list members?? I
have to say that I figured there would be much more chatter here than I
have seen so far, anyway.?
If by We you mean We the AMSAT Engineering team, of course we have been
discussing the problem, possible causes, and working on leads ever since
the anomaly became known.? Certainly many of us are unhappy at not
succeeding in making everybody else happy, but that is not the reason
for my silence in terms of sharing with the public.? Right now, with no
readily apparent reason or reasons for the behavior, there is nothing
else to report.
The situation has gone from a commissioning to being challenge, which is
actually fun and we're on it.?? We are looking at data from a number of
sources, as well as our past experiences with the other Fox-1 satellites
during their journey from the BOM to orbit.? Ideas such as the one Drew
mentioned about employing a mega-QRO station to see if it can be heard
by the bird have been on the table for several days but I don't plan to
report or discuss every thought we have in working this unless and until
it is something of merit or actionable.? As you probably know, our
resources are limited and it's all volunteered time.? Most if not all of
our remaining Fox-1 engineers are also involved in the GOLF-TEE project
so I have asked them to give that first priority with their available
volunteer time in order to keep the schedule.? AO-95 is in orbit now and
we can vary the amount of attention on her as resources allow in order
to achieve both goals.? If the results of our investigation point to a
possibility of recovery be it partial, full, or some workaround method,
we would all like to see her working as much as the rest of you and that
is a driver for this investigation.? But perhaps the most important
driver is that there are lessons to be learned for the betterment of
future missions.? I expect us to continue to look for the cause or
causes until we have results or reach a dead end because of the
inability to take the lid off and look inside AO-95.
The main point of the ANS is to let everyone know that commissioning
won't be happening, certainly not in the period that everyone has grown
accustomed to if at all, so that members and users can get on with
enjoying their activities on all of the other satellites.? Many had been
waiting in anticipation and wondering why talk of AO-95 commissioning
seemed so quiet, so once we were sure that it didn't appear to be an
intermittent thing we shared the news.? And as I said in the ANS, I will
certainly be keeping everyone posted when we have something new to
report so in the meantime please carry on and enjoy the birds!
Jerry Buxton, N?JY
------------------------------
Message: 5
Date: Mon, 10 Dec 2018 03:31:54 +0000
From: Ross Biggar <ross.biggar@???????.???>
To: "amsat-bb@?????.???? <amsat-bb@?????.???>
Subject: [amsat-bb] ESEO
Message-ID:
<BN6PR22MB0115C4622C3620E76E20D9A4F7A50@?????????????.????????.????.???????.??
?>
Content-Type: text/plain; charset="iso-8859-1"
Can someone please tell me what is happening with ESEO, has it been tested
and is it ready for operation yet?
Thanks
Ross
ZL1WN
------------------------------
Message: 6
Date: Mon, 10 Dec 2018 07:49:22 -0600
From: "JoAnne K9JKM" <joanne.k9jkm@?????.???>
To: <amsat-bb@?????.???>
Subject: Re: [amsat-bb] ESEO
Message-ID: <5c0e6ee0.1c69fb81.b7ade.fc55@??.??????.???>
Content-Type: text/plain; charset="iso-8859-1"
Hello Ross,
> Can someone please tell me what is happening with ESEO, has it been tested
> and is it ready for operation yet?
See below for the ESEO excerpt provided by the FUNcube operations team in
the AMSAT News Service bulletins. The full text of the bulletin is posted
at:
http://amsat.org/pipermail/ans/2018/001076.html
ESEO (FUNcube 4)
----------------
Signals and telemetry continue to be received from ESEO from the
main platform transmitter on 437.00 MHz. The are bursts of 9k6
data transmitted every one minute. Full details of these trans-
missions, including the telemetry equations, can now be found at
https://www.esa.int/Education/ESEO. Daniel Est?vez, EA4GPZ, com-
mented that the beacon at 437.000 MHz it is not standard FSK AX.25,
and it cannot be decoded with direwolf, UZ7HO or similar.
The AMSAT payload transmitter on 145.895MHz has not yet been act-
ivated and it seems likely to be sometime before this occurs.
Uplink: 1263.500 MHz FM voice with 67Hz CTCSS tone
Downlink: 145.895 MHz FM voice and telemetry
Telemetry: 145.875 MHz Use ESEO Dashboard from AMSAT-UK
https://download.funcube.org.uk/ESEO_Dashboard_v1177.msi
See also the AMSAT-UK summary of mission descriptions and
frequencies at:
https://amsat-uk.org/2018/11/14/ssoa-amateur-radio-satellites/
--
73 de JoAnne K9JKM
k9jkm@?????.???
> -----Original Message-----
> From: AMSAT-BB [mailto:amsat-bb-bounces@?????.???? On Behalf Of Ross
Biggar
> Sent: Sunday, December 09, 2018 9:32 PM
> To: amsat-bb@?????.???
> Subject: [amsat-bb] ESEO
>
> Can someone please tell me what is happening with ESEO, has it been tested
> and is it ready for operation yet?
>
> Thanks
> Ross
> ZL1WN
> _______________________________________________
> Sent via AMSAT-BB@?????.???. 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: http://www.amsat.org/mailman/listinfo/amsat-bb
------------------------------
Message: 7
Date: Mon, 10 Dec 2018 10:05:37 -0500
From: Don KB2YSI <kb2ysi@?????.???>
To: n0jy@?????.???
Cc: AMSAT BB <amsat-bb@?????.???>
Subject: Re: [amsat-bb] AO-95
Message-ID:
<CAAJiE8PojtdT-ihpbFC4u=oU_txS5MuMRC7Ltvna5A+=dxho+g@????.?????.???>
Content-Type: text/plain; charset="UTF-8"
Thanks to Drew and Jerry for the additional information, even though the
situation is not what anyone wanted hear.
I will echo John's statement. For those who have worked so hard on this
bird, along with those before it and those to come, THANK YOU! Without
people with the knowledge and skills to get a satellite into orbit, we
would not have anything to enjoy.
On Mon, Dec 10, 2018 at 2:03 AM Jerry Buxton <n0jy@?????.???> wrote:
> On 12/9/2018 18:17, Fred Castello wrote:
> > I am just curious why we are not discussing the apparent failure of the
> receiver of AO-95. Do we know anything more about the issue?
> > Thanks all,
> > Fred ? KF4FC
> >
> Hi Fred,
>
> I'm not sure if you were referring to We the amsat-bb list members? I
> have to say that I figured there would be much more chatter here than I
> have seen so far, anyway.
>
> If by We you mean We the AMSAT Engineering team, of course we have been
> discussing the problem, possible causes, and working on leads ever since
> the anomaly became known. Certainly many of us are unhappy at not
> succeeding in making everybody else happy, but that is not the reason
> for my silence in terms of sharing with the public. Right now, with no
> readily apparent reason or reasons for the behavior, there is nothing
> else to report.
>
> The situation has gone from a commissioning to being challenge, which is
> actually fun and we're on it. We are looking at data from a number of
> sources, as well as our past experiences with the other Fox-1 satellites
> during their journey from the BOM to orbit. Ideas such as the one Drew
> mentioned about employing a mega-QRO station to see if it can be heard
> by the bird have been on the table for several days but I don't plan to
> report or discuss every thought we have in working this unless and until
> it is something of merit or actionable. As you probably know, our
> resources are limited and it's all volunteered time. Most if not all of
> our remaining Fox-1 engineers are also involved in the GOLF-TEE project
> so I have asked them to give that first priority with their available
> volunteer time in order to keep the schedule. AO-95 is in orbit now and
> we can vary the amount of attention on her as resources allow in order
> to achieve both goals. If the results of our investigation point to a
> possibility of recovery be it partial, full, or some workaround method,
> we would all like to see her working as much as the rest of you and that
> is a driver for this investigation. But perhaps the most important
> driver is that there are lessons to be learned for the betterment of
> future missions. I expect us to continue to look for the cause or
> causes until we have results or reach a dead end because of the
> inability to take the lid off and look inside AO-95.
>
> The main point of the ANS is to let everyone know that commissioning
> won't be happening, certainly not in the period that everyone has grown
> accustomed to if at all, so that members and users can get on with
> enjoying their activities on all of the other satellites. Many had been
> waiting in anticipation and wondering why talk of AO-95 commissioning
> seemed so quiet, so once we were sure that it didn't appear to be an
> intermittent thing we shared the news. And as I said in the ANS, I will
> certainly be keeping everyone posted when we have something new to
> report so in the meantime please carry on and enjoy the birds!
>
> Jerry Buxton, N?JY
>
>
> _______________________________________________
> Sent via AMSAT-BB@?????.???. 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: http://www.amsat.org/mailman/listinfo/amsat-bb
>
--
73,
Don KB2YSI
https://www.hamqth.com/kb2ysi
------------------------------
Message: 8
Date: Mon, 10 Dec 2018 11:25:35 -0500
From: Chris Bouck <cbouck01@?????.??.???>
To: "amsat-bb@?????.???? <amsat-bb@?????.???>
Subject: [amsat-bb] AO-95
Message-ID: <33ad6899-3efa-3a90-bc87-f9eb0b934d6a@?????.??.???>
Content-Type: text/plain; charset=utf-8; format=flowed
Where are you getting the information on this spacecraft?
Chris KB4CMF
---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus
------------------------------
Message: 9
Date: Mon, 10 Dec 2018 11:34:14 -0500
From: Sean Kutzko <kx9x@?????.???>
To: Don KB2YSI <kb2ysi@?????.???>
Cc: AMSAT BB <amsat-bb@?????.???>
Subject: Re: [amsat-bb] AO-95
Message-ID: <B97E1009-2A27-443A-B7BD-2B90251D2723@?????.???>
Content-Type: text/plain; charset=utf-8
Hear, hear. I?m certainly not qualified to troubleshoot a satellite from
600km away, so I will leave that to the experts and do what I can to help,
which consists of contributing to AMSAT and staying out of the way of the
engineers.
As somebody recently said, ?Space is hard.? There?s no guarantee any of
these missions will be a success. Does that mean AMSAT shouldn?t try? Heck
no; please keep trying. And I?ll happily contribute to future efforts to the
best of my ability, because the success rate is still pretty high, and it
isn?t cheap. I get a great deal of pleasure from satellite operating; least
I can do is pay my fair share.
Thanks to the entire Engineering team for their efforts. It means a lot.
Sean Kutzko KX9X
> On Dec 10, 2018, at 10:05 AM, Don KB2YSI <kb2ysi@?????.???> wrote:
>
> Thanks to Drew and Jerry for the additional information, even though the
> situation is not what anyone wanted hear.
>
> I will echo John's statement. For those who have worked so hard on this
> bird, along with those before it and those to come, THANK YOU! Without
> people with the knowledge and skills to get a satellite into orbit, we
> would not have anything to enjoy.
>
>
>> On Mon, Dec 10, 2018 at 2:03 AM Jerry Buxton <n0jy@?????.???> wrote:
>>
>>> On 12/9/2018 18:17, Fred Castello wrote:
>>> I am just curious why we are not discussing the apparent failure of the
>> receiver of AO-95. Do we know anything more about the issue?
>>> Thanks all,
>>> Fred ? KF4FC
>>>
>> Hi Fred,
>>
>> I'm not sure if you were referring to We the amsat-bb list members? I
>> have to say that I figured there would be much more chatter here than I
>> have seen so far, anyway.
>>
>> If by We you mean We the AMSAT Engineering team, of course we have been
>> discussing the problem, possible causes, and working on leads ever since
>> the anomaly became known. Certainly many of us are unhappy at not
>> succeeding in making everybody else happy, but that is not the reason
>> for my silence in terms of sharing with the public. Right now, with no
>> readily apparent reason or reasons for the behavior, there is nothing
>> else to report.
>>
>> The situation has gone from a commissioning to being challenge, which is
>> actually fun and we're on it. We are looking at data from a number of
>> sources, as well as our past experiences with the other Fox-1 satellites
>> during their journey from the BOM to orbit. Ideas such as the one Drew
>> mentioned about employing a mega-QRO station to see if it can be heard
>> by the bird have been on the table for several days but I don't plan to
>> report or discuss every thought we have in working this unless and until
>> it is something of merit or actionable. As you probably know, our
>> resources are limited and it's all volunteered time. Most if not all of
>> our remaining Fox-1 engineers are also involved in the GOLF-TEE project
>> so I have asked them to give that first priority with their available
>> volunteer time in order to keep the schedule. AO-95 is in orbit now and
>> we can vary the amount of attention on her as resources allow in order
>> to achieve both goals. If the results of our investigation point to a
>> possibility of recovery be it partial, full, or some workaround method,
>> we would all like to see her working as much as the rest of you and that
>> is a driver for this investigation. But perhaps the most important
>> driver is that there are lessons to be learned for the betterment of
>> future missions. I expect us to continue to look for the cause or
>> causes until we have results or reach a dead end because of the
>> inability to take the lid off and look inside AO-95.
>>
>> The main point of the ANS is to let everyone know that commissioning
>> won't be happening, certainly not in the period that everyone has grown
>> accustomed to if at all, so that members and users can get on with
>> enjoying their activities on all of the other satellites. Many had been
>> waiting in anticipation and wondering why talk of AO-95 commissioning
>> seemed so quiet, so once we were sure that it didn't appear to be an
>> intermittent thing we shared the news. And as I said in the ANS, I will
>> certainly be keeping everyone posted when we have something new to
>> report so in the meantime please carry on and enjoy the birds!
>>
>> Jerry Buxton, N?JY
>>
>>
>> _______________________________________________
>> Sent via AMSAT-BB@?????.???. 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: http://www.amsat.org/mailman/listinfo/amsat-bb
>>
>
>
> --
> 73,
> Don KB2YSI
> https://www.hamqth.com/kb2ysi
> _______________________________________________
> Sent via AMSAT-BB@?????.???. 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: http://www.amsat.org/mailman/listinfo/amsat-bb
------------------------------
Message: 10
Date: Mon, 10 Dec 2018 11:35:22 -0500
From: Paul Stoetzer <n8hm@????.???>
To: cbouck01@?????.??.???
Cc: AMSAT BB <amsat-bb@?????.???>
Subject: Re: [amsat-bb] AO-95
Message-ID:
<CABzOSOpgdQweRDO65pqd4f5S3hW2QPq259QVx1GJzOJ6MNBRyw@????.?????.???>
Content-Type: text/plain; charset="UTF-8"
Please see https://www.amsat.org/fox-1cliff-ao-95-commissioning-status/
73,
Paul, N8HM
On Mon, Dec 10, 2018 at 11:25 AM Chris Bouck <cbouck01@?????.??.???> wrote:
>
> Where are you getting the information on this spacecraft?
>
> Chris KB4CMF
>
>
> ---
> This email has been checked for viruses by Avast antivirus software.
> https://www.avast.com/antivirus
>
> _______________________________________________
> Sent via AMSAT-BB@?????.???. 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: http://www.amsat.org/mailman/listinfo/amsat-bb
------------------------------
Message: 11
Date: Mon, 10 Dec 2018 10:36:16 -0600
From: Zach Metzinger <zmetzing@?????.???>
To: amsat-bb@?????.???
Subject: Re: [amsat-bb] AO-95
Message-ID: <fb6293ff-87f8-c740-a22e-8387de36bca2@?????.???>
Content-Type: text/plain; charset=utf-8; format=flowed
On 12/10/18 10:25 AM, Chris Bouck wrote:
> Where are you getting the information on this spacecraft?
Are you receiving the "ANS-xxx AMSAT News Service Weekly Bulletins",
sent to this list? That's the best source of information on AO-95, and
future missions.
On to Fox-1E and beyond!
--- Zach
N0ZGO
------------------------------
Subject: Digest Footer
_______________________________________________
Sent via amsat-bb@?????.???.
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 member? Join now to support the amateur satellite program!
http://www.amsat.org/mailman/listinfo/amsat-bb
------------------------------
End of AMSAT-BB Digest, Vol 13, Issue 412
*****************************************
Read previous mail | Read next mail
| |
