ive just bought a used snap on code reader from snap on,with all the pods and wires for most vehicles.can they be used for diagnosing faults on the cosworth models.i know the fault codes are in flashes but would one of these decipher the codes and tell the fault?i see there is a loom for the fords thats the same as the ones on the cossies.

would rather know first before trying it on a car-namely the escos with the fuelling fault!

if so any help on connections etc would be gratefully received.
thank you
jay

 

come on fellas,surely someone must know?

 

It will only read fault codes if they are present. If there is no fault codes present then it will display nothing.

 

as per daz. the connector is next to the ECU (not next to the battery)

 

Is there not always a fault code at rest?

Some makes of ECU's report a crank sensor fault at rest, due to no signal.

 

When i worked for ford we had the cosworth tester - it was basically a box with an LED - wasnt worth a toss and a good old multi meter was much more reliable

 

On Cossies, (except eec4 small turbo)

The code reader will ONLY work on original manufacturer chip software !!!

The ONLY exception are chips that have been over written with minor modifications
but these are few and far between and only 1 or 2 mappers do it this way.

 

Code readers will work with ALL my software.

 

As i said few and far between

 

so where on each cosworth do they plug in?

 

The fooking fuel injectors dont work properly on some peoples software, what chance has the error monitor and output code software?

ROFLOL

 

3 door and sapphire, next to ecu approx 4" down the loom

T34 Escos, under NS suspension turret brace.

T28 Escos, same place but with live datastreaming.

 

Absolutely in tears cause its fucking well true!

 

on the t34 escos,which plug do you use as there are 3 next to each other?is it the more triangular one of them?

 

2 of the plugs are for the octane adjustor and the other one is the diagnostics.

 

but which one is which?i think i know but im not certain.also on the ford loom i have to go with the code reader it has 3 connectors and a brown wire with a crocodile clip on it-what does that plug on to?

im new to all this modern(!)technology

 

the octane adjustor plugs are single wire going by the electrical schematic

couldn't tell you what the connectors look like tho, never looked on an escos, only a taxi

 

im getting it now i think.......if the car has standard bits on it(not chipped)my code reader will work.also on some modifiers chips,but not all.
basically all i want is to know if i get a cossie in with a fault-ie misfire-if i use the code reader will it help me out?or do i have to use the led thing and count the flashes?
i didnt buy the reader for the cossies,mainly bmw's and vuxhalls,but it would be a great help if it did them too.

im a bit rusty now-spent too long selling cars instead of repairing them!

 

to see the diagnostic connector, see this topic:

https://passionford.com/forum/viewtopic.php?t=158561

wouldn't it be fantastic if you could plug that into a laptop or palm and be able to read the datastream from the ecu with all of the information about rpm, MAP, TPS, coolant temperature, ignition timing etc?

 

You can on almost every car in the world since 1990 EXCEPT on the marelli systems.

 

i know stu, OBD is a good thing. shame that even that has 3 different communication standards

the current can bus is excellent - if you can get hold of the database

if it was possible on marelli stu, would you be interested, and do you think that there'd be a market?

 

i bought a fault code reader from ebay and was made by Draper Tools - left it at my mates garage so he could test it on a few cars and it never displayed a single thing -

 

Yes, but only if the protocol would fit into my closed loop software.

 

don't understand Stu what do you mean by fit into your closed loop software?

i'm thinking of a datastream output something along the lines of what is read by a pectel monitor. how is that connected to closed loop fueling?

 

The datastream output is inside the eprom and integral to the run program, thats why marelli has flash codes and pectel has datastream. Its part of teh chip you have bought. A full datastream output may take up more program area than is available within the software i currently use.

 

i see

thanks for the explanation Stu

 

Your welcome.

 

bloody intresting