krazykorean84

I've been using ecuflash 1.29 for over a year and a couple months ago I wanted to update to 1.35 but my tactrix 1.3M cable would not read/write with ecuflash 1.35. It still works with evoscan and it would read/write with ecuflash 1.29 but it limits me from utilizing the newer ecuflash features.

Last month per the advice of an evoM member I contacted Tactrix and they assisted me with reserializing my cable. However, this did not help with my read/write problem for ecuflash 1.35 and up. For the past 3 weeks I've emailed tactrix about this problem and I haven't gotten a response. Maybe because of the holidays?

Anyway, does anybody have any ideas as to why my cable will not read/write with ecuflash 1.35 or 1.40 but still works with 1.29 (even though its reserialized)?

Thanks for any opinions.

fknlowpsi

i have the same issue man. the only thing i can think of doing is pulling the rom from the ecu with 1.29 then opening it in 1.35-1.40 editing and saving and reflashing with 1.29. u just have to install the 2 different versions of ecuflash in to a dif directory. there is also a 1.3 cord hack on ecuflash boards/ hope this helps.

krazykorean84

Yeah this is what I was doing for a while. I have the cord hack but I would prefer to use the cable the way it was intended to be used.

golruss

iTrader: (3)

I have the same problem: contacted TACTRIX and after re-serializing my cable,
this is what they said when it did not work.

"However, from what I understand, as stated below, if this process doen't work, then it is probably a dying/flakey cable that is past its prime, particularly since its 2 yrs old which can happen with frequent use"

I just ordered a new cable, when it gets here I will see if that was the problem.
Using ver1.40.

krazykorean84

Great.... that's just what I need. I was really trying to avoid buying a new $180 cable.

deathtracks

iTrader: (4)

I followed the instructions taxtrix sent.
Ran oputiluser /i from the start, run, command
File found here: http://www.openecu.org/wiki/downloads/oputiluser.zip

Sent results to Tactrix and they wrote me back with this to run:
oputiluser /c 13M /r TX39HmV1 with new serial number they sent me (omitted here)

Uninstalled old version of 1.29a I was using and then installed 1.4 with the new cable driver. Worked great for me.

krazykorean84

I accomplished the exact same steps you've listed in the exact order you've listed and it didn't work for me.

I'm still waiting on a reply from Tactrix though, maybe they can shed some light on my problem.

dan l

iTrader: (3)

Are you sure that you entered the code correctly so that it put the correct serial # in? I don't mean to talk down but I remember it being tricky, so double and triple check when you are reflashing the firmware in the cable. It was my problem, and many other peoples problem, and many of us got it working correctly. Other than that I'm sorry I can't help you as these are the steps I took to fix the problem. Sorry, it sucks and I know how you feel.

gsrboi80

iTrader: (38)

Am I missing something. I'm running 1.40 with the older cable. No issues

Hmmmmmm

travman

iTrader: (26)

Not everyone had this problem........I bought my cable when they were first released way back when and I never had a single issue with mine. It has worked on every single version of ecuflash, some though have had issues and require the cable fix.....

gsrboi80

iTrader: (38)

^^ Cool thanks man. Yea me too I've pretty much had my cable since the begining. It's always worked for everything. EVOSCAN, MITSULOGGER, ECUFlash, OBD-II ScanTech

krazykorean84

I've tried and retried reserializing using the instructions given to me by tactrix. Nothing I do makes any difference.

Do you think you could provide me the steps you took to make this work?

Or maybe I could PM the instructions and serial # they gave me and you could tell me if there is any mistakes?

This problem is getting on my nerves and I'm about to just give up and run ecuflash 1.29 to flash and 1.40 to make adjustments. Either way thanks for the suggestion.

mitsuatb

iTrader: (6)

I upgraded to ver 1.4x , don't quite remember the exact version, from 1.34.

I had problems, so I went into that add remove programs and uninstalled the old version, and saved the rom files to another file.

Then I reinstalled version 1.4x and everything worked fine.

Some times the drivers conflict with new versions.

Mitsuatb

krazykorean84

I've already tried using different ecuflash versions paired with the different driver versions. Nothing has worked.

Does anybody have the steps they used to reserialize their cables? I'm only asking those people that have had to reserialize their cables through tactrix due to reading/flashing with older 1.3 tactrix cables. Just post the directions you used to successfully reserialize your cables or PM me the directions if you wish.

I really just want to see if anyone elses directions were different from mine.

fostytou

iTrader: (15)

Can you post the log from ecuflash? If you haven't yet, try starting the car and driving it around for 10-15 min. Then, with the car still running, try to connect.