<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Enhancements]]></title><description><![CDATA[Firmware wishlist &amp; desired features]]></description><link>https://forum.pycom.io/category/15</link><generator>RSS for Node</generator><lastBuildDate>Tue, 18 Aug 2026 17:44:59 GMT</lastBuildDate><atom:link href="https://forum.pycom.io/category/15.rss" rel="self" type="application/rss+xml"/><pubDate>Mon, 02 Aug 2021 12:20:41 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Micropython version update]]></title><description><![CDATA[@Gijs I think it's a concern of many users that Pycom is spreading resources thin by working on too many new products which never see the light of day while not following up enough on the existing products.
Let's just consider this list of Pycom vapourware:

PyGo 1/2 + PyLife : first announced 25/09/2018 (soon to be 3 years ago).
PyNode range: announced 25/06/2020
PyNode Touch: announced 06/07/2020
Expansion board V4: announced 14/10/2020
M.2 format boards: announced 17/11/2020
ESP32-S3-based boards: announced 01/02/2021
PyNode+ range: announced 08/02/2021

I know time-to-market can be essential in this industry but this is getting a bit out of hand...
]]></description><link>https://forum.pycom.io/topic/6929/micropython-version-update</link><guid isPermaLink="true">https://forum.pycom.io/topic/6929/micropython-version-update</guid><dc:creator><![CDATA[jcaron]]></dc:creator><pubDate>Mon, 02 Aug 2021 12:20:41 GMT</pubDate></item><item><title><![CDATA[littlefs:  set file creation&#x2F;modification timestamps?]]></title><description><![CDATA[@Gijs One can also:

open the file in r+ mode
read one byte
seek to 0
write the read byte back
close the file.

That will change the time stamp as well.
]]></description><link>https://forum.pycom.io/topic/7151/littlefs-set-file-creation-modification-timestamps</link><guid isPermaLink="true">https://forum.pycom.io/topic/7151/littlefs-set-file-creation-modification-timestamps</guid><dc:creator><![CDATA[robert-hh]]></dc:creator><pubDate>Sat, 17 Jul 2021 08:51:41 GMT</pubDate></item><item><title><![CDATA[Pytrack GPS API]]></title><description><![CDATA[I have done more testing and the call is actually working, I'm just not able to catch the confirmation reply.
@jcaron Thanks for the suggestion with the PMTK353.  I changed these around and discovered my antenna is not reading anything but GPS.  When I turn on Glonass only, I get nothing returned, so I must have a hardware issue.
]]></description><link>https://forum.pycom.io/topic/1626/pytrack-gps-api</link><guid isPermaLink="true">https://forum.pycom.io/topic/1626/pytrack-gps-api</guid><dc:creator><![CDATA[Alex Dew]]></dc:creator><pubDate>Mon, 24 May 2021 14:15:19 GMT</pubDate></item><item><title><![CDATA[ESP-Now support]]></title><description><![CDATA[Hi,
We're working on getting the documentation out there. In the meantime you can find it here: https://github.com/pycom/pycom-documentation/pull/387/files (near the bottom):
from network import WLAN
from network import ESPNOW
import binascii
import time
# The callback to be registered when a message has been sent to a Peer
def espnow_tx(result):
    # &quot;result&quot; is the parameter in form of 2 element long tuple
    # &quot;peer&quot; is the Peer which the message has been sent to
    # &quot;sent&quot; is a boolean showing whether the message could be sent
	peer, sent = result
	mac = peer.addr()
	if(sent == False):
		print(&quot;Sending message to %s failed!&quot; % binascii.hexlify(mac))
	else:
		print(&quot;Message sent to: %s&quot; % (binascii.hexlify(mac)))
# The callback to be registered when a message has been received
def espnow_rx(result):
	# &quot;result&quot; is the parameter in form of 3 element long tuple
    # &quot;mac&quot; is the MAC address of the sender
    # &quot;peer&quot; is the Peer which the message has been received from. If message has been received from a not registered Peer this parameter is None
    # &quot;msg&quot; is the payload from the received message
    mac, peer, msg = result
	if(peer is not None):
		print(&quot;Message received from %s with content: %s&quot; % (binascii.hexlify(mac), msg))
		peer.send(&quot;Sending back an answer&quot;)
