4 ms·
“this may have been a test configuration mistake” The article makes it seem like this is a good thing, I.e., there’s nothing inherently wrong with the design.
by bumby 7y ago
“this may have been a test configuration mistake”
The article makes it seem like this is a good thing, I.e., there’s nothing inherently wrong with the design.
If true, it means it may be a procedural escape which can be every bit as dangerous. Some of the fallout from the CST-100 Boeing Starliner issues seem to point to process escapes as well. Makes me wonder if in the rush to get “boots on the moon” by 2024 we may be letting schedule get the best of us...
- greglindahl 7y agoYou're comparing a vehicle at the start of development with a vehicle that was supposedly undergoing final testing.
- gamblor956 7y agoYou're comparing a software error (Boeing) to a hardware error (SpaceX). Boeing's hardware is effectively finalized, but the control software is still undergoing testing with the finalized (i.e., "frozen") hardware specs.
- gpm 7y agoBoeings most recent mission was supposed to be a demonstration that they were ready to fly crew to the station. Both hardware and software was supposed to be effectively finalized. This is compared to Starship where no one even really knows what the final hardware or software will look like yet and they are trying out manufacturing techniques in a field. The tests being performed are experiments, to see what does and doesn't work. Comparing the two failures is completely ridiculous. Not only was Boeing software supposed to be effectively finalized, but Boeing hardware also appears to have failed on that test. The thrusters experienced issues, and the antenna that were contractually required to provide end to end connectivity failed to do so. Moreover on the second most recent demonstration (pad abort) Boeing suffered a parachute failure.
- bumby 7y agoPretty good assessment. I couldn’t tell from your wording but I think the understanding is the thruster and comm issues were software related while the parachute issue was not?
- gpm 7y agoSorry, I guess I should have been more clear. The thruster and comms issues were also examples of hardware related issues. I can't say for certain that the comms issue couldn't be fixed in software, but it seems unlikely. The thruster issue was related to overuse and is arguably mitigated by "not doing that (via software changes and training for human pilots)", but it really shouldn't have been an issue in the first place. The software issues were the more serious issues that grabbed more headlines. The capsule incorrectly grabbing a time value from the rocket. The control logic for whatever reason didn't understand something was wrong, but instead "proceeded as normal" as if it was further ahead in the mission. Finally there was some other error that was caught before it happened but was something related to the thruster control logic and could have caused the loss of the capsule during re-entry.
- bumby 7y agoAh, ok thank you for clarifying. I thought you were originally talking about the thruster mapping issue that was another example of software issues
- gpm 7y agoNot sure why this is being downvoted. I appreciate both the thanks, and that you identified the source of the confusion. I also appreciate that you made it clear that you know what you're talking about and that I didn't really need to write such a long answer for you.
- greglindahl 7y ago"the understanding" ought to be that the incident review isn't done.
- 101404 7y agoThis is a very early prototype. Plan is to build at least 20 of them to try and test ideas and configurations. Some days ago I read that they are currently trying to reduce material thickness to reduce weight. Maybe that contributed to the RUD.
- gpm 7y agoThis is an early manufacturing path-finding test article and test, not a test article and test designed to validate that the system is safe. The procedures, design, manufacturing techniques, and everything else are still being developed and certainly haven't been validated yet. Failures are expected. It is a good thing that there is nothing inherently wrong with the design, just because that would mean more re-design work for SpaceX. A procedural issue (possibly this failure), a manufacturing defect (MK1 failure), a failure due to a temporary hack (SN1 failure), etc are all understandable errors and easily fixable at this point in time. Starship isn't really being driven by the "boots on the moon by 2024" push by the government. Starship is a private venture being developed on their own schedule (and with their own money).
- deleted 7y ago[deleted]
- bumby 7y ago> Starship isn't really being driven by the "boots on the moon by 2024" push by the government. You’re right, bad choice of phrasing on my part to boil it down to a turn-of-phrase. What I’m really poking at is how schedule pressure affects decision making. SpaceX is well known to have very ambitious timelines. I am wondering how much that pressure affects process checks like configuration control
- londons_explore 7y agoI worry that the people who ran this test either didn't know what they were doing, or were too tired or didn't care. The top tank was covered in ice, indicating it was nearly full, while the bottom tank had no ice. That leaves three possibilities: * The intention is the bottom tank was pressurized with gas:. There is no way that much gas at ~4 bar is safe. It would destroy all nearby buildings if it failed. That's a serious safety failing. * The intention is the bottom tank was filled with LN2. Whoever was running the test didn't notice the tank didn't turn white, and didn't have any kind of level gauge or flow meter? * The intention is the tank was unpressurized. The design could never withstand the top tank filled and the bottom tank unpressurized and empty. Whoever designed and ran the test didn't understand the basics of the design. All of those 3 possible explanations point to more than a simple oversight, and IMO suggest the team working at 3am might possibly not really understand what they were doing.
- Rebelgecko 7y agoSomewhat notable is that a test article from a recent Crew Dragon parachute test was also just destroyed due to problems with how they set up their test https://spacenews.com/spacex-reports-problem-in-crew-dragon-parachute-test/ https://spacenews.com/spacex-reports-problem-in-crew-dragon-...