CST-100

Автор Космос-3794, 12.10.2011 11:16:02

« назад - далее »

0 Пользователи и 2 гостей просматривают эту тему.

snek

Ветераны индустрии продолжают удивлять. Если это чудо полетит в этом году, то лоббисты боинга докажут, что не зря свой хлеб едят. 

tnt22

https://blogs.nasa.gov/commercialcrew/2020/02/07/nasa-shares-initial-findings-from-boeing-starliner-orbital-flight-test-investigation/
ЦитироватьNASA Shares Initial Findings fr om Boeing Starliner Orbital Flight Test Investigation

Marie Lewis
Posted Feb 7, 2020 at 9:33 am


Boeing, NASA, and U.S. Army personnel work around the Boeing CST-100 Starliner spacecraft shortly after it landed in White Sands, New Mexico, Sunday, Dec. 22, 2019. Photo Credit: (NASA/Bill Ingalls)

Following the anomaly that occurred during the December Boeing Starliner Orbital Fight Test (OFT), NASA and Boeing formed a joint investigation team tasked with examining the primary issues, which occurred during that test. Those issues included three specific concerns revealed during flight:
[LIST=1]
[/li][li]An error with the Mission Elapsed Timer (MET), which incorrectly polled time from the Atlas V booster nearly 11 hours prior to launch.
[/li][li]A software issue within the Service Module (SM) Disposal Sequence, which incorrectly translated the SM disposal sequence into the SM Integrated Propulsion Controller (IPC).
[/li][li]An Intermittent Space-to-Ground (S/G) forward link issue, which impeded the Flight Control team's ability to command and control the vehicle.
[/li][/LIST]
The joint investigation team convened in early January and has now identified the direct causes and preliminary corrective actions for the first two anomalies. The intermittent communications issues still are under investigation. NASA reviewed these results on Friday, Jan. 31 along with multiple suggested corrective actions recommended by the team. While NASA was satisfied that the team had properly identified the technical root cause of the two anomalies, they requested the team to perform a more in-depth analysis as to why the anomalies occurred, including an analysis of whether the issues were indicative of weak internal software processes or failure in applying those processes. The team is in the process of performing this additional analysis, as well as continuing the investigation of the intermittent communications issues. NASA briefed the Aerospace Safety Advisory Panel on the status of the investigation this week.

Regarding the first two anomalies, the team found the two critical software defects were not detected ahead of flight despite multiple safeguards.  Ground intervention prevented loss of vehicle in both cases. Breakdowns in the design and code phase inserted the original defects. Additionally, breakdowns in the test and verification phase failed to identify the defects preflight despite their detectability. While both errors could have led to risk of spacecraft loss, the actions of the NASA-Boeing team were able to correct the issues and return the Starliner spacecraft safely to Earth.

There was no simple cause of the two software defects making it into flight. Software defects, particularly in complex spacecraft code, are not unexpected. However, there were numerous instances wh ere the Boeing software quality processes either should have or could have uncovered the defects. Due to these breakdowns found in design, code and test of the software, they will require systemic corrective actions. The team has already identified a robust set of 11 top-priority corrective actions. More will be identified after the team completes its additional work.

The joint team made excellent progress for this stage of the investigation. However, it's still too early for us to definitively share the root causes and full set of corrective actions needed for the Starliner system. We do expect to have those results at the end of February, as was our initial plan. We want to make sure we have a comprehensive understanding of what happened so that we can fully explain the root causes and better assess future work that will be needed. Most critically, we want to assure that these necessary steps are completely understood prior to determining the plan for future flights. Separate from the anomaly investigation, NASA also is still reviewing the data collected during the flight test to help determine that future plan. NASA expects a decision on this review to be complete in the next several weeks.

NASA and Boeing are committed to openly sharing the information related to the mission with the public. Thus, NASA will be holding a media teleconference at 3:30 p.m. EST Friday, Feb. 7.

