Apollo 11 datorkļūdas nolaišanās laikā

Lidojošie, rāpojošie un statiskie mehānismi un tajos izmantotās tehnoloģijas, kas paredzētas tuvējā un tālā visuma izpētei

Apollo 11 datorkļūdas nolaišanās laikā

Postby x-f » 28 Jul 2015, 22:09

No, a "checklist error" did not almost derail the first moon landing
The cause of Apollo 11’s landing alarms is actually a lot more complicated.
Last week was the forty-sixth anniversary of the Apollo 11 moon landing—the first of the six crewed landings on our nearest celestial neighbor.
(..)
And as it turned out, the first landing on the moon almost did encounter disaster. Shortly after Eagle entered one of the most complicated stages of the descent, the guidance computer began throwing off alarms—very serious alarms, of a type no one in mission control or on the spacecraft was immediately familiar with. Back at MOCR2 in Houston, the burden to determine whether or not the alarms were benign—and therefore the decision to determine whether to abort the landing, blow the Eagle in half, and make an emergency burn to try to make it back up to Columbia—fell on the shoulders of two people: guidance controller Steve Bales and backroom guidance specialist Jack Garmin.
http://arstechnica.com/science/2015/07/ ... n-landing/

Interesants raksts par Apollo Mēness nolaišanās moduļa bortdatora darbību, tā spējām un dažām nejaušām sakritībām.
User avatar
x-f
Baltais punduris
Baltais punduris
 
Posts: 237
Joined: 20 Sep 2008, 11:52
Location: Sigulda

Return to Tehnoloģijas

Who is online

Users browsing this forum: No registered users and 1 guest

cron