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

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

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.

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): # "result" is the parameter in form of 2 element long tuple # "peer" is the Peer which the message has been sent to # "sent" is a boolean showing whether the message could be sent peer, sent = result mac = peer.addr() if(sent == False): print("Sending message to %s failed!" % binascii.hexlify(mac)) else: print("Message sent to: %s" % (binascii.hexlify(mac))) # The callback to be registered when a message has been received def espnow_rx(result): # "result" is the parameter in form of 3 element long tuple # "mac" is the MAC address of the sender # "peer" is the Peer which the message has been received from. If message has been received from a not registered Peer this parameter is None # "msg" is the payload from the received message mac, peer, msg = result if(peer is not None): print("Message received from %s with content: %s" % (binascii.hexlify(mac), msg)) peer.send("Sending back an answer") # 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("112233445566") # Send a message dedicated to the Peer p.send("My Message") # Sending 1 message to all Peers which are registered ESPNOW.send(None, "Hello all Peers!")

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

@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

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

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.

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

@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

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

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

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

@geoff-white : guess we'll find out.

Ill raise this internally. seems like a good idea.