On the following website, you can find the original Arduino IDE if you need it in the future. In this book, you will be fine sticking with the Adafruit version of the IDE, since the most common original Arduino boards are also supported. The following is the link for downloading the Arduino software: https://www.arduino.cc/en/Main/Software.

The IDE is where we will be doing all of our programming. The first time you open up the IDE, it should look like Figure 1.1:

Figure 1.1: The Arduino IDE

The main white area of the IDE is blank when you open a new sketch, and this is the area of the IDE where we will write our code later on. First, we need to get familiar with the functionality of the IDE.

At the top left of the IDE, you will find five buttons. The first one, which looks like a check sign, is the compile button. When you press this button, the IDE will try to compile the code in your sketch, and if it succeeds, you will get a message in the black window at the bottom of you IDE that should look similar to this:

Figure 1.2: The compile message window

When writing code in an IDE, we will be using what is known as a third-level programming language. The problem with microprocessors on Arduino boards is that they are very hard to communicate with using their native language, and this is why third-level languages have been developed with human readable commands. The code you will see later needs to be translated into code that the Arduino board understands, and this is what is done when we compile the code. The compile button also makes a logical check of your code so that it does not contain any errors. If you have any errors, the text in the black box in the IDE will appear in red, indicating the line of code that is wrong by highlighting it in yellow. Don't worry about errors. They are usually misspelling errors and they happen a lot even to the most experienced programmers. One of the error messages can be seen in the following screenshot:

Figure 1.3: Error message in the compile window

Adjacent to the compile button, you will find the Upload button. Once this button is pressed, it does the same thing as the compile button, and if your sketch is free from errors, it will send the code from your computer to the board:

Figure 1.4: The quick buttons

The next three buttons are quick buttons for opening a new sketch, opening an old sketch, or saving your sketch. Make sure to save your sketches once in a while when working on them. If something happens and the IDE closes unexpectedly, it does not autosave, so manually saving once in a while is always a good idea.

At the far right of the IDE you will find a button that looks like a magnifying glass. This is used to open the Serial monitor. This button will open up a new window that lets you see the communication form from, and to, the computer and the board. This can be useful for many things, which we will have a closer look at in Chapter 2, Working with Sensors.

At the top of the screen you will find a classic application menu, which may look a bit different depending on your operating system, but will follow the same structure. Under File, you will find the menu for opening your previous sketches and different example sketches that come with the IDE, as shown in Figure 1.5. Under Edit, you will find different options and quick commands for editing your code. In Sketch, you can find the same functions as in the buttons in the IDE window:

Figure 1.5: The File menu

Under Tools, you will find two menus that are very important to keep track of when uploading sketches to your board. Navigate to Tools | Board and you will find many different types of Arduino boards. In this menu, you will need to select the type of board you are working with. Under Tools | Serial port, you will need to select the USB port which you have connected to your board. Depending on your operating system, the port will be named differently. In Windows, they are named COM*. On OS X, they are named /dev/tty.****:

Figure 1.6: The Tools menu

Since there may be other things inside your computer also connected to a port, these will also show up in the list. The easiest way to figure out which port is connected to your board is to:

As I mentioned earlier, we will not be using the standard Uno Arduino boards in this book, which is the board most people think of when they hear Arduino board. Most Arduino variations and clones use the same microprocessors as the standard Arduino boards, and it is the microprocessors that are the heart of the board. As long as they use the same microprocessors, they can be programmed as normal by selecting the corresponding standard Arduino board in the Tools menu. In our case, we will be using a modified version of the Arduino IDE, which features the types of boards we will be using in this book. What sets other boards apart from the standard Uno Arduino boards is usually the form factor of the board and pin layout. In this book, we will be using a board called the FLORA. This board was created with wearables in mind. The FLORA is based on the same chip used in the Arduino Leonardo board, but uses a much smaller form factor and has been made round to ease the use in a wearable context. You can complete all the projects using most Arduino boards and clones, but remember that the code and construction of the project may need some modifying.

The FLORA board

