are you by chance running vista? i had problems with mine cause of vista, if not make sure when you uninstall evoscan you go into your program files and make sure the folder is deleted or otherwise empty...malibujack would know better then me

 

make sure you have a correct wideband checked or no check if there's no wideband.

 

Ok, this all sounds good. I am using Windows XP and, have never had this problem until now. I'll try to delete every file I can find thats attached to it and start again. Thanks Chabada. MalibuJack? What do you think?

 

Ok. Still no good. I'm stuck. Has anyone got anything??

 

anyone know how to get the updates. I lost my email that had all the info.

 

start a help ticket at evoscans website

 

Im having the same "cannot connect to ecu problem". I also get a box that says "root element missing" anyone have any idea what that means ?

I have also deleted then re downloaded ecu flash, evo scan, and made sure .net was updated.

Not sure where else to start. Anyone have any other ideas ? Ohh I run xp and I had no problems when i first downloaded it either or any other loggers. It all of a sudden happened.

Thanks

 

^ "root element is missing" mean your ecuflash definition (in XML format if you're technical) file is invalid. Basically, someone or somehow your file content was messed up.

 

ok well i read up on you can change you 94170008 to a 94170015 but i tryed this and it didn't work. that car would kick over like the code was wrong on the immoblizer. but i chacked it and it was right... can i get aby help and after i installed the 94170008 NLTS patch i have a wear ticking nose from my valve cover i took her off and everything seems ok.. kinda seem like a valve is sticking... i have 280 cams tho. has anyone had these problems???? plz help me i serched

 

280 cams make ur PCV make that noise...it happens with long duration cams

 

it just started this tho, if been running the cams for about 6-7 months

 

I'm practicly in the same spot, but I run vista. ecuflash works, obd scan tech reads my codes. On evoscan, when hitting Display DTC, i get
Info: Initialize Vehicle ECU...
Info: OBDII ISO Init...
Info: Waiting for vehicle ecu...
Info: Initializing At 5 baud...
Info: Initialization Complete...
Info: OBDII Sync Byte not found...00
Info: Connection successful...
Error: No Response from Vehicle ECU
Info: Check DTCs Complete.

Also, under Logging, Select Usb has openport 1.3 checked, but under com, Com1 is checked when it should be Com4, and I cannot change it. I have uninstalled (and deleted folders) and reinstalled evoscan 2.5 and no fix.

 

ur rom probly has a bit lower idle cause u switched it n may have fergot to switch your idle map, either way it isnt bad its common

 

Seriously we need help. OK last night I was working on my friends EVO, we tried to run evoscan on his car and it worked....WTH? Then, moved it back into my car and it doesn't work. I have no idea where to start looking. Is there a particular wire off of the ECU I should be looking for? Did I splice into something I shouldn't have when installing the AVC-R? The boost controller works fine. This sucks! Does any one have a clue? MalibuJack? TTP? Jestr?

 

mhm. i have evoscan 2.3 on an XP laptop that does work with my car, but 2.5 on this Vista computer does not. If anyone needs me to attemp anything in particular, let me know.