Book Image

C Programming for Arduino

By : Julien Bayle
Book Image

C Programming for Arduino

By: Julien Bayle

Overview of this book

Physical computing allows us to build interactive physical systems by using software & hardware in order to sense and respond to the real world. C Programming for Arduino will show you how to harness powerful capabilities like sensing, feedbacks, programming and even wiring and developing your own autonomous systems. C Programming for Arduino contains everything you need to directly start wiring and coding your own electronic project. You'll learn C and how to code several types of firmware for your Arduino, and then move on to design small typical systems to understand how handling buttons, leds, LCD, network modules and much more. After running through C/C++ for the Arduino, you'll learn how to control your software by using real buttons and distance sensors and even discover how you can use your Arduino with the Processing framework so that they work in unison. Advanced coverage includes using Wi-Fi networks and batteries to make your Arduino-based hardware more mobile and flexible without wires. If you want to learn how to build your own electronic devices with powerful open-source technology, then this book is for you.
Table of Contents (21 chapters)
C Programming for Arduino
About the Author
About the Reviewers

Types manipulations

When you design a program, there is an important step consisting of choosing the right type for each variable.

Choosing the right type

Sometimes, the choice is constrained by external factors. This happens when, for instance, you use the Arduino with an external sensor able to send data coded as integers in 10 bits (210 = 1024 steps of resolution). Would you choose byte type knowing it only provides a way to store number from 0 to 255? Probably not! You'll choose int.

Sometimes you have to choose it yourself. Imagine you have data coming to the board from a Max 6 framework patch on the computer via your serial connection (using USB). Because it is the most convenient, since you designed it like that, the patch pops out float numbers encapsulated into string messages to the board. After having parsed, cut those messages into pieces to extract the information you need (which is the float part), would you choose to store it into int?

That one is a bit more difficult to answer...