Pre-compliance testing is a phenomenon that should be a no-brainer, but for lots of reasons—none of them good—it’s not always done. When you’re doing a design that requires RF and you don’t do the testing, you’re really asking for trouble. That goes double for a product that’s going to ship into multiple geographies. To understand how this process should occur, I spoke to Paul Denisowski, a Product Management Engineer at Rohde & Schwarz, on this week’s Embedded Executives podcast.
Pre-compliance testing is a phenomenon that should be a no-brainer, but for lots of reasons—none of them good—it’s not always done. When you’re doing a design that requires RF and you don’t do the testing, you’re really asking for trouble. That goes double for a product that’s going to ship into multiple geographies. To understand how this process should occur, I spoke to Paul Denisowski, a Product Management Engineer at Rohde & Schwarz, on this week’s Embedded Executives podcast.