Payload Interface

Urwumpe

Not funny anymore
Addon Developer
Donator
Joined
Feb 6, 2008
Messages
37,588
Reaction score
2,312
Points
203
Location
Wolfsburg
Preferred Pronouns
Sire
How's the work with including the payload retention latch mechanism panel meshes going? Also, any A6U work ongoing with respect to the payload interface?

No work yet, I also have no system yet for the ready to latch indicators. I think adding some information into the configuration file for payloads might make sense for allowing this to work.
 

DaveS

Addon Developer
Addon Developer
Donator
Beta Tester
Joined
Feb 4, 2008
Messages
9,429
Reaction score
680
Points
203
No work yet, I also have no system yet for the ready to latch indicators. I think adding some information into the configuration file for payloads might make sense for allowing this to work.
Yes. Well, all it really needs to know is where to add the payload retention panel meshes and the keel pin retention latches.
 

Urwumpe

Not funny anymore
Addon Developer
Donator
Joined
Feb 6, 2008
Messages
37,588
Reaction score
2,312
Points
203
Location
Wolfsburg
Preferred Pronouns
Sire
Yes. Well, all it really needs to know is where to add the payload retention panel meshes and the keel pin retention latches.

That is what we need to know inside the SSU. But for the ready to latch indicators, we need to know where the other trunnions of the payload are. I currently assume the keel trunnion is the position of the attachment, but I would need 2 or 4 other coordinates for indicating correctly if the payload is correctly aligned.
 

DaveS

Addon Developer
Addon Developer
Donator
Beta Tester
Joined
Feb 4, 2008
Messages
9,429
Reaction score
680
Points
203
That is what we need to know inside the SSU. But for the ready to latch indicators, we need to know where the other trunnions of the payload are. I currently assume the keel trunnion is the position of the attachment, but I would need 2 or 4 other coordinates for indicating correctly if the payload is correctly aligned.
Well, to keep it simple, we could just make it three values like this:

Code:
SSU_RTL_POS = stb_trunnions port_trunnions keel_pin
where the trunnion locations on each side are combined to form a common POS for the sake of simplicity.
 

Urwumpe

Not funny anymore
Addon Developer
Donator
Joined
Feb 6, 2008
Messages
37,588
Reaction score
2,312
Points
203
Location
Wolfsburg
Preferred Pronouns
Sire
Well, to keep it simple, we could just make it three values like this:

Code:
SSU_RTL_POS = stb_trunnions port_trunnions keel_pin
where the trunnion locations on each side are combined to form a common POS for the sake of simplicity.

I thought about using a single line but with a different format:

Code:
PRL = type attachment-id pos1 (pos2)

The keel trunnion is always the attachment point. So, when the type is known, we only need maximal two additional coordinates for the offset in the X-axis relative to the attachment coordinate system.

The other two coordinates per latch can be calculated by the keel trunnion.
 
Last edited:

DaveS

Addon Developer
Addon Developer
Donator
Beta Tester
Joined
Feb 4, 2008
Messages
9,429
Reaction score
680
Points
203
The keel trunnion is always the attachment point.
Well, not always. The Lightweight MPESS Carrier(LMC) that flew on STS-114 and STS-121 is a good example of this. It made only use of trunnions with no keel pins.
 

Urwumpe

Not funny anymore
Addon Developer
Donator
Joined
Feb 6, 2008
Messages
37,588
Reaction score
2,312
Points
203
Location
Wolfsburg
Preferred Pronouns
Sire
Well, not always. The Lightweight MPESS Carrier(LMC) that flew on STS-114 and STS-121 is a good example of this. It made only use of trunnions with no keel pins.

Yes, but in that case, we would still have the invisible attachment as reference.
 

DaveS

Addon Developer
Addon Developer
Donator
Beta Tester
Joined
Feb 4, 2008
Messages
9,429
Reaction score
680
Points
203
Got some trouble attaching payloads here. Could someone take a look on the code below and see if I have made any errors?

Scenario:
Code:
BEGIN_DESC
Launch of STS-107 occurs in 39 minutes at 15:39:00 GMT, 16 January 2003. 
Payloads:
-SpaceHAB Research Double Module(SHRDM)
-Fast Reaction Experiments Enabling Science, Technology Applications and 
Research(FREESTAR)
-Extended Duration Orbiter(EDO) cryogenic kit supplying additional LH2 and LOX 
for the fuel cells to enable 16 day mission
END_DESC
 
BEGIN_ENVIRONMENT
  System Sol
  Date MJD 52655.6250027778
