MicroPython Forum (Archive)

So I tried to make a quick and dirty mockup of such a PCB in Fritzing (http://fritzing.org). The first problem I had is that the WROOM-02 board is too wide to fit between pyboard's pins. So I used an ESP-12 module instead, which has the same pins, but is much smaller. It looks something like this: p...

I am not capable of designing board layouts, maybe someone is keen on providing (and open-source) board designs for a ESP-WROOM-02 based board with a full or half pyboard foorprint? I can help you with that, perhaps you could start a separate thread where we could discuss how exactly such a board w...

I think that in the true UNIX fashion, all those pins are exposed as files in the /dev subsystem, so you should be able to control them using regular file operations. Then again, not sure if this is the most efficient way of doing it.

I'm not sure if it helps, but you can set a timeout on the socket itself.

That's what you get for using naked excepts. Your code is throwing an exception, and you can't even see it. If you correct this, such that only the i2c operation is in try-except, and you only catch the OSError exception, you will see the problem.

Really hard to say anything without seeing the code.

However, did you know that the micro:bit has a library for neopixels built-in?

As far as I know that's the plan eventually, but some considerable cleanup of the related code needs to happen first, see https://github.com/micropython/micropython/pull/2140 for some discussion.

I have started a dev manual on readthedocs some time ago, but no time to actually write there much. I guess I will try to write it in small fragments.

Yes, it's no longer necessary to edit your _boot.py, you as you can now unmount the filesystem.

A quick-and-dirty dirty driver for the SHARP GP2Y0E03 I²C distance sensor. Code at https://bitbucket.org/thesheep/micropython-gp2y0e03/src

Example usage: