Its for older tactrix cables that have a 7-digit serial encodeded in the chip instead of the newer 28?- digit ones. So when new versions of ecuflash try to comminucate with the cable, it freezes in an endless-loop. Maxes out the proc (or core for multi-core procs) and just sits there saying ECUFlash (not responding) in the title. This program changes the program code to 'work' somehow. I dont know enough assembly to know what i did, but i know enough to get my self in trouble :)

How do you tell which cable you have? I have had mine for quite some time.

yea how do you tell the difference between cables

Can someone show me where i can find ecuflash 1.38? i cant seem to find it anywhere

I posted in my original thread (1.35 i believe). Its not really a 'hack' The older tactrix cables dont have the long 28 (i think 28) serial number in them. If i use mprog to read my cable's eeprom data, i get a 8 digit serial, which doesnt work with new versions of ecuflash. My program changes a byte of the ecuflash program to stop the reading loop after the code is read. So it makes the serial look like xxxxxxxx00000000000000000000. It's only required to make the ecuflash program continue when reading/writing ecu data. If your ecuflash freezes and the title bar says (not responding) and your cpu is 100% (or 50% for dual core) then you should use this.

What happened to the 1.38 cable fix? I download it and the file is corrupted. I tried both links and it has the same outcome. Also, will you be creating a cable hack for ecuflash 1.40? Thanks for the help!{thumbup}

You can email orders at tactrix and they will help you upgrade the firmware in your cable so that you don't need the hack.

Thanks I'll give it a try{thumbup}

really. I dont have the problem but wouldn't mind new firmware.

latest n greatest n all that :P

Any idea what the turn around is on emails to tactrix? I emailed a few days ago and still nothing. Maybe I'm just being impatient but I really don't want to have to buy a whole new cable just to use the latest and greatest ecuflash.

allow 5 days for replies on emails to tactrix.

http://rs65.rapidshare.com/files/160...sh_138_win.rar

Here's a link from another member's post to the 1.38 version of ECUFlash.

I can confirm that this hack and this version can read from my RVR X3 ECU using the EVOScan cable. Prior to this hack, I had the 100% of one core issue.

Thanks a bunch :)

Do any of the latest versions of ECUFlash work without that hack?

I have the short serial Tatrix cable and am looking to upgrade ECUFlash. Help.

didn't colby offer firmware upgrades for cables?

I emailed a few times last year and never got a response. He has never answered the multiple post on openecu.org about it either. I'm still using v1.29.