Why I Stopped Ignoring Signal Purity (and You Should Too)

That "Minor" Distortion That Cost Us a Week

Last quarter, our lead engineer walked into my office with a problem. A prototype they'd been working on for a month—a new communication module—was failing in testing. The design looked solid on paper. The simulation said it should work. But real-world results were terrible.

He handed me a report. "Harmonic distortion," he said. "The signal generator's output isn't clean enough."

I'm not an RF engineer, so I can't speak to the technical specifics of phase noise or intermodulation. What I can tell you from a procurement perspective is this: we'd bought a budget signal generator to stay within project costs (this was back in 2024), used it for initial validation, and that decision added two weeks of rework and thousands in emergency shipping for replacement parts. The bottom line? We could have bought the higher-end unit twice over with what we wasted.

The Deeper Problem: What You Don't See Costs You

On the surface, the problem was a distorted signal. But the real issue wasn't the instrument—it was our buying criteria. We optimized for the wrong thing.

When I took over purchasing in 2020, I learned quickly that the lowest price on a spec sheet is rarely the lowest total cost. But this was different. We bought a device that met the specs on paper—same frequency range, similar output power—but didn't account for how it delivered that signal. The budget unit had higher harmonic content. It polluted the measurements.

A $30,000 prototype failed because we saved $15,000 on a test instrument. (Ugh.)

The thing is, this gets into a gray area. The vendor's datasheet didn't lie—the specs were accurate. But the practical performance in our application was different. I've never fully understood why this happens so consistently with cheaper test gear. My best guess is that manufacturers optimize for the numbers a marketer will highlight, not the real-world behavior an engineer will experience.

The Cascade Effect of Bad Data

Here's what a lot of people don't realize: a signal generator isn't just a tool that produces a waveform. It's the starting point of a chain. Every test you run, every measurement you take, is only as good as that first signal. If your source has distortion, your results are built on a lie.

Say you're using an impedance analyzer like the keysight e4990a manual describes—you're looking at component behavior over frequency. If your signal source has harmonics, you're measuring those harmonics, not your device under test. You'll draw wrong conclusions. You'll tune your design to compensate for ghost problems.

Trust me on this one. We had an engineer spend three days optimizing a filter for a harmonic that didn't actually exist in our target environment. Three days. Because the test signal was dirty.

The Invisible Price Tag of "Good Enough"

Let me put this in terms I understand: money. The cost of a mediocre test setup is real, and it shows up in places you don't immediately track.

  • Rework costs. Failed prototypes mean redoing layouts, ordering parts again, re-burning time. Processing 60-80 orders for reworking parts annually adds up fast.
  • Engineering hours. Every hour a senior engineer spends debugging a measurement artifact is an hour not spent on actual product development. That can be $150-200/hour of salary you're burning.
  • Opportunity cost. When products ship late because of test failures, you lose market window. In our 2024 vendor consolidation project, we realized that unreliable testing from budget equipment had delayed two product launches by an average of 2.5 weeks each. That's real revenue you don't get back.
  • Brand perception. This one is subtle but important. If you're a company that makes precision measurement equipment, you can't validate it with sloppy test gear. It sends the wrong message. The vendor who couldn't provide proper calibration documentation cost us $2,400 in rejected expenses—but the real damage was to our reputation when a client audited our lab and noted the inconsistency.

The client didn't complain publicly. They just stopped giving us the high-precision contracts. That vendor consolidation project? I learned that reliability was non-negotiable for our brand.

So What Actually Changes?

After that experience—when I had to explain to my VP why our flagship prototype was delayed—I changed my approach.

Now, when we spec test equipment, we don't just match frequency range. We look at signal purity. Specifically:

  • Harmonic distortion specs (like what you'd find on a keysight 50 ghz signal generator datasheet).
  • Phase noise levels.
  • Spurious content.

For our RF team, we standardized on instruments that deliver clean signals out of the box. Not the cheapest option—but the one where the first measurement is the right one. For instance, when evaluating test gear for 5G testing, we now prioritize instruments with proven spectral purity, avoiding the temptation to oversimplify comparisons like transparent smartphone vs broadcom reference designs.

To be clear, I still care about cost. I report to operations and finance. But now I calculate the cost of not having a quality measurement standard, not just the price of the instrument. When I factored in the rework costs from our "good enough" signal generator, the payback period for a premium unit like a keysight signal analyzer was under six months.

"The value of guaranteed signal fidelity isn't the precision—it's the certainty. Knowing that your test results reflect your design, not your instrument, is often worth more than a lower price with 'estimated' performance."

I have mixed feelings about the budget equipment world. On one hand, it democratizes access to testing. On the other, it can create more problems than it solves for professional teams. Part of me wants to save money. Another part remembers that expensive week of rework. I compromise by investing in core reference equipment and using budget gear only for non-critical benchtop education.

The bottom line, if you manage a test lab or procurement for an engineering team: pay attention to signal purity. It's not just a spec—it's the difference between data you trust and data that costs you time, money and credibility.

Leave a Reply