SSU V1.25 Release

[Poscik]

Hi! I will return to my "turning" after touchdown problem. So, I attached scenario which I flown few minutes ago. I made KSC re-entry partially using AFCS. I was approaching RWY15 from North-West direction and I made L OVHD HAC. At about 1800m/s of speed, I disengaged rolling in AFCS and flown with pitch hold only. At about 20km of altitude, I disengaged whole AFCS and I flown HAC and touchdown manually. And after touchdown, when chute deployed, orbiter immidiately turned right. I don't know why, but according to SiameseCats reply for my last post about this behaviour, built-in SpaceShuttleUltra scenarios works fine for me too, for example Space Shuttle Ultra/Atlantis Final Approach.scn

Maybe I missed something? I only know, that I missed Air Data Probes deployment, but I think that couldn't take affect on this behaviour.

 

[DaveS]

I wouldn't be surprised if AFCS had anything to do with your weired behavior of the orbiter post-touchdown. I certainly doesn't experience it.

 

[Poscik]

AFCS was disengaged when I touched down.
And this is my screen of approach:
http://i42.tinypic.com/23j3k2x.jpg

On this screen you can see, that AFCS is completely disengaged.

Oh, and I forgot to attach scenario I flown.
View attachment STS-100 one day to land.scn

 

[zerofay32]

I have had this happen once in about ten entries with Shuttle Fleet. At WOW the orbiter drifts and tilts to one side or the other with no input on the brakes and with only back pressure on the stick to keep the nose up untill the proper ground speed. Sense the same thing happends with both shuttles the issue is most likely with AFCS. I also disengage the AFCS at TAEM but for some reason AFCS still does something to cause this. I have never had this happen on any manual entries. Hope this helps.

Zerofay32

 

[Poscik]

I made small test. On Space Shuttle Ultra/Atlantis Final Approach.scn I engaged AFCS for few seconds and turned it off. But I didn't have that strange turn. Everything was normal.

 

[Donamy]

We need a release so I can start releasing STS mission payloads for the SSU.

 

[SiameseCat]

I agree. Last SSU release was over a year ago. What more needs to be done before release?

 

[DaveS]

I agree. Last SSU release was over a year ago. What more needs to be done before release?

Then we have a few things that needs fixing:
-Stack stays lit after lift-off during the night
-KU band antenna talkback on R13L shows "OP" instead of "DPY"
-RAD panel talkbacks: Latch talkbacks "OP" instead of "REL" and actual RAD talkbacks "OP" instead of "DPY".
-Ascent AP doesn't work if you quit during Stage 1 ascent and later re-enter the scenario. It goes conkers at MM103+10 seconds.

That's the only bugs I can think of right now. Anything else?

 

[SiameseCat]

Talkback problems are simple to fix. It shouldn't be too much trouble to turn the lighting off, either.
For the moment, I'd prefer to leave the ascent code alone. I think it's fairly reasonable to assume that the period from T-31s to MECO will be run without quitting Orbiter.

 

[DaveS]

Talkback problems are simple to fix. It shouldn't be too much trouble to turn the lighting off, either.
For the moment, I'd prefer to leave the ascent code alone. I think it's fairly reasonable to assume that the period from T-31s to MECO will be run without quitting Orbiter.

Another thing is texture for the ROFIs, currently we don't have any texture defined for them, but I think the regular Contrail2 would do it.

And could we have some simple utility to calculate MECO velocity based on MECO altitude and MECO apogee? I think that the utility would be an essential tool as most of us aren't math-savy enough(I sure isn't!) to calculate that on their own.

 

[tblaxland]

And could we have some simple utility to calculate MECO velocity based on MECO altitude and MECO apogee? I think that the utility would be an essential tool as most of us aren't math-savy enough(I sure isn't!) to calculate that on their own.

Would an Excel spreadsheet be suitable? It is not too hard to calculate. Is there a there a typical value for perigee? 40km or so?

 

[DaveS]

Would an Excel spreadsheet be suitable? It is not too hard to calculate. Is there a there a typical value for perigee? 40km or so?

Yes, we use about 60 km for MECO perigee to ensure ET re-entry. Is there any reason why a C++ utility like the standard date.exe utility couldn't be done?

 

[tblaxland]

Is there any reason why a C++ utility like the standard date.exe utility couldn't be done?

No, just a spreadsheet is easier and therefore quicker

 

[DaveS]

No, just a spreadsheet is easier and therefore quicker

OK, then go right ahead. Just wondered what the pro's/con's of each was.

 

[tblaxland]

OK, then go right ahead. Just wondered what the pro's/con's of each was.

Done, see attached.

EDIT: zip also includes ODS format as not everyone may be able to use XLS.

 

[DaveS]

tblaxland: Thanks! Works nicely here!

A few other bugs that needs fixing before release:
-ITEM 27 in MM104 makes the DAP in AUTO manuever to an incorrect attitude for burn
-When entering MM201 from any other mode, it's by default blank and need a RESUME keypress to show
-Panels A8 and A7 switches can be seen from the payload bay cameras.

 

[Urwumpe]

Should the mission files go into this release or can it get delayed into the next? I could debug and commit them today.

---------- Post added at 12:44 PM ---------- Previous post was at 10:16 AM ----------

Question: Do you want individual functions for querying the MECO parameters or would you prefer grouping such information into a MECOTARGETDATA structure?

 

[Pilot7893]

Someone should mod the ET to include spacebat!

 

[Urwumpe]

Someone should mod the ET to include spacebat!

Forget it!

 

[Donamy]

OK, then go right ahead. Just wondered what the pro's/con's of each was.

Con- I can't open .xls