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

    Stability of LTE M1

    Scheduled Pinned Locked Moved GPy
    gpylte m1telstra
    4 Posts 3 Posters 1.2k 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.
    • P Offline
      Paddy
      last edited by Paddy

      Can someone from Pycom give us some guidance on the whether or not the gpy will be able to provide stable LTE-M1 data connectivity. When I say stable I mean stable enough to be deployed to a remote and unattended site for years without needing to be reset. What I'm reading from others is that the experience is currently far from that, i.e. it either doesn't work at all or is quite unreliable. Most of the bad stories seem to be coming from users in the Telstra network in Australia. As Australia is my home and Telstra has by far the best coverage I would really like to get some good news on this front.

      P 1 Reply Last reply Reply Quote 0
      • P Offline
        Paddy
        last edited by

        I think the pycom suite of products and the gpy in particular are a great concept. So I'm really looking forward to hearing pycom let us know that they are aware that LTE connectivity is currently unstable and they have a plan and a timetable to get it sorted. I would much rather program in python than C++ but the particle electron seems to actually work so I might not have a choice.

        J 1 Reply Last reply Reply Quote 0
        • J Offline
          jsh @Paddy
          last edited by

          @paddy

          Agreed. The lack of stability needs to be addressed!

          1 Reply Last reply Reply Quote 0
          • P Offline
            PaulM @Paddy
            last edited by PaulM

            @paddy Any new info on this topic?

            I cannot get my FiPy to keep uploading for more than a few hours - sometimes 20 minutes - without returning endless EAGAIN or EHOSTUNREACH errors on HTTP calls.

            This a huge problem for my remote weather station design. I am going to have to have a fully parallel Raspberry Pi zero to run reliably 24/7 and sample the sensors (defeating low power requirement), since I currently have to shut down and reboot my FiPy in code everytime I start getting the HTTP request errors.

            American Verizon Wireless SIM card through Nimbelink and updated Sequans firmware.

            Dear Pycom: I want to love your product. Please help.

            1 Reply Last reply Reply Quote 1

            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