Hello.
My name is Stacescu Dragos, I own a little tuning company in Romania ( www.completechip.ro) , specialised in both diesel and petrol european engines.
Recently I wanted to extend the car model area to japanese models, I have bought for personal study and use a 2002 Subaru WRX and I chose Tactrix cable to be the first interface to be used in the process of tuning the car.
So I purchased Tactrix cable on 08dec 2013,
Item Title:
Order Number: 14293
Invoice ID:
46194_563b2ea7561e1917c062b75eed.
I received the cable 2-3 weeks after payment done via Paypal, having ZERO documentation ( no user manual ). The cable was initially achieved for my personal Subaru, as I said, so once I've got the cable having no documentation I tried to read/write the ecu to see how the interface works.
It took me half a day to realise that beside the test mode connector that must be bridged, there is another reflash connector that must be plugged, this being a conclusion after 3-4 hours of searching on the forum to find same issues as I had. Anyway, this is just a simple story, maybe my level of knowledge is zero and I am too "stupid" to own this cable. In the end I managed to read the ecu, modified it, reflashed it, car works like a charm.
Now let's get to the point of our topic:
This Monday we had a customer entering our workshop, owner of a Lancer X 1.5 N/A, 2008 my, who wanted just a simple raise of RPM CUT point.
I plugged the Tactrix cable, selected "mitsucan" protocol ( 2006+ CAN based mitsubishi ), and tried to read the ecu. I got an error while trying to read the ecu ( I repeat, I just pressed the "read" button ) and from this moment on there was no communication with the engine ecu on CAN network.
I diagnosed the ETACS unit and immo unit, both had PCM timeout CAN communication errors. Diagnosis of engine ecu was possible, but only on K-line, on CAN - ecu acted like it was dead.
What followed after this failure was a painful and awful series of attempts to bring ecu back to life. After starting to search the web for same issues, I got here:
http://mmcflash.ru/forum/index.php?showtopic=64
and here:
http://www.digital-kaos.co.uk/forums/f1 ... sh-377008/
, where it seems some other users of same Ecuflash+Tactrix cable had same issue and resulted in dead engine units.
Conclusion was that 93s66 eeprom content was corrupt, inhibiting CAN communication with the ecu, ecu acting like being stuck in bootmode.
I will not share the repair method, I will just tell you that I had to reach for the eeprom, which is installed on back of PCB, so ecu plastic case had to be cut, I think I desoldered/read/write/soldered back the 93S66 eeprom more than 50 times to make tests, in the end the car was restored with a certain content written by me inside the eeprom ( not the original content, obvious, which was corrupt ) and with the help of MUT3 tester from the local Mitsu dealership.
The guys from MMCFLASH.ru ( user name Bruce Willis, also on this forum ) know this issue and have solution for it, the MMCFLASH software has unlock button to bring ecu back to life.
Considering I was not warned in any way about this possible failure, considering here < http://www.tactrix.com/index.php?option ... &Itemid=41 > it is clearly stated that the cable works on " basically any Mitsubishi ECU based on a H8, SH-2, or M32r processor", I would like to ask the owner of this forum and the Tactrix cable supplier who is going to pay for the costs of labour for bringing ecu back to life, for the costs of entering the dealership , for the costs of renting a car for the customer as his car was immobilised all this time.
I will contact the Tactrix supplier and bring this to his knowledge, I have invoices for all services that had to be made to get the car back to life. If I will not get my money back, I will press charges against the supplier.
This topic is intended for all of you to know that ECUFLASH + TACTRIX will kill the Lancer 1.5 N/A 2008 ecu by simply pressing READ button.