# The ESPNOW module needs that WLAN is initialized
w = WLAN()
# Initialize the ESPNOW module
ESPNOW.init()
# Register the callback which will be called on TX
ESPNOW.on_send(espnow_tx)
# Register the callback which will be called on RX
ESPNOW.on_recv(espnow_rx)
# Add a dedicated Peer with MAC address: 11:22:33:44:55:66
p = ESPNOW.add_peer(&quot;112233445566&quot;)
# Send a message dedicated to the Peer
p.send(&quot;My Message&quot;)
# Sending 1 message to all Peers which are registered
ESPNOW.send(None, &quot;Hello all Peers!&quot;)

]]></description><link>https://forum.pycom.io/topic/2822/esp-now-support</link><guid isPermaLink="true">https://forum.pycom.io/topic/2822/esp-now-support</guid><dc:creator><![CDATA[Gijs]]></dc:creator><pubDate>Sun, 16 May 2021 07:23:36 GMT</pubDate></item><item><title><![CDATA[BT limit on nr of connections]]></title><description><![CDATA[@Fredrik-Andersson download the code from the GitHub repo (https://github.com/pycom/pycom-micropython-sigfox) and follow the instructions (which involve downloading and installing quite a few things).
]]></description><link>https://forum.pycom.io/topic/6928/bt-limit-on-nr-of-connections</link><guid isPermaLink="true">https://forum.pycom.io/topic/6928/bt-limit-on-nr-of-connections</guid><dc:creator><![CDATA[jcaron]]></dc:creator><pubDate>Wed, 31 Mar 2021 12:31:20 GMT</pubDate></item><item><title><![CDATA[ULP co-pro support]]></title><description><![CDATA[@tuftec said in ULP co-pro support:

PyCom Go-invent sessions

