Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Neopixel support #16

Open
whaleygeek opened this issue Aug 28, 2017 · 1 comment
Open

Neopixel support #16

whaleygeek opened this issue Aug 28, 2017 · 1 comment

Comments

@whaleygeek
Copy link
Owner

The standard MicroPython on micro:bit has a neopixel module.

It would be great to be able to do this directly on the host machine when a bitio enabled micro:bit is connected...

import neopixel
np = neopixel.NeoPixel(pin0, 8)
np[0] = (255, 0, 0)
np.show()

@whaleygeek
Copy link
Owner Author

In particular, this means that I have to think through the package paths carefully.

Currently there is a folder called microbit that provides the proxy classes that talk to the micro:bit device. This is so that the API is identical to code you would write on a microbit.

This would imply I need a neopixel folder in the distribution, and this would have to find the microbit folder to get access to the proxy REPL interface.

I specifically want this to be a zero install 'drop the folder in and it works' experience by default.

The same will be true of other modules, like the radio module.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant