HOWTO: Log from your ECU for less than £30

[Confused]

Knowing what is happening with your engine is critical to troubleshooting issues, ensuring healthy running, and chasing power.

Our cars have a diagnostic port, which is located under the dashboard on the driver's side, above where your left knee would be.

Whilst this port looks like a standard OBD2 (On-board Diagnostics 2) found in many other modern cars, the VR-4 was introduced before a global standard for both pin-out and communications protocol was agreed upon - so most available software and hardware which is marked 'OBD2' is not compatible with the VR-4 (namely popular mobile apps such as Torque, and the widely available bluetooth ELM327 adapters).


If you want to just read fault codes, then you can stop here - all you need is a simple piece of wire or even a paperclip - and take a look at the diagnostic codes (https://www.clubvr4.com/forum/showthread.php?45151-Reading-the-VR-4-s-Diagnostic-Codes)


So - what can we do if you need more information? Well, although the protocol isn't the standardised one, it's close enough that a cheap (approximately ?10) cable designed for VAG group cars, with a minor modification, will allow communication!

What you will be looking for is a ~?10 VAG-COM KKL USB cable - they are widely available on online auction sites such as eBay, and this style is nice and cheap:

76812

Beware: It will need to have an FTDI chip on board, not a CHG340

Out of the box, this still won't work. We need to connect Pin 1 to ground - this just so happens to set the engine ECU into a mode where it can communicate.

There are multiple ways of doing this - I will show below my preferred method, which makes no modifications to the car, and requires no ongoing maintenance.


Firstly, open the connector up by undoing the 4 screws, and remove the cover:

76813

Next, remove the circuit board from the casing, and unplug:

76814

Now you have access to all of the pins - take a short length of wire, and solder it between pins 1 and 4. I used an uninsulated piece of wire because it's what I had to hand, but you could use insulated, as you do not want to touch any other pins:

7681576816


Once that is done, the modification is complete, and you can put it back together.


Next, you want to head on over to http://www.evoscan.com/ and purchase EvoScan software (http://www.evoscan.com/evoscan-gps-obdii-cables/details/4/1/performance-vehicle-pc-diagnostic-interfaces/mitsubishi/subaru/obdii/can-evoscan-software) - this will set you back just $25!

The latest version (as of March 2017) is 2.9, but you will need to download version 2.7 if using this cable.

Once downloaded and installed, and your cable plugged in, run EvoScan, and from the Logging menu, select your ELM cable from the menu option, and from the 'Device cable selection' option in the top left, put a tick in the box next to Mitsubishi MUTIII.

Once you've done this, you should be able to click on 'Start Datalogger' and see some data showing in the list against the items you have checked.

The more data types you check, the fewer samples per second you'll get, so it's a balance between logging enough options and getting a good amount of data.


[I'll add some screenshots of EvoScan later!]

[jjmiller182]

Awesome write up cheers :)

[Davezj]

great thread garry i am surprised we have not done something like this before.

it seems obvious when you now how but noobies will no be able to do this without having it explained in twenty different ways by twenty people.

here is a link to a useful thread for ecuflash and evoscan.

https://www.clubvr4.com/forum/showthread.php?67698-Basic-Introduction-to-ECUflash-rom-tuning-and-Evoscan-logging&highlight=basic+ecuflash

[low_vr4]

Is this the right one?

http://www.trademe.co.nz/1271149107

USB VAG 409.1 OBD2 KKL

[Confused]

Is this the right one?

http://www.trademe.co.nz/1271149107

USB VAG 409.1 OBD2 KKL
That looks about right to me :)

[BCX]

https://www.ozvr4.com/threads/diy-datalogging-cable.9829/

more info here.

[Hemigunnar]

How can I get the older Evoscan (2.7)? When I try to buy, I get the latest (2.9)...

[Davezj]

If you a license for 2.9 you should be able to use that on 2.7
Is there an archive section on the website, I seem to remember there is.
But if you can't find it then maybe someone with the 2.7 install files can send it to you. If you have paid for version 2.9 I can't see any reason why you can't have a copy of 2.7 off someone.

Sent from my MI 5s using Tapatalk

[Confused]

Yes the licence for 2.9 allows you to install down as far as 2.7 - once you have purchased it, you can get the 2.7 version from the EvoScan website at http://www.evoscan.com/evoscan-updates#content

[Hemigunnar]

Okej, thanks! :)

[Confused]

Although I have still yet to add any images of EvoScan, I have added a link to retrieving the fault codes.

