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

Mitsubishi i-MiEV Forum

Help Support Mitsubishi i-MiEV Forum:

This site may earn a commission from merchant affiliate links, including eBay, Amazon, and others.
After all that - so sorry to hear. Thank you for all the details.

BTW, my 2012 i-MiEVs will not 'start' (i.e., go into READY) in N, but only 'start' in P.
Thanks. I just tried it and mine also does not go into start in N. It will only go into ON mode.

If the the fault is within controller board 1 then this is excepted

Try MCU2 with controller 2 and clear DCTs or MCU3 altogether
Alright. Taking out MCU2 now (With the car's original MCU in it). Will try MCU3 now.

Thanks.
 
Car is fixed!

Phew!...

It goes into D and R without error now. Accelerator raises the rear wheels RPMs on each side. Yes!

Just worked when I installed MCU3 in it. No programming required.

I guess the JDM cars don't care about the chassis number after all?

No new VIN/Chassis number related DTCs thrown.

Just the U1111 error code is still present. Not sure how to clear it yet. (Later edit: U1111 is because my factory head unit (center console) has been replaced by the prior owner with a Kenwood head unit and so the car can't see it anymore. Ignore this error.



Thank you @kiev and @MickeyS70. I am very grateful for all the patience and knowledge you have shared this past week with me.

I have learned so much. Which is the real win here. And hopefully my struggles and your input will help others who come after me.

I will continue to update my posts here and share some more details as I learn new things.

Thank you again.

Thanks to you as well @JoeS. Got 'er goin'!

Now to learn how to optimize the drum brakes so they don't have any resistance on the car. :)
 
Last edited:
Seems like a great tool for adjusting the brake pads quickly:



I think I'm going to use a bit less tension on my drum pads though to reduce the constant friction to increase battery range.
 
Last edited:
@MickeyS70 @kiev @JoeS

I took the car for a test drive tonight!

Works great! Lovely little car. Thanks guys!

It had a seized drum brake cylinder on the right rear (driver's side, RHD).

Got the part ordered and delivered today by 1300 and had it installed by 6pm when I got home. YES!

Made sure the drum brakes weren't rubbing anymore like before. It's such a great car. Zippy even if I want it to be.

I also got the correct sealant delivered yesterday so am all set to button it up right this weekend.

I'll even put MCU#2 back together with its original controller board and also test that one to be sure it works.

I even got a free charger with MCU#3, so have that for 'someday' should I ever need it. Lucky! Total cost about a grand into it with new tools! :)

More to come. Thanks again guys for making my month. I've been having an absolute blast fixing this little car. It was tiring, but I was happy to do it.

I even learned how to use a DMM properly finally. Haha. And so much more. :)

I hope to send more donations when I can as well as more people to the forum. I'll also keep adding knowledge as I find it.
 
I drove it to work today! Muwhaahhaahahahaha... Feels so good.

No issues getting to work. Will drive it home later today. I kinda like the eco mode. Gives it a bit more solid feeling somehow.

But D is more loose and zippy. Got some brake pad scraping probably from some rust.

I read in another post that I should get ceramic brake pads so as to limit the rust. Especially in humid environments like here.

Going to the car wash in a few and will vacuum it out. Beautiful fall day here.
 
Don't waste any money on ceramic or any brake pads--once you learn to shift to B you won't need to use the brakes much at all. :ROFLMAO:
:ROFLMAO: Nice! Okay. I'll start doing that.

And thanks again Kiev. I appreciate all the detail you shared with me. You're da man.

I'm raising my troubleshooting method precision each time I learn something from one of your posts.
 
You’re not finished with the original yet, it being left sitting for months means the BMU’s capacity value might be way off, a battery calibration would be a good way to test your Lexia/Diagbox setup…
Oh? Nice catch. Thank you. Okay. I'll try to find the procedure on how to do that.

Sadly the Lexia 3 full chip cable still isn't here yet.

By the way, do you know which cables are MUT3 compatible. I really want to try out the MUT3 software.

Nothing I've tried so far as been showing up in mut3 as a compatible VCI.
 
Oh? Nice catch. Thank you. Okay. I'll try to find the procedure on how to do that.

Sadly the Lexia 3 full chip cable still isn't here yet.

By the way, do you know which cables are MUT3 compatible. I really want to try out the MUT3 software.

Nothing I've tried so far as been showing up in mut3 as a compatible VCI.
There seems to be a possibility to use a full chip Lexia cable with MUT3 (post #1)

https://myimiev.com/threads/using-t...re-adapter-as-a-universal-j2534-adapter.5594/
 
How about taking a crack at writing a vci device driver?

Or maybe someone already has--PC USB or serial port data (asynch RxTx, Hayes AT Modem commands) -to- CAN Buss (differential Hi-Lo) data
 
There seems to be a possibility to use a full chip Lexia cable with MUT3 (post #1)

https://myimiev.com/threads/using-t...re-adapter-as-a-universal-j2534-adapter.5594/
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.

So far I've tried Win 7 32bit and win 7 64bit as well as Win 10 64 bit but never have the PSA driver tester find the single board lexia 3 VCI device. :( Actually I've not had openport 2.0 work either yet. MUT3 never finds any of my VCI devices so far.

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

I may buy it from him if I can get the USB dongle version so I can reinstall the OS a bunch of times until I can finally get the VCI detected and working. But is his driver for Tactrix openport 2.0 or Lexia 3 full chip or both when using MUT-III?

It seems to be a driver/ VCI detection issue for me so far in my half dozen attemptes so far with setting up the OS and lexia 3 VCI and/or my openport 2.0 VCI devices. I've not succeeded so far. Neither in baremetal OS installs and tests nor with any virtual machine.

But I'll start over this weekend now that I have the full chip version of the lexia 3 adapter.
 
Back
Top