You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Just me, Kassandra Perch (kperch on the githubz)
my email for all intents and purposes (incl. reimbursement) is kassandra [at] kassandraperch.com
Concept
I want to create an RGB LED grid with a BeagleBone Black and the npm module I wrote (open-pixel-control). Though I'm considering using fadecandy and that npm module. We'll see - it in theory should work either way, but I know for sure it works with BBB.
This panel will have some built-in patterns and animations (pixel art comes to mind), but I want to create a way to let people put their own designs on the board. Depending on how far I get through development, that could be a web app that submits to a REST API, or that could be people emailing me JSON files, or snippets of JS. I want people to be able to submit their pixel art to display, and I'll find a way to do so.
Tech Specs
Here's the plan so far to fit the budget:
a 12 x 20 grid of evenly spaced "neopixel" RGB LEDs, run via a beaglebone black board (or fadecandy board) and Node.JS. I'll need a power outlet - the BBB needs a power source, and the grid of lights will be powered by a 5V/10A switching power adapter. Other than that wifi would be nice but not necessary - new designs can be uploaded with a USB cable.
The way I'll go about it seems to be the most economical- buy a bunch of meter-long strips, then cut and re-solder them in a grid format, and glue/tape them to a supporting board. If the grid gets larger, I'll add connectors between multiple boards.
I have plans to obtain an accelerometer and have at least one design use the accelerometer and react to it.
A quick ballpark of the measurements of the panel leave it a little over 26" x 15.5", but I can go bigger -or- more dense pixels with a bigger budget. As it stands, I'm accounting for a $100 reimbursement and going out-of-pocket a little.
The web app I'm thinking of would be a series of pixels that you can change the colors of- I'm seeing if there's any painting programs I can use that are open-source JS. If not, I'll just have people email me JSON files with arrays of pixels, and I'll show them. Still fleshing out the submission process.
Implementation Plan
I've basically broken this project down into several stages - from a minimum to an ideal. I'll just keep iterating from minimum up until I run out of time.
Minimum Milestone - Panel w/submittable designs
I'll have a 20 x 12 panel of lights, and I can upload people's drawings manually through the BBB. The panel will have a button that lets you cycle through the designs.
Estimate time to completion: 1 week after I order parts
Milestone 2 - Accelerometer
One of the designs on the panel will react to an attached accelerometer- I'll make it accessible via a glove or stick.
Estimate time: a couple of days beyond minimum
Milestone 3 - Web App to submit designs
Users will be able to submit arrays of pixels in a JSON format, at a URL. They'll be curated for appropriateness, then tossed into a queue for the panel to cycle through.
Estimate time: about a week? beyond milestone 2.
Prereq: wifi available at show.
Milestone 4 - More Sensors
I haven't thought this one through, since I don't know I'll get to it. But I could add more sensors in (proximity, light, buttons) and have the panel react to those in different designs.
Estimate: ???
Display contents
I was planning on documenting the build with photos and notes. If you'd like, I can include a paper version of the log to sit at the table with the display, to show folks what went into the project.
All the code will be open sourced with an MIT license.
I'll add a comment before the deadline with some sketches, and more detailed info. If you have any questions, leave a comment and I'll do my best to answer them quickly.
The text was updated successfully, but these errors were encountered:
If/When you're ready for reimbursement, just email the receipts(can be photos if need be) and the email address we can refund you via PayPal to [email protected]
We're going to have an email list for Makers that will probably have an email or two go out regarding logistics of setup and what we can do to help make this process better for you. Thanks!!!
Submitters
Just me, Kassandra Perch (kperch on the githubz)
my email for all intents and purposes (incl. reimbursement) is kassandra [at] kassandraperch.com
Concept
I want to create an RGB LED grid with a BeagleBone Black and the npm module I wrote (open-pixel-control). Though I'm considering using fadecandy and that npm module. We'll see - it in theory should work either way, but I know for sure it works with BBB.
This panel will have some built-in patterns and animations (pixel art comes to mind), but I want to create a way to let people put their own designs on the board. Depending on how far I get through development, that could be a web app that submits to a REST API, or that could be people emailing me JSON files, or snippets of JS. I want people to be able to submit their pixel art to display, and I'll find a way to do so.
Tech Specs
Here's the plan so far to fit the budget:
a 12 x 20 grid of evenly spaced "neopixel" RGB LEDs, run via a beaglebone black board (or fadecandy board) and Node.JS. I'll need a power outlet - the BBB needs a power source, and the grid of lights will be powered by a 5V/10A switching power adapter. Other than that wifi would be nice but not necessary - new designs can be uploaded with a USB cable.
The way I'll go about it seems to be the most economical- buy a bunch of meter-long strips, then cut and re-solder them in a grid format, and glue/tape them to a supporting board. If the grid gets larger, I'll add connectors between multiple boards.
I have plans to obtain an accelerometer and have at least one design use the accelerometer and react to it.
A quick ballpark of the measurements of the panel leave it a little over 26" x 15.5", but I can go bigger -or- more dense pixels with a bigger budget. As it stands, I'm accounting for a $100 reimbursement and going out-of-pocket a little.
The web app I'm thinking of would be a series of pixels that you can change the colors of- I'm seeing if there's any painting programs I can use that are open-source JS. If not, I'll just have people email me JSON files with arrays of pixels, and I'll show them. Still fleshing out the submission process.
Implementation Plan
I've basically broken this project down into several stages - from a minimum to an ideal. I'll just keep iterating from minimum up until I run out of time.
Minimum Milestone - Panel w/submittable designs
I'll have a 20 x 12 panel of lights, and I can upload people's drawings manually through the BBB. The panel will have a button that lets you cycle through the designs.
Estimate time to completion: 1 week after I order parts
Milestone 2 - Accelerometer
One of the designs on the panel will react to an attached accelerometer- I'll make it accessible via a glove or stick.
Estimate time: a couple of days beyond minimum
Milestone 3 - Web App to submit designs
Users will be able to submit arrays of pixels in a JSON format, at a URL. They'll be curated for appropriateness, then tossed into a queue for the panel to cycle through.
Estimate time: about a week? beyond milestone 2.
Prereq: wifi available at show.
Milestone 4 - More Sensors
I haven't thought this one through, since I don't know I'll get to it. But I could add more sensors in (proximity, light, buttons) and have the panel react to those in different designs.
Estimate: ???
Display contents
I was planning on documenting the build with photos and notes. If you'd like, I can include a paper version of the log to sit at the table with the display, to show folks what went into the project.
All the code will be open sourced with an MIT license.
I'll add a comment before the deadline with some sketches, and more detailed info. If you have any questions, leave a comment and I'll do my best to answer them quickly.
The text was updated successfully, but these errors were encountered: