Discussion Space Shuttle Vessel - Payload Development Thread

so if the MMU is parent to the Stinger, the RMS cant grapple to be parent to the Stinger as well? could the Stinger be the parent object instead?
The RMS (actually the OV) has to be the parent, so it can move the child around.
 
so is this kind of setup just not possible with how Orbiter attachment points function?
Thinking about it, I'd say no... :(
We need an attachment system that retains the existing attachment behavior, but does away with the parent-child relationship and replaces it with the mated vessel physics that is used in docked vessels. This way, we could have the MMU and the RMS attached to the Stinger, and it attached to the HS-376 at the same time, and if either the MMU or the sat started firing thrusters, the whole thing would start spinning (sorry, no RMS dynamics).
 
MFR. I know most grapple fixture have targets. But it looks like the MFR doesn't? It looks like for STS41c the MFR was all white? so what should the alignment be?
 

Attachments

  • NASM-A20130045000cp02.jpg
    NASM-A20130045000cp02.jpg
    86.6 KB · Views: 13
  • NASM-A20130045000-NASM2014-05423-000001.jpg
    NASM-A20130045000-NASM2014-05423-000001.jpg
    23.1 KB · Views: 13
  • sts41cmfr.jpg
    sts41cmfr.jpg
    61.5 KB · Views: 13
Can we define custom payload latch positions like the cameras, or could that be implemented in the future?
Hmm, in the sills or keel? The existing positions were fixed, and the payloads had to adapt to them. 🤷‍♂️
If you mean the attachment of a SPARTAN or others, I haven't done anything for that as I simply don't know how that was operated... plus, the base is another vessel, so that means that actually the OV should (somehow) connect to that vessel to command the latches, and all the attachment business, animation, etc, should be handled by that base vessel. In addition to this, there would have to be the cooperation between vessels to allow the attachment hand-off.
 
any idea why a payload vessel would spawn in with NaNs for the position in the scenario when its installed in the payload bay?
What is the attachment configuration: is it attached to anything else? Parent, child?
 
nope. just setup as an active payload in the mission editor. attached to the keel with 1 latch (for testing right now). i can spawn the vessel in just fine with scenario editor.
Is the attachment ID in the PL edit dialog valid? Are the attachments "manipulated" by the vessel, i.e., created or deleted other than at the vessel creation?
 
does anyone have a good source for PAM deploy procedures? I'm aware flights that used them had checklists, but none are available online from my looking.
Without the GPC, SCA, etc, it comes down to this:
1) close sunshields once in orbit
2) once time comes to deploy, point vehicle +Zo -VV
3) open sunshields
4) unlatch PAM
5) spin up PAM
6) when crossing the equator, deploy PAM
7) move away
8) 45 minutes later watch it fire from a safe distance
 
whenever the time is right for the DPS Pages for payloads, this looks like a good reference for them: https://edan.si.edu/slideshow/viewer/?eadrefid=NASM.2014.0025_ref156
If only it were as simple as making the displays... there's at least one process behind each of those SPECs, that needs to get data from and send command to a box connected to bus PL-1 and/or 2, and that is where the payload interfaces. Plus, you might also have the Standard Switch Panel for certain commands, and backups.
The PAMs will need most of this, so that will open the way. Not that this is easy, but the thing I'm most concerned about is: how to configure all of this???
 
If only it were as simple as making the displays... there's at least one process behind each of those SPECs, that needs to get data from and send command to a box connected to bus PL-1 and/or 2, and that is where the payload interfaces. Plus, you might also have the Standard Switch Panel for certain commands, and backups.
The PAMs will need most of this, so that will open the way. Not that this is easy, but the thing I'm most concerned about is: how to configure all of this???
configure as in how to determine when it is allowed to display what DPS pages depending on the payloads?
 
configure as in how to determine when it is allowed to display what DPS pages depending on the payloads?
Yes, plus which code to run, connected to where, which SSP to show, where, connected to where... the Shuttle had so many options, that it's like lego for engineers.
 
Back
Top