The issue has already been decided. V1.1 is a suitable substitute for V1.0, now that it's had a successful flight.(And the engines are throttleable, you guys.)
Quote from: Robotbeat on 01/16/2014 09:20 pmThe issue has already been decided. V1.1 is a suitable substitute for V1.0, now that it's had a successful flight.(And the engines are throttleable, you guys.)I thought the issue being discussed here was whether Jason was so extraordinarily light that extreme measures might be needed, beyond throttling (throttling has limits).... not the whole 1.1 substituted for 1.0 thing (which I for one would desperately like to see NOT reopened)
Quote from: Lar on 01/16/2014 09:44 pmQuote from: Robotbeat on 01/16/2014 09:20 pmThe issue has already been decided. V1.1 is a suitable substitute for V1.0, now that it's had a successful flight.(And the engines are throttleable, you guys.)I thought the issue being discussed here was whether Jason was so extraordinarily light that extreme measures might be needed, beyond throttling (throttling has limits).... not the whole 1.1 substituted for 1.0 thing (which I for one would desperately like to see NOT reopened)...well, if Jason is so dang light and if v1.1 has excess performance, it's not impossible for the stage to cut off with plenty of fuel still in the tank, which would reduce the peak acceleration, too. Otherwise, all you do is add some aluminum ballast or something. It really, really isn't a big deal.
Don't they also, besides just throttling, also have the option of shutting down engines earlier than their 'standard' profile.
Quote from: faramund on 01/17/2014 05:34 amDon't they also, besides just throttling, also have the option of shutting down engines earlier than their 'standard' profile.This is about the second stage with its single engine.
Quote from: guckyfan on 01/17/2014 06:15 amQuote from: faramund on 01/17/2014 05:34 amDon't they also, besides just throttling, also have the option of shutting down engines earlier than their 'standard' profile.This is about the second stage with its single engine....and the M1Dvac can throttle deeper than the M1CVac, so the point still applies.
This sounds like the perfect flight to test second stage recovery. How about instead of ballast they put a heat shield and super dracos on the second stage? Isn't that the whole plan? To get full reuse for super light payloads like this?Why ballast when recovery can be tested?
Quote from: Norm38 on 01/17/2014 12:37 pmThis sounds like the perfect flight to test second stage recovery. How about instead of ballast they put a heat shield and super dracos on the second stage? Isn't that the whole plan? To get full reuse for super light payloads like this?Why ballast when recovery can be tested?And we come back around to what I was suggesting a few posts upthread too. Groupthink[1] says that 2014 is too early to see much, if any, second stage reuse testing, even preliminary things like trying to reenter an otherwise unmodified second stage and not have it tumble initially (till it melts, since it's unshielded), but maybe 2015?Exciting times ahead 1 - see the current poll standings here http://forum.nasaspaceflight.com/index.php?topic=33826.0 ... as of this writing it is 140/195 (or about 72% of respondents) for no reuse work at all.
Quote from: Lar on 01/17/2014 12:43 pmQuote from: Norm38 on 01/17/2014 12:37 pmThis sounds like the perfect flight to test second stage recovery. How about instead of ballast they put a heat shield and super dracos on the second stage? Isn't that the whole plan? To get full reuse for super light payloads like this?Why ballast when recovery can be tested?And we come back around to what I was suggesting a few posts upthread too. Groupthink[1] says that 2014 is too early to see much, if any, second stage reuse testing, even preliminary things like trying to reenter an otherwise unmodified second stage and not have it tumble initially (till it melts, since it's unshielded), but maybe 2015?Exciting times ahead 1 - see the current poll standings here http://forum.nasaspaceflight.com/index.php?topic=33826.0 ... as of this writing it is 140/195 (or about 72% of respondents) for no reuse work at all.They have done secondary burns after payload release before. I could see them doing this as a de-orbit burn after a LEO mission (seems very little additional effort), but nevertheless voted in the poll that this would not count as a recovery event.Cheers, Martin
Edit: I was reminded via PM that launch vehicles are not typically ballasted but rather are throttled back or engines shut down if g loads need adjusting.
Groupthink[1] says that 2014 is too early to see much, if any, second stage reuse testing, even preliminary things like trying to reenter an otherwise unmodified second stage and not have it tumble initially (till it melts, since it's unshielded), but maybe 2015?
Looks like NOAA is pressing to move up this satellite's launch to 1Q 2015 due to cancellation pressures from the CNES side if Jason-3 doesn't launches by then: http://www.spacenews.com/article/civil-space/39937noaa-seeks-boost-for-sat-programs-great-and-small-in-2015-budget
So the question becomes; If the SpaceX launch schedule moved another 2 weeks cause of CRS-3, did the Jason launch also move 2 weeks more? Can that time be made up?