SSU Development thread (4.0 to 5.0)

GLS

Addon Developer
Addon Developer
Joined
Mar 22, 2008
Messages
4,212
Reaction score
352
Points
108
I corrected that (space deleted) and erased all the old parameters but with no luck.
Deleting the parameters isn't enough, as they most likely moved somewhere else.
I'll run the STS-131 scenario and get it to work. One thing I spotted already is the "Ultra_OBSS" isn't SC3 (anymore) but has the config file "SSU_OBSS".

I guess I ll wait for you guys to release some more working scenarios in the future. I think it would be nice to have at least the launch scenarios for all STS missions and then, when Donamy will be able and willing to do so, add the payloads with the updated attachment points so that payloads are correctly positioned in the cargo bay.
The problem with that is "where do we (SSU) stop?" The shuttle is like lego, one can do tons of things with it, and if we have to make scenarios for every possible mission... we'll have no time for development, which is already going slowly. :(
I think the scenarios we have cover most (current) capabilities, and there is a fair explanation of the configuration of things in the manual. It would be nice to have SSUW to help but...
 

Wolf

Donator
Donator
Joined
Feb 10, 2008
Messages
1,083
Reaction score
2
Points
38
Location
Milan
Deleting the parameters isn't enough, as they most likely moved somewhere else.
I'll run the STS-131 scenario and get it to work. One thing I spotted already is the "Ultra_OBSS" isn't SC3 (anymore) but has the config file "SSU_OBSS".


The problem with that is "where do we (SSU) stop?" The shuttle is like lego, one can do tons of things with it, and if we have to make scenarios for every possible mission... we'll have no time for development, which is already going slowly. :(
I think the scenarios we have cover most (current) capabilities, and there is a fair explanation of the configuration of things in the manual. It would be nice to have SSUW to help but...

Thanks GLS. I totally undesrtand you have other priorities, much more important than scenarios.
 

GLS

Addon Developer
Addon Developer
Joined
Mar 22, 2008
Messages
4,212
Reaction score
352
Points
108
So:
>> ground vessels (LCC, MLP and Pad) are "connected" the new way
>> SRBs and ET are using old vessels that don't exist
>> missing MPS He and empty MPS subsystem blocks
>> missing PayloadBay
>> panel R2 switches are different
>> panel A6 is now called A6U

Here is the 131 launch scenario
Code:
BEGIN_DESC
Orbiter saved state at T - 40 sec
END_DESC

BEGIN_ENVIRONMENT
  System Sol
  Date MJD 55291.431042
  Context SSU
END_ENVIRONMENT

BEGIN_FOCUS
  Ship Discovery
END_FOCUS

BEGIN_CAMERA
  TARGET Discovery
  MODE Cockpit
  FOV 40.00
  BEGIN_PRESET
    Track:ISS:50.00:RELATIVE 4.000 0.000 0.000
    Track:ISS:50.00:RELATIVE 4.000 0.000 0.000
  END_PRESET
END_CAMERA

BEGIN_MFD Left
  TYPE User
  MODE CRT
END_MFD

BEGIN_MFD Right
  TYPE User
  MODE CRT
END_MFD

BEGIN_MFD 3
  TYPE User
  MODE CRT
END_MFD

BEGIN_MFD 4
  TYPE User
  MODE CRT
END_MFD

BEGIN_MFD 5
  TYPE User
  MODE CRT
END_MFD

BEGIN_MFD 6
  TYPE User
  MODE CRT
END_MFD

BEGIN_MFD 7
  TYPE User
  MODE CRT
END_MFD

BEGIN_MFD 9
  TYPE User
  MODE CRT
END_MFD

BEGIN_MFD 10
  TYPE User
  MODE CRT
END_MFD

BEGIN_VC
END_VC

BEGIN_SHIPS
Discovery:SpaceShuttleUltra
  STATUS Landed Earth
  POS -80.6232502 28.6197342
  HEADING 0.00
  ATTACHED 0:0,MLP2
  PRPLEVEL 0:1.000 1:1.000 2:1.000 3:0.969 4:0.969 5:0.970 6:1.000 7:1.000 8:1.000 11:0.020
  NAVFREQ 0 0
  CONFIGURATION 0
  MISSION STS-131
  GEAR 0 0.0000
  OPS 101
  PLB_CAM 0 -90.00000 -0.0 90.0000 0.0000 -90.0000 0.000 90.0000
