Reverse engineering BMS Firmware / Reflashing BMS

My Nissan Leaf Forum

Help Support My Nissan Leaf Forum:

This site may earn a commission from merchant affiliate links, including eBay, Amazon, and others.
Using a elm device (like you use for leafspy) would take around 90min to reflash.

I'm still working on the 4bar issue. A firmware update can fix that but not updating would be the better solution

Unlike the 3NA0D LBC firmware that you're clearly becoming very familiar with, the 24 & 30kWh AZE0 LBC firmwares don't allow the capacity bars to be restored - but they can easily be reduced lower. Looking at 4 bars on the cluster is obviously annoying, but you could reduce to 0 bars (by changing the SOH value that is used only for the bars) which would have no negative impact. I've done this before. Realistically the bars only served a purpose for Nissan's warranty criteria and once the warranty has expired as all ZE0 & AZE0 cars have it only serves as a constant reminder that your car isn't brand new anymore. At least on a ZE1, the capacity bars are on a screen that you need to navigate to rather than being in your face every day. Yes you could certainly do firmware patches for all of the effected AZE0 firmwares that allows the bars to be reset to 12, but would that even be a good thing? There will always be some less than honest people wanting to misrepresent cars for resale. There are certainly valid reasons to want to reset the SoH - i.e. after replacing cells. But perhaps a better solution would be to make your app always set the capacity bars to zero at the same time as the reset - which also makes it clear that the car has a non-standard battery pack.

Also, regarding your previous VCM question, no you don't need to worry about pairing keys etc after a VCM update. If you still want to try this then I could supply in a format ready for Consult to use if that's easiest for you. The way I look at it is updating the VCM is best practice anyway as earlier VCM versions were pretty buggy, although admittedly that is less of an issue on a Aus spec car as none of these shipped with the really old firmware versions. In theory the Nissan dealers looking after these cars when they were near new and under warranty should have updated these car's themselves, but unfortunately that isn't always the case - some dealers were more onto it than others.
 
Unlike the 3NA0D LBC firmware that you're clearly becoming very familiar with, the 24 & 30kWh AZE0 LBC firmwares don't allow the capacity bars to be restored - but they can easily be reduced lower. Looking at 4 bars on the cluster is obviously annoying, but you could reduce to 0 bars (by changing the SOH value that is used only for the bars) which would have no negative impact. I've done this before. Realistically the bars only served a purpose for Nissan's warranty criteria and once the warranty has expired as all ZE0 & AZE0 cars have it only serves as a constant reminder that your car isn't brand new anymore. At least on a ZE1, the capacity bars are on a screen that you need to navigate to rather than being in your face every day. Yes you could certainly do firmware patches for all of the effected AZE0 firmwares that allows the bars to be reset to 12, but would that even be a good thing? There will always be some less than honest people wanting to misrepresent cars for resale. There are certainly valid reasons to want to reset the SoH - i.e. after replacing cells. But perhaps a better solution would be to make your app always set the capacity bars to zero at the same time as the reset - which also makes it clear that the car has a non-standard battery pack.

Also, regarding your previous VCM question, no you don't need to worry about pairing keys etc after a VCM update. If you still want to try this then I could supply in a format ready for Consult to use if that's easiest for you. The way I look at it is updating the VCM is best practice anyway as earlier VCM versions were pretty buggy, although admittedly that is less of an issue on a Aus spec car as none of these shipped with the really old firmware versions. In theory the Nissan dealers looking after these cars when they were near new and under warranty should have updated these car's themselves, but unfortunately that isn't always the case - some dealers were more onto it than others.
I do agree about resetting the SOH to 0 if it's gonna be recalculated and return to a capacity you actually have in your pack. This way the owner will have to wait till SOH is recalculated before selling the EV.
 
mon outil fonctionnera directement avec le bms, ou via le port obd2 (evcan). J'utilise principalement le port ouvert tactrix, mais UCAN est toujours pris en charge, juste beaucoup plus lent.

Envoyez une photo de l'erreur que vous obtenez et je vous enverrai les dll qui vous manquent
mon outil fonctionnera directement avec le bms, ou via le port obd2 (evcan). J'utilise principalement le port ouvert tactrix, mais UCAN est toujours pris en charge, juste beaucoup plus lent.

Envoyez une photo de l'erreur que vous obtenez et je vous enverrai les dll qui vous manquent
Moi idem le logiciel
Leaf BMS flasher App for Tactrix Openport2.0 (clone) - Note this is currently only suitable for 3NA0x ECU's as it writes 3NA0D as the firmware label. I'll correct this at a later data for other BMS variants.
Hello, I have the same problem, the Tatrix leaf bmsflash software does not work, it does not even launch, nothing happens. Maybe I do not have the right version of Windows? I am on Windows 10!

Do I have to download something to make it compatible?

Thank you
 
Is it possible to use your software on a disassembled battery? by using a specific assembly and supplying it with 12 V?
 
I have a a BMS fimeware for battery custom 62kwh with calt cells to share if someone is intrested to analysing it?
yes please share here or better open a new thread with the name of the kit provider. I suppose Vivne. IIRC there is already a thread related with Vivne's kits. you could add ther and notify here. Would be interesting to see what is the values of the lookup tables.
 
I have a a BMS fimeware for battery custom 62kwh with calt cells to share if someone is intrested to analysing it?
Hi, I am analysing lookup tables in these firmwares to adjust firmware for used cells. I can check tables in this firmware if you can share it, thanks.


FYI
est. charging time tables already processed too :)
 

Attachments

  • est_time.jpg
    est_time.jpg
    291.1 KB
oui, merci de partager ici ou mieux encore d'ouvrir un nouveau fil avec le nom du fournisseur du kit. Je suppose que c'est Vivne. Si je me souviens bien, il existe déjà un fil lié aux kits de Vivne. Vous pouvez l'ajouter et le notifier ici. Il serait intéressant de voir quelles sont les valeurs des tables de recherche.
 
Yes, that's wha
yes please share here or better open a new thread with the name of the kit provider. I suppose Vivne. IIRC there is already a thread related with Vivne's kits. you could add ther and notify here. Would be interesting to see what is the values of the lookup tables.
Yes, that's what ViVent is saying. They make us believe that it's their engineers who reprogram their BMS, but in reality they subcontract lol
 
CURRENT LIMIT tables by temperature range (25 - 53 °C) vs SOC in ZE0 24kwh LBC
 

Attachments

  • TEMP-SOC-CURRENT_LIMIT.jpg
    TEMP-SOC-CURRENT_LIMIT.jpg
    136.2 KB
You need to split it, this 5 in 1 table is only for better grip I should split it up to 5 tables.
than't ok, but color rapms related to SOC seems not represented in the table, or it is an effect of color table stretching due to have splitted into multiple tables?
Are you able to just export as csv or some libreoffice spreadshit instead to share an image?
 
Back
Top