Kyle4200
Junior Member
- Messages
- 251
It does engine ECU and Transmission Faults, it isn't an SD2/3 scanner but it a very handy tool to have, later versions may add ABS etc but I only have the Trial Version, I'll update the guys when it gets released.
Obd code reader
- Thread starter highlander
- Start date
It does engine ECU and Transmission Faults, it isn't an SD2/3 scanner but it a very handy tool to have, later versions may add ABS etc but I only have the Trial Version, I'll update the guys when it gets released.
CatmanV2
Member
- Messages
- 48,836
highlander
Member
- Messages
- 5,223
Ok, could not go to work without trying above. Car started fine wi no spluttering. CEL still on but will test drive her tonight. At least if I get her running I can drive her to get the problem looked at rather than £300 to transport her. Thanks again Phil......any other handy resets Ive been ignorant of because she has been reliable to date?A 3200 owner who hasn't done a Throttle reset or does it as a matter of routine!?!?!?
Get in, turn ignition to MAR, don't touch pedals, wait 2 minutes , key off.
Turn to MAR, foot down all the way on accelerator wait 10 seconds, release pedals, key off.
Now start the car in the normal way
Kyle4200
Junior Member
- Messages
- 251
Here's just a few screenshots of the OBD scan tool that I'm trialling at the moment - appropriately called 'EasyMas', it's easy to use and clear, solved my issues which I will detail up soon, this included 2x new o2 sensors, cam cover replacement (leak) causing the timing sensor to flood and fail (cleaned & replaced), fault finding my failed cats and replacing a shot ignition coil that was causing misfires.
highlander
Member
- Messages
- 5,223
going round in circles and pulling my hair out with this!!!
all wired up correctly but keep getting "application failed to start because FTD2XX.dll was not found" message................wtf am i doing wrong!
all wired up correctly but keep getting "application failed to start because FTD2XX.dll was not found" message................wtf am i doing wrong!
Trev Latter
Member
- Messages
- 1,213
Nothing Greg. That DLL file isn't found with the KWP software for some reason. When I re installed it following a Window 10 upgrade, I had the same. It magically appeared after I reinstalled my Ducati Diag software, so I'm guessing it had the same file in there somewhere.
Sent from my iPhone using Tapatalk
Sent from my iPhone using Tapatalk
highlander
Member
- Messages
- 5,223
it is there, in the amd64 sub folder of the CDM 2.08.24 KWP folder for windows vista but being a trog with IT I have no idea what to do now...........
Trev Latter
Member
- Messages
- 1,213
I think we're in the same club mate.
Sent from my iPhone using Tapatalk
Sent from my iPhone using Tapatalk
CatmanV2
Member
- Messages
- 48,836
Greg does the error message tell you where it's looking? IS there any more detail?
This might help:
https://support.microsoft.com/en-us/kb/249873
What OS are you on?
C
highlander
Member
- Messages
- 5,223
No it doesn't and Oh god, now you are asking! Lol
The laptop is an old vista model, amg 64, in case it is not evident........I have almost zero IT skills
CatmanV2
Member
- Messages
- 48,836
No it doesn't and Oh god, now you are asking! Lol
The laptop is an old vista model, amg 64, in case it is not evident........I have almost zero IT skills
********. I could probably talk you through it, but I'm off to the US tomorrow morning.
C
highlander
Member
- Messages
- 5,223
i really am going round in circles with this now.
- i've tried the link on reading error codes thread and get several non encryption messages when extracting then when I then try to run application I get the dreaded "application failed to start because FTD2XX.dll was not found" message.
- I've tried going direct to FTDI page and downloading the vista AMD 64 link, which has the FTD2XX.dll in it, still get non encryption messages and can't then find an application to start when all the files are extracted.
- tried the disc that came with cable and no surprise, it does not recognise the car because it is not VW/Audi/seat.
as i've said before, i'm not really IT literate so have no idea where to go with this now. has anyone else tried to set this up recently from the links?
- i've tried the link on reading error codes thread and get several non encryption messages when extracting then when I then try to run application I get the dreaded "application failed to start because FTD2XX.dll was not found" message.
- I've tried going direct to FTDI page and downloading the vista AMD 64 link, which has the FTD2XX.dll in it, still get non encryption messages and can't then find an application to start when all the files are extracted.
- tried the disc that came with cable and no surprise, it does not recognise the car because it is not VW/Audi/seat.
as i've said before, i'm not really IT literate so have no idea where to go with this now. has anyone else tried to set this up recently from the links?
Stewart
Junior Member
- Messages
- 472
Don't know if this is of any help Greg, I bought reader of Amazon, 12.99. Plugged in Jeep waited as instructed, it came to life and gave me fault codes which I then erased, plugged into Gti , same result, wait , read faul code given delete , fix yourself or head to Garage.
Good luck.
Good luck.
highlander
Member
- Messages
- 5,223
thanks chief but marci is not obd so none of these scanners will work with her. hence the workaround with 3 pin extension and software.
if it is my old vista laptop that is the problem I can buy something else but not wanting to just be buying stuff on guesswork............if I was going that way, I'd just buy a couple of knock sensors but then if it is not them, I'd be £100 down for parts and probably another couple of hundred on labour and no further forward. No, I need to find someway to get this 3200 reader system working since getting her down to PK every time a CEL stays on is just not feasible or cost effective living up here.
if it is my old vista laptop that is the problem I can buy something else but not wanting to just be buying stuff on guesswork............if I was going that way, I'd just buy a couple of knock sensors but then if it is not them, I'd be £100 down for parts and probably another couple of hundred on labour and no further forward. No, I need to find someway to get this 3200 reader system working since getting her down to PK every time a CEL stays on is just not feasible or cost effective living up here.
hladun
Member
- Messages
- 149
This might be your problem. The pre-ODB systems had unique error codes so you need them to know what you're getting, but these systems could often be triggered to display the codes by flashing lights on the instrument panel. I had a 92 Alfa Spider and that's what you had to do. I cut this out of an Alfa post.
"You will need to pull the code from the ECU and reply back. Here is how you pull the code. It is flashed through the check engine light through a series of long and short flashes. Here is how to pull the code:
1. Turn the ignition key to the "on position" so that all the lights light up on the dash. Do not start the engine nor have it running.
2. Remove the access panel from your carpeted rear deck behind the passenger seat.
3. Locate the ECU button. There is a button on the outside of the steel box that the ECU sits in. The button faces the passenger side "b" pillar, the passenger side rear speaker, and seat belt retractor. Note that you will have to reach around to the outside of the steel box that the ECU sits in so have long flexible fingers or skinny ones that can fit between the carpeted deck and the top of the steel box.
4. Depress and hold the ECU button for 5 secs.
5. Release the button once the check engine light goes off.
6. The Check Engine light will flash the code.
7. Once the code is flashed (and it will repeat) you can simply turn the ignition key to the off position.
Here is how to read the code:
The check engine light flashes the code by long and short flashes.
1. The check engine light does a long flash followed by a long delay to say "here comes the code"
2. Then the individual numbers will be flashed by short flashes with a long delay between each seperate number.
3. The error code is a 4 digit code beginning in the number 1.
4. Code repeats over and over.
Here is an example:
F=Long flash
f=short flash
D=long delay
d=short delay
Error code 1234 1234
F........D.......f..D........f..d..f..D.......f..d ..f..d..f..D..........f..d..f..d..f..d..f..D...... .......F........D.......f..D........f..d..f..D.... ...f..d..f..d..f..D..........f..d..f..d..f..d..f.. D.............
So this would be read: Code 1234 Code 1234"
"You will need to pull the code from the ECU and reply back. Here is how you pull the code. It is flashed through the check engine light through a series of long and short flashes. Here is how to pull the code:
1. Turn the ignition key to the "on position" so that all the lights light up on the dash. Do not start the engine nor have it running.
2. Remove the access panel from your carpeted rear deck behind the passenger seat.
3. Locate the ECU button. There is a button on the outside of the steel box that the ECU sits in. The button faces the passenger side "b" pillar, the passenger side rear speaker, and seat belt retractor. Note that you will have to reach around to the outside of the steel box that the ECU sits in so have long flexible fingers or skinny ones that can fit between the carpeted deck and the top of the steel box.
4. Depress and hold the ECU button for 5 secs.
5. Release the button once the check engine light goes off.
6. The Check Engine light will flash the code.
7. Once the code is flashed (and it will repeat) you can simply turn the ignition key to the off position.
Here is how to read the code:
The check engine light flashes the code by long and short flashes.
1. The check engine light does a long flash followed by a long delay to say "here comes the code"
2. Then the individual numbers will be flashed by short flashes with a long delay between each seperate number.
3. The error code is a 4 digit code beginning in the number 1.
4. Code repeats over and over.
Here is an example:
F=Long flash
f=short flash
D=long delay
d=short delay
Error code 1234 1234
F........D.......f..D........f..d..f..D.......f..d ..f..d..f..D..........f..d..f..d..f..d..f..D...... .......F........D.......f..D........f..d..f..D.... ...f..d..f..d..f..D..........f..d..f..d..f..d..f.. D.............
So this would be read: Code 1234 Code 1234"
Stewart
Junior Member
- Messages
- 472
There was I believe a Mobil auto sparky from Inverness ?, going round the Garages here on a weekly basis, he was supposed to be first class, you can maybe find online.
I had one years ago for a fault on T5 Volvo, cured after inspection and hooking up.There has to be auto sparks in town.
I had one years ago for a fault on T5 Volvo, cured after inspection and hooking up.There has to be auto sparks in town.