@SUBSYSTEM HeEng_C
  PRESS 4200
  VALVES 1 1 0 0
@ENDSUBSYSTEM		;HeEng_C
@SUBSYSTEM HeEng_L
  PRESS 4200
  VALVES 1 1 0 0
@ENDSUBSYSTEM		;HeEng_L
@SUBSYSTEM HeEng_R
  PRESS 4200
  VALVES 1 1 0 0
@ENDSUBSYSTEM		;HeEng_R
@SUBSYSTEM HePneu
  PRESS 4200
  VALVES 1 1 0 
@ENDSUBSYSTEM		;HePneu
@SUBSYSTEM MPS_C
  SSME config 2
  VIE config 1
  DCU_chA config 3
  DCU_chB config 3
  CIE_chA config 1
  CIE_chB config 1
@ENDSUBSYSTEM		;MPS_C
@SUBSYSTEM MPS_L
  SSME config 2
  VIE config 1
  DCU_chA config 3
  DCU_chB config 3
  CIE_chA config 1
  CIE_chB config 1
@ENDSUBSYSTEM		;MPS_L
@SUBSYSTEM MPS_R
  SSME config 2
  VIE config 1
  DCU_chA config 3
  DCU_chB config 3
  CIE_chA config 1
  CIE_chB config 1
@ENDSUBSYSTEM		;MPS_R
@SUBSYSTEM FMC1
@ENDSUBSYSTEM        ;FMC1
@SUBSYSTEM FMC2
@ENDSUBSYSTEM        ;FMC2
@SUBSYSTEM FMC3
@ENDSUBSYSTEM        ;FMC3
@SUBSYSTEM MMC1
@ENDSUBSYSTEM        ;MMC1
@SUBSYSTEM MMC2
@ENDSUBSYSTEM        ;MMC2
@SUBSYSTEM MMC3
@ENDSUBSYSTEM        ;MMC3
@SUBSYSTEM MMC4
@ENDSUBSYSTEM        ;MMC4
@SUBSYSTEM AMC1
@ENDSUBSYSTEM        ;AMC1
@SUBSYSTEM AMC2
@ENDSUBSYSTEM        ;AMC2
@SUBSYSTEM AMC3
@ENDSUBSYSTEM        ;AMC3
@SUBSYSTEM EIU1
@ENDSUBSYSTEM        ;EIU1
@SUBSYSTEM EIU2
@ENDSUBSYSTEM        ;EIU2
@SUBSYSTEM EIU3
@ENDSUBSYSTEM        ;EIU3
@SUBSYSTEM MTU
  MET_RUNNING 0
  MET0 0.000000
  MET1 0.000000
  MET2 0.000000
@ENDSUBSYSTEM		;MTU
@SUBSYSTEM IDP1
  IDP1 SPEC 65535
  IDP1 DISP 65535
@ENDSUBSYSTEM		;IDP1
@SUBSYSTEM IDP2
  IDP2 SPEC 65535
  IDP2 DISP 18
@ENDSUBSYSTEM		;IDP2
@SUBSYSTEM IDP3
  IDP3 SPEC 65535
  IDP3 DISP 18
@ENDSUBSYSTEM		;IDP3
@SUBSYSTEM IDP4
  IDP4 SPEC 65535
  IDP4 DISP 65535
@ENDSUBSYSTEM		;IDP4
@SUBSYSTEM IMU1
@ENDSUBSYSTEM        ;IMU1
@SUBSYSTEM IMU2
@ENDSUBSYSTEM        ;IMU2
@SUBSYSTEM IMU3
@ENDSUBSYSTEM        ;IMU3
@SUBSYSTEM GPC1
@ENDSUBSYSTEM        ;GPC1
@SUBSYSTEM GPC2
@ENDSUBSYSTEM        ;GPC2
@SUBSYSTEM GPC3
@ENDSUBSYSTEM        ;GPC3
@SUBSYSTEM GPC4
@ENDSUBSYSTEM        ;GPC4
@SUBSYSTEM GPC5
@ENDSUBSYSTEM        ;GPC5
@SUBSYSTEM SimpleGPCSystem
  @BEGINSOFTWARE ATVC_SOP
  CONFIG 1
  @ENDSOFTWARE 
