Encountering problems connecting your 1996 vehicle to the Torque Pro app with an OBD2 scanner can be frustrating. Many enthusiasts attempting DIY diagnostics with tools like the BAFX scan tool and Torque Pro on their older vehicles report similar issues. Let’s break down common challenges and potential solutions when using Torque Pro on a 1996 OBD2 vehicle, specifically addressing the “ECU Problem” error and inaccurate readings.
It’s understandable to assume a 1996 vehicle is fully OBD2 compliant, as 1996 was the year OBD2 became standard in the USA. However, early implementations could sometimes present compatibility quirks. The error message “ECU Problem. The ECU is reporting that it does not support the reading of any PIDs…” suggests a communication breakdown between the scan tool and your truck’s Engine Control Unit (ECU). Despite this error, the “connected to ECU OK” message at the top might indicate a partial connection, enough to read basic data like RPM, but not the full range of parameters (PIDs).
One common issue is protocol mismatch. While your 1996 ECU should be OBD2 compliant, it might be using an earlier or slightly different protocol version than what Torque Pro expects by default. This can lead to inaccurate readings like a speedometer showing double the actual speed, or sensors like coolant temperature and boost pressure remaining static at incorrect values. The RPM gauge often works because it’s a fundamental engine parameter that is usually communicated even with partial OBD2 compliance.
The problem of the truck shutting down when scanning for faults is more concerning. This could indicate a more significant communication error causing the ECU to reset or misinterpret the diagnostic request as a critical command. It’s crucial to avoid repeated fault scans if this is occurring, as it could potentially cause further issues.
Regarding “Power Stroke PIDs,” this refers to specific Parameter IDs tailored for Ford Power Stroke diesel engines. If you are using Torque Pro with a Power Stroke, correctly configuring these custom PIDs is important for accurate readings beyond the generic OBD2 parameters. Within the Torque Pro app settings, you should explore options for adding or configuring custom PIDs, often found in settings related to “Extended PIDs” or “Plugins.” Online forums and communities dedicated to Torque Pro and your specific vehicle make and model are excellent resources for finding and importing the correct PID configurations.
To troubleshoot these issues, start by verifying your OBD2 adapter is securely connected and compatible with your vehicle’s OBD2 port. Within Torque Pro, delve into the adapter settings and connection types to ensure they are correctly configured for your vehicle. Experiment with different OBD2 protocols within the app’s settings if available. If you suspect PID issues, research and attempt to add custom PIDs relevant to your 1996 vehicle and engine. If problems persist, consulting online forums specific to your truck model and OBD2 diagnostics can provide valuable, model-specific advice. In some cases, the issue might stem from the vehicle’s ECU itself, or less commonly, a limitation of the scan tool’s compatibility with very early OBD2 systems.
