If the software lock cannot be itself disabled by the user, the I think you can argue that it is a non-radio product. But it is an 'argue' situation, where you must clearly document the reasons for your decision. With best wishes DESIGN IT IN! OOO - Own Opinions Only <http://www.jmwa.demon.co.uk/> www.jmwa.demon.co.uk J M Woodgate and Associates Rayleigh England Sylvae in aeternum manent. From: Chester Summers [mailto:[email protected]] Sent: 10 July 2017 23:46 To: [email protected] Subject: [SPAM] [PSES] radio function "locked out" via software...which rules apply? Dear listmates, I was asked an interesting question recently that I'm pretty certain has the standard compliance "it depends" answer: *Is a radio product with all radio functionality intentionally disabled via external software load still considered a radio product? The intent is to repurpose a common electronic HW assembly containing an embedded radio as a non-radio finished electronic product. The finished electronic product will be incorporated into a much larger final machine assembly where the radio is not needed. In this particular case it is apparently easier and more economical to disable the radio function with software load than to modify the subassembly hardware BOM. *Must products that contain disabled radio function (by way of HW or SW) be disclosed as radios, and if so, which countries require the disclosure? I'm withholding my thoughts in order to be brief, however, I'm hoping the experts in this matter will release the hounds and wax eloquently. Many thanks, Chet Summers This email and any files transmitted with it from Charles Machine Works are confidential and intended solely for the use of the individual or entity to which they are addressed. - ---------------------------------------------------------------- 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] <mailto:[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) <http://www.ieee-pses.org/list.html> List rules: http://www.ieee-pses.org/listrules.html For help, send mail to the list administrators: Scott Douglas <[email protected] <mailto:[email protected]> > Mike Cantwell <[email protected] <mailto:[email protected]> > For policy questions, send mail to: Jim Bacher <[email protected] <mailto:[email protected]> > David Heald <[email protected] <mailto:[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]>
