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

    Multitech Conduit AP 'Not OTAA joine yet...' issue (EU 868)

    Scheduled Pinned Locked Moved LoPy
    lopymultitechlorawan otaa
    7 Posts 2 Posters 840 Views 2 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.
    • B Offline
      bnjroos
      last edited by

      Hi everybody,

      I have updated my LoPy and my Multitech Conduit AP to the last firmwares, however I still get stuck in the 'Not yet joined...' loop, I've checked other topics but none gave me solution.

      Here is my code:

      from network import LoRa
      import time
      import ubinascii
      import pycom
      import socket
      
      # Colors
      off = 0x000000
      red = 0x7f0000
      green = 0x007f00
      blue = 0x00007f
      
      # Turn off hearbeat LED
      pycom.heartbeat(False)
      
      # LoRa region will be set when you update the firmware
      # it does not need to be explicitly stated  
      lora = LoRa(mode=LoRa.LORAWAN, region=LoRa.EU868, device_class=LoRa.CLASS_A, public = False)
      
      # OTAA authentication parameters
      dev_eui = ubinascii.unhexlify('70b3d5499f68dbb1')
      app_eui = ubinascii.unhexlify('af86e54a8730668c')
      app_key = ubinascii.unhexlify('48df5716b92753954f4a0331c68c303a')
      
      # join a network using OTAA (Over the Air Activation)
      lora.join(activation=LoRa.OTAA, auth=(dev_eui, app_eui, app_key), timeout=0)
      
      for i in range(3, 15):
          lora.remove_channel(i)
          print("removed channel: " + str(i))
      lora.add_channel(index=0, frequency=868100000, dr_min=0, dr_max=5)
      print("added channel 868.1Mhz")
      lora.add_channel(index=1, frequency=868300000, dr_min=0, dr_max=5)
      print("added channel 868.3Mhz")
      lora.add_channel(index=2, frequency=868500000, dr_min=0, dr_max=5)
      print("added channel 868.5Mhz")
      lora.add_channel(index=3, frequency=867500000, dr_min=0, dr_max=5)
      print("added channel 867.5Mhz")
      
      pycom.rgbled(0x1f0000)
      
      # Loop until joined
      while not lora.has_joined():
          print('Not OTAA joined yet...')
          pycom.rgbled(0x1f0000)
          time.sleep(0.1)
          pycom.rgbled(off)
          time.sleep(2.4)
      
      
      print('OTAA Joined')
      pycom.rgbled(0x00001f)
      
      s = socket.socket(socket.AF_LORA, socket.SOCK_RAW)
      s.setsockopt(socket.SOL_LORA, socket.SO_DR, 4)
      s.setblocking(True)
      
      i = 0
      while True:
          pycom.rgbled(0x00003f)
          count = s.send(bytes([i % 256]))
          print('Sent %s bytes' % count)
          time.sleep(0.1)
          pycom.rgbled(0x001f00)
          time.sleep(59.9)
          i += 1
      

      And here is my Gateway configuration:
      (multitech EU868

      It seems that the gateway is receiving join requests and that the requests are successful as per this screenshot :
      0_1533006475374_opera_2018-07-31_10-07-33.png

      But I am still stuck in the loop:

      Not OTAA joined yet...
      Not OTAA joined yet...
      Not OTAA joined yet...
      Not OTAA joined yet...
      Not OTAA joined yet...
      Not OTAA joined yet...
      Not OTAA joined yet...
      Not OTAA joined yet...
      Not OTAA joined yet...
      Not OTAA joined yet...
      

      Am I missing something ? Any idea ? Other than that ABP seems to work.

      Thank you in advance,

      Bnjroos

      robert-hhR 1 Reply Last reply Reply Quote 0
      • B Offline
        bnjroos
        last edited by

        I'll just answer myself as it seems that what was pointed out on another post was right, I disabled Join on RX2:
        0_1533007759506_opera_2018-07-31_10-28-55.png

        And now it is working.

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

          @bnjroos The Join delay is 5 seconds, nor one second as shown in the screen dump.

          B 1 Reply Last reply Reply Quote 0
          • B Offline
            bnjroos @robert-hh
            last edited by

            @robert-hh True, I've modified that too, but what is weird is that in the Multitech documentation I found the following for Private Network:

            0_1533021146444_opera_2018-07-31_14-11-29.png

            But indeed I've modified it to 5 at the same time i checked Disable Join Rx2 and it seems to work.

            Now I need to find out how to disable join Rx2 on loraserver.io !

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

              @bnjroos The PyCom software if configured for a 5 second RX1 delay for join. I could not test join at the RX2 window. loriot.io can be configured to use RX1 or RX2, but it seems to use RX1 in any case. The configuration only affects the other dowlink messages.

              B 1 Reply Last reply Reply Quote 0
              • B Offline
                bnjroos @robert-hh
                last edited by

                @robert-hh Yeah that is what came to my mind afterwards when I read "Must match Dot settings", that it was tied to the node hardware, however it is specified in the LoRaWAN regional parameters if I am not mistaken ?

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

                  @bnjroos Yes, the RX1 and RX2 delay are specified in the LORaWAN regional settings. I did not look that up for every region, but the ones I recall use 5 and 6 seconds for OTAA join, and 1 and 2 seconds for other downlink messages as default.

                  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