reviving an old thread....

I recently picked up Torque Pro and using it with a Vgate Scan Bluetooth OBD scanner. Everything seems to work and I can run tests etc... EXCEPT for trying to see if one of my cylinders is Misfiring. I am looking at test $53 but keep getting " Test incomplete or dependant test failed ".

Anyone have an experience with this for determining misfiirng coil cylinder #'s. I am not getting a CEL, but the truck feels like it is misfiring at idle and feels like it's running out of power hitting 40mph, at which point it feels like I'm driving on train tracks.

2000 V10 6.8 ( I believe OBD1 not OBD2 ) Truck has aftermarket hood, and sticker is no longer there.

Mode $06 report generated by Torque for Android
================================================
Vehicle VIN: Not present
Vehicle Manufacturer: Unknown
Vehicle Calibration ID: Not present
Unit and scaling information are not supplied with the data from the ECU for this type of vehicle. Consulting the manufacturers service book for this information is recommended.
Test report:
------------------
TID:$01 CID:$11
- Rich to Lean sensor threshold voltage(constant)
Min: 0
Test result value: 1,024
PASS
----
TID:$01 CID:$21
- Rich to Lean sensor threshold voltage(constant)
Min: 0
Test result value: 1,024
PASS
----
TID:$03 CID:$01
- Low sensor Voltage for switch time calculation
Min: 0
Test result value: 461
PASS
----
TID:$03 CID:$02
- Low sensor Voltage for switch time calculation
Min: 0
Test result value: 512
PASS
----
TID:$01 CID:$11
- Rich to Lean sensor threshold voltage(constant)
Min: 0
Test result value: 1,024
PASS
----
TID:$01 CID:$21
- Rich to Lean sensor threshold voltage(constant)
Min: 0
Test result value: 1,024
PASS
----
TID:$03 CID:$01
- Low sensor Voltage for switch time calculation
Min: 0
Test result value: 461
PASS
----
TID:$03 CID:$02
- Low sensor Voltage for switch time calculation
Min: 0
Test result value: 512
PASS
----
TID:$53 CID:$01
-
Test incomplete or dependant test failed
--
TID:$53 CID:$02
-
Test incomplete or dependant test failed
--
TID:$53 CID:$03
-
Test incomplete or dependant test failed
--
TID:$53 CID:$04
-
Test incomplete or dependant test failed
--
TID:$53 CID:$05
-
Test incomplete or dependant test failed
--
TID:$53 CID:$06
-
Test incomplete or dependant test failed
--
TID:$53 CID:$07
-
Test incomplete or dependant test failed
--
TID:$53 CID:$08
-
Test incomplete or dependant test failed
--
TID:$53 CID:$09
-
Test incomplete or dependant test failed
--
TID:$53 CID:$0a
-
Test incomplete or dependant test failed
--
TID:$01 CID:$11
- Rich to Lean sensor threshold voltage(constant)
Min: 0
Test result value: 1,024
PASS
----
TID:$01 CID:$21
- Rich to Lean sensor threshold voltage(constant)
Min: 0
Test result value: 1,024
PASS
----
TID:$03 CID:$01
- Low sensor Voltage for switch time calculation
Min: 0
Test result value: 461
PASS
----
TID:$03 CID:$02
- Low sensor Voltage for switch time calculation
Min: 0
Test result value: 512
PASS
----

End of report.

 

Did you also install the TorqueScan plugin? Add Ford PIDs support (go to settings->Manage extra PIDS/sensors->menu->add predefined list->Ford)? Seems to me I also installed the 6.0L PIDs since I sometimes see one of them.

 

I did see the list and when I clicked one of the PIDS after pressing Ford, I see a screen that I need to scroll down to I can press the "Test" button. When I press test I get a small window saying testing , but ' No Response' message then appears as well. I press some of the other PID's and they work fine. For some reason the Misfire cylinders test is not responding. I ran the car to normal operating temps, and left the scanner test running the " Real Time " for over 5 minutes. Still always got the same result as the log file.

Is there any other software other than Torque that I can try to check for misfires in cylinders, or are they simply not monitored / tested regardless of which of scanner.

Thanks !

 

Did you go to the "Test Results" screen? that's where they show up on mine.

 

How long has it been since it was last reset or you had an empty battery ?
It usually takes a while for these to show a value. It did on my 2000 obd2 EX

 

Yep - went into Test Results. Actually that's where I was able to get the log file from that I copied to my earlier post. Battery was replaced about 3 years ago and no issues other than what seems to be misfiring at idle and horrible past 40mph.

I just thought of something -- Since I have the SCT2 also, is there a way to plug the SCT tuner to the SCT software on my laptop and monitor cylinder misfires from there ?? - Just a thought.

 

