SSU Development Thread (2.0 to 3.0)

Status
Not open for further replies.
If there was another position after the existing one, over panel R2, that would be great... not sure if orbiter allows that.
 
If there was another position after the existing one, over panel R2, that would be great... not sure if orbiter allows that.

I wonder if we could use Pilot seat UP for setting up for R4. Currently this moves us to the center line camera of the ODS.

Alternatively: PILOT, Right, Panel R4, RIGHT, Mission Specialist Workstation
 
Last edited:
If there was another position after the existing one, over panel R2, that would be great... not sure if orbiter allows that.
It does. Each position is independent from another. We just have set up so that you can move to the R2 panel from the PLT position.
 
Anybody having a set of coordinates ready that I can use?
 
Anybody having a set of coordinates ready that I can use?
Try these: 1.30, 2.06, 14.03. Should place the view above R2 and forward of R4.
 
I used some try and error to get some useful coordinates, very similar to your suggestions. Checked the changes in.

Go right from PLT to view panel R4
Go left from CDR to view panel L4

---------- Post added at 11:07 PM ---------- Previous post was at 09:55 PM ----------

Still no chance to get to MM S202 for Payload bay opening.

Or SPEC 0/OPS 0: GPC MEMORY
Or SPEC 23: RCS

Still some work to do here.
 
I used some try and error to get some useful coordinates, very similar to your suggestions. Checked the changes in.

Go right from PLT to view panel R4
Go left from CDR to view panel L4

---------- Post added at 11:07 PM ---------- Previous post was at 09:55 PM ----------

Still no chance to get to MM S202 for Payload bay opening.

Or SPEC 0/OPS 0: GPC MEMORY
Or SPEC 23: RCS

Still some work to do here.
How do you mean? Could you explain a bit more closely?
 
How do you mean? Could you explain a bit more closely?

I am following the POST INSERTION checklist. As you said above about my issues. And just noting loudly which especially important steps in this checklist are NOT working.

If we are going to make an release, it should work at least "ok" - not have all those tiny nuts and bolts looking good.

Maybe you should do the same as well, then you would also notice the issues.
 
I am following the POST INSERTION checklist. As you said above about my issues. And just noting loudly which especially important steps in this checklist are NOT working.

If we are going to make an release, it should work at least "ok" - not have all those tiny nuts and bolts looking good.
OK. Yes, we're missing a lot of the DPS displays, heck we didn't even have the ASCENT TRAJ displays until GLS MPS implementation.

And the Ku band DPY & ACT is part of the same procedure and switch throws currently (R13L, PL BAY MECH PWR (2) ON, KU ANTENNA DPY).
 
OK. Yes, we're missing a lot of the DPS displays, heck we didn't even have the ASCENT TRAJ displays until GLS MPS implementation.

Actually we had it already for years. It was just left broken after the last release.

Also, the main problem is see is, that the SimpleGPCSystem is too simplified and also often not even attempting to follow DPS conventions.

MM G101 LAUNCH TRAJ would be almost the same display as MM G102 ASCENT TRAJ. The only reason why we can't display it, is a minor oversimplification in the code there.

The problem is: We can't just push the players at the NASA documentation, if the NASA FDFs do not work at all for SSU.
 
The problem is: We can't just push the players at the NASA documentation, if the NASA FDFs do not work at all for SSU.
Exactly and I agree 100% here. After mentioning the Ku band procedures I went back to the Ku band system ops workbook and I noticed that the MIP angles are wrong. I'll fix this unless someone has any objections?
 
Exactly and I agree 100% here. After mentioning the Ku band procedures I went back to the Ku band system ops workbook and I noticed that the MIP angles are wrong. I'll fix this unless someone has any objections?

What are the MIP angles? Before I also look at the work book again. :lol:

I look at making the SimpleGPCSystem operate a bit more like the hardware Space Shuttle Ultra, but before I change a single line of code, I better make a good plan there.

Plan is to add all system software displays to it and also allow the operations in the POST INSERTION checklist.
 
What are the MIP angles? Before I also look at the work book again. :lol:
MIP angles are α +116.5° and β -23.25°. However, I'm not sure if those are Ku gimbal angles or Orbiter gimbal angles.

---------- Post added at 12:44 AM ---------- Previous post was at 12:30 AM ----------

Based on the schematics in Ku band system ops workbook, specifically the one on page 4-3, I have calculated that the MIP position in terms of deltas from the stow positions are 7.8° in α and 4.25° in β. Previously I had assumed that the MIP position was the one shown in all the photos of the Ku band DA taken during the RPM.

This was clearly wrong based on the figure on page 4-3.
 
What are the MIP angles? Before I also look at the work book again. :lol:

I look at making the SimpleGPCSystem operate a bit more like the hardware Space Shuttle Ultra, but before I change a single line of code, I better make a good plan there.

Plan is to add all system software displays to it and also allow the operations in the POST INSERTION checklist.
How close are we to a release? I had the impression we wanted to create a new release soon, without adding new features. In that case, I'm not sure this is the best time to be rewriting the SimpleGPCSystem.
 
I took a look at the new positions to see panels L4/R4, and although it works, couldn't that be done with new AltGr+Arrow positions (in addition to the existing ones) instead of Ctrl+Arrow positions?
 
I took a look at the new positions to see panels L4/R4, and although it works, couldn't that be done with new AltGr+Arrow positions (in addition to the existing ones) instead of Ctrl+Arrow positions?

AltGr + Arrow key are intercepted by Windows 7 or newer. You rotate the display that way, which is a very easy way to crash Orbiter.
 
AltGr + Arrow key are intercepted by Windows 7 or newer. You rotate the display that way, which is a very easy way to crash Orbiter.


Alternate way is Ctrl+Alt+arrow.
 
Yes. Also rotates the display here, so no key binding that we can use.


Now that's weird. I'm using Windows 7 and it doesn't rotate the display unless you mean in Orbiter?
 
Now that's weird. I'm using Windows 7 and it doesn't rotate the display unless you mean in Orbiter?

No, Windows 7. Both key combinations work here.
 
Status
Not open for further replies.
Back
Top