AmateurRadio.com

…with Arduino.

Last time I showed you how easy it is to hook up a relay to an Arduino MCU. Without some human control, however, it is a pretty useless setup. It needs switches and the switches most used in the Arduino world are momentary push buttons. They are versatile as just by altering some code you can change a momentary switch into a toggle switch or a rotary switch. Nifty! Hooking them up is not quite straightforward, though, because they need either a pull-up resistor or a pull-down resistor. The voltages on Arduinos I/O (input/output) pins alter between two states: 0 and +5 Volt. When an I/O pin is connected to either ground (pulled down, LOW) or +5V (pulled up, HIGH) by shorting a switch, this state is easily read by the Arduino. But when the switch is not shorted the I/O pin “floats” and its state is not certain due to electrical noise; it might be anywhere between 0 and +5V. It’s difficult to tell what the Arduino will read then: either HIGH or LOW, but this is anybody’s guess. To prevent this from happening both ground and +5V are connected to the switch to make sure the I/O pin will see two clear states. To prevent damage due to high currents a 10k resistor is added.

With that out of the way and everything hooked up the fun stuff can begin.
Just like last time we first define what I/O pins we use. Apart from the relayPin we now also have a buttonPin, namely A0. In the setup we now declare that buttonPin is used for INPUT, as we already defined that the relayPin is used as an OUTPUT pin.

The part which the Arduino loops through (over and over) looks a bit more complex now. It features an “if” statement:

if (digitalRead(buttonPin) == HIGH) {
digitalWrite(relayPin, HIGH);
}

This is not so difficult as it looks. In plain English it reads: “if you read out the buttonPin and it is equal to HIGH, execute the commands that are sandwiched in between { and }“. And the single command is the same as last time: write to the relayPin and make it active, or HIGH.

But what in other cases? That is the next part, which begins with “else“.

else {
digitalWrite(relayPin, LOW);
}

In all other cases make the relayPin LOW or inactive.

The result of all this you can see in the following short video.

Better, but still not useful enough. Once we release the button our relay also deactivates. A toggle switch is what is needed in this case, so let’s change the code and make it into one.

And this is where I find joy in working with Arduinos. With just three lines of code I can change the behaviour of a push button. There are loads of examples on the web that use lots more code to achieve the same result, but by being clever it can be done far more efficiently. Discovering this gives me the same kick as working a new DXCC entity, or building a circuit which works the first time. Although it almost wrecks my brain sometimes, the reward makes it all worth it.

Let’s take a quick look at the code. If the Arduino finds that the switch is activated, the buttonPin read HIGH. Only then execute a single command…

digitalWrite(relayPin, !digitalRead(relayPin));

“Write to the relayPin and make it the opposite (!) of the state it is in when you read out the relayPin“. So when the relayPin is HIGH, make it LOW and vice versa. The exclamation mark is short for “not” or in this case “the opposite“. Even though we defined that the relayPin is used for OUTPUT, that doesn’t mean you can’t read the status of it. Genius, isn’t it?

To finish it off we add a little delay to prevent button bounce, because this will happen when you use momentary push buttons. (For Arduino purists: I know there are much better ways to combat button bounce – even hardware solutions – but for this article I’d like to keep things as simple as possible: KISS all over).

At the end of the day we now have one problem solved and our switchable loop antenna is one step closer to completion. The next problem: how to tune the loop?

6 Responses to “More Autumn Antenna Adventures….”