No. But we'll find out during the webcast. I'm guessing yes but could be wrong.
-
Want to remove ads? Register an account and login to see fewer ads, and become a Supporting Member to remove almost all ads.
Nikxice
Active Member
SpaceXVerified account @SpaceX
Standing down today due to excess upper level winds. Teams are working toward tomorrow's backup launch window, which opens at 10:30 p.m. EDT
7:56 PM - 15 May 2019
Standing down today due to excess upper level winds. Teams are working toward tomorrow's backup launch window, which opens at 10:30 p.m. EDT
7:56 PM - 15 May 2019
I think the number is slightly different for each rocket. F9 is highly susceptible to wind sheer because it is so tall and thin. Super Heavy and Starship will be much less so. I think. NASA probably determines the numbers based on safety since they were SpaceX's first major customer.
RFernatt
Solar/EV Owner/Enthusiast
That view in the fairing kinda reminds me of something... Coincidence? 
"Standing down to update satellite software and triple-check everything again. Always want to do everything we can on the ground to maximize mission success, next launch opportunity in about a week."
SpaceX on Twitter
So it was a payload issue - not a rocket issue.
SpaceX on Twitter
So it was a payload issue - not a rocket issue.
e-FTW
New electron smell
Hmm...
1- Can’t they update said software remotely on-orbit? I assume said software update is critical to deployment operation itself, so ‘no’.
2- QA much? It is nice that being their own customer, they have the flexibility to punt by a week, but one would think that once you are on the pad, all software QA possible would be done already.
¯\_(ツ)_/¯
Once more, SpaceX lets me get back from a one week vacation so I can see the launch. But now, I have to wait another week? Am running out of vacation budget here!
1- Can’t they update said software remotely on-orbit? I assume said software update is critical to deployment operation itself, so ‘no’.
2- QA much? It is nice that being their own customer, they have the flexibility to punt by a week, but one would think that once you are on the pad, all software QA possible would be done already.
¯\_(ツ)_/¯
Once more, SpaceX lets me get back from a one week vacation so I can see the launch. But now, I have to wait another week? Am running out of vacation budget here!
Yes people often upload FSW patches on orbit; traditionally pushing up an entire new image is a bit like rolling the dice (who knows what SpaceX's approach is to this). The downside is that the data rate is WAY slower when you're on orbit, and generally more prone to bit errors.
This is the most bizarre thing to most in the industry. What could possibly have happened that made them stack the whole thing, be ready for launch, and then stand down during the second launch attempt? There's literally nothing going on with the satellites at this point other than topping off the batteries, so that's the only thing that could possibly have thrown a flag form this payload. Its conceivable there was a race between a new FSW revision and getting this launch off, but you'd think SpaceX would have been able to track progress on both and reconcile the schedules if they were this close. Its hard to imagine there was some ah-ha moment that all the sudden changed the FSW...
On the production side, there's nothing short of uncovering a major design flaw back at the ranch that would have caused this kind of hold. And finding such a thing at this point would be seriously worrying.
One thing is absolutely certain: The "triple check everything" line was just a line. They're doing something specific; they're checking something specific.[/QUOTE]
The irony is not missed. This is a product to enable cheaper and faster communications between 2 end points in the globe, but the product itself cannot load its internal software at a decent rate?
