Engineer1
Member
Hi All,
I am putting together a "fault finding guide" for some remote sites that i support.
Effectively i have stated that there are four aspects to fault finding...
1. What is the fault?
2. What does that fault mean?
3. What causes the fault?
4. How do you solve the fault?
and i have listed resolutions to those as...
1. Note any fault codes, flashing lights, etc.
2. access the device manual for fault descriptions
3. investigate from the manual what causes the fault, or contact supplier
4. investigate from manual for solving or contact supplier.
i have found that there is a tendency for guys to just recycle power on faults, and continue until the fault re-occurs, cycle power again.
any additions to my list?
I am putting together a "fault finding guide" for some remote sites that i support.
Effectively i have stated that there are four aspects to fault finding...
1. What is the fault?
2. What does that fault mean?
3. What causes the fault?
4. How do you solve the fault?
and i have listed resolutions to those as...
1. Note any fault codes, flashing lights, etc.
2. access the device manual for fault descriptions
3. investigate from the manual what causes the fault, or contact supplier
4. investigate from manual for solving or contact supplier.
i have found that there is a tendency for guys to just recycle power on faults, and continue until the fault re-occurs, cycle power again.
any additions to my list?