The document provides guidance on coding an Arduino project using a structured methodology. It outlines 3 key steps: 1) plan the components and circuit, 2) program the circuit, and 3) test and refine the code. It then details how to structure the code, including declaring components and variables, initializing them in setup(), and controlling them in loop() using sensors and IF/ELSE statements. Well organized and commented code is emphasized for readability and troubleshooting.

1. 7th – Coding (Project)
Nestor Benavides

2. Automating something
Every project you try to create using Arduino, will be the reflection of defined
steps, make sure to follow this methodology (first think, then act):
THINK ACT
 What components do you need?
 Which sensors? Which actuators?
 Do you need specific components in specific places?
 Check pins, (+) and GND for each component.
1. Create the circuit.
 Declare the components and variables to use.
 State the sensors, actuators and serial monitor (if
required).
 Program the steps that the producto should follow.
2. Program the circuit.
 Change code and modify the circuit as many times as you
need to, until you have a perfect automated device.
3. Test the circuit and refine.

3. The code
It is necessary to understand
the whole code, remember
that it does not matter how
many components you have
in your project, you will
always use a code with one
part to declare, then a part
to start the program (void
setup) and finally, a part to
control the components as
desired (void loop).
Declare
Start
Control

4. Declare
Create space on the top of the code to establish which components you are using
and where they are connected to the Arduino. Follow the structure:
int buzzer1 = 12 ;
Variable’
s type
Variable’s
name
Arduino
connection
Semicolon
Then, create one variable per each sensor that you will use, that variable will
contain the information read by the sensor:
int LDR1reading = 0 ;
Variable’
s type
Variable’s
name (related
to the sensor)
Always
starts in 0
Semicolon

5. Looks like this
Actuators
Sensors
Variables
TIPS:
• Use the structure, first the
actuators, then the sensors
and finally the variables.
• Use short and easy to
remember names.
• Use names related to the
components that you are
using.
• Same number of sensors and
variables.

6. Start
In this section, you need to initialize the components and determine if they are
sensors or actuators, also to start the Serial Monitor.
pinMode ( buzzer1 , OUTPUT ) ;
Command Component Comma Sensor or
actuator
Semicolon
After you initialize all the components, start the Serial monitor, always using the
same code:
Serial.begin(9600);

7. Looks like this
Actuators
Sensors
Serial monitor
TIPS:
• Use the structure, first the
actuators, then the sensors
and finally the Serial monitor.
• OUTPUT = Actuators.
• INPUT = Sensors.
• The commands and variables
must be always written the
same way, capital letters and
lowercase matters.

8. Control
To control a project, always follow the same structure:
1. Make the sensor sense and store the variables.
2. Show them in the Serial monitor (useful to refine the code).
3. Create the IF/ELSE parameter to make your project take decisions and act.
IF ELSE
if (condition is true) {
action(s) to complete; }
else {
Action(s) to complete; }
If the condition is happening, then act
as required
Under any other circumstance, act as
required.

9. Control
STEP 1:
STEP 2:
Repeat these 2 steps for as many sensors as you are using in
the program.
LDR1Reading = analogRead ( LDR1 ) ;
CommandVariable Sensor to read
Serial.println ( LDR1Reading ) ;
Command Variable
Semicolon
Semicolon

10. Looks like this
TIPS:
• Be organized with your code, leave
spaces to have visual advantage.
• Check the changes of colors in the
software, they help you to know if your
capital/lowercase are fine or not.
• Keep in mind that all this is IN THE VOID
LOOP, do not write outside the { }

11. Control
STEP 3:
Complete as many ifs as you need and remember at the end to use the same
structure for the else, except the comparison part. ONLY ONE ELSE is used.
if ( LDR1Reading < 400 ) {
Command Variable Opening braceComparison Base number
digitalWrite ( buzzer1 , HIGH ) ; }
Command Component State Closing braceSemicolon

12. Looks like this
IFs
ELSE
TIPS:
• The more components you
use, the more complicated
your code will be.
• You need to know your
sensors and realize if the
readings of them are analog
or digital, before creating the
condition.
• Keep in mind that all this is IN
THE VOID LOOP, do not write
outside the { }

13. Everything looks like this
TIPS:
• Organize your code.
• Refine the code based on
the behavior of the code
(code, then test, and then
code again until you have
the result that you want).
• Be patient.