EvoScan J2534 Read Error - 16
#1
Newbie
Thread Starter
Join Date: Mar 2013
Location: Sweden
Posts: 3
Likes: 0
Received 0 Likes
on
0 Posts
EvoScan J2534 Read Error - 16
Hi guys!
I recently updated to EvoScan v2.9.0023
Since then I have started getting read errors when trying to display DTCs.
I then reinstalled EvoScan 2.8 and have been receiving the same type problems.
The vehicle is a Mitsubishi Evo8
It previously had rom ID: 92660006
Now has Tephra v7 96530706
Engine light has come on after the Tephra mod. and that's the reason I need to check DTCs on it.
The similar errors have been shown on two other Evos as well the last couple of days. One other Evo8 and a Evo9. I haven't been able to check DTCs at all consistantly, since the update.
Before recently, I haven't had any problems reading DTCs with EvoScan since I started using it 3-4 years ago. Have I missed configurating something?
I recently updated to EvoScan v2.9.0023
Since then I have started getting read errors when trying to display DTCs.
I then reinstalled EvoScan 2.8 and have been receiving the same type problems.
The vehicle is a Mitsubishi Evo8
It previously had rom ID: 92660006
Now has Tephra v7 96530706
Engine light has come on after the Tephra mod. and that's the reason I need to check DTCs on it.
Code:
Log from EvoScan: Info: OpenPort 2.0 Found. Info: OpenPort Firmware v1.12.368 Info: Battery 13.267V Info: Initialize Vehicle ECU... Info: OBDII Connecting... Info: Waiting for vehicle ecu... Info: Initializing At 5 baud... Info: Initialization Complete... Info: Waiting for vehicle ecu... Info: Connecting... Info: OpenPort 2.0 Found. Info: OpenPort Firmware v1.12.368 Info: Battery 13.245V Info: Initialize Vehicle ECU... Info: OBDII Connecting... Info: Waiting for vehicle ecu... Info: Initializing At 5 baud... Info: Initialization Complete... Info: J2534 Read Error - 16 Info: Check DTCs Complete. Diagnostic trouble codes: J2534 Read Error - 16
Before recently, I haven't had any problems reading DTCs with EvoScan since I started using it 3-4 years ago. Have I missed configurating something?
#2
Newbie
Thread Starter
Join Date: Mar 2013
Location: Sweden
Posts: 3
Likes: 0
Received 0 Likes
on
0 Posts
Forgot one very important addition to my post above:
I have no problems at all with the scanning/logging features.
It's only the "Display DTC's" that is causing an issue.
I have no problems at all with the scanning/logging features.
It's only the "Display DTC's" that is causing an issue.
#6
Trending Topics
#8
Evolving Member
iTrader: (4)
Join Date: Jan 2011
Location: Knoxville, TN
Posts: 150
Likes: 0
Received 0 Likes
on
0 Posts
I found this: http://www.tactrix.com/index.php?opt...d=38&Itemid=61
#12
Newbie
iTrader: (3)
Same issue for me on dtc scan for my evo 8. No problems with logging or anything at all. Im new to evoscan, just downloaded yesterday. I tried to clear cel and it said error but after a min or so cel went off so its working just throwing that error. Maybe a dumb question but does anyone elses abs light flash while logging?
#13
i had exactly the same problems after the new tactrix(force) firmware update.
sometimes it reads dtc but most of the time no. and also i am not able to log injectors duty cycle anymore.
sometimes it reads dtc but most of the time no. and also i am not able to log injectors duty cycle anymore.