You could present interesting soldering tips to your colleagues so they could learn more about soldering techniques and not make the same mistake again. A lot of people use Huntron Tracker test equipment to determine the cause for the failures in boards, it`s good that you told them about it and saved them a lot of time.
This story is a great example of the benefit of having a team with diverse backgrounds and experiences.
The DMM vs. Huntron comment is a reminder that you shouldn't get stuck relying on one piece of test gear, but should understand what each tester tells you.
I had a similar example from working at a contract manufacturer a few years ago. One of our customers couldn't get his techs to understand that even though their frequency counter says the oscillator is ok, a distorted waveform will kill their circuit. On the other hand, we couldn't get our techs to understand that even if an o-scope shows a pretty waveform, a counter would do a better job of telling you if you met the frequency tolerance and stability criteria.
Huntron Trackers can be useful. They can also be misleading.
A few years ago a tech came to me for some help. The output voltage of a DC to DC converter was low, he had replaced the converter to no avail, and was stumped. His Huntron Tracker showed the same curve at the converter output for both the failed UUT and a good unit.
I used a DMM to quickly determine that the converter load on the bad unit was 40 ohms compared to a few Kilohms on the good unit. A load electrolytic capacitor had gone leaky and was pulling down the voltage. The Huntron could not see any difference between the good and bad capacitors. The bad one was not open and still had it's capacitance, and was not shorted either.
After that the tech believed my mantra "Never trust a Huntron". He learned how to dig deeper when the Huntron could not indicate a fault.
What are the engineering and design challenges in creating successful IoT devices? These devices are usually small, resource-constrained electronics designed to sense, collect, send, and/or interpret data. Some of the devices need to be smart enough to act upon data in real time, 24/7. Are the design challenges the same as with embedded systems, but with a little developer- and IT-skills added in? What do engineers need to know? Rick Merritt talks with two experts about the tools and best options for designing IoT devices in 2016. Specifically the guests will discuss sensors, security, and lessons from IoT deployments.