Sujet : Re: EMC compliance question
De : blockedofcourse (at) *nospam* foo.invalid (Don Y)
Groupes : sci.electronics.designDate : 12. Oct 2024, 00:46:00
Autres entêtes
Organisation : A noiseless patient Spider
Message-ID : <vecdc6$3rk2m$1@dont-email.me>
References : 1 2 3 4
User-Agent : Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.2.2
On 10/11/2024 4:31 PM, legg wrote:
A wart used in an EMC certification becomes part of it. Hence
mrfs listing and retailing part numbers for suitable use.
But that's true of anything that you end up putting "in the box".
Worth considering if you let folks open your device and
replace things that *they* think are FRUs (memory, CPU, etc.)
If one of your customers makes such an (inobvious?) modification
and pisses off a local Ham who then files an informal complaint,
etc. It's relatively easy to piss through the monies you would
have spent on "certification" trying to diagnose and defend
*your* product.
[I had a neighbor visit me one evening because of all of the
hash coming from my office, close to the street. "Nothing funny,
here... everything is listed -- just noisey!"]
Warts can be (and are) listed independently, to reduce
potential testing and deployment gliches. A listed
wart doesn't guarantee radiated compliance, only facilitates
conducted performance on that one, main, port.