RupertisRed

I've a Tactrix running with EvoScan. I had the clutch replaced by a transmission place (never again) and got my car back with a CEL. I don't trust the place enough to take it back for them to fix this.

Found the two codes, one from MUTIII (P23E0) settings the other from OBD-II (P23B0) settings...I'm pretty sure those are the correct source/code combos.

I've been researching and have been able to find NOTHING on this DTC/CEL. The closest I've come to anything was for some BMW software custom error code that didn't really make sense.

Anyone have any info on this? I took it to the stealership and they weren't able to help. I'm pretty sure they artificially generated a P0123 error but I was able to clear that one up. Thanks !

KRome

iTrader: (2)

What version of EvoScan?


v2.9 will give you whack codes. Use v2.8 to view and clear DTC's.

RupertisRed

Indeed. 2.9. I'll be giving 2.8 a go then see if I get something different.

mityaz

i bet it's a p0300

RupertisRed

Howdy folks!
Sorry for the disappearing act. got sick, work kept interrupting, wife kept interrupting, kids kept interrupting...anyways.
Tried Evoscan v2.8 with no luck. kept getting errors when pulling the dtcs. logging works fine though.
Installed 2.8 on a new tablet and am still getting an error when pulling dtcs(different error): "J2534 Read Error - 16"
Anyone know what this is? Logging works fine on this one as well.

RupertisRed

A bit more info. Important bit in bold:
Info: OpenPort 2.0 Found.
Info: OpenPort Firmware v1.16.476
Info: Battery 11.785V
Info: Initialize Vehicle ECU...
Info: OBDII Connecting...
Info: Initializing At 5 baud...
Info: Initialization Complete...
Info: OBDII Sync Byte not found...F0
Info: Connection successful...
Info: J2534 Read Error - 16
Info: Check DTCs Complete.


I'm reading through another post on here:
https://www.evolutionm.net/forums/ec...or-16-a-5.html


Trying an older version of ECU Flash.

RupertisRed

PFM. I went with with ECUFlash 1.44.3252 and it worked...I was going for 1.43.something but was clicking around too fast. meh. it worked!
I also configured EvoScan in XP compatibility mode (running Winders 10) so not sure which if it's a combination of the two or just running the older ECUFlash version.


P0123...Throttle Position Sensor indeed is the CEL. yay for progress!

4G63_EVO

iTrader: (4)

Maybe they unplugged it for some kind of clearance and forgot to plug it back in when cranking the car and it threw the code?

RupertisRed

I did this (by mistake) while checking with Evoscan 2.9. I had both the bogus DTC and P0123. I was able to clear DTCs though but the Bogus one kept coming back.


I...cheateded...when I went to the stealership and took a snapshot of the TechInfo printout they were using to diagnose. It failed at the 2 Ohms reading. It was either 4 or 14...don't quite remember. Either bad sensor or bad ECM.


Step 6:
https://mitsubi****echinfo.com/data/...2200USA.htm#S6
...you'll need to add shi t (no space) in place of the *'s


I was trying to test this myself but kept not getting a good reading. Not sure if my meter is crappy or I couldn't find a good grounding point. yay. hell, I may have just forgotten to check it while in the On Position!...crap, I'm pretty sure I totally did this.

RupertisRed

So...it turns out that the issue was a miss-aligned pin in the ECM. I noticed an "extra hole" in the connector and looking on the ECM side, finally noticed the "off" pin. I realigned it properly and was able to clear out the DTC.


So glad that the issue is resolved.


That and my car's a whole lot more responsive on the throttle that it still catches me by surprise a week later!