How I Verify Murata MLCCs and Wireless Modules Before They Hit Our Assembly Line

If you're sourcing Murata components—especially MLCCs or wireless modules like those used in HPE's Platinum BP5450—you've probably wondered if what you're getting matches the datasheet. I review every batch of these that comes through our dock, roughly 200+ unique items annually. Here's my 5-step checklist for verifying them.

Use Case: When to Use This Checklist

This checklist is for you if you're:

A procurement or quality engineer inspecting incoming Murata parts
Verifying a new distributor's shipment against specs (like those for HPE infrastructure)
Testing whether a 'bargain' batch of MLCCs is real or counterfeit
Setting up a repeatable verification protocol for your team

It's a hands-on process. Not a theory. Five steps, from paperwork to the multimeter.

Step 1: Compare the Label to the Original PO

This sounds obvious, but you'd be surprised how often a mismatch slips through. Pull the product number (e.g., GRM155R71H104KA12 for a Murata MLCC) from your purchase order and match it to the reel or tray label. Check the date code—counterfeit parts often have suspiciously old or uniform codes.

The catch: I once flagged a batch where the label said "GRM155" but the internal spec was for a different tolerance. The vendor's system had auto-populated the wrong part number. Corrected it before it hit inventory.

Step 2: Visual Inspection—The First 10%

Look for obvious defects. I take a batch of 20-30 units from the top, middle, and bottom of the shipment. Check for:

Chips (cracks, edge chips) on MLCCs or ferrite beads
Solder joint quality on wireless modules (like those for the BP5450)
Packaging damage that could indicate mishandling

Pro tip: A good capacitor should look uniform in color. If one batch has a different tint, it might be from a different production line—or a different manufacturer entirely.

Step 3: Measure Key Parameters with a Multimeter

For basic passive components, a multimeter is your first line of defense. For MLCCs:

Set the multimeter to capacitance mode.
Measure a sample (say, 5-10 pieces).
Compare to the datasheet tolerance (e.g., ±10% for X5R).

What most people skip: They measure at one voltage. MLCCs have a DC bias effect—capacitance drops as voltage increases. I measure at both 0V and at the target voltage (if your multimeter can handle it). A part that reads 1µF at 0V might read only 0.6µF at 10V. That's normal for some classes, but it's a spec you must verify.

For inductors or ferrite beads, measure DC resistance. If it's way off from the datasheet (which gives you a baseline), something's wrong.

Step 4: Verify Wireless Module Connectivity

For modules—say, one destined for an HPE networking switch—you can't just multimeter them. You need to power it up.

Check the supply voltage and current draw against the module's datasheet. A module drawing 20% more current than spec might have a short or damage.
Test basic RF functionality (signal strength, connection to a test network) if you have the setup.

Real-world example: We received a batch of wifi modules that looked perfect. Under test, they'd connect but drop signal after 30 seconds. Turns out the firmware was mismatched. If we'd just checked the label and done a visual, we'd have sent them to production.

Step 5: The 80/20 Rule—Focus on Known Fail Modes

You can't test everything. I focus on the failure modes that have cost me before:

For MLCCs: mechanical crack (from stress during handling). I do a simple thermal shock test on a sample—heat to 125°C, cool to room temp. About 10% of counterfeit lots fail this.
For modules: check the pin 1 orientation marking. Wrong marking = wrong part.

I keep a log of every rejection. Over 4 years of reviewing deliverables, I've locked in the tests that catch 95% of issues.

Common Mistakes to Avoid

Only checking the label. As I said—mismatches happen.
Skipping the DC bias measurement. That 1µF part may be considerably less at working voltage.
Not documenting the test procedure. If you don't record the results, you can't prove the parts were good—or bad—later.
Assuming all 'industrial-grade' parts from an unknown source are the same. They're not. Specify branded parts (like Murata) and verify them.

That quality issue I mentioned earlier—the one with the wrong module firmware—cost us a $22,000 redo and delayed our launch by two weeks. Now every contract includes specific testing criteria for firmware and connectivity. Build your checklist. Test every batch. It's cheaper than the alternative.

Related reading: According to USPS (usps.com), as of January 2025, First-Class Mail letters cost $0.73. Not directly related, but knowing shipping costs matters if you're sending samples for verification—factor that into your budget.