[Amonlym]

A warning to others:
I got myself a cable appearing visually identical, but discovered after trying to connect it that the one you need *must* have an FTDI usb-serial chip on it. the one i got had a different pcb inside to what Confused shows, and will not work (unless anyone has any advice) the easiest clue i can see is that Confused's has a clear LED, mine was solid red.

the hunt continues :)

[Tony_T]

Has anyone seen a circuit diagram for interfacing the car directly to a serial port? I can't see why everyone wants to use USB and then have to include a USB to serial converter with all its driver and chipset issues. A good old RS232 port will work regardless of those issues if the interfacing to the car is correct. When I had my E39A Galant all it needed was a D9 connector with one diode and one resistor in it although I didn't use Evoscan, I used another program which was widely available on the net but whose name has slipped my memory, however it worked well.
That cable you got, Amonlym, may just need different drivers. I work in two-way radio and we find the same issues with various radio programming cables.

[Amonlym]

Tony_T I agree with everything you say, but Evoscan appears to only support ftdi converter cables. there is a com option in the menu - which cannot be selected, it tells you to get an openport cable as it is faster.
I cant use the FTDI drivers on the cable I got as it has not go the TFDI chip, I tried force installing the FTDI drivers for the device - no good. Can probably reverse engineer it from one of these cables (once confirmed working) and then its just developing an understanding of the protocol.

[Tony_T]

Can you identify the chip your cable actually has? If so you could search for driver software for it and try that; I can't see that there should be anything specific to that chip that Evoscan itself would be needing. I believe there is a problem with Windows 10 not accepting some USB drivers or simply not working with them, however I don't use (or like) Windows 10 as it tries to hide too much and not allow custom settings.

[Amonlym]

A second attempt, specifically searching for FTDI along with vagcom provided this:
FTDI FT232RL VAG COM KKL 409.1 OBD2 KWP2000 ISO9141 USB FOR VW/AUDI
seller jrprimetechllc
https://i.ebayimg.com/images/g/dewAAOSwCkZZWKPe/s-l1600.jpg
https://i.ebayimg.com/images/g/Y9YAAOSwkX1Zcdrk/s-l1600.jpg

This one, modded as above works fine with Evoscan, using the drivers included with Evoscan.

[Hemigunnar]

I have the same problem, have purchased a FTDI usb-device and modded it, but still can't choose ELM-device...! Help...!!

[Amonlym]

is the chip inside definitely an FTDI one? are you able to give a photograph?

[mgtd98]

Will this help clear srs fault codes?

[Confused]

Will this help clear srs fault codes?

Unfortunately not. Please have a look at this thread: Clearing SRS (Airbag) Fault Codes (https://www.clubvr4.com/forum/showthread.php?77975-Clearing-SRS-(Airbag)-Fault-Codes) for a list of devices we have confirmed work to clear SRS codes.

[Judder]

A warning to others:
I got myself a cable appearing visually identical, but discovered after trying to connect it that the one you need *must* have an FTDI usb-serial chip on it. the one i got had a different pcb inside to what Confused shows, and will not work (unless anyone has any advice) the easiest clue i can see is that Confused's has a clear LED, mine was solid red.

the hunt continues :)

