OVMS (Again)

[jamessimpson]

OK thanks again Peter. I Have installed 3.3.004-254-gc8914214/ota_0/edge, first with an Empty Vehicle. I'll see how it goes!

 

[jamessimpson]

OK thanks again Peter. I Have installed 3.3.004-254-gc8914214/ota_0/edge, first with an Empty Vehicle. I'll see how it goes!

Not great afraid. The edge version wasn’t stable and didn’t seem to update the metrics regularly so I switched to the latest main version which is working properly. I haven’t observed the crazy SoC spikes yet but it’s only been a short time ….

 

[GreyPeter]

Testing with the main version should be fine. There has only been changes to the MG4 code since April. Let me know if you have any problems.

 

[jamessimpson]

Hiya, I'm afraid I've still got problems.

Although with the 3.3.004 main version I no longer seem to get the crazy high SoC spikes, I am getting frequent problems with most of the status metrics (which I receive into Home Assistant via MQTT to create binary_sensors) such as v.e.drivemode and v.e.locked. They seem to switch status randomly, when the car is locked and idle. So it might say it's moving or unlocked. Sometimes this is when plugged in, sometimes not. What I have noticed is that the 12V reading often oscillates around the same time, flicking between a resting voltage and 13-14V every few seconds. This is accompanied by frequent stop/start status updates for 12V charging (see attached). It's also often, but not always, accompanied by failing to read the main battery SoC (no SoC value via MQTT or via web console), until the ignition is powered on. When it does this it'll charge all night but not update the SoC reading until it's switched on, and although you can log onto the console via a web browser the SoC is not displayed there either.

At first I thought this was sleeping behaviour of the module, shutting down due to low 12V readings and periodically re-checking. However I have extensively fiddled with all of the settings pertaining to this in Vehicle > 12V as well as under Power Management. I have also checked with an external meter (incl to calibrate) during this behaviour and the true voltage stays relatively constant during the time that OVMS reports it as constantly switching between charging and not.

Any ideas please? Is it a bug?

Thanks for all your help, it is much appreciated!

 

[jamessimpson]

Hiya, I'm afraid I've still got problems.

Although with the 3.3.004 main version I no longer seem to get the crazy high SoC spikes, I am getting frequent problems with most of the status metrics (which I receive into Home Assistant via MQTT to create binary_sensors) such as v.e.drivemode and v.e.locked. They seem to switch status randomly, when the car is locked and idle. So it might say it's moving or unlocked. Sometimes this is when plugged in, sometimes not. What I have noticed is that the 12v reading often oscillates around the same time, flicking between a resting voltage and 13-14v every few seconds. This is accompanied by frequent stop/start status updates for 12v charging (see attached). It's also often, but not always, accompanied by failing to read the main battery SoC (no SoC value via MQTT or via web console), until the ignition is powered on. When it does this it'll charge all night but not update the SoC reading until it's switched on, and although you can log onto the console via a web browser the SoC is not displayed there either.

At first I thought this was sleeping behaviour of the module, shutting down due to low 12v readings and periodically re-checking. However I have extensively fiddled with all of the settings pertaining to this in Vehicle > 12v as well as under Power Management. I have also checked with an external meter (incl to calibrate) during this behaviour and the true voltage stays relatively constant during the time that OVMS reports it as constantly switching between charging and not.

Any ideas please? Is it a bug?

Thanks for all your help, it is much appreciated!

BTW, I've also recently replaced the 12V battery...