I too am quite interested in utilizing the ULP.
The main MicroPython project has support for ULP:
https://docs.micropython.org/en/latest/library/esp32.html?highlight=ulp#esp32.ULP
Sincerely,
Duane
]]></description><link>https://forum.pycom.io/topic/6138/ulp-co-pro-support</link><guid isPermaLink="true">https://forum.pycom.io/topic/6138/ulp-co-pro-support</guid><dc:creator><![CDATA[Duane Kaufman]]></dc:creator><pubDate>Fri, 29 Jan 2021 20:44:16 GMT</pubDate></item><item><title><![CDATA[Atom question]]></title><description><![CDATA[I usually click the mousewheel and drag up/down depending on which direction I need to go, but indeed its not a nice solution. I dont know of any keyboard tricks
]]></description><link>https://forum.pycom.io/topic/6660/atom-question</link><guid isPermaLink="true">https://forum.pycom.io/topic/6660/atom-question</guid><dc:creator><![CDATA[Gijs]]></dc:creator><pubDate>Sun, 20 Dec 2020 14:25:24 GMT</pubDate></item><item><title><![CDATA[Canbus is managed separately or is using one of the uarts]]></title><description><![CDATA[<p dir="auto">Hello,</p>
<p dir="auto">On WIPY I use UART0 + ,UART1,UART2 and I want to use also CANBUS on P22,P23. Does anybody know if canbus is managed separately or is using one of the uarts ?</p>
<p dir="auto">Thank you,<br />
Cata</p>
]]></description><link>https://forum.pycom.io/topic/6524/canbus-is-managed-separately-or-is-using-one-of-the-uarts</link><guid isPermaLink="true">https://forum.pycom.io/topic/6524/canbus-is-managed-separately-or-is-using-one-of-the-uarts</guid><dc:creator><![CDATA[Colateral]]></dc:creator><pubDate>Tue, 03 Nov 2020 12:33:12 GMT</pubDate></item><item><title><![CDATA[Support for I2S Interface]]></title><description><![CDATA[Adding the I2S driver to the PyCom firmware is still open but we could manage to include it on a home brewed firmware version, see https://community.hiveeyes.org/t/erschliessung-von-i2s-support-und-fft-fur-micropython-auf-pycom-esp32/2331/30 Use at least version FiPy-1.20.1.r1-0.7.0-vanilla-dragonfly-onewire-i2s.tar.gz or better a newer release, see Dragonfly firmware for Pycom/ESP32.
]]></description><link>https://forum.pycom.io/topic/997/support-for-i2s-interface</link><guid isPermaLink="true">https://forum.pycom.io/topic/997/support-for-i2s-interface</guid><dc:creator><![CDATA[Clemens]]></dc:creator><pubDate>Tue, 25 Aug 2020 23:51:25 GMT</pubDate></item><item><title><![CDATA[CPU Frequency control....]]></title><description><![CDATA[<p dir="auto">Please fully implement the machine,freq() method so that we can run the processor frequency at full speed i.e. 240Mhz.<br />
we need the extra performance.</p>
<p dir="auto">Also it will allow those people for whom power efficiency is important to downclock the processor to a lower frequency.</p>
]]></description><link>https://forum.pycom.io/topic/6272/cpu-frequency-control</link><guid isPermaLink="true">https://forum.pycom.io/topic/6272/cpu-frequency-control</guid><dc:creator><![CDATA[cYc]]></dc:creator><pubDate>Fri, 21 Aug 2020 11:20:53 GMT</pubDate></item><item><title><![CDATA[Enable OrderedDict support by default]]></title><description><![CDATA[@DvdGiessen coming to this several years later. Seems still not enabled in 1.20.2.rc6 firmware because still getting an ImportError when running from ucollections import OrderedDict :(
]]></description><link>https://forum.pycom.io/topic/972/enable-ordereddict-support-by-default</link><guid isPermaLink="true">https://forum.pycom.io/topic/972/enable-ordereddict-support-by-default</guid><dc:creator><![CDATA[d.alvrzx]]></dc:creator><pubDate>Thu, 02 Jul 2020 22:11:23 GMT</pubDate></item><item><title><![CDATA[Using custom firmware as frozen firmware]]></title><description><![CDATA[@eranroll
The way we do it is put the files and sub-folders from the /lib folder into pycom-micropython-sigfox/esp32/frozen/Custom. main.py and boot.py get renamed to _main.py and _boot.py and go into pycom-micropython-sigfox/esp32/frozen/Base.
It then boots using are custom boot and main and has access to the libraries in Custom.
Tom
]]></description><link>https://forum.pycom.io/topic/5945/using-custom-firmware-as-frozen-firmware</link><guid isPermaLink="true">https://forum.pycom.io/topic/5945/using-custom-firmware-as-frozen-firmware</guid><dc:creator><![CDATA[tom.mcadam]]></dc:creator><pubDate>Tue, 26 May 2020 05:23:33 GMT</pubDate></item><item><title><![CDATA[What needs to be done to support 6lowpan via slip via uart ?]]></title><description><![CDATA[<p dir="auto">Hi Devs,</p>
<p dir="auto">excellent work you have done so far - congratulations !</p>
<p dir="auto">i got my nb-iot sim card from magenta today, ten minutes after fw upgrade i was able to send out my first udp packets ! - GREAT !</p>
<p dir="auto">as i am also experimenting with 6lowpan (contiki os), i want to connect them to my FiPy in order to query the 6lowpan nodes via CoAP and send the responses to my server via NB-IoT.</p>
<p dir="auto">therefore the question is what needs to be done in order to add this functionality to micropython ?</p>
<p dir="auto">on the linux side this is done with a tool called tunslip6 which bridges the 6lowpan via slip to a tun device on the pc.</p>
<p dir="auto">i checked out pycom-micropython-sigfox from github and to my surprise i found 6lowpan and slip code in lib/lwip/src/netif.</p>
<p dir="auto">so how can this be integrated in a custom build ?</p>
<p dir="auto">how does the socket code know how to interface with the network devices ?</p>
<p dir="auto">what about the AbstractNIC stuff that is documented in docs/library/network.rst ?</p>
<p dir="auto">and how would i set this up under micropython ?</p>
<p dir="auto">i am experienced python and embedded programmer (ported pymite a couple years ago), so no problem to get my hands dirty with this !</p>
<p dir="auto">i think i haven't found the correct documentation, or &quot;big picture&quot; on how the things are connected - also not on the micropython page ... :(</p>
<p dir="auto">so please, point me in the right direction or give me some hints so that i can bring this to life ;)</p>
<p dir="auto">regards,<br />
mexx.</p>
]]></description><link>https://forum.pycom.io/topic/5715/what-needs-to-be-done-to-support-6lowpan-via-slip-via-uart</link><guid isPermaLink="true">https://forum.pycom.io/topic/5715/what-needs-to-be-done-to-support-6lowpan-via-slip-via-uart</guid><dc:creator><![CDATA[mexx4711]]></dc:creator><pubDate>Thu, 20 Feb 2020 18:16:03 GMT</pubDate></item><item><title><![CDATA[ULP support]]></title><description><![CDATA[<p dir="auto">During the GOINVENT roadshow in Melbourne last year, there was an announcement/discussion about support for ULP control functionality directly within Pycom micropython.<br />
It was promoted by Fred as being a simple clean control interface.<br />
Has this mechanism been implemented yet?<br />
If so, how do we use it?</p>
<p dir="auto">I am looking for a solution that enables me to use the ULP from directly within micropython without the need to rebuild new versions of the pycom core core.</p>
<p dir="auto">A solution that would enable a precoded ULP module in binary form to be loaded and then intiated from micropython would be great.</p>
<p dir="auto">Also tools to help with coding of the ULP would be fantastic.</p>
<p dir="auto">Can someone provide an unpate on the availability of this feature?</p>
<p dir="auto">I am aware that other implementations of micropython have made progress in this area.</p>
]]></description><link>https://forum.pycom.io/topic/5676/ulp-support</link><guid isPermaLink="true">https://forum.pycom.io/topic/5676/ulp-support</guid><dc:creator><![CDATA[tuftec]]></dc:creator><pubDate>Tue, 11 Feb 2020 20:55:32 GMT</pubDate></item><item><title><![CDATA[Support for Pulse Counter]]></title><description><![CDATA[@jmarcelino Is it still the case that we cannot access the counter through Python? Or has a driver been written? I'm looking to monitor a system fan, but with as little overhead as possible. If I count the fan tachometer output and check it every so often, I should get a good idea of how it's going. The system is busy, so I don't want lots of interrupts happening and was hoping to take care of this in the already available hardware.
]]></description><link>https://forum.pycom.io/topic/998/support-for-pulse-counter</link><guid isPermaLink="true">https://forum.pycom.io/topic/998/support-for-pulse-counter</guid><dc:creator><![CDATA[John Baird]]></dc:creator><pubDate>Sun, 24 Nov 2019 05:46:41 GMT</pubDate></item><item><title><![CDATA[Firmware Flashing Documentation Insufficient Information]]></title><description><![CDATA[Pybytes (2.0) / Pybytes-legacy (1.0) is a cloud-based device management platform. You can use it to visualize the sensors data, see the status and geolocation of your devices and you can also perform Firmware Over the Air updates. Pybytes version 1.0 and 2.0 are built on top of the low-level firmware.
The legacy firmware contains the old low-level modules of the Pycom devices without pybytes. It contains the micropython interface, FreeRTOS and all the drivers (LTE, Wifi, Bluetooth, i2c, sockets, Lora, etc).
]]></description><link>https://forum.pycom.io/topic/5289/firmware-flashing-documentation-insufficient-information</link><guid isPermaLink="true">https://forum.pycom.io/topic/5289/firmware-flashing-documentation-insufficient-information</guid><dc:creator><![CDATA[oligauc]]></dc:creator><pubDate>Tue, 15 Oct 2019 09:59:40 GMT</pubDate></item><item><title><![CDATA[Multi-functional grain thresher&#x2F;Sheller use precautions]]></title><description><![CDATA[@yanghm Well, I'll certainly keep this in mind. Perhaps the lack of a hair net relates to some of the LTE issues I had. I'll try putting one on...
]]></description><link>https://forum.pycom.io/topic/4708/multi-functional-grain-thresher-sheller-use-precautions</link><guid isPermaLink="true">https://forum.pycom.io/topic/4708/multi-functional-grain-thresher-sheller-use-precautions</guid><dc:creator><![CDATA[John Baird]]></dc:creator><pubDate>Wed, 17 Apr 2019 10:20:34 GMT</pubDate></item><item><title><![CDATA[Touchpad support implemented]]></title><description><![CDATA[@geoff-white : guess we'll find out.
]]></description><link>https://forum.pycom.io/topic/4026/touchpad-support-implemented</link><guid isPermaLink="true">https://forum.pycom.io/topic/4026/touchpad-support-implemented</guid><dc:creator><![CDATA[psychogenic]]></dc:creator><pubDate>Mon, 01 Apr 2019 04:07:41 GMT</pubDate></item><item><title><![CDATA[WPA3 is coming...]]></title><description><![CDATA[<p dir="auto">Are there any on going preparations for implementing WPA3 in the WiFi stack?</p>
]]></description><link>https://forum.pycom.io/topic/4454/wpa3-is-coming</link><guid isPermaLink="true">https://forum.pycom.io/topic/4454/wpa3-is-coming</guid><dc:creator><![CDATA[rskoniec]]></dc:creator><pubDate>Wed, 27 Feb 2019 15:28:19 GMT</pubDate></item><item><title><![CDATA[Firmware: All relases should be available]]></title><description><![CDATA[Ill raise this internally.  seems like a good idea.
]]></description><link>https://forum.pycom.io/topic/4158/firmware-all-relases-should-be-available</link><guid isPermaLink="true">https://forum.pycom.io/topic/4158/firmware-all-relases-should-be-available</guid><dc:creator><![CDATA[Paul Thornton]]></dc:creator><pubDate>Thu, 27 Dec 2018 16:59:57 GMT</pubDate></item><item><title><![CDATA[A few questions about the LoRa mesh]]></title><description><![CDATA[hi @mgranberry,
Thanks for your PR. I will take a closer look later this week, now I'm into some funky openthread behaviour.
There are lots of stuff for the Mesh I need to add, but for multisocket I did not wrote any code.
]]></description><link>https://forum.pycom.io/topic/4077/a-few-questions-about-the-lora-mesh</link><guid isPermaLink="true">https://forum.pycom.io/topic/4077/a-few-questions-about-the-lora-mesh</guid><dc:creator><![CDATA[catalin]]></dc:creator><pubDate>Tue, 18 Dec 2018 07:25:06 GMT</pubDate></item><item><title><![CDATA[More date support]]></title><description><![CDATA[@anacleto
utime.localtime(utime.time())

