I'm building a scenic model - a diorama indeed. In fact this diorama is the reason I got interested in electronics in the first place. You see the model will have a few buildings & they'll all be lit with LEDs. There may also be some motorised gimmicks if I can get them to work. The problem was that I didn't know how to wire up LEDs, so hit Google and disappeared down an electronics rabbit hole. The original plan that was to have a simple set of circuits where each LED had a potentiometer to adjust the brightness along with a fixed resistor to protect the LED. The LEDs would be switched on and off using some slider switches that I got from an electronics surplus shop many moons ago. All would be powered from an old model railway 12V power controller I've had since I was a teenager. Yep, it's old! But that'd be too simple wouldn't it? So now I'm planning to electronicify it. Not that it needs doing of course, but it'll be more fun. The plan is to
I previously blogged about some Wi-Fi and HDMI cable related problems I had with my new Raspberry Pi 4B - here's the post . There's one more thing that I encountered while setting up the Pi that may be helpful to anyone in the same position as I was. The Raspberry Pi set up instructions explicitly say that you should set up the Pi using a wired USB keyboard and mouse, even if you intend to use wireless items later. When I read that my heart sank. Somewhere there may be a wired USB keyboard / touchpad combo around the place, providing I didn't throw it out, but could I find it? Take a wild guess. So I plugged in my Logitech wireless dongle to one of the Pi's USB 2 ports and went for broke. It worked . Phew. That's a pretty good testament to how far Linux has come when, right from the off, it recognised and worked flawlessly with a wireless UK layout keyboard and mouse. There was a time when setting up peripherals with Linux was a nightmare for the uninitiated like m