openecu.org

Not sure if I'm in the right forum, so apologies if I've got it wrong.

Just tried loding Ecuflash onto this mini laptop (I cussrently use EF successfully on a Dell) and cnnot seem to takk to the ECU. I plug in the cable, fire up EF and then try a read & gt th following screen. The read fails.

[18:31:12.015] Version 1.34.1435
[18:31:12.031] 11 memory models read.
[18:31:12.046] scanning for metadata models in E:/WRX/Ecuflash/rommetadata
[18:31:14.015] 219 ROM metadata models scanned.
[18:31:14.015] checksum module "subarudbw" loaded.
[18:31:14.015] flashing tool "wrx02" loaded.
[18:31:14.015] flashing tool "wrx04" loaded.
[18:31:14.015] flashing tool "sti04" loaded.
[18:31:14.015] flashing tool "sti05" loaded.
[18:31:14.015] flashing tool "mitsukernel" loaded.
[18:31:14.015] flashing tool "mitsukernelocp" loaded.
[18:31:14.015] flashing tool "shbootmode" loaded.
[18:31:41.390] Using interface OpenPort 1.3 Subaru TX45akk480cdf6d5980f25c83afb92e16adde3e12744126c
[18:31:47.062] denso02_bootloader_cmd_start
[18:31:48.296] denso02_bootloader_cmd_start
[18:31:49.515] denso02_bootloader_cmd_start
[18:31:50.750] denso02_bootloader_cmd_start
[18:31:51.984] denso02_bootloader_cmd_start
[18:31:52.421] kernel get version
[18:31:52.796] interface close
[18:31:52.812] interface close

Any clues what's going on? FWIW, Romraider does not see the ECU either.

As I was running EF v1.30 successfully on my Dell, I uninstalled v1.34 that was on the Eee, deleted all the folders related to EF, and installed v1.3. Installation appears to progress properly, including the Open Port drivers.

Problem is, that when I insert the Tactrix cable, instead of the computer just running the 2 drivers (as it did on my Dell), I get a dialogue box from Windows asking where the drivers are located, or insert the CD with drivers.

If I look at the device manager I see that the port is in error.

As a complete guess, I had a look in the EF directory and found a drivers folder. In that, I saw 2 folders (x64 and x86). I reinstalled the driver x86 to the port that showed the error, and the error went away! Did I do right?

Anyway, the end result is that although EF sees the cable, it does not talk to the ECU after I turn the key on and press "Read" for example. It stops at the good old "Get Kernel" line. Romraider works and I can log data. Interesting that the 774 version of Enginuity does not talk either, even when rebooting computer, re connecting cable or resettin the com port (of which there is only one on this Eee (COM3).

After reloading v1.34 twice, and v1.3 once, Trying to fix drivers, still no go. Can anybody suggest what I can do to try and fix this com issue with EF?

Thanks for reading.......

Tried this from evasiv3 and didn't work either....

1. Uninstall ALL occurnaces of EcuFlash, FTDI drivers, OpenPort Drivers, Unplug Cable, etc...
2. Install a copy of EcuFlash 1.28 but DO NOT install the OpenPort Drivers when prompted.
3. Reboot computer.
4. Unzip attached file to a folder on your desktop
5. Place Tactrix cable in the computer
6. When prompted to install driver, select from "Other Location"
7. Install driver from unzipped folder on your desktop
8. Configure COM Port to your liking.
9. Done!

Looked like a good shot though.....

Same deal. Enginuity can see the cable and can log.
Ecuflash sees the cable but fails on connection to the ecu with about 5 lines on the log ending with Kernel Get Error......you know the one..
V774 of Enginuity (the one with wb logging) does not even see the cable!

I'm gonna figure this out if it KILLS me!

I'm trying yet another re-install now.

If you're running the Linux software on the Asus EEE, then you might want to read the thread at:
http://forums.openecu.org/viewtopic.php?t=2422

Thanks Jon. I converted the Eee to Xp. Romraider works. Logger works. Hell, even Learning View works. It's just EcuFlash that doesn't work. Ecuflash sees the cable, but I can't connect to the ECU for some reason.

I just keep getting that Kernel error!

Maybe the connection speed thru the Eee is a problem? Also, I have the EF software running off the flash card inserted into the Eee. Maybe that's a problem?

Anyone ever made an Eee connect up with the ECU using EF?

cheers mate