- Joined
- Aug 5, 2008
- Messages
- 4,261
- Reaction score
- 1
- Points
- 0
Will this improved ISS be released with SSU?
If it is, we may design scenarios only for that.
If it is, we may design scenarios only for that.
Will this improved ISS be released with SSU?
:lol:! Seems to me that the comm breakdown is on Pete's end, not yours. I find your previous reply very clear. Pete's on the other hand: :huh:OK. I am obviously not able to communicate today. :dry:
Urwumpe
if your code isnt very complicated i think i can add support of your ODS to pma and station.
So you need only docking port and attachment point?
"APAS9" - is it attacment point identifier string?
That's pretty much what I had in mind also. The ISS attachment point could be created at docking-time by SSU; this would let SSU dock to any other vessel without having to add new attachment points. During the retract sequence, we'll probably have to destroy the SSU docking port; otherwise, the shuttle will keep docking to the ISS.Currently, I am thinking about the following design, which means most of the magic happens inside the SSU module:
You have a docking port - logically.
At the same place, you have a child->parent attachment. Code for the attachment is "APAS9".
The Shuttle first attempts to attach to the attachment when docking. When the attachment is made, the "CAPTURE" light lights.
When the ring is retracted and the latches opened, the normal docking is done.
Undocking happens as usual unless you have closed latches.