Search the Community

Does anyone know of an app that lists the voltage outputs on pins from the obd2 port in near real time via a Bluetooth dongle? If not this would be a good one to have.

For 2000-2002 Year Trucks (For Owners Without Code Readers) Insert your ignition key. Turn it to the OFF position. Now turn it ON, OFF, ON, OFF, ON in less than 5 seconds. Leave it in the on position. In the odometer display it should start to display codes. It starts with P PCU errors. This is to notify you that the error codes are coming. They would show up as Pnnnn. All error codes are listed in 4 digits. Write down all Pnnnn error codes that are displayed. P Done will notify that P PCU error code list is done. Now we display P ECU errors. This is to notify you that the error codes are coming. They would show up as Pnnnn. All error codes are listed in 4 digits. Write down all Pnnnn error codes that are displayed. This is notify that P ECU error code list is done. Now turn your key off. Here is a demonstration of it. http-~~-//www.youtube.com/watch?v=7XQJmaIF9Do Now take notice to the error codes displayed. Powertrain Control Module (P PCU)Engine Control Module (P ECU)P0500 - Speed Sensor Error P1693 - Companion CodeP0236 - Boost Too High Too Long P1693 - Companion Code Now notice the P1693 popped twice. There is a reason for it. Like if you have an error in the ECM then the P1963 will be displayed in the PCM. If there is a error in the PCM then the P1693 will be displayed in the ECM. Now in my case I had errors on both side so the P1693 was displayed on both modules to alert you that there is errors in both. Always make sure you see P Done Twice! It really common to see on the forums where some says "Oh my I got a P1693 and that's it" It's impossible to have just a P1693 error code by itself. So more that likely the owner saw the P Done and shut the key off and didn't allow for the ECM to display its errors. Also read my thread over at CumminsForum.Com concerning this issue... http://www.cumminsforum.com/forum/98-5-02-powertrain/139687-p1693-codes-solo.html For 1998-2002 Year Trucks (For All Code Readers) The PCM and ECM monitor many different circuits in the powertrain system. If the ECM or PCM senses a problem with a monitored circuit often enough to indicate an actual problem, it stores a Diagnostic Trouble Code (DTC) in the ECM’s or PCM’s memory. With certain DTC’s, if the problem is repaired or ceases to exist, the ECM or PCM cancels the code after 40 warm-up cycles. Certain other DTC’s may be cancelled after 1 or 2 good “trips”. Refer to Trip Definition. DTC’s that affect vehicle emissions illuminate the Malfunction Indicator Lamp (MIL). The MIL is displayed as an engine icon (graphic) on the instrument panel. Refer to Malfunction Indicator Lamp. Certain DTC’s will set a “P1693 companion DTC” in the opposite control module. This means that after repair, the DTC must be erased from both modules. Certain criteria must be met before the ECM or PCM will store a DTC in memory. The criteria may be a specific range of engine RPM, throttle opening, engine temperature or input voltage. The ECM or PCM might not store a DTC for a monitored circuit even though a malfunction has occurred. This may happen because one of the DTC criteria for the circuit has not been met. For example, assume the DTC criteria requires the ECM to monitor the circuit only when the engine operates between 750 and 2000 RPM. Suppose the sensor’s output circuit shorts to ground when engine operates above 2400 RPM (resulting in 0 volt input to the ECM). Because the condition happens at an engine speed above the maximum threshold (2000 rpm, the ECM will not store a DTC. There are several operating conditions for which the ECM and PCM monitors and sets DTC’s. Refer to Monitored Systems, Components, and Non-Monitored Circuits. Technicians must retrieve stored DTC’s by connecting the DRB scan tool (or an equivalent scan tool) to the 16–way data link connector (Fig. 3). Refer to the Diagnostic Trouble Code chart (list). Remember that DTC’s are the results of a system or circuit failure, but do not directly identify the failed component or components. Various diagnostic procedures may actually cause a diagnostic monitor to set a DTC. For instance, disconnecting a relay or removing an electrical connector while the engine is running. When a repair is completed and verified, connect the DRB scan tool to the 16–way data link connector to erase all ECM and PCM DTC’s and extinguish the MIL. Diagnostic Trouble Code Listing Diagnostic Trouble Code chart (PDF File) Self Erasing Of Error Codes Trip Indicator The Trip is essential for running monitors and extinguishing the MIL. In OBD II terms, a trip is a set of vehicle operating conditions that must be met for a specific monitor to run. All trips begin with a key cycle. Good Trip The Good Trip counters are as follows: ● Specific Good Trip ● Fuel System Good Trip ● Misfire Good Trip ● Alternate Good Trip (appears as a Global Good Trip on DRB III) ● Comprehensive Components ● Major Monitor ● Warm-Up Cycles Specific Good Trip The term Good Trip has different meanings depending on the circumstances: ●If the MIL is OFF, a trip is defined as when the Oxygen Sensor Monitor and the Catalyst Monitor have been completed in the same drive cycle. ● If the MIL is ON and a DTC was set by the Fuel Monitor or Misfire Monitor (both continuous monitors), the vehicle must be operated in the Similar Condition Window for a specified amount of time. ● If the MIL is ON and a DTC was set by a Task Manager commanded once-per-trip monitor (such asthe Oxygen Sensor Monitor, Catalyst Monitor, Purge Flow Monitor, Leak Detection Pump Monitor, EGR Monitor or Oxygen Sensor Heater Monitor), a good trip is when the monitor is passed on the next startup. ● If the MIL is ON and any other emissions DTC was set (not an OBD II monitor), a good trip occurs when the Oxygen Sensor Monitor and Catalyst Monitor have been completed, or two minutes of engine run time if the Oxygen Sensor Monitor and Catalyst Monitor have been stopped from running. Fuel System Good Trip To count a good trip (three required) and turn off the MIL, the following conditions must occur: ● Engine in closed loop ● Operating in Similar Conditions Window ● Short Term multiplied by Long Term less than threshold ● Less than threshold for a predetermined time If all of the previous criteria are met, the PCM will count a good trip (three required) and turn off the MIL. Misfire Good Trip If the following conditions are met the PCM will count one good trip (three required) in order to turn off the MIL: ● Operating in Similar Condition Window ● 1000 engine revolutions with no misfire Warm-Up Cycles Once the MIL has been extinguished by the Good Trip Counter, the PCM automatically switches to a Warm-Up Cycle Counter that can be viewed on the DRB III. Warm-Up Cycles are used to erase DTCs and Freeze Frames. Forty Warm-Up cycles must occur in order for the PCM to self-erase a DTC and Freeze Frame. A Warm-Up Cycle is defined as follows: ● Engine coolant temperature must start below and rise above 160° F ● Engine coolant temperature must rise by 40° F ● No further faults occur