Hello Group, Can anyone direct me to information concerning e labeling of a Bluetooth module and Device. We are currently marking the FCC, IC and KC ID physically on the product label but we ran out of room due to an OEM request on one of our products. I understand that FCC and IC accept e labels on products with permanent displays and have easy access to this e label screen and its directions on how to get to that screen in the manual. I have heard and seen posts that this too is acceptable in S. Korea but these sources are not official. Any information will be helpful since we are designing the physical label for this OEM right now. Do I have to keep the KC MSIP ID on the physical label?
Thanks, Mark Please be advised that this email may contain confidential information. If you are not the intended recipient, please notify us by email by replying to the sender and delete this message. The sender disclaims that the content of this email constitutes an offer to enter into, or the acceptance of, any agreement; provided that the foregoing does not invalidate the binding effect of any digital or other electronic reproduction of a manual signature that is included in any attachment. - ---------------------------------------------------------------- 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]>
