Choose a country or area to see content specific to your location
White Papers
We often hear questions regarding the differences between pre-compliance and compliance testing. Verifying your designs on your own is called pre-compliance testing. Pre-compliance testing closely simulates the way compliance tests are run – putting your designs against actual compliance test limits. Then, once you are confident in your design, you can take it to a third-party lab for final compliance testing.
Pre-compliance testing is important because it is a low-risk, cost-effective method to ensure your device under test (DUT) will pass final compliance testing. Waiting until the end of the product development cycle for compliance testing is risky, so if you implement pre-compliance testing during development, it will help minimize surprises. For example, by checking your designs for electromagnetic compatibility (EMC), you can help your device pass compliance testing on the first try. If your device fails compliance testing, a simple design tweak might fix the issue, so the only added cost is more time in the compliance lab. However, this best-case scenario rarely happens. Instead, many devices fail compliance testing two or more times, which results in costly rework and a delayed product ship date - something no one wants.
Unlock Content
Sign up for free
*Indicates required field
Thank you.
Your form has been successfully submitted.
Note: Clearing your browser cache will reset your access. To regain access to the content, simply sign up again.
×
Please have a salesperson contact me.
*Indicates required field
Thank you.
A sales representative will contact you soon.