1

Automatic settings always (re-)activated in Android Auto

  • Done

Avatar
Daniel Bofinger

If you plan in Android Auto the automatic settings are always fully activated. I don't use automatic reference consumption (way too high) and SOH (Always 40% but in real 0%, Kia Soul EV problem) but automatic SOC. In settings i switch off this setting.
Planning in the app everything is O.K. but if I use AA all automatic settings are switched on.
Version 4.3.7

Activity Newest / Oldest

Avatar

Katya_ABRP

Status changed to: Done

Avatar

Daniel Bofinger

Now with the newest Version the problem is back again.


Avatar

Samuel_ABRP

Status changed to: In progress

Avatar

Samuel_ABRP

This will be fixed with the next version.


  • Avatar
Avatar

Daniel Bofinger

Now with the newest version the problem is back again. Planning with the app on the phone when AA is connected is O.K. but when you plan over the car screen the automatic settings are active.


Avatar

Samuel_ABRP

Hi, activating auto settings in AA is intentional. However it should not use the invalid SoH anymore. Does it still use it?


Avatar

Daniel Bofinger

Sorry for the delay. I don't like the automatic settings activated because the reference consumption is way too high. The SOH setting is still activated.


Avatar

Samuel_ABRP

In that case we should rather fix the soh issue. I'll check the task again and rank it higher.


Avatar

Daniel Bofinger

And this behaviour is not konsistent. Planning in the App doesn't activate the automatic settings. Planning with AA is with automatic settings.


Avatar

Samuel_ABRP

Yes that's intentional, as when you plan in the app you can do it from everywhere with every car and every state your car can have, but if you plan from AA or start a route, you are actually using that specific car so we assume the live data is correct when we read it. So the only reasonable way to fix this is to fix the live data.


Avatar

Daniel Bofinger

O.k. i already startet an issue on the ABRP/OVMS-link script to deactivate the SOH-transmission. What ist the reason for the wrong reference consumption? Does the script send wrong data or to few data?


Avatar

Samuel_ABRP

Probably the reduced estimated battery capacity due to bad soh. So is OVMS your telemetry data source? I think we also have native OBD support for the Soul. Did you try that too?


Avatar

Daniel Bofinger

I will try, but ovms is much more convenient. I also use it for monitoring the soc and stop charging at 80% at home. So always change the plug is not an option.


Avatar

Daniel Bofinger

Today I tested the direct OBD bluetooth connection without success. Unfortunately it doesn't work with my Konnwei adapter.


Avatar

Daniel Bofinger

I have now modified the script so that I can define the SOH myself. Now everything works. The reference consumption is now also calculated correctly.
Who wants to use the modified script for OVMS:
github.com/bofi99/ovms-link


Avatar

Daniel Bofinger

I have to correct me. The reference consumption ist still too high. Values auround 175 give me the best calculation but the automatic caclulation of the consumption is too high (220 +)