-
#840
by
AnalogMan
on 01 Oct, 2008 19:57
-
For those interested the full transcript of the HST Press Briefing from 29 Sep 08 has been published by NASA
-
#841
by
Chris Bergin
on 02 Oct, 2008 11:29
-
Per L2, HST payload removal from Atlantis to begin at the weekend.
-
#842
by
Chris Bergin
on 02 Oct, 2008 17:24
-
-
#843
by
Chris Bergin
on 02 Oct, 2008 19:34
-
Updated the article with the rollback date of October 20 (which can move left or right - most likely left - depending on what works best for the milestones etc.)
-
#844
by
maxx
on 02 Oct, 2008 19:41
-
Sorry if this was asked before.
If got my dates right, around 28 days of processing have now been done since the arrival of Atlantis at the pad. How many days of processing will have to be redone when she returns to the pad?
Thanks
-
#845
by
psloss
on 02 Oct, 2008 19:45
-
If got my dates right, around 28 days of processing have now been done since the arrival of Atlantis at the pad. How many days of processing will have to be redone when she returns to the pad?
Likely most of it, with perhaps the exception of the TCDT; however, I wouldn't use calendar days the vehicle has physically been at the pad to measure processing time. For one thing, the teams that work on the vehicle at the pad don't work 24/7.
-
#846
by
rdale
on 02 Oct, 2008 20:03
-
Last 10 minutes of today's ISS hour (replays on NASA TV this evening) was coverage of Grunsfeld training in the NBL for EVA 5...
-
#847
by
maxx
on 02 Oct, 2008 20:08
-
If got my dates right, around 28 days of processing have now been done since the arrival of Atlantis at the pad. How many days of processing will have to be redone when she returns to the pad?
Likely most of it; however, I wouldn't use calendar days the vehicle has physically been at the pad to measure processing time. For one thing, they don't work 24/7.
Thanks, I know that "days" aren't the most suitable unit I could have used but couldn't figure out a better way to formulate my question.
A ballpark number, a fraction or a percentage would do it. But for now I'm satisfied with your "most of it" :-)
-
#848
by
psloss
on 02 Oct, 2008 20:28
-
A ballpark number, a fraction or a percentage would do it. But for now I'm satisfied with your "most of it" :-)
Whatever the figures are, it's probably more of an issue of how the work "items" fit into the big picture than a single time period. And that's dependent on lots of factors. I'm sure this site will have all the news on the schedules for the 125 and 4xx vehicles when they get back into launch processing in earnest. (And all the other shuttle and HST program news going on in between.)
-
#849
by
maxx
on 02 Oct, 2008 21:33
-
A ballpark number, a fraction or a percentage would do it. But for now I'm satisfied with your "most of it" :-)
Whatever the figures are, it's probably more of an issue of how the work "items" fit into the big picture than a single time period. And that's dependent on lots of factors. I'm sure this site will have all the news on the schedules for the 125 and 4xx vehicles when they get back into launch processing in earnest. (And all the other shuttle and HST program news going on in between.)
Agreed but the SSP or whatever office is in charge need at least some sort of ballpark number to estimate when to bring the stack out to support a give launch date or give a launch date once the prerequisites are dates known (in this case the arrival of the replacement unit for HST).
Maybe this is worth a new thread on how do they make the processing schedule...
Many thanks for your answers
-
#850
by
psloss
on 02 Oct, 2008 21:55
-
Agreed but the SSP or whatever office is in charge need at least some sort of ballpark number to estimate when to bring the stack out to support a give launch date or give a launch date once the prerequisites are dates known (in this case the arrival of the replacement unit for HST).
Sure, and they probably have schedules and options laid out for discussions and decisions down the road. For us on the outside, though, we don't have full visibility into the program, which would be largely disruptive. Thanks to the information we get here, we have much better visibility, but it's still minimal, relatively speaking.
(And yes, I agree this should move to probably the Q&A thread.)
-
#851
by
Chris Bergin
on 04 Oct, 2008 07:02
-
-
#852
by
ChrisC
on 04 Oct, 2008 20:39
-
Thanks for those details. I'm absolutely on the edge of my chair awaiting Side A / B results. Procedure approval, VEST test results, the actual cutover attempt, etc.
In the article, you have a quote apparently from presentation materials:
“On Monday, HST will brief results and plans to Goddard Center Director. Tuesday, HST will take it to HQ. Wednesday, plan is to have them press on with commanding over to side B. When complete VEST work to take the side B routine over, will start flight qualification work on the new SICBH boxes.”
It's not clear to me in there when the VEST runthrough happens. And as I recall from the initial press briefing last week, that process (on VEST and on Hubble itself) would take something like 8 hours (basically a whole day). So it seems like everything is packed in too tight there. I'm sure it's not, just trying to divine more details out of it.
Has anyone found a source for more detailed Hubble status info, similar to the ISS daily reports or a forum like this one?
-
#853
by
rdale
on 04 Oct, 2008 20:49
-
Has anyone found a source for more detailed Hubble status info, similar to the ISS daily reports or a forum like this one?
During the presser they mentioned going to their website and getting the Hubble Daily Reports, but they are not available publicly there. If you watch closely they are reposted elsewhere, but not on a NASA or Hubble related site.
-
#854
by
STS Tony
on 04 Oct, 2008 20:54
-
Has anyone found a source for more detailed Hubble status info, similar to the ISS daily reports or a forum like this one?
Seen some on L2 when they are relevant. They aren't very long. There was more detail in the end of week Standup, which are a L2 regular.
-
#855
by
rdale
on 04 Oct, 2008 21:03
-
11511 - NSSC-1 is safed, PIT toggle test failed
Upon acqusition of signal at 272/00:52:19 vehicle telemetry was in HF format with NSSC-1 in fixed format. Two 486 ESB messages "D24" (SICDH_TOGGLE_TEST_FAIL) and "D01" (SAFE_HLD_MACROS_ACTIVE_INFO) were received at 00:10:41 according to ESB dump. SCDHSAFA (Safing Macro Active), SDSTOGF (Toggle Failure Counter), SSiCDHT (SIC&DH Toggle OK Flag), and SSIPTBE (PIT Togggle Test) flags were set.
Science Observations Affected in Proposals: WFPC Proposal ID #11289, #11130, #11796, #11113, #11107, #11218, #11302; #11793, #11103, #11797 and ACS Proposal ID #11196,
11515 - GSAcq(1,2,2) failed to RGA Hold (Gyro Control)
Upon acquisition of signal at 272/15:19:30,the GSAcq(1,2,2)scheduled at 272/15:16:41 - 15:24:46 had begun acquisition walkdown, then at 272/15:20:19 acquisition walkdown failed to RGA Hold due to (QF1STOPF) stop indication flag set on FGS-1.
The payload had safed. Affected data are included in the HSTAR 11511.
COMPLETED OPS REQUEST:
18294-3 - Perform NSSC-1 Hardware memory dump @ 272/0554z
18295-0 - Turn off CDH regulator @ 272/0727z
18296-0 - Reset CU command counter @ 272/1734z
18297-0 - Switch to CU RIUB and perform H/W dump @ 272/1815z
18298-0 - power cycle CU/SDF A @ 272/1851z
18300-0 - NSSC-1 Fill Data Test @ 272/2233z
Flash Report:
As a result of NCS cooler and the Sis being safed, the HST load decreased from ~75A to ~53A, resulting in a battery heat up with the increased charge current. Per COP 4.27A the +BB SPA Trim relay (Battery 3) was off-lined as Battery 3's temperature was demonstrating an increasing warming trend and was approaching 3.5 DegC, the yellow ground limit. Commanding to off-line the SPA was performed at DOY 275, 01:04 GMT via Ops Request 18303.
11519 - GSAcq(1,2,1) failed to RGA Hold (Gyro Control)
GSAcq(1,2,1) scheduled at 275/16:37:58 - 16:46:03 failed to RGA Hold due to (QF1STOPF) stop flag indication on FGS-1.
11520 - OM1EBOXT (STIS MAMA1 Electronics Box Temp) Limit Violation
At 275/20:26:03, STIS MAMA1 Electronics Box Temperature (OM1EBOXT) began flagging out of limit intermittently one count below its red low limit of 0.0 deg C at -0.15 deg C.
11521 - GSAcq(1,2,1) failed due to SSLEX @ 276/02:14:40z
During LOS the GSacq(1,2,1) scheduled at 276/02:14:04 failed due to scan step limit exceeded on FGS 1.
11522 - GSacq(1,2,1) failed to RGA control.
During LOS GSacq(1,2,1) scheduled at 276/07:01:44 failed. At AOS stop flags QF1STOPF and QSTOP were set for FGS 1.
-
#856
by
STS Tony
on 04 Oct, 2008 21:13
-
About the issues, which he is asking about, not what Galaxy it's taking photos of. And about the issues, the Standup is better.
-
#857
by
Chris Bergin
on 07 Oct, 2008 23:08
-
HST payload now out of Atlantis and in the PCR.
-
#858
by
nathan.moeller
on 08 Oct, 2008 14:03
-
Chris - where are they taking the payload once it's removed from the PCR?
-
#859
by
psloss
on 08 Oct, 2008 14:06
-
Chris - where are they taking the payload once it's removed from the PCR?
Back to the Payload Hazardous Servicing Facility (PHSF), where it was integrated and placed in the carrier.