END_ENVIRONMENT
 
BEGIN_FOCUS
  Ship STS-107
END_FOCUS
 
BEGIN_CAMERA
  TARGET STS-107
  MODE Extern
  POS 4.00 -13.46 39.16
  TRACKMODE GlobalFrame
  FOV 50.00
END_CAMERA
 
BEGIN_HUD
  TYPE Surface
END_HUD
 
BEGIN_MFD Left
  TYPE Map
  REF Earth
  BTARGET Cape Canaveral
END_MFD
 
BEGIN_MFD Right
  TYPE Orbit
  PROJ Ship
  REF Earth
END_MFD
 
BEGIN_SHIPS
STS-107:SpaceShuttleUltra
  STATUS Landed Earth
  POS -80.6232502 28.6197342
  HEADING 0.00
  ATTACHED 0:0,MLP
  PRPLEVEL 0:1.000 1:1.000 2:1.000 3:1.000 4:1.000 5:1.000 6:1.000 7:1.000 
8:0.999
  NAVFREQ 0 0
  CONFIGURATION 0
  MET 0.000
  WING_NAME Columbia
  ARM_STATUS 0.500000 0.013600 0.014688 0.500000 0.500000 0.500000
  ROLLOUT 0 0.000000
  CARGODOOR 0 0.0000
  BAYDOORLATCH0 0 0.0000
  BAYDOORLATCH1 0 0.0000
  BAYDOORLATCH2 0 0.0000
  BAYDOORLATCH3 0 0.0000
  SHOULDER_BRACE 0.000
  MRL 1.000000 1.000000
  GRAPPLE 1 1.0000
  RIGIDIZE 1 1.0000
  EXTEND 1 1.0000
   PAYLOAD CACTIVE1 8.000000 0.000000 0
   PAYLOAD CACTIVE2 0.000000 0.000000 0
   PAYLOAD CACTIVE3 -8.000000 0.000000 0
   PAYLOAD CPASSIVE1 4.000000 0.000000 0
   PAYLOAD CPASSIVE2 2.000000 0.000000 0
   PAYLOAD CPASSIVE3 -6.000000 0.000000 0
   PAYLOAD CPASSIVE4 7.000000 0.000000 0
   PAYLOAD PORT1 3.000000 0.000000 0
   PAYLOAD PORT2 -2.000000 0.000000 0
   PAYLOAD PORT3 -8.000000 0.000000 0
   PAYLOAD PORT4 7.000000 0.000000 0
   PAYLOAD STBD1 3.000000 0.000000 0
   PAYLOAD STBD2 -2.000000 0.000000 0
   PAYLOAD STBD3 -8.000000 0.000000 0
   PAYLOAD STBD4 0.000000 0.000000 0
  OPS 101
  AUTOPILOT 39.000000 80.500000 105000.000000 7607.601000 0.730000
  ASSIST 133.000000 298.000000
  THROTTLE_BUCKET 1789.0 2094.0 
  HEADS_UP 13214.0
  TGT_ID 2
  BODY_VECT 1
  ROLL 0.000
  PITCH 0.000
  YAW 0.000
  P 0.000
  Y 0.000
  OM -1.000
  GEAR 0 0.0000
  STBD_RMS 1
  EE MODE 1
  CRT_SEL 1 1
  LPROBEARM 1
  LPROBE 2
  RPROBEARM 1
  RPROBE 2
  LOMS 1
  ROMS 1
  AIR_DATA_PROBES 0.000000 0.000000
  BOILERN2SPLY0 0
  BOILERN2SPLY1 0
  BOILERN2SPLY2 0
  BOILERCNTLR0 0
  BOILERCNTLR1 0
  BOILERCNTLR2 0
  BOILERHTR0 0
  BOILERHTR1 0
  BOILERHTR2 0
  APUFUTKVLV0 1
  APUFUTKVLV1 1
  APUFUTKVLV2 1
  APUCNTLRPWR0 1
  APUCNTLRPWR1 1
  APUCNTLRPWR2 1
  HYDCIRCPUMP0 1
  HYDCIRCPUMP1 1
  HYDCIRCPUMP2 1
  APUAUTOSHTDN 0
  APUSPDSEL0 1
  APUSPDSEL1 1
  APUSPDSEL2 1
  APUCNTRL0 1
  APUCNTRL1 1
  APUCNTRL2 1
  HYDMNPMPPRESS0 0
  HYDMNPMPPRESS1 0
  HYDMNPMPPRESS2 0
  MPSENGPWR00 0
  MPSENGPWR01 0
  MPSENGPWR02 0
  MPSENGPWR10 0
  MPSENGPWR11 0
  MPSENGPWR12 0
  HEISOLA0 0
  HEISOLA1 0
  HEISOLA2 0
  HEISOLB0 0
  HEISOLB1 0
  HEISOLB2 0
  APU0 0
  APU1 0
  APU2 0
  HYDRAULIC_PRESS0 0
  HYDRAULIC_PRESS1 0
  HYDRAULIC_PRESS2 0
  FUEL_PRESS0 0
  FUEL_PRESS1 0
  FUEL_PRESS2 0
  MPS0 1
  MPS1 1
  MPS2 1
  L_ET_UMB_DOOR 1.000
  R_ET_UMB_DOOR 1.000
  ET_DOOR_LATCHES 0.000000 1.000000 1.000000
  MTU_MET_RUNNING 0
  MTU_MET0 0.000
  MTU_MET1 0.000
  MTU_MET2 0.000
   EVENT_TIMER0 540.000000 DOWN STOPPED
   EVENT_TIMER1 0.000000 DOWN STOPPED
