ECUFlash 1.38 cable fix.
#16
Evolving Member
Thread Starter
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
#20
Evolving Member
Thread Starter
It isn't evident in this discussion as to just what this hack is and under what circumstances it would be necessary.
Someone please explain briefly.
Someone please explain briefly.
#21
Evolving Member
Join Date: Jun 2007
Location: NorCal
Posts: 154
Likes: 0
Received 0 Likes
on
0 Posts
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!
#25
Evolving Member
Join Date: Jun 2007
Location: NorCal
Posts: 154
Likes: 0
Received 0 Likes
on
0 Posts
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.
#27
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
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