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

    Firmware release 1.1.0.b1

    Scheduled Pinned Locked Moved Announcements & News
    32 Posts 13 Posters 12.0k Views 12 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.
    • G Offline
      gertjanvanhethof Pybytes Beta @daniel
      last edited by

      @daniel Is it possible that pycom makes it possible to download older firmware updates too?
      I need this because the latest is not working fine for me (see AWS MQTT connection issues). But i don't have the older firmware anymore.

      1 Reply Last reply Reply Quote 0
      • D Offline
        daniel
        last edited by

        @gertjanvanhethof yes, we will make this available early next week.

        1 Reply Last reply Reply Quote 0
        • S Offline
          stevie @mohpor
          last edited by

          @mohpor, actually I am not angry with the Pycom guys. I think they are doing a great job. They are developing the firmware farther at a steady pace. While they may be behind their initial schedule (or our expectations of the schedule) this is in big parts due to the fact that they are on the leading edge of the ESP32 users. Others playing around with the ESP32 are also delayed by the late delivery of the BLE features. If the ESP32 manufacturers don't deliver certain features, the Pycom guys can hardly deliver them either. All in all the WiPy and LoPy are great modules and I am sure they will improve further with time. As it is now, the best strategy would be to accept the development status as it is and just wait and help prioritizing things.

          1 Reply Last reply Reply Quote 2
          • P Offline
            perfeco
            last edited by

            This release supports LoRa transmission.
            Release 1.1.1.b1 crashes and reboots a few seconds after a LoRa transmission.
            Tested on LORA (MAC) mode.

            D 1 Reply Last reply Reply Quote 0
            • D Offline
              daniel @perfeco
              last edited by

              @perfeco is that with the 868 or the 915 MHz version? Can you provide a small piece of code that reproduces it? Thanks.

              Cheers,
              Daniel

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

                Test code for LORA MAC TX:

                import machine
                from network import LoRa, WLAN
                import socket
                from time import sleep

                wlan = WLAN(mode=WLAN.STA) # Switch off WLAN AP
                lora = LoRa(mode=LoRa.LORA) # Switch on LoRa
                s = socket.socket(socket.AF_LORA, socket.SOCK_RAW)
                s.setblocking(False)
                lora.power_mode(LoRa.ALWAYS_ON)
                sleep(.1)
                s.send(">>> ")

                • Crashes on os.uname() == (sysname='LoPy', nodename='LoPy', release='1.1.1.b1', version='v1.8.6-281-g75e2452 on 2017-01-03', machine='LoPy with ESP32')
                • Works on os.uname() == (sysname='LoPy', nodename='LoPy', release='1.0.1.b1', version='v1.8.6-264-gadacebe on 2016-12-22', machine='LoPy with ESP32')

                How do I check which frequency LoRa is using?

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

                  Tested with lora.frequency() == 868000000

                  D 1 Reply Last reply Reply Quote 0
                  • D Offline
                    daniel @perfeco
                    last edited by daniel

                    @perfeco thanks. I can confirm the issue is there. It crashes a few seconds after sending. We are investigating it... Will report shortly.

                    It only happens in LoRA MAC mode, not in LoRaWAN.

                    Cheers,
                    Daniel

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

                      Lowest current consumption so far: 106 mA during time.sleep().

                      Is machine.idle() a low-power mode where all CPUs are supposed to be idle and execution stopped until next IRQ?

                      1 Reply Last reply Reply Quote 0
                      • P Offline
                        perfeco @daniel
                        last edited by perfeco

                        It only happens in LoRA MAC mode, not in LoRaWAN.

                        Can a LoPy be LoRaWAN gateway to a LoPy device?

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

                          @perfeco said in Firmware release 1.1.0.b1:

                          It only happens in LoRA MAC mode, not in LoRaWAN.

                          Can a LoPy be LoRaWAN gateway to a LoPy device?

                          No, due to hardware. LoPy is a device with SX127x while a LoRaWAN GW requires SX130x chipset.

                          P F 2 Replies Last reply Reply Quote 0
                          • P Offline
                            perfeco @bmarkus
                            last edited by

                            @bmarkus Thanks for promt answers!

                            1 Reply Last reply Reply Quote 0
                            • M Offline
                              maku @the_ned
                              last edited by

                              @the_ned bump

                              Need that too.

                              1 Reply Last reply Reply Quote 0
                              • F Offline
                                Fred administrators @bmarkus
                                last edited by

                                @bmarkus It can be a LoRaWAN nano gateway listening to one channel at a time. Be mindful that this is not LoRaWAN compliant but is very useful in certain conditions. We will release the full firmware with this functionality early Feb.

                                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