Ilovemyfez

Hi,

i purchased an elmscan 320 interface and obdii cable from scantools.net to use with my ford fiesta 1.25 zetec-se (lx)
it's a w-reg (2000).

Unfortunately i just cant get it to work! it would appear the laptop can communicate with the interface box using the serial cable, but the interface box is just getting no response from the ECU at all! Just get NO DATA... I have checked the pin config on the interface port and it should support PWM.. however apparently it has a pin 7 which most fords dont have :S

i was wondering if my car may have a siemens ecu as some fiestas do have? mine was an import from jersey ...

Any ideas would be much appreciated

Duncan

andyhardy

You have to be really careful what software and interface you get for the OBD2 diagnostics - what kit did you buy exactly?

Cheers,

Andy

andyhardy

Actually - you're right on the border for European cars, I can't say 100% whether your car has OBD2 or not?

Is it EEC-IV or EEC-V management?

Cheers,

Andy

ECU Monitor Enthusiast

iTrader: (1)

W reg is TOO early for the OBD2 scan tool standard which became MANDATORY for cars sold from year 2000 onwards.

You will need a ford STAR tester or Ford SCP compatiable scan tool to read fault data !

Or go to halfords and buy a cheap flash code tool !

I used to work in this exact industry designing these scan tools so I do know a bit about it !!

Ilovemyfez

ford told me the car should have the EEC-V engine management unit .....
I know someone on zsoc who apparently has a w-reg fiesta (may be zetec-s though) who has got this tool to work

it was the elm320 interface chip from scantools.net!

i was looking at those cheap flashcode tools but they have weird 3pin/5pin connectors, not obdii style connectors!.... i dont think they allow you to remove the code either.

the reason im trying to get this working, is because my dash is displaying two DTC codes, 5967 and 9359. i cant find the meaning to them anywhere, they must be ford specific codes! .....

many thanks for the replies

ECU Monitor Enthusiast

iTrader: (1)

Those codes are defo manufacturer specific !!!

NOT all EEC5 cars are OBD2 compatiable.

Just looked in my extensive database and those codes are NON existant.

Even if you managed to read these codes directly from the ECU,
the scan tool is VERY unlikely to display the text meanings for them.

However, EEC4 and 5 are prone to storing fault codes that are GHOST's.
The car will still run correctly even when these are present.

I really do suspect you will eventually go to a Ford dealer to find out the true meaning !!!

Good luck.

Ilovemyfez

yeah i know i kinda guessed they were manufacturer specific, but i was hoping the scan tool would bring up any faults that may be present, or perhaps the codes were just a manufacturer-specific mask for the real code....

the annoying thing is, i cant remove them tried disconnecting the battery and removing the ECU related fuses etc... no good. unless they are still active.

Another one popped up the other day!

my car has an obdii port with pins 2, 4, 5, 7, 10 and 16 populated.

Thanks

Duncan

ECU Monitor Enthusiast

iTrader: (1)

EEC5 runs a protocol called SCP (standard corporate protocol)
A version of this WAS included in the OBD2 standard called J1850.

Beware, NOT all scan tools can read FORDS as they use this unique J1850 protocol
and usually only more expensive/full featured tools will read them.

You cannot reset codes on and EEC5 ecu by removing power.
Can ONLY be removed with proper scan tool.

Dave Henshall

damn those ford peeps

Ilovemyfez

Thank you for that information ...

I believe this tool does support/use J1850 yeah, PWM.
The tech support guy of scantools.net did say that the elm320 interface i have should work with the EEC-V ECU though .... and has been reported to work with others?

This is the package i have:
http://www.scantool.net/products/elmscan_pwm.htm

Many thanks for your time