SSU V1.25 Release

Status
Not open for further replies.
Neither have I. No attachment issues here.

Still possible that I have a bug there, which only manifests on few selected machines. I remember vaguely the attachment definition code, it was quickly written. Will investigate this in the code, just to be sure. When I have done the mission file handling, this code would need to be touched anyway.

---------- Post added at 11:01 AM ---------- Previous post was at 10:24 AM ----------

Found (and printed) this one:

"Space shuttle Solid Rocket Booster (SRB) separation"

http://ntrs.nasa.gov/archive/nasa/casi.ntrs.nasa.gov/19760006102_1976006102.pdf

Contains not only the exact location of the BSMs, but also the full timing of the separation sequence and contains test data which we can use for improving our own implementation.
 

Found (and printed) this one:

"Space shuttle Solid Rocket Booster (SRB) separation"

http://ntrs.nasa.gov/archive/nasa/casi.ntrs.nasa.gov/19760006102_1976006102.pdf

Contains not only the exact location of the BSMs, but also the full timing of the separation sequence and contains test data which we can use for improving our own implementation.
Thanks for finding this document! It's very nice!

Some prelim findings based on the data given on page 25:

Code:
Real FWD BSM pitch angle relative to horizontal: 40°s
SSU FWD BSM pitch angle relative to horizontal: 16°s
Delta angle: [B]24[/B]°s!

Real FWD BSM rotational angle around the Frustrum: 20°
SSU FWD BSM rotational angle around the Frustrum: 36°s
Delta angle: [B]16[/B]°s!
So, not strange that we have issues with SRB sep with these deltas! I'll continue the measurements of the aft BSMs and see what kind of deltas we have there.
 
I can no longer enter anything in CRT MFD. I'm in MM201, I press ITEM 15 + 90 EXEC and nothing happens, or ITEM 19 EXEC, no asterisk.

---------- Post added at 12:59 AM ---------- Previous post was Yesterday at 11:19 PM ----------

I guess only OPS 201 has the problem, reloading the last version of MGAtlants.dll fixes the bug.
 
Item entry using the keyboard seems to be working for me. I'm not sure if this is what you're referring to, but CRT MFD can not be used for data entry anymore (this was actually removed last year).
 
I'm using the VC keypad, and pressing the keys in MM201 have no effect, DaveS has reported to me as having the same problem.
 
Does the debug string display anything after you enter the data and press EXEC? You should see 'Item Input:' followed by the item number entered.

I still haven't been able to reproduce this.
 
Does the debug string display anything after you enter the data and press EXEC? You should see 'Item Input:' followed by the item number entered.

I still haven't been able to reproduce this.
That line appears but the actual values on the MM201 screen doesn't update. It remains set at 0 if you for example enter ITEM 6+90 EXEC.
 
The SPEC 20 screen does not work for me either.

When I press ITEM 14+3 EXEC, it displays on the screen, but EXEC does not appear in the debug line until I press EXEC a second time. When I press RESUME, the debug line says "9 (null) (null)", when I press CLEAR, the screen clears, but not the debug screen.
 
Do the other MMs work? There's nothing in the input handling code which is really dependent on the major mode.

Donamy: You only need to press EXEC once. The debug string is used to output debugging info from the input handling functions, so it won't display the same things as the CRT scratch pad.

---------- Post added at 08:35 AM ---------- Previous post was at 08:29 AM ----------

MM201 SPEC 20 is not working for me. The main MM201 screen still seems to work. The OMS MNVR display also seems to be working.

---------- Post added at 08:59 AM ---------- Previous post was at 08:35 AM ----------

I fixed a bug in the IDP code; see if this helps.
 
To be clear, I know how the screens work, they work fine with a previous build. I'm just letting you know, how the keys are working with the new build. The debug line doesn't work the same as before. Is this by design ?

---------- Post added at 03:09 PM ---------- Previous post was at 03:07 PM ----------

SC, could you send me the new MGAtlantis.dll ?
 
The behaviour of the debug line was changed fairly recently. It doesn't display the scratch pad line anymore.
 
I see, could that maybe have caused the problem ?
 
Bug is now fixed, at least on my end.
 
Bug is now fixed for me also !! :)
 
Great. In case anyone is interested, the bug was in determining the IDP being used for data entry.
 
Status
Not open for further replies.
Back
Top