Problem Atlantis Space Shuttle RCS Thrusters Stuck 'On' When Restarting Scenario

DrSolidRocketMotor · Jun 20, 2012

Hello Everyone

I am experiencing a strange problem whenever I attempt to restart a saved scenario from a previous Orbiter session. The problem occurs whether or not I use my own personal saved scenario folder, or the Current State folder.

The problem occurs with the Atlantis Space Shuttle. Several seconds after restarting the scenario, and without any input on my part, several of the shuttle's RCS thrusters become stuck in the 'on' position. Also, the shuttle's OMS (Orbital Maneuvering System) engines go to full thrust, once again, without any input on my part.

I am able to shut down the OMS engines (with numpad *), but no matter what I try, I cannot turn off the stuck RCS thrusters -- the shuttle continues to tumble, with increasing pitch, yaw, and roll rates -- until the Shuttle runs out of fuel.

Since I exited the previous Orbiter session with the vehicle in a free coast mode, and absolutely no rotational movement, I am at a loss to understand why this is happening at all.

Hopefully, someone will be able to offer some insight as to what is causing this problem....thank you very kindly!

System Information & Logfiles follow --
please let me know if you need additional information

Code:

-----------------------------------------------------------------------------------------------
OS Name    Microsoft Windows XP Home Edition (32 bit)
Version    5.1.2600 Service Pack 3 Build 2600
OS Manufacturer    Microsoft Corporation
System Name    HAL9000SE
System Manufacturer    HP Pavilion 04
System Model    P5267A-ABA 7935
System Type    X86-based PC
Processor    AMD Athlon Processor
        x86 Family 6 Model 4 Stepping 4 AuthenticAMD ~1300 Mhz
BIOS Version/Date    Phoenix Technologies LTD 3.08, 8/31/2001
SMBIOS Version    2.31
Windows Directory    C:\WINDOWS
System Directory    C:\WINDOWS\system32
Boot Device    \Device\HarddiskVolume1
Locale    United States
Hardware Abstraction Layer    Version = "5.1.2600.5512 (xpsp.080413-2111)"
Total Physical Memory    1,024.00 MB
Available Physical Memory    391.47 MB
Total Virtual Memory    2.00 GB
Available Virtual Memory    1.96 GB
Page File Space    8.88 GB
Page File    C:\pagefile.sys


Sound Device (onboard)
Name    VIA AC'97 Audio Controller (WDM)
Manufacturer    VIA Technologies, Inc.
Status    OK
PNP Device ID    PCI\VEN_1106&DEV_3058&SUBSYS_803E1043&REV_50\3&61AAA01&0&3D
I/O Port    0x00001000-0x000010FF
I/O Port    0x00001414-0x00001417
I/O Port    0x00001410-0x00001413
IRQ Channel    IRQ 10
Driver    c:\windows\system32\drivers\viaudio.sys (6.14.01.3880 built by: VIA, 72.25 KB (73,984 bytes), 8/19/2003 5:27 PM)


Graphics (single PCI card -- shows up as two devices)

-----------------------------------------------------------------------------------------------
Please Note -- The following device (onboard graphics) has been disabled

Name    S3 Graphics ProSavage 8A26 (Microsoft Corporation)
PNP Device ID    PCI\VEN_5333&DEV_8A26&SUBSYS_00000000&REV_03\4&9AEDED5&0&0008
Adapter Type    ATI display adapter (0x5961), S3 Graphics, Inc compatible
Adapter Description    S3 Graphics ProSavage 8A26 (Microsoft Corporation)
Adapter RAM    128.00 MB (134,217,728 bytes)
Installed Drivers    ati2dvag.dll
Driver Version    6.14.10.0012-13.94.12
INF File    ps5333.inf (S3SavageNB section)
Color Planes    1
Color Table Entries    4294967296
Resolution    1360 x 768 x 60 hertz
Bits/Pixel    32
Driver    c:\windows\system32\drivers\s3gnbm.sys (6.14.10.0012-13.94.12, 163.00 KB (166,912 bytes), 8/4/2004 1:29 AM)
-----------------------------------------------------------------------------------------------
    
The following two devices are active --

Name    RADEON 9200 SERIES
PNP Device ID    PCI\VEN_1002&DEV_5961&SUBSYS_05801545&REV_01\3&61AAA01&0&70
Adapter Type    ATI display adapter Secondary (0x5941), ATI Technologies Inc. compatible
Adapter Description    RADEON 9200 SERIES
Adapter RAM    128.00 MB (134,217,728 bytes)
Installed Drivers    ati2dvag.dll
Driver Version    6.14.10.6599
INF File    oem17.inf (ati2mtag_RV280 section)
Color Planes    Not Available
Color Table Entries    Not Available
Resolution    Not Available
Bits/Pixel    Not Available
Memory Address    0xE0000000-0xE7FFFFFF
I/O Port    0x00001800-0x000018FF
Memory Address    0xD8000000-0xD800FFFF
IRQ Channel    IRQ 17
I/O Port    0x000003B0-0x000003BB
I/O Port    0x000003C0-0x000003DF
Memory Address    0xA0000-0xFFFFF
Driver    c:\windows\system32\drivers\ati2mtag.sys (6.14.10.6599, 1.41 MB (1,478,656 bytes), 8/4/2004 1:29 AM)
    
Name    RADEON 9200 SERIES - Secondary
PNP Device ID    PCI\VEN_1002&DEV_5941&SUBSYS_05811545&REV_01\3&61AAA01&0&71
Adapter Type    Not Available
Adapter Description    ATI Technologies Inc.
Adapter RAM    Not Available
Installed Drivers    Not Available
Driver Version    Not Available
INF File    6.14.10.6599 (oem17.inf section)
Color Planes    ati2mtag_RV280
Color Table Entries    Not Available
Resolution    Not Available
Bits/Pixel    Not Available
Memory Address    0xE8000000-0xEFFFFFFF
Memory Address    0xFFEE0000-0xFFEEFFFF
Driver    c:\windows\system32\drivers\ati2mtag.sys (6.14.10.6599, 1.41 MB (1,478,656 bytes), 8/4/2004 1:29 AM)
-----------------------------------------------------------------------------------------------
Orbiter.cfg

; === ORBITER Master Configuration File ===
EchoAllParams = FALSE
LPadRect = 0 0 542 573

; === Logical parameters ===
StartPaused = TRUE

; === Visual parameters ===
EnableCloudShadows = TRUE
EnableSpecularRipples = TRUE
AmbientLevel = 60
NightlightBrightness = 0.75

; === Device settings ===
DeviceIndex = 4
ModeIndex = 25
Fullscreen = TRUE

; === Active plugin list ===
ACTIVE_MODULES
  OrbiterSound
END_MODULES

