Features wish list

[JF002]

@gertjanvanhethof said in Features wish list:

@daniel Non blocking for I2C should be put on top of the wish list.

But if I can add new topics than I would ask you to put full support of TTN as nano-gateway to the list.

I second this! I would like to make a LoRaWAN/TTN nano-gateway (I know, it won't be fully compliant with LoRaWAN specification, but from my understanding, it should be possible to use it as a development gateway).

[alexander]

In no particular order:

• Long range WiFi with DSSS @ 1MBit/s (WiPy is advertised with 1km)
• Pulse counter
• 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
• Integration with other Micropython ports, staying as compatible as possible
• Deep sleep and timer based wakeup

[lmetcalfe]

@daniel
Priority order

• Sleep/DeepSleep with RTC and RTC memory functions. How environment is preserved during various sleeps.
• Power consumption in various sleep functions - Radios on/ff
• Non Blocking options on peripherals
• bluetooth.get_adv()

[mohpor]

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.

[madsdk]

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.

[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...)

2. (802.1X)

I've asked for this before ;)

3. 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.

4. 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..

5. 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...

[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#

[cfaessler]

Some additional wishes from my side:

• Allow to specify port (FPort) for LoRaWAN packages
• Allow confirmed and unconfirmed LoRaWAN packages

[bmarkus]

@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 :(

[daniel]

@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

[daniel]

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.

[cfaessler]

@daniel Cool thanks!

[cfaessler]

This post is deleted!

[Meide]

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

[mohpor]

@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.

[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

[cfaessler]

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?

[Colateral]

@daniel Wifi rssi() is important in IOT.

[livius]

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

[beyonlo]

@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.