<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://devzone.nordicsemi.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Radiated immunity test problem</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/40945/radiated-immunity-test-problem</link><description>I’ve provided radiated immunity test for our devise based on the nRF52832. 
 The test has been provided by electromagnetic pulse with a power of 10V/m ,duration 1sec and the same test with a duration 3sec, the frequency range from 2GHz to 2.7GHz with</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 27 Nov 2018 14:59:43 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/40945/radiated-immunity-test-problem" /><item><title>RE: Radiated immunity test problem</title><link>https://devzone.nordicsemi.com/thread/159272?ContentTypeID=1</link><pubDate>Tue, 27 Nov 2018 14:59:43 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:8f5d596f-c578-4eb9-9fd0-f3d968904fde</guid><dc:creator>AmbystomaLabs</dc:creator><description>&lt;p&gt;It is unlikely the burst is causing processor issues.&amp;nbsp; Most likely is the low frequency burst is just aliasing inband in the receiver.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;With most ETSI (RED) testing you are allowed to just spec how you fail during immunity and as long as your public documentation (ie, user manual) declares it that is sufficient to pass.&amp;nbsp; However, you mentioned a medical home use requirement so you may not get this luxury to just spec and it call it a day.&lt;/p&gt;
&lt;p&gt;If it truly is aliasing in-band your only solution will be a tighter bandpass filter on the front end to remove the&amp;nbsp;2.165-2.345GHz band. If BLE allows it, you could also just map out the problematic frequencies in software.&amp;nbsp; As long as they aren&amp;#39;t associated with advertising channels, the link won&amp;#39;t care if&amp;nbsp;it can&amp;#39;t use 5 channels. Essentially for every frequency you fail on there should be a corresponding &amp;#39;bad&amp;#39; ble channel.&lt;/p&gt;
&lt;p&gt;Another thought is to look at how the CCA routine is running. Offhand I don&amp;#39;t know how often ble determines channel assessment but this could be a way to mitigate the problem.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>