@ENDSUBSYSTEM		;SimpleGPCSystem
@SUBSYSTEM ODS
  RING_STATE -1 0.0000
@ENDSUBSYSTEM        ;ODS
@SUBSYSTEM ADPS
  LEFT_AIRDATAPROBE 1 3 0
  RIGHT_AIRDATAPROBE 1 3 0
@ENDSUBSYSTEM        ;ADPS
@SUBSYSTEM ETUmbDoors
  ET_DOORS 1.000000 1.000000
  ET_DOOR_LATCHES 0.000000 1.000000 1.000000
@ENDSUBSYSTEM        ;ETUmbDoors
@SUBSYSTEM -Y Star Tracker Door Motor
@ENDSUBSYSTEM        ;-Y Star Tracker Door Motor
@SUBSYSTEM -Z Star Tracker Door Motor
@ENDSUBSYSTEM        ;-Z Star Tracker Door Motor
@SUBSYSTEM ACBusSystem
@ENDSUBSYSTEM        ;ACBusSystem
@SUBSYSTEM INVERTER1
@ENDSUBSYSTEM        ;INVERTER1
@SUBSYSTEM INVERTER2
@ENDSUBSYSTEM        ;INVERTER2
@SUBSYSTEM INVERTER3
@ENDSUBSYSTEM        ;INVERTER3
@SUBSYSTEM APU1
  APU1_State 2
  APU1_FuelPress 1451.108
  APU1_HydPress 3004.392
  APU1_Speed 103.521
@ENDSUBSYSTEM        ;APU1
@SUBSYSTEM APU2
  APU2_State 2
  APU2_FuelPress 1459.138
  APU2_HydPress 2985.080
  APU2_Speed 97.918
@ENDSUBSYSTEM        ;APU2
@SUBSYSTEM APU3
  APU3_State 2
  APU3_FuelPress 1441.774
  APU3_HydPress 2988.386
  APU3_Speed 100.585
@ENDSUBSYSTEM        ;APU3
@SUBSYSTEM WSB1
@ENDSUBSYSTEM        ;WSB1
@SUBSYSTEM WSB2
@ENDSUBSYSTEM        ;WSB2
@SUBSYSTEM WSB3
@ENDSUBSYSTEM        ;WSB3
@SUBSYSTEM LATCH0
  LATCH_STATE1 1 1.0000
  LATCH_STATE2 1 1.0000
  LATCH_STATE3 1 1.0000
  LATCH_STATE4 1 1.0000
  LATCH_STATE5 1 1.0000
@ENDSUBSYSTEM        ;LATCH0
@SUBSYSTEM LATCH1
  LATCH_STATE1 1 1.0000
  LATCH_STATE2 1 1.0000
  LATCH_STATE3 1 1.0000
  LATCH_STATE4 1 1.0000
  LATCH_STATE5 1 1.0000
@ENDSUBSYSTEM        ;LATCH1
@SUBSYSTEM LATCH2
  LATCH_STATE1 1 1.0000
  LATCH_STATE2 1 1.0000
  LATCH_STATE3 1 1.0000
  LATCH_STATE4 1 1.0000
  LATCH_STATE5 1 1.0000
@ENDSUBSYSTEM        ;LATCH2
@SUBSYSTEM PayloadBay
  DOOR_PORT 0 0.0000
  DOOR_STBD 0 0.0000
  RADIATOR_PORT 0 0.0000
  RADIATOR_STBD 0 0.0000
  RADLATCH_PORT 0 0.0000
  RADLATCH_STBD 0 0.0000
  DOORLATCH0 0 0.0000
  DOORLATCH1 0 0.0000
  DOORLATCH2 0 0.0000
  DOORLATCH3 0 0.0000
  DOORLATCH4 0 0.0000
  DOORLATCH5 0 0.0000
  DOORLATCH6 0 0.0000
  DOORLATCH7 0 0.0000
  KUBAND 0 0.0000
