I found the 2 green connectors under the dash allready connected-Car was/is working fine with them connected.I disconnected them and then reconnected again,but it wont go into diagnostic mode-ie fans cycling ect.

Any reason for this???

Or is there some kind of problem???

The car is a 2001 bugeye.

 

Sorted it-phew!!!-discovered that there was 2 more green connectors that were unplugged behind the passenger side sill trim below the dash!!!
Diag mode works a treat now

 

u flashed it yet then !!

 

I wish-been pulling my hair out-cant seem to connect to the ecu(keep getting a kernel error)-waiting for a reply on openecu.

 

Scott-have you got any ideas??-Or anyone else???

http://forums.openecu.org/viewtopic.php?t=1040

 

Have you loaded the drivers for the Cable, which can be found on the Tari site.
I get the following on my desktop i.e no cable or no ECU connected

[00:10:08.171] Version 1.28.716
[00:10:08.171] 8 memory models read.
[00:10:08.921] 74 ROM metadata models read.
[00:10:08.921] checksum module "subarudbw" loaded.
[00:10:08.937] flashing tool "wrx02" loaded.
[00:10:08.937] flashing tool "wrx04" loaded.
[00:10:08.937] flashing tool "sti04" loaded.
[00:10:08.937] flashing tool "sti05" loaded.
[00:10:08.937] flashing tool "mitsukernel" loaded.
[00:10:08.937] flashing tool "mitsukernelocp" loaded.
[00:10:08.937] flashing tool "mitsubootloader" loaded.
[00:10:08.937] error loading FTD2XX.DLL

 

Ive got the drivers-and the cable is recognised when it is plugged into any of the usb ports-TBH im not sure what the com port stuff is about-ive set it to port3 on ECUflash as advised but havnt got a clue what its about.Ive tried it in all 3 usb's and I do appear to have a bit of a dodgy connection on one of the usb ports on my laptop though.I wonder if this has anything to do with it???

 

It even comes up with the same error without the cable plugged into the laptop????????