Review on 🔵 BlueDriver Bluetooth Pro for iPhone and Android by Mariealphonse Seattle

I don't usually write reviews (this is my first review) but I wanted to write about this device because I think it will be useful for both users and developers. Firstly, this device combines many beautiful technologies. in a small and cheap package. Bluedriver's depth of code reading and real-time data monitoring really can't be matched at this price point. Unfortunately, none of these features worked properly, and I think the developers bit off more than they can chew. I used this unit with an iPhone X running iOS 12.1 to diagnose a 2004 Chrysler Concorde and a 2007 Dodge Grand Caravan. Installing the app was easy, but I often had trouble losing the Bluetooth connection. I've always been able to fix this issue by disabling Bluedriver, restarting the app, or a combination of both. I updated Bluedriver to the latest firmware (2.44 at the time) and saw no improvement. The connection was usually lost when my phone's screen turned off. Often Bluedriver could only read OBDII data and no additional data until I restarted the app. This can be a real problem for smog test readiness indicators and can confuse less advanced users of this product. The Bluedriver indicated my car was going to pass when it clearly broke down. When the Bluedriver enters this state, many of the Bluedriver's readiness indicators become unavailable, such as: B. the evaporator and catalyst systems. Because Bluedriver can't see them, and everyone it sees are marked as done, Bluedriver calls this a pass. I used Bluedriver to diagnose the oxygen sensor and ABS wheel sensor. Bluedriver gave correct codes for both conditions, but in many cases Bluedriver also gives 10 or 20 additional error codes that simply didn't exist. On the first scan, Bluedriver gave me the correct codes, but it also indicated that my ABS and BCM computers had internal errors, followed by other codes that didn't really make sense. Because of the codes, I became concerned that I would have to replace these modules and started investigating these errors. However, when I reread the codes later, I received far fewer codes; Codes that I was sure actually existed. That's when I found out that Bluedriver often reports junk data. In general, the error codes above are correct, but the last ones are garbage. I learned to identify junk sensors simply by rescanning and seeing which ones survived. I tried to diagnose the oxygen sensor using live data. Oxygen sensors switch to a healthy sensor approximately every 100 ms. Unfortunately, Bluedriver updated about once a second, even when only one gauge was displayed. This doesn't make diagnosing the oxygen sensor impossible, it just means that the data you're seeing is only a rough approximation of what's actually going on. This problem is actually minor compared to what I later found. Bluedriver actually injected junk into the stream. The PCM in the car issued a P0138 code indicating the oxygen sensor was stuck high. Looking at the data stream, the stream showed the switching quality of all 4 oxygen sensors, indicating that all sensors were functioning correctly. None of the data was duplicated, meaning the PCM was not simply padding the oxygen sensor data with valid data from another sensor. I was really very confused by this for a few days. At some point I tried to show the real-time car speed sensor, but found that when driving the car, Bluedriver often shows the car speed as 0 when the car is driving on the highway. The speedometer in the car never failed. I realized that the shift quality I was seeing wasn't coming from the oxygen sensor, it was junk data. At this point I replaced the oxygen sensor and the code was gone. The chart looked the same before and after replacing the sensor. This makes it practically impossible to diagnose many sensors and their connections with Bluedriver. Sensors often fail intermittently and this tool actually makes finding the problem harder. I am returning Bluedriver. I really wanted to keep it. I like to fix my own stuff and live data and deep code scanning made real sense to me at that price point. The reality is that this device is a diagnostic tool and has made diagnosing my issues much more difficult than a regular code scanner without live data. I can deal with app bugs, bad UI and things that keep crashing, but I can't deal with bad data. It really messed me up. I respect the vision of this company. This product can replace other big names like Snap-On, however I recommend that users stay away from this product until these issues are resolved. I also recommend that developers pay more attention to data integrity than anything else. It's a tool and people should trust their tools.