Firmware for charger, BMU, CMUs

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.
kiev said:
#01 could cause the EV-ECU to throw P1B08
#02 could " " " " " "

i started going thru the list to find a 1-to-1 relation of decimal codes to DTC P-codes, then remembered that there is a Mits Service Bulletin, MSB-18EXML54-002, with updated information on troubleshooting the OBC and DCDC for Model Years 11-14, and seems to match up P-codes to the symptoms of the decimal codes.

http://mmc-manuals.ru/msb/BASE/003/2018/MSB-18EXML54-002/E/MSB-18EXML54-002.pdf
Click to expand...

Thanks kiev. I believe I see now. You have to use the VCI with MUT3 SW. Mine only supports VCI - Lite with MUT3 SE SW.

There are more functions with MUT3 and VCI that I don't have.
 
coulomb said:
CAN bus messages on the BMU to CMU private bus
Click to expand...
piev asked me about this recently as he is digging into the Pack CAN Buss.
Here is a capture from a 2012 miev that i made some time ago:
Code: 
Summary of CMU CAN buss scan in which the ignition key was toggled ACC and ON.
The buss turns off when the key is in the OFF or ACC position.                                      
    PID 3C3    8 bytes                  
        1    2    3    4    5    6    7    8  
    3C3    When key goes to ON, sends 4 messages with 0x0F in the 5th byte, then it sends ~25 messages with a temperature limit? in the 2nd byte, then sends a cell voltage in 2 bytes, and possibly a cooling or balancing? indicator in the 4th byte.                          
                                       
                                        ACC=off
SCAN HEX DATA STARTS HERE WHEN KEY IS SWITCHED FROM ACC TO ON                                      
REPEATS    4X    0x0    0    0    0    F    0    0    0    ON
        0x0    0    0    0    F    0    0    0  
        0x0    0    0    0    F    0    0    0  
        0x0    0    0    0    F    0    0    0  
REPEATS 25X    0x0    52    0    0    0    0    0    0  
        temp limit = 82 - 40 offset = 42C
        0x0    52    0    0    0    0    0    0  
        0x0    52    0    0    0    0    0    0  
REP 429X    0x1    8D    0    0    0    0    0    0  
        cell voltage 3.98
        0x1    8E    0    0    0    0    0    0    3.97
        0x1    8D    0    0    0    0    0    0    3.98
        0x1    8E    0    0    0    0    0    0  
        0x1    8E    0    2    0    0    0    0    ACC=off
                                       
repeats 4x    0x0    0    0    0    F    0    0    0    ON
        0x0    0    0    0    F    0    0    0  
        0x0    0    0    0    F    0    0    0  
        0x0    0    0    0    F    0    0    0  
repeats 25x    0x0    52    0    0    0    0    0    0    ON
till key off    0x0    52    0    2    0    0    0    0    ACC=off
                                       
repeats    4x    0x0    0    0    0    F    0    0    0    ON
        0x0    0    0    0    F    0    0    0  
        0x0    0    0    0    F    0    0    0  
        0x0    0    0    0    F    0    0    0  
repeats 42x    0x0    52    0    0    0    0    0    0  
till end of scan0x0    52    0    0    0    0    0    0  
        0x0    52    0    0    0    0    0    0  
        0x0    52    0    0    0    0    0    0  
        0x0    52    0    0    0    0    0    0  
        0x0    52    0    0    0    0    0    0  
        0x0    52    0    0    0    0    0    0  
        0x0    52    0    0    0    0    0    0  
        0x0    52    0    0    0    0    0    0  
        0x0    52    0    2    0    0    0    0    ON
                                       
                                       
