Idea Shuttle Fleet recompile for Orbiter 2016

Last edited:
Hi Gattis - thanks again for all your work - you are like Santa in the spring!

On thing I'm trying to work on is STS-51A. I've got this working so far with your Spaceshuttle2016:
HTML:
BEGIN_DESC

END_DESC

BEGIN_ENVIRONMENT
  System Sol
  Date MJD 46013.9065899249
  Help CurrentState_img
END_ENVIRONMENT

BEGIN_FOCUS
  Ship STS-51A
END_FOCUS

BEGIN_CAMERA
  TARGET STS-51A
  MODE Extern
  POS 1.939150 137.171271 -25.529581
  TRACKMODE TargetRelative
  FOV 22.79
END_CAMERA

BEGIN_HUD
  TYPE Surface
END_HUD

BEGIN_MFD Left
  TYPE Map
  REF Earth
  TARGET Cape Canaveral
  ZOOM 2
  DISP 1711
END_MFD

BEGIN_SHIPS
STS-51A:Shuttle2016B
  STATUS Orbiting Earth
  RPOS -5348051.268 2869144.815 -2717988.146
  RVEL 3347.1382 -502.7406 -6982.2040
  AROT -174.722 -24.424 -117.854
  VROT -0.0668 0.0000 -0.0017
  AFCMODE 7
  PRPLEVEL 0:0.872410
  NAVFREQ 0 0
  UMMUCREW Ev2-Joe_Allen-47-70-70
  UMMUCREW Ev3-Dale_Gardner-36-70-70
  CONFIGURATION 3
  OV- 103
  ORIGINAL 
  RENDER 
  RMSARM 
  NOCHUTE 
  CARGODOOR 1 1.0000
  KUBAND 1 1.0000
  POSTLAND 0 0.0000
  SSMES 1 1.0000
  ADTA 0 0.0000
  PETD 0 0.0000
  SETD 1 1.0000
  ARMTILT 1 1.0000 1 1.0000
  PRADIATOR 1 1.0000
  SRADIATOR 0 0.0000
  GEAR 0 0.0000
  PAYLOAD_MASS1 3.0000
  PAYLOAD_MASS2 0.0000
  PAYLOAD_MASS3 0.0000
  ARM_STATUS 0.5000 0.0151 0.0162 0.5000 0.5000 0.5000
  PL1_OFS 0.000000 0.150000 7.500000
  PL1_DIR 0.000000 1.000000 0.000000
  PL1_ROT 0.000000 0.000000 1.000000
  PL2_OFS 0.000000 -0.800000 0.250000
  PL2_DIR 0.000000 1.000000 0.000000
  PL2_ROT 0.000000 0.000000 1.000000
  PL3_OFS 0.100000 0.500000 -6.500000
  PL3_DIR 0.000000 1.000000 0.000000
  PL3_ROT 1.000000 0.000000 0.000000
  PL4_OFS 0.000000 0.000000 3.250000
  PL4_DIR 0.000000 1.000000 0.000000
  PL4_ROT 0.000000 0.000000 1.000000
  PL5_OFS 0.000000 0.000000 0.250000
  PL5_DIR 0.000000 1.000000 0.000000
  PL5_ROT 0.000000 0.000000 1.000000
  PL6_OFS 0.000000 0.000000 7.250000
  PL6_DIR 0.000000 1.000000 0.000000
  PL6_ROT 0.000000 0.000000 1.000000
  KEEL_CAM 0.145000 -0.500000 -1.356000
  SPIN2 
  SPIN3 
  OMS 
  CALLOUT 
END
RETRIEVAL-PALLET:Pylon\PALLET
  STATUS Orbiting Earth
  RPOS -5348050.155 2869144.549 -2717990.261
  RVEL 3347.1382 -502.7406 -6982.2040
  AROT 133.319 53.612 44.185
  VROT 0.0668 -0.0017 0.0000
  ATTACHED 0:0,STS-51A
  AFCMODE 7