In addition to these reviews, NASA is planning to perform an Organizational Safety Assessment of Boeing's work related to the Commercial Crew Program. The comprehensive safety review will include individual employee interviews with a sampling from a cross section of personnel, including senior managers, mid-level management and supervision, and engineers and technicians at multiple sites. The review would be added to the company's Commercial Crew Transportation Capability contract. NASA previously completed a more limited review of the company. The goal of the Organizational Safety Assessment will be to examine the workplace culture with the commercial crew provider ahead of a mission with astronauts.

Boeing's Orbital Flight test launched on Friday, Dec. 20, on United Launch Alliance Atlas V rocket from Space Launch Complex 41 at Cape Canaveral Air Force Station in Florida. The mission successfully landed two days later on Sunday, Dec. 22, completing an abbreviated test that performed several mission objectives before returning to Earth as the first orbital land touchdown of a human-rated capsule in U.S. history.

tnt22

https://www.nasa.gov/press-release/nasa-boeing-to-provide-update-on-starliner-orbital-flight-test-reviews
ЦитироватьFeb. 7, 2020
MEDIA ADVISORY M20-023

NASA, Boeing to Provide Update on Starliner Orbital Flight Test Reviews
NASA and Boeing will host a media teleconference at 3:30 p.m. EST Friday, Feb. 7, to discuss the status of the joint independent review team investigation into the primary issues detected during the company's uncrewed Orbital Flight Test in December as part of NASA's Commercial Crew Program.

Participants in the briefing will be:



    [/li]
  • NASA Administrator Jim Bridenstine
  • Jim Chilton, senior vice president, Boeing Space and Launch
  • Douglas Loverro, associate administrator, NASA's Human Exploration and Operations Mission Directorate
  • Kathy Lueders, program manager, NASA's Commercial Crew Program
  • John Mulholland, vice president and program manager, Boeing's CST-100 Starliner Program
Audio of the teleconference will stream live online at:

-end-

Last Updated: Feb. 7, 2020
Editor: Karen Northon

tnt22

https://starlinerupdates.com/statement-on-independent-review-team-recommendations-for-the-starliner-orbital-flight-test-anomalies/
ЦитироватьStatement on Independent Review Team Recommendations for the Starliner Orbital Flight Test Anomalies
February 6, 2020

We accept and appreciate the recommendations of the jointly led NASA-Boeing Independent Review Team (IRT) as well as suggestions from the Aerospace Safety Advisory Panel following Starliner's Orbital Flight Test (OFT). Their insights are invaluable to the Commercial Crew Program and we will work with NASA to comprehensively apply their recommendations.
    [/li]
  • Regarding the Mission Elapsed Timer anomaly, the IRT believes they found root cause and provided a number of recommendations and corrective actions.
  • The IRT also investigated a valve mapping software issue, which was diagnosed and fixed in flight. That error in the software would have resulted in an incorrect thruster separation and disposal burn. What would have resulted from that is unclear.
  • The IRT is also making significant progress on understanding the command dropouts encountered during the mission and is further investigating methods to make the Starliner communications system more robust on future missions.
We are already working on many of the recommended fixes including re-verifying flight software code.

Our next task is to build a plan that incorporates IRT recommendations, NASA's Organizational Safety Assessment (OSA) and any other oversight NASA chooses after considering IRT findings. Once NASA approves that plan, we will be able to better estimate timelines for the completion of all tasks. It remains too soon to speculate about next flight dates.

NASA has issued the following advisory:

https://www.nasa.gov/press-release/nasa-boeing-to-provide-update-on-starliner-orbital-flight-test-reviews

Чебурашка

Аудиоконференция по Старлайнеру начинается https://www.nasa.gov/nasalive

Чебурашка

#1165
ЦитироватьJohn Mulholland of Boeing says Starliner's flight software has about 1 million lines of code. Now they will have to go back through and verify all of that.

ЦитироватьBoeing adds: Starliner has approximately 1 million lines of code. We exercised ~66% of the scripts correctly during the mission but we're going to go back and re-verify.

И займёт это лет пять

Not

ЦитироватьЧебурашка написал:

И займёт это лет пять
А почему не десять? Зуб даешь? :D

Чебурашка

Сигналы сотовой связи мешали передачи команд на корабль?