END
MLP:Atlantis_MLP
  STATUS Landed Earth
  POS -80.6040620 28.6083832
  HEADING 0.00
  NAVFREQ 0 0
END¨
SpaceHAB:SpaceHAB_RDM
  STATUS Orbiting Earth
  ATTACHED 0:8,STS-107
END
FREESTAR:MPESS_FREESTAR
  STATUS Orbiting Earth
  ATTACHED 0:9,STS-107
END
EDO_cryokit:EDO_cryokit
  STATUS Orbiting Earth
  ATTACHED 0:10,STS-107
END
END_SHIPS

SpaceHAB_RDM.cfg:
Code:
;===Configuration file for SpaceHAB Research Double Module===
Meshname = SpaceHAB_RDM
Size = 12
Mass = 9300 ; Best estimate of RDM mass I could find.
EnableFocus = TRUE
 
; === Attachment specs ===
BEGIN_ATTACHMENT
P 0 0 0    0 -1 0  0 0 1 XS
END_ATTACHMENT

MPESS_FREESTAR.cfg:
Code:
;===Configuration file for MPESS FREESTAR===
Meshname = MPESS_FREESTAR
Size = 12
Mass = 2000 ; Best estimate of FREESTAR mass I could find
EnableFocus = TRUE
 
; === Attachment specs ===
BEGIN_ATTACHMENT
P 0 0 0    0 -1 0  0 0 1 XS
END_ATTACHMENT

EDO_cryokit.cfg:
Code:
;===Configuration file for EDO cryo kit===
Meshname = EDO_cryokit
Size = 12
Mass = 3200 ; Best estimate of the EDO cryokit mass I could find
EnableFocus = TRUE
 
; === Attachment specs ===
BEGIN_ATTACHMENT
P 0 0 0    0 -1 0  0 0 1 XS
END_ATTACHMENT
 

DaveS

Addon Developer
Addon Developer
Donator
Beta Tester
Joined
Feb 4, 2008
Messages
9,429
Reaction score
680
Points
203
OK, anything? I have tried over and over, but just cannot get a good attachment.
 

Urwumpe

Not funny anymore
Addon Developer
Donator
Joined
Feb 6, 2008
Messages
37,588
Reaction score
2,312
Points
203
Location
Wolfsburg
Preferred Pronouns
Sire
Could you include the scenario and meshes into the SVN, my first guesstimate is, that the position of the attachment points on the payload is wrong, as it uses CoG of the payload. Also, the coordinate system could be wrong.

What is the error description, BTW?
 

DaveS

Addon Developer
Addon Developer
Donator
Beta Tester
Joined
Feb 4, 2008
Messages
9,429
Reaction score
680
Points
203
Could you include the scenario and meshes into the SVN, my first guesstimate is, that the position of the attachment points on the payload is wrong, as it uses CoG of the payload. Also, the coordinate system could be wrong.

What is the error description, BTW?
Error description:
Scenario starts with MLP+Shuttle in heliospherical orbit. Problem goes away when the payloads are removed. Then tje ML+Shuttle is back at 39A where it supposed to be.

Scenario and meshes are going in.
 

DaveS

Addon Developer
Addon Developer
Donator
Beta Tester
Joined
Feb 4, 2008
Messages
9,429
Reaction score
680
Points
203
Things checked in.
 

Urwumpe

