Is it an industry requirement that application notes always contain an error?
I've just been using C code from a 1-wire application note and it didn't work. It took a couple of hours with the scope checking timings etc before I spotted a wrong hex address in the code.
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
formatting link
| 1962 | I love to cook with wine. Sometimes I even put it in the food.
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.
--
John Larkin Highland Technology, Inc
jlarkin at highlandtechnology dot com
http://www.highlandtechnology.com
Precision electronic instrumentation
Picosecond-resolution Digital Delay and Pulse generators
Custom laser drivers and controllers
Photonics and fiberoptic TTL data links
VME thermocouple, LVDT, synchro acquisition and simulation
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
--
Dr Philip C D Hobbs
Principal Consultant
ElectroOptical Innovations LLC
Optics, Electro-optics, Photonics, Analog Electronics
160 North State Road #203
Briarcliff Manor NY 10510
845-480-2058
hobbs at electrooptical dot net
http://electrooptical.net
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
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.
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.
ElectronDepot website is not affiliated with any of the manufacturers or service providers discussed here.
All logos and trade names are the property of their respective owners.