ЦитироватьMulholland: the high noise floor for communications was over specific "geographic footprints" and appears to be close to frequencies associated with cell towers.

opinion

ЦитироватьNot написал:
 
ЦитироватьЧебурашка написал:

И займёт это лет пять
А почему не десять? Зуб даешь?
Not, вспомни свои рассказы, как у вас там относятся к СпэйсИкс и Боингу. Вспомнил? А теперь забудь! Теперь отношение изменится. Бранденстайн: "NASA oversight was insuffisient".
There are four lights

Not

Цитироватьopinion написал: Бранденстайн: "NASA oversight was insuffisient".
Да ладно, не плакай, филолух! И всегда вспоминай, что там Алекс II пишет про гуманитариев, чтобы временами возвращаться на грешную землю :D

Not

Для первого полета все было вполне допустимо. По сравнению же с первым полетом Дракона спейсексов - близко к совершенству :D

opinion

ЦитироватьNot написал:
Для первого полета все было вполне допустимо. По сравнению же с первым полетом Дракона спейсексов - близко к совершенству
К тому миллиону строк кода вам теперь придется дописать два-три миллиона строк тестов и тогда, может быть, будет допустимо, а не вполне допустимо.
There are four lights

Чебурашка

Бгг...
Lost of mission в первом полете допустимо?
Сколько там по требованиям NASA в вероятность LOM должна быть - 1 к 400 вроде

У Dragon 2 в первом полете кстати Full success ;)
Объективная реальность.

Ну-и-ну

Миллион строк - программа большой сложности, но не гигантская. 30 кодеров должны держать столько в головах.

opinion

ЦитироватьNot написал:
 
ЦитироватьДа ладно, не плакай, филолух!
Тебе всё филологи везде мерещатся, а сычберду начала мерещится саранча. Может это вирус?
There are four lights

opinion

ЦитироватьЧебурашка написал:
Бгг...
Lost of mission в первом полете допустимо?
Сколько там по требованиям NASA в вероятность LOM должна быть - 1 к 400 вроде

У НАСА есть требования к LOC. Это потеря экипажа, а не миссии. И, кажется, условие более слабое, 1 к 270 или что-то вроде этого.
There are four lights

tnt22

Цитировать Chris G - NSF@ChrisG_NSF 11:42 PM - Feb 7, 2020

Kathy Lueders: Mission Event Timer issue was traced to a software requirement issues.  2 parameters were needed; only 1 was actually coded in the flight software.
@NASA @BoeingSpace #Starliner #OFT


11:42 PM - Feb 7, 2020

Kathy Lueders: "While getting ready for reentry, the way the Service Module software was coded was incorrect."
@NASA @BoeingSpace #Starliner #OFT

tnt22

Цитировать Chris G - NSF@ChrisG_NSF 11:52 PM - Feb 7, 2020

John (Boeing): Second issue was an incorrect valve mapping coding that would not have allowed the Service Module to fire its thruster to get away from Starliner after separation.
@NASA @BoeingSpace #Starliner #OFT


11:53 PM - Feb 7, 2020

John (Boeing): The antenna issue "would have presented regardless of other issues."  No real info to present at this point.
@NASA @BoeingSpace #Starliner #OFT

tnt22

ЦитироватьBoeing, NASA update the media on Starliner anomalies - Teleconference audio (2/7/2020)

NASASpaceflight

7 февр. 2020 г.
https://www.youtube.com/watch?v=xv5UX2j2UBshttps://www.youtube.com/embed/xv5UX2j2UBs (56:31)

Serge V Iz

https://iz.ru/export/google/amp/973791

ЦитироватьСМИ узнали о фундаментальных проблемах в ПО корабля Starliner от Boeing
...
«Мы не знаем, сколько ошибок сейчас в программном обеспечении. Возможно, две, а возможно, и много сотен. Дело в том, что эта сфера промышленности очень плохо справляется с [разработкой] ПО»

А чего хотели? Не надо было занимать позицию бюрократа и считать штуки подписей под документами, вынося мозг актуальным работникам, а надо было активно участвовать а идеологии и технологии разработки и испытаний - тогда бы и "знали" ))