Quote from: Prober on 01/25/2012 02:48 pmMaybe combing Demo 2/3 was a bad idea? Had Demo 2 launched by now these problem might have been fixed? The focus on saving costs, and time, sometimes bites you and you find out in the end you didn’t save anything.Probably not. COTS 2 alone would be station prox ops, so I'm guessing a lot of these issues would need to be fixed anyway. ...
Maybe combing Demo 2/3 was a bad idea? Had Demo 2 launched by now these problem might have been fixed? The focus on saving costs, and time, sometimes bites you and you find out in the end you didn’t save anything.
Quote from: Prober on 01/25/2012 02:48 pmMaybe combing Demo 2/3 was a bad idea? Had Demo 2 launched by now these problem might have been fixed? The focus on saving costs, and time, sometimes bites you and you find out in the end you didn’t save anything.Probably not. COTS 2 alone would be station prox ops, so I'm guessing a lot of these issues would need to be fixed anyway. Otherwise, why not just remanifest as COTS 2 only and launch on Feb 7? Clearly they are not doing that.Combining Orbcomm was a bad idea, and since been undone.
Quote from: iamlucky13 on 01/23/2012 09:33 pmMost of the work should be able to happen in parallel. The guys working on EMI aren't depending on trajectory refinements to do their tasks and vice versus, for example.About the EMI problem, I have my questions if they can solve this at the Cape. Do they have the shielded environment to do the testings or they need to transfer dragon back to their main facility?
Most of the work should be able to happen in parallel. The guys working on EMI aren't depending on trajectory refinements to do their tasks and vice versus, for example.
On page 17 of the Jan 16 issue of Aviation Week, an article by Jen Dimascio says "..and final approval for Dragon to approach the station will not come until at least three dys after launch." This conflicts with some posted schedules, which have the berthing two days after launch.It also say "By then, it should be clear whether SpaceX has control over the 20-ton vehicle as it orbits."20 tons? That's high, isn't it?
Quote from: Prober on 01/25/2012 02:48 pmMaybe combing Demo 2/3 was a bad idea? Had Demo 2 launched by now these problem might have been fixed? The focus on saving costs, and time, sometimes bites you and you find out in the end you didn’t save anything.Yeah, maybe. Would love to hear other perspectives on this?
I believe that you don't need a final cots-3 dragon to perform cots-2. The question is whether they could have had a cots-2 dragon ready significantly sooner than it's taken them to do the full-up cots-2/3.
Since they haven't launched a commercial customer payload since F1-5 in 2009, the only income is from COST/CRS milestones, investors, and taking deposits from customers on Launch B, C, and D and using the money to pay for Launch A in what is basically a space industry ponzi scheme.
About the EMI problem, I have my questions if they can solve this at the Cape. Do they have the shielded environment to do the testings or they need to transfer dragon back to their main facility?
>And optical can't transmit power.
There may now be a possible schedule conflict between the delayed Soyuz TMA-04M launch and TMA-22 return.http://forum.nasaspaceflight.com/index.php?topic=27678.msg855061#msg855061AFP: Russia 'to postpone next manned space launch'http://www.google.com/hostednews/afp/article/ALeqM5hHonNkSx76_s6cJApIH4XheVHeSA
Doesn't that post belong in the ISS thread? Or Russian launchers thread?
Quote from: woods170 on 01/27/2012 12:55 pmDoesn't that post belong in the ISS thread? Or Russian launchers thread?No, I only posted it here since it may have an effect on the C2/C3 mission. Full coverage of course belongs on the Russian thread.
So the delay to COTS 2/3 would be due to return of sufficient Dragon-trained crew to conduct rendezvous? or am I misunderstanding?