END
ABS:STS_PAYLOADS\ABS
  STATUS Orbiting Earth
  RPOS -5348049.827 2869144.442 -2717990.653
  RVEL 3347.1382 -502.7406 -6982.2040
  AROT 133.319 53.612 134.185
  VROT 0.0017 0.0668 0.0000
  ATTACHED 0:3,RETRIEVAL-PALLET
  AFCMODE 7
END
PFR:STS_PAYLOADS\PFR2
  STATUS Orbiting Earth
  RPOS -5348052.701 2869143.499 -2717990.024
  RVEL 3347.1382 -502.7406 -6982.2040
  AROT 82.952 -25.177 -62.814
  VROT -0.0017 0.0000 0.0668
  ATTACHED 0:9,RETRIEVAL-PALLET
  AFCMODE 7
END
MFR:STS_PAYLOADS\MFR
  STATUS Orbiting Earth
  RPOS -5348048.820 2869145.973 -2717993.479
  RVEL 3347.1382 -502.7406 -6982.2040
  AROT -46.681 -53.612 -134.185
  VROT 0.0017 -0.0668 -0.0000
  ATTACHED 0:12,RETRIEVAL-PALLET
  AFCMODE 7
END
STINGER:STS_PAYLOADS\STINGER
  STATUS Orbiting Earth
  RPOS -5348051.816 2869143.320 -2717990.883
  RVEL 3347.1382 -502.7406 -6982.2040
  AROT -46.681 -53.612 135.815
  VROT -0.0668 -0.0017 -0.0000
  ATTACHED 0:2,RETRIEVAL-PALLET
  AFCMODE 7
END
TELSTAR-3C-ASE:STS_PAYLOADS\ASE
  STATUS Orbiting Earth
  RPOS -5348051.298 2869144.831 -2717988.437
  RVEL 3347.1382 -502.7406 -6982.2040
  AROT 133.319 53.612 44.185
  VROT 0.0668 -0.0017 0.0000
  ATTACHED 0:5,STS-51A
  AFCMODE 7
END
ANIK-ASE-DOOR2:spacecraft\spacecraft3
  STATUS Orbiting Earth
  RPOS -5348051.837 2869145.121 -2717988.710
  RVEL 3347.1382 -502.7406 -6982.2040
  AROT 133.319 53.612 -135.815
  VROT -0.0668 0.0017 0.0000
  ATTACHED 0:0,TELSTAR-3C-ASE
  AFCMODE 7
  NAVFREQ 0 0
  RCS 1
  CTRL_SURFACE 1
  CONFIGURATION 1
  CURRENT_PAYLOAD 0
  SEQ 0 -2 0.000000
  SEQ 1 -2 0.000000
END
PAM-2:STS_PAYLOADS\PAM
  STATUS Orbiting Earth
  RPOS -5348050.520 2869144.448 -2717988.047
  RVEL 3347.1382 -502.7406 -6982.2040
  AROT 133.319 53.612 44.185
  VROT 0.0668 -0.0017 0.0000
  ATTACHED 0:2,STS-51A
  AFCMODE 7
  PRPLEVEL 0:1.000000
  NAVFREQ 0 0
END
STAR-48B2:STS_PAYLOADS\EQUIP
  STATUS Orbiting Earth
  RPOS -5348050.520 2869144.448 -2717988.047
  RVEL 3347.1382 -502.7406 -6982.2040
  AROT 133.319 53.612 44.185
  VROT 0.0668 -0.0017 0.0000
  ATTACHED 0:0,PAM-2
  AFCMODE 7
END
STAR-30B2:STS_PAYLOADS\STAR
  STATUS Orbiting Earth
  RPOS -5348050.520 2869144.448 -2717988.047
  RVEL 3347.1382 -502.7406 -6982.2040
  AROT 133.319 53.612 44.185
  VROT 0.0668 -0.0017 0.0000
  ATTACHED 0:0,STAR-48B2
  AFCMODE 7
