Space Shuttle Ultra 1.25 Revision B development

[DaveS]

After quite some problems getting the side panel console correct, I think that we have finally overcome the the only major roadblock! I have attached a screenshot of the current state of the panels. Nothing too fancy right now, just the center and right-hand consoles.

On top the right-hand console is the Laser Docking System(not yet added).

 

[DaveS]

Here's the latest CT cab work. That's an actual photo of the CT cab I used for reference in GMAX. Photo credit goes to Interspacenews.com. It's one of few that they took during the media tour in 2006 when CT-1 celebrated its 40th anniversary(first used in 1966).

 

[DaveS]

One note on the speed control of the CT:

It's should take more time to go from 0 MPH to full 2 MPH unloaded speed. Also, the CT reacts very badly to going from completely stationary to 1 MPH in a very short time(a few seconds). You have to ease the speed up gently.

Also, based a various vibration testings done during 2003(MLP with two SRBs braced with an ET Intertank thrust beam) and 2006(MLP with complete stack, rollout of STS-115), they found that the optimal speed based on vibrations induced by the CT is 0.8 MPH and exceeding 0.8 MPH requires permission from the NTD.

 

[Urwumpe]

Small update from my side:

While still unable to code properly here, because I have to use a bad replacement keyboard (with jamming space bar, you see it by my post count), I took some hours to work on the UML modelling of SSU, especially about finding a working solution for the Shuttle Bus problem, which I still didn't have...

Now I have gotten ahead by starting from a more formal point, by modeling the use cases of the shuttle bus, I think I am on the right track now.

 

[Urwumpe]

Small update on the architectural work: Here is a UML sequence diagram about how the classes of the shuttle bus system should interact. If you can see logical errors in the diagram, please point them out, I think it works like that.

You can have one commanding GPC and as many listening GPCs as you like (maximal 3 in reality), also you can have as many bus terminals on the bus as you like (though it would be limited to 31 in reality)

Small legend:

"BusTerminal::flush()" removes all previous data from the bus terminal FIFO.
"BusTerminal::writeData()" puts new data into the bus terminal FIFO

The phases "Pre-Phase", "Command Phase" and "Read Phase" are to make sure all Bus Terminals and GPCs get the same data during the same time step.

The GPC software would not access the data instantly, instead, it would delegate this task to the IOP and let it do the data exchange with memory. You would just check if the data got exchanged properly during the time step. There is no limit for the data requested during the command phase for each GPC, except memory in the computer running Orbiter.

 

[DaveS]

Tested the latest Crawler code check-in(rev 726) and only get consistent CTDs. Used scenario is STS-114 April 6 2005 rollout to pad B.scn.

 

[SiameseCat]

Should be fixed now.

 

[DaveS]

Should be fixed now.

Yes, thanks! Attachment needs tweaks as before the CT raises its main-body before it can pick up the MLP. Once the MLP has been attached to the CT, the CT once again raises main-body with the attached MLP clear of the stands. Only then can the roll begin.

Here's a zipped version of a time-lapse video of the STS-118 rollout from VAB High Bay 1: http://rapidshare.com/files/278722864/CT_MLP_raise.rar.htm

 

[Donamy]

Would it be possible to have the ODS and airlock removable in the Scenario file. would be nice to be able to do other missions that didn't fly one, or one not in the same position.

 

[Donamy]

bump !!

 

[DaveS]

Once the CT is an a good state, I would like to see some attention being put on CRTMFD to make it a bit more useful. For example, the MEDS-specific screens like ADI, AVVI, AMI, HSI, APU/HYD, OMS/MPS and SPI could be implemented in their full graphical correct states.

 

[Urwumpe]

Once the CT is an a good state, I would like to see some attention being put on CRTMFD to make it a bit more useful. For example, the MEDS-specific screens like ADI, AVVI, AMI, HSI, APU/HYD, OMS/MPS and SPI could be implemented in their full graphical correct states.

The MDU specific information like the Commander/Pilot bar should also be added... maybe I can give it a start over the next four days, but I am currently really slowed down in coding by the substandard keyboard here. But things get better, I start to grow muscles on my thumb.

 

[Donamy]

The MDU specific information like the Commander/Pilot bar should also be added... maybe I can give it a start over the next four days, but I am currently really slowed down in coding by the substandard keyboard here. But things get better, I start to grow muscles on my thumb.

:rofl:

Seriously, can we get the Airlock removable in the bay, by way of the scenario ?

 

[Urwumpe]

:rofl:

Seriously, can we get the Airlock removable in the bay, by way of the scenario ?

We can, the question is just when.

 

[Donamy]

Soon would be nice !! Or whenever someone gets the chance, if they would, that would be cool.

 

[SiameseCat]

Yes, thanks! Attachment needs tweaks as before the CT raises its main-body before it can pick up the MLP. Once the MLP has been attached to the CT, the CT once again raises main-body with the attached MLP clear of the stands. Only then can the roll begin.

Here's a zipped version of a time-lapse video of the STS-118 rollout from VAB High Bay 1: http://rapidshare.com/files/278722864/CT_MLP_raise.rar.htm

Crawler platform can now be raised/lowered manually.
CTRL+J raises, CTRL+K lowers

 

[DaveS]

Nice job on the CT JEL! Could you make it so that the diagonal struts connecting the main body with the drive trucks not get disconnected when raising the main body?

 

[Donamy]

Another request, would be to have the ability to stow the SSME's after MECO. :flowers:

 

[Urwumpe]

Another request, would be to have the ability to stow the SSME's after MECO. :flowers:

yeah, that must be done, we also need this for reentry and after landing.

A 100% solution would be doing this after the Shuttle Bus code, the ATVC and the ATVC SOP (should be part of the GNC software in OPS 1, 3, 6 and 8).

Could maybe be done earlier with a temporary solution, but would then also require temporary controls, while the 100% solution could be controlled over DPS SPECs.

 

[SiameseCat]

Nice job on the CT JEL! Could you make it so that the diagonal struts connecting the main body with the drive trucks not get disconnected when raising the main body?

Probably, but it might be a bit tricky. Do you have any images showing how the struts look when the main body is raised?