taylorgang

iTrader: (5)

I could try putting a bone stock rom on the car. I tried reading my rom from my car yesterday and it wouldn't read it from ECUflash. It read it just fine from EVOscan but then when I tried to load the rom into ecuflash it didn't work again. So maybe that's a sign that it's locked?

BEKevo

iTrader: (2)

I would put the air box on for sure, I doubt the perrin intake is CARB approved. How big of cams are we talking about? Larger cams produce higher levels of NOx, bigger cams are harder to pass. Also would of advice, get the catalytic converter HOT as you can before the test. Hotter the cat, the more efficient it works.

Please save yourself a headache and stay away from a ref.. They actually know their ****, and they know EVos like to be modded

codgi

iTrader: (22)

Odd that it reads from EvoScan and not EcuFlash but I've never used EvoScan to pull the rom so maybe it uses a different technique then EcuFlash. That does indeed sound like its locked. Did you try ECUUnlocker?

taylorgang

iTrader: (5)

I'm able to flash the car though. I've changed maps a few times (turning on NLTS, then turning it off). I wouldn't be able to do that if the ecu was locked, right?

I haven't tried using ecuunlocker yet but I may try it

SmurfZilla

iTrader: (33)

My car did similar inconsistent things when my battery was low. Swapped to a new one....all my weird evoscan/ecuflash issues went away

BEKevo

iTrader: (2)

This problem seems to be associated with 9's moreso than 8's. Not saying youre wrong or anything. It's just the OP has an 8. Hopefully the OP checked the battery first though

BEKevo

iTrader: (2)

Very weird symptoms you're having, as codgi mentioned. Usually people read/ write ROM via Ecuflash..

If you can access "NLTS", you've accessed the ROM aka your ECU shouldn't be locked. Especially if you've changed the maps a couple times. I wouldn't mess with an Ecuunlocker, unless you didn't have to. Who previously tooned your car? TSComp? You should talk to him, if so.

golruss

iTrader: (3)

Any idea what setting could cause this. I am having a similar problem. Changed ECU loaded up my settings and still the same thing. Battery is good voltage on pin 16, pin 7 to ECU pin 62 is good. Can read and write to the ECU but will not connect to my scan tool or the state computer. At a loss.

What voltage should be on pin 62 on the ECU? Is pin 62 the voltage source?

Thanks.

10isace

iTrader: (12)

Anyone figure this out? I'm having the same issue at the emissions center with a USDM IX. Readiness monitors all pass and no cels, but the state inspector's scanner won't connect. Apparently the voltage is reading really low from the OBD to the scanner at around 2 volts instead of 12V+ which apparently means it's not communicating. I helped the inspector get it to start reading, but the calibration ID wasn't something they have in their database. The only adjustment to the stock ROM is the immobilizer is disabled as the immobilizer is unknown. I'm wondering if this is the issue. Anyone of the previous posters and OP have the immobilizer disabled? I also have the clutch safety switch disconnected, but don't believe that would cause an issue or is related.

Also, I've tried two different ECU's and two different ROM's 88590015 and 88950016.

golruss

iTrader: (3)

My problem was the baud rate in the bin file got changed for some reason during a dyno tuning session. Make sure that "BaudRate 1_OBD" is set to 15625. My immobilizer is not disabled. ROM 96534706. In my case I could read and edit the ROM but state computer could not connect to it. Hope this helps.

10isace

iTrader: (12)

Interesting! My Baud rate is set to 41666. I've never messed with this table in 11 years of tuning. I'll give it a shot. Thanks!

golruss

iTrader: (3)

Check it with your code scanner before going for inspection.

10isace

iTrader: (12)

My cheap scanner works flawlessly with correct Readiness Monitors passing and no CEL's. The Snap On scanners at the state inspector's wouldn't communicate. They have like 3 or 4 of them. Their emissions computer communicates though, but that PC looks ancient. Mitsubishi's scanner wouldn't connect just like the state inspectors. So my theory is the cheaper scanners are using the same parameters as EvoScan. EvoScan reads no problem and all Readiness Monitors are passing on stock ROM 88590015 and 88590016, but just won't communicate for the ref's needs. He said that's highly unusual. So I'm really crossing my fingers for the OBD Baud rate to fix it. Not sure how to read that on the scanner, unless I spring for a Snap On scanner (which I'm looking into).

Thanks for your help!!!

EV09AWD

if you've tried multiple ECU'S with multiple ROMS, we could maybe eliminate those. How about wiring? trace back any modified wires, and check grounds all over?... i know nothing but just a thought... if the battery was relocated could there be insufficient voltage going to ECU? How are the pins looking for the OBD port? etc etc.

10isace

iTrader: (12)

Thanks for the suggestions. I checked the continuity of the wires to the ECU and they check out and pins look good. Also a good full size battery in stock location. I get 12V resting from the battery. OBD pin 16 gets 12V also with engine off. I'm talking to the state ref via email. I think I may try this ECU I swapped in and see if Mitsubishi can flash the latest TSB flash with the immobilizer.