So what is a BMW OBD2 scanner? OBD stands for on-board diagnostics, and the current standard is OBD2. BMW began installing the 16-pin OBD2 socket in its vehicles from 1996. Prior to this, the OBD1 standard was used. OBD2 has been mandatory in vehicles with gasoline engines since 2001, and diesel-engined vehicles since 2004. The socket can be found beneath the steering wheel of your BMW. With the appropriate BMW OBD2 scanner, you can read and analyze stored error codes that often provide information about the condition of your BMW, as well as the opportunity to customize certain aspects of it.
Crack Obd Diag Scan
Today, the MIL is part of the OBD for all vehicles. New regulations also require monitoring of the surveillance conducted by the system. The reason for this requirement is the fear that diagnoses would not be carried out regularly over the service life and influence the values. So now diagnoses must be recorded and must also be made at a certain interval. The results should then be read out via a serial interface with standardized protocols and via the CAN bus, which we will learn about later.
Sp OBD was in effect born out of an interest to control emissions. As time and technology progressed, the function range of OBD has been vastly expanded. In addition to the environmentally relevant task areas originally envisaged, safety-relevant aspects were added to the vehicle diagnosis. Areas such as seat belt systems and airbags, faults such as short circuits or line interruptions, problems that could cause possible engine damage, maintenance instructions such as maintaining correct oil level, and more. The OBD has become much more than a mere emissions monitoring system today.
This simple example illustrates the importance of a BMW OBD2 scanner. Those who regularly read the control units themselves via such adapters and scanners have saved a fair bit of money because they were able to check and understand the fault, saving themselves a trip to the workshop and paying for a corresponding scan. Self-scanning allows one to determine if the problem is minor or serious, and act accordingly. If you want to know more about reading devices, we recommend our other articles on this topic.
The socket has a total of 16 poles, all of which are assigned to different tasks or buses. The manufacturers can customize seven of these poles to their requirements. Therefore, these often differ from manufacturer to manufacturer. For BMW vehicles, the BMW OBD2 scanner connector poles are as follows:
The two lines are primarily required for diagnosis and readout and are used specifically for external communication. This is useful, for example, if you want to look through your BMW with a readout device, since the lines are involved in the on-board diagnosis of control units. As stated, the transmission can only take place in one direction at a time, but as soon as this transmission is interrupted, it can also take place again in the other direction. The property of a bus remains, however, as communication with several control units is still possible via the same cable. As soon as a control unit is addressed, communication is carried out with it until another control unit is addressed.
Control units are minicomputers that are connected to the most important components such as the engine or components that provide comfort such as the climate control system. They are responsible for ensuring everything runs smoothly. They are all connected via the CAN bus and can be read out using a BMW OBD2 scanner.
There are three different ways to read your BMW and we will briefly touch upon each one, with the possible advantages and disadvantages too. These methods include reading out using a diagnostic device, using software, and using an app. All three methods require access to the OBD system, and therefore, a generic or specific BMW OBD2 scanner. However, there are differences in the way in which they connect. Some smartphone apps allow a connection via Bluetooth to the OBD scanner, while more advanced software interfaces require a special OBD cable and adapter. Regardless of which way you choose, a diagnosis should be the end result.
Reading out via software is a rare variant among private vehicle owners and drivers. The software runs on a laptop usually unless you have a PC in the garage! Software solutions require a corresponding OBD adapter to communicate between the vehicle and host computer but are packed with features and can perform in-depth diagnoses. The larger screen of a laptop also helps with readability. A software program may be confusing at first glance, but with the help of the user manual, you should get the hang of it.
The last option is particularly popular due to its ease of use. Diagnosis by app is quick and versatile, but many apps may not offer in-depth analyses. They are ideal for a quick check, and some allow coding as well. This solution is the quickest and easiest to understand compared with the first two. Since we at Carly have chosen this way of diagnosis, and are compatible with BMW vehicles, we would like to introduce you to the Carly app in more detail.
The software needs to access the OBD device, which is found at /dev/ttyUSB0. This is owned by root with the group dialout, so the proper way to run the scantool software is to add your user to the dialout group, e.g.:
When researching before trying the software out, I noticed someone recommending you run scantool with root so that it can read the device. While running it with sudo would work, it violates the principle of least privilege: scantool doesn't need superuser privileges to run, it just needs to be able to read the OBD interface. Running it as root is lazy - don't do it!
Hi i'm install this soft on my rasp pi2 and when i going command "scantools" im see this:Version: 1.21 for DOSInitializing All Modules...---------------------------------Initializing Alegro... OKSegmentation fault
Since I'd expect packages for the pi to already be compiled for arm, I think this might just be a case of choosing the wrong port on first run (you have to scroll down to the bottom of the list to get to he USB device). If so, "rm /.scantoolrc" will clear the current configuration and let you try again.
Thanks for this very informative webpage. Just received my USB ELM327 device today.Hooked it up, started the engine and ran scantool, which connected after a little struggle with configuration.For baud rate, device specifications stated 9600 or 38400, not what scantool defaults to.For the COM port, scantool's output to console was helpful.
I was able to run scantool with a cheap BT dongle, but I found it much more useful to just buy Torque Pro app for my phone for $4.99. Nevertheless, I will share how I got it on my Ubuntu 18.04 laptop.I used "1234" as the pairing code, but it would immediately disconnect after briefly connecting. After googling, I found that I could keep it connected thusly:As root, create a file "/etc/bluetooth/rfcomm.conf" with this contents: rfcomm99 bind yes; device 00:1D:A5:0A:FF:AB; channel 1; comment "ELM327 based OBD II test tool"; Then,sudo rfcomm --auth connect 99 00:1D:A5:0A:FF:AB 1Please use your own BT device address for both of these.This procedure will keep your BT connected, and open /dev/rfcomm99 as a the port.However, scantool only recognizes serial ports. To trick scantool into using BT, do this:cd /devsudo rm -f ttyS3sudo ln -s rfcomm99 ttyS3sudo chmod 766 rfcomm99
This kludge tricks scantool into using COM4 port, and worked for my laptop. However, scantool was very limited in its diagnostics, and buggy as well. It crashed my computer when my car threw a fault, although that may be a linux issue. I like the idea of using my laptop, but the phone app was the easy choice here.
Failure/Limitations of Software: The Biggest Variable. Software inside a F.R.E.D. can become corrupted, rendering it unable to communicate with other modules on the bus or scan tool. This is rare, but I have seen it and can recall cases of TSBs issued to perform a reflash to allow a particular module to communicate properly under all conditions.
You hear a new, disturbing noise coming from your engine, open the hood, look around, and find nothing. Now what? Before you reach for a conveniently-placed torque wrench to try the ol' "love tap," hook up a diagnostic tool to get a little bit more intel on what's going on.
Don't make the mistake of thinking a diagnostic tool is a magical solution to fixing all of your vehicular troubles. It's not going to fix a flat or replace a windshield. If it does, that means the built-in AI has gotten a little too intelligent. In fact, the most basic diagnostic tools will only spew nonsense code at you when the Check Engine light is on. So, if you want to get the most out of the tool, you need to know when to use it.
Diagnosing problematic issues your vehicle can detect is pretty easy on paper. Ignoring the high level of mechanic skill you may need, specialized tools for working on the vehicle, and the mind-numbing trial-and-error process that comes with fixing a car, all you really need is the diagnostic tool and a vehicle.
Diagnostic tools tend to be pretty similar in design and function. While some offer more features like advanced statistics/reading capabilities, nearly all of them are plug-and-scan. Therefore, there's only one process you really need to follow.
The basic idea of using a diagnostic scan tool is to get the diagnostic trouble codes your vehicle automatically records when it detects a problem. This is the exact same process that mechanics use when you take it into a garage, just with much fancier, more capable equipment.
Diagnostic tools download data from a vehicle's onboard diagnostic (OBD-II) port. This universal access port will give you access to virtually anything the vehicle detects in terms of issues. To access the information, you need to apply a little juice to the setup. 2ff7e9595c
コメント