Needless to say, I'm extremely excited to even see a static fire of this monster. Re-using boosters for your early development is pretty nice and efficient too I imagine.
Needless to say, I'm extremely excited to even see a static fire of this monster. Re-using boosters for your early development is pretty nice and efficient too I imagine.
It sounds good on paper but it's not easy in practice, see: the Russian N-1 moon rocket, which basically just took the R7 rocket and scaled it up with more engines. Turns out too many engines means too many points of failure, and the rocket never worked.
https://en.wikipedia.org/wiki/N1_(rocket)
Much like in computing, you can't substitute one oxen with a thousand chickens and expect the same outcome when you plow your field.
SpaceX has already shown that with modern control systems, you can bundle a bunch of chickens together to plow a field. Having 9 engines has already helped them complete missions where one failed. The Falcon Heavy problem isn't scaling from 9 to 27 per se, it's building a new structure to handle all the new stresses that will occur, from the launch sequence to aerodynamic.
It uses the same engines and very similar hardware, but there are so many new/not-flight-proven things on this rocket that it will be exciting, one way or another!
Don't make the mistake of thinking that a large system is implicitly using weaker processors. They're as powerful as we can make them, some tasks just need a lot of them.
Which is too bad, because it would be really awesome if they had managed to make it work.
So making the Falcon Heavy work as simply and well as possible is the important part. Getting another 10% by making crossfeed work, at the cost of making it more complex, harder to build and re-use, simply wouldn't be worth it.
Falcon Heavy can fly for a couple of years now and it can handle current demands.
They will open up to next level capability with a next level vehicle.
We just don't have the numbers, I would love to see the internal accounting of these projects.
Heck, Falcon Heavy has turned out to be a much larger engineering problem than originally thought even without asparagus staging (cross-feed) due to issues with reinforcing the center core to handle the loads from the side cores.
Based on Musk's latest presentation regarding BFR, it seems that Falcon Heavy will be a somewhat short-lived launch platform.
Then again, with SpaceX, plans change early and often...
SpaceX plans to do in-orbit refueling for its BFR, though. I may be oversimplifying, but it seems to me this is a fairly similar feat than cross-feeding. Couldn't the experience gained in this help for that?
"Shortly after liftoff the center core engines are throttled down. After the side cores separate, the center core engines throttle back up to full thrust."
This is easier then one would think because the rocket is fuelled and the engines already have a hard time living the rocket at all.
They use the same launch pad during launch and the clamps only release when the computer has made sure all engines have correctly stared and are running correctly.
Check out the video from RocketLab when they had a launch abort to see a example of this.