END
ANIK-D2:STS_PAYLOADS\HS-376
  STATUS Orbiting Earth
  RPOS -5348052.356 2869145.432 -2717988.975
  RVEL 3347.1382 -502.7406 -6982.2040
  AROT 133.319 53.612 44.185
  VROT 0.0668 -0.0017 0.0000
  ATTACHED 0:0,STAR-30B2
  AFCMODE 7
  PRPLEVEL 0:1.000000
  NAVFREQ 0 0
  RCS 1
  CTRL_SURFACE 1
  CONFIGURATION 1
  CURRENT_PAYLOAD 0
  SEQ 0 -2 0.000000
  SEQ 1 -2 0.000000
END
LEASAT-2-ASE:STS_PAYLOADS\ASE3
  STATUS Orbiting Earth
  RPOS -5348048.363 2869143.976 -2717993.306
  RVEL 3347.1382 -502.7406 -6982.2040
  AROT 133.319 53.612 44.185
  VROT 0.0668 -0.0017 0.0000
  ATTACHED 0:6,STS-51A
  AFCMODE 7
END
ORBUS-7S:STS_PAYLOADS\APC
  STATUS Orbiting Earth
  RPOS -5348054.400 2869145.485 -2717982.467
  RVEL 3347.1382 -502.7406 -6982.2040
  AROT -174.722 -24.424 -117.854
  VROT -0.0668 0.0000 -0.0017
  ATTACHED 0:3,STS-51A
  AFCMODE 7
  PRPLEVEL 0:1.000000
  NAVFREQ 0 0
END
PKM:STS_PAYLOADS\pylonPKM
  STATUS Orbiting Earth
  RPOS -5348054.070 2869145.418 -2717983.193
  RVEL 3347.1382 -502.7406 -6982.2040
  AROT -174.722 -24.424 -117.854
  VROT -0.0668 0.0000 -0.0017
  ATTACHED 0:0,ORBUS-7S
  AFCMODE 7
END
R-4D-10:STS_PAYLOADS\STAR
  STATUS Orbiting Earth
  RPOS -5348053.367 2869145.276 -2717984.734
  RVEL 3347.1382 -502.7406 -6982.2040
  AROT -174.722 -24.424 -117.854
  VROT -0.0668 0.0000 -0.0017
  ATTACHED 0:0,PKM
  AFCMODE 7
END
Leasat-2:STS_PAYLOADS\LEASAT
  STATUS Orbiting Earth
  RPOS -5348053.367 2869145.276 -2717984.734
  RVEL 3347.1382 -502.7406 -6982.2040
  AROT -174.722 -24.424 -162.854
  VROT -0.0471 0.0471 -0.0017
  ATTACHED 0:0,R-4D-10
  AFCMODE 7
  PRPLEVEL 0:1.000000
  NAVFREQ 0 0
  RCS 1
  CTRL_SURFACE 1
  CONFIGURATION 1
  CURRENT_PAYLOAD 0
  SEQ 0 -2 0.000000
  SEQ 1 -2 0.000000
END
LEASAT-2-OnmiAntenna:STS_PAYLOADS\Onmi-Antenna
  STATUS Orbiting Earth
  RPOS -5348052.349 2869145.070 -2717986.964
  RVEL 3347.1382 -502.7406 -6982.2040
  AROT -174.722 -24.424 -162.854
  VROT -0.0471 0.0471 -0.0017
  ATTACHED 0:0,Leasat-2
  AFCMODE 7
END
PALAPA-B2-R:STS_PAYLOADS\HS-376
  STATUS Orbiting Earth
  RPOS 5658312.333 -2931156.243 2172870.141
  RVEL -2689.2001 165.4510 7213.1396
  AROT -174.820 -27.130 -115.434
  VROT 0.0000 0.0000 -6.0000
  AFCMODE 7
  NAVFREQ 0 0
  RCS 1
  CTRL_SURFACE 1
  CONFIGURATION 1
  CURRENT_PAYLOAD 0
