The other logo has a P-POD on it.
Now have cross confirmation this static fire didn't go to plan.Aborted due to high chamber pressure on one engine (around 1.5 seconds). Trying to recycling for another attempt today. 3pm is the range limit.
Quote from: Chris Bergin on 12/03/2010 05:57 pmNow have cross confirmation this static fire didn't go to plan.Aborted due to high chamber pressure on one engine (around 1.5 seconds). Trying to recycling for another attempt today. 3pm is the range limit.Sounds like the static fire has earned it's keep - although this would presumably have been detected before release if this was a real launch.Do we know how many times an array of nine Merlins has been fired up before? I presume most times would have been on the test stand?If this turned out to be a major issue for engine #6, could it be replaced?cheers, Martin
Would this have been a "go" condition on flight day?
Would this have been a "go" condition on flight day? If this had come through, would it have just shut that engine down and gone for it on the other 8? They've talked about engine-out as being a big safety thing in Falcon 9, but do they have the software set up to trust in that?
Someone else may have better info, but it looks like the aborts they've had are due to tight software limits on chamber pressure being exceeded by engine start transients, and not a "real" hardware problem, at least not that I've heard. It's a learning curve and they're on the steep part of it.
Quote from: Kabloona on 12/04/2010 12:33 amSomeone else may have better info, but it looks like the aborts they've had are due to tight software limits on chamber pressure being exceeded by engine start transients, and not a "real" hardware problem, at least not that I've heard. It's a learning curve and they're on the steep part of it.Data is good. I learned a lot about how they do it on F9 flight 1. Apparently they do indeed set the margins extremely low, basically completely insane expectations for the rocket. I actually like that they do it this way. I like it a lot. When you have a several hour turn around time restart capability, use it. At least until you have a whole lot of data to go by and can decide just how it's going to behave.