I'm buying a non-runner MIEV here in Japan!

[MickeyS70]

My FULL CHIP Lexia 3 cable arrived yesterday finally. But the driver's aren't loading correctly and it's still an 'unknown device'.

I need to start over again with a clean OS install. Just need to figure out which OS is the best one to use. I see you used XP. Readme doc says to use Win 7 32bit and only up to 7.57 of Diagbox is best

Yes, I use Diagbox 7.58 on Win XP; my Lexia cable shows as ACTIA USB Devices (USB COM Board Evolution Driver) in Device manager.

I did use the CDs provided with the clone, even the outdated Virus scanner was on constant overdrive but who cares, it’s an old laptop only running Diagbox without Wi-Fi access…

.Oh yeah. I was forgetting about that driver by @kolyandex. That looks promising. I REALLY want to get MUT-3 working

Best chance of that happening seems to be using a genuine Tactrix Openport 2.0. Just be wary, others have reported that kolyandex has a tendency to overpromise and underperform.

 

[Rational]

For about the same price as his driver aliexpress is selling this VCI option.
https://www.aliexpress.com/item/1005007130256815.html

 

[Rational]

The other option is the NVCI RNM adapter.
https://www.aliexpress.com/item/1005006990957054.html



Which says it also works with Nissan consult3+ as well.

 

[Rational]

The car has been running great. So grateful again for all your help. Thank you guys.

I've not had time to get back to trying to get the full chip lexia cable working. Will do though eventually here soon.

But in the meantime, I thought I might order a second key fob as I only have one right now. Model G8D-841M-KEY-D. Two buttons.

Any recommendations on ordering a replacement? Do you know if the JDM ones are different than other countries?

Aliexpress has other model numbers that look the same, but not sure if they'll work.

Also, what's the best procedure you've used to program these?

Oh, and do you know if a used key can be reprogrammed? I found one on ebay and another on yahoo auctions.

Also, anyone know if it's a 315 mhz key? I found this page that shows it as 315mhz:
https://automotivekeysupply.com/products/mitsubishi-prox-remote-used-g8d-841m-key-d-2-2-2b

 

[MickeyS70]

I've not had time to get back to trying to get the full chip lexia cable working. Will do though eventually here soon.

Also, what's the best procedure you've used to program these?

Oh, and do you know if a used key can be reprogrammed? I found one on ebay and another on yahoo auctions.

You need Diagbox/MUT3 to (re?) program a fob (remote lock/unlock) or pair a new key (transponder chip).

 

[Rational]

I finally just got the VCI cable visible in psa-diag.fr VM version 9.91r3!
(Edit: Actually the r3 version came on a CD with one of my cables. It wasn't from psa-diag.fr. I'll try theirs again later.)

I'm finally seeing it show up as Actia USB Devices > USB Com Board Evolution Driver (UMDF) in device manger! Yes!

And the PSA Interface checker V3 also sees it now as INIT OK and version APPLI_XS_Fuji_P106138A V4.4.0 @ ACTIA 17.09.20
Reference serial is 921815 C/

Edit: I also got the VCI detected in the psa-diag.fr VM version 7.57 as well now too!


I'm not at home to plug it into the car right now though but will when I get home. Fingers crossed it works!

But one problem is diagbox is asking for a 17 character VIN. My car has a Japanese chassis number which is much shorter. So I'm not sure it will work.

Has anyone shared their VIN on here that I could try to type it in if it doesn't auto find my car and talk to it?


About XP & Win 7 32 bit OS installs:
I'd also like to still figure out how to get a 7.57 or 7.58 install to work on XP or Win 7 32bit so I can do it myself in case it works better for my car. Any idea on the drivers required to get past the unknown device on those OSs?

Based on the driver name in the Vmware 9.91r3 VM, I'm going to try this driver in XP and Win 7 32 bit next to see if it helps.
https://www.driverscape.com/download/usb-com-board-evolution-driver-(-multi-instance-)

Also, in the virtualbox 7.57 VM it shows this driver:


