<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[1 of 5 FiPys connect to NB-LTE]]></title><description><![CDATA[<p dir="auto">Hello!</p>
<p dir="auto">I bought 5 FiPys with expansion boards and antennas to build some IoT devices. After a few days of trial and error I managed to get 1 of the devices connected to our lab's NB-LTE network but the other 4 identical devices with same firmware, SIM card and code can't even find the network. I tried switching antennas and expansion boards, but the only working FiPy connects with any combination of parts while none of the others do.</p>
<p dir="auto">Currently the functional part of my code looks like this (band, earfcn, apn hidden):</p>
<pre><code>commands = ['AT+CFUN=0',
            'AT+CFUN=1',
            'AT!=&quot;clearscanconfig&quot;',
            'AT!=&quot;addscanfreq band=BAND dl-earfcn=EARFCN&quot;',
            'AT+CGDCONT=1,&quot;IP&quot;,&quot;APN NAME&quot;']

lte = LTE()

for command in commands:
    print(lte.send_at_cmd(command))
    time.sleep(1)

while not lte.isattached():
    time.sleep(1)

lte.connect()
</code></pre>
<p dir="auto">Showphy shows randomly synchro state as CELL_SEARCH or FAST_SCAN for the devices with connection problems but the signal stays at 99,99 for &gt;15 minutes with no change.</p>
<p dir="auto">FiPy firmware: 1.18.0.r1<br />
Sequans firmware: FIPY_GPY_NB1_37781</p>
<p dir="auto">What could be the cause for such a weird problem? I assume the modem saves entered settings even through power cycles, but reloading the firmware should clear the settings, shouldn't it?</p>
]]></description><link>https://forum.pycom.io/topic/3607/1-of-5-fipys-connect-to-nb-lte</link><generator>RSS for Node</generator><lastBuildDate>Tue, 18 Aug 2026 17:18:35 GMT</lastBuildDate><atom:link href="https://forum.pycom.io/topic/3607.rss" rel="self" type="application/rss+xml"/><pubDate>Tue, 07 Aug 2018 08:25:35 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to 1 of 5 FiPys connect to NB-LTE on Wed, 15 Aug 2018 08:09:06 GMT]]></title><description><![CDATA[<p dir="auto">Hello!</p>
<p dir="auto">I bought 5 FiPys with expansion boards and antennas to build some IoT devices. After a few days of trial and error I managed to get 1 of the devices connected to our lab's NB-LTE network but the other 4 identical devices with same firmware, SIM card and code can't even find the network. I tried switching antennas and expansion boards, but the only working FiPy connects with any combination of parts while none of the others do.</p>
<p dir="auto">Currently the functional part of my code looks like this (band, earfcn, apn hidden):</p>
<pre><code>commands = ['AT+CFUN=0',
            'AT+CFUN=1',
            'AT!=&quot;clearscanconfig&quot;',
            'AT!=&quot;addscanfreq band=BAND dl-earfcn=EARFCN&quot;',
            'AT+CGDCONT=1,&quot;IP&quot;,&quot;APN NAME&quot;']

lte = LTE()

for command in commands:
    print(lte.send_at_cmd(command))
    time.sleep(1)

while not lte.isattached():
    time.sleep(1)

lte.connect()
</code></pre>
<p dir="auto">Showphy shows randomly synchro state as CELL_SEARCH or FAST_SCAN for the devices with connection problems but the signal stays at 99,99 for &gt;15 minutes with no change.</p>
<p dir="auto">FiPy firmware: 1.18.0.r1<br />
Sequans firmware: FIPY_GPY_NB1_37781</p>
<p dir="auto">What could be the cause for such a weird problem? I assume the modem saves entered settings even through power cycles, but reloading the firmware should clear the settings, shouldn't it?</p>
]]></description><link>https://forum.pycom.io/post/21373</link><guid isPermaLink="true">https://forum.pycom.io/post/21373</guid><dc:creator><![CDATA[cnopicilin]]></dc:creator><pubDate>Wed, 15 Aug 2018 08:09:06 GMT</pubDate></item><item><title><![CDATA[Reply to 1 of 5 FiPys connect to NB-LTE on Wed, 08 Aug 2018 06:55:36 GMT]]></title><description><![CDATA[<p dir="auto">I managed to get 4 of the 5 devices to connect yesterday, but this morning one of the previously working ones refuses to find any signal at all. I didn't make any modifications, so the FiPys might just be extremely unreliable.</p>
]]></description><link>https://forum.pycom.io/post/21392</link><guid isPermaLink="true">https://forum.pycom.io/post/21392</guid><dc:creator><![CDATA[cnopicilin]]></dc:creator><pubDate>Wed, 08 Aug 2018 06:55:36 GMT</pubDate></item><item><title><![CDATA[Reply to 1 of 5 FiPys connect to NB-LTE on Wed, 15 Aug 2018 06:45:26 GMT]]></title><description><![CDATA[<p dir="auto">One of the working devices dropped connection the same day it finally connected and after a week of testing I haven't been able to reconnect it. It briefly found a signal two days ago but wasn't able to attach and has been silent since.</p>
<p dir="auto">No idea what could be the cause, are there some commands outside of the LTE example on docs I should try? Also the 'AT!=&quot;zsp0:npc 1&quot;' always returns &quot;command unknown&quot;.</p>
]]></description><link>https://forum.pycom.io/post/21558</link><guid isPermaLink="true">https://forum.pycom.io/post/21558</guid><dc:creator><![CDATA[cnopicilin]]></dc:creator><pubDate>Wed, 15 Aug 2018 06:45:26 GMT</pubDate></item><item><title><![CDATA[Reply to 1 of 5 FiPys connect to NB-LTE on Wed, 22 Aug 2018 07:27:28 GMT]]></title><description><![CDATA[<p dir="auto">After &gt;18 hours of connecting the last device finally started working with the network. I have no idea what happened, because I made no changes to anything.</p>
<p dir="auto">The only thing I can say is that the commands I have in the first post should be enough and be patient with it as it can take &gt;24 hours to find signal and connect.</p>
]]></description><link>https://forum.pycom.io/post/21713</link><guid isPermaLink="true">https://forum.pycom.io/post/21713</guid><dc:creator><![CDATA[cnopicilin]]></dc:creator><pubDate>Wed, 22 Aug 2018 07:27:28 GMT</pubDate></item></channel></rss>