@ENDSUBSYSTEM		;PayloadBay
@SUBSYSTEM RMS
  ARM_STATUS 0.500000 0.013600 0.014688 0.500000 0.500000 0.500000
  SHOULDER_BRACE 1.000
  GRAPPLE 1 1.0000
  RIGIDIZE 1 1.0000
  EXTEND 1 1.0000
  RMS_ELBOW_CAM 0.0000 0.0000
  RMS_ROLLOUT 0 0.0000
  RMS_LATCHES 0 0.0000
@ENDSUBSYSTEM        ;RMS
@SUBSYSTEM STBD_MPM
  STBD_MPM_ROLLOUT 0 0.0000
  STBD_MPM_LATCHES 0 0.0000
  STBD_MPM_ATTACHED_PAYLOAD Ultra_OBSS 0
@ENDSUBSYSTEM        ;STBD_MPM
  @PANEL F2
  @ENDPANEL 
  @PANEL F4
  @ENDPANEL 
  @PANEL F6
  @OBJECT "CDR1"
  DISPLAY 3
  MENU 2
  @ENDOBJECT
  @OBJECT "CDR2"
  DISPLAY 1
  MENU 1
  @ENDOBJECT
  "Cdr Flt Cntlr Pwr" ON
  @ENDPANEL 
  @PANEL F7
  @OBJECT "CRT1"
  DISPLAY 0
  MENU 3
  @ENDOBJECT
  @OBJECT "CRT2"
  DISPLAY 0
  MENU 3
  @ENDOBJECT
  @OBJECT "CRT3"
  DISPLAY 0
  MENU 3
  @ENDOBJECT
  @OBJECT "MFD1"
  DISPLAY 4
  MENU 2
  @ENDOBJECT
  @OBJECT "MFD2"
  DISPLAY 3
  MENU 2
  @ENDOBJECT
  "Event Time" 40 0.000000 1 0
  @ENDPANEL 
  @PANEL F8
  @OBJECT "PLT1"
  DISPLAY 1
  MENU 1
  @ENDOBJECT
  @OBJECT "PLT2"
  DISPLAY 4
  MENU 2
  @ENDOBJECT
  "Plt Flt Cntlr Pwr" ON
  @ENDPANEL
  @PANEL R2
  "Boiler1 N2 Supply" ON
  "Boiler2 N2 Supply" ON
  "Boiler3 N2 Supply" ON
  "Boiler1 Power" ON
  "Boiler2 Power" ON
  "Boiler3 Power" ON
  "Boiler1 Cntlr/Htr" A
  "Boiler2 Cntlr/Htr" A
  "Boiler3 Cntlr/Htr" A
  "APU1 Operate" START/RUN
  "APU2 Operate" START/RUN
  "APU3 Operate" START/RUN
  "Hyd Main Pump Press 1" NORM
  "Hyd Main Pump Press 2" NORM
  "Hyd Main Pump Press 3" NORM
  "APU1 Cntlr Pwr" ON
  "APU2 Cntlr Pwr" ON
  "APU3 Cntlr Pwr" ON
  "APU1 Fuel Tank Valve" OPEN
  "APU2 Fuel Tank Valve" OPEN
  "APU3 Fuel Tank Valve" OPEN
  "ET Umb Centerline Latch" GND
  "ET Umb Left Door" OFF
  "ET Umb Left Door Latch" OFF
  "ET Umb Right Door" OFF
  "ET Umb Right Door Latch" OFF
  "MPS Pwr Left AC2" [1]
  "MPS Pwr Ctr AC1" [1]
  "MPS Pwr Right AC3" [1]
  "MPS Pwr Left AC3" [1]
  "MPS Pwr Ctr AC2" [1]
  "MPS Pwr Right AC1" [1]
  "MPS He Isol A Left" OPEN
  "MPS He Isol A Ctr" OPEN
  "MPS He Isol A Right" OPEN
  "MPS He Isol B Left" OPEN
  "MPS He Isol B Ctr" OPEN
  "MPS He Isol B Right" OPEN
  @ENDPANEL 
  @PANEL C3
  "LOMS Arm" ARM/PRESS
  "ROMS Arm" ARM/PRESS
  "BFC CRT Display" ON
  "BFC CRT Select" 2+3
  "LADP Stow Enable" INHIBIT
  "RADP Stow Enable" INHIBIT
  "LADP Deploy" STOW
  "RADP Deploy" STOW
  @ENDPANEL 
  @PANEL R11
  @ENDPANEL 
  @PANEL A6U
  "SENSE" -X
  "Aft Flt Cntlr Pwr" OFF
  "Payload Ret Latch 1" OFF
  "Payload Ret Latch 2" OFF
  "Payload Ret Latch 3" OFF
  "Payload Ret Latch 4" OFF
  "Payload Ret Latch 5" OFF
  "Payload Select" 1
  @ENDPANEL 
  @PANEL AftMDU
  @ENDPANEL 
  @PANEL A7A3/A8A3
  "SYSTEM POWER MNA" [1]
  "SYSTEM POWER MNB" [1]
  "PYRO POWER MNA" [0]
  "PYRO POWER MNC" [0]
  "SYS1 VENT ISOL" [1]
  "SYS1 VENT" [1]
  "SYS2 VENT ISOL" [1]
  "SYS2 VENT" [1]
  "PSU POWER MNA" [0]
  "PSU POWER MNB" [0]
  "LIGHTS AIRLOCK 1-4" [0]
  "LIGHTS AIRLOCK 2-3" [0]
  "LIGHTS DOCKING TRUSS FWD" [0]
  "LIGHTS DOCKING TRUSS AFT" [0]
  "ARLK/TNL FAN A" [0]
  "ARLK/TNL FAN B" [0]
  "LIGHTS C/L VESTIBULE PORT" [0]
  "LIGHTS C/L VESTIBULE STBD" [0]
  "CNTL PNL PWR A" OFF
  "CNTL PNL PWR B" OFF
  "CNTL PNL PWR C" OFF
  "HTRS/DCU PWR H1" OFF
  "HTRS/DCU PWR H2/DCU" OFF
  "HTRS/DCU PWR H3/DCU" OFF
  "APDS PWR A" OFF
  "APDS PWR B" OFF
  "APDS PWR C" OFF
  "PYROS Ap" OFF
  "PYROS Bp" OFF
  "PYROS Cp" OFF
  @ENDPANEL 
  @PANEL A8
  "Port MPM Deploy Cover" [0]
  "Stbd MPM Deploy Cover" [0]
  "Port RMS Latches" OFF
  "Stbd MPM Latches" OFF
  "Port MPM Deploy" OFF
  "Stbd MPM Deploy" OFF
  "EE Mode" OFF
  "RMS SELECT" OFF
  "Parameter" POSITION
  "Joint" SHOULDER_YAW
  "RMS Mode" OPR_CMD
  @ENDPANEL 
