Centaur G/G Prime High Energy Upper Stage

[GLS]

I see the problem now, I was adding the adapter offset to both the payload and the adapter mesh. :facepalm:
Try it now, it should all work as advertised.

---------- Post added 03-05-15 at 02:51 AM ---------- Previous post was 03-04-15 at 10:36 PM ----------

53.8%
That's +/- the value that will give a 50% OMS load (the extra 3.8% is ARCS prop, as it currently shares the same "tank").
So, armed with the new shuttle performance I did a series of launches for the 61F and 61G missions, using the actual masses of the respective probes, and it works....... barely!!! Which is probably correct as these were the most performance critical missions (we'll talk about the VAFB missions at another time ). And I also fooled around in orbit, did some OMS burns, and still had plenty OMS prop left after the deorbit burn, so 50% OMS prop seems to be enough. Somebody else needs to run these missions, just to make sure they work.

 

[DaveS]

Where do we stand on getting the CISS animations up and running? That's the only thing that's left on the pre-release list to add.

 

[Urwumpe]

Where do we stand on getting the CISS animations up and running? That's the only thing that's left on the pre-release list to add.

Did not yet get to it yet. h:

 

[DaveS]

Did not yet get to it yet. h:

Just a heads up that you can duplicate the animations for the G Prime CISS as it will share the same data with the G CISS.

 

[Urwumpe]

Just a heads up that you can duplicate the animations for the G Prime CISS as it will share the same data with the G CISS.

Are there really any differences except a few more helium bottles?

 

[DaveS]

Are there really any differences except a few more helium bottles?

Not that I can find out. The aft section is exactly the same on both versions and located at the same orbiter relative position.

 

[Urwumpe]

Not that I can find out. The aft section is exactly the same on both versions and located at the same orbiter relative position.

I wonder: Could we use the same DLL for both then and just use a different configuration file or scenario file setting for just adding the differences between the two to a base CISS.

 

[DaveS]

I wonder: Could we use the same DLL for both then and just use a different configuration file or scenario file setting for just adding the differences between the two to a base CISS.

That's how things are set-up currently with both the CISS and the Centaurs, one common module with different cfg files that specifies the type.

 

[Urwumpe]

That's how things are set-up currently with both the CISS and the Centaurs, one common module with different cfg files that specifies the type.

So, it is likely one development task anyway.

 

[DaveS]

So, it is likely one development task anyway.

This is how it is set up currently:

void SSU_CISS::DefineCentaurGPrimeAnimations()
{
    anim_rotate = CreateAnimation(0.0);
    rotateAnimState.Set(AnimState::CLOSED, 0.0);

    static UINT DA_GRP[25] = {GRP_DEPLOYMENT_ADAPTER_GPRIME,
                              GRP_GOX_DUCT_BELLOW_1_GPRIME,
                              GRP_GOX_DUCT_BELLOW_2_GPRIME,
                              GRP_GOX_DUCT_BELLOW_3_GPRIME,
                              GRP_GOX_DUCT_SEGMENT_1_GPRIME,
                              GRP_GOX_DUCT_SEGMENT_2_GPRIME,
                              GRP_GOX_DUCT_SEGMENT_3_GPRIME,
                              GRP_LOX_DUCT_BELLOW_1_GPRIME,
                              GRP_LOX_DUCT_BELLOW_2_GPRIME,
                              GRP_LOX_DUCT_BELLOW_3_GPRIME,
                              GRP_LOX_DUCT_SEGMENT_1_GPRIME,
                              GRP_LOX_DUCT_SEGMENT_2_GPRIME,
                              GRP_LOX_DUCT_SEGMENT_3_GPRIME,
                              GRP_LH2_DUCT_BELLOW_1_GPRIME,
                              GRP_LH2_DUCT_BELLOW_2_GPRIME,
                              GRP_LH2_DUCT_BELLOW_3_GPRIME,
                              GRP_LH2_DUCT_SEGMENT_1_GPRIME,
                              GRP_LH2_DUCT_SEGMENT_2_GPRIME,
                              GRP_LH2_DUCT_SEGMENT_3_GPRIME,
                              GRP_GH2_DUCT_BELLOW_1_GPRIME,
                              GRP_GH2_DUCT_BELLOW_2_GPRIME,
                              GRP_GH2_DUCT_BELLOW_3_GPRIME,
                              GRP_GH2_DUCT_SEGMENT_1_GPRIME,
                              GRP_GH2_DUCT_SEGMENT_2_GPRIME,
                              GRP_GH2_DUCT_SEGMENT_3_GPRIME};
    static MGROUP_ROTATE DA (mesh_idx, DA_GRP, 25, _V(0,-0.04,-2.12), _V(-1,0,0), static_cast<float>(45.0*RAD));
    AddAnimationComponent(mesh_idx, 0, 1, &DA);

    /*static UINT GOX_VentLine_Seg1_Grp[6] = {GRP_GOX_DUCT_BELLOW_1_GPRIME,
                                            GRP_GOX_DUCT_BELLOW_2_GPRIME,
                                            GRP_GOX_DUCT_BELLOW_3_GPRIME,
                                            GRP_GOX_DUCT_SEGMENT_1_GPRIME,
                                            GRP_GOX_DUCT_SEGMENT_2_GPRIME,
                                            GRP_GOX_DUCT_SEGMENT_3_GPRIME};
    static MGROUP_ROTATE GOX_VentLine_Seg1 (mesh_idx, GOX_VentLine_Seg1_Grp, 6, _V(-1.77,-0.47,-2.12), _V(-1, 0, 0), static_cast<float>(45.0*RAD));
    AddAnimationComponent(mesh_idx, 0, 1, &GOX_VentLine_Seg1);

    static UINT LOX_VentLine_Seg1_Grp[6] = {GRP_LOX_DUCT_BELLOW_1_GPRIME,
                                            GRP_LOX_DUCT_BELLOW_2_GPRIME,
                                            GRP_LOX_DUCT_BELLOW_3_GPRIME,
                                            GRP_LOX_DUCT_SEGMENT_1_GPRIME,
                                            GRP_LOX_DUCT_SEGMENT_2_GPRIME,
                                            GRP_LOX_DUCT_SEGMENT_3_GPRIME};
    static MGROUP_ROTATE LOX_VentLine_Seg1 (mesh_idx, LOX_VentLine_Seg1_Grp, 6, _V(-1.58,-0.66,-2.17), _V(-1, 0, 0), static_cast<float>(45.0*RAD));
    AddAnimationComponent(mesh_idx, 0, 1, &LOX_VentLine_Seg1);

    static UINT GH2_VentLine_Seg1_Grp[6] = {GRP_GH2_DUCT_BELLOW_1_GPRIME,
                                            GRP_GH2_DUCT_BELLOW_2_GPRIME,
                                            GRP_GH2_DUCT_BELLOW_3_GPRIME,
                                            GRP_GH2_DUCT_SEGMENT_1_GPRIME,
                                            GRP_GH2_DUCT_SEGMENT_2_GPRIME,
                                            GRP_GH2_DUCT_SEGMENT_3_GPRIME};
    static MGROUP_ROTATE GH2_VentLine_Seg1 (mesh_idx, GH2_VentLine_Seg1_Grp, 6, _V(1.77,-0.47,-2.12), _V(-1, 0, 0), static_cast<float>(45.0*RAD));
    AddAnimationComponent(mesh_idx, 0, 1, &GH2_VentLine_Seg1);

    static UINT LH2_VentLine_Seg1_Grp[6] = {GRP_LH2_DUCT_BELLOW_1_GPRIME,
                                            GRP_LH2_DUCT_BELLOW_2_GPRIME,
                                            GRP_LH2_DUCT_BELLOW_3_GPRIME,
                                            GRP_LH2_DUCT_SEGMENT_1_GPRIME,
                                            GRP_LH2_DUCT_SEGMENT_2_GPRIME,
                                            GRP_LH2_DUCT_SEGMENT_3_GPRIME};
    static MGROUP_ROTATE LH2_VentLine_Seg1 (mesh_idx, LH2_VentLine_Seg1_Grp, 6, _V(1.58,-0.66,-2.17), _V(-1, 0, 0), static_cast<float>(45.0*RAD));
    AddAnimationComponent(mesh_idx, 0, 1, &LH2_VentLine_Seg1);*/

    static MGROUP_ROTATE AttachmentTrack (LOCALVERTEXLIST, MAKEGROUPARRAY(centaurAttachment), 3, _V(0,-0.04,-2.12), _V(-1, 0, 0), static_cast<float>(45.0*RAD));
    AddAnimationComponent(mesh_idx, 0, 1, &AttachmentTrack);
}

void SSU_CISS::DefineCentaurGAnimations()
{
    anim_rotate = CreateAnimation(0.0);
    rotateAnimState.Set(AnimState::CLOSED, 0.0);
    // TODO: implement animation (once mesh has been created)
}

 

[DaveS]

Urwumpe: What is your interim plan re: CISS actions (rotation/deploy)? According to my information, I think it was in either tech description documents, that the CISS actions was controlled from a Standard Switch Panel (SSP, L12). Unfortunately I haven't managed find any good photos of an SSP, much less one configed for Centaur.

 

[Urwumpe]

Urwumpe: What is your interim plan re: CISS actions (rotation/deploy)? According to my information, I think it was in either tech description documents, that the CISS actions was controlled from a Standard Switch Panel (SSP, L12). Unfortunately I haven't managed find any good photos of an SSP, much less one configed for Centaur.

I have no good idea as well, I think I will use some obscure key press as stand-in until I have a better idea.

One option would be taking the IUS switch panel as reference and mod it into a faked CISS control panel - as long as we know it is wrong, I can live with it.

For the Galileo missions, we would also need a control panel for the RTG cooling if I guess correctly there - STS-34 had something like that.

Another option would be using a GO/NOGO keypress and finally start on implementing communication and AI crew members... since the CISS would have been controlled by a payload specialist, no big deal.

 

[DaveS]

I have no good idea as well, I think I will use some obscure key press as stand-in until I have a better idea.

One option would be taking the IUS switch panel as reference and mod it into a faked CISS control panel - as long as we know it is wrong, I can live with it.

For the Galileo missions, we would also need a control panel for the RTG cooling if I guess correctly there - STS-34 had something like that.

Another option would be using a GO/NOGO keypress and finally start on implementing communication and AI crew members... since the CISS would have been controlled by a payload specialist, no big deal.

I have managed to find this partial photo of a SSP that flew on STS-95 to control the HOST: http://www.edcheung.com/archive/hostssp2.jpg

And here's another, not sure of accurate it is, but seems to be from STS-49 for the Intelsat VI reboost equipment: http://www.beneaththewaves.net/Drives/Images/2010_Day_05-01C-SSM_Consoles-DSC_9479.JPG

---------- Post added at 08:47 PM ---------- Previous post was at 05:38 PM ----------

After a bit of work, this is what I have for the CISS configed SSP in terms of graphics:

 

[Urwumpe]

Can you duplicate the up/down switches and add some "mechanics power" and logic power switch to each? There is a primary and a backup deployment actuator

 

[DaveS]

Can you duplicate the up/down switches and add some "mechanics power" and logic power switch to each? There is a primary and a backup deployment actuator

No problem, there's plenty of switches.

 

[Urwumpe]

No problem, there's plenty of switches. Although I can't move the TBs, they're fixed.

Thats no deal, there should be plenty enough TBs for the system.

Not sure if the propellant dump switches are on that panel though. The propellant dump would have to be capable of being activated by the PASS GPCs in GNC configuration.

The OI data though is only accessible by SM.

 

[DaveS]

Second revision:

---------- Post added 04-11-15 at 02:35 PM ---------- Previous post was 04-10-15 at 10:06 PM ----------

And here's the actual panel for the VC:

---------- Post added at 02:48 PM ---------- Previous post was at 02:35 PM ----------

The panel has now been checked into the ShuttleCentaur branch for initial testing.

 

[DaveS]

Found this interesting little notation in an AIAA document on the safety challenges of the Shuttle/Centaur fluid interfaces. Seems like the plan was to replace some of the FRSI blankets on Challenger with the same type AFRSI blankets used on Discovery and Atlantis.

 

[DaveS]

Done some more work on the Centaur G Prime, changes which will be retro-fitted to the Centaur G. The following changes have been made:

• Equipment Module redone to the proper shape and size
• Added the Signal Conditioner and Forward Instrumentation Boxes
• Added the two deployable antennas on the EM
• Added the Staging Disconnects on the Aft Adapter
• Resized the insulation to tank dia+1.5"

 

[DaveS]

Urwumpe: How far along did you get with the Centaur/CISS SSP integration? I'm just wondering how far away a functional Centaur/CISS is. Mesh-wise, everything is done except for wiring on the Centaur Equipment Module and LOX tank barrel from the cableway box to the staging disconnects. The then the same goes for the CISS (wiring from the various avionics boxes on the Deployment Adapter leading to staging disconnects on the DA which in turn mate with the staging disconnects on the Centaur). Donamy, I believe you earlier expressed an interest in helping out with the wiring. Is this still the case?