END
PALAPA-ONMI:STS_PAYLOADS\Onmi-Antenna
  STATUS Orbiting Earth
  RPOS 5658312.848 -2931156.334 2172869.139
  RVEL -2689.2001 165.4510 7213.1396
  AROT -174.820 -27.130 -115.434
  VROT 0.0000 0.0000 -6.0000
  ATTACHED 0:0,PALAPA-B2-R
  AFCMODE 7
END
WESTAR-VI-R:STS_PAYLOADS\HS-376
  STATUS Orbiting Earth
  RPOS 5137591.208 -2856166.078 3277555.901
  RVEL -3817.6038 769.5570 6645.8092
  AROT -174.820 -27.130 -115.434
  VROT 0.0000 0.0000 -6.0000
  AFCMODE 7
  NAVFREQ 0 0
  RCS 1
  CTRL_SURFACE 1
  CONFIGURATION 1
  CURRENT_PAYLOAD 0
END
WESTAR-ONMI:STS_PAYLOADS\Onmi-Antenna
  STATUS Orbiting Earth
  RPOS 5137591.724 -2856166.169 3277554.899
  RVEL -3817.6038 769.5570 6645.8092
  AROT -174.820 -27.130 -115.434
  VROT 0.0000 0.0000 -6.0000
  ATTACHED 0:0,WESTAR-VI-R
  AFCMODE 7
END
END_SHIPS

But I can't get the errant satellites to dock or to grapple them. The files are from the original STS payloads you found - [ame="https://www.orbithangar.com/searchid.php?ID=2481"]STS PAYLOADS v.2.01[/ame] - on the wayback machine.

Just wondering on your ideas.

Many thanks - MH
 
Thanks. So can't grapple the sats with rms? Or something else. I don't think they can be docked
 
Yes - they can't be grappled or "docked" to the pallet / EVA astronaut. I guess, what I'm wondering is if the mission is doable - as in recapturing the errant sattelites and returning them to earth as in the real mission.

Thanks - just asking.
 
So those are operated via PLyon.

anDkFRF.jpg


AKB0QOb.jpg

sceeMts.jpg

grV97W0.jpg


Code:
It's activated with shift-P

The MFD shows what vessel is selected, his parent, and the selected attachment (and sub-vessel if there is one)
You can change the view between attachments with shift-Q and shift-A. You can select the parent (go up) with shift-W and the sub-vessel (go down) with shift-S.
You can attach, release, create and destroy sub-vessels in the selected attachment.

Also if the sub-vessel is a Pylon, you can set, increment and decrement the selected parameter (shift-V, shift-N, shift-B). The meaning of each operation depends on the Pylon module. You select different parameters with shift-Z and shift-X. If you pass off the number of parameters you will select a sequence, if there is any. Sequences are executed with shift-N and cancelled with shift-B.

If the selected vessel is a pylon, you can also select beyond its attachments (with Q or A) and access to its own parameters ans sequences.

Keys:

W: Go up in the structure of attachments.
S: Go down through the selected attachment in the structure of attachments.
Q: Select previous attachment
A: Select next attachment
C: Create an object in a free attachment. Vessel name and class (vessel:class) is queried
R: Release vessel in the attachment. Release velocity is queried.
D: Destroy object in attachment. Confirmation is queried.
T: Attach an existing vessel to the selected attachment. Name of the vessel is queried. (In future versions this will be replaced by a more realistic reattach operation)

Z: Select previous pylon parameter / sequence
X: Select next pylon parameter / sequence
N: Increment parameter/execute sequence
B: Decrement parameter/cancel sequence
V: Set parameter value (value is queried)

F: Change focus to the selected vessel

This is what I have for pylon
https://drive.google.com/open?id=1Tj7NZmK4LvGPuEHwwrsqD1ctnpLHxHgz

So did this work in 2010/2006? I am not sure how it was to work?


https://historycollection.jsc.nasa.gov/JSCHistoryPortal/history/shuttle_pk/pk/Flight_014_STS-51A_Press_Kit.pdf

So we need an eva guy to grap the satellite grap device.

---------- Post added 05-16-19 at 04:39 AM ---------- Previous post was 05-15-19 at 04:42 AM ----------

