![]() ![]() Instead of, the DTC descriptions usually pretty detailed and informative. 1994-2003 – provide no malfunction sub-code and status info (except standard OBDII codes that may have Confirmed or Pending status). We conditionally divide the ECUs into 3 groups: If any switch is broken, the corresponding OD code will be thrown.įormat and information, provided in DTC, depends on module. In order to find this out, operator has to run the module self-test with all doors opened. So the module cannot recognize if the door is closed, or the switch is damaged. For example, BCM/GEM module usually has no ability to detect door ajar switch malfunction as when the door is closed, the switch circuit is normally broken. Self-test/OD codes are helpful in case of malfunction that cannot be detected without operator’s assistance. OD codes are generated during a self-test (on demand test) called by operator. Operator doesn’t need to perform any action to generate these codes, but just read them from the module memory. CM codes are thrown by a module if it detects an issue during its regular work. In Ford/Mazda diagnostic, there are 2 kind of codes: Continuous Monitoring (CM) and On Demand (OD). Otherwise, if the issue is not important enough, the driver will not see it until next visit to a workshop. In the last case the module lights its malfunction indicator lamp (MIL) up so the issue becomes visible for the driver. The priority of the issue may vary in range from not really important (rather some kind of warning) to crucial. Generally speaking, if a module finds an issue, it throws a diagnostic trouble code so a technician can read it and realize the issue exists. So it is important to understand what DTC is and how it works. Try to learn other users’ experience (can be found using Google by DTC or problem description).Īs you may see, read and analysis of diagnostic trouble codes is the first thing that has to be done. The workshop manual may contain a lot of helpful information, including pinpoint tests and diagnostic charts. Try to get more information using a workshop manual for the vehicle, if it is available. Obtain additional information using FORScan datalogger (read PIDs). If the DTC description provided by FORScan doesn’t contain enough information, go to Step 5. If there is no any code related to the problem, go to Step 6. Check for diagnostic trouble codes (DTC). ![]() In simple case, the troubleshooting sequence is: This article is written for people that have no these skills yet but looking for a start point. It means that FORScan operator must have at least some basic knowledge of troubleshooting principles in order to use it effectively. In contrast to majority of OBDII applications, FORScan is designed to use service level abilities, like a professional equipment. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |