That has been my experience with CB Scheme, E-mark, and product safety in the USA using an NRTL. Namely, pick worst-case with justifications, talk with your certifier, and reach an understanding. If they won't budge and insist on full testing of every variant, move to another certifier who is willing to listen to reason.
If the "code" is different and your firmware is a functional safety component, then you may not have much choice but to repeat at least some of the tests called out in the test plan to verify nothing was "broken" when tweaking the firmware to accommodate each hardware variant. Ralph -----Original Message----- From: Lfresearch <[email protected]> Sent: Friday, April 5, 2024 3:47 PM To: [email protected] Subject: [PSES] I would like to hear your thoughts please Hi folks, I would like to advise a client at where to draw the line on what needs testing. I would like to solicit opinions besides my own. Otherwise it’s the fox urging the chicken coop… So a manufacturer that makes a product of which there will be several variants. All use the same board, but have different sections of circuits populated. This may require slightly different code to run on the same uP in each case. So.. The burning question is can we perform and analysis that postulates a worse case hardware/software combination and test just one configuration? Or, do we have to do every combination? Or, are there some guidelines about where we draw the line of what to test and what can be claimed as similarity? Off list responses are welcome too. Thanks, Derek Walton LFResearch/SSCLabs. - ---------------------------------------------------------------- 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: https://www.mail-archive.com/[email protected]/ Website: https://ewh.ieee.org/soc/pses/ Instructions: https://ewh.ieee.org/soc/pses/list.html (including how to unsubscribe) List rules: https://ewh.ieee.org/soc/pses/listrules.html For help, send mail to the list administrators: Mike Sherman at: [email protected] Rick Linford at: [email protected] For policy questions, send mail to: Jim Bacher: <[email protected]> _________________________________________________ To unsubscribe from the EMC-PSTC list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=EMC-PSTC&A=1 - ---------------------------------------------------------------- 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: https://www.mail-archive.com/[email protected]/ Website: https://ewh.ieee.org/soc/pses/ Instructions: https://ewh.ieee.org/soc/pses/list.html (including how to unsubscribe) List rules: https://ewh.ieee.org/soc/pses/listrules.html For help, send mail to the list administrators: Mike Sherman at: [email protected] Rick Linford at: [email protected] For policy questions, send mail to: Jim Bacher: <[email protected]> _________________________________________________ To unsubscribe from the EMC-PSTC list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=EMC-PSTC&A=1