https://www.driverscape.com/download/usb-com-board-evolution-driver-(-multi-instance-)

So far I have not been able to successfully install any version of the software directly on Win 7 32 or 64 bit or Win 10.

I tried last night on XP but the Diagbox 7.01 installation also fails because it is not registered after entering scary01. This was a fresh install of XP on an old HP E5430 laptop.

It simply says: "Activation failed (error o)". Or sometimes that there is no internet connection. But all read-me files say not to connect it to the internet.

I'm on my 7th try at least with different OS and VM versions and still no luck.

I must be missing a step or not finding the right drivers to install.

 

[Rational]

Well I got home tonight and tried it on both VMs. Says it can't update the VCI and so won't proceed.

It wasn't doing this when I was testing at work. So I wonder if when I switched the VCI around on different versions of Diagbox it didn't like updating the VCI each time with a different version of the firmware? Is that how these work? They need a specific firmware version for each different version of Diagbox?

If so, which firmware versions match which Diagbox version and where do I get the firmware files to update the VCI cable manually?

 

[MickeyS70]

If so, which firmware versions match which Diagbox version and where do I get the firmware files to update the VCI cable manually?

No idea, my installation doesn’t even feature a VCI checker??
Ever tried the ‘non full chip version’?

 

[Rational]

No idea, my installation doesn’t even feature a VCI checker??
Ever tried the ‘non full chip version’?

Yeah, I couldn't get it to work before. I've misplaced it since. So until I find it I won't be able to try it with my new understanding of how all this works.

I did get the full chip version of the cable talking tonight though!

I downloaded the v9.068 VM version from psa-diag.fr and I was finally able to get it to talk to the car!

But I had to use a VIN I found in one of the posts someone made sharing their full 17 digit VIN number.

I used WEGTPHE4XBXXX01--, from this post: https://myimiev.com/threads/another-i-miev-battery-pack-failing-help.4308/post-39058

Sadly it didn't read all components of my car. But the MCU was one that did work. I grabbed some screenshots.

I wished someone knew how to get these JDM cars with only a chassis number to read. It seems like I may only be able to use MUT3 with these.

 

[Rational]

Interesting. I just found this VIN coder breakdown document.

Source: https://owners.mitsubishicars.com/s/vehicle-resources/vin-details

https://mmna-ssb.my.salesforce.com/...5/SUDP9dftqgAhSefTwDKegCuoWOWVDl8vH_m4yEj8yk8


So for a Japan built MIEV it should be something like: JA3115A1?CU100439.

Not sure what the check digit in slot 9 should be. I see it as W in some shared VINs on this forum.

So maybe I could test with JA3115A1WCU100439 ? I'll try that and see what it shows.

Oh, but I also just found this page with some example VIN search results showing the 9th digit as 4.
https://vininspect.com/vin/mitsubishi/i-miev/2012/ja3215h14cu



So I might try JA3115A14CU100439 in Diagbox and see what I get.

Or just use one of these listed VINs as they're likely to be usable as they're from real cars of the 2012 model.
Which since the JDM was released a year earlier in Japan as a 2011 model I'm thinking they'd be identical to Diagbox.

Based on this post: https://myimiev.com/threads/car-not-working-after-hv-traction-pack-swap.5634/post-49944

He shares these two VINs, "VIN numbers are JMALDHA3WBU000217 for the old crashed donar car and JMALDHA3WBU000297 for the car I am trying to fix"

They decoder chart above says it is for "MMNA vehicles". The above two VINs don't conform to this layout in fields 2-11.

What are MMNA vehicles? = "Mitsubishi Motors North America, Inc"


I wonder what they call the JDM division? MMJ vehicles? MMJP vehicles?

Later edit 2 Nov 2024: Found the answer on http://www.auteltech.com/vehicle-coverage/coverage2 website.


It would be nice to find a decoder sheet chart for the JDM chassis numbers.

