You have found or designed a circuit, and it’s time to build a permanent version of it. You could design and order (or make) a printed circuit board, but that will cost money and/or time. It also makes changes and corrections difficult. The obvious alternative: Implement the circuit on one or several prototyping boards. So, how do you go about building on a protoboard? I’ll describe a sequence of steps here.
Are you bored with conventional two-dimensional circuit layouts, or looking for a way to add an artistic flair to your next project? I’ve taken point-to-point construction style a step further by making it self-supporting, which opens up a wide range of physical circuit topologies. (Point-to-point construction usually uses supporting structures like terminal strips that are functional but not pleasing to the eye.) I call this construction style the copper cobweb. Here’s how to do it.
In the previous installment, we discussed the Five Program Steps and how we can use those five steps to organize our thoughts about writing programs. In this article, we’ll discuss the format that the Arduino Integrated Development Environment (IDE) requires for your program to execute in the IDE. We’ll then examine how the IDE allows us to easily organize a program using the Five Program Steps.
An RTOS (Real Time Operating System) is a software component that lets you rapidly switch between different running sections of your code. Think of it as having several loop() functions in an Arduino sketch where they all run at the same time.
Most of you have at one time or another thought about designing your own electronics. The thing stopping many of you is the fact that you realize you’re not a “real” graduate engineer. Well, so what? You don’t have to have an EE degree to design. You can do your own design with a little direction. Here’s my approach to it, so you can give it a try.
Most of us have invested some time in learning those things we want or need to do. Learning how to program is no different, and it can be an extremely satisfying endeavor. Seeing a device respond to code you wrote is, well, intoxicating in a good way. My goal is to create an interest in exploring microcontrollers and encourage you into investing $5 and some of your time into that exploration. I honestly think you'll enjoy the journey.