How to ask for debugging help

earthtonesaudio · Post by **earthtonesaudio** » 22 Jun 2013, 23:54

If you have a debugging question for the forum, there are some things you can do to get the best, most timely advice possible. Some suggestions:

1. Describe the problem *as observed* (just the facts)
2. Include a complete (as-built) schematic and layout of the circuit
3. Include relevant measurements, such as voltages at IC and transistor pins, power supply voltage(s)
4. Include clear pictures

What is relevant to include in #3 depends greatly on your particular circuit. For example, if your circuit has a low frequency oscillator (LFO) you could say something like "pin 3 oscillates between 3.5 and 4.6 volts".

Please chime in if I forgot something. Maybe if we get a good list going one of the moderators could make a sticky for this section.
Cheers!

Dirk_Hendrik · Post by **Dirk_Hendrik** » 24 Jun 2013, 08:23

Good initiative!
I'd like to stress on number 2, the schematic.

Do not assume that, because you, the one with the non functioning circuit, built from a verolayout, kit or whatever and just used the building instructions, the schematic is not required for debugging. Possible errors in the circuit come forward in the schematic almost immediately while they stay very hidden in a drawing of the build.

Also,
If you need help, that's fine and please do ask. We all were in the dire straits you are in once and most likely far more than once. But! when you ask, be prepared and willing to learn as well.

DrNomis · Post by **DrNomis** » 27 Jun 2013, 18:33

Also, when faultfinding your build, try to be methodical and above all try not to get discouraged, and,or, lose your cool, otherwise you won't be able to use your most powerful troubleshooting tool, deductive reasoning, at it's maximum effectiveness.....

deltafred · Post by **deltafred** » 27 Jun 2013, 18:40

DrNomis wrote:Also, when faultfinding your build, try to be methodical and above all try not to get discouraged, and,or, lose your cool, otherwise you won't be able to use your most powerful troubleshooting tool, deductive reasoning, at it's maximum effectiveness.....

+1

If you are stumped then leave it for a while so you come back to it fresh and have had time for your brain to make sense of the information and you have had time to settle down if you were getting in a bit of a raz with it.

Post by **modman** » 14 Jul 2015, 21:23

http://www.geofex.com/fxdebug/newfx.htm