END
ET:SSU_SLWT
  STATUS Orbiting Earth
  PRPLEVEL 0:0.996000
  ATTACHED 0:20,Discovery
END
LSRB:SSU_LSRB_RSRM
  STATUS Orbiting Earth
  ATTACHED 0:21,Discovery
END
RSRB:SSU_RSRB_RSRM
  STATUS Orbiting Earth
  ATTACHED 0:22,Discovery
  AFCMODE 7
END
LC39A:SSU_Pad
  STATUS Landed Earth
  POS -80.6040720 28.6083850
  HEADING 270.00
  NAVFREQ 0 0
  OAA 0 0.0000
  GVA 0 0.0000
  VENT_HOOD 0 0.0000
  ETVAS 1 1.0000
  IAA 0 0.0000
  RSS 0 0.0000
  FSS_OWP 0 0.0000
  RSS_OWP 0 0.0000
  EAST_SRB_SFD 1 1.0000
  WEST_SRB_SFD 1 1.0000
  LCC_NAME LCC
END
LCC:SSU_LCC
  STATUS Landed Earth
  POS -80.6493245 28.5852249
  HEADING 35.60
  NAVFREQ 0 0
  LAUNCH_MJD 55291.431505
  PAD_NAME LC39A
END
MLP2:SSU_MLP
  STATUS Landed Earth
  ATTACHED 0:0,LC39A
  HEADING 0.00
  NAVFREQ 0 0
  T0_UMB 1 1.0000
END
END_SHIPS
It doesn't include the payloads but they should be ok.
I corrected the launch time and the scenario time, and now it starts at T-40s.

