Académique Documents
Professionnel Documents
Culture Documents
Home
Where to find the DataLink Connector 0
Products The 12pin male connector is only for reflashing/reprogramming the ecu, and is optional if you want to do datalogging.
The 16pin female OBDII connector is for datalogging and reflashing the ecu.
Cable Selector
Tutorials
Software Updates
Share
ECU Flashing
Android
iPhone iPad
Virtual Road Dyno
ECU Mods
Tech Info
Vehicle Manuals
GPSNav Updates
EvoScan Forums
Help & Support
Your Details
Lost Serial
Shopping Cart
OBDII Mitsubishi pinout:
16 pin OBDII diagnostics connector
Show Cart
• Flashing Diagnostic AYC/ACD/EFI/ABS lights, yes it is normal - this is Mitsubishi Factory Diagnostics mode.
Disconnect pin1 to stop the flashing lights permanantly. (pre 1998 ecus need flashing lights to even start EFI datalogging)
Latest Tweets • Yes disconnecting pin9 on the EvoScan Cable with pliers is ecommended for Mitsubishi AYC/ACD usage (pin9 is only used for subaru
reflashing) (the reason for removing pin9 is because Mitsubishi ETACS and AYC/ACD ecus will not datalog until pin9 is removed from the
16pin end of the USB cable.)
• Diagnostic Flashing lights stop flashing when KPH/MPH > 0
• There is also option in the EvoScan Logging menu to "disable flashing lights" when datalogging.
US Dollar
US Dollar 2001+ Mitsubishi 12pin Secondary Diagnostics Connector
21 22 23 24 25
26 27 28 29 30 31 32
PIN 1 EFI
PIN 2 Electronic Power Steering
PIN 3 Active Electronic Control Suspension Output (ECS)
PIN 4 ABS
PIN 5 Auto Cruise Control
PIN 6 AT Transmission (ELC-4 A/T Control Unit)
PIN 7 Full Auto A/C (AirCon control unit)
PIN 8 SRS AirBag
PIN 9 ETACS unit
PIN 10 Data (switching input)
PIN 11 Simulated Speed Input (Speed sensor)
PIN 12 Ground (negative)
Logging with Evoscan for 1995-1997 DSM / 3000GT
1. The 1995/96 ECU's use a different address to log knock than the 1997+ ECU's, so you need to make sure that you set the address for
"Knocksum" to 3E when logging a 1995 EPROM ECU. Otherwise you will just see a value that changes from 0 to 1.
Very simply, just Right-Click on the Knocksum line, click "Edit", then under "RequestID" change it to 3E, if not already. The correct address
for 1997+ ECU's is 26.
2. Jeff at Keydiver doesn't like the formula EvoScan is using for the 4 fueltrim values. Its the same old formula everyone used for 1G
fueltrims, which yielded the strange 81-140 values, which don't really tell you anything. Instead, change the old formula 0.78125*x to the
new formula: (x/4)-32 for all 4 fueltrims, even though 2G's don't use the HIGH TRIM. This will make the values read true percentages of
fuel being added or removed by the fueltrims.
3. For DSM, one of the items maybe incorrectly labeled the MDP Sensor as "EGR Temperature", way down the list. The 2G's don't use an
EGRT temperature probe to check the EGR operation, they use the MDP Sensor, which reads in psia. So, Right-Click on the EGR
Temperature line, change the formula to x*0.07353-0.0725, change the label to MDP Sensor, the LOGReference to MDPpsia, and the
units to psia. This should make the value read correctly up to ~18.7 psia, which is about 4 psi.
5. If you are logging a 1995 or 1996 ECU, set the BAUD RATE to 10400. If you try anything faster, the ECU will randomly disconnect and
attempt to reconnect
.
6. The 1995/96 protocol rides on top of the OBDII stuff, so it is VERY slow, only 7-9 samples per second. So, when logging you should
only select 1-2 items at a time.
The protocol is simple: request-reply. Request and reply are one-byte message.
To edit press Ctrl-E in EvoScan Add new items as needed. If the LogReference already exists you will need to edit the existing ones,
duplicated logreference items are not permitted.
EvoScan DataItems
DisplayName LogReference RequestID Eval Unit
Accel Enrichment AccelEnrich 1D 100*x/255 %
Coolant Temp CoolantTemp 07 -1.45*x+308 deg F
Engine Speed RPM 21 31.25*x rpm
Fuel Trim High FuelTrim_High 0E (x/4)-32 %
Fuel Trim Low FuelTrim_Low 0C (x/4)-32 %
Fuel Trim Middle FuelTrim_Mid 0D (x/4)-32 %
Injector Pulse Width InjPulseWidth 29 0.256*x ms
Oxygen Feedback Trim O2FeedbackTrim 0F 0.78*x %
Oxygen Sensor O2Sensor 13 0.0195*x V
Throttle Position TPS 17 100*x/255 %
Air Flow Hz AirFlow 1A 6.29*x Hz
Air Temperature AirTemp 3A -1.69*x+358 deg F
Air Volume AirVol 2C x Hz
Barometer Baro 15 0.00486*x bar
ISC Steps ISCSteps 16 x Steps
Knock Sum KnockSum 26 x Count
Timing Advance TimingAdv 06 x-10 deg
Battery Battery 14 0.0733*x V
EGR Temperature EGRTemp 12 -2.7*x+597.7 deg F
TDC TDC 02 x bit 4 on/off
Power Steering PwrSteeringSw 02 x bit 8 on/off
AC Switch ACSwitch 02 x bit 16 on/off
Park/Neutral ParkSwitch 02 x bit 32 on/off
Idle Switch IdleSwitch 02 x bit 128 on/off
AC Clutch ACClutchSw 00 x bit 32 on/off
To run a custom request in Evoscan, press the start logger. during logging you can type a 2 letter custom request code inthe the custom
request box at the bottom of the EvoScan main screen. Leave repeat unticked, unless you want to continually run the custom request.
F1 to F6 only work with engine stopped. After ECU any of theese commands it invokes corresponding relay/solenoid for about 6 seconds.
After that it answers in the Response box with 0x00. If engine is running ECU returns 0xFF immediately as completed.
F7 to FC disable injector for about 6 seconds and returns a response of 0x00.
Diagnostic fault codes are stored as bitmaps in two 8-bit cells. There're two kinds: active and stored (accumulated).
You can use the windows calculator in programmer mode (Alt-3) to convert between hex (0x??) numbers (don't need to type the 0x part,
just the ?? part) and you can use the calculator to then switch to the 8-bit binary (bin) numbers for trouble code bit analysis.
Also you can use the EvoScan DTC option "MUTII EFI" from the dropdown, and select DisplayDTC and it will do the conversion for you
automatically and look up the diagnostic codes. If your vehicle doesn't support
Custom Request: CA will clear the DTS / Diagnostic Trouble Code CEL (check engine light) fault memory.
Custom
Description
Request
38 (4C) Faults, low byte
39 (4D) Faults, high byte
3B (4A) Stored faults, low byte
3C (4B) Stored faults, high byte
CA Clear faults, returns 0x00
Bit # Code Fault
1 11 Oxygen sensor
2 12 Intake air flow sensor
3 13 Intake air temperature sensor
4 14 Throttle position sensor
5 15 ISC motor position sensor
6 21 Engine coolant temperature sensor
7 22 Engine speed sensor
8 23 TDC sensor
9 24 Vehicle speed sensor
10 25 Barometric pressure sensor
11 31 Knock sensor
12 41 Injector circuit
13 42 Fuel pump relay
14 43 EGR
15 44 Ignition coil
16 36 Ignition circuit
Mitsubishi Trouble Code Info
1. Ground Data Link Connector terminal # 1. pin4 and pin5 are ground. (so you can connect pin 1 and pin 4 with a paperclip or short
wire)
2. Set the ignition switch to "ON", the Malfunction Indicator (check engine) Lamp will illuminate for a particular duration and a certain
number of times.
3. Clear the trouble codes by disconnecting the vehicle battery negative terminal for 16 seconds or longer.
EXAMPLES
No Codes--normal
The Lamp will illuminate for 0.5 seconds, then stay Off for 0.5 seconds, this pattern will repeat until the ignition is
turned OFF.
Code 13
The Lamp will illuminate one time for approximately 0.5 second. This will represent one unit of ten. There will be
approximately a one second delay and then the Lamp will illuminate three times for approximately 0.2 seconds with
0.2 second delay between deflections. This will represent three units of one.
Code 23
The Lamp will illuminate two times for approximately 0.5 second with approximately 0.3 second delay between
deflections. This will represent two units of ten. There will be approximately a one second delay and then the Lamp
will illuminate three times for approximately 0.2 seconds with 0.2 second delay between deflections. This will
represent three units of one..
Clearing Trouble Codes
Diagnostic trouble codes may be cleared by disconnecting the battery ground cable for at least 20 seconds. Reconnect
negative battery cable and recheck codes to confirm the repair.
Diagnostic Codes
Mitsubishi
Without OBD-II
41 Injector(s) fault
43 EGR fault.
ECI
Voltmeter or Test Light
1 Oxygen Sensor.
2 Ignition Signal.
4 Pressure Sensor.
MPFI
86-88 4 Cyl.
Voltmeter or Test Light
MPFI
V6 and 89-95 4 Cyl.
(Exc. 95 Eclipse)
Voltmeter or Test Light
11 Oxygen Sensor.
23 TDC/CMP Sensor.
26 BARO Sensor.
31 Knock Sensor.
39 Oxygen Sensor.
41 Injector.
42 Fuel Pump.
43 EGR.
2. Count the number of times the malfunction indicator lamp (check engine lamp) on the instrument panel flashes on and off. The
number of flashes represents the trouble code. There is a slight pause between the flashes representing the first and second digits
of the code. Longer pauses (approx. 4 seconds) separate individual trouble codes.
3. Repair the malfunction while referring to the inspection chart for diagnostic trouble codes.
4. After disconnecting the battery cable from the battery (-) terminal for 10 seconds or more, reconnect the cable.
5. Start the engine and run it at idle for about 15 minutes after the engine has warmed up.
MPFI
95-98 Eclipse (Non-Turbo)
Check Engine/Light Scan Tool
95 Eclipse (Turbo)
96-98 Vehicles
OBD2