Quote from: TheRadicalModerate on 09/18/2020 06:49 amQuote from: GregA on 09/17/2020 06:44 amHe means have a standard Starship that's used in lots of different ways.Rather than modifying Starship types for a variety of different types of missions.I'm assuming that too.QuoteI agree generally that it should be standardised.But if it can be particularly more efficient for a customer who wants a lot of launches, maybe there's some scope.The beauty of the modern shipping container is not that it's a great way to load and deploy cargo. Rather it's a great way to transship cargo, which turns out to be more expensive than the deployment problem--at least on Earth. But for Starlink and a whole bunch of other satellites, reliable deployment is everything, because there is no transshipment happening.Beyond that, for Starlink, you also want to minimize deployment debris. The tensioning rods aren't perfect in this regard, but they're vastly better than some kind of standardized container tossed into space. If you want to re-use the containers, you can't stack stuff on top of one another, then unstack and deploy it in orbit, without a huge amount of complexity. Deployment complexity scares the bejeezus out of your customers.When you get to lunar or martian surface deployments, containers make a lot more sense. But for satellites? Not happening any time soon.I took Robotbeat's patient advice and started a topic on this subject:https://forum.nasaspaceflight.com/index.php?topic=51968.new;You make a good point about satellites, but my original thinking was indeed for colony-building (on a surface or a free-flying facility) rather than the general satellite population. The shipping volume will be orders of magnitude greater. Also, I was thinking more about a standard interfacing method rather than a physical container, as in load attachment geometry, gripping points for handling, signal connectors, digital interface standards, and so forth.
Quote from: GregA on 09/17/2020 06:44 amHe means have a standard Starship that's used in lots of different ways.Rather than modifying Starship types for a variety of different types of missions.I'm assuming that too.QuoteI agree generally that it should be standardised.But if it can be particularly more efficient for a customer who wants a lot of launches, maybe there's some scope.The beauty of the modern shipping container is not that it's a great way to load and deploy cargo. Rather it's a great way to transship cargo, which turns out to be more expensive than the deployment problem--at least on Earth. But for Starlink and a whole bunch of other satellites, reliable deployment is everything, because there is no transshipment happening.Beyond that, for Starlink, you also want to minimize deployment debris. The tensioning rods aren't perfect in this regard, but they're vastly better than some kind of standardized container tossed into space. If you want to re-use the containers, you can't stack stuff on top of one another, then unstack and deploy it in orbit, without a huge amount of complexity. Deployment complexity scares the bejeezus out of your customers.When you get to lunar or martian surface deployments, containers make a lot more sense. But for satellites? Not happening any time soon.
He means have a standard Starship that's used in lots of different ways.Rather than modifying Starship types for a variety of different types of missions.
I agree generally that it should be standardised.But if it can be particularly more efficient for a customer who wants a lot of launches, maybe there's some scope.
Now back to Starship and Starlink. A V1.0 Starlink is ~260kg but a 50% heavier V2.0 is likely to be as much as 400kg. So numbers of sats per launch at best would be 240. On a reduced payload capability Starship probably just 120. In the full 42,000 sat set of end game Starlink a 5 year life would require ~8000 sats launched each year. At 240 sats per launch that is 34 launches/year if the mass of the Starlink sats do not get any heavier. A 500kg V2.1 would require 40+ launches/year. As stated before this is just the rate needed to support Starlink. By 2024 the launch rates for Starship would need to be about 50/year to meet the needs of Starlink and all the other demands not able to be met by other existing smaller LVs including F9 and FH. Just 2 Lunar mission in 1 year would need ~12 launches. By 2026 demand from Starlink and others would balloon the launch rate to close to 100/year. NOTE just 2 pads launching once a week can keep up with this large number of launches.
There are some pretty good reasons why they might not increase the size of the v2.x birds:
...4) The astronomers. I guess you could do a partial solar deployment, but that's not great for low-orbit checkout and de-orbiting things that fail early. Otherwise, more power = brighter birds in open-book mode, during orbit raise.
Question - Presently with F9, S2 starts a longitudinal spin to disperse the Starlink stack of satellites, Starship does not perform the dispersal spin, plus, even if it did, the "chompper" hatch is potentially(?) an obstruction, so the question, how does the physics work to get the dispersion of the sats, and what is the mechanism to make that happen? if previously asked, apologies, otherwise...thank you -
Quote from: winkhomewinkhome on 11/02/2020 01:06 amQuestion - Presently with F9, S2 starts a longitudinal spin to disperse the Starlink stack of satellites, Starship does not perform the dispersal spin, plus, even if it did, the "chompper" hatch is potentially(?) an obstruction, so the question, how does the physics work to get the dispersion of the sats, and what is the mechanism to make that happen? if previously asked, apologies, otherwise...thank you -Different launch vehicle; different constraints; different solution.Since F9 S2 is expendable and mass-constrained, it made sense to go with the cheap, lightweight, and novel deployment approach they did. If they end up with the occasional crib death as a result of trading paint, it's still cheaper than a "proper" aerospace-grade deployment mechanism.With SS being volume constrained, on the other hand, they can afford to throw hardware at it to make a robust deployment mechanism. And since the entire vehicle is reusable, it doesn't really matter if it costs a bit more.
Quote from: XenIneX on 11/02/2020 01:37 amQuote from: winkhomewinkhome on 11/02/2020 01:06 amQuestion - Presently with F9, S2 starts a longitudinal spin to disperse the Starlink stack of satellites, Starship does not perform the dispersal spin, plus, even if it did, the "chompper" hatch is potentially(?) an obstruction, so the question, how does the physics work to get the dispersion of the sats, and what is the mechanism to make that happen? if previously asked, apologies, otherwise...thank you -Different launch vehicle; different constraints; different solution.Since F9 S2 is expendable and mass-constrained, it made sense to go with the cheap, lightweight, and novel deployment approach they did. If they end up with the occasional crib death as a result of trading paint, it's still cheaper than a "proper" aerospace-grade deployment mechanism.With SS being volume constrained, on the other hand, they can afford to throw hardware at it to make a robust deployment mechanism. And since the entire vehicle is reusable, it doesn't really matter if it costs a bit more.Given that the chomper appears to be one sided it seems plausible to me that it’ll integrate some kind of robotic arm to move the payload outside enough to be deployed. I must say, the one sided design does seem sub-optimal from a deployment stand point, but I guess they gain enough from heat shielding and launch characteristics that the weight of some complex deployment mechanism is worth it.
Quote from: XenIneX on 11/02/2020 01:37 amQuote from: winkhomewinkhome on 11/02/2020 01:06 amQuestion - Presently with F9, S2 starts a longitudinal spin to disperse the Starlink stack of satellites, Starship does not perform the dispersal spin, plus, even if it did, the "chompper" hatch is potentially(?) an obstruction, so the question, how does the physics work to get the dispersion of the sats, and what is the mechanism to make that happen? if previously asked, apologies, otherwise...thank you -Different launch vehicle; different constraints; different solution.Since F9 S2 is expendable and mass-constrained, it made sense to go with the cheap, lightweight, and novel deployment approach they did. If they end up with the occasional crib death as a result of trading paint, it's still cheaper than a "proper" aerospace-grade deployment mechanism.With SS being volume constrained, on the other hand, they can afford to throw hardware at it to make a robust deployment mechanism. And since the entire vehicle is reusable, it doesn't really matter if it costs a bit more.Don't forget: SpaceX get that deployment mechanism back at the end of the mission with Starship.
Quote from: ZChris13 on 11/02/2020 09:10 amQuote from: XenIneX on 11/02/2020 01:37 amQuote from: winkhomewinkhome on 11/02/2020 01:06 amQuestion - Presently with F9, S2 starts a longitudinal spin to disperse the Starlink stack of satellites, Starship does not perform the dispersal spin, plus, even if it did, the "chompper" hatch is potentially(?) an obstruction, so the question, how does the physics work to get the dispersion of the sats, and what is the mechanism to make that happen? if previously asked, apologies, otherwise...thank you -Different launch vehicle; different constraints; different solution.Since F9 S2 is expendable and mass-constrained, it made sense to go with the cheap, lightweight, and novel deployment approach they did. If they end up with the occasional crib death as a result of trading paint, it's still cheaper than a "proper" aerospace-grade deployment mechanism.With SS being volume constrained, on the other hand, they can afford to throw hardware at it to make a robust deployment mechanism. And since the entire vehicle is reusable, it doesn't really matter if it costs a bit more.Don't forget: SpaceX get that deployment mechanism back at the end of the mission with Starship.Here is a simple mechanism to do the starlink deploy.Eject the stack as one unit. Once free from SS have a small compressed N2 jet start the spin. Then release the clamps and allow the dispersal. Only requires one COPV and a RCS bell/jet.
Edit: now that I think of it, in Starship, the columns of cartridges could be stacked on a turntable to increase the amount of satellites deployed from each cartridge stack.
Quote from: rsdavis9 on 11/02/2020 12:02 pmQuote from: ZChris13 on 11/02/2020 09:10 amQuote from: XenIneX on 11/02/2020 01:37 amQuote from: winkhomewinkhome on 11/02/2020 01:06 amQuestion - Presently with F9, S2 starts a longitudinal spin to disperse the Starlink stack of satellites, Starship does not perform the dispersal spin, plus, even if it did, the "chompper" hatch is potentially(?) an obstruction, so the question, how does the physics work to get the dispersion of the sats, and what is the mechanism to make that happen? if previously asked, apologies, otherwise...thank you -Different launch vehicle; different constraints; different solution.Since F9 S2 is expendable and mass-constrained, it made sense to go with the cheap, lightweight, and novel deployment approach they did. If they end up with the occasional crib death as a result of trading paint, it's still cheaper than a "proper" aerospace-grade deployment mechanism.With SS being volume constrained, on the other hand, they can afford to throw hardware at it to make a robust deployment mechanism. And since the entire vehicle is reusable, it doesn't really matter if it costs a bit more.Don't forget: SpaceX get that deployment mechanism back at the end of the mission with Starship.Here is a simple mechanism to do the starlink deploy.Eject the stack as one unit. Once free from SS have a small compressed N2 jet start the spin. Then release the clamps and allow the dispersal. Only requires one COPV and a RCS bell/jet.Wouldn't this method also need an on board computer/reaction wheel, battery and so on (aside from what is used to release the payload) to position the stack in a way that makes the RCS bell spin it in the correct plane? What if the stack rotates slightly for some reason after it has been ejected from Starship? Then the RCS will spin the stack in some unpredictable plane.Or does the orientation of the spin not matter? I thought the F9 S2 performs it's spin in this axis for a reason instead of any other axis.I think it would be more complicated than just adding a fire extinguisher bracket to the base of the stack and let it rip once the stack is far enough away from SS
Quote from: capoman on 11/02/2020 12:13 pmEdit: now that I think of it, in Starship, the columns of cartridges could be stacked on a turntable to increase the amount of satellites deployed from each cartridge stack.If you include the ability to tilt the base of each stack's mounting base out 90 degrees then you can do away with ejector springs.Tilt the stack perpendicular to the ship's longitudinal axis and begin a slow roll of the ship. Release the stack at the proper time and rotate the turntable to the next stack, repeat the tilt and release.
Quote from: Slothman on 11/02/2020 01:48 pmQuote from: rsdavis9 on 11/02/2020 12:02 pmQuote from: ZChris13 on 11/02/2020 09:10 amQuote from: XenIneX on 11/02/2020 01:37 amQuote from: winkhomewinkhome on 11/02/2020 01:06 amQuestion - Presently with F9, S2 starts a longitudinal spin to disperse the Starlink stack of satellites, Starship does not perform the dispersal spin, plus, even if it did, the "chompper" hatch is potentially(?) an obstruction, so the question, how does the physics work to get the dispersion of the sats, and what is the mechanism to make that happen? if previously asked, apologies, otherwise...thank you -Different launch vehicle; different constraints; different solution.Since F9 S2 is expendable and mass-constrained, it made sense to go with the cheap, lightweight, and novel deployment approach they did. If they end up with the occasional crib death as a result of trading paint, it's still cheaper than a "proper" aerospace-grade deployment mechanism.With SS being volume constrained, on the other hand, they can afford to throw hardware at it to make a robust deployment mechanism. And since the entire vehicle is reusable, it doesn't really matter if it costs a bit more.Don't forget: SpaceX get that deployment mechanism back at the end of the mission with Starship.Here is a simple mechanism to do the starlink deploy.Eject the stack as one unit. Once free from SS have a small compressed N2 jet start the spin. Then release the clamps and allow the dispersal. Only requires one COPV and a RCS bell/jet.Wouldn't this method also need an on board computer/reaction wheel, battery and so on (aside from what is used to release the payload) to position the stack in a way that makes the RCS bell spin it in the correct plane? What if the stack rotates slightly for some reason after it has been ejected from Starship? Then the RCS will spin the stack in some unpredictable plane.Or does the orientation of the spin not matter? I thought the F9 S2 performs it's spin in this axis for a reason instead of any other axis.I think it would be more complicated than just adding a fire extinguisher bracket to the base of the stack and let it rip once the stack is far enough away from SSI think this is what I was suggesting. KISS.
There's no reason to think SpaceX will deploy Starlinks the same way with Starship as with F9. F9 has some serious limitations it has to deal with at 60 satellites, and the reason they do it the way they do. Per my previous post, I think that using a cartridge tower on a turntable is the simplest solution. They can be ejected one at a time sideways away from the ship, no debris or anything like that, no fancy spins or even the need to angle ejector out to space. Springs are reliable and there are many simple ways of doing a latch. The proposals above are just way more complicated than need be, and are using the assumption that SpaceX will use the F9 method of deployment which would be no longer needed with Starship.