There was some discussion regarding this, that we never resolved. Perhaps a good time to finalise a unified approach for this? To avoid metric bloat, we could perhaps use OvmsMetricSet to store different estimates for different kW ratings? Regards, Mark.
On 24 Feb 2019, at 10:45 PM, Robin O'Leary <ovmsdev@caederus.org> wrote:
https://github.com/openvehicles/Open-Vehicle-Monitoring-System-3/pull/207
This adds support for 6 metrics ("xnl.v.c.duration....") reporting the Leaf BMS's time estimates in minutes for various hypothetical charging conditions:
* to 100% charge (".full") * to 80% charge (".range")
* with power ~1.6kW (".l0") * with power ~3.3kW (".l1") * with power ~6.7kW (".l2")
I find them useful, although they don't seem to fit in the existing OVMS charge reporting framework, which expects an on-going charge before it calculates any estimate.
They may also help us reverse-engineer whether the BMS expects temperature, cell state, tapering near full, etc. to affect the duration, if we want to make our own time estimation algotithm,
On my Leaf (which has the 6.6kW charger), the dash display normally shows two charge time estimates: at 3.3kW power ("xnl.v.c.duration.full.l1") and at 6.6kW power ("xnl.v.c.duration.full.l2"). My model has the option for "Long life battery mode"; when this is enabled, it instead shows the values to 80% ("xnl.v.c.duration.range.l1", "xnl.v.c.duration.range.l2"). _______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev