June 01, 2012

How you can Identify a BMW

All contemporary BMW GT1 models use a number of diagnostic systems. Being able to access these requires specialized hardware. With respect to the system you want to interact, acquiring a scanner or code readers could be either difficult or hard and pricey. Second generation On-Board Diagnostic scanning devices would be the at their most effective and simple to find. Others, for example Supplemental Restraint System air bags, aren't easily available towards the general consumer. Regardless of system, the entire process of locating codes and coming in a diagnosis is comparable.

1

Open the BMW's driver-side door. Consider the lower limb-space underneath the dashboard. There, you'll find 16 pin-receiving Data Link Connector. This DLC outlet is featured in various locations, with respect to the type of BMW you're dealing with. Some may readily seen, but others might be hidden behind an access panel. In case you have trouble finding your BMW's DLC outlet, there's a web-based application that may assist (see Assets).

2

Connect your diagnostic handheld towards the DLC outlet. For many products, this can be a similar process. A BMW OPS Plus scanner or perhaps a code readers typically has a diagnostic cable having a 16-prong plug. Connect the cable towards the device, and plug the cable in to the DLC outlet.

3

Switch your device on. Then slide your BMW's key in to the vehicle's ignition. Change to "On." This can activate the BMW's electrical array. With respect to the tool and the machine you're dealing with, you may even need an energetic engine. If this sounds like the situation, start the automobile's engine at this time around.

4

Wait a couple of seconds to some minute. Your tool and the vehicle's diagnostic system will begin a connection. Some products, once an incoming data stream is detected, will instantly retrieve active trouble codes. If you don't have a very device pre-programmed to get this done, talk to your device's guide. Button designs and general layout differ by logo and kind of diagnostic handheld. Your device's guide will detail the precise instructions regarding how to enter a code-locating command.

5

Examine the codes in your device's screen. The way the codes are displayed also is dependent around the device you use. OBD-II codes are alphanumeric, and also the first letter from the trouble code will specify where the issue is situated. Anti-securing brake codes are usually purely statistical. Many products will even differentiate a code's status. Any code listed as "pending" are infrequent malfunctions these complaints haven't triggered your BMW's warning lights.

6

Copy the active trouble codes onto another piece of paper. If you work with several scanner and troubleshooting several diagnostic system, make certain you classify their list. Posts are helpful methods to organize trouble codes. This is especially true for OBD-II diagnostics, which functions being an umbrella for various kinds of codes. For example, P-codes cover the BMW's powertrain, while B, C, and U codes cover your body, chassis and network communications system.

7

Lookup each code drawn in the BMW. Some device hand books contains coding definitions. BMW Scanner 1.4.0 devices, for instance, offer generic coding lists great for all publish-1996 automobiles. However, you'll have to use the internet to locate BMW's supplemental OBD-II codes. Typically, an automobile's user guide won't contain coding definitions for just about any diagnostic system. However, trouble codes may be easily obtained online (see Assets).

8

Copy the right definitions for their corresponding trouble codes. Go through all the definitions and come to a decision. If you possess the mechanical experience, you can try DIY fixes on a few of the problems. However, some diagnostic systems, like ABS brakes, are extremely complex and really should be deferred to some trained auto technician.

9

Take your code list along with you, if you choose to consult a BMW-licensed auto technician. Their list could save you profit diagnostic costs.

Posted by: obd2tool at 02:53 AM | No Comments | Add Comment
Post contains 653 words, total size 5 kb.

Comments are disabled. Post is locked.
17kb generated in CPU 0.0091, elapsed 0.0279 seconds.
33 queries taking 0.0208 seconds, 143 records returned.
Powered by Minx 1.1.6c-pink.