What actually is MUT III in detail?

[hjdlsnbc]

Could you tell where to find this cloning functionality in the BMU when using Diagbox?

If one knew how to find, decode and then change the information, this function could be used to customise the BMU, e.g. increase the capacity…

This wont be needed any more for the NMC cells. We can just use the already modified BMU from @piev where @kolyandex modified his BMU for the NMC cells.

If you tell here in a thread (probably at best some extra thread written as a howto by you) as detailed as possible at best with pictures how to clone the BMU with Diagbox, then @piev can repeat this and upload his BMU firmware to the forum here.

 

[MickeyS70]

This wont be needed any more for the NMC cells. We can just use the already modified BMU from @piev where @kolyandex modified his BMU for the NMC cells.

That never happened I’m afraid (see post #2/4 below)
https://myimiev.com/threads/main-traction-battery-upgrade-i-miev.5458/

Could you tell where to find this cloning functionality in the BMU when using Diagbox?

It’s been a while since I used Diagbox (Version 7.x) but IIRC it can be found in the repair section of the BMU.

 

[hjdlsnbc]

Here a really short howto to get the MUT-3 SE (the CAN version) as fast as possible working with a J2534 passthru capable adapter because i struggled to get it otherwise working:
Download the latest https://psa-diag.fr/diagbox/Diagbox-vm.php (newest version of it, based on Windows 10) and install in this Diagbox VM the MUT-3 2022 (or 2021 version, should not make any difference) version, install the two file version from ParisCY (the directory replacement version is required on 2023 and newer MUT-3 SE) of the passthru dll file with the .txt file, install the normal J2534 adapter driver of the adapter you have and then it should somehow work.
It have nothing to do with the Diagbox software in the VM. This VM there is just the base i used to install additional MUT-3 SE on it because i had issues with other OS combinations. Maybe i would write a more in detail version and try out what is working best when i finally get this working: https://myimiev.com/threads/tpms-on-i-mievs.1881/post-50834

 

[Rational]

Here a really short howto to get the MUT-3 SE (the CAN version) as fast as possible working with a J2534 passthru capable adapter because i struggled to get it otherwise working:
Download the latest https://psa-diag.fr/diagbox/Diagbox-vm.php (newest version of it, based on Windows 10) and install in this Diagbox VM the MUT-3 2022 (or 2021 version, should not make any difference) version, install the two file version from ParisCY (the directory replacement version is required on 2023 and newer MUT-3 SE) of the passthru dll file with the .txt file, install the normal J2534 adapter driver of the adapter you have and then it should somehow work.
It have nothing to do with the Diagbox software in the VM. This VM there is just the base i used to install additional MUT-3 SE on it because i had issues with other OS combinations. Maybe i would write a more in detail version and try out what is working best when i finally get this working: https://myimiev.com/threads/tpms-on-i-mievs.1881/post-50834

Oh, perfect timing. I was actually going to start over and do this today. I'll use your input above. Thank you.

 

[Rational]

Here a really short howto to get the MUT-3 SE (the CAN version) as fast as possible working with a J2534 passthru capable adapter because i struggled to get it otherwise working:
Download the latest https://psa-diag.fr/diagbox/Diagbox-vm.php (newest version of it, based on Windows 10) and install in this Diagbox VM the MUT-3 2022 (or 2021 version, should not make any difference) version, install the two file version from ParisCY (the directory replacement version is required on 2023 and newer MUT-3 SE) of the passthru dll file with the .txt file, install the normal J2534 adapter driver of the adapter you have and then it should somehow work.
It have nothing to do with the Diagbox software in the VM. This VM there is just the base i used to install additional MUT-3 SE on it because i had issues with other OS combinations. Maybe i would write a more in detail version and try out what is working best when i finally get this working: https://myimiev.com/threads/tpms-on-i-mievs.1881/post-50834

Yes, I have also spent crazy amounts of time and frustration on this but have a feel for it all now so hope to succeed finally with it.

Some questions:

What baremetal OS are you running on your laptop? Win 10?

What laptop model? I'm asking as CPU virtualization support is a factor to confirm. So the CPU generation trying to be used may matter.


Summary:
1. Then you are loading the latest Win10 VM from psa-diag.fr. OK. Will do that.
( I will document the exact version name and link here later if I succeed.)
Can you share the exact version you succeeded with? I have 9.068 downloaded now.
But you say, 'latest'. So that seems to be 9.186. That what you used?

2. Then loading MUT3 2022 or 2021. OK. Will do that.
( I will document the exact version name and link here later if I succeed.)
Can you share the exact version you succeeded with?
And where did you download it from? Have a link?

3. Install the normal J2534 adapter driver of the adapter you have and then it should somehow work. OK. I will do that.
( I will document the exact version name and link here later if I succeed.)
Can you share the exact driver version you succeeded with?

So you did successfully get MUT-3 SE to talk to the car through the PSA adapter? Or which adapter did you use?

 

[Rational]

By the way, ParisCY posted this about MUT3 versions:

He says, "2016 and 2022 on windows 11 64bit tested and working great, no errors on installation, the windows was not fresh, was full of softwares from other brands, all installations i make of Mut was successful always, it's a very easy software and it's hard to get error, so probably issue of anyone has error on Mut will be a killed file from antivirus."

https://mhhauto.com/Thread-Mitsubis...-Bosch-Autel-Actia-etc?pid=2710003#pid2710003

So now I'm in search of a 2022 and 2016 MUT-III versions. I have only "MUT3-OBD2-Software-PRE21061_00" currently.

 

[Rational]

The MUT III software can be found here:
http://mmc-forum.ru/viewtopic.php?p=1173#p1173

Oh, nice. I was just looking for some links for 2016. But it seems that russian site doesn't have any versions after 2021 though. Later edit: All the links are dead. No seeders.

The 'Immobilizer Key Register Password' for the i-miev is: 8035

I was just going to post this nugget! I read it on page 4 of that russian site mut3 thread. Great info! I may need this to program some key fobs successfully.

 

[Rational]

The driver of kolyandex of course got hacked at some point by someone else that now sells his driver. Even this person who sells the cracked kolyandex software recommends to not use china clones for really crtitical operations here: https://mhhauto.com/Thread-MUT-3-J2534-FULL-DRIVER?pid=2406799#pid2406799

Woah, this is interesting. If I can't get ParisCY's verision working this is the next cheapest option it seems.

Oh, but it seems it is only via remote install. No thanks.

 

[Rational]

Haha. Well that didn't work. This was after copying in the version.txt file and the .dll from ParisCY's common folder.

If I revert back to the stock .dll it opens fine. Just not with his MutVciPassThru.dll

Used Diagbox_9.186_PSA-DIAG.FR_VMWARE_2024 with MUT3 PRE23061.iso I'd found on a russian site last week.

I didn't load any VCI driver. Just tried to use the PSA XS one built into the VM.

I guess I'll try to find a 2022 version next...

Edit: oh, wait. He said this, "The 2 files fix is until 2022 version, for 2023 versions find my 2023 solution in 2023 thread. "
https://mhhauto.com/Thread-Mitsubis...-Bosch-Autel-Actia-etc?pid=2777355#pid2777355

Need to find that thread now... what a pita.

Later edit: There is no other thread. omg.

He says later this, "On 2023 and 2024 you must rename the common folder and add the folder i post. Did you do that?"
https://mhhauto.com/Thread-Mitsubis...-Bosch-Autel-Actia-etc?pid=2883152#pid2883152

So I'll try copying in the 2024 common folder with complete contents that he offers in his first post and see if that opens the 2023 version and works.

Well, I got two new options this time on initial start of mut3se. And it does open now that I've copied in the 2024 common folder from ParisCY.

I chose option 2, PSA- J2534.




I don't have my car here to plug into at the moment though. But it does error out when I try to click the check mark to read one of the ECUs.



This is the error I've been getting all along with all different VCIs so far with MUT3. But I'll try it when connected to the car next to see if it succeeds. But to me this looks like the software isn't talking to the VCI yet.

So do I need a particular driver loaded? Or choose option 1 maybe?

 

[Rational]

Nope. Same error when connected to the car.

For both options. PSA Full chip doesn't work for me with this version of mut3se. And or the 9.186 VM.

 

[Rational]

Yes!!! I got it talking!

Phew. That was tough. It didn't work with the PSA XS full chip clone. I had to use the openport 2.0 clone.

And it's not perfect. Two ECUs cause MUT3se to crash. If I scan all DTCs the 3rd-4th on the list all crash it.

So I have to uncheck those. I think one was airbags and another was the air conditioner.

I took a ton of screenshots or so I thought but it tuns out the VM didn't actually save them anywhere. Bah...

So it does detect my chassis number finally! This is the only software that does. And has all the correct info listed.

I just need to get a more stable VCI working. Once I have a quality one I will feel comfortable enough to try reprogramming some key fobs with it.

I think my sm2pro clone will likely be the most reliable one of the bunch once I reflash the firmware on it.

I will also try the godiag gd10 as well next to see if it talks to it. But right now perhaps the openport 2.0 original version may be the most stable and trustworthy one to purchase from what I can tell so far in using this .dll file.

Will need to do more testing. I also really like the MUT3 software. It's very simple and clear. I also found the spot to write the VIN/chassis number to the MCU if I ever wanted to do that. Pretty simple actually as it pulls it from other ECUs and just gives you the option to write it to the MCU if you want to.

I may try an earlier version of MUT3SE to see if it will work with the PSA full chip adapter. That could be a great one if I can get it to work. I tried both options and neither saw it within MUT.

I'll try and get more screenshots tomorrow to share.

Edit: By the way I just learned that, "PRE - for the European market, SEW - for Asia."

I found the older versions of MUT3 here: https://forum.kolyandex.su/viewtopic.php?f=14&t=19
This page also explains how to start the install properly within powershell as administrator.

Also here: https://rutracker.org/forum/viewtopic.php?t=5559302

 

[kiev]

So it does detect my chassis number

How does it display--as 10 digits or 17 ?

 

[Rational]

How does it display--as 10 digits or 17 ?

It displays as HAW3-0100439. So 12 digits.

I was hoping to have a screenshot for you already. But I only have a few I captured properly on the baremetal OS.



It seems that it errors on SRS-AIR BAG and Air Conditioner. I started over from Air Conditioner and it still errored out.
Was fine starting with ETACS. The first two also worked fine. So the OP2 clone doesn't seem to work with the air bag or A/C ECU areas.


These are the three options I currently have to choose from: Neither 1 nor 2 talk to the PSA VCI adapter.

 

[kiev]

0100439

" ZAAHA3WLDD0100439 " for a 17-digit VIN ?

 

[Rational]

" ZAAHA3WLDD0100439 " for a 17-digit VIN ?

I could try it on Diagbox I suppose. I'll let you know if it works. Thanks for the idea.

 

[Rational]

Just wanted to update this thread for anyone getting here in the future. Got it working. Details here:
https://myimiev.com/threads/im-buying-a-non-runner-miev-here-in-japan.5649/post-50987

 

[hjdlsnbc]

the two file version from ParisCY

btw, here it is so that you should not have to register to other forum for just this files. I removed the password and repacked it as zip file. Its for MUT-3 SE up to year 2022.

And here a short review between original ACTIA VCI interface original made for diagbox and original Tactrix OpenPort 2.0:
With the original OpenPort 2.0 i do have crashes with MUT3-SE fully reproducible when doing this:
Press "ALL DTC" button and then read DTC. If you let all checked or read just "Air Conditioner" does not make a change. The MUT3-SE software dated year 2021 always crashes with OpenPort 2.0 . But when i instead use the ACTIA VCI then its not crashing when reading "Air Conditioner". It just report back "NC" and continue when other things then "Air Conditioner" have been selected to read out.

I also attached the
M.U.T.-III SE User's Manual
Ver.4.1
to this post. It is important to know what button does what and where to find different things.

 

[Rational]

And here a short review between original ACTIA VCI interface original made for diagbox and original Tactrix OpenPort 2.0:
With the original OpenPort 2.0 i do have crashes with MUT3-SE fully reproducible when doing this:
Press "ALL DTC" button and then read DTC. If you let all checked or read just "Air Conditioner" does not make a change. The MUT3-SE software dated year 2021 always crashes with OpenPort 2.0 . But when i instead use the ACTIA VCI then its not crashing when reading "Air Conditioner". It just report back "NC" and continue when other things then "Air Conditioner" have been selected to read out.

Thanks for the confirmation that this is the same behavior between your original Tactrix OpenPort 2.0 and my clone OP2. I get the exact same crash. So I guess I won't bother buying an original if it is no better for this use case.

Thank you for saving me $180.

My full chip actia clone behaves as you state above too. It just says NC for those two areas but continues smoothly through the scan without crashing. Shown in this video I posted earlier here:
https://myimiev.com/threads/im-buying-a-non-runner-miev-here-in-japan.5649/post-50996