Just creating a corner for MPS related stuff...
Finally I've managed to complete a working version... it's far from perfect but it's a begining. Now I need someone to joint my code with the rest. Who want's the files?
Also, does anyone have any docs with the rules/valve position seq/whatever on ignition and shutdown??? (it's all open loop so there must be some rules) I have some charts with the position of the valves on ignition and shutdown, but for a shutdown during ignition I don't know what the vlvs do.
And about the MPS Power switches, do I call the panel to know what the switch is doing, or the switch calls me???
So, I get the PROPELLANT_HANDLE on the constructor...
The .pdf file, is it on the web? If not, I can get up to 10Mb by e-mail... I'll PM you the address...
I would suggest a USA employee since they're the ones who process the flight hardware at KSC. NASA only provides management and oversight.I have those... Thanks anyway!!! I also have one from Boeing, nice pics but not alot of info... and a bunch from ntrs...
I'm really starting to believe that we're going to have to kidnap a NASA employee to learn more about the shuttle....:titanic:
I would suggest a USA employee since they're the ones who process the flight hardware at KSC. NASA only provides management and oversight.
:feedback:
Currently, I'm *mentally designing* a valve class to have a more or less realistic valve operation. I'm thinking in having a basic class and them derive a bunch of vlv types. But I don't know how it's going to interface with the EPS or HYD, (or the piping, when I figure out how to make them, but that's a headache for another day!).:suicide:
I was wondering what you people think, because I want to make it so that it could also be used on OMS/RCS, etc...
I just found out I have a nice doc with redlines and stuff, but before I do the redlines I'd like to get the vlvs in a confortable position... (actually it has a lot about everything... I'll see if I can find it on the web)
:sos: Anyone has a list of the data in the VDT (Vehicle Data Table)??? I have around 20-25 (of 128 fields) taken from the docs posted above...
:sos:Also about the start enable/shutdown enable and start/shutdown cmds: my understanding is that they have to be sequential (ex. start enable, start). Any other cmd after the start enable will "reset" the enable... can anyone confirm this?
No, does not make sense to me... If I see the diagram correctly, multiple GPCs issue the commands to the EIUs. So, there can be 3 commands of start enable, and 3 start commands from 4 GPCs reaching the three independent channels of the engine controller. (2 directly, 1 over a FIFO transmitting the first command and deadfacing the second).
All three commands in a frame get voted by the DCU A (or DCU B, if active).
There are 50 frames per second.
class SubsystemDirector
{
public:
/**
* @param usMPSNo numerical ID of the SSME
* @param fThrust0 Vacuum thrust
* @param fISP0 Vacuum ISP
* @param fISP1 Sealevel ISP
* @return false for failure, true for success
*/
bool SetSSMEParams(unsigned short usMPSNo, double fThrust0, double fISP0, double fISP1);
/**
* @param usMPSNo numerical ID of the SSME
* @param dir direction vector of the SSME force vector
* @return false for failure, true for success
*/
bool SetSSMEDir(unsigned short usMPSNo, const VECTOR3& dir);
};