There are many new features in the pipeline, it’s all about whether you want to try them out in your test builds.

Adam and Matthew recently were featured at an event that helps promote STEM for women in Africa. Their Blinky POV kit was featured and has been built all of the world. 10s of thousands have now been sold!

Another popular W&L product is the video game shield, which uses Wii nunchucks to control a B&W video output.

The nunchuck uses i2c, but the problem is they’re always at the same address since they’re normally connected to a Wii controller.

Comments

Actually the Wayne and Layne blinky programmer inspired a kit of mine I made for a soldering workshop we ran two years in a row at Boston University. It was for an outreach program for girls in tech called Artemis. It is an audio synthesizer/sequencer kit and you can program in different waveforms (you program in a set of harmonics) and you can also send sequences. The big difference from the screen programming from Wayne and Layne is we went with a single detector and encoded the clock in one stream; however, I ran into so many of the same problems.

I am working on simplifying the design a little more: Currently it uses a 12-bit DAC for a variety of reasons, but that adds quite a bit to the cost… I am looking to move to PWM and There are some size limits and button things I am working on trying to reduce and possibly move to using cap touch buttons or something…

I haven’t looked into the blinky thing yet (diagram, etc.) but, about the problem with the programming via the monitor, would adding a simple analog filter at the front end of the detector solve some of these issues?

I personally think that designing to be compatible with as many screen technologies as possible is good thinking… like more into the real world.