Welcome to the Pycom forum Forum
    • \[\[global:header.categories\]\]
    • \[\[global:header.recent\]\]
    • \[\[global:header.tags\]\]
    • \[\[global:header.popular\]\]
    • Login

    Explore Pybytes | Official Documentation | Report a Firmware Bug/Issue | GitHub

    LTE Cat M1 unable to connect

    Scheduled Pinned Locked Moved FiPy
    fipylte fipy sim
    3 Posts 3 Posters 1.4k Views 3 Watching
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • A Offline
      andrey.gvrd
      last edited by

      I'm using this example, but lte.isconnected() (ran after lte.connect()) always returns False.

      I'm using a SIM card from hologram which is supposed to work with US LTE Cat M1 networks.

      Any pointers?

      B 1 Reply Last reply Reply Quote 0
      • B Offline
        brotherdust @andrey.gvrd
        last edited by

        @andrey-gvrd see: https://forum.pycom.io/topic/2343/set-cellular-access-point-name-apn/38

        1 Reply Last reply Reply Quote 1
        • J Offline
          joeg2000
          last edited by

          I'm not testing in the US but I use these workarounds while we wait for stable SW.

          1. First try it with an IOT sim card from your operator and confirm they have CAT-M coverage in your area
          2. Check the SIM is inserted correctly. The sim-card holder is low cost and may not provide a good connection. In the current firmware, there is no error check on the SIM card so the lte.connect() response will hang without a warning.
            3.Use a better antenna than the one supplied by PyCom. The current firmware does not include any status of the radio link or attach errors. For your initial testing, make sure you are in good coverage - preferably with line-of-sight to your providers antenna. I've found connectivity can be reliable in good RF. ( the CAT-M coverage extension may not be functioning correctly in the current SW ?..)
          3. There appears to be a bug in the current firmware, or sequans chipset. It seems to get locked into a state that will never connect even after soft resets. This may be due to a fault in the band selection. A full power reset is often the only way to achieve a successful lte.connect().
          1 Reply Last reply Reply Quote 0

          Hello! It looks like you're interested in this conversation, but you don't have an account yet.

          Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

          With your input, this post could be even better 💗

          Register Login
          • 1 / 1
          • First post
            Last post

          Pycom on Twitter

          Pycom