MicroPython Forum

Mine is just a receiver.

A TX is some way down my long TODO list. Please don't hold your breath waiting...

For high performance applications I would recommend the Pyboard D. WiFi is offloaded to a separate chip so does not impact the CPU speed and is supremely reliable. MicroPython itself runs on "bare metal" and is fast. By contrast the ESP32 runs an underlying OS and is therefore slower. But it is the ...

It might be simplest not to use a timer: I'm not sure if there's a way to get a timer to emit an exact number of pulses. import pyb from time import ticks_us, ticks_diff def rats(): t = ticks_us() for _ in range(700): p(1) p(0) print(ticks_diff(ticks_us(), t)) executes in 6.8ms. If your stepper moto...

The rating of the wall wart tells you little. The problem is reliability. You can charge a cellphone battery even if the PSU has occasional glitches, perhaps caused by electrical noise on the mains. Hardware devices will crash. I find wall warts designed for continuous running are best - e.g. the on...

The file freesans20.py is Python sourcecode created using the font_to_py utility. It is up to you to incorporate such files as frozen bytecode in your project. If you just put the file in the filesystem and import it, it will use lots of RAM. As frozen bytecode, when you import it, it will use very ...

That is a very interesting observation, and a reason to avoid SPIRAM for some applications.

Have you used the --verify option on esptool? I have programmed ESP8285's with the following: esptool.py --port /dev/ttyUSB0 --baud 115200 write_flash --verify --flash_size=detect -fm dout 0 build/firmware-combined.bin but other (older?) chips required esptool.py --port /dev/ttyUSB0 --baud 115200 wr...

Are you sure your source of power is reliable? Some USB wall warts are OK for charging cellphones but crap for running hardware.

You need to implement fonts as frozen bytecode to conserve RAM. That is the reason for converting them to Python source: see font-to-py repo.

I think (u)asyncio has become steadily simpler to use. The history of asyncio is not pretty. It confused the hell out of me and I've been writing asynchronous code for nearly 40 years. One motive behind the tutorial was to suggest a programming style which ignored old redundant features. I will upda...