Quote from: Robotbeat on 03/02/2013 03:06 pmGuys we get tweets from the space X team members. it's not that big of a deal if we don't get it on the official Twitter account.Apart from @elonmusk, whose tweets do you recommend for actual technical content?
Guys we get tweets from the space X team members. it's not that big of a deal if we don't get it on the official Twitter account.
In other prop news: Did anyone else think the Mvac nozzle looked a little peculiar right after stage two shutdown?
Quote from: jcm on 03/02/2013 05:21 pmQuote from: Robotbeat on 03/02/2013 03:06 pmGuys we get tweets from the space X team members. it's not that big of a deal if we don't get it on the official Twitter account.Apart from @elonmusk, whose tweets do you recommend for actual technical content?I like Mollie McCormick and Matt Sachtlerhttps://twitter.com/Molliway and https://twitter.com/mattsachtlerI would be interested in others too.
But a missed rendezvous??? Premature exclamation man!This stuff is normal. As another poster said, if anything, abnormally FEW problems.... Chill! Enjoy the ride and stop worrying so much. (I admit, I was worried right after launch up till about 3 PM eastern but they fixed it)
Quote from: Lar on 03/02/2013 04:59 pmBut a missed rendezvous??? Premature exclamation man!This stuff is normal. As another poster said, if anything, abnormally FEW problems.... Chill! Enjoy the ride and stop worrying so much. (I admit, I was worried right after launch up till about 3 PM eastern but they fixed it)Yes, they missed it. They were supposed to be there today, and they are not, because they could not make a burn in time to get there. They still haven't gotten there because they have to prove that it won't happen again.So they did miss the rendezvous that was planned. This was supposed to use a quicker approach to ISS. If there was an experiment in there which required one day before it had to get to ISS or data would be lost (not saying there is) then this experiment would be gone.The plan was to get to ISS in one day, that did not happen because something went wrong. Saying "this only proves how awesome SpaceX is!!!11!1!" means you are losing sight of what is important...
If you pay for FedEx overnight delivery, and the truck catches fire, but because of some heroic and clever actions by the FedEx people you package survives and is delivered intact by a day late, it's still late.
It's got to be incredibly frustrating for people to pick on every little glitch as counting against them.
Since there's extra margin built in, it's fine for NASA if Falcon 9 loses an engine on the way up, if the thrusters have a glitch, if a computer loses sync, etc. These systems are redundant for a reason because what matters is delivering the payload successfully within a reasonable time frame not whether there are non-LOM glitches in the meantime.
Quote from: Robotbeat on 03/02/2013 07:27 pm Since there's extra margin built in, it's fine for NASA if Falcon 9 loses an engine on the way up, if the thrusters have a glitch, if a computer loses sync, etc. These systems are redundant for a reason because what matters is delivering the payload successfully within a reasonable time frame not whether there are non-LOM glitches in the meantime.Redundancy didn't save the day here. It would have been LOM if the pod glitches would not have gone away by valve yanking. Redundant system would not have required it to proceed with the mission.
Quote from: yg1968 on 03/02/2013 11:06 amNo, it wasn't known before. See this post on the cost of the solar arrays:http://forum.nasaspaceflight.com/index.php?topic=30385.msg1020178#msg1020178Posts in that general area indicate it was.However I'll note that space rate panels will have a load of parts Earth panels will not. Specifically all the space rated mechanical bits to deploy/steer them. Going battery only also eliminates knock on parts, like latches, actuators, deployment mechanisms plus all the associated testing/QC costs. That sounds like a pretty good trade.Downside. You will definitely need a separate software build for Crewed Vs Cargo Dragon. Array deployment seems a pretty big event and a bunch of code will be associated with it, some of which will probably trigger/inhibit other stuff.
No, it wasn't known before. See this post on the cost of the solar arrays:http://forum.nasaspaceflight.com/index.php?topic=30385.msg1020178#msg1020178
Quote from: R7 on 03/01/2013 09:39 pmQuote from: smoliarm on 03/01/2013 08:48 pm2. CO2 -- since most of He production goes from natural gas, some processing schemes give He with substantial CO2 content. However, it is difficult to imagine that CO2 would form a solid ice blocking valve.Well the He is released from very high pressure reservoir, it expands, does work, cools, no? But does it cool enough to freeze CO2, dunno. Moisture more likely would freeze.Agree on both comments.Also, about moisture -- it is not only freezes more easily, it is also pretty easy to get as contaminant. It can get in He at production, transportation, and at propellant/pressurizer loading just as well.
Quote from: smoliarm on 03/01/2013 08:48 pm2. CO2 -- since most of He production goes from natural gas, some processing schemes give He with substantial CO2 content. However, it is difficult to imagine that CO2 would form a solid ice blocking valve.Well the He is released from very high pressure reservoir, it expands, does work, cools, no? But does it cool enough to freeze CO2, dunno. Moisture more likely would freeze.
2. CO2 -- since most of He production goes from natural gas, some processing schemes give He with substantial CO2 content. However, it is difficult to imagine that CO2 would form a solid ice blocking valve.
For anyone interested, here's some best available images (1080p @ fullscreeen) of the HRSGFs visible in the Dragon Trunk just after separation.SpaceX have apparently been trying to keep images of the Trunk + cargo secret - pretty pointless in the end.
redundancy probably did contribute to this non-LOM glitch.
Quote from: Lar on 03/02/2013 04:59 pmBut a missed rendezvous??? Premature exclamation man!This stuff is normal. As another poster said, if anything, abnormally FEW problems.... Chill! Enjoy the ride and stop worrying so much. (I admit, I was worried right after launch up till about 3 PM eastern but they fixed it)Yes, they missed it. They were supposed to be there today, and they are not, because they could not make a burn in time to get there. They still haven't gotten there because they have to prove that it won't happen again.So they did miss the rendezvous that was planned. This was supposed to use a quicker approach to ISS. If there was an experiment in there which required one day before it had to get to ISS or data would be lost (not saying there is) then this experiment would be gone.The plan was to get to ISS in one day, that did not happen because something went wrong. Saying "this only proves how awesome SpaceX is!!!11!1!" means you are losing sight of what is important.If you pay for FedEx overnight delivery, and the truck catches fire, but because of some heroic and clever actions by the FedEx people you package survives and is delivered intact by a day late, it's still late.By the way, I'm not worried, I'm following this with as much excitement as anyone else here. I think SpaceX is doing great work. I'm trying not to let my excitement get in the way of being objective, however.
Agreed, but redundancy probably did contribute to this non-LOM glitch. They have a lot more valves than if they had just a single ox and single fuel tank.
Wouldn't it be simple enough to chill the He so that all water vapour freezes out before loading it to the spacecraft?
Not so sure how you'd ensure no water is already in the prop system before you begin loading - long flush with high temperature dry nitrogen?
Did NASA pay extra for overnight delivery? If you order 5 business day delivery, often get the package in 3 days but one time have to wait until the 4th day, you have no right to complain.NASA is used to 3-day rendezvous, so this is still early for them. It's got to be incredibly frustrating for people to pick on every little glitch as counting against them. What matters is that the payload gets safely to ISS within a reasonable time (and back to the ground). Since there's extra margin built in, it's fine for NASA if Falcon 9 loses an engine on the way up, if the thrusters have a glitch, if a computer loses sync, etc. These systems are redundant for a reason because what matters is delivering the payload successfully within a reasonable time frame not whether there are non-LOM glitches in the meantime.If you were just trying to minimize number of glitches, you'd have single-string everything and you'd have a high LOM rate but otherwise, hey, no glitches!