@gregcope Wondering if it might be useful to simply start a thread for everything. If I spawn an alarm in one thread, an interrupt in another and so on, I may be able to avoid the issue of blocking. The major issue is that since some of the functions I need to run can take 20 seconds or so, I don't want one to block another from running and have to wait a whole other interval for the respective functions to be run. Especially since there are multiple interrupts and one or two alarms. So would simply running a function that spawns an alarm within a separate thread make it so that the alarm itself is contained in that thread indefinitely?

@livius It features a MAX3421E USB host controller chip and USB-A port. We created this board to communicate with existing serial-over-USB (CDC, or communications device class) devices. Adding support for other USB "drivers" is a matter of understanding the USB endpoints and writing the implementation in MicroPython. Update: Check out the First look: USB Host Expansion Board by Semireg

@fsergeys Is there a particular reason you need to capture stdout/stderr vs. just writing your log straight to the file?

Ok by following this guide and using the config below I have my LoPy running through a Jupyter notebook. In kernel.json: { "argv": ["python3", "-m", "jupyter_micropython_kernel", "/dev/cu.usbmodemPy343431", "115200", "-f", "{connection_file}"], "display_name": "MicroPython", "language": "micropython" }

@ahaw021 Do you host your library somewhere? I have been running a pure C LWM2M client on bare-metal ESP32 with satisfying results. The implementation is based on https://github.com/Openhab-Nodes/libWakaamaEmb with DTLS support. I need to explore the possibility to use MicroPython as a base for LWM2M Hackathon. Cheers!

@stefan85e That is correct, the 1.17.0.b1 upgrade is for the LoPy. You do not need to ever upgrade firmware for the expansion board 2

@jhoguaman You can not. There is no OS on pycom modules. Micropython is the OS. If you build your own firmware, you can write C modules, wich you then can call from Python.

@monersss Raw LoRa is a best effort medium with absolutely no acknowledgements or retransmissions. If you want to be sure that data has been received, you will need to implement such a strategy. That involves adding frame counters (not absolutely needed in the most basic case, but it’s usually a good idea), sending back ACKs when you have received data, and resending data if you don’t get the ACK. Note that if your target scenario is not point to point but multiple senders to one receiver, LoRAWAN may be a simpler option as this can be handled by LoRaWAN. However be aware of the limitations on the band.

Found my answer after hours of looking around. Found this beautiful post on TTN regarding decoding the values of different types and what have you found here by Arjanvanb on TTN The main answer was posted on Stackoverflow by Ilya Bursov.

This is what I add into my lopy so they get a name: bluetooth.set_advertisement(name="lopy", manufacturer_data="lopy_v1") and when I look for the lopy I do this: from network import Bluetooth #import time - Dont need this part for this bt = Bluetooth() bt.start_scan(-1) while True: adv = bt.get_adv() if adv and bt.resolve_adv_data(adv.data, Bluetooth.ADV_NAME_CMPL) == 'lopy': try: conn = bt.connect(adv.mac)

When I started I first read this tutorial to understand the Python language. Not everything is available in Micropython, but you get the concept: https://docs.python.org/3/tutorial/ I looked up details uniqe to Micropython here when I found something from Python that was not working: http://docs.micropython.org/en/latest/pyboard/ For Pycom functionality documentation and examples are available here: https://docs.pycom.io/ Johan

Thanks for porting this over, great work!

Hello guys, The issue fixed in the IDF is definitely affecting us. We will merge that patch and will be available for our next release this week. Cheers, Daniel

@LoneTech This suggestion saved me, feed() was not working and then I moved it just before my loop delay and it began to work. It was probably made worse because I had a gc.collect() after feed() originally. Thanks!