So Pylon basically moves. interacts with the attachment points. So for sts51A to work you need a way to attach the stinger to the mmu, stinger to sat. RMS to stinger,......

tg2OBty.jpg
mmu to stinger
E9sNA4W.jpg


But when I attached the rms to the stinger the MMU became detach:(
 
Last edited:
That's probably okay since your astronaut can go put the A frame on top. And I could be wrong but I don't think it worked in 2010 (at least, I never got it to).
 
Last edited:
Ok. I played around some with Plyon. I could get it to read the attachments, I could release. But that was it.

So what if we bypass pylon altogether and use VB! or sc3.

It looks like a llot of work aka reality. So you eva guy out. you attach an mmu you get the stinger and attach. Fly to the sat and attach it and then use the rms to attach and bring it to the bay,

So what if I made a new eva guy no MMU a little rcs for movement. I would use the Donamy's mesh that is the same as the HST_ex guys.

then either make an attachment for the MMu or press a key and the MMu appears?

Right now the shuttle has only 1 eva guy. So I may make a window foe eva. Allow 4 eva guys?
 
So 3 eva guys. It might be nice to read the name from the scn and name the evaguy that. But that maybe too much.

Let me get a eva vessel working. Donamy guy has a lot of joints. I may make a window for that?
 
Well I can get the mmu to grap the stinger. And the stinger to grap the sat.
hEmzJcF.jpg

BUT when I attach the rms to the stinger the mmu does not come it?
Code:
MMUNEW:SHUTTLEMMUNEW
  STATUS Orbiting Earth
  RPOS 4383970.507 -1302691.528 -4804007.624
  RVEL 4895.3436 -3027.0971 5230.7190
  AROT -104.897 -63.943 -174.169
  VROT -0.0827 0.0000 -0.0023
  RCSMODE 2
  AFCMODE 7
  PRPLEVEL 0:0.996799
  NAVFREQ 0 0
  GUY 1 
END
STINGER1:STINGER
  STATUS Orbiting Earth
  RPOS 4383971.736 -1302692.460 -4804007.533
  RVEL 4895.3436 -3027.0971 5230.7190
  AROT -104.897 -63.943 -174.169
  VROT -0.0827 0.0000 -0.0023
  ATTACHED 0:0,MMUNEW
  AFCMODE 7
  NAVFREQ 0 0
END
Code:
PALAPA-B2-R:STS_PAYLOADS\HS-376
  STATUS Orbiting Earth
  RPOS 4383973.193 -1302692.896 -4804007.674
  RVEL 4895.3436 -3027.0971 5230.7190
  AROT -104.897 -63.943 -84.169
  VROT -0.0000 -0.0827 -0.0023
  ATTACHED 1:0,STINGER1
  AFCMODE 7
  NAVFREQ 0 0
  RCS 1
  CTRL_SURFACE 1
  CONFIGURATION 1
  CURRENT_PAYLOAD 0
END
Code:
; === Configuration file for vessel class Adapter ===
ClassName = STINGER
Module = STINGER

BEGIN_ATTACHMENT
P -0.28 -0.20 -0.64  0 0 1  0 1 0 XS ;TO PAYLOAD BAY/MMU
P .526 -0 -0.281  0 1 0  1 0 0 GS ;rms TO SATELLITE
END_ATTACHMENT
RC3d4Nf.jpg


after rms attach:
Code:
PALAPA-B2-R:STS_PAYLOADS\HS-376
  STATUS Orbiting Earth
  RPOS 5299082.874 -1913818.583 -3519181.129
  RVEL 3447.5060 -2543.6208 6476.7658
  AROT -73.878 -61.978 -112.488
  ATTACHED 1:0,STINGER1
  AFCMODE 7
  NAVFREQ 0 0
  RCS 1
  CTRL_SURFACE 1
  CONFIGURATION 1
  CURRENT_PAYLOAD 0
END
MMUNEW:SHUTTLEMMUNEW
  STATUS Orbiting Earth
  RPOS 5299203.223 -1913842.773 -3519475.216
  RVEL 3447.8047 -2543.6988 6476.3610
  AROT -63.616 -59.282 148.584
  VROT -0.0987 0.0000 -0.0027
  RCSMODE 2
  AFCMODE 7
  PRPLEVEL 0:0.996799
  NAVFREQ 0 0
  GUY 1 
END
STINGER1:STINGER
  STATUS Orbiting Earth
  RPOS 5299081.441 -1913818.107 -3519181.358
  RVEL 3447.5060 -2543.6208 6476.7658
  AROT -73.878 -61.978 157.512
  ATTACHED 1:1,STS-51A
  AFCMODE 7
  NAVFREQ 0 0
END


now the mmu guy isn't attached to anything?
 
So try this for the HST_ex. On all these updates I try to put into different folders so SF or payloads remains the same.
https://drive.google.com/open?id=18L5Rtl_tSpUEfTxjkD1115Wcvlf2FffO

So on the guidance. First I am not a shuttle guy. so the guidance files may need to be looked at.

So should the basic shuttle guidance just be the orbit,main engine start,inverse in all and then jettison(MECO)?
oGGlTOO.jpg


I didn't see the reverse command.

---------- Post added at 05:31 AM ---------- Previous post was at 04:49 AM ----------

So from the press kit. I did notice the MECo aka Jettison time is way wrong.

But what should the guidance file look like?
dSxB05M.jpg

UPGYubj.jpg

Hello "gattispilot"
So for STS-31 can you correct the position of HST in the cargo hold:
It is located closer to the cockpit of the Shuttle.




Now concerning the file "GUIDANCE" below the result of my tests:

In reality the Shuttle had to finish the circularization of its orbit with the engines of the OMS.
In the case of STS-31 the orbit reached after MECO and the ET drop is 325 x 27 Km.





Thanks to OMS the final orbit achieved by DISCOVERY was 330 x310 Km (the highest reached by a Shuttle).

With the "GUIDANCE" file referenced "ET", the autopilot (MultiStage2015) is disabled when "ET" is dropped.

So we have to finalize our orbit in manual ...
Where to cheat a little bit with the file "GUIDANCE" is to give him directly the final orbit to reach: 330 x 310.
 
Last edited:
You have to make the stinger, the parent to both the satellite and EMUguy. Or make the RMS grapple a "dummy" attachment on the EVAguy, that lines up with the Grapple fixture of the stinger.
 
You have to make the stinger, the parent to both the satellite and EMUguy. Or make the RMS grapple a "dummy" attachment on the EVAguy, that lines up with the Grapple fixture of the stinger.
Thanks. but that mean the mmu couldn't grap the stinger. So I will try the dummy attachment.


On the HST
https://drive.google.com/open?id=1jRZNN_XXEjnKn51L2eX3pkf-w51bwlhw


PzFBhZr.jpg



So on the guidance I have this:
Code:
-30.000 =orbit(601.9,574.12,28.45,-1)
-6.0 =engine(0,100,6)
3.0 =engine(100,100,1.00)
30.0 =engine(100,72.00,5.00)
55.0 =engine(72.0,100,5.00)
120.0 =inverse()
531.0=jettison()


One thing to remember the orbit in the press kits is in n.m. (nautical miles) and ms2015 is in KM. this should be 325 x 310 nm


I also fixed the ini for sts61 it had the wrong shuttle mesh
 
Last edited:
Hello "gattispilot"
For STS-31 It would be necessary to modify the line of the file "GUIDANCE", because the value of the time in seconds is not correct, the reversal of the Shuttle took place with T + 4 mn 6 sec = 246



For STS-61
We must add the line:
246.0 = inverse ()
I did not find the details of the flight of STS-61 with the exact time of the turnaround of the Shuttle, but the phase takes place is almost in the same period I suppose.



Concerning the STS-31 scenario, you must modify the line concerning the .ini file




HST is in place now
thanks again
 
Wait, but if this "inverse" is about "roll to heads up" it did not happen until around 1997...
 
Back
Top