Also I read somewhere that it is possible to look up the VIN numbers online somewhere for the US and European cars somehow as there's a big list for showing some kind of details. Need to remember where I read that and what it was used for. With that I might be able to find some more info on a possible Japanese chassis number listing.

Edit: I found it: https://myimiev.com/threads/i-miev-and-lexia-3-and-diagbox.4042/post-37821
"
Although the VIN number on a C-Zero/Ion is detected automatically by Diagbox you have to enter a valid RPO number manually, which is not actually printed on the car. (I looked mine up on Puegeot service box)

Diagbox has a database of vehicle VIN numbers built into the software that lists exactly what ECU is present in every supported car sold by Peugeot/Citroen. So the VIN number of the vehicle is used to look up this database and build a list of ECU's to search for and query.

If i-Miev VIN numbers are not in this database it won't know what ECU's it should be looking for and will say that it is an unsupported car."

 

[MickeyS70]

What do CANIon or OBDZero show for VIN, blanks or chassis number?

 

[Rational]

What do CANIon or OBDZero show for VIN, blanks or chassis number?

Where do i look in those apps? I don't remember seeing any VIN listed in those?

Only the Topdon successfully auto found the VIN so far out of all the scantools I have tried.

 

[MickeyS70]

Where do i look in those apps? I don't remember seeing any VIN listed in those?

CANIon: see pic in post #10 (you may have to tick the box in settings for it to show)
https://myimiev.com/threads/i-think-its-just-one-bad-cell.5668/

OBDZero: (last?) entry in OBD tab

 

[Rational]

CANIon: see pic in post #10 (you may have to tick the box in settings for it to show)
https://myimiev.com/threads/i-think-its-just-one-bad-cell.5668/

OBDZero: (last?) entry in OBD tab

Canion is not showing the VIN for me. Even though it was already checked in the settings to display it.

I did not check OBDZero yet, but perhaps it's in past screenshots I've posted of it. I'll try and check it next I remember.

So today I spent the day playing with VMs of Diagbox 9.68 and 7.57 from psa-diag.fr. They both work.

But 'work' needs to be defined. I'd read other posts stating it is working, but it's not really recognizing many ECUs because of my VIN issues.

Also it asks for an RPO number? I think that was it. Someone posted you can use 0000 and it will work. Well, again, 'work' just means it will continue. Not that it has correct definitions to be able to talk to the ECUs correctly. 1234 also 'works' in the respect it continues.

So my fault scans stated they couldn't recognize many of the subsystems. But I could get information from them and scan for error codes and clear them. So I guess it 'works'. It doesn't inspire confidence though that it's safe or accurate to do so though.

I think for these JDM i-miev models it is probably best to use MUT-III.

I was able to clear all codes with 7.57 though and they stayed gone afterwards. 9.86 wouldn't clear a steering wheel error code and keep it gone. It also stated at one point that it would need to connect to the internet to perform an action. Sadly I couldn't remember what it was to test it on 7.57 again later.

But it is nice having these working finally and the full chip adapter has nice clicky relays in it. So that inspires confidence.

I also took out my MCU#3 today as it was still not sealed up. I sealed up MCU#2 and put it in the car to confirm if it would work. It does!

I even got the actual threebody 1207F as recommended in the manual. I'm up to spec.

In fact, it shows an RR of 100km at 75% SOC. Which MCU#3 was showing only 41km at about 50% SOC. So it seems the GOM stuff is definitely stored in the MCU.

I took it for a test drive and it works great!

So I have a spare MCU and OBC unit now at the ready should they ever fail.

New coolant added and all buttoned up! Just need to get the seats steam cleaned and the body waxed and she'll be good as new.

I love this little car. Dare I say it? I actually like it for quick trips more than the Leaf!

 

[Rational]

Oh, we also ordered two more key fobs of the exact same model. Should be here this coming week.

I'll need to find out how to program them with Diagbox. All steps and tips appreciated if you know them.

 

[kiev]

In fact, it shows an RR of 100km at 75% SOC. Which MCU#3 was showing only 41km at about 50% SOC. So it seems the GOM stuff is definitely stored in the MCU.