-----------------------------------------------------------------------------------------------
Orbiter.log

**** Orbiter.log
Build Aug 30 2010 [v.100830]
Timer precision: 2.79365e-007 sec
Found 0 joystick(s)
Devices enumerated: 6
Devices accepted: 5
==> RGB Emulation
==> Direct3D HAL
==> Direct3D T&L HAL
==> Direct3D HAL (RADEON 9200 SERIES  )
==> Direct3D T&L HAL (RADEON 9200 SERIES  )
Module AtlantisConfig.dll .... [Build 100830, API 100830]
Module AtmConfig.dll ......... [Build 100830, API 100830]
Module DGConfigurator.dll .... [Build 100830, API 100830]
Module OrbiterSound.dll ...... [Build ******, API 060425]
---------------------------------------------------------------
>>> WARNING: Obsolete API function used: oapiRegisterMFDMode
At least one active module is accessing an obsolete interface function.
Addons which rely on obsolete functions may not be compatible with
future versions of Orbiter.
---------------------------------------------------------------

**** Creating simulation session
DirectDraw interface OK
Direct3D interface OK
Graphics: Viewport: Fullscreen 1360 x 768 x 32
Graphics: Hardware T&L capability: Yes
Graphics: Z-buffer depth: 32 bit
Graphics: Stencil buffer depth: 8 bit
Graphics: Active lights supported: 8
Loading 15382 records from star database
Module Sun.dll ............... [Build 100830, API 100830]
VSOP87(E) Sun: Precision 1e-006, Terms 554/6634
Module Mercury.dll ........... [Build 100830, API 100830]
VSOP87(B) Mercury: Precision 1e-005, Terms 167/7123
Module Venus.dll ............. [Build 100830, API 100830]
Module VenusAtm2006.dll ...... [Build 100830, API 100830]
VSOP87(B) Venus: Precision 1e-005, Terms 79/1710
Module Earth.dll ............. [Build 100830, API 100830]
Module EarthAtmJ71G.dll ...... [Build 100830, API 100830]
VSOP87(B) Earth: Precision 1e-008, Terms 2564/2564
Module Moon.dll .............. [Build 100830, API 100830]
ELP82: Precision 1e-005, Terms 116/829
Module Mars.dll .............. [Build 100830, API 100830]
Module MarsAtm2006.dll ....... [Build 100830, API 100830]
VSOP87(B) Mars: Precision 1e-005, Terms 405/6400
Module Phobos.dll ............ [Build ******, API 060425]
Module Deimos.dll ............ [Build ******, API 060425]
Module Galsat.dll ............ [Build 100217, API 100215]
Module Jupiter.dll ........... [Build 100830, API 100830]
VSOP87(B) Jupiter: Precision 1e-006, Terms 1624/3625
Module Io.dll ................ [Build 100217, API 100215]
Module Europa.dll ............ [Build 100217, API 100215]
Module Ganymede.dll .......... [Build 100217, API 100215]
Module Callisto.dll .......... [Build 100217, API 100215]
Module Satsat.dll ............ [Build 100215, API 100212]
Module Saturn.dll ............ [Build 100830, API 100830]
VSOP87(B) Saturn: Precision 1e-006, Terms 2904/6365
Module Mimas.dll ............. [Build 100215, API 100212]
SATSAT Mimas: Terms 113
Module Enceladus.dll ......... [Build 100215, API 100212]
SATSAT Enceladus: Terms 33
Module Tethys.dll ............ [Build 100215, API 100212]
SATSAT Tethys: Terms 101
Module Dione.dll ............. [Build 100215, API 100212]
SATSAT Dione: Terms 59
Module Rhea.dll .............. [Build 100215, API 100212]
SATSAT Rhea: Terms 68
Module Titan.dll ............. [Build 100215, API 100212]
SATSAT Titan: Terms 100
Module Iapetus.dll ........... [Build 100215, API 100212]
SATSAT Iapetus: Terms 605
Module Uranus.dll ............ [Build 100830, API 100830]
VSOP87(B) Uranus: Precision 1e-006, Terms 1827/5269
Module Miranda.dll ........... [Build ******, API 060425]
Module Ariel.dll ............. [Build ******, API 060425]
Module Umbriel.dll ........... [Build ******, API 060425]
Module Titania.dll ........... [Build ******, API 060425]
Module Oberon.dll ............ [Build ******, API 060425]
Module Neptune.dll ........... [Build 100830, API 100830]
VSOP87(B) Neptune: Precision 1e-006, Terms 391/2024
Finished initialising world
Module Atlantis.dll .......... [Build 100830, API 100830]
Module ShuttleA.dll .......... [Build 100830, API 100830]
Module Atlantis_SRB.dll ...... [Build 100830, API 100830]
Finished initialising status
Finished initialising camera
Finished initialising panels
Finished setting up render state
Module LuaInline.dll ......... [Build 100830, API 100830]
---------------------------------------------------------------
>>> WARNING: Obsolete API function used: oapiGetStationCount
At least one active module is accessing an obsolete interface function.
Addons which rely on obsolete functions may not be compatible with
future versions of Orbiter.
---------------------------------------------------------------
**** Closing simulation session

-----------------------------------------------------------------------------------------------
Report Addons (module OrbiterSound in use)

kuddel · Jun 20, 2012

Hi,

first of all thank you for your detailed description!

Reading your issue report I first thought about a joystick-problem, but I see that you do not have one attached.

