Space Shuttle Ultra development thread
- Thread starter DaveS
- Start date
Maximum down on each nozzles, which is 10.5°s.
It's part of the Post-landing procedures in the Generic Entry Flight Data File. It's done by the PLT by first performing the BODYFLAP SET procedure where the bodyflap is moved to maximum down angle to provide clearance for engines 2 and 3.
Then the movement of the nozzles is done by the PLT in the SSME REPO procedure.
Here's the link to generic Entry FDF: http://www.nasa.gov/centers/johnson/pdf/203839main_ENT_G_H_4.pdf.
It's on page 5-7.
Yes, but the only time they go to maximum down is when the orbiter is unpowered and the ferrry flight elevon locks aren't installed.
No and yes. The bodyflap is always locked in place but the rudder isn't.
No, I believe it's locked then.
Urwumpe
Not funny anymore
- Joined
- Feb 6, 2008
- Messages
- 38,965
- Reaction score
- 3,937
- Points
- 203
- Location
- Wolfsburg
- Preferred Pronouns
- Sire
Ok, Air Data Probe Animation and the fixed Panel C3 are done.
Next I want to do: the 4 ADTAs and a experimental implementation of the FF MDMs. I am not sure if my model of the MDMs will work, but based on the available information, it could be as close as we can get without stressing the freedom of information act.
Next I want to do: the 4 ADTAs and a experimental implementation of the FF MDMs. I am not sure if my model of the MDMs will work, but based on the available information, it could be as close as we can get without stressing the freedom of information act.
C3PO
Addon Developer
- Joined
- Feb 11, 2008
- Messages
- 2,604
- Reaction score
- 31
- Points
- 63
I've used a similar way to implement spoilerons on my [ame="http://www.orbithangar.com/searchid.php?ID=933"]DG-Carrier[/ame].
It uses range 0-0.5 on the left, and 0.5-1 on the right. (Well, it's a bit more complicated, but you can see what I mean)
There are some good examples provided in the SC3-package. I've spent quite some time reverse engineering them.
I used to experiment quite a lot with animations in SC3 (and the older versions) Mostly panel deployment. The ATV that comes with Hendo's Ariane 5 was quite hard to animate. If you look closely, the animations aren't linear. Almost all computer generated graphics have way too linear movements IMHO.
Last edited:
Donamy
Addon Developer
I've used a similar way to implement spoilerons on my DG-Carrier.
It uses range 0-0.5 on the left, and 0.5-1 on the right. (Well, it's a bit more complicated, but you can see what I mean)
There are some good examples provided in the SC3-package. I've spent quite some time reverse engineering them.
I used to experiment quite a lot with animations in SC3 (and the older versions) Mostly panel deployment. The ATV that comes with Hendo's Ariane 5 was quite hard to animate. If you look closely, the animations aren't linear. Almost all computer generated graphics have way too linear movements IMHO.
I'll have to check them out, I'm having a hard time doing the animations for the ODS docking ring.
Donamy
Addon Developer
SiameseCat
Addon Developer
I finally finished the RMS translation work.
Now I just need to add rotation capability.
Now I just need to add rotation capability.
Donamy
Addon Developer
I finally finished the RMS translation work.
Now I just need to add rotation capability.
Sounds like you've got it licked. Can't wait to use it.
Urwumpe
Not funny anymore
- Joined
- Feb 6, 2008
- Messages
- 38,965
- Reaction score
- 3,937
- Points
- 203
- Location
- Wolfsburg
- Preferred Pronouns
- Sire
The flight-critical forward Multiplexers-Demultiplexers.
The Shuttle has 4 of these (FF1 - FF4), which are all equal in their hardware and software set-up. They form a node in the computer network inside the Shuttle and send commands, issued by the GPCs over the Flight-Critical buses, to the hardware and collect and format data for the GPCs.
They have at least 13 input/output cards out of 16 possible. Inside the MDM are two bus interface units called MIA, each connected to its own Sequence Control Unit, which is roughly a tiny dictionary telling the MDM how to reply to a request from the GPC. The Sequence control unit picks up to 31 16 bit values from the IO cards and put them into one reply frame for each poll of the GPC.
Each IO card can be one out of nine different types:
- Discrete output high (DOH), 28 volts, three l6-bit channels
- Discrete output low (DOL), 5 volts, three l6-bit channels
- Discrete input high (DIH), 28 volts, three l6-bit channels
- Discrete input low (DIL), 5 volts, three l6-bit channels
- Analog output differential (AOD), 16 channels
- Analog input differential (AID), 16 channels
- Analog input single-ended (AIS), 32 channels
- Serial input/output (SIO), four channels
- Tacan/radar altimeter (special-purpose I/O)
One card for example could be used for issuing commands to the RCS - likely a 28V DIH card with three 16-bit channels (=48 possible discretes)
The SIO card on the other hand seems to be again based on the Shuttle Bus - it seems to be the type of card used for connecting one FF MDM to one ADTA (Air Data Transducer Assembly), which in turn is connected to a air data probe over pneumatic tubes.
FF1 and FF3 are connected to the left probe.
FF2 and FF4 are connected to the right probe.
Now the important reasons for implementing this stuff so complex are:
- Failures and pilot errors - when you power down the wrong MDM, you have no RCS anymore. Also we can simulate bus failures simpler that way.
- Simpler to implement the redundant or common set of GPCs than any "evil hack" attempt to implement this inside the GPCs.
Get this error when trying to compile the latest sources:
Seems that you haven't checked in the latest version of a meshres.h file.
Code:
[SIZE=1]
.\PanelO3.cpp(194) : error C2065: 'GRP_O3S12_VC' : undeclared identifier
[/SIZE]
