AA77 FDR Data, Explained

[Anti-sophist]

Dodge. Dodge. Dodge.

Yes, I answer, than you answer. That's the deal. I'm trying to answer, and you won't let me. I'm sorry I can't just "answer" your question in a single post but every time I try to do that, you don't understand. I'd love to answer it in one simple post, but I need to go f'ing slllooowwwwww to make you understand anything. So please bare with me. I'm trying to answer..

I'd _love_ to answer all your subsequent questions but one at a time. This one. Once this one is settled, we can move on. I don't do subject changes, sorry.

Here's the question I'm currently trying to answer:

Can you please post YOUR OWN diagrams, links and references to the
T4-T5 timing that you "CLAIM" is part of the equation?
According to my sources and document, you made up all of that junk.

And we are SO close to finally having the answer here. So very close. But you keep dodging the questions I am asking to make sure you understand and are following along.

What are the data policies at the NTSB vis a vis data decoding and data validation of full frames and how many FULL frames might have been on the CPM but were still thrown out? Does your answer include how many FULL frames might be corrupted due to the on-board compression being interrupted by a crash?

Please keep in mind that PfT has assumed this number to be 0. I've never seen a shred of justification for this belief.

 

[lapman]

Anti, TF has yet to back his 500ms max time fallacy. Why would you think that he would answer any of your questions and acknowledge that he was wrong?

 

[Turbofan]

Anti, TF has yet to back his 500ms max time fallacy. Why would you think that he would answer any of your questions and acknowledge that he was wrong?

Hey Lapman, I've already provided an e-mail, a voice recording, a phone number
and a few links to support the 500 msec value.

Too bad for you and Anti, it has nothing to do with his made up theory.

THEN Anti, THEN! Then you will answer my question.

It's your turn. Don't worry, I'm keeping up just fine, I've already pointed out
a few mistakes on your diagram.

Now I'm making you look pretty bad because you can't produce the word
positions after 11 times of asking!

A deal is a deal. We will play your games after you answer my question.
It's only ONE question. It should be easy for someone who can start a
thread called, "AA77 Flight Data, Explained"

Explain the word positions please.

BTW, are you still sticking to your "max two seconds missing" claim?

 

[lapman]

Hey Lapman, I've already provided an e-mail, a voice recording, a phone number
and a few links to support the 500 msec value.

All of them point to the 500ms max between sensor transmissions. Nice try.

 

[Turbofan]

All of them point to the 500ms max between sensor transmissions. Nice try.

Bzzz! Wrong!

You see, if you had a clue you wouldn't say that. Some sensors are updated
8 times per second.

Stay out of discussions that are above you. This is how bad information
spreads.

 

[lapman]

Bzzz! Wrong!

You see, if you had a clue you wouldn't say that. Some sensors are updated
8 times per second.

Stay out of discussions that are above you. This is how bad information
spreads.

Wow, you are beyond clueless. Sensors are not updated. They only transmit. The ARINC document states both the min and max transmission times for the sensors with some of them having a max of 500ms. You are the one the keeps mistaking this as the time from sensor to CPM which is not covered anywhere. Once you understand your mistake, then you'll start to understand where you're wrong about everything else.

 

[Turbofan]

Wow, you are beyond clueless. Sensors are not updated. They only transmit. The ARINC document states both the min and max transmission times for the sensors with some of them having a max of 500ms. You are the one the keeps mistaking this as the time from sensor to CPM which is not covered anywhere. Once you understand your mistake, then you'll start to understand where you're wrong about everything else.

Oh god, it's the king of semantics! Some PARAMETERS are updated 8 times per second. Better?

So the 500 msec only applies to certain sensors? Some of the other ones
can transmit every 125 mseconds?

Are you for real?

Seriously, please stay out of this discussion. I bet even Anti is cringing at
your reply.

Let me know when anyone here can decode a raw file, or get a frame layout.

 

[lapman]

Oh god, it's the king of semantics! Some PARAMETERS are updated 8 times per second. Better?

So the 500 msec only applies to certain sensors? Some of the other ones
can transmit every 125 mseconds?

Are you for real?

Seriously, please stay out of this discussion. I bet even Anti is cringing at
your reply.

Let me know when anyone here can decode a raw file, or get a frame layout.

I highly doubt Anti is cringing.

When are you going to let us know when you understand what transmission times in the ARINC document really means.

 

[Turbofan]

Believe me, I know he's cringing. Well, maybe he's laughing at this point
since you were silly enough to reaffirm your ignorance with that last nonsense.

How can you apply 500 msec transmit time to all sensors, when some of
them transmit at 125 msec intervals?

