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

    Features wish list

    Scheduled Pinned Locked Moved Announcements & News
    48 Posts 23 Posters 25.7k Views 25 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.
    • M Offline
      mohpor
      last edited by

      To reiterate others or the original list, (Better be safe than sorry):

      • BLE Peripheral (server) of course!
      • BLE Peripheral or Central events (connected, subscribed, written, ...)
      • Reliable Pin Interrupts
      • Deep Sleep with Pin/RTC interrupted wake ups
      • RTC
      • WiFi 802.11X
      • Enable/Disable WiFi/BLE

      I know lots of them are on the original list and plan and I hope we will see them in the upcoming releases.

      1 Reply Last reply Reply Quote 2
      • M Offline
        madsdk
        last edited by

        For me the most critical features I'm missing right now are:

        1. Deep sleep with RTC wakeup
        2. The ability to disable Wi-Fi and Bluetooth altogether to conserve energy.
        1 Reply Last reply Reply Quote 3
        • R Offline
          Roosted Pybytes Beta
          last edited by Roosted

          I've been thinking about this for some more. Here is my list:

          1. Upstream open source code

          Right now, code updates are infrequent (only on version number), and in completely separate fork. This has resulted in very few PR from other developers...
          I'm really hesitant to help this uPy development, because it is completely separated from upstream - and I have spoken several other developers that feel the same. We understand the re-licensing might have been necessary because of (for example) LoRa chipset vendor drivers, but probably not all the code - right? If all the core esp32 stuff was merged upstream, free development help might come by itself :)

          If help does not come by itself, you guys might set (financial or material) intensives for helping the development. Since you probably have a very good list with features people want, you could set rewards on these features? I know you are looking to hire, and this might be a cheaper & easier alternative?
          (If I would study in Eindhoven instead of Delft, I would have applied already...)

          1. (802.1X)

          I've asked for this before ;)

          1. mDNS

          mDNS would be really awesome, because you could telnet to 'lopy.local/' instead of scanning the network and telnet'ting into the scanned IP. I guess this is not to hard to implement, as it is all UDP broadcast.

          1. SSH instead of telnet

          Since we have the hw encryption SSH should be possible? Of course we could all implement this is python, but a C based version would be desirable..

          1. Cloud IDE

          This one is on the bottom of my list, for a good reason :P (privacy, security, etc, ..)
          But still! It would be amazing if your wifi device could connect with some Pycom web IDE to fetch it's (encrypted) python code...

          1 Reply Last reply Reply Quote 6
          • L Offline
            livius
            last edited by livius

            i see that this is still not fixed then i add this to the list it is about ADC:
            We're working with the ESP32 manufacturer on enabling 12 bits plus the internal attenuation (will enable measurements of up to 4.4V).

            https://forum.pycom.io/topic/226/lopy-adcs/8#

            think about people first, then computers

            1 Reply Last reply Reply Quote 1
            • C Offline
              cfaessler
              last edited by cfaessler

              Some additional wishes from my side:

              • Allow to specify port (FPort) for LoRaWAN packages
              • Allow confirmed and unconfirmed LoRaWAN packages
              bmarkusB 1 Reply Last reply Reply Quote 1
              • bmarkusB Offline
                bmarkus @cfaessler
                last edited by

                @cfaessler said in Features wish list:

                Some additional wishes from my side:

                • Allow to specify port (FPort) for LoRaWAN packages

                Is it really missing, port can't be specified per today? In such case I can't use it, as in our network ports allocated to services :(

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

                  @bmarkus No, this is already supported. Use the bind() method on a LoRa socket to select the port. For instance s.bind(1) will select port #1 for the socket.

                  Cheers,
                  Daniel

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

                    Allow confirmed and unconfirmed LoRaWAN packages

                    This is already supported via socket options.

                    We are releasing new docs in around 2 hours which will show all this. We'll make an announcement shortly.

                    C 1 Reply Last reply Reply Quote 0
                    • C Offline
                      cfaessler @daniel
                      last edited by

                      @daniel Cool thanks!

                      1 Reply Last reply Reply Quote 0
                      • C Offline
                        cfaessler
                        last edited by cfaessler

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

                          A 'read_timed' command as the one in the following link can be interesting:
                          http://docs.micropython.org/en/v1.8.6/pyboard/library/pyb.ADC.html

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

                            @daniel
                            Currently, WiFi is initialized at boot (WiPy 2.0) and this feature cannot be disabled to be initialized later on (in boot.py) for example. I know it might be useful in some use cases, but it increases boot time and occupies memory and consumes battery power before we as developers get to disable it. I wish no extra features would be started before boot and we get to enable them as we wish, afterwards.

                            Cheers,
                            M.

                            L 1 Reply Last reply Reply Quote 2
                            • L Offline
                              livius @mohpor
                              last edited by livius

                              @mohpor
                              yes, somewhere someone wirite good point about this
                              i suppose that all features like wifi, blootooth, lora, ... should be disabled at start
                              maybe this can be achived by e.g. file existence on the flash.
                              like boot.config

                              if it does not exist - then all go same as is now
                              but if it exists then it should be parsed

                              think about people first, then computers

                              1 Reply Last reply Reply Quote 1
                              • C Offline
                                cfaessler
                                last edited by

                                Just read that the ESP32 shall have a built in Hall effect sensor and CAN bus Interface.
                                We needed both of it and used external peripherals until now. Is this something on your roadmap to implement?

                                1 Reply Last reply Reply Quote 2
                                • C Offline
                                  Colateral @daniel
                                  last edited by

                                  @daniel Wifi rssi() is important in IOT.

                                  1 Reply Last reply Reply Quote 3
                                  • L Offline
                                    livius @daniel
                                    last edited by livius

                                    @daniel
                                    Will be good to have built in DTMF generator :)

                                    think about people first, then computers

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

                                      @alexander said in Features wish list:

                                      Direct hardware access (similar to the examples on Micropython speed), i.e. the Viper code emitter or some other approach to allow high speed digital IO

                                      I agree.

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

                                        @Roosted said in Features wish list:

                                        @jasonriedy said in Features wish list:

                                        • Enterprise WPA support

                                        802.11X is the feature i'm really waiting for!
                                        I've seen Wi-Fi marked as 'done' somewhere, but it is not usable in enterprise/educational environments...

                                        For as far as I know 802.11X is supported in the ESP-IDF, so it would 'just' need to be implemented in python - right?

                                        Thanks for steady development pace! :)

                                        I think you are talking about 802.1x, correct?

                                        Thanks.

                                        1 Reply Last reply Reply Quote 0
                                        • G Offline
                                          gertjanvanhethof Pybytes Beta
                                          last edited by

                                          @daniel One important feature to bring the xxPy devices to a higher enterprise ready plan is to add functionality to do firmware updates and software updates over-the-air.
                                          Are there plans to add this?

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

                                            @gertjanvanhethof yes, there are plans for this.

                                            B 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
                                            • 2 / 3
                                            • First post
                                              Last post

                                            Pycom on Twitter

                                            Pycom