After the most recent round of mods, I've had a weird CEL. Unfortunately, I've added A LOT of parts (turbo kit, cams, intake, intercooler, injectors, fuel pump, yada yada). I tried to use ScanTech and it had problems connecting, so I just went to Autozone and bought the least expensive code puller (Actron / Pocket Code Scan Tool - bout 70 bucks) just to read the codes. It also will not connect to the Ecu. The odd thing is that I can still reflash and datalog through the port.

I tried the code scanner on another evo and it worked great. I also went to Autozone and used their slightly fancier version and it also did not connect. Any thoughts?

 

Do you mean that your cel is on all the time and you can't read the cel code? Do you have Evoscan it can read diagnostic codes.

 

That's exactly it... I have a CEL and no scanner will connect. I have heard that the Evoscan diagnostic reader is not correct.

After searching some more, I'm wondering if it could be due to increasing the baud rate to 62500. I'm going to try and change it back to factory and see if that works.

 

My Evoscan will read and clear codes but I also have a Can 100 reader. Evoscan baud rate of 15625 on my Evoscan. I have the 1.0 alpha version.

 

evoscan 1 will read and clear codes?
I did not know that.

 

since you have the tactrix register on Malibu Jacks website and download the generic scan tool. Its free and works, reads codes and clears codes

 

I did... it doesn't work (says it cannot connect). I'm really thinking it has to do with setting up the flash to run 62500 baud rate - I may have done it incorrectly so it's throwing the code and not transferring information well. I was just seeing if anyone else had the problem.

 

im going with baudrate.

afaik the baudrate doesn't actually let you log any faster (even though it should!!!)

 

did you set the right come port? and did you set it to the jeff protical? I am not trying to be a dick just trying to help

 

No worries man... yeah, I did both. The thing is that the obd2 readers do not work either - so I don't think it's a problem with the software/hardware of the scanners, but rather an issue with the signal coming from the obd2 port. I have a ton of school work to do tonight but I'll be figuring it out tomorrow.

 

OBD II readers are dummy proof if the key is on and the cable is connected to the port it will read unless the ECU is damaged or the OBD port cable is damaged. The ECU can be damaged really easy, a static arc from your hand to the OBD port can kill the ECU. I work in auto shop and I've seen it happen. If you have a turbo timer or any other kind of patch harnesses on the car you might want to check them out. The first rule of modding your car is to do a mod one at a time so you can work the bugs out more easily.

 

Yeah, it had to do with the baud rate modification on the rom - put it back to the stock settings and it works now.

I know you're supposed to do 1 mod at a time, but it's a bit tough when you are installing a full turbo kit and the supporting hardware. A few bugs are bound to come up but I've got them just about taken care of.

 

Good deal, there's nothing like spending money on mods and the car runs like crap.