This is amazing. You pretending to teach me how these systems work by showing me marketing versions of tech sheets and tutorials for systems I used to spec out, buy, build, and test. I've never met a truther so completely ignorant and so completely arrogant in my life.
That being said...
LMAO! Are YOU telling me that the PDF links that I posted do NOT explain the data transfer rates that you had no clue about as per your questions?!
First, let's be clear. I know exactly how it works and that's why I wrote this post and spent so much time proving all your ignorant fools wrong. I am using my questions as a rhetorical technique to expose how utterly ignorant you are.
To answer your question: Not even close.
No, not even close. Page 13, in particular, is describing data transfer between two components. Not through the entire system. Look...
ARINC 429 is the most commonly used data bus for commercial and transport aircraft.
All you are doing is showing me the time requirements of the interconnect between the sensor and the DFDAU and pretending it applies it to T1 through T5. Let's look at T1 through T5, shall we?
T0: The time at which an event actually occurs (plane is X feet above ground)
T1: The time it takes from T0 for an instrument to generate a measurement
T1.5: The time it takes for that measurement to be digitally buffered at the recorder (this is effectively 0, so it can be ignored)
T2: The time it takes from T1 for the measurement to be included in the bit-stream. This is the time that the measurement remains in the buffer waiting for his turn to enter the bitstream.
T3: The time it takes from T2 for the measurement to be written to the media. This is the time it takes to encode the bitstream, compress it, and store it
T4: The time from T3 for when that sub-frame is "completed" on the media, ie, you have a "complete" sub-frame
T5: The time from T4 when data was lost for whatever reason (any and all missing sub-frames, including the impact one)
The only time interval on this list that ARINC429 applies to is T1.5 The one I told you can be effectively ignored.
I'll await your YES, or NO response so I can quote it, and highlight it.
No, not even close. The tutorial you have shown me only represents a TINY FRACTION of the system.
Here's a picture:
Can you find ARINC 429 on this image? Are YOU going to sit there and tell ME that ARINC 429 governs the entire time requirements of a full FDR system? I'll await your YES, or NO response so I can quote it, and highlight it.
11. Recording shall commence in the crash protected memory within 250 milliseconds for audio and 500 milliseconds for flight data after power is applied and the start criteria are satisfied. After power interruptions greater than 5 minutes, up to 10 seconds are allowed for flight data sensor initialization and calibration.
Nowhere have I denied it. That statement is absolutely true. You just have absolutely no idea what it means. The bitstream resumes recording within some time frame after powerloss. That has absolutely nothing to do with the latency of the elements inside the bistream, nor any of the other numerous factors in T1-T5.
The flight data received from the ARINC 717 input source is recorded into crash survivable memory no
less frequently than once every 125 milliseconds
Again, you have ABSOLUTELY no idea what this means. ARINC 717 data has already undergone digital buffering and time multiplexing. You think this means FROM THE SENSORS and you are wrong. Not to mention this is a tech sheet for some other system -- not the one installed on AA77. You are wrong twice.
The delay in recording of flight data from the time of
SSDVDR input reception to the time of recording in the crash survivable memory does not exceed five
hundred (500) milliseconds.
Tech information on systems not installed on AA77 aren't relevant. Even still, see two above, as you still have no idea what this means.
Alright, so I've successfully demonstrated that ALL of your supposed proof is nothing but you FINDING numbers and pretending they apply to things that they don't.
I am STILL waiting for your FULL and logically consistent estimate of T1, T2, T3, T4, and T5.