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

    New firmware release 1.6.7.b1 (LoRaWAN Nano Gateway with TTN example!!)

    Scheduled Pinned Locked Moved Announcements & News
    firmware
    113 Posts 34 Posters 88.5k Views 32 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.
    • R Offline
      rvandam
      last edited by

      I have a setup with a node and a nano gateway with the latest default script from Github. The data is received in the TTN backend, so that part is working.

      I want to update the date and time on the nodes over Lora (no wifi) I discovered that no rx data is received on the node. Could you give me a hint how to configure the gateway to send back the current time to the node?

      J 1 Reply Last reply Reply Quote 0
      • J Offline
        jmarcelino @rvandam
        last edited by jmarcelino

        @rvandam
        In LoRaWAN with TTN (Class A) you must send data from the node in order to receive any messages back.

        But if you queue a downlink with TTN you should receive it in your node - for example with data = s.recv(64) - once you've done an uplink (an s.send(...) ).

        R 1 Reply Last reply Reply Quote 0
        • R Offline
          rvandam @jmarcelino
          last edited by

          @jmarcelino thank you for your reply!

          When I add some data in the downlink field in the TTN backend, this data is received by the node. This is already one more step forward :-)

          Should I see the gateway as a "dumb" packet forwarder, and do the logic on the node and the TTN side?

          J 1 Reply Last reply Reply Quote 0
          • J Offline
            jmarcelino @rvandam
            last edited by

            @rvandam
            Glad you managed to receive data.

            Yes, that's exactly what LoRaWAN gateways are :) They don't send or receive anything on their own, that's the job for the network server.

            R 1 Reply Last reply Reply Quote 0
            • R Offline
              rvandam @jmarcelino
              last edited by

              @jmarcelino thank you again. This makes much sense. I was looking on the wrong end.

              1 Reply Last reply Reply Quote 0
              • V Offline
                Vicky_
                last edited by

                @jmarcelino I live in Malaysia. May i know what frequency should i use? i have tried to search but i couldn't find.

                Thanks.

                J 1 Reply Last reply Reply Quote 0
                • J Offline
                  jmarcelino @Vicky_
                  last edited by

                  @vicky_

                  Malaysia uses the AS923 plan:

                  https://www.thethingsnetwork.org/wiki/LoRaWAN/Frequencies/Frequency-Plans#lorawan-frequencies_as923

                  1 Reply Last reply Reply Quote 0
                  • B Offline
                    bilou7
                    last edited by

                    Hello Daniel,

                    Did you add the functionality : "Ability to receive packets sent on any spreading factor" to the lopy gateway ?

                    Thanks in advance

                    1 Reply Last reply Reply Quote 0
                    • R Offline
                      researcher
                      last edited by researcher

                      Hello guys, regarding this code here at https://github.com/pycom/pycom-libraries/tree/master/examples/lorawan-nano-gateway

                      When I am trying to use the config for both, node and nano-gtw, with the AU915 configuration and change the following parameters into:

                      LORA_FREQUENCY = 915200000
                      LORA_GW_DR = "SF10BW125"
                      LORA_NODE_DR = 2

                      Because on LoraWAN Regional Parameters v1.1rb it says on page 37 that for OTAA procedure, the JoinReq message should be sent with DR2 data rate when BW = 125 kHz.

                      9cf989b0-040d-439d-8bdb-7349c87fb47b-image.png

                      But when uploading the code, it outputs an error regarding that the following function has an error:

                      lora.join(activation=LoRa.OTAA, auth=(dev_eui, app_eui, app_key), timeout=0, dr=config.LORA_NODE_DR)

                      However, it works when I change the config file into:

                      LORA_NODE_DR = 0
                      LORA_GW_DR = "SF12BW125"

                      Am I doing something wrong? Maybe not understanding correctly the technical specification?

                      Thanks in advance

                      1 Reply Last reply Reply Quote 0
                      • B Offline
                        Bert J Zazueta
                        last edited by

                        I am trying to use the config for both, node and nano-gtw

                        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
                        • 3
                        • 4
                        • 5
                        • 6
                        • 3 / 6
                        • First post
                          Last post

                        Pycom on Twitter

                        Pycom