Not funny anymore
Addon Developer
Donator
Joined
Feb 6, 2008
Messages
37,588
Reaction score
2,312
Points
203
Location
Wolfsburg
Preferred Pronouns
Sire
Things checked in.

Fixed the scenario without the payloads - you have the MLP, which is parent of the SSU, after the SSU in the scenario file, this can't work of course.

EDIT: Spacehab_RDM.cfg file was missing
 

DaveS

Addon Developer
Addon Developer
Donator
Beta Tester
Joined
Feb 4, 2008
Messages
9,429
Reaction score
680
Points
203
Works fine now, thanks for the help. But here's an observation: the payloads were aligned good.

But when I exited the sim and then re-entered it through the (Current state) scenario, all the payloads were above and behind the payload bay! I have attached a screenshot of this error.
 

Attachments

  • SSU_PL_error.jpg
    SSU_PL_error.jpg
    125.9 KB · Views: 519

Urwumpe

Not funny anymore
Addon Developer
Donator
Joined
Feb 6, 2008
Messages
37,588
Reaction score
2,312
Points
203
Location
Wolfsburg
Preferred Pronouns
Sire
Works fine now, thanks for the help. But here's an observation: the payloads were aligned good.

But when I exited the sim and then re-entered it through the (Current state) scenario, all the payloads were above and behind the payload bay! I have attached a screenshot of this error.

As they appear to be looking correctly relative to each other otherwise, I will investigate where this change in position comes from. Maybe our offset variable is broken at a point.

BTW, what do you think about making the EDO-pallet a part of the SSU, like the ODS? Would make the implementation of the EPS simpler.
 

DaveS

Addon Developer
Addon Developer
Donator
Beta Tester
Joined
Feb 4, 2008
Messages
9,429
Reaction score
680
Points
203
BTW, what do you think about making the EDO-pallet a part of the SSU, like the ODS? Would make the implementation of the EPS simpler.
Sure. Maybe we could then bring 102 into the fleet, at least the post-2001 version of her as she was the prime EDO orbiter. Endeavour was the other and she even had support for the LDO version, which had PRSD tanks on both sides of the main EDO structure.
 

Urwumpe

Not funny anymore
Addon Developer
Donator
Joined
Feb 6, 2008
Messages
37,588
Reaction score
2,312
Points
203
Location
Wolfsburg
Preferred Pronouns
Sire
Sure. Maybe we could then bring 102 into the fleet, at least the post-2001 version of her as she was the prime EDO orbiter. Endeavour was the other and she even had support for the LDO version, which had PRSD tanks on both sides of the main EDO structure.

Right. For some other orbiters, we might need Panel A11 as optional panel, I have it here in the Post-Insertion checklist for OV103. It contains the "CRYO TANK 4 HEATERS" switches.
 

DaveS

Addon Developer
Addon Developer
Donator
Beta Tester
Joined
Feb 4, 2008
Messages
9,429
Reaction score
680
Points
203
Right. For some other orbiters, we might need Panel A11 as optional panel, I have it here in the Post-Insertion checklist for OV103. It contains the "CRYO TANK 4 HEATERS" switches.
Are you sure the panel diagram is for OV-103? The only EDO orbiters was OV-102 and OV-105. During the construction of OV-104, Rockwell did offer NASA to perform the EDO mods to her, but NASA declined the offer which left OV-102 the only EDO orbiter until the introduction of OV-105.
 

Urwumpe

Not funny anymore
Addon Developer
Donator
Joined
Feb 6, 2008
Messages
37,588
Reaction score
2,312
Points
203
Location
Wolfsburg
Preferred Pronouns
Sire
Are you sure the panel diagram is for OV-103? The only EDO orbiters was OV-102 and OV-105. During the construction of OV-104, Rockwell did offer NASA to perform the EDO mods to her, but NASA declined the offer which left OV-102 the only EDO orbiter until the introduction of OV-105.

I am sure it is for OV-103, but I am not sure if it is for the EDO, pallet. Is tank 4 already EDO or does Tank 4 still belong to the number of tanks which fit into the orbiter mid structure?
 

DaveS

Addon Developer
Addon Developer
Donator
Beta Tester
Joined
Feb 4, 2008
Messages
9,429
Reaction score
680
Points
203
I am sure it is for OV-103, but I am not sure if it is for the EDO, pallet. Is tank 4 already EDO or does Tank 4 still belong to the number of tanks which fit into the orbiter mid structure?
According to the EPS chapter of the SCOM, all orbiters can carry up to 5 nominal cryo tank sets, while OV-102 and OV-105 supports 4 additional tanks on the EDO pallet.
 
Top