Your most important switcher runtime features at your fingertips - leave the rest to your laptop! The C51 control panel gives you an array of buttons for bus selection, cut, auto, keyers or whatever ATEM feature is important to you during your live production.
We are creating an 8x8 matrix of RGB LED buttons. SparkFun sells a 4x4 button pad and circuit board for this. We're going to connect four of those together to make an 8x8 grid. When you press a button, it will cycle through 8 colors: red, yellow, green, cyan, blue, purple, black and white.
It would be cool if you could save these images that you make, and then show them as a slideshow, although that will be a secondary goal that we'll shoot for only after we get the LEDs and buttons working in the first place. The Arduino has 512 bytes of EEPROM memory (which will not be lost when you turn off the board.) You can read and write to this with the EEPROM functions. This would allow us to store 512/64 = 8 images.
I am unsure at this point whether we can run the 8x8 leds with one LED driver per color, or if we'll need one LED driver per 4x4 board. I think it depends on how the boards are wired. Since the drivers are not as cheap as I thought, it is kind of important that we figure this out soon. Or we could just order 16 of them and plan on adding them to the pool of available electronics, since they'll be useful for something else some day anyway.
Haven't posted on this project in a while, but there have been some developments.
I determined that the reason I wasn't seeing anything at all was because I had inadvertently grounded one of the output pins on the receiver. Whoops, I figured it would be something stupid like that.
However, that did not immediately solve my problems. Luckily, I was working in an electronics lab, where there was some handy equipment like an oscilloscope and an RF spectrum analyzer. Using the oscilloscope to monitor the receiver, it quickly became clear that there were some interesting timing issues to resolve. The receiver kept getting out of sync with the transmitter, which was characterized by a slowly rising voltage on the output pin. It took a half-cycle for the receiver to lock on to the transmitter's signal when it first starts, and if the transmitter was silent for longer than ~100ms, the receiver would lose its lock. This basically means I would have to work pretty hard to keep them in sync.
After that little experiment, I decided to look around for some alternative wireless modules that would do some of the lower-level signal processing for me, so I could focus on the main goal of the project. Craig Hickman told me he has successfully used the xbee modules in the past. These are relatively cheap ($19 each) modules which can both transmit and receive serial data.
Best of all, the xbees have a built-in ADC converter! This pretty much means all the hard work is done for me, and I don't need an Arduino in the transmitter at all! I can connect the analog output of the Ultrasonic sensor directly to the xbee module. This data will be transmitted serially to the receiving xbee module. The receiver will automatically convert that data to a PWM signal! I can then read the PWM signal on the Arduino. Since the receivers will be sending PWM instead of serial, it will be super easy to connect three of these to one Arduino, avoiding the problem of rigging up additional serial ports on the Arduino, or coordinating three transmitters sending to one receiver.
The only remaining question I have is: will I need to do some sort of conversion to step up the 3.3v pwm value from the xbee to the 5v arduino on the receiving end?