![]() | ||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||
|
Graphical Scan Tool DataPosted 4/12/1999By Jim Linder
Scan tool graphical data as recorded and viewed through a personal computer has been around for some time, but hasn't been very user friendly for the working technician. I have memories of finding an injector problem on a early injected GM S10 pickup that had eluded the oscilloscopes of the day many years ago using an OTC scan tool and a product called EZ-Event. Now, 15 years later, this approach to data retrieval is a must! Taking information from your scan tool and displaying it into an easy-to-understand live sensor graph will help to ensure that no intermittent sensor problems go unnoticed. Lab scopes are great, but lack some record ability when trying to look at many parameters at once. For many years we have used the scan tool to pull codes, check prom numbers and troubleshoot the vehicle. Many techs have been accused as being a "scanner tech" as they use this tool for everything they do. But do we use this tool to its full potential? More than likely, the answer is "no!" We must understand the basic tool before taking it to the next step, which is graphical display. Software and support interfaces enable the technician to detect the problem, view it much more closely and print out the detailed values of a problem sensor. These computer programs help eliminate the limitations of your scan tool. You may now store as much information as you need. This becomes very beneficial if you need to look at many specific sensors at one time. Once a spike is seen in one of the sensors, you may freeze the graph and expand the area to show actions before and after the spike. Another great feature is being able to print all sensors in a spread sheet format that allows you to quickly pinpoint the sensor that started the chain reaction. Example: A 1998 Ford Crown Victoria may display more than 400 data paramaters (PIDS)! Also diagnostic printouts impress customers and makes it easier to sell service. The printouts facilitate service in several ways:
Merchandising service using the diagnostic printout To show the effect of the graphical scan tool software, we will use the following case studies: Case Study 1 - Defective ECM?A case study from Wayne Miller, Waukesha, Wis.wrmiller@execpc.com Vehicle: 1991 General Motors Lumina - 3.1L engine. Complaint: Customer complaint was stalling and check engine lamp on. Codes 15, 16, 21 and 43 were present. Graphs taken running at idle using record on its first stall that then required a couple of crank times for restart. ECM was replaced and all lines were flat at idle. This example of graphical data shows an ECM/PCM problem that may have been difficult to analyze using digital data alone. The graphs show very sharp and unusual change indicating a defective ECM.
Graphical Line Characteristics: When a line changes direction, pay attention to the way it makes a turn. Is the line sharp or rounded? Does the inside angle vary or remain constant? Does the amplitude of the line remain the same, change randomly or repeat?
Case Study 2 - A Graphical Repair!Vehicle: 1993 Pontiac Grand Am - 3.1L V6 automatic transmission. Complaint: Intermittent Check Engine Light; DTCs = 26 Quad driver Fault, 39 TCC Malfunction
The transmission had been recently rebuilt by a local transmission shop and sent to a local repair shop for Mil problem after rebuild. Repair shop checked codes and replaced TCC solenoid and ECM. The problem was still there. While running the car on a dynomometer, the problem was easy to duplicate. After running 40-45 mph for a couple of minutes, the check engine lamp came on. With every occurrence, the same DTCs were set.
Using VT-100 mode provides a large list of parameters to view. However, it is still an alphanumeric display. With more parameters to focus on, the intermittent problem becomes buried in a large list of data. Circuit Description: Power from the fuse is routed through the brake switch to the TCC line switch. This switch closes in second and third gear, providing power to the TCC solenoid. Each quad driver module in the ECM has a sense line and a fault line. When the TCC is commanded on, the voltage on the sense line is low, and when the TCC is commanded off, the voltage on the sense line is high. DTC 26 sets when the ECM is commanding a controlled component on, and the voltage on the sense line is high, or if the component is commanded off and the voltage on the sense line is low. This can be monitored by watching the QDM fault line on the scan tool. High = Fault; Low = OK. By studying the wiring diagram and using the graphed information shown, the problem is easily solved. Look at the faults indicated by the QDM sense line. The ECM is expecting to see battery voltage at the sense line. With every QDM high reading, the ECM is seeing low voltage. Remember power is supplied to the TCC through the brake switch. However, the brake switch reading consistently shows open. With the use of graphed scan data we have eliminated several problems and are left with two possibilities: 1 = Open TCC Pressure Switch (2nd gear switch) 2 = Poor Connection at the ECM A quick check with a voltmeter confirmed that indeed there was a continuity problem with the inline pressure switch. A scan tool software graphics program will allow you to display, analyze and print vehicle data using the scan tool of your choice. Most can display scanner data in test or graphic formats. These programs can be used to display live engine data, review a snap shot or recall a previously saved file. This makes displaying and analyzing data parameters quick and easy. You may :
|
|||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||||