Sage advice, Mr. O'Connell! Barry Rowland
On 03/08/2016, at 19:09 , "Brian O'Connell" <[email protected]> wrote: > Dear Hardware People on the third rock from Sol, > > Software beings (self included) are idiotically clever and tend to be rather > subversive. We can devise profoundly evil schemes that can 'go around' fault > conditions in electrical components that forces our equipment to pump out > giggle watts of power while the surrounding creation melts down. > > Pro-tips for future compliance engineers: > 0. Never trust any software types; not even a single one among us. If your > significant other is a software engineer, learn to sleep with eyes open. > 1. learn how to read code like a book (which means you will need to > understand the language's basic syntax and structural characteristics). > 2. learn how to run code in an emulator that can run under fully static clock > conditions. > 3. learn how to determine code coverage. > 4. carry a large hammer to meetings with the s/w dev team. > > Brian > > > From: Richard Nute [mailto:[email protected]] > Sent: Wednesday, August 03, 2016 9:41 AM > To: [email protected] > Subject: Re: [PSES] SAFETTY FEATURES controlled by ....SOFTWARE > > 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:[email protected]] > Sent: Wednesday, August 03, 2016 7:33 AM > To: [email protected] > 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 > <[email protected]> > > 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 <[email protected]> > Mike Cantwell <[email protected]> > > For policy questions, send mail to: > Jim Bacher: <[email protected]> > David Heald: <[email protected]> - ---------------------------------------------------------------- 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 <[email protected]> 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 <[email protected]> Mike Cantwell <[email protected]> For policy questions, send mail to: Jim Bacher: <[email protected]> David Heald: <[email protected]>
