Yep, on my limitless cable, had to use the driver that came with ECUFLASH. The EVOSCAN driver worked with evoscan but didn't work when used with ecuflash. The ecuflash driver worked for both ecuflash and evoscan.

 

True...let's make it easier - which one should be installed first? EvoScan or EcuFlash? Then, when we hook up the cable the very first time, which driver set should we choose between the EvoScan and EcuFlash???

it'd be more helpful for those who have had the same problem and got it fixed to chip in more tips...

 

Boy boy boy...I finally got my both laptops working with the EvoScan cable. And out of my surprise, I did un-install and re-install with the EvoScan 2.5 drivers on my laptop #2, and both EvoScan and EcuFlash are working! But with my laptop #1, i didn't do a single thing, except that I did drive my car for half day right before doing it. So, I think the real trick...as the other post stated already...is due to the voltage in the battery.

In my conclusion, check and make sure your battery is good and above 12.5v before knocking on Hamish's mail box ;-)

Have fun, guys!!

 

I just want to bump this thread because I feel like Hamish was getting bashed earlier pretty bad.

Its definitely an issue with battery voltage - here in VT (0 degrees C/32F today) its just not a reasonable expectation of my 12lb race battery to have enough voltage to write to the ECU first time every time.

If I warm it up for 30 minutes, no problem at all!

^^^ I'm sure people from Minnesota know what freezing cold weather is like, and these are the people that are having the worst problems.

I'd buy a round for Hamish - try getting a quality, new 1.3U cable at $100 anywhere else - not gonna happen. Literally. If you want to spend 3 times that amount on something that does the same thing, go ahead (evo x guys excluded). But, Hamish is doing a good job.

 

I'd also like to buy a round for Mr. Hamish. He did get back to me when I sent him emails for questions, and they also provide a pretty decent "Support Ticketing" system too. And keep in mind that he is on the other side of the globe from "most" of us, so don't expect to get an instand reply, ok. At last and not least, he is more than willing to do a complete full refund (at least on a couple postings I've read...) So, he is a provider, and I would buy others from him again.
for Hamish!

 

Does anyone have a contact email for the limitless cable? When I click on the email link at the top of their page, nothing happens. Is the person in charge there a member of EVOM?

 

evoscan@limitless.co.nz

 

I logged a support ticket with limitless around 3 weeks ago (iirc).. no reply as yet.

E7 ECU (MR560648) in E4.

Confirmed Pin79 has continuity to the auxilary jack on the OpenPort 2.0 device.

Tried with car running, car off, car on charger... Ecu unlocker on, ecu unlocker off.

Tried with car on jumper pack on (just under 15volts), laptop on mains power, dual powered USB cable (from portable hdd).. removed drivers and software manually and reinstalled fully countless times.

Can datalog with Evoscan ok with same setup.

[18:58:45.632] EcuFlash Version 1.42.2595
[18:58:45.632] OS Version Windows XP
[18:58:45.632] Qt Version 4.5.0
[18:58:45.652] 56 memory models read.
[18:58:45.652] scanning for metadata models in C:/Program Files/OpenECU/EcuFlash/rommetadata
[18:59:14.984] 344 ROM metadata models scanned.
[18:59:14.984] checksum module "subarudbw" loaded.
[18:59:14.984] checksum module "mitsucan" loaded.
[18:59:14.984] flashing tool "wrx02" loaded.
[18:59:14.984] flashing tool "wrx04" loaded.
[18:59:14.984] flashing tool "sti04" loaded.
[18:59:14.984] flashing tool "sti05" loaded.
[18:59:14.984] flashing tool "mitsukernel" loaded.
[18:59:14.984] flashing tool "mitsukernelocp" loaded.
[18:59:14.984] flashing tool "mitsubootloader" loaded.
[18:59:14.984] flashing tool "shbootmode" loaded.
[18:59:16.076] flashing tool "shaudmode" loaded.
[18:59:16.076] flashing tool "subarucan" loaded.
[18:59:16.076] flashing tool "mitsucan" loaded.
[19:00:04.435] J2534 API Version: 04.04
[19:00:04.435] J2534 DLL Version: 0.50.2598 (DEBUG) Jun 26 2009 15:02:29
[19:00:04.435] Device Firmware Version: 1.07.2597
[19:00:19.236] sending init sequence 1 (0001)
[19:00:22.531] sending init sequence 1 (0003)
[19:00:25.826] sending init sequence 1 (FFFF)
[19:00:29.101] sending init sequence 1 (F0F0)
[19:00:31.825] no response to any known code
[19:00:31.825] interface close

Apparently the ecu has never been flashed or tampered with in any way so should respond to init codes. I am wondering if my tactrix cable is faulty... what voltage should i see on the auxilary wire to pin 79 .. Im wondering if the ecu isnt getting anything telling it to init.

 

Hamish always has helped me , try to contact him ,

 

I dont know who Hamish is? ... Im getting the impression my tactrix cable is faulty.

Ive measured continuity from the mini din that goes into the OpenPort 2.0 dongle all the way to the circuit board inside the ecu and its there.. but i dont seem to get any voltage reading along that wire when its sending the INIT codes... anyone know what you should be seeing on this signal wire?

 

SUCCESS.

Found a post on some DSM forum regarding the voltages... it should pulse ~ 14 volts on the INIT wire to pin 79 on ecu. Mine was managing a measely 0.05 volts... jammed multimeter up inside the tactrix dongle... ow hello 14 VOLTS... So yeah the auxilary port jack is faulty. Shaped up some wire and pushed it in the slot all the way to the end.. fired it up ... VOILA!.... god damn it.

I had a feeling it was faulty when i was about 10 hours into it... but as i had no idea what to look for in the way of voltages it made it hard to diagnose.

 

yep, I am Hamish

thats interesting that you found a fault, what sort of aux plug is it, is it a black fully molded 12pin plug and 3.5mm jack, or is it a white 12pin with wire to 3.5mm jack?

 

the port inside then OpenPort 2.0 where the 3.5mm jack goes in is faulty.

 

I run EcuFlash 1.34 and EvoScan 2.4 with the EvoScan 1.3 cable and anytime I have ever had a connection problem it has been due to low battery voltage.

+1 for the newbs!

Thanks for all your hard work Hamish!

 

is the cable that hamish - evoscan sells (OpenPort 2.0 for 169$) 100% compatible w/ the one Tactrix Sells for (189$)? firmware and everything?

The tactrix openport 2.0 cable looks different in regards to the optional reflash adapter (has a 3.5mm plug)



While the limitless openport 2.0 cable has a built-in reflash adapter? The picture shows a white plug which I believe is the reflash adapter, does it come with it as part of the package?