<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>ble on toorun.dev</title><link>https://toorun.dev/tags/ble/</link><description>Recent content in ble on toorun.dev</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Wed, 15 Jul 2026 09:00:00 +0000</lastBuildDate><atom:link href="https://toorun.dev/tags/ble/index.xml" rel="self" type="application/rss+xml"/><item><title>Receiver Blocking in RF Testing: Practical Guide for Embedded Wi-Fi and BLE Engineers</title><link>https://toorun.dev/posts/receiver-blocking-rf-testing-wifi-ble/</link><pubDate>Wed, 15 Jul 2026 09:00:00 +0000</pubDate><guid>https://toorun.dev/posts/receiver-blocking-rf-testing-wifi-ble/</guid><description>Receiver Blocking in RF Testing Receiver blocking becomes important the moment a product works in a quiet lab but fails in a crowded RF environment.
In real deployments, your receiver must decode a wanted signal while strong unwanted signals are present nearby in frequency. Receiver blocking evaluates that resilience.
What Receiver Blocking Actually Means Receiver blocking is the receiver&amp;rsquo;s ability to keep working when two RF signals are present:
A wanted signal: the one your device should decode A blocking signal: an unwanted interferer that is intentionally made strong During a blocking test, the wanted signal is usually set near the receiver threshold, while the blocking signal is applied at specific offset frequencies defined by the applicable standard.</description></item></channel></rss>