Does the problem occur even when you completely close Orbiter and re-start it again? If that's the case I would say that this has to do with 'uninitialized memory'.
If that did the trick, I would recomend you to set the "Orbiter shutdown options" to "Respawn Orbiter process" (see attached image if you don't know how to reach that setting)

If that still keeps firering your RCS, would you please post the scenario you've tried?

Cheers,
Kuddel

DrSolidRocketMotor · Jun 21, 2012

kuddel said:
Hi,

first of all thank you for your detailed description!

Reading your issue report I first thought about a joystick-problem, but I see that you do not have one attached.

Does the problem occur even when you completely close Orbiter and re-start it again? If that's the case I would say that this has to do with 'uninitialized memory'.
If that did the trick, I would recomend you to set the "Orbiter shutdown options" to "Respawn Orbiter process" (see attached image if you don't know how to reach that setting)

If that still keeps firering your RCS, would you please post the scenario you've tried?

Cheers,
Kuddel

Thank you for your response!

To answer your first question, yes, the problem does recur even after I completely exit the program and then restart it again.

I'm not sure I understand what you mean by 'uninitialized memory' -- could you please explain?

I will try your suggestions -- thanks!

When you asked me to post the scenario that I've tried, I'm assuming you mean the contents of the scenario file?

kuddel · Jun 21, 2012

DrSolidRocketMotor said:
Thank you for your response!

To answer your first question, yes, the problem does recur even after I completely exit the program and then restart it again.

Hmmm that's odd.

DrSolidRocketMotor said:
I'm not sure I understand what you mean by 'uninitialized memory' -- could you please explain?

As it does not seem to be your problem it is not much you should worry about. Nevertheless here's a brief description to what it means:

Using uninitialized memory: Contents of uninitialized memory are treated as garbage values. Using such values can lead to unpredictable program behavior.
Example: A program likes to add some values. Therefore it uses a memory(-location) where it adds several values.
If the (lazy) programmer did not explicitely initialize that memory(-location) with a zero, it might work the first time (because after power-up that location contained a zero).
A second time the memory(-location) might contain already a value (e.g. 98765) from any other programm or a previous run -thus the value after the adding will not be correct.
This kind of errors are ugly because they sometimes appear very seldom.

DrSolidRocketMotor said:
When you asked me to post the scenario that I've tried, I'm assuming you mean the contents of the scenario file?

Yes, would you please do so?

/Kuddel

DrSolidRocketMotor · Jun 22, 2012

I tried setting the Orbiter shutdown options as you suggested -- no effect.

Here is the saved scenario file for your examination --

Code:

BEGIN_DESC
test state
END_DESC

BEGIN_ENVIRONMENT
  System Sol
  Date MJD 51984.1388440802
  Script demos/atlantis_launch
END_ENVIRONMENT

BEGIN_FOCUS
  Ship STS-101
END_FOCUS

BEGIN_CAMERA
  TARGET STS-101
  MODE Extern
  POS 1.85 148.78 -20.41
  TRACKMODE GlobalFrame
  FOV 50.00
  BEGIN_PRESET
    Cockpit:STS-101:40.00
    Ground:STS-101:40.00:Earth -80.62339 28.61960 110.00
    Track:STS-101:50.00:RELATIVE 2.890 -0.009 -1.229
    Ground:STS-101:10.00:Earth -80.65298 28.58028 20.00
    Track:ISS:40.00:RELATIVE 1.983 -0.474 -0.522
    Track:Earth:40.00:GLOBAL 2.896 2.132 -0.331
  END_PRESET
END_CAMERA

BEGIN_HUD
  TYPE Orbit
  REF AUTO
END_HUD

BEGIN_MFD Left
  TYPE Surface
  SPDMODE 4
END_MFD

BEGIN_MFD Right
  TYPE Map
  REF Earth
  BTARGET Cape Canaveral
  ZOOM 4
END_MFD

BEGIN_SHIPS
ISS:ProjectAlpha_ISS
  STATUS Orbiting Earth
  RPOS 6529571.29 266861.69 -1636161.01
  RVEL 798.446 -7399.909 1951.188
  AROT 16.53 24.08 -120.76
  AFCMODE 7
  PRPLEVEL 0:1.000000
  IDS 0:1 100 1:2 100 2:3 100 3:4 100 4:5 100
  NAVFREQ 0 0
  XPDR 466
END
Mir:Mir
  STATUS Orbiting Earth
  RPOS 5449213.78 420290.69 3809007.47
  RVEL -4429.253 220.578 6342.594
  AROT -135.04 68.66 64.66
  VROT -0.04 -0.02 0.05
  AFCMODE 7
  IDS 0:540 100 1:542 100 2:544 100
  XPDR 482
END
Luna-OB1:Wheel
  STATUS Orbiting Moon
  RPOS 1025480.89 1989021.24 1097.22
  RVEL -1315.701 678.211 0.271
  AROT -0.02 0.00 -12.39
  VROT 0.00 0.00 10.00
  AFCMODE 7
  IDS 0:560 100 1:564 100
  XPDR 494
END
STS-101:Atlantis
  STATUS Orbiting Earth
  RPOS 5158866.63 3582197.07 -2445768.14
  RVEL 4894.775 -4419.568 3917.659
  AROT -24.44 -84.55 -25.59
  AFCMODE 7
  PRPLEVEL 0:0.636457
  THLEVEL 4:0.000149 5:0.000149 8:0.000442 9:0.000442 12:0.000530 13:0.000530
  NAVFREQ 0 0
  CONFIGURATION 3
  GEAR 0 0.0000
  ARM_STATUS 0.5000 0.0000 0.0000 0.5000 0.5000 0.5000
  SAT_OFS_X 0.000000
  SAT_OFS_Y 0.000000
  SAT_OFS_Z 0.000000
  CARGO_STATIC_MESH Carina_cradle
  CARGO_STATIC_OFS 0.000000 -1.650000 0.050000
  CARGODOOR 1 1.0000
  KUBAND 1 1.0000
END
Carina:Carina
  STATUS Orbiting Earth
  RPOS 5158866.63 3582197.07 -2445768.14
  RVEL 4894.775 -4419.568 3917.659
  AROT -24.44 -84.55 -25.59
  ATTACHED 0:0,STS-101
  AFCMODE 7
  NAVFREQ 0 0
END
SH-02:ShuttleA
  STATUS Landed Earth
  BASE Cape Canaveral:5
  POS -80.6745292 28.5197208
  HEADING 100.00
  AFCMODE 7
  PRPLEVEL 0:1.000000 1:1.000000
  NAVFREQ 0 0
  XPDR 0
  PODANGLE 0.0000 0.0000
  DOCKSTATE 0 0.0000
  AIRLOCK 0 0.0000
  GEAR 0 0.0000
  PAYLOAD MASS 4.0 0
END
STS-101-SRB1:Atlantis_SRB
  STATUS Landed Earth
  POS -76.3628596 28.5416384
  HEADING 329.17
  AFCMODE 7
END
STS-101-SRB2:Atlantis_SRB
  STATUS Landed Earth
  POS -76.3577402 28.4747359
  HEADING 210.17
  AFCMODE 7
END
STS-101-Tank:Atlantis_Tank
  STATUS Landed Earth
  POS 45.4401311 -18.6357525
  HEADING 263.92
  AFCMODE 7
END
END_SHIPS

I also noticed that a docking adapter or target that was previously sitting in the shuttle's cargo bay has mysteriously reappeared several meters below the shuttle's underbelly. I can provide a screenshot if you would like to see one.

Several other notes --

Now I understand what you meant by uninitialized memory -- sorry, I used to be a programmer -- it's been a while since I've written any code, but now it comes back to me.

Here's another wrinkle -- I'm not sure if it means anything. I use a 3D graphics program on my system called trueSpace. trueSpace's master project files also use the .scn extension -- in fact, when I first looked at Orbiter's scenario files in Windows Explorer, they were identified as trueSpace scene files -- it was only after reading about scenario files in one of the documentation files did I realize that they were plain text that could be read with Notepad.

I don't see how the two programs could interact, but I wonder about the common file extension.

Thanks for your help!

---------- Post added at 06:00 AM ---------- Previous post was at 05:55 AM ----------

I'm also wondering if this behavior may be a sign that my operating system has somehow become corrupted?

Given the number of people that have viewed this post and the number of replies that I've received (namely, yours) -- I'm guessing that I may be the only one experiencing this problem.

Urwumpe · Jun 22, 2012

Uninitialized memory is no corrupted operating system, but plain sloppy programming.

In C++, all memory that your program allocates is not initialized. Effectively random data, it is what was once stored in the memory locations before your program was loaded there.

If such an uninitialized variable is used, anything can happen.

Too look closer at your problem, this line is interesting:

THLEVEL 4:0.000149 5:0.000149 8:0.000442 9:0.000442 12:0.000530 13:0.000530

This line describes the state of the RCS thrusters at the moment your scenario was saved. instead of being plain zero, you have minimal activity there. Possibly caused by a joystick that wasn't centered properly with too little deadbands.

Next, your scenario loads the atlantis launch autopilot script. Possible next source for problems. But I would need to read the Lua file for telling you anything about its behavior on a relaunch. I suspect, it does not like being activated at the wrong time.

IronRain · Jun 22, 2012

I've tried your scenario and the only thing I noticed was that the OMS firing which is indeed solved by pressing the * key.

Have you tried a clean installation?

Urwumpe · Jun 22, 2012

IronRain said:
I've tried your scenario and the only thing I noticed was that the OMS firing which is indeed solved by pressing the * key.

Have you tried a clean installation?

Did you have the Lua module activated?

IronRain · Jun 22, 2012

Urwumpe said:
Did you have the Lua module activated?

Nope, and when I turned it on the spinning started.. I guess that's the problem

kuddel · Jun 22, 2012

Hello DrSolidRocketMotor,

after some more people are involved (see, your're not alone

) I'll come back to you.

would you try this scenario, please?

Code:

BEGIN_DESC
test state (with 'zeroed' THLEVEL & removed 'atlantis_launch' script)
END_DESC

BEGIN_ENVIRONMENT
  System Sol
  Date MJD 51984.1388440802
END_ENVIRONMENT

BEGIN_FOCUS
  Ship STS-101
END_FOCUS

BEGIN_CAMERA
  TARGET STS-101
  MODE Extern
  POS 1.85 148.78 -20.41
  TRACKMODE GlobalFrame
  FOV 50.00
  BEGIN_PRESET
    Cockpit:STS-101:40.00
    Ground:STS-101:40.00:Earth -80.62339 28.61960 110.00
    Track:STS-101:50.00:RELATIVE 2.890 -0.009 -1.229
    Ground:STS-101:10.00:Earth -80.65298 28.58028 20.00
    Track:ISS:40.00:RELATIVE 1.983 -0.474 -0.522
    Track:Earth:40.00:GLOBAL 2.896 2.132 -0.331
  END_PRESET
END_CAMERA

BEGIN_HUD
  TYPE Orbit
  REF AUTO
END_HUD

BEGIN_MFD Left
  TYPE Surface
  SPDMODE 4
END_MFD

BEGIN_MFD Right
  TYPE Map
  REF Earth
  BTARGET Cape Canaveral
  ZOOM 4
END_MFD

BEGIN_SHIPS
ISS:ProjectAlpha_ISS
  STATUS Orbiting Earth
  RPOS 6529571.29 266861.69 -1636161.01
  RVEL 798.446 -7399.909 1951.188
  AROT 16.53 24.08 -120.76
  AFCMODE 7
  PRPLEVEL 0:1.000000
  IDS 0:1 100 1:2 100 2:3 100 3:4 100 4:5 100
  NAVFREQ 0 0
  XPDR 466
END
Mir:Mir
  STATUS Orbiting Earth
  RPOS 5449213.78 420290.69 3809007.47
  RVEL -4429.253 220.578 6342.594
  AROT -135.04 68.66 64.66
  VROT -0.04 -0.02 0.05
  AFCMODE 7
  IDS 0:540 100 1:542 100 2:544 100
  XPDR 482
END
Luna-OB1:Wheel
  STATUS Orbiting Moon
  RPOS 1025480.89 1989021.24 1097.22
  RVEL -1315.701 678.211 0.271
  AROT -0.02 0.00 -12.39
  VROT 0.00 0.00 10.00
  AFCMODE 7
  IDS 0:560 100 1:564 100
  XPDR 494
END
STS-101:Atlantis
  STATUS Orbiting Earth
  RPOS 5158866.63 3582197.07 -2445768.14
  RVEL 4894.775 -4419.568 3917.659
  AROT -24.44 -84.55 -25.59
  AFCMODE 7
  PRPLEVEL 0:0.636457
  THLEVEL 4:0.000000 5:0.000000 8:0.000000 9:0.000000 12:0.000000 13:0.000000
  NAVFREQ 0 0
  CONFIGURATION 3
  GEAR 0 0.0000
  ARM_STATUS 0.5000 0.0000 0.0000 0.5000 0.5000 0.5000
  SAT_OFS_X 0.000000
  SAT_OFS_Y 0.000000
  SAT_OFS_Z 0.000000
  CARGO_STATIC_MESH Carina_cradle
  CARGO_STATIC_OFS 0.000000 -1.650000 0.050000
  CARGODOOR 1 1.0000
  KUBAND 1 1.0000
END
Carina:Carina
  STATUS Orbiting Earth
  RPOS 5158866.63 3582197.07 -2445768.14
  RVEL 4894.775 -4419.568 3917.659
  AROT -24.44 -84.55 -25.59
  ATTACHED 0:0,STS-101
  AFCMODE 7
  NAVFREQ 0 0
END
SH-02:ShuttleA
  STATUS Landed Earth
  BASE Cape Canaveral:5
  POS -80.6745292 28.5197208
  HEADING 100.00
  AFCMODE 7
  PRPLEVEL 0:1.000000 1:1.000000
  NAVFREQ 0 0
  XPDR 0
  PODANGLE 0.0000 0.0000
  DOCKSTATE 0 0.0000
  AIRLOCK 0 0.0000
  GEAR 0 0.0000
  PAYLOAD MASS 4.0 0
END
STS-101-SRB1:Atlantis_SRB
  STATUS Landed Earth
  POS -76.3628596 28.5416384
  HEADING 329.17
  AFCMODE 7
END
STS-101-SRB2:Atlantis_SRB
  STATUS Landed Earth
  POS -76.3577402 28.4747359
  HEADING 210.17
  AFCMODE 7
END
STS-101-Tank:Atlantis_Tank
  STATUS Landed Earth
  POS 45.4401311 -18.6357525
  HEADING 263.92
  AFCMODE 7
END
END_SHIPS

(you can also take the attached scn-file)

It it the same as yours, except that

The THLEVEL values are 'zeroed' (proposal by Urwumpe)
Removed 'atlantis_launch' script from starting (IronRains input)

I'm pretty sure that this scenario will not fire any thrusters or the SSMEs.

Have a nice weekend,

Kuddel

kuddel · Jun 22, 2012

IronRain said:
Nope, and when I turned it on the spinning started.. I guess that's the problem

Jepp, that makes sense.

The launch-(lua)-script should be extended, to...

kill all the thrust (set to zero) after orbit insertion, and...
not start at all when shuttle is already in orbit.

for the first thing I think there was a procedure like 'kill_all_thrust' written by someone here on the forum. I'll dig that out when I'm on my "home-machine".
here at work I don't have the "time"

Cheers, Kuddel

---------- Post added at 19:40 ---------- Previous post was at 17:25 ----------

O.K. it's me again,

the changed scenario I've posted before does the trick.
But to prevent that any future users will run into the same issue, here's a slightly changed 'launch.lua' script (with my changes colored):

Code:

-- Load attitude functions
run('attctrl')

term.out('Space Shuttle Atlantis ascent autopilot')
term.out('Run function \'launch()\' to start')
term.out('Global variables (can be adjusted before launch):')
term.out('vif: target spacecraft interface (default: current)')
term.out('orbit_alt: target altitude [m] (default 300e3)')
term.out('azimuth: launch azimuth [rad] (default: 90*RAD)')

-- Reset some of the attitude parameters
pitch_a = 0.6
pitch_b = 5.7

vif = V -- target vessel interface
if vif == nil then
   vif = vessel.get_focusinterface()
end
orbit_alt = 300e3   -- target orbit altitude (can be overridden before launch)
azimuth = PI/2      -- launch azimuth
do_oms1 = true
do_oms2 = true

R_Earth = 6.37101e6 -- Earth radius
comment = nil       -- running comments
last_comment = nil  -- previous comment
comment_timer = 0

-- return periapsis radius
function ped (v)
    local el,prm
    el,prm = v:get_elementsex()
    return prm.PeD
end

-- return apoapsis radius
function apd (v)
    el,prm = v:get_elementsex()
    return prm.ApD
end

-- return apoapsis time
function apt (v)
    el,prm = vif:get_elementsex()
    return prm.ApT
end

function met_counter ()
  local t0 = oapi.get_simtime()+7
  local met, metstr
  for i=-7,10000 do
    met = oapi.get_simtime()-t0
    metstr = 'MET = '..string.format('%0.0f',met)
    if i==126 then comment = 'Solid rocket booster separation' end
    if comment ~= last_comment then
      comment_timer = 0
    else
      comment_timer = comment_timer+1
      if comment_timer > 10 then comment = nil; comment_timer = 0 end
    end
    last_comment = comment
    if comment ~= nil then
      metstr = metstr..'\n'..comment
    end
    note.set_text(metstr)
    proc.wait_simtime(t0+i+1)
  end
  note.set_text('')
end

function spdpitch (v)
  -- pitch angle of velocity marker
  -- this only works for bank=0 or bank=pi
  local p=v:get_pitch()
  local a=v:get_aoa()
  if math.abs(v:get_bank()) < PI05 then
    return p-a
  else
    return p+a
  end
end

function ascent_pitch_prog (v)
  local p = {70,60,50,40,30,20, 10,  0,-5}  -- pitch targets
  local t = {20,10,10,10,40,65,195,130,30}  -- pitch intervals
  for i = 1,7 do
    term.out ('pitch '..p[i])
    setpitch (v,RAD*p[i],t[i],0)
    -- note that we set a tolerance of 0 to prevent the
    -- pitch programme from terminating prematurely
  end
  term.out ('hold altitude programme')
  pitch_a = 1.0
  pitch_b = 3.0
  setpitch (v,0,160,0,spdpitch)
end


-- ------------------------------------------------------
-- The complete autopilot
-- ------------------------------------------------------

function launch ()
[COLOR=Green]  if vif:get_altitude() > 100 then
    term.out('It seems we are already launched. Teminating autopilot')
    return
  end[/COLOR]
  term.out('Ascent autopilot initiated.')
  term.out('Attached to: '..vif:get_name())
  term.out('Launch azimuth: '..azimuth*DEG..'deg.')
  term.out('Target altitude: '..orbit_alt*1e-3..'km')
  if vif:get_classname() ~= 'Atlantis' then
    term.out('**** WARNING: Unexpected vessel type')
    term.out('**** '..vif:get_classname())
  end
  ascent(vif)
  if do_oms1==true then
    oms_burn1 (vif,orbit_alt)
    if do_oms2==true then
      oms_burn2 (vif,orbit_alt)
    end
  end
  term.out('Exit launch autopilot.')
end


-- ------------------------------------------------------
-- First part of ascent autopilot.
-- Convers launch to ET separation
-- ------------------------------------------------------

function ascent (v)
  proc.bg(met_counter)  -- launch MET counter

  proc.wait_simdt(3);
  v:set_thrustergrouplevel (THGROUP.MAIN, 1)
  comment = 'Main engine ignition'
  proc.wait_simdt(4) -- SSME ignition

  t0 = oapi.get_simtime()         -- set MET reference
  comment = 'We have liftoff!'

  local dr = 10+(PI/2-azimuth)*DEG*0.1
  if dr < 0 then dr=0 elseif dr > 21 then dr=21 end

  proc.wait_simtime(t0+6)
  comment = 'Start roll programme'
  SetRCS(v, RCSMODE.BANK, -1)  -- roll programme

  proc.wait_simtime(t0+6+dr)
  SetRCS(v, RCSMODE.BANK, 0)   -- end roll programme

  proc.wait_simtime(t0+21)
  term.out('initial pitch')
  SetRCS(v, RCSMODE.PITCH, 1) -- intital pitch to avoid gimbal lock
  proc.wait_simtime(t0+24)
  SetRCS(v, RCSMODE.PITCH, 0)

  proc.wait_simtime(t0+25)
  comment = 'initiate roll and yaw stabilisation'
  bank_prog = proc.bg(setbank,v,PI,500,0)
  yaw_prog  = proc.bg(setyaw,v,azimuth,500,0)
  pitch_prog = proc.bg(ascent_pitch_prog, v)
  comment = 'Start pitch programme'
  -- run the roll/yaw stabilisation and the pitch control
  -- in separate program branches

  -- meanwhile, in the main branch we sit back and wait
  -- until MECO conditions are satisfied

  proc.wait_ge(ped, R_Earth-100e3, v)
  -- wait for perigee > -100km
  proc.wait_ge(apd, R_Earth+154e3, v)
  -- wait for apogee > 154km

  proc.kill(bank_prog)
  proc.kill(yaw_prog)
  proc.kill(pitch_prog)
  -- end the ascent attitude control programs

  term.out('Main engine cut off')
  v:set_thrustergrouplevel (THGROUP.MAIN, 0)

  proc.wait_simdt(10)
  term.out('roll upright')
  setbank(v,0,40,0)
  setpitch(v,0,20,0)

  term.out('jettison tank')
  v:send_bufferedkey(ktable.J)

  proc.wait_simdt(10)
  term.out('RCS for moving away from tank')
  v:set_thrustergrouplevel (THGROUP.ATT_UP,1)
  proc.wait_simdt(2)
  v:set_thrustergrouplevel (THGROUP.ATT_UP,0)

  setpitch(v,0,10,0)
end


[COLOR=Green]-- ------------------------------------------------------
-- Helper method to kill all thrusters
-- ------------------------------------------------------
function kill_all_thrust (v)
  v:set_thrustergrouplevel (THGROUP.MAIN,0)
  -- term.out('THGROUP RESET')
  v:set_thrustergrouplevel (THGROUP.ATT_PITCHUP,0)
  v:set_thrustergrouplevel (THGROUP.ATT_PITCHDOWN,0)
  v:set_thrustergrouplevel (THGROUP.ATT_YAWLEFT,0)
  v:set_thrustergrouplevel (THGROUP.ATT_YAWRIGHT,0)
  v:set_thrustergrouplevel (THGROUP.ATT_BANKLEFT,0)
  v:set_thrustergrouplevel (THGROUP.ATT_BANKRIGHT,0)
  v:set_thrustergrouplevel (THGROUP.ATT_RIGHT,0)
  v:set_thrustergrouplevel (THGROUP.ATT_LEFT,0)
  v:set_thrustergrouplevel (THGROUP.ATT_UP,0)
  v:set_thrustergrouplevel (THGROUP.ATT_DOWN,0)
  v:set_thrustergrouplevel (THGROUP.ATT_FORWARD,0)
  v:set_thrustergrouplevel (THGROUP.ATT_BACK,0)
end[/COLOR]


-- ------------------------------------------------------
-- Second part of ascent autopilot.
-- Convers OMS burn from ET separation to orbit
-- circularisation (not complete yet)
-- ------------------------------------------------------

function oms_burn1 (v,ap_alt)
  term.out('Start OMS1 programme')
  local bank_programme  = proc.bg(setbank,v,0,500,0)
  local yaw_programme   = proc.bg(setyaw,v,azimuth,500,0)
  local pitch_programme = proc.bg(setpitch,v,RAD*15,500,0)
  proc.wait_simdt (20);
  comment = 'OMS burn to raise apogee to '..ap_alt*1e-3..'km'
  term.out ('OMS burn 1 (target apogee '..ap_alt*1e-3..'km)')
  v:set_thrustergrouplevel (THGROUP.MAIN,1)
  proc.wait_ge (apd, R_Earth+ap_alt, v)
  proc.kill(bank_programme)
  proc.kill(yaw_programme)
  proc.kill(pitch_programme)
  [COLOR=Green]kill_all_thrust(v)[/COLOR]
  comment = 'OMS shutdown'
end


-- ------------------------------------------------------
-- Third part of ascent autopilot.
-- Second OMS burn for orbit circularisation
-- ------------------------------------------------------

function oms_burn2 (v,ap_alt)
  term.out ('Start OMS2 programme')
  proc.wait_le (apt, 50, v)
  comment = 'OMS burn for orbit circularisation'
  local att_programme = proc.bg(setdir,v,v.get_progradedir,0,500,0)
  proc.wait_le (apt, 20, v)
  local minalt = apd(v)-R_Earth-5e3
  v:set_thrustergrouplevel (THGROUP.MAIN,1)
  proc.wait_ge (ped, minalt+R_Earth, v)
  proc.kill(att_programme)
  [COLOR=Green]kill_all_thrust(v)[/COLOR]
  comment = 'OMS shutdown'
end

I think this is the least invasive change to fix that problem.
I had to use vif:get_altitude() 'cause vif:get_flight_status() is currently not exposed at lua level. Nevertheless this condition (alt > 100) also does the trick

Anyone here with better contact to martins that can ask him to introduce this patch to the next release?

/Cheers, Kuddel

DrSolidRocketMotor · Jun 23, 2012

IronRain said:
I've tried your scenario and the only thing I noticed was that the OMS firing which is indeed solved by pressing the * key.

Have you tried a clean installation?

I've tried several clean installations....on different partitions....even on different physical hard drives....no change -- it does the same behavior in each case.

---------- Post added at 03:15 AM ---------- Previous post was at 03:03 AM ----------

Urwumpe said:
Uninitialized memory is no corrupted operating system, but plain sloppy programming.

In C++, all memory that your program allocates is not initialized. Effectively random data, it is what was once stored in the memory locations before your program was loaded there.

If such an uninitialized variable is used, anything can happen.

Too look closer at your problem, this line is interesting:

This line describes the state of the RCS thrusters at the moment your scenario was saved. instead of being plain zero, you have minimal activity there. Possibly caused by a joystick that wasn't centered properly with too little deadbands.

Next, your scenario loads the atlantis launch autopilot script. Possible next source for problems. But I would need to read the Lua file for telling you anything about its behavior on a relaunch. I suspect, it does not like being activated at the wrong time.

I agree -- I noticed the THLEVEL line -- for one test I even removed the line from the file, since I noticed that it was not present in the Demo scenario, so I guessed that it was not absolutely required, and might reset RCS thrust levels to zero -- unfortunately, it didn't work.

Also, I'm not using a joystick on my computer.

This is the first time I've even heard of the lua file -- I have no idea if I'm using it or not.

PhantomCruiser · Jun 23, 2012

Even when using kuddel's scenario?

DrSolidRocketMotor · Jun 23, 2012

Urwumpe said:
Uninitialized memory is no corrupted operating system, but plain sloppy programming.

In C++, all memory that your program allocates is not initialized. Effectively random data, it is what was once stored in the memory locations before your program was loaded there.

If such an uninitialized variable is used, anything can happen.

Too look closer at your problem, this line is interesting:

This line describes the state of the RCS thrusters at the moment your scenario was saved. instead of being plain zero, you have minimal activity there. Possibly caused by a joystick that wasn't centered properly with too little deadbands.

Next, your scenario loads the atlantis launch autopilot script. Possible next source for problems. But I would need to read the Lua file for telling you anything about its behavior on a relaunch. I suspect, it does not like being activated at the wrong time.

Thanks for your input! I will get the lua file for you -- I'm guessing, perhaps a Demo file is not meant to be restarted?

---------- Post added at 03:23 AM ---------- Previous post was at 03:20 AM ----------

PhantomCruiser said:
Even when using kuddel's scenario?

No -- I haven't tried that one yet....I'll be testing that next.

---------- Post added at 03:26 AM ---------- Previous post was at 03:23 AM ----------

Urwumpe said:
Did you have the Lua module activated?

Lua module? I'll have to reread my documentation on that one.

---------- Post added at 03:30 AM ---------- Previous post was at 03:26 AM ----------

kuddel said:

Hello DrSolidRocketMotor,

after some more people are involved (see, your're not alone

) I'll come back to you.

would you try this scenario, please?

Code:

BEGIN_DESC
test state (with 'zeroed' THLEVEL & removed 'atlantis_launch' script)
END_DESC

BEGIN_ENVIRONMENT
  System Sol
  Date MJD 51984.1388440802
END_ENVIRONMENT

BEGIN_FOCUS
  Ship STS-101
END_FOCUS

BEGIN_CAMERA
  TARGET STS-101
  MODE Extern
  POS 1.85 148.78 -20.41
  TRACKMODE GlobalFrame
  FOV 50.00
  BEGIN_PRESET
    Cockpit:STS-101:40.00
    Ground:STS-101:40.00:Earth -80.62339 28.61960 110.00
    Track:STS-101:50.00:RELATIVE 2.890 -0.009 -1.229
    Ground:STS-101:10.00:Earth -80.65298 28.58028 20.00
    Track:ISS:40.00:RELATIVE 1.983 -0.474 -0.522
    Track:Earth:40.00:GLOBAL 2.896 2.132 -0.331
  END_PRESET
END_CAMERA

BEGIN_HUD
  TYPE Orbit
  REF AUTO
END_HUD

BEGIN_MFD Left
  TYPE Surface
  SPDMODE 4
END_MFD

BEGIN_MFD Right
  TYPE Map
  REF Earth
  BTARGET Cape Canaveral
  ZOOM 4
END_MFD

BEGIN_SHIPS
ISS:ProjectAlpha_ISS
  STATUS Orbiting Earth
  RPOS 6529571.29 266861.69 -1636161.01
  RVEL 798.446 -7399.909 1951.188
  AROT 16.53 24.08 -120.76
  AFCMODE 7
  PRPLEVEL 0:1.000000
  IDS 0:1 100 1:2 100 2:3 100 3:4 100 4:5 100
  NAVFREQ 0 0
  XPDR 466
END
Mir:Mir
  STATUS Orbiting Earth
  RPOS 5449213.78 420290.69 3809007.47
  RVEL -4429.253 220.578 6342.594
  AROT -135.04 68.66 64.66
  VROT -0.04 -0.02 0.05
  AFCMODE 7
  IDS 0:540 100 1:542 100 2:544 100
  XPDR 482
END
Luna-OB1:Wheel
  STATUS Orbiting Moon
  RPOS 1025480.89 1989021.24 1097.22
  RVEL -1315.701 678.211 0.271
  AROT -0.02 0.00 -12.39
  VROT 0.00 0.00 10.00
  AFCMODE 7
  IDS 0:560 100 1:564 100
  XPDR 494
END
STS-101:Atlantis
  STATUS Orbiting Earth
  RPOS 5158866.63 3582197.07 -2445768.14
  RVEL 4894.775 -4419.568 3917.659
  AROT -24.44 -84.55 -25.59
  AFCMODE 7
  PRPLEVEL 0:0.636457
  THLEVEL 4:0.000000 5:0.000000 8:0.000000 9:0.000000 12:0.000000 13:0.000000
  NAVFREQ 0 0
  CONFIGURATION 3
  GEAR 0 0.0000
  ARM_STATUS 0.5000 0.0000 0.0000 0.5000 0.5000 0.5000
  SAT_OFS_X 0.000000
  SAT_OFS_Y 0.000000
  SAT_OFS_Z 0.000000
  CARGO_STATIC_MESH Carina_cradle
  CARGO_STATIC_OFS 0.000000 -1.650000 0.050000
  CARGODOOR 1 1.0000
  KUBAND 1 1.0000
END
Carina:Carina
  STATUS Orbiting Earth
  RPOS 5158866.63 3582197.07 -2445768.14
  RVEL 4894.775 -4419.568 3917.659
  AROT -24.44 -84.55 -25.59
  ATTACHED 0:0,STS-101
  AFCMODE 7
  NAVFREQ 0 0
END
SH-02:ShuttleA
  STATUS Landed Earth
  BASE Cape Canaveral:5
  POS -80.6745292 28.5197208
  HEADING 100.00
  AFCMODE 7
  PRPLEVEL 0:1.000000 1:1.000000
  NAVFREQ 0 0
  XPDR 0
  PODANGLE 0.0000 0.0000
  DOCKSTATE 0 0.0000
  AIRLOCK 0 0.0000
  GEAR 0 0.0000
  PAYLOAD MASS 4.0 0
END
STS-101-SRB1:Atlantis_SRB
  STATUS Landed Earth
  POS -76.3628596 28.5416384
  HEADING 329.17
  AFCMODE 7
END
STS-101-SRB2:Atlantis_SRB
  STATUS Landed Earth
  POS -76.3577402 28.4747359
  HEADING 210.17
  AFCMODE 7
END
STS-101-Tank:Atlantis_Tank
  STATUS Landed Earth
  POS 45.4401311 -18.6357525
  HEADING 263.92
  AFCMODE 7
END
END_SHIPS

(you can also take the attached scn-file)

It it the same as yours, except that

The THLEVEL values are 'zeroed' (proposal by Urwumpe)
Removed 'atlantis_launch' script from starting (IronRains input)

I'm pretty sure that this scenario will not fire any thrusters or the SSMEs.

Have a nice weekend,

Kuddel

I will run a test with your file....thanks very kindly for your help!

DrSolidRocketMotor · Jun 29, 2012

kuddel said:

Hello DrSolidRocketMotor,

after some more people are involved (see, your're not alone

) I'll come back to you.

would you try this scenario, please?

Code:

BEGIN_DESC
test state (with 'zeroed' THLEVEL & removed 'atlantis_launch' script)
END_DESC

BEGIN_ENVIRONMENT
  System Sol
  Date MJD 51984.1388440802
END_ENVIRONMENT

BEGIN_FOCUS
  Ship STS-101
END_FOCUS

BEGIN_CAMERA
  TARGET STS-101
  MODE Extern
  POS 1.85 148.78 -20.41
  TRACKMODE GlobalFrame
  FOV 50.00
  BEGIN_PRESET
    Cockpit:STS-101:40.00
    Ground:STS-101:40.00:Earth -80.62339 28.61960 110.00
    Track:STS-101:50.00:RELATIVE 2.890 -0.009 -1.229
    Ground:STS-101:10.00:Earth -80.65298 28.58028 20.00
    Track:ISS:40.00:RELATIVE 1.983 -0.474 -0.522
    Track:Earth:40.00:GLOBAL 2.896 2.132 -0.331
  END_PRESET
END_CAMERA

BEGIN_HUD
  TYPE Orbit
  REF AUTO
END_HUD

BEGIN_MFD Left
  TYPE Surface
  SPDMODE 4
END_MFD

BEGIN_MFD Right
  TYPE Map
  REF Earth
  BTARGET Cape Canaveral
  ZOOM 4
END_MFD

BEGIN_SHIPS
ISS:ProjectAlpha_ISS
  STATUS Orbiting Earth
  RPOS 6529571.29 266861.69 -1636161.01
  RVEL 798.446 -7399.909 1951.188
  AROT 16.53 24.08 -120.76
  AFCMODE 7
  PRPLEVEL 0:1.000000
  IDS 0:1 100 1:2 100 2:3 100 3:4 100 4:5 100
  NAVFREQ 0 0
  XPDR 466
END
Mir:Mir
  STATUS Orbiting Earth
  RPOS 5449213.78 420290.69 3809007.47
  RVEL -4429.253 220.578 6342.594
  AROT -135.04 68.66 64.66
  VROT -0.04 -0.02 0.05
  AFCMODE 7
  IDS 0:540 100 1:542 100 2:544 100
  XPDR 482
END
Luna-OB1:Wheel
  STATUS Orbiting Moon
  RPOS 1025480.89 1989021.24 1097.22
  RVEL -1315.701 678.211 0.271
  AROT -0.02 0.00 -12.39
  VROT 0.00 0.00 10.00
  AFCMODE 7
  IDS 0:560 100 1:564 100
  XPDR 494
END
STS-101:Atlantis
  STATUS Orbiting Earth
  RPOS 5158866.63 3582197.07 -2445768.14
  RVEL 4894.775 -4419.568 3917.659
  AROT -24.44 -84.55 -25.59
  AFCMODE 7
  PRPLEVEL 0:0.636457
  THLEVEL 4:0.000000 5:0.000000 8:0.000000 9:0.000000 12:0.000000 13:0.000000
  NAVFREQ 0 0
  CONFIGURATION 3
  GEAR 0 0.0000
  ARM_STATUS 0.5000 0.0000 0.0000 0.5000 0.5000 0.5000
  SAT_OFS_X 0.000000
  SAT_OFS_Y 0.000000
  SAT_OFS_Z 0.000000
  CARGO_STATIC_MESH Carina_cradle
  CARGO_STATIC_OFS 0.000000 -1.650000 0.050000
  CARGODOOR 1 1.0000
  KUBAND 1 1.0000
END
Carina:Carina
  STATUS Orbiting Earth
  RPOS 5158866.63 3582197.07 -2445768.14
  RVEL 4894.775 -4419.568 3917.659
  AROT -24.44 -84.55 -25.59
  ATTACHED 0:0,STS-101
  AFCMODE 7
  NAVFREQ 0 0
END
SH-02:ShuttleA
  STATUS Landed Earth
  BASE Cape Canaveral:5
  POS -80.6745292 28.5197208
  HEADING 100.00
  AFCMODE 7
  PRPLEVEL 0:1.000000 1:1.000000
  NAVFREQ 0 0
  XPDR 0
  PODANGLE 0.0000 0.0000
  DOCKSTATE 0 0.0000
  AIRLOCK 0 0.0000
  GEAR 0 0.0000
  PAYLOAD MASS 4.0 0
END
STS-101-SRB1:Atlantis_SRB
  STATUS Landed Earth
  POS -76.3628596 28.5416384
  HEADING 329.17
  AFCMODE 7
END
STS-101-SRB2:Atlantis_SRB
  STATUS Landed Earth
  POS -76.3577402 28.4747359
  HEADING 210.17
  AFCMODE 7
END
STS-101-Tank:Atlantis_Tank
  STATUS Landed Earth
  POS 45.4401311 -18.6357525
  HEADING 263.92
  AFCMODE 7
END
END_SHIPS

(you can also take the attached scn-file)

It it the same as yours, except that

The THLEVEL values are 'zeroed' (proposal by Urwumpe)
Removed 'atlantis_launch' script from starting (IronRains input)

I'm pretty sure that this scenario will not fire any thrusters or the SSMEs.

Have a nice weekend,

Kuddel

Hello again -- sorry for the late response, it's been a busy week......my kind thanks to Urwumpe, IronRain, and kuddel......I tried your modified scenario file and launch script......it worked like a charm! Absolutely no problems now! I'm beginning to feel like a real beta tester.

I'm wondering everyone....will the remaining spacecraft included in the default program require similar code changes to work in the same manner? (Not that I'm trying to create more work for anyone!)

As I previously mentioned, were these "demo" scenarios meant to be used in this manner?

kuddel · Jun 29, 2012

DrSolidRocketMotor said:
Hello again -- sorry for the late response, it's been a busy week...

No problem, some of us do have a real life, too

DrSolidRocketMotor said:
...my kind thanks to Urwumpe, IronRain, and kuddel......I tried your modified scenario file and launch script......it worked like a charm! Absolutely no problems now! I'm beginning to feel like a real beta tester.

You're welcome.
The 'issue' you've discovered was not found by anyone before (or at least nobody did ask about it). Thanks again -for really trying the proposed solutions. Not everybody does it that way. I really appreciate that kind behavior.

DrSolidRocketMotor said:
I'm wondering everyone....will the remaining spacecraft included in the default program require similar code changes to work in the same manner? (Not that I'm trying to create more work for anyone!)

I don't think so. As you already said yourself (below) these "demo" scenarios were never saved and re-opened by anyone before. Nevertheless, they should allow you to do that.
When I find some time I will look over some of the other "demo" scenarios and check whether they are affected by this kind of problem as well.

DrSolidRocketMotor said:
As I previously mentioned, were these "demo" scenarios meant to be used in this manner?

I don't think anybody did think about this before

Happy orbiting,
Kuddel

Problem Atlantis Space Shuttle RCS Thrusters Stuck 'On' When Restarting Scenario

DrSolidRocketMotor

New member

kuddel

Donator

Attachments

DrSolidRocketMotor

New member

kuddel

Donator

DrSolidRocketMotor

New member

Urwumpe

Not funny anymore

IronRain

The One and Only (AFAIK)

Urwumpe

Not funny anymore

IronRain

The One and Only (AFAIK)

kuddel

Donator

Attachments

kuddel

Donator

Attachments

DrSolidRocketMotor

New member

PhantomCruiser

Wanderer

DrSolidRocketMotor

New member

DrSolidRocketMotor

New member

kuddel

Donator

Similar threads