Troubleshooting Analog Circuits (EDN Series for Design Engineers)

Based on the author’s popular series in EDN Magazine, the book contains a wealth of information on debugging and troubleshooting analog circuits. In this book, you’ll find advice on using simple equipment to troubleshoot (would you believe an ordinary AM radio?); step-by-step procedures for analog troubleshooting methods; and generous helpings of the author’s unique insights, humor, and philosophy on analog circuits.

  • Provides proven methods for troubleshooting analog circuits
  • Accompanying disk contains over 60 pre-built Electronics Workbench circuits

Users Comments:

  • This hard cover is far more durable as the soft cover is showing a lot of shelf wear. It doesn’t matter what it cost,, I bought it.
    This book is essentially a review of my last 75 years. (yep I started taking dead things apart to see what went wrong at age 5.
    Bob was the one “who you gonna call” person for tens of millions of people with common goals. His Pease Porridge column in ‘Electronics and other industrial magazines and of course my friend. I have known hundreds of engineers, even MIT graduates like bob but Bob actually knew “stuff.
    There are solutions in this book to the most sneaky problems that drive you nuts and the big thing is the how and the why stuff happens from the basic component point of view.
    Ironically his book “How to drive into accidents and how not to” did not cover what happens when your 1969 (sort of) VW hits a foreign object on a curvy road in the dusky evening. For more information simply BING
    ROBERT PEASE NATIONAL SEMICONDUCTOR. This is important,,, do it.
  • Bob Pease was always an unusual character at work. He will remain a notable part of our Analog Semiconductor History and that alone is a good reason for an engineer to keep this book in his personal library. The troubleshooting/debugging examples in this book are a bit dated (advanced technologies become obsolete in a relatively short amount of time), but Bob’s troubleshooting philosophy is still applicable. His tips aren’t just useful for Design Engineers. Semiconductor Test Engineers and Product Engineers can benefit from this book as well.
  • This is not the only book Bob Pease wrote. You really need to read all of them. Pease was a prolific author, and an excellent writer. Like some of his other books, this one is a compilation of many of the articles he’s written over the years, with some extra verbiage thrown in for good luck.
    Everything Pease has written has taught me something new, and this book is no exception. It may require rereading several times to get everything he threw in there.
    Bob Pease was killed in a one-car traffic accident on June 18, 2011, on his way home from a memorial service for Jim Williams, who, like Pease, was an analog circuit designer and author. No doubt Pease appreciated the irony. We’ll all miss him, and we’re all a little smarter for his having been here.
  • Ok, it’s clear Bob Pease is waaay good. And we’re fine with that. The book is VERY good, very clear in all the aspects, and in all I am very happy to have it. If you read this, you will find many other books use Bob’s advice and circuits. I am learning how to build tube amps, and this book almost only talks in terms of low voltage circuits, but still it’s incredibly useful.
    Highly recommended if you are to build reliable circuits.
  • A fun read, and an excellent reference filling the huge gap between datasheets and most texts. A must have for anyone who touches hardware. I can’t count the number of times I’ve gone to this book whenever I’m not quite using a device as intended, or I’ve got a sinking feeling I’m about to shoot myself in the foot with a design. I own *lots* of books and this book is packed with useful info that isn’t found in any of them and isn’t all that intuitive to start with.
  • Troubleshooting Analog Circuits takes a device-centric approach. About half of the chapters focus quite specifically on a type of device, and proceed to tell you a few common ways in which that type of device can fail. The other half of the chapters are quite random and don’t seem to fit together very well, although they also contain useful information.
    The primary theme in this book could be condensed quite simply: Don’t assume anything. A recurring theme in the book is “This type of component is usually pretty reliable, but might sometimes be out of tolerance, so don’t assume it’s correct.” Pease reiterates this same theme for resistors, capacitors, test equipment, circuit configurations, and so on. Virtually everything boils down to “x might not work, so if the system it’s in doesn’t work, x could be the problem”.
    This, in turn, means the book boils down to little more than a collection of random observations which normally would remain unpublished in some engineer’s notebook, but are just valuable enough to make a published book in this case, because Pease has so many decades of experience that his experience is worth a bit more than the standard spurious observation. Even so, this book is in no way a comprehensive guide on how to troubleshoot anything. It really is a collection of thoughts and tips from Pease; it should be called “Bob Pease’s Book Of Tips And Tricks”.
    Pease is also singularly obsessed in his hatred of SPICE. While he’s correct that SPICE can’t be relied upon for perfectly accurate simulation of anything, it’s funny that he rejects its use so strongly in a book whose overwhelming theme is that *EVERYTHING* is unreliable. The accompanying photo of Pease throwing a computer off a roof is, like the rest of the book, amusing but hardly useful. In the end, this book contains a lot of information that *could* be useful, but don’t rely on it as any kind of resource on troubleshooting. It has little to do with troubleshooting at all; its main audience is seasoned engineers who can benefit from a fellow engineer’s experiences.

Be the first to comment on "Troubleshooting Analog Circuits (EDN Series for Design Engineers)"

Leave a comment

Your email address will not be published.


*