Connected but state of charge reported as 0%

[andyorkney]

So I have OVMS connected and sharing info to ABRP - however ABRP was reporting state of charge 0% - running the script eval generates: (removed the GPS data)

OVMS# script eval abrp.info()
Plugin Version: 2.2.0
UTC Timestamp: 1757971430 s
State of Charge: 0 %
Battery Power: 0 kW
Charging: false
DC Fast Charging: false
Parked: true
State of Health: 85 %
GPS Elevation: 48.6 m
External Temp: 14.5 °C
Battery Temp: 15 °C
Battery Voltage: 394.5 V
Battery Current: 0 A
Odometer: 92717.7 km
Estimated Range: 211 km
HVAC Setpoint: 0 °C
Cabin Temp: 13.3333 °C

all good but the SoC and maybe the Battery Power? Support to ID where I’m going wrong would be great, or is this a new issue, running firmware 3.3.005-130-gd2e63edb

thanks

[andyorkney]

So doing a bit of digging, seems my env200 2018 40kwh is always returning 0 from xnl.v.b.soc.instrument,

here's full list of vehicle derived values. Anyone steer me to what this might be?

My current workaround is to use xnl.v.b.soc.nominal to give me a guesstimate in ABRP - better than zero

OVMS# metrics list xnl.
xnl.bms.balancing 2,4,5,6,8,10,12,14,16,18,20,22,24,25,26,27,28,30,32,34,35,36,38,40,42,44,46,48
xnl.bms.temp.int
xnl.bms.thermistor
xnl.cc.fan.only no
xnl.cc.remotecool no
xnl.cc.remoteheat no
xnl.cc.rqinprogress no
xnl.v.b.capacitybars 9
xnl.v.b.charge.limit 35.5kW
xnl.v.b.e.available 20.88kWh
xnl.v.b.e.capacity 40kWh
xnl.v.b.gids 261
xnl.v.b.heatergranted no
xnl.v.b.heaterpresent no
xnl.v.b.heatrequested no
xnl.v.b.hx 64.1016
xnl.v.b.max.gids 500
xnl.v.b.output.limit 110kW
xnl.v.b.range.instrument 80M
xnl.v.b.regen.limit 11.5kW
xnl.v.b.soc.instrument 0%
xnl.v.b.soc.newcar 61.2676%
xnl.v.b.soc.nominal 64.3%
xnl.v.b.soh.instrument 85%
xnl.v.b.soh.newcar 86.0479%
xnl.v.b.type 2
xnl.v.c.chargebars 12
xnl.v.c.chargeminutes3kW 0
xnl.v.c.count.l0l1l2 2916
xnl.v.c.count.qc 93
xnl.v.c.duration 105,240,480Min
xnl.v.c.event.notification reset
xnl.v.c.event.reason
xnl.v.c.limit.reason normal
xnl.v.c.mode.raw 0
xnl.v.c.quick 210
xnl.v.c.relay.ac 32
xnl.v.c.relay.qc 0
xnl.v.c.state.previous charging
xnl.v.e.hvac.auto no
xnl.v.pos.odometer.start 57648M

[jason-abrp]

Unfortunately, we don't really have insight into the vehicle-facing side of the OVMS, you'll probably need to reach out on their forums or an ENV200 enthusiast group.

Does the OVMS App show a valid SoC? If so, it's possible they're using a different value to compute the SoC to display. In that case, perhaps a special case could be added to the code to handle that for the ENV200.

[andyorkney]

So the issue is resolved, the instructions on OVMS I think need some tweaks in respect of settings for CAN bus. To start with I edited code to read SoC "new car" as a work around but once ignored the instructions to set date to 2015 to get another feature working and changed the v3 server provider the SoC data started to work in ABRP. There are somethings in respect of ABRP and car play integration that I'd love to see some options/variations about. In the middle of a 1500-2000 mile trip so some issues in regards to user interface for ABPR in Apple CarPlay are repeatedly experienced. What might be best way to provide feedback on those observations?

[jason-abrp]

We track issues externally on Featurebase, so that's the best place to submit feedback:

https://abrp.featurebase.app/