Space Shuttle Ultra 1.25 Revision B development

[DaveS]

What's needed for correct implementation of the payload latch system?

Would be nice to have it done.

 

[SiameseCat]

There isn't that much work required; all we need to do is animate the latch switches on Panel A6. I can work on this if you're interested.

 

[DaveS]

There isn't that much work required; all we need to do is animate the latch switches on Panel A6. I can work on this if you're interested.

Won't we need a way to control where the longerons are placed in the payload bay?

Edit:
Just to let you know that my computer has suffered a serious malfunction, so I don't know when I'll be able to rejoin the development again. All the SSU stuff are safe. It's just that Windows refuses to boot.

I'm posting this from my Wii console.

 

[Urwumpe]

What about the Ares I stuff, is that also safe?

 

[DaveS]

What about the Ares I stuff, is that also safe?

Yes. All the development stuff are on a separate partition of the HDD. It's just that the Windows partition is no-go for booting. And I can't find the Win7 disc I made when the RC1 was released.

 

[SiameseCat]

Won't we need a way to control where the longerons are placed in the payload bay?

Edit:
Just to let you know that my computer has suffered a serious malfunction, so I don't know when I'll be able to rejoin the development again. All the SSU stuff are safe. It's just that Windows refuses to boot.

I'm posting this from my Wii console.

I was thinking about controlling the actual attach points, not the visual implementation. I think the latch positioning is already defined in the mission file.

For the visuals, we don't display the latches at all yet. Once we can properly simulate the GPCs, we'll also need to add support for the PDRS displays.

 

[Donamy]

The visual longerons can be supplied for each flight with the payload, very easy to implement.

 

[SiameseCat]

A6 Rotary Switch

I was thinking about controlling the actual attach points, not the visual implementation. I think the latch positioning is already defined in the mission file.

For the visuals, we don't display the latches at all yet. Once we can properly simulate the GPCs, we'll also need to add support for the PDRS displays.

I've started working on the A6 latch switches, and I'm wondering how to handle the rotary switch which selects which group of latches is controlled. Normally, the rotary switch would either have a single output signal and multiple input signals, or multiple inputs and one output.

In this case, the switch needs to have multiple inputs and outputs. The different latch/release switches need to connect to the active latch group, and the talkbacks also need to be connected to the correct latch group. I'm thinking of having a single output DiscBundle associated with the rotary switch, and multiple input bundles. The rotary switch would then 'connect' the output bundle to the appropriate input bundle.

 

[Urwumpe]

Make multiple outputs and resolve the status by panel logic. In the real shuttle, the position of this switch should end as 16 bit word in telemetry.

 

[DaveS]

I regret to inform that due some carelessness on my part, all the SSU/Ares 1X dev stuff is gone. I did the error/mistake during a botched attempt on getting Ubuntu installed. It seems like my HDD is physically failing, at least that is what Ubuntu is telling me. One half of the HDD has bad sectors, the other half is A-OK.

So right now I'm on the Ubuntu LIveCD mode, which is working nicely but I'll have to replace the HDD and I'm not sure when I can do that.

 

[agentgonzo]

I feel your pain. I've lost code before due to wetware errors and it's a pain. Writing code a second time is just unfulfilling.

I do all my development under a version control system that uses an external server (either my own or sourceforge) and so acts as a backup in case of drunkenness at the root prompt.

 

[Urwumpe]

Argh. Do you need the Ares I-X files I have from you for a restart?

 

[DaveS]

I feel your pain. I've lost code before due to wetware errors and it's a pain. Writing code a second time is just unfulfilling.

I do all my development under a version control system that uses an external server (either my own or sourceforge) and so acts as a backup in case of drunkenness at the root prompt.

Well, the pain won't be in the remodelling everything(I'm actually looking forward to it!), it will getting all the research back! That was the result of basically going through every single section of the KSC Media Archive which I started doing 4 years ago!

 

[Donamy]

Hmmm ...where's my external HD ?

 

[DaveS]

Argh. Do you need the Ares I-X files I have from you for a restart?

Well, since my new SSU SRBs were to be based on the same meshes as the 1X FS meshes, I would have to say yes! They were made to support future stacking activities in the VAB.

But it will have to wait until my new HDD is up and running.

---------- Post added at 06:47 PM ---------- Previous post was at 06:36 PM ----------

Hmmm ...where's my external HD ?

Ever since I discovered the bad HDD section, I have been looking at some external HDDs So far I have found two that suits my needs. Both are USB connected(got plenty of free USB slots) and are in a good price range(85/175 US$).

They're on 500 GB/1 TB respectively and they're both made by SeaGate.

 

[GLS]

Heads-up to a bunch of new docs at http://www.nasa.gov/centers/johnson/news/flightdatafiles/index.html including a recent SCOM (IO-33) :thumbup:

 

[Urwumpe]

Heads-up to a bunch of new docs at http://www.nasa.gov/centers/johnson/news/flightdatafiles/index.html including a recent SCOM (IO-33) :thumbup:

Damn, are we outdated now. Is anybody willed to finance me three weeks of holidays for working on SSU and my family 3 weeks in Cancun for not disturbing me? :lol:

 

[DaveS]

Good stuff for whoever is working the MPS: http://forum.nasaspaceflight.com/index.php?topic=14350.0

Lots of nice technical talk about the ET!

 

[Urwumpe]

I just have seen that the PASS *** TRAJ displays changed a lot during the last software upgrades, shall I concentrate on the current ones or do I try keeping the historic display format as option?

---------- Post added at 02:41 PM ---------- Previous post was at 02:39 PM ----------

Good stuff for whoever is working the MPS: http://forum.nasaspaceflight.com/index.php?topic=14350.0

Lots of nice technical talk about the ET!

Shoved the files on my USB stick, will read them later.

 

[DaveS]

I've started working on the A6 latch switches, and I'm wondering how to handle the rotary switch which selects which group of latches is controlled. Normally, the rotary switch would either have a single output signal and multiple input signals, or multiple inputs and one output.

In this case, the switch needs to have multiple inputs and outputs. The different latch/release switches need to connect to the active latch group, and the talkbacks also need to be connected to the correct latch group. I'm thinking of having a single output DiscBundle associated with the rotary switch, and multiple input bundles. The rotary switch would then 'connect' the output bundle to the appropriate input bundle.

How's the latch work coming? Once this is done, would you be willing to implement the aerosurface/SSME TVC checks done during terminal countdown?