You are just wasting my time.

Put down the ARINC document and try another hobby. Understanding
networks is not your forte.

 

[Jonnyclueless]

I think PFT has done a great job of opening the can of worms here. now hopefully with their presentation it can get the government (you know, the people behind the diabolical caper) to fund some money so that they can further investigate what specific kind of magic was involved in creating the crime scene. They did their job of "just asking questions dude", and now it's just a matter of finding a really good Wizard who can figure out the details of the magic involved.

Anyone know any expert Wizards or Magi?

 

[lapman]

Believe me, I know he's cringing. Well, maybe he's laughing at this point
since you were silly enough to reaffirm your ignorance with that last nonsense.

How can you apply 500 msec transmit time to all sensors, when some of
them transmit at 125 msec intervals?

You are just wasting my time.

Put down the ARINC document and try another hobby. Understanding
networks is not your forte.

I never said that 500ms is the max time for all sensors. Obviously, reading comprehension is not your forte since you have such a hard time comprehending what transmission interval means. Since I do understand what it means, I have infinitely more knowledge of the subject. So, go back to school and take a basic electronics class and maybe you'll start to understand what the t1-t4 times mean.

 

[Turbofan]

I never said that 500ms is the max time for all sensors. Obviously, reading comprehension is not your forte since you have such a hard time comprehending what transmission interval means. Since I do understand what it means, I have infinitely more knowledge of the subject. So, go back to school and take a basic electronics class and maybe you'll start to understand what the t1-t4 times mean.

Give it up. You tried to imply that Ed Santana's reply, and my links referred
to some sort of sensor transmit interval.

Busted.

Basic electronics huh? Let's talk. I happen to have a College education
in Electronics Engineering. 15 years in the field too! Uh oh, Lapman didn't
do his homework!

 

[lapman]

Give it up. You tried to imply that Ed Santana's reply, and my links referred
to some sort of sensor transmit interval.

Busted.

Basic electronics huh? Let's talk. I happen to have a College education
in Electronics Engineering. 15 years in the field too! Uh oh, Lapman didn't
do his homework!

It was shown that Ed did not confirm what you claim. As far as your supposed degree, i highly doubt it's real since you have zero idea what the Tx times mean in the ARINC tables. It even spells it out and you just handwave it away. You are completely ignoring the bottlenecks in the process.

 

[DavidJames]

I happen to have a College education
in Electronics Engineering. 15 years in the field too! Uh oh, Lapman didn't
do his homework!

hmmm

You're on line with an Auto Tech and getting schooled about FDR's...

 

[Jonnyclueless]

Is ITT tech really a college?

 

[lapman]

Ok, Mr Electrical Engineer with all the documentation, how many clock cycles does it take for the FDR to read the data from the input source, resolve the next memory address and store the data and check the CRC to verify that the data in memory was stored correctly?

 

[Turbofan]

hmmm

What's wrong? Can I not have more than one area of study?

Lapman, you are assuming quite a bit here. It's nice how you changed
the subject after I exposed you.

However, let's play more games while Anti continues to fury over his
'lost' word position notes.

Do you want to know the clock cycles needed to convert the data to
serial format, and then clocked into CPM, or post muxed?

What is this going to prove with respect to Anti's theory? You know
this is totally unrelated and off topic?

Are you just testing my background in electronics?

 

[lapman]

Lapman, you are assuming quite a bit here. It's nice how you changed the subject after I exposed you.

So, I guess that's a no.

Do you want to know the clock cycles needed to convert the data to
serial format, and then clocked into CPM, or post muxed?

The data is received in serial format by the FDR from the FDAU. It is then converted to the full word and stored. This takes time. So, once the word is received, how many clock cycles does it take?

What is this going to prove with respect to Anti's theory? You know
this is totally unrelated and off topic?

It has everything to do with Anti's theory. If the CRC check fails, T4 and T5 come into play.

Are you just testing my background in electronics?

Sort of, and so far you've failed.

 

[Turbofan]

Oh look at this, lapman replied and I didn't get a notice. Still no Anti?

He must have gone into hiding since he can't find his frame layout.

I'll be back with more soon. First of all, I need to work on Mackey and
his claim that FDR's shouldn't stop recording before impact...yet the
data stops 6 seconds before impact.

Gotta love when you catch someone in a contradiction.

 

[bje]

Gotta love when you catch someone in a contradiction.

Like when you claim AA77 flew over the Pentagon without a single eyewitness but can't explain why widely separated, independent eyewitnesses saw it hit the Pentagon.

Don't you ever tire of making your ridiculous claims, Turbofan?