I have virtually no experience in software safety.
I'm a hardware guy.
I suggest simulating failures in the sensors
(hardware) that gives the software info about what
state the battery is in. And, simulating failures
of the hardware controlling the charging,
discharging, and overcharging the battery. In
this way, you have accounted for the worst-case
failures of both the hardware and the software.
Rich
From: Bolintineanu, Constantin
[mailto:cbolintine...@tycoint.com]
Sent: Wednesday, August 03, 2016 7:33 AM
To: EMC-PSTC@LISTSERV.IEEE.ORG
Subject: [PSES] SAFETTY FEATURES controlled by
....SOFTWARE
Dear Colleagues,
I would like to kindly ask those who have an
extensive experience regarding the above subject,
to share their opinion about the following aspect:
Having a circuit which is charging a battery, and
having it controlled and protected by SOFTWARE
ONLY from the point of view of CHARGING ,
DISCHARGING, OVERCHARGING,
1. How do you think that SINGLE FAULT CONDITIONS
shall be applied? (without SOFTWARE working at
all? Or by providing a fault on the component
where the SOFTWARE is stored? OR BOTH
2. Which conditions do you think that shall be
imposed to the software and/or to the memory in
which it is stored?
Any other suggestions/observations/comments are
more than welcome.
Sincerely,
Constantin Bolintineanu P.Eng.
-
----------------------------------------------------------------
This message is from the IEEE Product Safety Engineering Society emc-pstc
discussion list. To post a message to the list, send your e-mail to
<emc-p...@ieee.org>
All emc-pstc postings are archived and searchable on the web at:
http://www.ieee-pses.org/emc-pstc.html
Attachments are not permitted but the IEEE PSES Online Communities site at
http://product-compliance.oc.ieee.org/ can be used for graphics (in well-used
formats), large files, etc.
Website: http://www.ieee-pses.org/
Instructions: http://www.ieee-pses.org/list.html (including how to unsubscribe)
List rules: http://www.ieee-pses.org/listrules.html
For help, send mail to the list administrators:
Scott Douglas <sdoug...@ieee.org>
Mike Cantwell <mcantw...@ieee.org>
For policy questions, send mail to:
Jim Bacher: <j.bac...@ieee.org>
David Heald: <dhe...@gmail.com>
