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

    30uA and LoRaWAN

    Scheduled Pinned Locked Moved LoPy
    low power
    13 Posts 6 Posters 1.4k Views 7 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 @marcozennaro
      last edited by

      @marcozennaro That is hard to tell. As a blind shot, I would set the GPIO pins used for Lora/Sigfox to input. For P5 to P7 this is easy. For the other Pins at GPIO17, 18, and 23 this is not supported. These are internal Pins and not accessible through machine.Pin. And for GPIO17 it might be not recommended anyhow. AFAIK, this is also used for SPIRAM Clock.

      1 Reply Last reply Reply Quote 0
      • J Offline
        jcaron @marcozennaro
        last edited by

        @marcozennaro Unrelated, but note that you'll probably save a bit by using pycom.wifi_on_boot(false) rather than "manually" disabling WiFi and Bluetooth.

        1 Reply Last reply Reply Quote 1
        • J Offline
          jcaron
          last edited by

          Another thing you may try: set the socket to blocking to be sure it's finished sending before going to sleep, and/or add a (long enough) time.sleep.

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

            @jcaron Not likely, because the sx1276 takes 20-120 mA when sending, and about 10 mA when receiving.

            1 Reply Last reply Reply Quote 0
            • M Offline
              malachib
              last edited by

              Just curious, does your application call for receiving any LoRa packets? Or just sending [1, 2, 3] on start?

              M 1 Reply Last reply Reply Quote 0
              • M Offline
                marcozennaro Pycom Ambassadors @malachib
                last edited by

                @malachib it is just sending. As I use ABP I don't have to wait for an acknowledge from the gateway.

                B 1 Reply Last reply Reply Quote 1
                • B Offline
                  beyonlo @marcozennaro
                  last edited by

                  This post is deleted!
                  1 Reply Last reply Reply Quote 0
                  • B Offline
                    beyonlo
                    last edited by

                    @marcozennaro said in 30uA and LoRaWAN:

                    @malachib it is just sending. As I use ABP I don't have to wait for an acknowledge from the gateway.

                    Using ABP do not means that node will not waiting for a possible ACK from the Gateway. Both, ABP and OTAA always waiting a time (are two DOWNLINK slot times) after sending data, for a possible ACK from the gateway, that is standard. The difference is that OTAA needs an authentication (that will use a DOWNLINK too) before to sent any data, ABP doens't.

                    M bmarkusB 2 Replies Last reply Reply Quote 0
                    • M Offline
                      marcozennaro Pycom Ambassadors @beyonlo
                      last edited by

                      @beyonlo you are perfectly right!

                      1 Reply Last reply Reply Quote 0
                      • bmarkusB Offline
                        bmarkus @beyonlo
                        last edited by

                        @beyonlo said in 30uA and LoRaWAN:

                        @marcozennaro said in 30uA and LoRaWAN:

                        @malachib it is just sending. As I use ABP I don't have to wait for an acknowledge from the gateway.

                        Using ABP do not means that node will not waiting for a possible ACK from the Gateway. Both, ABP and OTAA always waiting a time (are two DOWNLINK slot times) after sending data, for a possible ACK from the gateway, that is standard. The difference is that OTAA needs an authentication (that will use a DOWNLINK too) before to sent any data, ABP doens't.

                        You are missing different things.

                        First, Gateway never send ACK, it is done by the LoRaWAN Network Server when requested by the device.

                        ABP and OTAA are activation modes and handling encryption keys. ABP itself doesn't generate any air traffic, keys exchanged out of LoRaWAN. OTAA is a way to generate keys but it has nothing to do with authentication.

                        Whether node will wait for downlink and when is independent of activation mode, it depends on Devics Class 'A' or 'C', 'B' is not supported by PyCom and most of other devices.

                        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