For a Falcon9/Falcon Heavy Payload Assist Module, the idea of using superdraco for the application might have some merit for deep space missions like interplanetary probes, or insertions to GEO. I think though that SpaceX have decided to maximize the Falcon architecture recoverable/re-usable fraction, so a development program like that might be viewed by them as counter-intuitive. For an imaginary F1e, I think that the superdracos' low Isp would help less than a better Kestrel2.
No, it has little merit for a deep space mission. Once you are out of the deep gravity well, Isp is king. Thrust does not matter. So a Draco (or cluster of them) would actually be superior to SuperDraco for the purpose of a final kick stage.
Well now, this is my kind of thread.Quote from: Stan-1967 on 01/07/2016 04:12 pmWell I took the leap last night to give my best effort at making my own new "Phoenix" F1 class vehicle and testing it out on a simulator linked to by this site in the archives at Silverbird Astronautics.http://www.silverbirdastronautics.com/LVperform.html[...]Here is what the calculations returned:Mission Performance:Launch Vehicle: User-Defined Launch VehicleLaunch Site: Cape Canaveral / KSCDestination Orbit: 185 x 185 km, 45 degEstimated Payload: 1687 kg95% Confidence Interval: 1294 - 2172 kg[...]So... assuming I was a billionaire, I had a couple of Mercury style capsules as payloads (m = 1400kg), and a death defying love of Koalas, I could have lunch in Cape Canaveral, get on a Phoenix at 3pm, have breakfast in Taronga zoo, Sydney (at 4pm/8am), get on another Phoenix at 5pm/9am and be back at KSC in time for dinner?
Well I took the leap last night to give my best effort at making my own new "Phoenix" F1 class vehicle and testing it out on a simulator linked to by this site in the archives at Silverbird Astronautics.http://www.silverbirdastronautics.com/LVperform.html[...]Here is what the calculations returned:Mission Performance:Launch Vehicle: User-Defined Launch VehicleLaunch Site: Cape Canaveral / KSCDestination Orbit: 185 x 185 km, 45 degEstimated Payload: 1687 kg95% Confidence Interval: 1294 - 2172 kg[...]
Quote from: Lars-J on 01/08/2016 05:03 pmNo, it has little merit for a deep space mission. Once you are out of the deep gravity well, Isp is king. Thrust does not matter. So a Draco (or cluster of them) would actually be superior to SuperDraco for the purpose of a final kick stage.But if you're going to do all of that, in space, a SRM has much better storability properties, probably weighs less (when you account for the plumbing), and is a known and available quantity already. Just use a Star 48 or equivalent if that's what you want!Really, SuperDracos were designed for a very specific purpose, and trying to use them elsewhere just doesn't make sense at all.
Remembering that this is supposed to be a low-cost launcher and its design should therefore be optimised for cost, not performance, I'd suggest the following design parameters: Common propellant for both stages and using existing equipment where possible.Given the above, how about the following proposal: A 2-stage rocket; both stages keralox with a single M1-D SL engine? The SL version is not as efficient as the Vac in space, but it should be sufficient (it has a vacuum isp of 308 versus 348). It's also lower thrust, which helps with problems of over-acceleration on the second stage (and it can throttle down to 70%).Anyone care to run the numbers?
Quote from: CuddlyRocket on 01/09/2016 02:59 pmRemembering that this is supposed to be a low-cost launcher and its design should therefore be optimised for cost, not performance, I'd suggest the following design parameters: Common propellant for both stages and using existing equipment where possible.Given the above, how about the following proposal: A 2-stage rocket; both stages keralox with a single M1-D SL engine? The SL version is not as efficient as the Vac in space, but it should be sufficient (it has a vacuum isp of 308 versus 348). It's also lower thrust, which helps with problems of over-acceleration on the second stage (and it can throttle down to 70%).Anyone care to run the numbers?Won't work, too much thrust for a merlin on second stage at minimum throttle the upper stage would hit 20gs at burn out.
Quote from: Lars-J on 01/08/2016 05:03 pmNo, it has little merit for a deep space mission. Once you are out of the deep gravity well, Isp is king. Thrust does not matter. So a Draco (or cluster of them) would actually be superior to SuperDraco for the purpose of a final kick stage.Not that I disagree with you, but a Star 48 has an ISP of 292 (see http://forum.nasaspaceflight.com/index.php?topic=33084.msg1109220#msg1109220) which is also really poor. SpaceX built the SuperDraco to essentially compete with an SRM: low ISP, high thrust, quick ignition, non-cryo propellant, with the notable difference being that it can throttle dynamically instead of being stuck with a fixed thrust profile.But if you're going to do all of that, in space, a SRM has much better storability properties, probably weighs less (when you account for the plumbing), and is a known and available quantity already. Just use a Star 48 or equivalent if that's what you want!Really, SuperDracos were designed for a very specific purpose, and trying to use them elsewhere just doesn't make sense at all.
That would be somewhat counter-productive I think. A single m1-d can move..eh...lets say about 70,000kg off the pad for a low TWR. Lets say that S2 is bigger (40 tonnes, including payload). This means that the first stage should weigh about 30 tonnes. M1-d does about 84,000kgf in vacuum (we are still talking about the SL version, not MVac). How much could you feasibly throttle it down before the payload liquefies?
My pony is that is your upper stage is large enough, the situation is no different than what current small F9 payloads experience - such as CASSIOPE, DISCOVR, and now JASON-3 - and somehow those payloads don't seem to "liquefy". You are exaggerating the issue of g-loads at burnout.
Well I took the leap last night to give my best effort at making my own new "Phoenix" F1 class vehicle and testing it out on a simulator linked to by this site in the archives at Silverbird Astronautics.http://www.silverbirdastronautics.com/LVperform.htmlThis was the first time I have ever done an exercise like this. I have watched many other here do similar, some of you are very very good at it. I do not profess to be good at all.My designs started with the specifications for using the Merlin 1D FT engine w/ 756 kN thrust, and building the vehicle around that. I also made an early decision to make the new vehicle with a 2m core, not the 1.7 I believe the old F1 had. I think the Merlin 1D FT is too much rocket to stick on that small a diameter core without getting something too long and bendy.I also wanted to make a better S2, so I selected to use a 100kN Methane upper stage. ( Darma Technolgies CHASE 10 ) I had to guess what a vacuum engine could do for ISP, and guessed 350s.G's at liftoff were set to be 1.18, so the mass of the complete vehicle would then be 65329 kg's.After some iterations on the calculations, my mass distribution is a followsStage 1:Dry mass = 3461 kgPropellant = 55368 kgThrust = 756 kNISP avg = 304Stage 2:Dry mass = 619Propellant = 5881Trust = 100 kNISP = 350Fairing 160 kg
Quote from: Dante80 on 01/09/2016 04:58 pmThat would be somewhat counter-productive I think. A single m1-d can move..eh...lets say about 70,000kg off the pad for a low TWR. Lets say that S2 is bigger (40 tonnes, including payload). This means that the first stage should weigh about 30 tonnes. M1-d does about 84,000kgf in vacuum (we are still talking about the SL version, not MVac). How much could you feasibly throttle it down before the payload liquefies?My pony is that is your upper stage is large enough, the situation is no different than what current small F9 payloads experience - such as CASSIOPE, DISCOVR, and now JASON-3 - and somehow those payloads don't seem to "liquefy". You are exaggerating the issue of g-loads at burnout.
Quote from: Lars-J on 01/09/2016 08:14 pmMy point is that is your upper stage is large enough, the situation is no different than what current small F9 payloads experience - such as CASSIOPE, DISCOVR, and now JASON-3 - and somehow those payloads don't seem to "liquefy". You are exaggerating the issue of g-loads at burnout.I think that its not the same thing man. Running the numbers for a 110+ ton S2 lifted by 9 M-1ds to a 40 ton S2 lifted by one makes me think that the situation is different at S2 burnout with a small payload.
My point is that is your upper stage is large enough, the situation is no different than what current small F9 payloads experience - such as CASSIOPE, DISCOVR, and now JASON-3 - and somehow those payloads don't seem to "liquefy". You are exaggerating the issue of g-loads at burnout.
No, you are not getting what I'm saying. What I am proposing is that the upper stage basically be the F9 upper stage, but slimmed and stretched to F1 diameter, powered by a single M1D. This large upper stage would not have the burnout g-load issue that you are concerned with, since it would have a similar dry weight of the F9 upper stage. But since this stage would not be SSTO, I propose putting it on top of a smaller but same diameter 1st stage, with an M1D at full thrust.
But I understood what you said. That's why S2 is a little bigger than S1 (as you said), and it's less than half the weight of the F9 S2. The diameter is 1.7m.
But since this stage would not be SSTO, I propose putting it on top of a smaller but same diameter 1st stage, with an M1D at full thrust.