Ah! I see. looking at the website I see Fluke has reverted to feature-oriented application notes rather than task-oriented notes. That is one of the great communications battles I fought and thought I had won for good. This is the constant battle between sales and marketing communications.
You don't come at a problem wondering which feature will make sales happy; You come at a problem looking for a procedure that will lead to the solution. The notes I wrote were all task/procedure oriented i.e. "Here's a procedure you can use to find a cause, and here's what to do about it when you find it."
But with complex systems there is a limit to that approach and maybe Fluke has come up against that. These are the two factors that novices and many experienced techs fail to grasp: you're viewing the effect, now go find the cause. You may need a meter to view the effect in enough detail to lead you to the cause. With enough experience you can dispense with some of the cause/effect process and play the odds game but understand that's what you're doing -- playing the odds. Like knowing about Ford's pole shoe problem for example.
The odds game was more effective in the old days when there was a finite number of failure modes, as in cars before computer systems. But now there are potentially more failure modes than incidences of a particular failure, so the odds game doesn't work so well. And now, sometimes you run the scan tool and come up with several codes so the task becomes finding one or more causes that have the error codes in common. Here again you're playing the odds game but at least you have a fighting chance and can check some voltages that might not show up in the scan tool data stream. Experience matters.
