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
Credits
About the Author
Acknowledgement
About the Reviewers
www.PacktPub.com
Preface
Index

Summary


This chapter taught us how to deal with Arduino using Max 6.

We learnt a bit more about some usual techniques in Max 6, and we practiced some concepts previously learnt in this book. Obviously, there is more to learn in Max 6, and I'd like to give you some good pointers for better learning.

Firstly, I'd suggest you read all the tutorials, beginning with those about Max, then about MSP, and then about digital sound, and at last about Jitter if you are interested in visuals and OpenGL. That sounds obvious but I still have two or three persons a day asking me where to begin Max 6 from. The answer is: tutorials.

Then, I'd suggest you design a small system. Less is definitely more. A small system provides easy ways to maintain, modify, and support. Using comments is also a nice way to quickly remember what you tried to do in this or that part.

Lastly, patching a bit everyday is the real key to success. It takes time, but don't we want to become masters?