Space Shuttle Ultra 1.25 Revision B development

[SiameseCat]

Checked in the csv file for the basic aerodynamics (Config/SSU_Aero.csv).

The original data is at http://ntrs.nasa.gov/archive/nasa/casi.ntrs.nasa.gov/19850070642_1985070642.pdf

The csv file format is described below; basically each block of 4 lines has the mach and AOA values followed by a line for each of the normal, axial and moment values. Note that the blocks MUST go in order of increasing AOA, then mach. It's probably also a good idea to post what you're doing, so we don't do the same sections of the file. I'm currently working on the elevon file.

 

[Poscik]

I'll do Body Flap.

---------- Post added at 04:19 PM ---------- Previous post was at 04:59 AM ----------

Finally finished csv for Body Flap. I was typing this goddamn table whole day Maybe I'll win in lottery this time I suggest you to write simple checker(or I'll do this) for that files. It was veeery easy to type . instead of , and vice versa. Also had some problems with "is it 5 or 6?", but I think there are no mistakes Anyway, it is worth to check if those files are correct. I'll PM you my csv.

 

[SiameseCat]

Got your file; thanks.

The formatting is checked on loading, so any . vs , errors should be caught. You're not the only one who had problems distinguishing between numbers either; both 5/6 and 8/9 can be hard to distinguish sometimes.

 

[Poscik]

Thanks for checking in Attitude Control Code documentation. It explains a lot.

 

[SiameseCat]

Checked in the elevon and body flap files. The main thing left to do is complete the data files; the elevon and basic aerodynamic files only have data for M<1.

 

[DaveS]

If you haven't already noticed, I have checked in some SRB things that really improves stuff there! The biggest change is the now near-100% accurate SRB sep sequence! I've compared ours with STS-114/LF1/RTF2.1 and everything matches up very very closely now. The problem all along was the positions and thrust vector of the BSMs and they're now correct.

I've also checked in a trimming to the Ku antenna drive time. It's now down to ~19 seconds which is the actual observed drive time.

 

[SiameseCat]

Great to have the SRB sep finally working. I'm in the process of adding the high-mach values to the aerodynamics csv files.

 

[DaveS]

Just checking here: Do we currently simulate random MPS failures?

Just asking because I just experienced a RSLS abort due to a ME-3 failure at T-1.98 seconds in a STS-114 launch scenario I have created!


Edit:
If we are indeed simulating random MPS failures, then once the aerodynamics have been completed, the next order of business should be implementing proper RSLS abort pad sequences(activating the aft water deluge, extending the OAA and GVA and ET propellant drain).

 

[SiameseCat]

I don't think we simulate RSLS failues, but I'll take a look at the code. Are you sure the switch settings were correct?

---------- Post added at 08:48 AM ---------- Previous post was at 08:44 AM ----------

We don't simulate random failures; the only way to trigger a failure is with a line in the scenario file.

 

[DaveS]

I don't think we simulate RSLS failues, but I'll take a look at the code. Are you sure the switch settings were correct?

Pretty sure. Checked them after the abort as we don't currently simulate any post-abort procedures.

I'll run the scenario again and see if it is repeatable.

---------- Post added at 02:18 PM ---------- Previous post was at 02:07 PM ----------

Tried the scenario again, no RSLS abort this time. So maybe I did configure ME-3 incorrectly last time.

 

[DaveS]

Can someone confirm that we use the method recommended by jarmonik to load the mission file specified orbiter texture?

 

[Urwumpe]

Can someone confirm that we use the method recommended by jarmonik to load the mission file specified orbiter texture?

I think we can be sure that we don't do that...it is a 2010 feature.

 

[DaveS]

I think we can be sure that we don't do that...it is a 2010 feature.

OK. So maybe we can update the function to use it? To make it more compatible with the OVP clients? The D3D9Client is really an improvement over the default D3D7 client.

 

[Urwumpe]

OK. So maybe we can update the function to use it? To make it more compatible with the OVP clients? The D3D9Client is really an improvement over the default D3D7 client.

Sure "we" can... I just don't know when I can do it, which has me keep a low profile here. We just need to replace the current 2006 function calls by the extended versions of 2010, which give more information to orbiter about what we intend. The current version should be using a similar function.

 

[SiameseCat]

Updated the code so it should work with other graphics clients. It works with the standard D3D7 client, but I haven't tested it with the D3D9 client.

 

[DaveS]

Updated the code so it should work with other graphics clients. It works with the standard D3D7 client, but I haven't tested it with the D3D9 client.

Thanks. It works nicely now!

 

[Poscik]

SC could you tell me which table are you typing now? I can type one more if you want.

 

[SiameseCat]

I'm doing the elevons at the moment. It would be great if you can finish the basic table (SSU_Aero.csv). The entries for M0.4, M0.6 and above M10.0, but I haven't added the values in-between yet. The current version of the file has been checked in.

 

[Poscik]

Sure. You'll receive complete Basic Table tomorrow.

---------- Post added 11-04-10 at 07:11 PM ---------- Previous post was 11-03-10 at 10:52 PM ----------

File may not be ready today. I didn't suppose that I have to type much more data than for body flap.

---------- Post added at 11:28 PM ---------- Previous post was at 07:11 PM ----------

I finished typing normal force, and axial up to mach 3.

 

[tl8]

I was bored and started converting the flight checklist to html.

Here is the launch checklist for you to look at and comment on.

http://dl.dropbox.com/u/3550991/SSU Launch Checklist.html

Basic legend for Event Type:
S - Switch
O - Observation
SE - Scenario Enables
K - Key Pad
A - Autopilot