The excitement around Bluetooth OBD2 devices for vehicle diagnostics is palpable, and I recently decided to try one out myself. My initial focus was on using it for basic settings adjustments, particularly on older vehicles equipped with VE rotary pump diesel engines. While the experience has been mostly positive, I’ve encountered a notable issue concerning communication timing during basic settings on these specific models. Interestingly, this problem doesn’t seem to manifest in newer PD (Pumpe Düse or unit injector) diesel engines.
VE Pump Timing Challenge
Currently, this communication timing issue prevents the accurate checking of injection pump base timing on VE rotary pump cars using this Bluetooth OBD2 tool. This is a significant drawback for anyone working on these older diesel engines, as precise timing is crucial for optimal performance and fuel efficiency. I promptly reported this feedback to the developers, and I must commend their responsiveness. They were quick to acknowledge the issue, and I even received a software update shortly after reporting it. However, I have yet to thoroughly test if this update has resolved the VE pump timing issue. My initial tests on AHU and ALH engine codes before the update clearly demonstrated the problem. During the basic setting procedure, the glow plug light flash rate behaved erratically, and the pump timing readings in field 2 fluctuated wildly, making it impossible to obtain a stable and reliable measurement. This stands in stark contrast to the consistent and accurate readings I am accustomed to when using VCDS (Vag-Com Diagnostic System) for the same task.
Development in Progress and Promising Potential
It’s important to remember that this Bluetooth OBD2 tool is still under active development. Based on my experience and the responsiveness of the developers, I am optimistic that this VE pump timing issue will be resolved in future updates. Like with any product, identifying and fixing bugs relies heavily on user feedback. Reporting issues allows developers to investigate, implement solutions, and improve the product for everyone. I’ve even contributed suggestions to Ross-Tech for VCDS in the past, and both companies demonstrate a commitment to addressing user-reported issues and providing ongoing updates.
I intend to rigorously test the latest software update to determine if the basic settings issue has been resolved and will share my findings soon. It’s worth noting that I routinely use VCDS and have done so since 2006. VCDS remains my benchmark for comparison and a tool I rely on daily.
Core Functionality is Solid
Beyond this specific VE pump timing challenge, the Bluetooth OBD2 adapter performs admirably, largely aligning with other user reviews. It effectively accesses various control modules, enabling functions like adaptation, coding, basic settings (with the noted VE pump exception), fault code reading and clearing, and accessing measured values. All the fundamental diagnostic capabilities expected from a professional-grade scan tool are present. However, in its current state, VCDS offers a more refined and user-friendly experience, particularly due to its superior label files and integrated hints and tips, which simplify complex procedures and interpretations.
Looking ahead, the developers are actively working on a long coding helper, designed to function similarly to the highly regarded long coding assistant in VCDS, specifically for Mk5 and newer vehicles. While still a work in progress, this feature holds significant promise and could substantially enhance the tool’s capabilities for newer VW/Audi models.
In conclusion, this Vcds Bluetooth Obd2 alternative shows considerable potential and provides access to essential diagnostic functions. While the current VE pump timing issue needs resolution, the developers’ responsiveness and ongoing development efforts are encouraging. For now, VCDS remains the more polished and feature-complete solution, but this Bluetooth OBD2 tool is definitely one to watch as it matures.
