jhenkins
Standard Member
Hello!
I am attempting to get the most current information for 2024 together in this thread, so please forgive me for posting yet another "OVMS And MG5" thread.
Firstly, I have an OVMS unit that I have installed into my wife's Nissan Leaf '14 (AZE0) model, and we are immensely pleased with it. So it's based on this that I bought another one to add to my (new to me) 2021 model MG5 SR (49kWh). I've been reading that things are still pretty experimental with the MG5, so I did not expect things to work completely out of the box. Being a Linux user I am quite happy with the experimental nature of the MG5 support, and I am looking forward to opportunities to contribute.
What I have found so far:
Since I have the 2021 EU-spec model, I have observed the "Zombie" mode as described in other threads on the same topic as this one. I have also observed the fact that I have to run the OVMS in manual polling mode, or face the alarm going off. I also experienced the alarm going off when I left an OBD2 Bluetooth dongle plugged in overnight, which was interesting to say the least.
I have also read that MG5 support has been moved into the edge firmware, so I have installed the latest version I could find:
3.3.004-117-gd7013460/ota_1/main (build idf v3.3.4-851-gfa4f07fb3b Jun 23 2024 17:00:42)
Before I upgraded to the edge version, I had the latest stable OTA installed. The battery SoC did not report correctly (and in fact it did not do so even after I upgraded to edge). Here follows some photos and screen captures.
Firstly, the dash reports 62% charge:
The next two graphics shows the data from the OVMS app (I used the images for the ZS because we currently do not have MG5 images in the app - I hope to have some ready within the next month). First one shows car details, and the second one the battery percentage:
As we can see, the battery percentage and GOM estimates does not reflect what is visible on the dash photo.
Here are the same info as above as visible in the OVMS web GUI:
The status view echos what is visible in the OVMS app, and the charger metrics view also adds the same details with SoC at 56% instead of 62%. At least the SoH value corresponds to what is visible via an OBD2 dongle and an app like Torque Pro or Car Scanner, so I'm happy about that. Oh, and I noticed that there is an artefact in the header of the charger metrics view that says my car is a ZS EV, which probably points to the fact that the ZS EV files were used as a starting point for the MG5.
My first question for this thread is how do I get the battery display to be accurate? It would be great if the GOM could also be tweaked, but I suspect that the GOM estimates are correctly calculated from the wrong battery SoC value. Any ideas, please?
Thanks in advance!
Jan Henkins
PS: Something I've forgotten to do before I posted the above: I will get the SoC value as reported by Torque and/or Car Scanner, and append it to this message. It would be interesting to see whether that is similar to the value as reported on the dash as opposed to the other value reported by OVMS.
I am attempting to get the most current information for 2024 together in this thread, so please forgive me for posting yet another "OVMS And MG5" thread.
Firstly, I have an OVMS unit that I have installed into my wife's Nissan Leaf '14 (AZE0) model, and we are immensely pleased with it. So it's based on this that I bought another one to add to my (new to me) 2021 model MG5 SR (49kWh). I've been reading that things are still pretty experimental with the MG5, so I did not expect things to work completely out of the box. Being a Linux user I am quite happy with the experimental nature of the MG5 support, and I am looking forward to opportunities to contribute.
What I have found so far:
Since I have the 2021 EU-spec model, I have observed the "Zombie" mode as described in other threads on the same topic as this one. I have also observed the fact that I have to run the OVMS in manual polling mode, or face the alarm going off. I also experienced the alarm going off when I left an OBD2 Bluetooth dongle plugged in overnight, which was interesting to say the least.

3.3.004-117-gd7013460/ota_1/main (build idf v3.3.4-851-gfa4f07fb3b Jun 23 2024 17:00:42)
Before I upgraded to the edge version, I had the latest stable OTA installed. The battery SoC did not report correctly (and in fact it did not do so even after I upgraded to edge). Here follows some photos and screen captures.
Firstly, the dash reports 62% charge:
The next two graphics shows the data from the OVMS app (I used the images for the ZS because we currently do not have MG5 images in the app - I hope to have some ready within the next month). First one shows car details, and the second one the battery percentage:
As we can see, the battery percentage and GOM estimates does not reflect what is visible on the dash photo.
Here are the same info as above as visible in the OVMS web GUI:
The status view echos what is visible in the OVMS app, and the charger metrics view also adds the same details with SoC at 56% instead of 62%. At least the SoH value corresponds to what is visible via an OBD2 dongle and an app like Torque Pro or Car Scanner, so I'm happy about that. Oh, and I noticed that there is an artefact in the header of the charger metrics view that says my car is a ZS EV, which probably points to the fact that the ZS EV files were used as a starting point for the MG5.
My first question for this thread is how do I get the battery display to be accurate? It would be great if the GOM could also be tweaked, but I suspect that the GOM estimates are correctly calculated from the wrong battery SoC value. Any ideas, please?
Thanks in advance!
Jan Henkins
PS: Something I've forgotten to do before I posted the above: I will get the SoC value as reported by Torque and/or Car Scanner, and append it to this message. It would be interesting to see whether that is similar to the value as reported on the dash as opposed to the other value reported by OVMS.