"Live" SoC At Start

When beginning a trip in a KIA EV6 with live data coming from an OBD2 dongle connected via OBDBLE. The initial SoC value may not reflect the actual SoC value even though the BLE connection appears to be up. This isn’t a big deal and it corrects itself within a few minutes, but it is a bit disconcerting at first. I looks like the SoC isn’t updating in real time (which is a very sensible decision) and the last known value (which may have been manually set) is used until the first update comes in.

This is what I saw today at start up:

This is the actual SoC about a minute later:

If the SoC value is available “on demand” it seems like requesting the SoC value at start up (and certainly before planning a route) would be a nice thing to do. If you have to wait for the car to send out the value, then perhaps ABRP could either display “- - %” or hold off on making the Bluetooth symbol green until a full set of data has come in (or at least the SoC value has come in). If a route has been planned that involves charging stops based on a (possibly) stale SoC value, it would be nice if the route was replanned based on the live value.

It seems to me that when I’ve started trips with incorrect SoC values that it can take quite a while for ABRP to notice that the charging stops that were planned need to be updated.