The mission file:
Code:
Name=STS-131
Orbiter=Discovery
OrbiterTexture=Discovery_9thmod
ET=SLWT
ETFRL=FALSE
SRM=RSRM
LaunchSite=KSC
LaunchPad=LC-39A
MLP=2
TargetInc=51.620000
TargetLAN=0.000000
MECOAlt=105564.000000
MECOVel=7607.601000
MECOFPA=0.730000
PerformRollToHeadsUp=TRUE
OMSAssistEnable=TRUE
OMSAssistDuration=59.000000
MaxSSMEThrust=104.5
ThrottleDown=1399.670000
ThrottleUp=1670.670000
UseRMS=TRUE
UseKUBand=TRUE
UseSTBDMPM=TRUE
UseODS=TRUE
UseExtAL=TRUE
UseTAA=FALSE
AftTAA=FALSE
HasBulkheadFloodlights=TRUE
HasDragChute=TRUE
Bridgerails=0,1
PayloadZPos7=0
PayloadZPos8=0
SILTS=FALSE
LogSSMEData=FALSE
UseCISS=FALSE
CISS_GPrime=TRUE
UseASE_IUS=FALSE
ASE_IUS_AftLocation=FALSE
InternalPRSDTankSets=5
HasEDOKit=FALSE
EDOPallets=0
I copied the launch parameters from the old scenario, so I can't confirm they are ok, but the throttle bucket seems to be way too late.
Also, only the External Airlock bridgerails are added, but others should be added as needed, and the payloads z position I also copied from the old scenario.
 

Wolf

Donator
Donator
Joined
Feb 10, 2008
Messages
1,083
Reaction score
2
Points
38
Location
Milan
I may have found a bug in OPS3.
Has anyone else noticed an erratic behaviour of the AFCS as the Orbiter alignes on final approach? It exits the HAC correctly pointing the nose to the RWY but then it starts overcorrecting with a series of S turns right and left of the extended RWY centerline chasing the lateral guidance green diamond.
 

GLS

Addon Developer
Addon Developer
Joined
Mar 22, 2008
Messages
4,212
Reaction score
352
Points
108
I may have found a bug in OPS3.
Has anyone else noticed an erratic behaviour of the AFCS as the Orbiter alignes on final approach? It exits the HAC correctly pointing the nose to the RWY but then it starts overcorrecting with a series of S turns right and left of the extended RWY centerline chasing the lateral guidance green diamond.

I'm currently working on the AerojetDAP: adding some missing parts, making corrections, taking out duplicate calculations, making it use the correct altitude reference and hopefully correcting for winds.
 

Donamy

Addon Developer
Addon Developer
Donator
Beta Tester
Joined
Oct 16, 2007
Messages
6,832
Reaction score
86
Points
123
Location
Cape
Has the procession roll of the RMS been fixed yet ?
 

DaveS

Space Shuttle Ultra Project co-developer
Addon Developer
Donator
Beta Tester
Joined
Feb 4, 2008
Messages
8,869
Reaction score
199
Points
153

zerofay32

Buckeye
Joined
Feb 6, 2008
Messages
470
Reaction score
0
Points
16
Location
Columbus, Ohio
I may have found a bug in OPS3.
Has anyone else noticed an erratic behaviour of the AFCS as the Orbiter alignes on final approach? It exits the HAC correctly pointing the nose to the RWY but then it starts overcorrecting with a series of S turns right and left of the extended RWY centerline chasing the lateral guidance green diamond.

One thing going for it, is that the Autopilot was only tested all the way down final once (STS 3?) and had some unusual pitch oscillations. There are still conflicting reports as to the cause. But the autopilot was never used after entering TAEM from then on AFAIK. (Might have been disconnected prior to entering the HAC, can't really remember.)
 

GLS

Addon Developer
Addon Developer
Joined
Mar 22, 2008
Messages
4,212
Reaction score
352
Points
108
One thing going for it, is that the Autopilot was only tested all the way down final once (STS 3?) and had some unusual pitch oscillations. There are still conflicting reports as to the cause. But the autopilot was never used after entering TAEM from then on AFAIK. (Might have been disconnected prior to entering the HAC, can't really remember.)

The crew would take over just before the HAC*, but AFAIK Autoland was good to control the vehicle all the way to wheels stop (except for dropping the gear).
Of course, the pilots wanted to land the shuttle themselves, so although using Autoland all the way was a test objective in the early part of the program, it never got done and all landings where man controlled.

If I remember well, in STS-3 they used Autoland up to the flare, and then getting the humans back in the loop was not entirely seamless...

Currently in SSU, from the flare on it didn't work (let's hope this changes).


*) Except (at least) for STS-2 that was flown manually from EI, and STS-3
 

