When to Stop Troubleshooting

Abstract

Kirk and Fred discussing the challenge of when to end efforts in troubleshooting a failure.

Key Points

Join Kirk and Fred as they discuss issues surrounding the efforts made to understand the root cause of a failure when they have had trouble recording this podcast.
Topics include:

• In some cases the troubleshooting efforts removes or corrects the underlying cause, such a disconnecting a cable and then plugging it back in may clean off the contacts making an open connect closed again.
• Troubleshooting may require extensive monitoring and instruments, which may not be easily available, and access to other elements of a connected network or system that are not available such as the routers and servers in our podcast recording network.
• Both Fred and Kirk discuss both having a crystal manufacturing latent defect, which they had to determine whether it was a design or manufacturing issue.
• Low cost devices may never be sent back to the manufacturer and that makes development testing and in-house testing much more necessary.
• Every component manufacturer is trying to reduce their costs of manufacturing and sometimes the resulting changes may cause failures in your application among the many users of that device.

Enjoy an episode of Speaking of Reliability. Where you can join friends as they discuss reliability topics. Join us as we discuss topics ranging from design for reliability techniques to field data analysis approaches.

---

---

Show Notes

Please click on this link to access a relatively new analysis of traditional reliability prediction methods article from the US ARMY and CALCE titled  “Reliability Prediction – Continued Reliance on a Misleading Approach”

For more information on the newest discovery testing methodology here is a link to the book “Next Generation HALT and HASS: Robust design of Electronics and Systems” written by Kirk Gray and John Paschkewitz.

The post SOR 727 When to Stop Troubleshooting appeared first on Accendo Reliability.