You can take a look at Dashcommand.

 

I don't remember the specifics, but it won't work if you recently reset your codes. If you did, you had to accelerate to 65 mph then slow to 40 mph or so, without using the brakes, several times.
Don't quote me on that since it's been a while since I went through that procedure.

 

Figured I would add this info as it may be helpful.

$50- Misfires that cannot be attributed to a specific cylinder
$51- early model Ford systems for misfire
$53- Later non CAN systems for misfire
$0B- CAN Systems misfire history/last 10 drive cycles
$0C for current/last performed

 

That OBDI system will not see or log misfires. Due to the GVWR (emissions calibration).

 

Obviously, you have failed to read the whole thread....

 

Just noticed today that my 2005 V10 is california/OBD II compliant per the sticker under the hood. It was sold new in Texas.

 

I just used my torque and obd2 plug on my 2002 v10 x to diagnose a bad misfire on cylinder 7. It wasn't bad enough to trip the cel, but was logged in the "logged faults" folder. bought a new motorcraft cop, popped it in there and test drove for about an hour running errands and no more faults.

Saved me a pile of work and $$ guessing Which cylinder was misfiring.

 

Guys,
I'm new to the forums and have done quite a bit of reading before posting this. I don't think what I'm specifically looking for has been covered, but it's entirely possible I've missed things.

The short version is that my 99 F250 V10 SD has a couple problems. 52,xxx original miles, been in the family since it was built (no I will not sell it to you).

Issue 1 is that the check engine light is coming on occasionally at start up and seems to be related to starting right back up when hot (especially when towing). There is a severe loss of power (I can't pull my 9000lb RV) and have to wait 5-10 minutes for it to cool down before I can start and the light goes off and power is restored.

Issue 2 is that if the OBD reader is inserted into the plug on the truck BEFORE starting, it creates a similar situation with the check light and power loss. Discovered this at the emissions test station when the guy failed me. If you plug the reader in after starting there are no issues.

I've had the Torque app for a long time and have used it a little, but am by no means good with it. I'm seeing a couple red items in the test list that appear to be failures. I'd like to start there. From the posts in this forum, I think, but am not sure, that I have an OBD I system (it was purchased in Missouri).

I'm going to post a picture of the emissions sticker (for OBD identification)

and some of the Torque data. I'm seeing 2 failures in the test results.

Thanks in advance for the guidance from you guys that have way more experience with this stuff than I.

Mode $06 report generated by Torque for Android
================================================

Vehicle VIN: Not present
Vehicle Manufacturer: Unknown
Vehicle Calibration ID: Not present

Unit and scaling information are not supplied with the data from the ECU for this type of vehicle. Consulting the manufacturers service book for this information is recommended.

Test report:
------------------
TID:$01 CID:$11
- Rich to Lean sensor threshold voltage(constant)
Min: 0
Test result value: 767
PASS
----
TID:$01 CID:$21
- Rich to Lean sensor threshold voltage(constant)
Min: 0
Test result value: 731
PASS
----
TID:$03 CID:$01
- Low sensor Voltage for switch time calculation
Min: 0
Test result value: 461
PASS
----
TID:$03 CID:$02
- Low sensor Voltage for switch time calculation
Min: 0
Test result value: 512
PASS
----
TID:$10 CID:$11
-
Max: 45
Test result value: 32
PASS
----
TID:$10 CID:$21
-
Max: 49
Test result value: 65,535
FAIL
----
TID:$41 CID:$11
-
Min: 64,640
Test result value: 257
FAIL
----
TID:$41 CID:$12
-
Max: 1,078
Test result value: 257
PASS
----
TID:$45 CID:$20
-
Max: 26,423
Test result value: 13,510
PASS
----
TID:$4a CID:$30
-
Min: 1,408
Test result value: 1,772
PASS
----
TID:$4b CID:$30
-
Max: 26,214
Test result value: 8,306
PASS
----
TID:$53 CID:$01
-
Max: 64,768
Test result value: 64
PASS
----
TID:$53 CID:$02
-
Max: 64,768
Test result value: 129
PASS
----
TID:$53 CID:$08
-
Max: 64,768
Test result value: 64
PASS
----


End of report.

 

My 02 V-10 runs OBDI software in a OBDII computer. Mine has an 8900lb GVWR. Now the 5.4 equipped trucks had an 8600lb GVWR and those were equipped as an OBDII system. 8600 was the cutoff, 8601 and up back then was OBDI when it was federal emissions. It's a numbers game when it comes to the emissions game!

In fact back in the late 90's early 2000's some cars that were badged as ULEV had 3 or 6 O2 sensors! It was crazy until VVT came around.