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.
Festo's BionicKangaroo combines pneumatic and electrical drive technology, plus very precise controls and condition monitoring. Like a real kangaroo, the BionicKangaroo robot harvests the kinetic energy of each takeoff and immediately uses it to power the next jump.
Design News and Digi-Key presents: Creating & Testing Your First RTOS Application Using MQX, a crash course that will look at defining a project, selecting a target processor, blocking code, defining tasks, completing code, and debugging.
Focus on Fundamentals consists of 45-minute on-line classes that cover a host of technologies. You learn without leaving the comfort of your desk. All classes are taught by subject-matter experts and all are archived. So if you can't attend live, attend at your convenience.