*face-palm*. It isn't called time _division_ multiplexing anywhere outside of a communications class and/or wikipedia. I have a hunch which of the two you found that term at.
Is that right? You might want to check MIL-STD-1553, or avionics product
documentation. But you know what, it's cool. Now we're on the same page.
I can find several other current and past examples using time_division as a
reference. The term is not as displaced as you think...
As I've stated many times, I don't care about your background. Your ignorance, however, is much more troubling.
The feeling is mutual. I'll give you a pat on the back for catching me
on LRU, however that's the least of your worries. LRU/Instrumentation
semantics.
The fact that the DAU receives the same sensor data is what is most
important in this discussion. Sorry, but as you're surely aware it's tough
to get wiring diagrams for Boeing aircraft. You're asking about minor
details which in the big picture do not matter.
The fact that the FDAU is a dedicated RX makes your story even more of a
problem. Devices such as the LRA-900 (RAD altimeter) interface directly
to ARINC 429.
So, now we're left with the task of finding the latency from sensor, through
device processor to FDAU to FDR memory. I'll see what I can find through
the manufacturers just to please you.
I like the way you've just subtly contradicted yourself by pretending this was your opinion all along. Ok, that's one way to admit defeat. I'm glad to see you've changed your mind and agreed with me. Remember when you
tried to tell me that the instrumentation was "post" DAU? Yea. That was funny.
That was funny, but even funnier is ... it doesn't matter. The only error
I made was thinking the DAU processed the data from the sensors and
supplied it to the LRU.
This all is neverminding the fact that 500ms from the sensor is PHYSICALLY IMPOSSIBLE. If you sample something at once per second (as many parameters are sampled), you cannot have 500ms maximum delays. That fact that your own little theory of how this all works is internally inconsistent doesn't seem to bother you at all.
There is nothing inconsistent with my logic. You are claiming the sensor
data can't make it safely to CPM under 500 milliseconds. I'm saying all this
time, that it's a maximum of 500 milliseonds.
No, it doesn't. Nowhere have you ever demonstrated that 500ms applies to T1, T2, T3, T4, and T5. At best the specs you have shown us demonstrates T3, alone, is 500ms. Even more hilariously, you aren't even claiming T1-T5, you are only claiming T2+T3 < 500ms. You are wrong twice. You've -completely- ignored T1, T4, and T5 for the entire duration of this conversation.
Wrong again. 500 ms is an absoluate maximum. The actual transmission time
is less!
Instead of questioning the data, you pick on the most rediculous points and
try to find excuses that the FDR was at fault. You're asking questions that
you don't have answers to, and don't have resources to find the answers.
Now you're expecting the world to solve your t1-t5 equation instead of
contacting the NTSB for clarification and explanation on the data they released!
Awesome dude.
I'll do my best to find those answers for you.