this I feel is a typical troubleshooting scenario. many a times lack of understanding of the topology of the circuit , component charactetistics may result in this. for example an opamp based schmitt trigger may appear like a non inverting amplifier ( first impression on circuit topology) and if one has to torubleshoot a problem , lack of understandign of the topolgy may create more errors than a possilble solution.
Rob, it may be more cynically stated that "the customer always lies." Or, at least, "the customer never tells the whole truth." Troubleshooting such problems almost always means you have to be a Missourian: "Show me" or it didn't really happen.
Here's another good example of why it's important to dig down to the real problem. What appears to be the problem at first may not actually be the problem. We're seeing this again and again in the Sherlock Ohms posts.
In an age of globalization and rapid changes through scientific progress, two of our societies' (and economies') main concerns are to satisfy the needs and wishes of the individual and to save precious resources. Cloud computing caters to both of these.
For industrial control applications, or even a simple assembly line, that machine can go almost 24/7 without a break. But what happens when the task is a little more complex? That’s where the “smart” machine would come in. The smart machine is one that has some simple (or complex in some cases) processing capability to be able to adapt to changing conditions. Such machines are suited for a host of applications, including automotive, aerospace, defense, medical, computers and electronics, telecommunications, consumer goods, and so on. This discussion will examine what’s possible with smart machines, and what tradeoffs need to be made to implement such a solution.