DaveS

Space Shuttle Ultra Project co-developer
Addon Developer
Donator
Beta Tester
Joined
Feb 4, 2008
Messages
8,869
Reaction score
199
Points
153
*) Except (at least) for STS-2 that was flown manually from EI, and STS-3
This is a very common myth that Joe Engle handflew the orbiter all the way from EI to wheelstop. Engle did take control of the orbiter for some parts of the entry but only in the pitch channel and for a few seconds for some preplanned Program Test Inputs (PTIs). Once the PTIs had been completed, pitch channel control were returned to AUTO from CSS.
 

GLS

Addon Developer
Addon Developer
Joined
Mar 22, 2008
Messages
4,212
Reaction score
352
Points
108
Looking at the mountain of equations I'm currenty in, I was just now dreaming of the day where the vehicle will land totally on its own, and I was wondering if we shouldn't add an option to choose between manual and auto gear and chute deploy.
Currently we have somewhere in Atlantis.cpp (so not in the GPC code) logic to do those things as the PLT would, and it makes total sense as the user is usually busy "playing the CDR". But, if I can get all this working*, the user could also experience that alternate reality where the only thing the crew does during landing is drop the gear and the chute, so it makes sense to remove the current "help" in the operation of those things.
So, this is a good candidate for an option in the cfg file... we just need a name for it. :shrug:

*) I'm only working the guidance bit, and it is bad enough already, so I hope I don't have to get into the FCS mess... :shifty:
 

DaveS

Space Shuttle Ultra Project co-developer
Addon Developer
Donator
Beta Tester
Joined
Feb 4, 2008
Messages
8,869
Reaction score
199
Points
153
Looking at the mountain of equations I'm currenty in, I was just now dreaming of the day where the vehicle will land totally on its own, and I was wondering if we shouldn't add an option to choose between manual and auto gear and chute deploy.
Currently we have somewhere in Atlantis.cpp (so not in the GPC code) logic to do those things as the PLT would, and it makes total sense as the user is usually busy "playing the CDR". But, if I can get all this working*, the user could also experience that alternate reality where the only thing the crew does during landing is drop the gear and the chute, so it makes sense to remove the current "help" in the operation of those things.
So, this is a good candidate for an option in the cfg file... we just need a name for it. :shrug:

*) I'm only working the guidance bit, and it is bad enough already, so I hope I don't have to get into the FCS mess... :shifty:
Well, intact unmanned recovery of an orbiter was only an option for STS-121 and subsequent flights (excluding STS-125) through the Remote Control Orbiter (RCO) IFM cable of which only one existed and it was stowed on the ISS until it was brought back on STS-135.

Here's an NTRS document on the RCO capability: https://ntrs.nasa.gov/archive/nasa/casi.ntrs.nasa.gov/20070019347.pdf
 

Donamy

Addon Developer
Addon Developer
Donator
Beta Tester
Joined
Oct 16, 2007
Messages
6,832
Reaction score
86
Points
123
Location
Cape

GLS

Addon Developer
Addon Developer
Joined
Mar 22, 2008
Messages
4,212
Reaction score
352
Points
108
Any info on how late a landing site change is available? It seems from the TAEM guidance logic that it is not available in MM305, so I'm tempted to impose this limit. :shrug:
 

DaveS

Space Shuttle Ultra Project co-developer
Addon Developer
Donator
Beta Tester
Joined
Feb 4, 2008
Messages
8,869
Reaction score
199
Points
153
Any info on how late a landing site change is available? It seems from the TAEM guidance logic that it is not available in MM305, so I'm tempted to impose this limit. :shrug:
Landing site or runway? Landing site change can occur pretty much right up to the de-orbit burn, just need the crew to reload the uplinked targets (ITEM 22). Runway change can be made right up to TAEM. They were considering a runway change for STS-107 and STS-121 while those were still in the entry phase but those changes never happened.
 

GLS

