R18eclipse pulled my rom last night from my brand new 2010 Evo MR (55580005) and when he attempted to use evoscan to do some data logging, after the "link engaged" it popped a check engine code for P1871 code ?! (APS system abnormality) Anyone else had this issue? Once disconnected from Evoscan the code had to be cleared with an OBDII scanner... We didn't try to use evo scan anymore and the code didn't return.

 

Sounds like connecting to log triggered the code by causing abnormal communication with the TCU... see a better description here:

hxxp://www.***************/forums/showpost.php?p=298837&postcount=10

Probably interrupted communications when it initialized or something. I wouldn't worry about it.

Some people are also suggesting you may have hit the torque limiter and or have a dirty MAF, but that seems unlikely.

 

I guess the interruption is possible. Car was a parked when I linked up. So couldn't be a limiter, it's on the stock rom. Dirty MAF is highly unlikely car only has 700miles on it.

 

Every single SST equipped Mitsu will pop codes when you read or write a rom from/to the ECU.

Just clear it after you read/write.

It is odd that evoscan caused a code. Did you try to read codes from Evoscan or just log?

- Bryan

 

Just went to data log... When I hit the link button ("Link Engagued") it popped a code. I had a 08 GSR and it didn't ever pop codes when I was data logging I guess you're right about the SST rom's. Sensitive I guess =\

 

Something is up with that. The SST cars never pop a code for me when I log them with evoscan.

Which version of evoscan are you running?

- Bryan

 

have you worked with a 2010 rom?

 

Yes, have tuned a bunch and I also own a 2010 that I log every other day.

- Bryan

 

Strange... Maybe engaged the link too soon to start up. I know there are a lot of processes that go on right when the MR is fired up. What version of evoscan are you using?

 

2.6

- Bryan

 

Ok so was with the tuner tonight... The car is poping "service engine soon" light and code P1871 is coming up and beig cleared... I have however figured it it was not evoscan it has been ecuflash... It did it origionally when ecuflash was used to pull my rom.. Tonight evoscan connected fine and only when reflashing the ecu did the service light come up. No brick so I am happy with that at least but still wondering why and curious if it has happened to others

 

Because reading/writing ECU breaks the connection from the ECU to the gearbox .. and the CANBus detects that as a fault in the system ..

In fact you should get
U0100
P1870
P1871

 

See post #4, it's normal for the SST equipped mitsus.

- Bryan

 

K thanks guys... Pm'n you gst

 

GST... I was going over a link posted to a server from norcalmotorsports.org. The file for the evo10base.xml is a broken link =\ Can i get this from someone?