Quote from: Lars_J on 12/01/2012 09:27 pmJurvetson (SpaceX investor) posted a flickr image of the current state of the CRS2 Dragon - currently under construction in a clean room at Hawthorne:http://www.flickr.com/photos/jurvetson/8234369578/in/photostream (picture takes two days ago)Nice. Also, Falcon 9v1.1 1st stage, Merlin 1D, and a real 5m fairing.
Jurvetson (SpaceX investor) posted a flickr image of the current state of the CRS2 Dragon - currently under construction in a clean room at Hawthorne:http://www.flickr.com/photos/jurvetson/8234369578/in/photostream (picture takes two days ago)
Jurvetson (SpaceX investor) posted a flickr image of the current state of the CRS2 Dragon - currently under construction in a clean room at Hawthorne
I start to suspect CRS-2 launch would not happen in Jaunary even without engine out on CRS-1.
March 1 - Dragon CRS2, CUSat 1&2 - Falcon 9 v1.0 - Canaveral SLC-40
Quote from: Lars_J on 12/01/2012 09:27 pmJurvetson (SpaceX investor) posted a flickr image of the current state of the CRS2 Dragon - currently under construction in a clean room at HawthorneHuh? I thought Dragon for this mission was already build. I remember a few months ago some photo with four Dragons in various stages of construction.
No need to suspect:Quote from: SaloMarch 1 - Dragon CRS2, CUSat 1&2 - Falcon 9 v1.0 - Canaveral SLC-40
Quote from: tigerade on 12/02/2012 12:01 pmNo need to suspect:Quote from: SaloMarch 1 - Dragon CRS2, CUSat 1&2 - Falcon 9 v1.0 - Canaveral SLC-40IIRC, the reschedule was at least partly driven by customer requirements, specifically something happening on ISS that required a re-arrangement of supply missions. I maintain my annoyanc at the delay e because it's going to make it harder to achieve the launch number goals for 2013 but I'm sure that SpaceX have some idea what they are doing.
Quote from: Ben the Space Brit on 12/02/2012 01:31 pmQuote from: tigerade on 12/02/2012 12:01 pmNo need to suspect:Quote from: SaloMarch 1 - Dragon CRS2, CUSat 1&2 - Falcon 9 v1.0 - Canaveral SLC-40IIRC, the reschedule was at least partly driven by customer requirements, specifically something happening on ISS that required a re-arrangement of supply missions. I maintain my annoyanc at the delay e because it's going to make it harder to achieve the launch number goals for 2013 but I'm sure that SpaceX have some idea what they are doing.IIRC there was also an ISS software upgrade in the mix as well....
Quote from: LegendCJS on 11/16/2012 06:17 pmQuote from: baldusi on 11/16/2012 05:54 pmThe article also mentioned that they decided not to resynch the computer, because they didn't felt it was necessary, but the fact that it got out of the loop doesn't means it had permanent damage.I suspect, if I'm forced to make a guess, that the radiation event might have generated some non recoverable latch up. But instead of trying to get it back, they kept it down so they could analyze it later when it returned.SpaceX wanted to resynch the computer, but Nasa was not in favor of doing that while it was attached to station, so they didn't. If it had been free flying SpaceX would have issued the resynch command. Moving forward SpaceX plans on making resynching automatic. Also to note is that SpaceX's expectations for radiation induced electronics trouble were higher than what they actually observed for the mission.source: talk given by SpaceX employee (senior GNC engineer)Absolutely, positively 100% false. NASA thought it was a good idea to resync but mainly wanted to make sure they and SpaceX understood the process. SpaceX's plan changed a lot which did not give a clear indication that the resync was well understood. NASA just asked for caution and many felt if it was not well understood and not truly critical, then don't push it. Also not sure if by your last sentence you mean SpaceX expected less problems from the rad environment or more than then saw. From the beginning they dismissed radiation hits and NASA had to repeatedly pushed for more evidence. In the end a waiver was granted but we were expecting problems.
Quote from: baldusi on 11/16/2012 05:54 pmThe article also mentioned that they decided not to resynch the computer, because they didn't felt it was necessary, but the fact that it got out of the loop doesn't means it had permanent damage.I suspect, if I'm forced to make a guess, that the radiation event might have generated some non recoverable latch up. But instead of trying to get it back, they kept it down so they could analyze it later when it returned.SpaceX wanted to resynch the computer, but Nasa was not in favor of doing that while it was attached to station, so they didn't. If it had been free flying SpaceX would have issued the resynch command. Moving forward SpaceX plans on making resynching automatic. Also to note is that SpaceX's expectations for radiation induced electronics trouble were higher than what they actually observed for the mission.source: talk given by SpaceX employee (senior GNC engineer)
The article also mentioned that they decided not to resynch the computer, because they didn't felt it was necessary, but the fact that it got out of the loop doesn't means it had permanent damage.I suspect, if I'm forced to make a guess, that the radiation event might have generated some non recoverable latch up. But instead of trying to get it back, they kept it down so they could analyze it later when it returned.
Remember that they had water issues on the electric system that meant the freezer was shut down for a while. That might mean some other extra mods.
I wonder what does "sea water ingress" even means. Where did the water get to?
Quote from: krytek on 12/07/2012 11:51 amI wonder what does "sea water ingress" even means. Where did the water get to?It probably gets into the RCS fuel system through the thruster nozzles and seeps into the lower service ring through the open parachute bay.
Quote from: Ben the Space Brit on 12/07/2012 01:09 pmQuote from: krytek on 12/07/2012 11:51 amI wonder what does "sea water ingress" even means. Where did the water get to?It probably gets into the RCS fuel system through the thruster nozzles and seeps into the lower service ring through the open parachute bay.hope your wrong about the location of the leaks. Many still have issues of the Dragon being trucked from CA to Texas on US highways with toxic fuels not removed.
Jim claimed that the Dragon propellants were off loaded at Sealaunch's facilities in San Diego. I haven't seen confirmation of that anywhere else.
Quote from: douglas100 on 12/07/2012 03:06 pmJim claimed that the Dragon propellants were off loaded at Sealaunch's facilities in San Diego. I haven't seen confirmation of that anywhere else.Long Beach and that was suppose to be for the first one.
Long Beach and that was suppose to be for the first one.