<![CDATA[LTE-M on 800MHz?]]>Does the current FiPy firmware support LTE-M in the 800MHz band?

]]>https://forum.pycom.io/topic/3033/lte-m-on-800mhzRSS for NodeMon, 13 Apr 2026 07:55:58 GMTThu, 12 Apr 2018 21:42:40 GMT60<![CDATA[Reply to LTE-M on 800MHz? on Thu, 12 Apr 2018 21:42:40 GMT]]>Does the current FiPy firmware support LTE-M in the 800MHz band?

]]>https://forum.pycom.io/post/18421https://forum.pycom.io/post/18421Thu, 12 Apr 2018 21:42:40 GMT<![CDATA[Reply to LTE-M on 800MHz? on Fri, 13 Apr 2018 08:07:59 GMT]]>Hi @kersing,

There isn't proper support for Band 20 yet, we need to add the band manually via AT commands and maybe some more things.

Is this to support KPN? Our team in Eindhoven is already testing it, hopefully we'll have it soon.

]]>https://forum.pycom.io/post/18435https://forum.pycom.io/post/18435Fri, 13 Apr 2018 08:07:59 GMT<![CDATA[Reply to LTE-M on 800MHz? on Fri, 20 Apr 2018 22:47:54 GMT]]>Hi @jmarcelino ,

I'm interested since you're specifically asking about supporting KPN. I'm trying to get LTE-M to work on a KPN network, but am unable to do so. Just after the attach() call I can execute AT+COPS=?, and after a long time (30s?) it'll show KPN. However, directly after it'll give a +CEREG: 4 (= unknown (e.g. out of E-UTRAN coverage)). After that it's unable to find any networks when using AT+COPS=?.

If you managed to get KPN to work, I'd love to hear what AT commands you used.

]]>https://forum.pycom.io/post/18867https://forum.pycom.io/post/18867Fri, 20 Apr 2018 22:47:54 GMT