For automotive technicians and DIY enthusiasts, OBDII apps have become indispensable tools for vehicle diagnostics. These apps, when paired with an OBDII adapter, offer a wealth of data, allowing for in-depth analysis of engine performance and health. One crucial parameter often accessed through these apps is balance rates, which provide insights into the performance of individual fuel injectors. However, users sometimes encounter frustrating issues when trying to access this specific data, particularly with certain OBDII adapters and apps.
This article delves into a common problem experienced when using an OBDII adapter with an iOS device and an app like Engine Link, specifically focusing on the challenges of retrieving balance rates. The user initially encountered issues with a newly purchased OBD2 adapter from Amazon. While generic PIDs (Parameter IDs) seemed to function adequately, problems arose when attempting to access more specific, custom PIDs such as injector balance rates.
The typical sequence observed was as follows: upon plugging in the OBD2 adapter, a single red LED would illuminate. Connecting to the adapter’s Wi-Fi hotspot would then activate the remaining LEDs, initiating data transfer and displaying generic PID data within the Engine Link app. However, the app would then prompt a “Fuel System monitoring not correct or possible” message. Following this, the LED status on the OBD2 adapter would become erratic, cycling between all LEDs illuminated and reverting back to a single red LED. This cyclical pattern continued, preventing consistent data retrieval for custom PIDs, including the desired balance rates.
To isolate the source of the problem – whether it was the app or the adapter – the user sought assistance from a friend using an Android phone and the Torque app. While a connection was successfully established with this alternative setup, a similar issue emerged when attempting to select specific PIDs like “Injector Rate” and “Balance Rates.” The connection would intermittently drop, exhibiting the same communication cut-out experienced with the iOS device and Engine Link. Interestingly, during a brief period when both the iOS and Android devices were simultaneously connected with their respective apps, both displayed the same communication problems, suggesting the adapter might be the common denominator.
In a fleeting moment, the Engine Link app on the iOS device momentarily began recording data. Custom PID selections transitioned from grey to green, indicating data availability, and everything appeared to function correctly. However, this state was short-lived, as the system soon locked up, and access to custom PID settings became unresponsive, likely due to the recurring communication failures. A subsequent app reinstallation did not resolve the issue.
Although detailed log files were not saved during this troubleshooting process, the user did recall observing a significantly high misfire count on cylinder 8 (approximately 16,000) compared to other cylinders, which registered misfires in the single to low thousands. This observation, though anecdotal, highlights the importance of accessing custom PIDs like misfire counts and balance rates for a comprehensive diagnostic assessment.
Ultimately, the user decided to return the initially purchased OBD2 adapter. The next step is to acquire the OBD2 adapter specifically recommended by the Engine Link app developers, despite its higher cost (approximately $30.00). This decision underscores the critical role of adapter compatibility and reliability when utilizing OBDII apps for advanced diagnostics, especially when focusing on parameters as vital as balance rates for accurate engine health evaluation. Ensuring seamless communication between the OBDII adapter, the diagnostic app, and the vehicle’s ECU is paramount for obtaining reliable and actionable data.