contains the day of week
]]></description><link>https://forum.pycom.io/topic/865/more-date-support</link><guid isPermaLink="true">https://forum.pycom.io/topic/865/more-date-support</guid><dc:creator><![CDATA[crumble]]></dc:creator><pubDate>Thu, 22 Nov 2018 16:26:32 GMT</pubDate></item><item><title><![CDATA[Update on LoraMesh]]></title><description><![CDATA[@catalin
Everything's clear now, thanks again.
]]></description><link>https://forum.pycom.io/topic/3858/update-on-loramesh</link><guid isPermaLink="true">https://forum.pycom.io/topic/3858/update-on-loramesh</guid><dc:creator><![CDATA[morpheus]]></dc:creator><pubDate>Thu, 15 Nov 2018 20:42:52 GMT</pubDate></item><item><title><![CDATA[Method send_at_cmd_pretty for LTE class]]></title><description><![CDATA[@robert-hh I thought so. Thanks.
]]></description><link>https://forum.pycom.io/topic/3891/method-send_at_cmd_pretty-for-lte-class</link><guid isPermaLink="true">https://forum.pycom.io/topic/3891/method-send_at_cmd_pretty-for-lte-class</guid><dc:creator><![CDATA[rskoniec]]></dc:creator><pubDate>Thu, 18 Oct 2018 14:14:43 GMT</pubDate></item><item><title><![CDATA[PSM &amp; eDRX]]></title><description><![CDATA[Is there any release date for the support of PSM and eDRX features?
If you cant keep up with the amount of work you have to deliver, maybe you should think something like bounties for most requested features by your community.
]]></description><link>https://forum.pycom.io/topic/3394/psm-edrx</link><guid isPermaLink="true">https://forum.pycom.io/topic/3394/psm-edrx</guid><dc:creator><![CDATA[Aris]]></dc:creator><pubDate>Fri, 05 Oct 2018 10:02:14 GMT</pubDate></item><item><title><![CDATA[Canbus support and documentarion]]></title><description><![CDATA[apologies,
https://docs.pycom.io/firmwareapi/pycom/machine/can#constructors
i was incorrectly using the Search Function in the new documentation.
]]></description><link>https://forum.pycom.io/topic/3813/canbus-support-and-documentarion</link><guid isPermaLink="true">https://forum.pycom.io/topic/3813/canbus-support-and-documentarion</guid><dc:creator><![CDATA[kingy189]]></dc:creator><pubDate>Sun, 30 Sep 2018 01:42:57 GMT</pubDate></item></channel></rss>