12v battery went dead. Jumped it and left key in ready for 30 mins. Then completed charging with ext charger. That all went fine. Plugged main charger in and in a mental slip turned key to on then to ready. Check engine light (stop car and call dealer light came on). Switched key off and completed charging of drive batty overnight. Call dealer light stayed on. Took it for a 45 mile spin all normal except the call dealer light stayed on. Disconnected 12 v batty for 30 secs hooked it back up and commenced charging drive battery. Call dealer light still on. I am in Abaco Bahamas there is no dealer to call. Hope someone can help.
Check engine light on
- Thread starter vh2q
- Start date
Help Support Mitsubishi i-MiEV Forum:
PV1
Well-known member
Had this happen to me. It appears to be some overzealous programming that makes you go to the dealer so they can check why the 12 volt battery went dead. This is triggered when the battery is too low for the vehicle to either start or charge. Unfortunately, without a dealer or their MUT-3 and computer tool, this light will remain on.
Do you know what caused the 12 volt battery to go dead? Did you try to start or charge it before jumping the 12 volt battery?
Do you know what caused the 12 volt battery to go dead? Did you try to start or charge it before jumping the 12 volt battery?
zzcoopej
Well-known member
vh2q said:
The "check engine" light is also known as the "dealership $ sign". Its likely that the flat battery has just tripped one of the sensors. Some faults reset after a couple of cycles however others remain until they are reset. I have plans to build the feature to find out the fault code & reset it (assuming its trivial) into my App EvBatMon, however it hasn't risen to the top of the feature requests yet.
i don't think you can read the fault code with an OBD reader--it is not using the same CAN protocol that ICE cars use. i've tried and the reader could not identify the protocol.
PV1
Well-known member
Torque and the i-MiEV don't get along. Just opening the app causes the MCU Warning light (car with !), RBS, ASC, and ASC Off lights to come on. A simple power cycle clears it, but I don't recommend using Torque.
You can bet with that announcement that code reading will jump up on the request list for EVBatMon (which is working well except for random value spikes and the accompanying beep).
You can bet with that announcement that code reading will jump up on the request list for EVBatMon (which is working well except for random value spikes and the accompanying beep).
DonDakin
Well-known member
I experienced this also while measuring the 12 volt loads. At one point while putting an amp meter on the 12 volt battery I think the 12 volt became disconnected while the car was in ready mode and the exclamation point symbol came on.
The car ran fine and i used it for months with the light on. I eventually got it rest by the dealer.
Don.....
The car ran fine and i used it for months with the light on. I eventually got it rest by the dealer.
Don.....
We address this 'storage' issue in various threads on this forum. Anything over about three weeks and the 12v battery should be either disconnected or attached to a smart 'float' charger (not old-fashioned 'trickle' charger). If outside, a very small solar panel with regulator also works great. With OEM 12v batteries now with four-year+ lives (and thus diminished capacity), I would slap on a 12v float charger even if I left the car for a week.vh2q said:
Excellent data point.DonDakin said:
That's sort of what I figured and if it was me I simply wouldn't worry about it as the 'failure' cause has been identified.DonDakin said:
zzcoopej
Well-known member
vh2q said:
I am prepared to add the feature to EvBatMon if you are happy to test it for me? It will take about a week.
vh2q, thanks for the update as I think you're the first one to have actually pulled codes off our i-MiEV. As we had discussed before, in your situation (having rental i-MiEVs on an isolated island), I would try to get a MUT3. I was hoping zzcoopej would further develop EVBatMon to include both error-code reading as well as reset capability.
I take it the car runs ok despite the warning?
I take it the car runs ok despite the warning?
Those codes don't appear as valid codes in the factory service manual, i would guess they are some artifact of the reader--what sort of reader did you use?
zzcoopej
Well-known member
JoeS said:
Yes that is still the plan. We're about to release the iOS version of EvBatMon, and then back to adding features like reading & resetting DTC codes.
vh2q said:
Did it identify the meaning of each code, or just show a list of codes?
It seems strange that codes could be thrown for which there is no identification or explanation in the service manual, so please let us know your findings.
Zzcoopej i can test code reading if u do new beta version for evbatmon 
What was this feature which allows code reset for 2-4 times with Citroen maintenance Official tool? But after that even it cant reset it? I have motor controller condensator code now resetted 3 times and now its locked. How it it resetted again? Those 3 resets maded in same afternoon so no any change on car between resets..
What can even Official maintenance do in this situation? Can they someway reset this 3 time reset countet? Maybe it need somekind of total reset to hole system. Or firmware reload?
What was this feature which allows code reset for 2-4 times with Citroen maintenance Official tool? But after that even it cant reset it? I have motor controller condensator code now resetted 3 times and now its locked. How it it resetted again? Those 3 resets maded in same afternoon so no any change on car between resets..
What can even Official maintenance do in this situation? Can they someway reset this 3 time reset countet? Maybe it need somekind of total reset to hole system. Or firmware reload?
Similar threads