Addon Developer
Addon Developer
Joined
Mar 22, 2008
Messages
4,212
Reaction score
352
Points
108
Landing site or runway? Landing site change can occur pretty much right up to the de-orbit burn, just need the crew to reload the uplinked targets (ITEM 22). Runway change can be made right up to TAEM. They were considering a runway change for STS-107 and STS-121 while those were still in the entry phase but those changes never happened.

Err, I wrote landing site.... :uhh:

The DPS Dictionary only says ITEM 41 is available in OPS 1, 3 and 6, but it can't be the whole MM305. On the other hand, the limit can't be pre-deorbit burn as then changing landing sites couldn't be used to handle under and overburns.

Then there are also the Edwards runways, where changing landing sites could mean a smaller change (in the target position) than changing runways.
 

DaveS

Space Shuttle Ultra Project co-developer
Addon Developer
Donator
Beta Tester
Joined
Feb 4, 2008
Messages
8,869
Reaction score
199
Points
153
Err, I wrote landing site.... :uhh:

The DPS Dictionary only says ITEM 41 is available in OPS 1, 3 and 6, but it can't be the whole MM305. On the other hand, the limit can't be pre-deorbit burn as then changing landing sites couldn't be used to handle under and overburns.

Then there are also the Edwards runways, where changing landing sites could mean a smaller change (in the target position) than changing runways.
Changing landing sites do mean the same for the software as it can only handle a single physical runway at the time. So changing landing sites = changing runways, you use the same software keyboard entries, it's all done through the local x05 HORIZ SIT screen.
 

GLS

Addon Developer
Addon Developer
Joined
Mar 22, 2008
Messages
4,212
Reaction score
352
Points
108
Changing landing sites do mean the same for the software as it can only handle a single physical runway at the time. So changing landing sites = changing runways, you use the same software keyboard entries, it's all done through the local x05 HORIZ SIT screen.

A landing sites has 2 runways (originally the 2 ends of the same runway, but "now" they don't have to be near each other).
So, changing a runway (originally, and for most landing sites) is a much smaller change in the target location than changing a landing site, so it makes sense that it would be allowed until much later than a change in landing site.
 

DaveS

Space Shuttle Ultra Project co-developer
Addon Developer
Donator
Beta Tester
Joined
Feb 4, 2008
Messages
8,869
Reaction score
199
Points
153
A landing sites has 2 runways (originally the 2 ends of the same runway, but "now" they don't have to be near each other).
So, changing a runway (originally, and for most landing sites) is a much smaller change in the target location than changing a landing site, so it makes sense that it would be allowed until much later than a change in landing site.
Yes, this is correct. The OMS isn't accurate enough to guarantee a landing on a specific runway. Also, atmospheric conditions can throw that targeting off by miles.

For PASS/BFS the term "landing site" doesn't really exist. The landing site is chosen by executing the proper de-orbit burn so that the entry trajectory lines up with your desired target.

So that's MM302's job, to set up the entry trajectory. That is also why AOA is two-burn sequence, the first burn is a standard OMS-2 with the second the appropriate de-orbit burn. x05 HORIZ SIT only kicks in after the de-orbit burn, once 304/604 has been entered.
 

GLS

Addon Developer
Addon Developer
Joined
Mar 22, 2008
Messages
4,212
Reaction score
352
Points
108
For PASS/BFS the term "landing site" doesn't really exist. The landing site is chosen by executing the proper de-orbit burn so that the entry trajectory lines up with your desired target.
Not so. AFAIK there is a module called "site selection" that provides the data to guidance about the location of the landing site. The deorbit burn "throws" the vehicle into the atmosphere such that the landing site is within reach, so it has to be planned correctly. Actually getting there, needs entry guidance to do its bit and guide the vehicle there, and it can do that with different starting conditions. It can tolerate underburns and overburns and still make it safely to the runway (only large deorbit burn errors need a landing site change).

x05 HORIZ SIT only kicks in after the de-orbit burn, once 304/604 has been entered.
Actually, SPEC 50 is available in OPS 1, 3 and 6 (we only have it working in OPS3), but it doesn't feed info into the deorbit burn, so humans have to select the landing site for the deorbit burn they are doing.


Anyway, I was thinking of moving the entry/landing displays out of the AerojetDAP class, as I now expect to have the data they need +/- isolated, but I don't know where to put them... :facepalm: Urwumpe, how are the displays handled again? :uhh:
 
Top