Here is the full running list:
The top ten recommended rules of troubleshooting:
1. Before troubleshooting, survey the entire system and check if there are any other issues. "That was working before you got here, you must have done something".
2. If it doesn't work, then everyone is guilty until proven innocent.
3. Don't tell us what was specified, or show us what was ordered or even shipped, show us what is installed.
4. If it ain't broke, then don't fix it. However, if it's going to break, then it is best if it happens while we are here on site.
5. Don't solve a problem we don't have yet, no leaping to conclusions.
6. Sometimes you just have to unplug it and then plug it back in again to make it work.
7. Sometimes you just have to factory default the device, power cycle the processor, and reload the database to make it work.
8. If it doesn't work then check your wiring, if it still doesn't work, then check your wiring again, if it still doesn't work, then have someone else check your wiring.
9. If it doesn't work then check your programming, if it still doesn't work, then check your programming again, if it still doesn't work then have someone else check your programming.
10. Always get a second opinion either from a fellow technician or the factory hotline.
11. If you identify something which is not labeled, then label it
12. Photo or video record anything which "no one will believe is happening", or any unexplained anomalies.
13. An adaptive power module or a minimum load capacitor can solve a lot of problems.
14. Once you solve the problem, be sure to identify and confirm what made it fail in the first place.
15. Document everything. the system OOO, any observations, take equipment photos.
16. Never comment on system design. Ever.