Mine came with a RED LED and is using a WCH CH340T USB to Serial chip [data-sheet (https://cdn.sparkfun.com/datasheets/Dev/Arduino/Other/CH340DS1.PDF)] which I'm pretty sure if I install the drivers for [link (https://sparks.gogo.co.nz/ch340.html)], will work pretty much exactly the same as the FTDI chip based ones

Here's a photo for reference

81099

81100

Also, following on from Dave's initial post (*excellent post by the way Dave) is there an alternative PIN on the adapter that can be used to ground Pin #1, rather than Pin #4, as on my adapter Pin #4 is tucked underneath the daughter board and looks rather fidly to get to?

Also - just because I'm interested - what mode does grounding pin #1 on the ECU adapter do to the ECU? I've been reading that the VAG protocol is also used by Fiat / Seat in an expanded way so adapters work there too but have even more functionality on different pins for MES [link (http://forum.multiecuscan.net/viewtopic.php?t=255&start=120)]

[Amonlym]

Hi Alex,

99.9% wont work. I think that is the exact chip mine had.
Best as I can tell Evoscan is looking for the FTDI chip! not for a serial interface but the actual FTDI chip - probably for specific configuration of the interface to the car.
Pin 1-4 is nothing to-do with vagcom, it sets the interface on our cars (MUTII) into debug mode. The FTDI vagcom cables just happen to be (physically) the same, or close enough, as the cable that evoscan wants once 1-4 are shorted.

[Judder]

Hi Alex,

99.9% wont work. I think that is the exact chip mine had.
Best as I can tell Evoscan is looking for the FTDI chip! not for a serial interface but the actual FTDI chip - probably for specific configuration of the interface to the car.

Finally had a chance to look at this this weekend and yes you are absolutely correct - unless it has the FTDI chip then there is no way Evoscan will talk to it as it seems to use that driver directly, rather than talking to a general USB -> Serial conversion device

Out of interest a couple of observations from this weekend that it would be great to get feedback form anyone else who has this working:

1. The lead that seems to work has a clear LED rather than the RED led and only lights up when it is connected to the cars not-quite-OBDII port - the red LED ones seem to light up when they get a USB connection

2. When I did connect the lead to the not-quite-ODBII port, then the dashboard lights did a random flashing between the Turbo light, and a few others - is that correct or is my lead doing something strange?

3. Evoscan when you select the first menu (Logging -> Select USB Device) doesn't actually bring up any menu as I was expecting - I guess it just picks the FTDI device if it finds one

4. It says it is logging at 5kbps which sounds pretty slow but is that normal??

Any screen grabs of your setup much appreciated and I can share the same :)

[Confused]

Yes, at slow road speeds, your dash will flash like a Christmas tree! It stops when you get to about 10mph(ish). I'm also pretty sure it is slower at logging than the OpenPort cable.

It's been a while since I last hooked up a working cable, so can't assist with the other points I'm afraid! However, it does sound like you've managed to get it successfully working!

[Judder]

Yes, at slow road speeds, your dash will flash like a Christmas tree! It stops when you get to about 10mph(ish). I'm also pretty sure it is slower at logging than the OpenPort cable.

It's been a while since I last hooked up a working cable, so can't assist with the other points I'm afraid! However, it does sound like you've managed to get it successfully working!

Great - that's good to know and especially the feedback about all the dash lights working - the thread doesn't mention that anywhere and it makes you a bit nervous if you're not expecting it!!

Thanks again

[glyn]

has anyone manage to sort this with the cable that has a red led ? mine has a red led and doesn't work either, I cant seem to find one online that has a clear led, so im struggling, help please

[Judder]

has anyone manage to sort this with the cable that has a red led ? mine has a red led and doesn't work either, I cant seem to find one online that has a clear led, so im struggling, help please

The key here is the chipset of the USB driver being by FTDI as this driver is hardcoded into Evoscan so it can't talk to leads with other chipset unluckily

The way to find the right one is to search for FTDI in the OBD-II diagnostic cable search on eBay or similar and they turn up

Here's a quick example of one that _looks_ correct for sale today

OBD2 FTDI Diagnostics Lead (https://www.ebay.co.uk/itm/SUBARU-FORESTER-USB-OBD2-II-FTDI-KKL-Diagnostic-Lead-Works-with-FreeSSM-V1-2-5/202787892902)

[glyn]

brill, ive ordered one, fingers crossed this will have the right chip ! thanks for your help

[Kryndon]

I found a VAG-KKL USB cable which physically has an EFTDI chip on it, but I also noticed it has pins 4 and 5 soldered together. Would it become an issue when I solder a wire from pin 1 to 4, essentially bridging pins 1 4 and 5 together? Also does anybody have the install files for EvoScan 2.7?

[Confused]

Pin 5 is also ground, so it should be fine.

Once you've purchased EvoScan, you can go to the Downloads (http://www.evoscan.com/evoscan-updates) page (once you've logged in with your username and password), and you will find a link to 2.7.0090 FINAL

[Judder]

brill, ive ordered one, fingers crossed this will have the right chip ! thanks for your help

Just back with my car again after lockdown and now have time to rig up my ODB-II lead again so wondered how everyone got on with their search for a compatible lead?

From checking on eBay, it looks like all FTDI serial <-> USB powered leads that should be compatible with EvoScan use a FT232BM chip as per this datasheet (http://www.ftdichip.com/Support/Documents/DataSheets/ICs/DS_FT232BM.pdf)

If you search on eBay for that chipset with ODBII or for "subaru-forester-usb-obd2-ii-ftdi-kkl-diagnostic-lead-works-with-freessm" as the same chipset lead appears to be needed for FreeSSM for Subarus then a number of leads turn up for about £15 such as this one (https://www.ebay.co.uk/itm/202969918666)

[Judder]

Pin 5 is also ground, so it should be fine.

Once you've purchased EvoScan, you can go to the Downloads (http://www.evoscan.com/evoscan-updates) page (once you've logged in with your username and password), and you will find a link to 2.7.0090 FINAL

Hey Confused I think I've read the answer to this somewhere but can we use EvoScan v2.9.0100 with these leads?

It says it includes drivers for "for FTDICOM / Openport 1.3D" so it _sounds_ like it might work

[Confused]

I don't think so.

2.9 doesn't add anything extra useful for us, but I'm pretty sure it doesn't work with the modified VAG-COM cables.

To be safe, stick with 2.7!

[Judder]

To be safe, stick with 2.7!

Will do and thanks for clarifying :thumbsup:

[CHESHIRECAT]

Hi guys, could you let me know if you think I have the correct cable. The circuit board looks different to the one posted on here8340983410
Thanks.

[Judder]

Hi guys, could you let me know if you think I have the correct cable. The circuit board looks different to the one posted on here8340983410
Thanks.

That should work fine - the key is in the Serial -> USB chip used and this needing to be a FTDI 232 based chip as that is the drivers that EvoScan has built in compatibility with

Looking at a zoom of your first picture you can see your chip is an FTDI FT232RL so should be fine

83411

[CHESHIRECAT]

Thanks, I couldn't even see that in front of me lol. What tit I am.

[howardalex]

Will this wire work? I've bought a soldering iron and solder and all tonight, going to look very closely at the instructions when I come to solder it!

https://www.ebay.co.uk/itm/165391568054?hash=item26821b0cb6:g:aLcAAOSwQXpiNad F

[Judder]

Will this wire work? I've bought a soldering iron and solder and all tonight, going to look very closely at the instructions when I come to solder it!

https://www.ebay.co.uk/itm/165391568054?hash=item26821b0cb6:g:aLcAAOSwQXpiNad F

I cross referenced that lead based on the manufacturer code C44D47A6AF72 and from this resultant page (https://nazya.com/freeshipping/single/94823761/orig_desc.html) it looks like it has a FT232BL chip so _should_ work fine

[howardalex]

Fantastic, thank you! I'll get one ordered!

[Confused]

I've just ordered one, will give it a try with EvoScan (see if it detects it) then modify it accordingly - might even then sell pre-modified ones via https://www.adaptiveengineering.co.uk in case anyone can't solder :)

[howardalex]

Good shout that! If I hadn't already bought the soldering iron and plug, I'd buy one.....I may still do after I mess mine up lol

[Confused]

Well, I'll get some modified and up for sale - if not for you, for the next person!

[Confused]

Unfortunately the one I got delivered from that last eBay listing has a CH340 chip, which isn't an FTDI chip, so won't work with EvoScan.

I've ordered another, from another seller, which states it's got a FTDI chipset, so hopefully that'll arrive in a few days.

[CHESHIRECAT]

Hi guys I've sorted the cable out and the car is going into flashy mode when plugged in, but evoscan doesn't seem to but connectting to the ECU. Any ideas?

83422

[CHESHIRECAT]

83423

[CHESHIRECAT]

I did a reboot and it is working now.

[Judder]

I did a reboot and it is working now.

/GJ /bounce

[Confused]

Awesome! Nice work!

The second cable I ordered, which specifically said FTDI in the title, was also a CH340G chipset! :( My hunt continues!

[Judder]

Looks like these guys might be on it for the Forester
https://www.djwwautodiagnostics.co.uk/SUBARU_FORESTER_USB_OBD2_II_FTDI_KKL_lead_Works_Wi th_FreeSSM_V125/p5996490_21584490.aspx

[PunkyB]

Iv'e been deliberating to grab myself an openport 1.3 (Flash capable not just logging) but $157 for a cable of limited use is off-putting. The thing is unlike a lot of other Galant's mine does actually work with Torque and OBD apps. The only thing that I can see being the reason is that mine is GDI. Given I own an openport 2.0 can I just get this bit and end up with the same thing? https://evoscan.com/product/mitsubishi-reflash-connector-1998-2006/

[Confused]

Yes, an OpenPort 2.0 is absolutely fine - it's what I have, along with the linked reflash adapter.

We often need to ignore some of the crap that's thrown around regarding EvoScan and OpenPort from the Evo lot... :D

Though, whether anyone has a definition file for the GDI ECU is another thing...