Andreas Thaler
Subscriber
If the mirror on an SLR stays up or the camera is not receiving any power at all, troubleshooting often begins more or less immediately.
A few thoughts about what the cause of the error might be, plus experience and intuition, a look at the web, a quick consultation of the available technical documentation and the diagnosis is made.
Risky dismantling, no direct success control possible
As is the case with photographic equipment, it is often necessary to dismantle it more or less deeply to get to the suspected location of the problem.
No viewfinder displays light up, the camera shows no signs of life. How can troubleshooting be carried out effectively?
This is always risky, as damage may occur or reassembly may no longer be possible.
Once you have arrived and repaired the suspected error, you often cannot check whether the repair was successful; this is only possible after (partial) assembly.
If you were right, the device will work again.
If not, hours of work may have been unsuccessful.
Is systematic troubleshooting therefore better?
Would it improve the chances if you systematically diagnose the error and invest more time in this?
To get answers to these questions I am currently reading
Darrel P. Kaiser: Basic Electrical Troubleshooting for Everyone
The author:
Among other things the book contains systematic questions on how to isolate errors and mistakes that can be made.
Your own approach to effective troubleshooting
Of course, this has to be broken down into the specific repair task and adapted to the specifics of photo equipment repair (see above). This is complemented by your own experiences and knowledge, which are then added in this way.
I'll try to use all of this to create a troubleshooting approach that I plan to use as a practical guideline.
More on that later.
How do you go about troubleshooting?
Do you have recipes for success?
A few thoughts about what the cause of the error might be, plus experience and intuition, a look at the web, a quick consultation of the available technical documentation and the diagnosis is made.
Risky dismantling, no direct success control possible
As is the case with photographic equipment, it is often necessary to dismantle it more or less deeply to get to the suspected location of the problem.
No viewfinder displays light up, the camera shows no signs of life. How can troubleshooting be carried out effectively?
This is always risky, as damage may occur or reassembly may no longer be possible.
Once you have arrived and repaired the suspected error, you often cannot check whether the repair was successful; this is only possible after (partial) assembly.
If you were right, the device will work again.
If not, hours of work may have been unsuccessful.
Is systematic troubleshooting therefore better?
Would it improve the chances if you systematically diagnose the error and invest more time in this?
To get answers to these questions I am currently reading
Darrel P. Kaiser: Basic Electrical Troubleshooting for Everyone
The author:
What does the title mean? It is the idea that we can approach any electrical or electronic (and mechanical) fault using a basic logical or probability-based investigation to observe and correctly identify the significant indicators that will eventually lead us to the failure or failures. This is no different from the Detective Books you read or TV Shows you watch where the hero used a logical approach (while all those around him just ran around willy nilly) to identify the clues and catch the bad guy. This book is a complete course in Troubleshooting. Along with the written theory explaining my troubleshooting methods, there are over 80 diagrams and drawings, and 50 comprehension questions (with the answers) that will help you monitor how much you understand.
Among other things the book contains systematic questions on how to isolate errors and mistakes that can be made.
Your own approach to effective troubleshooting
Of course, this has to be broken down into the specific repair task and adapted to the specifics of photo equipment repair (see above). This is complemented by your own experiences and knowledge, which are then added in this way.
I'll try to use all of this to create a troubleshooting approach that I plan to use as a practical guideline.
More on that later.
How do you go about troubleshooting?
Do you have recipes for success?
Last edited: