Diving into the world of car diagnostics can be both exciting and a little daunting, especially for newcomers. Like many Mazda owners keen to understand their vehicle better, I recently decided to explore the capabilities of OBD2 (On-Board Diagnostics II) applications. My journey began with acquiring an OBDLink LX Bluetooth scan tool, a Samsung Tab A 7* tablet, and the popular TorquePro software. My aim? To gain deeper insights into my Mazda CX-5’s performance and health using a Mazda Obd2 App.
Choosing the OBDLink LX was a deliberate decision, driven by strong recommendations from various review sites. The added security of a passcode connection, preventing unauthorized access, and the availability of firmware updates were also significant factors in my choice. Connecting the OBDLink LX to my Samsung tablet proved to be a straightforward process, setting the stage for exploring the TorquePro app.
As a novice in the realm of OBD2 apps, my initial impression of TorquePro is still forming. One immediate observation is the limited availability of comprehensive documentation, a common challenge when venturing into such software. Understanding the full scope of features before purchase can be tricky, and I quickly noticed that TorquePro doesn’t include pre-configured PID (Parameter ID) sets specifically tailored for Mazda vehicles.
Setting up TorquePro for a generic CUV (Crossover Utility Vehicle) and connecting to the OBDLink scanner provided a list of generic CUV PIDs. These PIDs were categorized by status: “No Active Sensor seen,” “Active Sensor seen but not receiving data,” and “Active Sensor, receiving data.” This initial scan offered a glimpse into the data accessible through a generic OBD2 profile.
However, my exploration soon hit a snag. Disappointingly, I couldn’t find a PID for Engine Oil Pressure within any of the generic PID sets. This was particularly frustrating as monitoring engine oil pressure was a primary reason for my foray into OBD2 apps. Even delving into the Ford-specific profile within TorquePro yielded no Engine Oil Pressure PID. This absence raises questions: Is engine oil pressure monitoring fundamentally unavailable through generic OBD2, or is it Mazda-specific data not readily accessible in TorquePro’s default configurations?
The ability to add Custom PIDs offers a potential workaround, but this requires further investigation and knowledge I’m still developing. It’s surprising that Engine Oil Pressure, seemingly a fundamental engine parameter, isn’t included as a standard gauge if the vehicle is equipped with a sensor. This leads to the question: Do Mazda oil pressure sensors function merely as switches, triggering a warning light at a preset minimum pressure, rather than providing continuous pressure readings via a sending unit? Input from experienced users on whether FORScan, another popular OBD2 software, offers an Oil Pressure PID for Mazdas would be greatly appreciated.
On a more positive note, finding a Transmission Temperature PID that “Receives Data” in my CX-5 within TorquePro was encouraging, especially considering reports of difficulty locating this parameter in some software. During a short 20-mile trip, I observed that the Transmission Temperature reading mirrored the Engine Coolant Temperature (198°F). Online forums suggest this behavior is common initially, with Transmission Temperature eventually rising above Engine Coolant Temperature after extended driving, and remaining elevated. My interest in transmission temperature primarily stems from the need to reach a specific temperature for accurate fluid level checks, and not from concerns about towing (as I only plan to tow a small boat).
Further investigation revealed a crucial correction: the Transmission Temperature PID in TorquePro, in my case, actually reads the coolant temperature. This became apparent when I added a coolant temperature gauge alongside it and observed them tracking identically.
TorquePro does offer a HUD (Heads-Up Display) feature, projecting gauges onto the windshield for nighttime viewing. While I haven’t tested this at night yet, daytime use revealed the display to be washed out in bright conditions. The app’s support for multiple Profiles is a useful feature, allowing customized setups for different vehicles.
One significant drawback of TorquePro is its user forum. The forum’s layout is poorly structured, lacking topic-specific sections and relying on a dated, page-based navigation system. Finding relevant information within its threads appears challenging, despite the presence of a search function.
Finally, a note on the Samsung tablet choice: The 7-inch size was ideal for mounting in the dash trough of my CX-5, allowing it to be easily lowered for accessing the infotainment screen and raised for viewing gauges. However, a significant oversight on my part was the realization that polarized sunglasses render the tablet screen invisible when mounted horizontally. This unexpected issue, discovered after carefully planning the mounting setup, highlights the importance of considering even seemingly minor details in practical application. Despite this setback, the exploration of Mazda OBD2 apps and the initial experience with TorquePro remain a valuable learning process, prompting further investigation and community input to fully unlock the diagnostic potential for my Mazda.
