This is a quick one, but one you’ll want to read if you find yourself diagnosing errors on vehicles built in the last two years. Gery from Florida ran across an issue (after several diagnostic steps) that appears to be a function of the unique
Many of our previous posts, whether in this category or in our feature article category, have noted the importance of having a diagnostic strategy. Often, this involves something along the lines of “Order of Operations” that we all learned in grade school math: if you
This month, we turn to Jeffrey in Illinois, who warns us to, “Don’t Be Like Me.” We love a good self-deprecating how-to piece where the author shows how they made a mistake and then teaches others to avoid said mistake. That’s reality and we’ve all
This month’s resource piece provides some excellent information when you’re faced with a difficult vehicle that requires a key relearn but communications or other errors are preventing you from programming new keys. In the quick but informative case study on Diagnostic Network, Kevin from Manitoba
This month’s resource piece is a little different, in the sense that, although it does provide a good case study on a tricky diagnostic issue, it also raises the question of proper compensation for diagnostic work. In it, our old friend Michael from Utah recounts
This month’s resource piece is a quick, but very useful, one. In it, Diagnostic Network founder Scott Brown provides tips on how to search the waveform library on Diag.net. He provides three different search strategies to make it as easy as possible to see if
This month, we return to Michael from Utah. Here, he provides a case study on a 2014 Beetle that exhibits a number of electrical issues.
We return once more to Bob from Massachusetts (he’s on a serious roll with great case studies!), who shared a tricky diagnosis on a “no communication” 2016 F-350 Super Duty. The funny thing is, the vehicle operated fine (apparently), but when taken to an inspection
We return again to Bob from Massachusetts, who shared a new case study regarding a 2008 Nissan Altima that was showing a trouble code for high idle. This is a very detailed diagnostic story that, as they often do, leads down some blind alleys and
This month, the focus is on a post from Bob from Massachusetts about an intermittent fault on a 1998 Ford Explorer that resulted in rough operation and a check engine light. The direct cause of the fault was quickly tracked down to a blown fuse
