There are no apparent docking targets as such, so there will be some work required to "train" the approach and docking software.
NG MEV would be a better choice for this task. Cygnus/Service module is an option too.
Quote from: rsnellenberger on 10/01/2022 01:32 pmThere are no apparent docking targets as such, so there will be some work required to "train" the approach and docking software. Fiducial is visible in the centre of the LIDS ring.
Quote from: Reynold on 09/30/2022 03:10 pmMy prediction is that they will end up doing 2 missions, first a cargo Dragon reboost, which might just need a docking adaptor for the docking system installed on the Hubble in the last servicing mission. Presumably in the trunk, so the Dragon thrusters can point the right way to boost the Hubble. NASA may or may not be able to scrape together some money to pay SpaceX to develop the docking adaptor and fly the mission, but it would be pocket change compared to what they would have spent to deorbit it. This would be pretty low risk, NASA has gotten very comfortable with cargo Dragon. Then a Polaris manned mission with Jared and at least one NASA astronaut to do servicing, at a minimum a gyro swap out. By then, EVA from the Dragon will have been tested by Jared and crew on Polaris Dawn. NASA will presumably pay something to fly their astronaut, but most of the NASA money for that phase will probably go into building whatever parts are getting swapped out and training on what they want to do, support for the mission, etc. I'm guessing there will be a lot of support in NASA to do this, though, far more of the public has heard of Hubble and likes it than has heard of Artemis. If true about flying a NASA astronaut, it would be interesting to see if they choose one of the STS-125 crew that's still active.
My prediction is that they will end up doing 2 missions, first a cargo Dragon reboost, which might just need a docking adaptor for the docking system installed on the Hubble in the last servicing mission. Presumably in the trunk, so the Dragon thrusters can point the right way to boost the Hubble. NASA may or may not be able to scrape together some money to pay SpaceX to develop the docking adaptor and fly the mission, but it would be pocket change compared to what they would have spent to deorbit it. This would be pretty low risk, NASA has gotten very comfortable with cargo Dragon. Then a Polaris manned mission with Jared and at least one NASA astronaut to do servicing, at a minimum a gyro swap out. By then, EVA from the Dragon will have been tested by Jared and crew on Polaris Dawn. NASA will presumably pay something to fly their astronaut, but most of the NASA money for that phase will probably go into building whatever parts are getting swapped out and training on what they want to do, support for the mission, etc. I'm guessing there will be a lot of support in NASA to do this, though, far more of the public has heard of Hubble and likes it than has heard of Artemis.
Either de-rating the Dragon SuperDracos or replacing them outright with baseline Dracos would solve the RCS physical placement issues. There’d still be some cosine losses, but no need for a new-build thruster module in the Trunk. Cheap and cheerful! The showstopper, as I see it, is the capsule’s apex cap and the way it would fit - or not - up against the base of Hubble (handrails etc). The old Cargo Dragons had no nose covering during re-entry so maybe that’ll be the way forward.
Fascinating - thanks for the details! Glad to have these "nitpicks" as I certainly don't want to tell fish-tales. (I learned most of what I know on the subject from a combination of Wikipedia and various NSF posts where people in the know have commented on specific details as you've done here.) I've bookmarked your post for future reference... Since I have your $0.02, may I follow this up with a few more questions so I can be more knowledgeable about this going forward:1. Would it be correct to say that, although IDSS isn't quite as low-impact as LIDS (due to not having the "active force feedback control"), it is still much lower-impact than the legacy APAS-95 used by the Shuttle? Basically, that IDSS is a compromise on the more "ideal" design of LIDS that gets most of its benefits (compared to legacy APAS) without quite as much implementation complexity (and without diverging as much in mechanical compatibility from legacy APAS; I'm guessing Russia was the "international partner" who requested these design changes since they wanted the use a unified implementation)?2. Wikipedia's article on IDSS states that IDSS utilizes "6 servo-actuated legs" to "remove any relative motion [prior to retraction]". How does this differ from the more advanced "active force feedback control" used by LIDS? Is it a question of IDSS waiting until after initial capture to damp out relative motion versus LIDS actively compensating for it from the first moment of contact? Or is this where the distinction of magnets vs. latches/servos comes into play?3. For berthing scenarios where a robotic arm is used to precisely maneuver a vehicle/module to the port, does the soft-capture mechanism matter at all, or is only the hard-capture mechanism needed since the robotic arm already has (enough) control of the vehicle's positioning on all relevant axes? The ability to support both docking and berthing is often cited as a key feature of both IDSS and LIDS; was this ever prohibitive with legacy APAS or is selling this up for IDSS/LIDS just "marketing speak"? 4. [if you (or anyone else) know the answer...] Is the reason why Russia went to the trouble of creating its "hybrid" APAS/SSVP ports for the attachment of large modules (which, IIRC, use an APAS hard-capture ring in conjunction with the SSVP system's probe-and-drogue soft-capture mechanism) because this allowed them to use the wider tunnel and superior structural connection of the APAS hard-capture ring in conjunction with a lower-impact (and/or less-complicated) soft-capture system?
It's a little complicated, but only because people tend to make a lot of assumptions which aren't valid. The biggest one is that everyone follows the IDSS, they don't necessarily. To add more to the confusion, there is the NDS standard and NDS hardware, in this post I'm going to denote the hardware as NDS*. NDS* is a Boeing built docking adapter for NASA.Orion and CST-100 use the NDS*. Block 1 is not androgynous, I don't know for certain if Block 2 is. For it to be androgynous it must have active and passive Hard Capture hooks, and passive strikers for the other active's soft capture latches. Unless it's truly androgynous (where one system can be active or passive), there must be an active and a passive. Dragon 2 uses it's own docking system, but is compatible with NDS. So it's not correct to say that Dragon 2 uses an NDS*. They built their own system. You can also see all this in photos. Like CST-100/NDS*, neither have passive docking hooks or strikers.It's kinda like buying two different USB thumb drives. They work differently inside, but both can interface with the same USB port.
Polaris Dragon docked to Hubble
Looking good.. may want to flip Dragon 180 degrees though. Just a guess 😉
twitter.com/truthful_ast/status/1575637811981537282QuotePolaris Dragon docked to Hubblehttps://twitter.com/rookisaacman/status/1576310153053278208QuoteLooking good.. may want to flip Dragon 180 degrees though. Just a guess 😉
Seems like a smart way. Presume they would also need cameras/range finder in the truck to help with docking. No doubt they have already thought of this and have a solution Quote from: FutureSpaceTourist on 10/02/2022 05:02 amtwitter.com/truthful_ast/status/1575637811981537282QuotePolaris Dragon docked to Hubblehttps://twitter.com/rookisaacman/status/1576310153053278208QuoteLooking good.. may want to flip Dragon 180 degrees though. Just a guess 😉
Quote from: kevinof on 10/02/2022 08:15 amSeems like a smart way. Presume they would also need cameras/range finder in the truck to help with docking. No doubt they have already thought of this and have a solution Quote from: FutureSpaceTourist on 10/02/2022 05:02 amtwitter.com/truthful_ast/status/1575637811981537282QuotePolaris Dragon docked to Hubblehttps://twitter.com/rookisaacman/status/1576310153053278208QuoteLooking good.. may want to flip Dragon 180 degrees though. Just a guess 😉If there is a docking mechanisim in the trunk, and hubble is about the same diamiter as the trunk itself... is there any plume-related reason you cannot use the superdracos on Dragon , in a "pull" configuration?
Quote from: rakaydos on 10/02/2022 10:56 pmQuote from: kevinof on 10/02/2022 08:15 amSeems like a smart way. Presume they would also need cameras/range finder in the truck to help with docking. No doubt they have already thought of this and have a solution Quote from: FutureSpaceTourist on 10/02/2022 05:02 amtwitter.com/truthful_ast/status/1575637811981537282QuotePolaris Dragon docked to Hubblehttps://twitter.com/rookisaacman/status/1576310153053278208QuoteLooking good.. may want to flip Dragon 180 degrees though. Just a guess If there is a docking mechanisim in the trunk, and hubble is about the same diamiter as the trunk itself... is there any plume-related reason you cannot use the superdracos on Dragon , in a "pull" configuration?Both plume and the fact that the Super-Dracos are way too powerful.
Quote from: kevinof on 10/02/2022 08:15 amSeems like a smart way. Presume they would also need cameras/range finder in the truck to help with docking. No doubt they have already thought of this and have a solution Quote from: FutureSpaceTourist on 10/02/2022 05:02 amtwitter.com/truthful_ast/status/1575637811981537282QuotePolaris Dragon docked to Hubblehttps://twitter.com/rookisaacman/status/1576310153053278208QuoteLooking good.. may want to flip Dragon 180 degrees though. Just a guess If there is a docking mechanisim in the trunk, and hubble is about the same diamiter as the trunk itself... is there any plume-related reason you cannot use the superdracos on Dragon , in a "pull" configuration?
Seems like a smart way. Presume they would also need cameras/range finder in the truck to help with docking. No doubt they have already thought of this and have a solution Quote from: FutureSpaceTourist on 10/02/2022 05:02 amtwitter.com/truthful_ast/status/1575637811981537282QuotePolaris Dragon docked to Hubblehttps://twitter.com/rookisaacman/status/1576310153053278208QuoteLooking good.. may want to flip Dragon 180 degrees though. Just a guess
twitter.com/truthful_ast/status/1575637811981537282QuotePolaris Dragon docked to Hubblehttps://twitter.com/rookisaacman/status/1576310153053278208QuoteLooking good.. may want to flip Dragon 180 degrees though. Just a guess
Looking good.. may want to flip Dragon 180 degrees though. Just a guess
Screen capture (cropped) from last night's NSF live showing @brickmack's rendering of Dragon forward thrusters boosting hubble
Another thing I think we need to look at is Dragon on orbit endurance. Consumables, fuel, ECLSS... Especially when accounting for cabin depressurization. Dragon is shorter than Shuttle, but how much can it be expanded? Shuttle had a larger crew to spread workload around. Because it had an airlock, the non-eva crew was able to do more work than the non-eva crew in dragon will (I would think - they are basically in EVA too at that point)I think a boost mission would be a priority. Gyro replacement would be a bonus. So the mission would proceed something like: Launch, Dock, Boost, EVA(s), repress, undock, deorbit. First do no harm mentality - probably only replacing the failed gyros, leaving current operational gyros intact. This site contains good reference information about STA-125 and the Hubble EVA plans. Haven't read through it all yet, but of anyone else is looking to learn more, maybe this will interest you. I'm trying to grasp just how involved an EVA would be... https://www.nasa.gov/centers/johnson/news/flightdatafiles/foia_archive.html https://www.nasa.gov/centers/johnson/pdf/345766main_EVA_125_F_A.pdf
Isaacman: training schedule for Inspiration4 was six months. Looking at eight to nine months for Polaris Dawn.
Isaacman: if we can boost Hubble above altitude of Starlink constellation and “put some enhancements” on it, could operate for 20 more years. [Depends on what those enhancements are.]
Isaacman reiterates that any Hubble servicing could be done “at little or no cost” to taxpayers thanks to commercial space funding. “That’s all that should matter.” [It’ll be an interesting government procurement process, to be certain.]
Quote from: AstroWare on 10/03/2022 03:19 pmAnother thing I think we need to look at is Dragon on orbit endurance. Consumables, fuel, ECLSS... Especially when accounting for cabin depressurization. Dragon is shorter than Shuttle, but how much can it be expanded? Shuttle had a larger crew to spread workload around. Because it had an airlock, the non-eva crew was able to do more work than the non-eva crew in dragon will (I would think - they are basically in EVA too at that point)I think a boost mission would be a priority. Gyro replacement would be a bonus. So the mission would proceed something like: Launch, Dock, Boost, EVA(s), repress, undock, deorbit. First do no harm mentality - probably only replacing the failed gyros, leaving current operational gyros intact. This site contains good reference information about STA-125 and the Hubble EVA plans. Haven't read through it all yet, but of anyone else is looking to learn more, maybe this will interest you. I'm trying to grasp just how involved an EVA would be... https://www.nasa.gov/centers/johnson/news/flightdatafiles/foia_archive.html https://www.nasa.gov/centers/johnson/pdf/345766main_EVA_125_F_A.pdfThe Crew Dragon already carries enough air supply to repressurize the cabin in case of a full depressurization, so that's a non-issue. IIRC, nominally the Dragon only carries a few days worth of supplies. For example, the Inspiration 4 flight only lasted 3 days. The first Polaris Dawn mission is supposed to last 5 days. Presumably more internal storage space could be used for more supplies for longer duration flights, but IMO a 5 day flight should be more than sufficient for a Hubble reboost and one EVA for gyro replacement.