Appication notes

They were testing you to see if you were paying a attention!

Sometimes that works to let them know how interested their users/readers really are about what they are looking at.

Well, that's my story and I am sticking to it. :)

Jamie

How do you expect application "engineers" to get their jollies ?:-) ...Jim Thompson

-- | James E.Thompson, CTO | mens | | Analog Innovations, Inc. | et | | Analog/Mixed-Signal ASIC's and Discrete Systems | manus | | Phoenix, Arizona 85048 Skype: Contacts Only | | | Voice:(480)460-2350 Fax: Available upon request | Brass Rat | | E-mail Icon at

I wonder how many (how many hundred?) other engineers made the same discovery. I've seen decade-old data sheets that are still wrong, years after apps engineers have helped me find a bug.

They do that just to help the young. Anyone who wants to learn electronics can get a stack of app notes, determine in advance that every one of them has something serious wrong with it, and learn a lot finding them.

(My early adolescence in a nutshell. Then I discovered girls.) ;)

Cheers

Phil Hobbs

found out the same about girls? :p

-Lasse

Some of them are a little buggy too.

Hallo and good morning. Guinea pig is not pig. Application engineer is not engineer.

Sometimes I have to look into the reference C code; but I never use it as copy-paste.

Vladimir Vassilevsky DSP and Mixed Signal Consultant

"Raveninghorde"

Typos just like YOUR one in the heading here ...

... Phil

Let me explain how documents get created. People who know what they are doing create circuits, programs, etc. that work. [Hey, excluding dry labbers.] Marketing doesn't like how your schematic looks, blah blah blah. They pretty things up and introduce errors. Many schematics in datasheets do not like like they came from schematic capture because....well... they didn't come from schematic capture. Some marketing type took a good schematic captured circuit and then drew it in Visio or whatever.

Here is a clue on how to sort fact from fiction in datasheets. Scope photo: fact. Spreadsheet data: often fiction or at least prone to error because some marketing type screwed with it. LTC as an example has many scope photos or at least documents that look like they came right off an instrument (spectrum analyser, DSA, AP, etc.). I suspect design engineering at LTC has a bit more control over the marketing types.

Without even seeing your code error, I have this nagging suspicion is some marketing type didn't like the font in the code they were given and re-typed it, leaving out a line or adding a bug. In C, a + and ++ are very different!

I don't know if they still do so but UK Ordnance Survey maps used to have one deliberate (minor) error per map for copyright reasons. Only one person with access to the safe containing the nature of each error

Yes. Pineapple cake, upside down.

What make you think 'application notes' are authored by 'application engineers'?

And you know all about engineers and their capacities from where, asshole?

And you are the abvmaster... err appmaster, right?

He posts here from time to time, and he's pretty good; much better than Raveninghorde. I don't recall having seen your nym at all - maybe you should have lurked for a bit longer before you decided who you should call an asshole.

-- Bill Sloman, Nijmegen

It's AlwaysWrong.

I'd rather he just lurk forever.

Now, them's fighting words! As an application engineer for ten years, I can tell you that we WERE engineers, in every aspect!

Charlie

Analog Devices AD9850. The data sheet shows one schematic for the test circuit, and the test software shows another. The first won't load some of the data to the chip, the second does. I had a series of emails about that part, and the guy asking questions doesn't believe that the DS schematic is wrong.