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

    Lora: Documentation vs. Example code regards OTAA

    Scheduled Pinned Locked Moved LoPy
    loraotaa
    23 Posts 5 Posters 6.5k Views 5 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.
    • robert-hhR Offline
      robert-hh @jmarcelino
      last edited by

      @jmarcelino In my tests so far, neither using the 2-tuple or the 3-tuple made OTAA succeed. But I'm still trying more this night.

      J 1 Reply Last reply Reply Quote 0
      • J Offline
        jmarcelino @robert-hh
        last edited by

        I think the problem you're having with OTAA is related to you not receiving downlinks properly https://forum.pycom.io/topic/1254/ttn-otaa-join-acknowledgement-not-being-received/13 and not the Dev EUI

        robert-hhR S 3 Replies Last reply Reply Quote 0
        • robert-hhR Offline
          robert-hh @jmarcelino
          last edited by

          @jmarcelino Agreed, because that's what is see with ABP mode too.

          1 Reply Last reply Reply Quote 0
          • S Offline
            ssmith @jmarcelino
            last edited by

            @jmarcelino Since updating to 1.16 I'm getting this error when trying to connect.

            [   388.642] Received packet: {"rxpk": [{"data": "AFlERE/vvq3e6FJQ/v+krjC7ifKetjw=", "time": "2018-02-19T13:38:40.120571Z", "chan": 0, "tmst": 388895160, "stat": 1, "modu": "LORA", "lsnr": 5.0, "rssi": -17, "rfch": 0, "codr": "4/5", "freq": 918.9, "datr": "SF7BW125", "size": 23}]}
            [   388.675] Push ack
            [   393.694] Pull rsp
            Unhandled exception in callback handler
            Traceback (most recent call last):
              File "lorawan_nanogateway.py", line 386, in <lambda>
              File "lorawan_nanogateway.py", line 345, in _send_down_link
            ValueError: frequency 923300000 out of range
            
            J 1 Reply Last reply Reply Quote 0
            • J Offline
              jmarcelino @ssmith
              last edited by jmarcelino

              @ssmith
              Which region are you in please and what frequency is LORA_FREQUENCY set to in config.py?

              This error seems related to the recent LoRa region changes in 1.16 but it's strange that the nanogateway is able to listen on the correct frequency but not transmit on 923300000.

              S 1 Reply Last reply Reply Quote 0
              • S Offline
                ssmith @jmarcelino
                last edited by ssmith

                @jmarcelino, region=LoRa.US915,. This worked fine with 1.15. and here is lora config

                lora.init(mode=LoRa.LORA, frequency=918900000, power_mode=LoRa.ALWAYS_ON, tx_power=20, bandwidth=LoRa.BW_125KHZ, sf=7,
                              preamble=8, coding_rate=LoRa.CODING_4_8, tx_iq=False, rx_iq=False)
                
                J 1 Reply Last reply Reply Quote 0
                • J Offline
                  jmarcelino @ssmith
                  last edited by

                  @ssmith
                  Could you add region=LoRa.US915 as a parameter in both lora.init() please?

                  S 2 Replies Last reply Reply Quote 0
                  • S Offline
                    ssmith @jmarcelino
                    last edited by ssmith

                    @jmarcelino It's there, that was a different config file from my previous test just to show the frequency. Here's the config from the nano_gateway file.

                            self.lora = LoRa(
                                mode=LoRa.LORA,
                                region=LoRa.US915,
                                frequency=self.frequency,
                                bandwidth=self.bw,
                                sf=self.sf,
                                preamble=8,
                                coding_rate=LoRa.CODING_4_5,
                                tx_iq=True
                            )
                    
                    1 Reply Last reply Reply Quote 0
                    • S Offline
                      ssmith @jmarcelino
                      last edited by

                      @jmarcelino I also tried AU915 with the same result. I'll try EU next. I assume with the generic FW now that it should accept it.

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

                        @jmarcelino Cannot try more, I think I expired my downlink message quota (of 10?) for the day.

                        S 1 Reply Last reply Reply Quote 0
                        • S Offline
                          ssmith @robert-hh
                          last edited by

                          @robert-hh Are you going to TTN? I've sent thousands of messages there in a day during testing.

                          robert-hhR 1 Reply Last reply Reply Quote 0
                          • S Offline
                            ssmith @ssmith
                            last edited by ssmith

                            @jmarcelino Wasn't able to get EU868 to work with LoRaWAN. Gave me a frequency error. I was able to set it up and send raw LoRa between 2 LoPy4's at both 868 and 915 bands without changing the FW. Looks like it is in the LoRaWAN stack.

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

                              @ssmith Yes, I'm using TTN. As far as I can could read, the limit is for downlink messages, from TTN to the node. Uplink, to TTN, I did not experience any limit.

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

                                @ssmith Besides that, no luck. Simple device-to-device works, the power getting out of the antenna looks similar, with the FiPy a little bit (25% = 2 dB) stronger. But that may be within the setup-variation.

                                1 Reply Last reply Reply Quote 0
                                • A Offline
                                  asavvin
                                  last edited by

                                  Hello!
                                  I am having issue with activating using method otaa lopy with ttn gateway fot US915.
                                  whats correct code i should use I searched a lot of topics over weekend and could not find correct code.
                                  Thank you

                                  Same time using ttn node US915 with ttn gateway activation worked as shown.

                                  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
                                  • 2
                                  • 1 / 2
                                  • First post
                                    Last post

                                  Pycom on Twitter

                                  Pycom