With App Notes, Trust But Verify

Reading time ( words)

For this month’s issue on app notes, I checked in with Clive “Max” Maxfield. The author of Bebop to the Boolean Boogie and countless technical articles and blog posts, he has been involved with all manner of app notes and datasheets during his long career. Max shares his thoughts on data. As he points out, “Remember that these documents are not written by an ‘infallible creator.’”

Andy Shaughnessy: Max, you’ve been involved with electronics design in a variety of different segments: ICs, PCBs, programmables, etc. Give us an overview of how you view the role of app notes vs. datasheets for a PCB designer or EE.

Clive “Max” Maxfield: First of all, you can have datasheets and app notes for all sorts of things, including subsystems, systems, products, machines, etc. From my perspective, I usually think of these in terms of electronic components—either discrete components like resistors, capacitors, diodes, transistors, or more complex components like integrated circuits, from op-amps all the way up to microcontrollers and the like. In this context of datasheets vs. app notes, they serve two different purposes. A datasheet summarizes the characteristics and performance of a component. By comparison, an app note briefly describes how a component is to be configured and used for a specific example application.

Shaughnessy: Have you ever written any datasheets or app notes?

Maxfield: I haven’t written any datasheets, but I have written a couple of application notes.

Shaughnessy: We’ve heard from some PCB designers and EEs who work for companies that demand that they follow app notes, but some well-known design instructors advise designers that IC makers’ app notes should be assumed wrong until proven right. What’s your take on this?

Maxfield: I think app notes can be really useful when you are first starting to work with a new component or with a known component in a new or “new to you” configuration or application. Having said this, I think everything you read, including datasheets and application notes, should be assumed to be lacking or misleading or indeed incorrect/wrong just in case.

Shaughnessy: It looks to me as if IC manufacturers’ datasheets are more grounded in facts, while app notes are sometimes overly optimistic. Some designers say app notes are used more like marketing materials. Is that a fairly accurate description?

To read this entire interview, which appears in the June 2020 issue of Design007 Magazine, click here.



Suggested Items

Footprints: A Distributor’s Perspective

02/19/2021 | Andy Shaughnessy, Design007 Magazine
No issue on footprints and library management would be complete without input from a component distributor. I recently interviewed Geof Lipman of Octopart; as director of operations for part data, he’s one of the brains behind the entire site. Geof explains how Octopart functions and manages millions of component data points, and he also discusses the current landscape of electronic components.

Best Practices: Footprint Design and CAD Library Management

02/09/2021 | I-Connect007 Editorial Team
The I-Connect team spoke with Altium’s John Watson about the hurdles surrounding footprints and footprint design. John talks about how being proactive and improving the CAD library can better QC processes and help protect against footprint difficulties.

Chapter 1 Excerpt from the Book ‘Thermal Management: A Fabricator's Perspective’

12/08/2020 | Anaya Vardya, American Standard Circuits
Heat cannot be efficiently exchanged with stagnant air surrounding a hot device; however, it can be transferred away from the electronic component to the PCB using thermal vias. A thermal via is a good conductor of heat that runs between the top layer and bottom layer of the PCB, dissipating heat through simple conduction. In simple terms, thermal vias are plated holes located under, or electrically connected to, a surface-mounted heat source on a PCB that allows heat transfer through the hole.

Copyright © 2021 I-Connect007. All rights reserved.