I really, really
want to keep it down to a single processor.
But but but but I wanna double the POWAAAAHHHHHHH.
So what's the plan?
At the moment, I'm not 100% sure. There are other steps being worked on at the same time. I tend to jump back and forth between them on any given day, or even time of day.
For now the system works by storing everything in PROGMEM, within the limitations of the available SRAM. There are several different steps I'm trying to solve here. In the order of importance:
- research batteries. In order for this to work properly, I need a 5V-6V, rechargeable battery with a large mAh *
- add USB charging circuit to the controller
- add some sort of communication between the two batons so they are always in sync
- read (next) dataset from SD without impeding the current, running display
- design/finish controller
- fit everything inside of a 3/4" inner diameter tube
- available length to put battery and controller is between 3-3.5"
- I forgot: eventually incorporate a way to detect rotation speed and direction to display "static" images
The LED PCBs are getting wrapped up today and sent off to the manufacturer. LED drivers will be arriving some time next week. I need to ficus on the whole battery debacle and the controller itself. After that it's all software which I can do on a 2nd revision if needed.*
Battery is the biggest hurdle at this point. With 48 pixels per side, four sides, that's a lot of mAh to content with. At full blast, a single side will pull 48 * 3 * 18mA = 2.88A. Ideally I'd have a battery that can provide at least twice that. I'm not concerned about driving all four sides at full blast (11.52A) because honestly there won't ever be a moment where everything is on full blast, but I's like to account for at least twice the amount needed for one strip.