PDA

View Full Version : evoscan not work and error codes



c0xxy
12-07-2011, 03:29 PM
heya peeps.

i'v recently bought eveoscan and an ebay cable to try do some logging (got a kanji ecu now) before i (fingers crossed) have another go at wiring the map2 in.
iv never managed to get evoscan to connect since getting it
i have 2.7 and 2.8 installed. windows 7 64bit. have downloaded ftdi? drivers.
i keep getting told no repsonse from ecu, same message with flashy dash on or off

thanks in advance

ash

46629466304663146628

foxdie
12-07-2011, 04:20 PM
What cable did you buy? Chances are you'll have to modify it.

Join me in chat, I'll walk you through it.

Nick Mann
12-07-2011, 09:54 PM
Did you get it sorted? Mine does that sometimes with a dodgy connection between the cable and the cars ODB2 port. It also does it if the com channel is configured incorrectly.

c0xxy
12-07-2011, 10:00 PM
nope. stupid thing

foxdie
12-07-2011, 10:07 PM
Was working with Ash for about an hour with this, he's trying to use a VAG-COM cable on his 64-bit Windows 7 laptop, he tried EvoScan v2.7 / 2.8 but those won't recognise serial-based cables, and v2.5 has permissions issues opening csv files.

Ash, did you try the instructions outlined in this thread (http://forums.evolutionm.net/6913689-post9.html)?

c0xxy
12-07-2011, 10:12 PM
was appreciated. yeah, followed instructions
now it asks for registered e-mail and serial number and then says they are incorrect

foxdie
12-07-2011, 10:22 PM
You have PM

c0xxy
12-07-2011, 10:27 PM
thanks buddy. will try that tomorrow
ash

c0xxy
13-07-2011, 02:14 PM
2.5 connects to log, so big thanks to jason/foxdie for the help!
will have to see how well it logs later in week.
still says no repsonse from ecu for error codes.
cheers for help
ash

foxdie
13-07-2011, 02:18 PM
I had difficulties reading the DTCs with my VAG-COM cable, I think the initialisation sequence is different and bridging pins 1 and 4 together (in your case with the switch) is perhaps tampering with this.

You may find that it's not possible at all to read DTCs with anything other than either a genuine MUT-II/III or a Tactrix / OpenPort cable.

c0xxy
29-07-2011, 12:24 AM
iv finally wired my wideband to out put to pin 5 plug 4 as nj told.
although iv said earlier it connects to log... it doesn't actually log anything! nearly every field is a 0. coolant and air temps are both 380 or something... bit tired now. lol
anybody any help?
cheers
ash

Nutter_John
29-07-2011, 12:34 AM
Pin 1 and 4 need to be shorted

not sure what you mean about pin 5

c0xxy
29-07-2011, 12:51 AM
i have a switch to short 1+4 on obd. it connects, tells me link engaged :-S but no values all seem to go to 0 and do nothing?
think you told me to put a pin in 5th position on 4th ecu plug to allow logging of wideband thru evoscan. at least that's the position i wrote on me piece of paper.
ash

Nutter_John
29-07-2011, 01:00 AM
Yeah sorry now makes sense to me :)

pin 5 on socket 4 is the secondary o/2 sensor - you need to select the tick box saying you want to capture the info

c0xxy
29-07-2011, 01:02 AM
have done that... its not capturing any info at all tho, on anything
ash

Nick Mann
29-07-2011, 01:22 PM
Have you got anything selected to log? Sorry, silly question!

c0xxy
29-07-2011, 01:24 PM
yup. it saves the log files too... hundreds of zeros, nothing changes

c0xxy
23-10-2011, 03:52 PM
have now tried with another laptop and same problem. connects but shows 0's