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

    LOPY1.0 with new firmware unable to connect to TTN

    Scheduled Pinned Locked Moved LoPy
    lopyttnfirmware update
    8 Posts 3 Posters 1.5k 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.
    • philwilkinsonP Offline
      philwilkinson
      last edited by

      I have a Lopy 1.0 that has been running fine connecting to a nearby gateway and publishing through The Things Network.
      Then I upgraded to the latest firmware (1.16.0.b1) and I cannot connect anymore.
      I have run the simple OTAA code suggested and have passed the regional setting.
      lora = LoRa(mode=LoRa.LORAWAN, region=LoRa.AU915)

      Any ideas of how to fault find this problem?

      I have a strong suspicion it is related to the new firmware regional setting. I am in Australia and chose that selection on firmware download, however I have had problems selecting this regional frequency before. Have other users in Australia/New Zealand found the transition OK?

      robert-hhR 1 Reply Last reply Reply Quote 0
      • robert-hhR Offline
        robert-hh @philwilkinson
        last edited by robert-hh

        @philwilkinson That happens in the EU too. As far as I could tell, it's a timing problem. The receive window in the Firmware is set to 20 ms (actually I've seen a little bit longer times), which is what the standard recommends, but is starts up to 30 ms too early, with a variation of +/- 20ms. Then, the node misses the joins response message. I changed the firmware to extend the receive window to 200ms. Then it works better. But I hope that Pycom will fix that in a more decent way
        Note 1: The standard talks about a timing error of +/- 20µs. The xxPy devices have timing error of at least +/- 20ms.
        Note 2: I had the impression than v1.15.0.b1 works better.

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

          SIM test card for internet of things, open SDR LTE platform.

          philwilkinsonP 1 Reply Last reply Reply Quote 0
          • philwilkinsonP Offline
            philwilkinson @pistol_bbq
            last edited by

            @pistol_bbq . I don't understand a word you have written. What do you suggest i do?

            robert-hhR P 2 Replies Last reply Reply Quote 0
            • robert-hhR Offline
              robert-hh @philwilkinson
              last edited by

              @philwilkinson Unless you modify the sources, wait, or go back to 1.15.0.b1

              1 Reply Last reply Reply Quote 0
              • P Offline
                pistol_bbq @philwilkinson
                last edited by

                @philwilkinson Some of the questions perplexed me, and I had to think about it first of myself.

                1 Reply Last reply Reply Quote 0
                • philwilkinsonP Offline
                  philwilkinson
                  last edited by

                  please can someone from Pycom respond to this post.

                  If this is a known issue with the 1.16.0.b1 firmware, please can you inform the community and let us all revert to something that works, while the bugs get dealt with.

                  Also,, repeating my request to those in Australia/NZ region. Has anyone updated their firmware and been able to connect with OTAA? If you have then I know it is my board.
                  thanks,
                  Phil

                  1 Reply Last reply Reply Quote 0
                  • philwilkinsonP Offline
                    philwilkinson
                    last edited by

                    anyone reading this.
                    please refer to:

                    Problem joining TTN in Australia with OTAA using a LoPy 4

                    post on the LoPy section of the forum.
                    The solution to this issue seems to be to restrict the channels of the AU915 regional settings.

                    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