In the following Figure 1.7 you will find the FLORA board:

Figure 1.7: The FLORA board

The biggest difference to normal Arduino boards besides the form factor is the number of pins available. The pins are the copper-coated areas at the edge of the FLORA. The form factor of the pins on FLORA boards is also a bit different from other Arduino boards. In this case, the pin holes and soldering pads are made bigger on FLORA boards so they can be easily sewn into garments, which is common when making wearable projects. The larger pins also make it easier to prototype with alligator clips, which we will be using later on in this chapter as shown in Figure 1.10. The pins available on the FLORA are as follows, starting from the right of the USB connector, which is located at the top of the board in the preceding Figure 1.7:

The pins available on the FLORA are as follows, starting from the right of the USB connector, which is located at the top of the board in Figure 1.7:

• 3.3V: Regulated 3.3 volt output at a 100mA max
• D10: Is both a digital pin 10 and an analog pin 10 with PWM
• D9: Is both a digital pin 9 and an analog pin 9 with PWM
• GND: Ground pin
• D6: Is both a digital pin 6 and an analog pin 7 with PWM
• D12: Is both a digital pin 12 and an analog pin 11
• VBATT: Raw battery voltage, can be used for as battery power output
• GND: Ground pin
• TX: Transmission communication pin or digital pin 1
• RX: Receive communication pin or digital pin 0
• 3.3V: Regulated 3.3 volt output at a 100mA max
• SDA: Communication pin or digital pin 2
• SCL: Clock pin or digital pin 3 with PWM

As you can see, most of the pins have more than one function. The most interesting pins are the D* pins. These are the pins we will use to connect to other components. These pins can either be a digital pin or an analog pin. Digital pins operate only in 1 or 0, which mean that they can be only On or Off. You can receive information on these pins, but again, this is only in terms of on or off.

The pins marked PWM have a special function, which is called Pulse Width Modulation. On these pins, we can control the output voltage level. The analog pins, however, can handle information in the range from 0 to 1023. As we introduce analog sensors in Chapter 2, Working with Sensors, we will look into the differences between them in more detail.

The 3.3V pins are used to power any components connected to the board. In this case, an electronic circuit needs to be completed, and that's why there are two GND pins. In order to make an electronic circuit, power always needs to go back to where it came from. For example, if you want to power a motor, you need power from a power source connected via a cable, with another cable directing the power back to the power source, or the motor will not spin.

TX, RX, SDA, and SCL are pins used for communication, which we will have a look at later on in the book in the chapters dealing with more complex sensors. The VBATT pin can be used to output the same voltage as your power source, which you connect to the connector located at the bottom of the FLORA board shown in Figure 1.7.

In Figure 1.8 you will find the other board types we will be using in this book:

Figure 1.8: The Gemma, Trinket and Trinket pro board

In Figure 1.8, the first one from the left is the Gemma board. In the middle, you will find the Trinket board, and to the right, you have the Trinket pro board. Both the Gemma and Trinket board are based on the ATtiny85 microprocessor, which is a much smaller and cheaper processor, but comes with limitations. These boards only have three programmable pins, but what they lack in functionality, the make up for in size. The difference between the Gemma and Trinket board is the form factor, but the Trinket board also lacks a battery connector. The Trinket Pro board runs on an Atmega328 chip, which is the same chip used on the standard Arduino board to handle the USB communication.

This chip has 20 programmable pins, but also lacks a battery connector. The reason for using different types of boards in this book is that different projects require different functionalities, and in some cases, space for adding components will be limited. Don't worry though, since all of them can be programmed in the same way.

In order to make sure that you have installed your IDE correctly and to ensure your board is working, we need to connect it to your computer using a USB to USB micro cable, as show in Figure 1.9:

Figure 1.9: USB to USB micro cable

The small connector of the cable connects to your board, and the larger connector connects to your computer. As long as your board is connected to your computer, the USB port on the computer will power your board. In Chapter 3, Bike Gloves, we will take a closer look at how to power your board using batteries.

