<?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>Troubleshooting test basestation connection issue during certification</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/96653/troubleshooting-test-basestation-connection-issue-during-certification</link><description>Dear Nordic Team, We have a custom device based on our beloved nRF9160 SiP. For one of our partners, certifying our device is mandatory. We took part in radio signaling testing (part of a RED certification in Germany) but our device failed to connect</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 14 Feb 2023 12:21:57 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/96653/troubleshooting-test-basestation-connection-issue-during-certification" /><item><title>RE: Troubleshooting test basestation connection issue during certification</title><link>https://devzone.nordicsemi.com/thread/409841?ContentTypeID=1</link><pubDate>Tue, 14 Feb 2023 12:21:57 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:7a8dae0a-b359-413c-8ead-d35e7a660e8d</guid><dc:creator>H&amp;#229;kon Alseth</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Unfortunately, the modem traces (*.bin files) were empty, so I&amp;#39;ll have to give directions based on the .txt logs.&lt;/p&gt;
&lt;p&gt;at_client_1.txt shows:&lt;/p&gt;
&lt;p&gt;&lt;pre class="ui-code" data-mode="text"&gt;...
+CEREG: 2,&amp;quot;C364&amp;quot;,&amp;quot;01E15B08&amp;quot;,9
+CNEC_EMM: 15
+CEREG: 2,&amp;quot;C364&amp;quot;,&amp;quot;01E15B08&amp;quot;,9,0,15
...&lt;/pre&gt;&lt;/p&gt;
&lt;p&gt;EMM return code of 15 means that you&amp;#39;re not allowed to connect to the specific network:&lt;/p&gt;
&lt;p&gt;&lt;pre class="ui-code" data-mode="text"&gt;Cause #15 – No suitable cells in tracking area

      This EMM cause is sent to the UE if it requests service, or if the network initiates a detach request, in a tracking area where the UE, by subscription, is not allowed to operate, but when it should find another allowed tracking area or location area in the same PLMN or an equivalent PLMN.

NOTE 3:  Cause #15 and cause #12 differ in the fact that cause #12 does not trigger the UE to search for another allowed tracking area on the same PLMN.&lt;/pre&gt;&lt;/p&gt;
&lt;p&gt;The CellID here is different from what is shown in the other logs:&lt;/p&gt;
&lt;p&gt;&lt;pre class="ui-code" data-mode="text"&gt;+CEREG: 2,&amp;quot;C2FA&amp;quot;,&amp;quot;002E7F67&amp;quot;,9
▸[MODEM] Searching for networks
▸[MODEM] LTE cell changed: Cell ID: 3047271, Tracking area: 49914
▸[MODEM] LTE mode updated: NB-IoT&lt;/pre&gt;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;This indicates that the nRF9160 is trying to connect to actual live networks in your area, and not the tester network.&lt;/p&gt;
&lt;p&gt;Without any logs from the CMW-500, it is hard to say what specifically is wrong here, but it all points to incorrect configuration on the tester itself.&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Kind regards,&lt;/p&gt;
&lt;p&gt;Håkon&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>