CELL DATA FROM CMUs
    PID    INDEX    3 temperatures/card    cell voltage    cell voltage      
                                       
    611    0x1    0    45    45    1    8E    1    8E    cmu 1
    612    0x1    0    45    45    1    8E    1    8E    8-cells
    613    0x1    44    45    0    1    8E    1    8E    2 cards
    614    0x1    0    0    0    1    8E    1    8E
                                       
    621    0x2    0    45    44    1    8E    1    8E    cmu 2
    622    0x2    44    44    0    1    8E    1    8E    8-cells
    623    0x2    44    45    0    1    8E    1    8E  
    624    0x2    0    0    0    1    8E    1    8E  
                                       
    631    0x3    0    45    44    1    8E    1    8E    cmu 3
    632    0x3    44    44    0    1    8E    1    8E    8-cells
    633    0x3    44    45    0    1    8E    1    8E  
    634    0x3    0    0    0    1    8E    1    8E  
                                       
    641    0x4    0    45    45    1    8E    1    8E    cmu 4
    642    0x4    44    44    0    1    8E    1    8E    8-cells
    643    0x4    44    45    0    1    8E    1    8E  
    644    0x4    0    0    0    1    8E    1    8E  
                                       
    651    0x5    0    45    45    1    8E    1    8E    cmu 5
    652    0x5    45    45    0    1    8E    1    8E    8-cells
    653    0x5    45    45    0    1    8E    1    8E  
    654    0x5    0    0    0    1    8E    1    8E  
                                       
    661    0x6    0    45    45    1    8E    1    8E    cmu 6
    662    0x6    45    FF    0    1    8E    1    8E    4-cells
    663    0x6    FF    FF    0    FF    FF    FF    FF    1 card
    664    0x6    0    0    0    FF    FF    FF    FF  
                                       
    671    0x7    0    45    45    1    8E    1    8E    cmu 7
    672    0x7    45    45    0    1    8E    1    8E    8-cells
    673    0x7    45    45    0    1    8E    1    8E  
    674    0x7    0    0    0    1    8E    1    8E  
                                       
    681    0x8    0    45    45    1    8E    1    8E    cmu 8
    682    0x8    44    44    0    1    8E    1    8E    8-cells
    683    0x8    44    45    0    1    8E    1    8E  
    684    0x8    0    0    0    1    8E    1    8E  
                                       
    691    0x9    0    45    45    1    8E    1    8E    cmu 9
    692    0x9    44    44    0    1    8E    1    8E    8-cells
    693    0x9    44    45    0    1    8E    1    8E  
    694    0x9    0    0    0    1    8E    1    8E  
                                       
    6A1    0xA    0    45    44    1    8E    1    8E    cmu 10
    6A2    0xA    44    44    0    1    8E    1    8E    8-cells
    6A3    0xA    44    45    0    1    8E    1    8E  
    6A4    0xA    0    0    0    1    8E    1    8E  
                                       
    6B1    0xB    0    46    45    1    8E    1    8E    cmu 11
    6B2    0xB    45    45    0    1    8E    1    8E    8-cells
    6B3    0xB    45    45    0    1    8E    1    8E  
    6B4    0xB    0    0    0    1    8E    1    8E  
                                       
    6C1    0xC    0    46    45    1    8E    1    8E    cmu 12
    6C2    0xC    46    FF    0    1    8E    1    8E    4-cells
    6C3    0xC    FF    FF    0    FF    FF    FF    FF  
    6C4    0xC    0    0    0    FF    FF    FF    FF
 
Last edited:
Hello, can I ask if anyone has previously analyzed the files to read and write data learned from BMU? Wouldn't this be a way to hack the BMU? Furthermore, it seems safe to go back when saving the original data file. I don't think this has any meaning. to do with firmware, if not with real data from our batteries stored in the BMU, maybe we can change LEV50 to LE50N? In addition, there is a manual programming of the time in months and km of our battery, perhaps we can cross-reference data from all our BMUs and analyze each one by comparison, it seems to be possible with MUTIII and the functionality is also in DiagBox according to MickeyS70
http://mmc-manuals.ru/manuals/i-miev/online/Service_Manual/2017/00/html/M100102100002203ENG.HTM
 
Juanjo Madrid said:
In addition, there is a manual programming of the time in months and km of our battery, perhaps we can cross-reference data from all our BMUs and analyze each one by comparison, it seems to be possible with MUTIII and the functionality is also in DiagBox according to MickeyS70
Click to expand...
There is no need to cross-reference this data, these values are just used to calculate the battery capacity based on age and usage (mileage). It gets you in the ball park though and should then allow the ‘native calibration’ to do the fine adjustments over time.

You need MUT/Diagbox to enter this information, therefore using these tools to run an actual battery calibration makes way more sense.
 

Latest posts

Back
Top