EvoScan J2534 Read Error - 16
Nov 24, 2013, 01:51 PM
#31
Newbie
Join Date: Jul 2011
Location: Phoenix,AZ
Posts: 7
Likes: 0
Received 0 Likes
on
0 Posts
Update
For Evo x not sure about 8/9
In your evoscan "Change to EVOX EFI under Select DTC Method/ECU" It worked perfect for me. I didn't not figure this out a member on Evo x forum did.
For Evo x not sure about 8/9
In your evoscan "Change to EVOX EFI under Select DTC Method/ECU" It worked perfect for me. I didn't not figure this out a member on Evo x forum did.
Nov 25, 2013, 06:36 PM
#32
Evolved Member
iTrader: (10)
Join Date: Mar 2013
Location: Chicago
Posts: 890
Likes: 0
Received 0 Likes
on
0 Posts
With evoscan the Evo X should be run as CAN not the "J" driver anyways so its a totally different issue. Thanks though but this issue is only for VIII & IX actually.
Nov 30, 2013, 10:17 AM
#34
Evolved Member
iTrader: (10)
Join Date: Mar 2013
Location: Chicago
Posts: 890
Likes: 0
Received 0 Likes
on
0 Posts
The openport 2.0 has the pin 9 I believe that the 1.3 cables do not have (for evos). Can anyone confirm that removing this pin could possibly fix this issue? It makes sense to me but before I go breaking a pin out of my new openport 2.0 I would like to confirm this. Thanks.
Nov 30, 2013, 02:58 PM
#35
Evolving Member
Join Date: Sep 2012
Location: Ottawa, Ontario, Canada
Posts: 181
Likes: 0
Received 0 Likes
on
0 Posts
There are many more pins in the 2.0 as well, but they're disabled in the software when it connects to ecuflash and you pick the mitsubishi vehicle you're working with. It was an issue with the older 1.2 and 1.3 cables I believe, because it was constantly live. It's no longer an issue.
The reason this problem hasn't been fixed is because they have no desire to do so. That's the answer in a nutshell.
The reason this problem hasn't been fixed is because they have no desire to do so. That's the answer in a nutshell.
Dec 17, 2013, 02:50 PM
#39
Newbie
Join Date: Jan 2009
Location: CA
Posts: 65
Likes: 0
Received 0 Likes
on
0 Posts
i have had the same problem for years now. you can reset your light by unhooking the battery for a min or so but it will just come back if there are issues. has anyone went to a mitsu dealer to read their codes or even used an obd2 reader? would love to get the software the dealers have
Dec 18, 2013, 08:45 AM
#40
Evolved Member
iTrader: (10)
Join Date: Mar 2013
Location: Chicago
Posts: 890
Likes: 0
Received 0 Likes
on
0 Posts
I have a 1.3r cable and also one of those parts stores orange obdII readers for clearing codes. Although it would still be nice to be able to use the 2.0 for everything. I agree with broke4speed at this point. If they were going to fix this it would be fixed by now.
Apr 22, 2014, 05:15 PM
#42
Evolved Member
iTrader: (10)
Join Date: Mar 2013
Location: Chicago
Posts: 890
Likes: 0
Received 0 Likes
on
0 Posts
Bump for update, I have done a lot of research on this matter and broke4speed is 100% correct. Hamish was sent the OP firmware update but never wrote it into evoscan. If I had to guess its because he would rather sell more 1.3 cables. I guess I can't blame him but it still sucks.
May 19, 2014, 03:42 PM
#43
Yep it is because of the latest OpenPort 2.0 firmware upgrade. Basically it means zero messages returned. but can also mean zero messages returned in the 2nd group of DTCs. and may not display the first group of DTCs. I have an update for EvoScan.. I will release it this weekend.
May 19, 2014, 09:59 PM
#44
Evolved Member
iTrader: (10)
Join Date: Mar 2013
Location: Chicago
Posts: 890
Likes: 0
Received 0 Likes
on
0 Posts
That's good news considering you were sent the firmware update over a year ago. Thanks. People don't even really care about the DTC stuff to be honest. Make it work with the actuators and then I'll be impressed. FWIW I use my 1.3 for live tuning still even tho I prefer the 2.0 as a whole. Man I have a huge secret about the 2.0 but promised to keep my trap shut lol.
Last edited by jrainwater; May 20, 2014 at 06:54 AM.