For no explicit reason why to qualify my sanity, I bought a(aka MUT3, Multi Use Tester v3 ) for my EVO X toolkit assortment. After surfing on the net, I decided on a unit off (turns out they all are from China) that gave the impression to meet my wishes, integrated a later model of tool (ALL of them include tool), a CF programming card and in particular said it used to be a programming model. It arrived 4 calendar days later. Incorporated a difficult case, a V.C.I (Car Communique Interface) field and a number of other OBD2 adapter cables. The VCI connects to the OBD2 port at the CAN bus by the use of an integrated cable, then to a USB port at the laptop with an ordinary A/B USB cable. Then the pc speaks to the automobile by the use of the VCI connection.
After surfing the MUT3 handbook (to be had right here:) I realized that the blue cable is suitable for all CAN-bus Mitsubishi vehicles. The crimson dual-head unit is for FUSO vehicles.
The PC must run the MUT3 diagnostic tool which got here on one DVD with two subdirectories on it. One a part of the two tool elements, PRG12031, incorporates the MUT3 diagnostic tool that will have to be put in first. This may also be put in from the DVD or by way of copying information/directories to the HD and putting in from there. Execute the Mut3Check.exe report. It is strongly recommended to put in onto Home windows 2K or XP working IE6 or IE8. The documentation states issues working beneath IE7; the MUT3 utility runs within Web Explorer. I’ve examine a success installations with Vista and Win7 at the Web; on the other hand I didn’t try this.
To start with there have been LOTS of mistakes putting in the diagnostic tool. It introduced a lot of completely unrelated mistakes and complained a couple of password being too quick (“Error: The password is shorted than required”). The XP SP3 pocket book I decided on to put in to have been part of my AD area and had minimal password period and complexity regulations already in position. The SW bundle installs a lite model of MS SQL 2005 and retail outlets all its knowledge in diversified MDB database information (Get entry to). It sounds as if the set up makes use of easy, quick passwords (extra in this later). First hurdle mounted by way of converting Native Safety Coverage.
Subsequent I skilled quite a lot of different set up mistakes: “FDICopy() failed”; “It used to be now not up to date in most cases”; “Didn’t setup database”; and so on. After uninstalling, cleansing the registry of scraps and re-installing a number of occasions I in the end were given the diagnostic bundle to complete with out error. After the compelled restart, I decided on to put in the opposite bundle, the database updates (programming knowledge). It ALWAYS failed when put in from the DVD and/or after copying it to the HD.
At this level I determined to Ghost my present pocket book symbol (incorporates ECUFlash, EVOScan, and a few different stuff I sought after to save lots of), then re-installed from the unique media to manufacturing unit new situation. Yep, I save the whole thing.
Then I uninstalled all of the trash tool that is available in a brand new pocket book from the SONY. I put in XP SP3. With a blank set up, I made any other Ghost symbol as a place to begin. Put in the diagnostic tool with out error. Every other symbol stored.
Tried to put in the programming date replace, I at all times won “Database replace error happened. Replace is cancelled.”. Grrr. I seemed within the subdirectory that had the programming updates in it, studying all of the ini & textual content information, the various CSV information, finding out what it used to be making an attempt to do to put in the updates. I came upon a easy programming error: It’s going to now not set up if now not run from a root listing! I copied that subdirectory to a brand new CD with handiest the ones information on it and the EXE report within the root. Good fortune! The knowledge information up to date. Now to play with the applying and spot what it has to provide.
Hooked up the VCI to my 08 MR after which to the pocket book. The auto used to be identified, diversified settings are to be had to be programmed or modified (TPMS, door lock settings, wiper velocity settings, and so on. And all of the anticipated CAN bus stuff, SAS stuff, and code checking/clearing. Up to now, so just right.
I learn despite the fact that diversified displays within theprogram and took copious notes at the section and tool numbers assigned to objects I knew just like the ECU and TCU. Lots of the tool numbers are Mitsubishi section numbers and now not associated with what we all know because the ROM ID. The one quantity I may acknowledge is the MFI (engine) tool model of 526921, representing a ROMID of 52690021. For instance:
ECU Beginning 04
Provider ID 85
ECU ID 00
ECU Diag Ver 01
Device Model 526921
Choice of Module 01
Device P/N 1860A98006
Chassis VIN JA3AW56V98Uxxxxxx
TC-SST:ECU Beginning 04
Provider ID 95
ECU ID 00
ECU Diag Ver 00
Device Ver 280204
Choice of Module 01
Device P/N 01 8631A3790B
Finally even I controlled to get the tool and knowledge updates put in, however it might now not ID any program information as being appropriate for my automobile. Grrr…
Subsequent I began in search of an OLDER model of. A member right here presented 11121 so I uninstalled my present 12031 (if truth be told reset again to an previous Ghost symbol). That model does see the automobile however does now not display any appropriate updates. I determined to put in the later TCU tool since I knew the report quantity to make use of, 8631B001.cff.
The TCU report put in as it should be. And it even labored! BTW – I disconnected each radiator lovers and hooked up a charger to the terminal subsequent to the grasp cylinder beneath the hood (a lot more uncomplicated than gaining access to the battery within the boot) and the cigar lighter charger to the pocket book. Programming took about 6 mins and didn’t set any codes afterwards. When having a look into the TC-SST programming segment, “Educate-In Mode” now presentations up as an to be had button the place it used to be now not displayed prior to now..
Automotive began, ran and drove. Moving used to be harsher beneath part-throttle modes than ahead of. Good fortune!
Having a look over the listing containing different .cff information (ROM knowledge information), it’s REALLY tough to determine which of them are for EVO X fashions. I did to find two for UK EVO X, however none for USDM (MMNA). Possibly any individual else has an inventory to transform between “1860A98006” and 52690021??
I’m beginning this thread to speak about knowledge and diverse successes/screw ups with MUT3 units and their tool.
I began studying the various MDB information the MUT3 utility makes use of to retailer knowledge. All of them use easy passwords to fasten the information – simply cracked with suitable equipment. There may be LOTS of helpful knowledge in a report named VIN_Search.mdb, 177MB in dimension. Password for that report is DGPLQ_UNN.
That’s it for now.