[Ovmsdev] net.c SOC alert obsolete?
s2000 at audiobanshee.com
Wed Apr 20 15:15:56 HKT 2016
Any battery will continue to self-discharge, even after it is disconnected from everything.
The Tesla Roadster does disable driving when the battery is below the single-digit cutoff, but I would still want a warning so I can come rescue the car! For example, if it were parked somewhere for a long term and the charge reached 5% (or even 7%), then I'd want to know about that because it's not a good idea to ignore the system and leave it when the charge is that low. It's certainly a warranty-voiding situation (although surely no Roadsters are in warranty any longer).
In other words, it's not a BMS bug. Chemistry dictates that all batteries will self-discharge, even if very slowly.
What I'm curious about is why other electric car owners would not also want to know if their battery was low enough to trigger an automatic cut-off.
On Apr 18, 2016, at 2:23 PM, Michael Balzer <dexter at expeedo.de> wrote:
> so the roadster doesn't cut off the battery to avoid deep discharging?
> Sounds like a bad BMS bug...
> Ok, that's a very good reason why this kind of alert should be sent out
> on all channels available.
> Thanks & regards,
> Am 18.04.2016 um 20:56 schrieb Tom Saxton:
>> Personally, I like having the second backup warning that doesn’t depend on a setting being right. It’s a big deal if our Roadster gets down to 5% accidentally.
>> On 4/18/16, 8:35 AM, "Michael Balzer" <ovmsdev-bounces at lists.teslaclub.hk on behalf of dexter at expeedo.de> wrote:
>>> Hi everyone,
>>> we've currently two low SOC alerts in the framework, one is the
>>> configurable (feature #9) min SOC alert in vehicle_ticker(), the other
>>> is the OVMS_SOCALERT code in net_state_ticker600().
>>> The latter is fixed to 5% and does not respect user channel &
>>> notification configuration. Is there still a use case for this or is it
More information about the OvmsDev