So I think I finally scratched an itch I had for some time: where are the MEDS ADCs getting their data from?
It looks like some (and this is only me adding 1 and 1 together, I haven't seen "hard data" on this) of the data displayed in the subsystem displays takes the scenic route to get there. Some data comes directly from the hardware (e.g. MPS He pressures), but for things like SSME PC or aerosurface positions that doesn't work. In the MCDS, that data was sent from the GPCs to MDMs that then generated analog signals that drove the mechanical displays. It seems that in MEDS the ADCs pick up those analog signals from the MDMs, convert them to digital and send it to the IDPs. So, some data goes from the GPCs, to MDMs, to ADCs, to IDPs, which are already connected to the GPCs via, not 1 but, 2 busses! :lol: Even the Galileo spacecraft had an easier path to Jupiter than this... :rofl:
But it makes sense as the MEDS was supposed to be transparent to the GPCs, and this way the display data being output by the GPCs is the same. :shrug:
BTW, the data for the PFDs was originally sent to the DDUs, and is now sent to the IDPs, so that has a more direct route.
---------- Post added at 12:23 PM ---------- Previous post was at 12:21 PM ----------
Why wouldn't my suggestion of using an O-F vBulletin project for the tickets work? Works nicely for OHM/O-F and Orbiter itself. The files are different though. Not sure about that one.
I wouldn't mind having the tickets here. Could they be "inside" our sub-forum?
Also, what about access: do only devs have write access as before, or should they be open to anyone?