Once your board is connected to the computer, open up your IDE and enter the following code. Follow the basic structure of writing sketches:

The first line of code declares pin number 7 as an integer and gives it the name LED. An integer is a data type, and declaring the variable using the name int allows you to store whole numbers in memory. On the FLORA board, there is a small on-board LED connected to the digital pin 7. The next part is void setup(), which is one of the functions that always needs to be in your sketch in order for it to compile. All functions use curly brackets to indicate where the function starts and ends. The { bracket is used for the start, and } the bracket is used to indicated the end of the function. In void setup(), we have declared the mode of the pin we are using. All digital pins can be used as either an input or an output. An input is used for reading the state of anything connected to it, and output is used to control anything connected to the pin. In this case, we are using pin 7, which is connected to the on-board LED. In order to control this pin we need declared it as an output.

The void loop() function is where the magic happens. This is where we put the actual commands that operate the pins on the board. In the preceding code, the first thing we do is turn the led pin HIGH by using the digitalWrite()command. The digitalWrite() function is a built-in function that takes two parameters. The first is the number of the pin, in this case, we put in the variable led that has the value 7. The second parameter is the state of the pin, and we can use the HIGH or LOW shortcuts to turn the pin on or off, respectively.

Then, we make a pause in the program using the delay() command. The delay command takes one parameter, which is the number of milliseconds you want to pause your program for. After this, we use the same command as before to control the state of the pin, but this time we turn it LOW, which is the same as turning the pin off. Then we wait for an additional 1000 milliseconds. Once the sketch reaches the end of the loop function, the sketch will start over from the start of the same function and keep on looping until a new sketch is uploaded. The reset button is pressed on the FLORA board, or until the power is disconnected.

Now that we have the sketch ready, you can press the upload button. If everything goes as planned, the on-board LED should start to blink with a 1 second delay. The sketch you have uploaded will stay on the board even if the board is powered off, until you upload a new sketch that overwrites the old one. If you run into problems with uploading the code, remember to perform the following steps:

Now that we know that your IDE and board are working, we will have a look at some more code. Programming with Arduino is a fairly straightforward process, but as with any other skill, it takes some practice. You should never feel stupid if you don't understand straightaway or if you can't get something to work as it should. This is a part of the process we call prototyping. When you prototype something, you may have a clear idea of what you want to do, but not a clear plan of how to achieve this. A big part of prototyping is the process of trial and error. If you try something and it does not work, then you try something different. A common misconception is that electronics break easily. It is true that components can break if connected the wrong way, but even breaking stuff can be helpful in the process of understanding how they work. However, it is very hard to break anything by code. Again, it is possible to break the microprocessor in most Arduino boards by uploading faulty code to them, but the IDE makes this nearly impossible since it always checks your code for errors before uploading it to the board. Microprocessors are logical in the strictest sense.

