I have been playing around with the EVO6 ECU with the Plan of making a Stand Alone Display unit that plugs into the OBD-II port and reads out diags and displays on LCD.

But first I wanted to experiment with the serial routines using a laptop before moving onto doing it with a Pic Chip and LCD.

After going off on a Steep Learning curve, I have mixed information from people and forums on whether the OBD-II ISO 9141-2 actually works with the EVO6 ECU.
I built a JEFF interface to start with and no luck doing the Slow INIT on the ECU, using programs such as ScanTech, ,so moved onto the MUT Protocol.

Next I moved onto USB cables such as OpenECU.
I have used the FTDI 232 chip for many years in other circuit designs I have designed and built, so I have a few chips lying around and one of my circuits has break out blocks, so I was able to tap into those lines and get EvoScan 2.5 to recognise it. It does the Slow INIT and then goes green saying connected, to only then drop out and try again.

If I fire up Hyperterminal and connect to the Virtual Comm port I get a ECHO back when hitting any characters, even at high Baud rates, so happy the circuit is working and I can see the K-Line pulsing with a meter.

With programs using the serial port I am able to use Portmon to see if the ECU is sending back the correct reply, but I think EVOScan is probably talking direct to the FT232 rather than the virtual Com Port.

I have also tried Mitsubishilogger but it fails on the Slow Init.
So where I am at the moment is actually trying too see if the ECU has booted up correctly.

Here is a picture of my Bench ECU, excuse the Breadboard at the moment LOL



I have the follwoing pins connected from the ECU

Pin 12 12V SW Supply
Pin 13 Ground
Pin 25 12V SW Supply
Pin 26 Ground
Pin 36 CEL Light.
Pin 56 Pin 1 on OBD-II connector.
Pin 62 to K Line of OBD-II Interface
Pin 80 Backup Supply
Pin 82 Ignition SW Supply
Pin 91 Ground

When I power it up I get the CEL light lit up.
If I take Pin 56 to Gnd I get the CEL light flashing in diagnostics mode for reading the fault codes.

So seems to be booted but still no communication with either OBD-II ISO protocol or MUT.



Have not got a Flash Cable here to see if I can Read the ECU as it is more the Diagnostics I want.

Anyone Benched a EVO6 ECU before?

Cheers

Sean.

P.S Have released a prototype PCB that uses the FTDI 232 chip and a MC33290 if anyone is interested in making their own FTDI cable on the cheap?
It does not pulse the 16V on the Flash line and is only for Diagnostics.

 

Quick note to say now all sorted, popped a 74hc04 inverter chip between my FTDI RX and TX lines.
Finished Interface will not have this problem as using the MC33290 ISO 9141 chip.

MitsubishiLogger and EvoScan working now

So MUT Protocol working, but looks like OBD-II is not supported on EVO6 ECU