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.
    • D Offline
      daniel
      last edited by

      Hello everyone,

      Time for a new firmware release :-). We have done major changes to the Bluetooth API which we hope you will like. It's much more object oriented now.

      The release notes are as follows:

      • Add bluetooth.isscanning() method to check if a scan is still in progress.
      • Add a method to get the characteristics of a service.
      • Create the BluetoothConnection, BluetoothService and BluetoothCharacteristic classes.
      • bluetooth.connect() now returns an object of the type BluetoothConnection

      Please have a look at the docs in: https://docs.pycom.io/pycom_esp32/library/network.Bluetooth.html
      for all the details.

      Reading and writing characteristics is now possible and we will keep enhancing this functionality.

      In the upcoming releases we will add a method for subscribing to notifications/indications, and non-blocking options to most of the API calls. All these features depend on the new interrupt mechanism that we plan to release next week and that's the reason why they are not available yet.

      The firmware update tool is available here: https://www.pycom.io/support/supportdownloads/

      Looking forward to receive your feedback.

      Cheers,
      Daniel

      J G 2 Replies Last reply Reply Quote 5
      • T Offline
        the_ned
        last edited by

        Hi Daniel,

        I just received today my SiPY modules and I am trying to access the BLE stack and I am getting an import module error for Bluetooth.
        Is there a way to upgrade the SiPY firmware with that update? Currently the upgrade tool does not support it (not present in the firmware list).

        Thanks

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

          @the_ned sorry to keep you waiting. We plan to add support to the SiPy on the updater tool next Tuesday.

          T 1 Reply Last reply Reply Quote 0
          • J Offline
            jasonriedy @daniel
            last edited by

            Place this under "desires:" My application could use a filtering BLE scan with a timeout that returns an array of the advertisement data. The addresses in my case will come in multiples of three (three sensors per bee hive). I cannot quite trace esp_ble_adv_filter_t through the IDF code, so I'm guessing this isn't implemented yet. The scan would be followed by a period of deep, deep sleep ideally.

            An alternative would be to collect all BLE advertisements from the whitelist into a FIFO queue while in "sleep", then wake up to process and send via LoRaWAN / whatever. But that likely would be less energy-efficient. There may be many BLE devices passing by, and I only want the data every 10-15 minutes.

            1 Reply Last reply Reply Quote 0
            • FridaF Offline
              Frida
              last edited by

              What is wrong here?

              MicroPython v1.8.6-274-g9a2018f on 2016-12-29; WiPy with ESP32
              Type "help()" for more information.
              ">>>"
              paste mode; Ctrl-C to cancel, Ctrl-D to finish
              === from network import Bluetooth
              === import time
              === bt = Bluetooth()
              === bt.start_scan(-1)

              BTDM CONTROLLER VERSION: 010101
              btip start
              copy .data from 4000d890 to 3ffae6e0, len 00001830
              set .bss 0x0 from 3ffb8000 to 3ffbff70, len 00007f70
              BTDM ROM VERSION 0101
              BD_ADDR: 24:0A:C4:00:70:C6
              NVDS MAGIC FAILED
              RF Init OK with coex
              W (34905) wifi: post pm rx bcn failed
              ">>>"

              it is the first lines from here

              https://docs.pycom.io/pycom_esp32/library/network.Bluetooth.html

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

                @daniel
                Next week will be the perfect timeframe.
                Thanks again. Great job. And I wish you a lot of XxPy for 2017!!

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

                  @Frida nothing, it's just a warning message that will be removed in future releases. Is the scan returning results?

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

                    @daniel I am able to scan and get the advertisement from my TI Sensor Tag, but not my Eddystone Beacon. Not sure why... Do the advertisements get queued up and we retrieve them one by one with get_adv() method? Any plans to set up a callback feature for receiving advertisements instead of polling with get_adv()?

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

                      @drnordstedt yes advertisements are queued and the FIFO behind has space for 8 advertisement messages.

                      Have you tried on a for loop?

                      while True:
                          bt.get_adv()
                      

                      Yes, we do have plans to also offer a callback feature.

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

                        @daniel Thanks for the info. Yes, I tried it in a loop. I'll run some more tests with other devices and sniff out the packets. I can send you the advertising packet data if you'd like when I run my captures.

                        J 1 Reply Last reply Reply Quote 0
                        • J Offline
                          jasonriedy @drnordstedt
                          last edited by

                          @drnordstedt @daniel What may work "better" is if get_adv() returns an array of all currently known requests, resetting the queue. I can see too many race conditions otherwise.

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

                            Hi @daniel
                            As I have mentioned in my email, there is no BLE Peripheral in the current implementation, nor anything is planned for the near future. Do you have any plans for it?
                            set_adv(), add_service(), add_characteristic()... would be a dream come true for me now. I have waited a few weeks, I'm losing hope.

                            D F 2 Replies Last reply Reply Quote 0
                            • D Offline
                              daniel @mohpor
                              last edited by

                              @mohpor Hi, I have replied to your email a few minutes ago... we do have plans for supporting BLE in GATT server mode, we just chose to implement the client functionality first as this is what most people was requesting.

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

                                @mohpor In line with Daniel's message several weeks ago, we asked the community for input. We have now prioritised the firmware build and we will NOT be making changes at this point. Your request will be added after the firmware release mid January.

                                With regards to other comment you made, the team DID release the firmware through the Christmas period and will CONTINUE further development according to Daniel's build schedule.

                                Thanks Fred

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

                                  @Fred

                                  OK. Looks like you are angry with me which I can not understand for the life of me. If anyone here should be angry is us customers, not you guys with empty promises!

                                  F S 2 Replies Last reply Reply Quote 0
                                  • M Offline
                                    mohpor
                                    last edited by

                                    @Fred

                                    Regarding my (Deleted) Comment, I have checked your forum and my eyes could handle the build number bump from 1.0.1.b1 to 1.1.0.b1! forgive me for being pedantic, but that's not the way people pump their build numbers.

                                    I KNOW you have submitted an update. No need to point that out AGAIN.

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

                                      @mohpor I suggest you take a balanced view of your opinions and reconsider 'empty promises'. I have emailed you separately. I believe you can also note that the Firmware release promised during the Christmas vacation was delivered by the team, contrary to your other comment.

                                      You were invited to put any items required onto our roadmap, and since nothing was forthcoming, we built up the list inline with the majority of our customers requirements.

                                      Thanks Fred

                                      1 Reply Last reply Reply Quote 0
                                      • O Offline
                                        Oneillsite
                                        last edited by

                                        -- infos ---
                                        Interesting app (Android) to monitor BLE.
                                        Gives Flags
                                        Services UUIDs
                                        Service Data

                                        nRF connect
                                        from NordicSemiConductor

                                        1 Reply Last reply Reply Quote 0
                                        • 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

                                            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