<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
I thought about using FEATURE_CB_SVALERTS for this as well -- no
need to introduce a separate alert class IMO.<br>
<br>
But this really has no priority, just one user wondered why he got
an SOC alert he did not configure... I think he'll be fine to accept
it as a hard coded feature as well.<br>
<br>
Regards,<br>
Michael<br>
<br>
<br>
<div class="moz-cite-prefix">Am 06.05.2016 um 05:08 schrieb Mark
Webb-Johnson:<br>
</div>
<blockquote
cite="mid:F79E0C94-98F3-4CC6-9F15-0293C3B50FCA@webb-johnson.net"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
I think it is fine to put this as a carbits feature to opt-out.
<div class=""><br class="">
</div>
<div class="">Perhaps:</div>
<div class=""><br class="">
</div>
<blockquote style="margin: 0 0 0 40px; border: none; padding:
0px;" class="">
<div class="">#define FEATURE_CB_SSOCZERO 0x80 // Set to 1 to
suppress SOC 0% alert</div>
</blockquote>
<div class=""><br class="">
</div>
<div class="">Regards, Mark.</div>
<div class=""><br class="">
</div>
<div class="">P.S. sys_features are current 8bit. Not hard to
increase to 16 or 32 if necessary.</div>
<div class=""><br class="">
</div>
<div class="">
<div>
<blockquote type="cite" class="">
<div class="">On 20 Apr 2016, at 5:20 PM, Michael Balzer
<<a moz-do-not-send="true"
href="mailto:dexter@expeedo.de" class="">dexter@expeedo.de</a>>
wrote:</div>
<br class="Apple-interchange-newline">
<div class="">
<div class="">Brian,<br class="">
<br class="">
I was not thinking about removing both SOC alerts, just
the fixed one, and maybe then default the configurable
to 5%.<br class="">
<br class="">
Self discharging rates are very low on lithium cells in
general, and the BMS will normally cut off the battery
long before reaching critical voltage levels, leaving
several months of self discharging without damage. All
third party BMS systems I checked during the last year
or so support this.<br class="">
<br class="">
I understood from reading a web report on this, that the
roadster BMS does not cut off the battery by a relais,
the car electronics will continue operation until the
battery is dead. The first gen Twizy has the same
problem on the 12V aux battery, that's why I introduced
the 12V alert. That's also a bug, consequences are just
not as expensive.<br class="">
<br class="">
I don't need the low SOC alert at all, I use the car
nearly every day (the Twizy is my only car), I always
know the SOC and take care to charge it up as soon as
possible, to keep cycles shallow and charge while the
battery is warm. Parking at 100% SOC is also no problem
on the Twizy, as the 100% mark is at ~ 4.12 V per cell,
well below spec max.<br class="">
<br class="">
But the situation is of course different when you've got
plenty of capacity and fast charging capability.<br
class="">
<br class="">
Regards,<br class="">
Michael<br class="">
<br class="">
<br class="">
Am 20.04.2016 um 09:15 schrieb HONDA S-2000:<br class="">
<blockquote type="cite" class="">Michael,<br class="">
<br class="">
Any battery will continue to self-discharge, even
after it is disconnected from everything.<br class="">
<br class="">
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).<br class="">
<br class="">
In other words, it's not a BMS bug. Chemistry dictates
that all batteries will self-discharge, even if very
slowly.<br class="">
<br class="">
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.<br
class="">
<br class="">
Brian<br class="">
<br class="">
<br class="">
On Apr 18, 2016, at 2:23 PM, Michael Balzer <<a
moz-do-not-send="true"
href="mailto:dexter@expeedo.de" class=""><a class="moz-txt-link-abbreviated" href="mailto:dexter@expeedo.de">dexter@expeedo.de</a></a>>
wrote:<br class="">
<blockquote type="cite" class="">Tom,<br class="">
<br class="">
so the roadster doesn't cut off the battery to avoid
deep discharging?<br class="">
Sounds like a bad BMS bug...<br class="">
<br class="">
Ok, that's a very good reason why this kind of alert
should be sent out<br class="">
on all channels available.<br class="">
<br class="">
Thanks & regards,<br class="">
Michael<br class="">
<br class="">
Am 18.04.2016 um 20:56 schrieb Tom Saxton:<br
class="">
<blockquote type="cite" class="">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.<br
class="">
<br class="">
Tom<br class="">
<br class="">
On 4/18/16, 8:35 AM, "Michael Balzer" <<a
moz-do-not-send="true"
href="mailto:ovmsdev-bounces@lists.teslaclub.hk"
class=""><a class="moz-txt-link-abbreviated" href="mailto:ovmsdev-bounces@lists.teslaclub.hk">ovmsdev-bounces@lists.teslaclub.hk</a></a>
on behalf of <a moz-do-not-send="true"
href="mailto:dexter@expeedo.de" class="">dexter@expeedo.de</a>>
wrote:<br class="">
<blockquote type="cite" class="">Hi everyone,<br
class="">
<br class="">
we've currently two low SOC alerts in the
framework, one is the<br class="">
configurable (feature #9) min SOC alert in
vehicle_ticker(), the other<br class="">
is the OVMS_SOCALERT code in
net_state_ticker600().<br class="">
<br class="">
The latter is fixed to 5% and does not respect
user channel &<br class="">
notification configuration. Is there still a use
case for this or is it<br class="">
obsolete?<br class="">
<br class="">
Regards,<br class="">
Michael<br class="">
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<br class="">
<br class="">
-- <br class="">
Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal<br
class="">
Fon 02333 / 833 5735 * Handy 0176 / 206 989 26<br
class="">
<br class="">
<br class="">
_______________________________________________<br
class="">
OvmsDev mailing list<br class="">
<a moz-do-not-send="true"
href="mailto:OvmsDev@lists.teslaclub.hk" class="">OvmsDev@lists.teslaclub.hk</a><br
class="">
<a class="moz-txt-link-freetext" href="http://lists.teslaclub.hk/mailman/listinfo/ovmsdev">http://lists.teslaclub.hk/mailman/listinfo/ovmsdev</a><br
class="">
</div>
</div>
</blockquote>
</div>
<br class="">
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
OvmsDev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:OvmsDev@lists.teslaclub.hk">OvmsDev@lists.teslaclub.hk</a>
<a class="moz-txt-link-freetext" href="http://lists.teslaclub.hk/mailman/listinfo/ovmsdev">http://lists.teslaclub.hk/mailman/listinfo/ovmsdev</a>
</pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal
Fon 02333 / 833 5735 * Handy 0176 / 206 989 26
</pre>
</body>
</html>