When learning to program, the most important part is to learn how to debug. Debugging is simply the process of finding where the problem is. Compile errors are the most obvious, since the IDE will let you know that your sketch contains an error somewhere. However, the IDE can only check for semantic errors and it does not know what you are trying to achieve. Your sketch might compile, but it still does not do what you want it to do. The deeper your understanding of the different commands, the faster you will become in the debugging process. In this book, I will explain the different commands as they are used in the chapters, but even if we use a lot of them, we will not cover all possible commands. If you want to learn more about all the possible commands, the Arduino website has a reference list in which you can find them (http://arduino.cc/en/Reference/HomePage). This book is aimed at readers who have some experience with programming for Arduino, and it does not include an introduction to programming. With this said, you should not feel excluded if you don't know how to program, since it should be possible to follow all the projects without a deeper understanding of programming. By following the instructions and code in this book, you should be able to create your own working version of all the projects. The following sketches are examples to get you going, which includes some of the basic functions and commands.

External LEDs and blinking

Now that we've tried a really simple example with the board by itself, it's time to add some extra components:

• FLORA board
• USB to USB micro cable
• Two alligator clips
• PCB mounted LED

Tip

Downloading the example code

You can download the example code files from your account at http://www.packtpub.com for all the Packt Publishing books you have purchased. If you purchased this book elsewhere, you can visit http://www.packtpub.com/support and register to have the files e-mailed directly to you.

In this sketch example, we will use an external LED, but if you want, you can stick with the on-board LED on the FLORA board. The LED used in following Figure 1.10 is a special surface-mounted LED that is placed on a PCB. If you are using another LED, make sure to pair it with the right resistor. In the case of the custom LED found in Figure 1.6, the resistor is mounted on a PCB (printed circuit board). These LEDs are made with wearables in mind, and you can find them in most specialized electronic stores:

Figure 1.10. The LED connected to the board using alligator clips

To connect the LED to the board, we used alligator clips. Alligator clips are normal wires with metal clips at the end that are great for prototyping, and work especially well with wearable Arduino boards like the FLORA. LEDs have a positive and a negative side to them. In the case of the LED in Figure 1.10, these are marked on the PCB with a + sign for the positive and a - sign for the negative side. The positive side connects to pin D12 on the FLORA board, and to complete the circuit, the negative side connects to GND.

Different speed blinking

The following sketches show how to blink the LED at different speeds, using the for loops:

int led = 12; //declares a variable called led connected to pin 12

void setup() {
  pinMode(led, OUTPUT); //declares led as an output pin
}

void loop() {
//start looping until the counter is bigger then 5
  for(int i=0; i<5; i++){
    digitalWrite(led, HIGH); //turn the led on
    delay(1000); //wait for a bit
    digitalWrite(led, LOW); //turn the led off
    delay(1000); //wait some more
  }
//start looping until the counter is bigger then 5
  for(int j=0; j<5; j++){
    digitalWrite(led, HIGH); //turn the led on
    delay(500); //wait for a bit
    digitalWrite(led, LOW); //turn the led off
    delay(500); //wait some more
  }
//start looping until the counter is bigger then 5
  for(int k=0; k<5; k++){
    digitalWrite(led, HIGH); //turn the led on
    delay(100); //wait for a bit
    digitalWrite(led, LOW); //turn the led off
    delay(100); //wait some more
  }
}

In this sketch, we use three different for loops. In the for loop, a counter, end condition, and counter increment is declared. All the counters in this sketch start on 0, and as long as the counter is smaller than 5, the for loop will keep on looping. For every time the for loop makes a loop, the counter is increased by one. Inside the for loop, the LED is first turned on and then there is a delay. The delay time is the difference between the three for loops.

Then, the LED is turned off and there is a new delay. Once the first loop has met the end condition, the second loop takes over, and so on. The for loops are good if you know you want to do a certain thing a certain number of times.

As you can see in the preceding sketch, the procedure for turning the LED on and off is the same for all of the for loops. This is a perfect opportunity to introduce a function into your code. Functions help save memory space. In the case of the sketch we are working with, memory space will not become a problem since the sketch is very small. However, as you progress, sketches will become bigger and bigger, and memory space may become a problem. Depending on the board you are using, there is a limit to how big you can make you sketches. Optimizing your code helps save space, but is also good coding practice, since it gives you a better overview of your code:

int led = 12;

void setup() {
  pinMode(led, OUTPUT);
}

void loop() {
  for(int i=0; i<5; i++){
    blinkLed(1000); //call the function and add the delay time
  }
  for(int j=0; j<5; j++){
    blinkLed(500); //call the function and add the delay time
  }
  for(int k=0; k<5; k++){
    blinkLed(100); //call the function and add the delay time
  }
}

/*declares the function blinkLed and adds a parameter that needs to be included with the use of the function*/
void blinkLed(int delayTime){
digitalWrite(led, HIGH); //turn the led on
    delay(delayTime); //wait for a bit
    digitalWrite(led, LOW); //turn the led off
    delay(delayTime); //wait some more
}

The blinkLed function has been declared so it takes a parameter, which is delayTime. This variable is then used inside the function to set the speed of the blinking.