Hey @Blayden.
Very exciting! I hope the Busy Board I’m making for my kid to be ready by Christmas. 
After a lot of play testing I’ve realized that my scope was too large. Lot’s of buttons was overwhelming for the kids I tested.
I needed fewer components that did more.
For instance, a glowbit rainbow that sometimes sweeps, sometimes pulses, and sometimes flashes is better than three rainbows doing one of each.
I’m very happy with how the c++ code is coming along. I’m now building the actual box for all the buttons, dials, and leds. After that I imagine there will be 3-4 weeks of debugging.
I’ll post some photos when I’m done.
In this thread I spent a long time with Bob on a clock to trigger hardware interrupts.
The biggest lesson I took away from that was that my lack of education and was preventing me from asking good questions and giving relevant information. Things like not being able to draw a diagram of what I was making, or mistaking 1nf for infinity. After I realized I was stuck I bought the Art of Electronics by Horowitz and Hill and spent some time getting the jargon under my belt.
I did get that working in the end; but by the time I did I had also re-evaluated what I really needed and discovered there were better ways.
The point is this has taken, as usual, longer than expected. I knew when I started I was challenging myself but I had not realized that embedded systems was an entire ecosystem and industry separate to my information technology background.
Watch this space. I’ll have something to show for my efforts soon!