Who could argue with such rational logic?

Your understanding of how these cars operate would be greatly improved by reading the technical information section of the service manual.

 

[MickeyS70]

Canion is not showing the VIN for me. Even though it was already checked in the settings to display it.

I did not check OBDZero yet, but perhaps it's in past screenshots I've posted of it. I'll try and check it next I remember.

Don’t bother, based on the experience of @alviseven it will be blank also, seems like both apps to a rudimentary VIN check and leave it blank if the information found doesn’t comply.

So today I spent the day playing with VMs of Diagbox 9.68 and 7.57 from psa-diag.fr. They both work.

But 'work' needs to be defined. I'd read other posts stating it is working, but it's not really recognizing many ECUs because of my VIN issues.

Also it asks for an RPO number? I think that was it. Someone posted you can use 0000 and it will work. Well, again, 'work' just means it will continue. Not that it has correct definitions to be able to talk to the ECUs correctly. 1234 also 'works' in the respect it continues.

So my fault scans stated they couldn't recognize many of the subsystems. But I could get information from them and scan for error codes and clear them. So I guess it 'works'. It doesn't inspire confidence though that it's safe or accurate to do so though.

Try this (cancel all error messages you get in the process)
1. Turn on the car (READY)
2. Connect the Lexia cable
3. Start Diagbox 7.5x
4. Select Peugeot
5. Select iON
6. Confirm “Is the VIN read on the vehicle correct” it should show chassis no..
7. RPO enter 0000
8. Confirm “Connect to the internet” but don’t connect.
9. On Application Launching click on ‘Fault Finding’
10. Global Test will access and show about a two dozen ECUs

Step 6 seem to be important, if the VIN isn’t recognised automatically it’s probably not going to work out for you.

I think for these JDM i-miev models it is probably best to use MUT-III.

Seems to be the case if you have problems with step 6. above. It may be possible to ‘fool’ Diagbox with a CAN bridge though.

I was able to clear all codes with 7.57 though and they stayed gone afterwards. 9.86 wouldn't clear a steering wheel error code and keep it gone. It also stated at one point that it would need to connect to the internet to perform an action.

It appears that Diagbox 9.x wants to ‘phone home’ before it will let you do certain actions, best to stick with V7.xx

So I have a spare MCU and OBC unit now at the ready should they ever fail.

Where did you get the OBC from or do you mean type 1 EVSE?

I love this little car. Dare I say it? I actually like it for quick trips more than the Leaf!

Welcome to the club..

 

[Rational]

Found this nice page with info on the transponders inside the fobs for all the different Mitsubishi models.

https://www.transpondery.com/transponder_catalog/mitsubishi_transponder_catalog.html



I think my JDM miev is the same as the Outlander 2006-2012 models as well as I see a lot of Outlander youtube fob videos have the same key fob design.



I may end up trying my XTOOL scantool to do the programming instead of diagbox since I'm still not so sure about diagbox with my car yet.

Diagbox says it needs 'the customer's confidential card." No idea what or where that may be found. I don't have it I don't think.



Found this great video showing an XTOOL key reprogramming procedure. Gives me some confidence.

 

[Rational]

Just seeing your last reply now. I'll check it and reply in a bit.

So I can't find the key slot I see they have in other cars like the outlander. The slot where they put the fob in the glovebox when reprogramming a fob key.

Do you have them in your mievs? Hopefully the process won't ask for that knowing it doesn't exist on my model when I eventually try it.

Still awaiting the used fobs to arrive.

I may make my own "How to install and use Diagbox for i-miev" video soon as there is actually a lot to understand the first time.

It would be better to have a more concise video than what is currently scattered about youtube.

 

[MickeyS70]

Diagbox says it needs 'the customer's confidential card." No idea what or where that may be found. I don't have it I don't think.

It’s the car’s security code, usually written down in the user manual, but if lost, a Mitsu dealer should be able to get it for you.

Do you have them in your mievs?

No