Re: OBD II reader and Forscan program.
|
|
Quote:
Originally Posted by mif73
Hi guys.
I posted a question about forscan and O2 sensors amplitude in the ecu section but i have no replies as yet, so i will try here 
Other post:
http://www.fordforums.com.au/showpos...81&postcount=1
I also managed to get the engine running test to work once and it showed dtc po116 (ect) even though forscan shows 87deg and gauge is normal.
I also found one table under fuelsys shows error in cmp(cam pos sensor) while the engine is running.
There are no dtcs when i first connect to the car.
Has anyone else come across these issues?
Cheers, Andrew |
I made an error. There are two fuelsys pids, one says closed as in closed loop, the other
Says error.
The other ones are cmp_f =yes fault, the other is cmp level=LOW.
I didnt get any other faults in engine running test or dtc .
I did unplug an O2 sensor while engine running with no dtc and measured with a meter. It was sitting at 0.5v unplugged from car.
I still wonder why forscan displays over 2v for o2 sensors?
__________________
Weekend Toy: S1 AU Fairlane V8 with LTD bits, Tickford 17" wheels, front and rear chin spoilers, series 2 front brake conversion with Super pro bushes, Pacemaker headers, rear muffler removed, Kings/Pedders lowered suspension, Koni adj rears, painted headlight bezels, HR 2300kg hitch, 2 stage shift kit, trans cooler, reverse cam and media player.
Wife unit's : 2010 update FG XR6, reverse cam, HR 2300kg Hitch, German Maestro speakers, parcel shelf sub, trimmed mudflaps, batman stickers.
Last edited by mif73; 22-02-2014 at 04:11 PM.
|