Scratch 4 Arduino

From Vision - Multimedia Education

(Difference between revisions)
Jump to: navigation, search
Line 4: Line 4:
|}
|}
-
 
+
<br/>''This Translation its in WIP state, need some revisions and things to finish&nbsp;:)''
-
''This Translation its in WIP state, need some revisions and things to finish :)''
+
{{Organization_Citilab}}
{{Organization_Citilab}}
== What is it&nbsp;? ==
== What is it&nbsp;? ==
-
[[Image:S4ahardsoft.JPG|thumb|right|250px|Scratch 4 arduino and arduino board]]
+
 
-
S4A is a Scratch modification that supports simple programming of the Arduino open source hardware platform. It provides new blocks for managing sensors and actuators connected to Arduino. There is also a sensor report board similar to the PicoBoard.
+
[[Image:S4ahardsoft.JPG|thumb|right|250px]] S4A is a Scratch modification that supports simple programming of the Arduino open source hardware platform. It provides new blocks for managing sensors and actuators connected to Arduino. There is also a sensor report board similar to the PicoBoard.
It has been created to attract people to the programming world. The goal is also to provide a high level interface to Arduino programmers with functionalities such as interacting with a set of boards through user events.
It has been created to attract people to the programming world. The goal is also to provide a high level interface to Arduino programmers with functionalities such as interacting with a set of boards through user events.
 +
Line 20: Line 20:
Scratch is an opensource programming environment oriented for initiate kids and youngsters in the world of programming. The programming language vinculated at Scratch’s interface it’s a simple language with the fundamental syntaxis of programming, with a lot of instructions (embedded in blocks) for make multimedia projects, like animations or games. You can drag and drop these blocks for build your program like a puzzle.
Scratch is an opensource programming environment oriented for initiate kids and youngsters in the world of programming. The programming language vinculated at Scratch’s interface it’s a simple language with the fundamental syntaxis of programming, with a lot of instructions (embedded in blocks) for make multimedia projects, like animations or games. You can drag and drop these blocks for build your program like a puzzle.
 +
<br/>[[Image:Scracth code.JPG|thumb|left|250px]]
-
[[Image:Scracth_code.JPG|thumb|left|250px|Example of Scratch code.]]
 
=== What is Arduino? ===
=== What is Arduino? ===
-
Arduino is a tool for making computers that can sense and control more of the physical world than your desktop computer. It's an open-source physical computing platform based on a simple microcontroller board, and a development environment for writing software for the board.
+
Arduino is a tool for making computers that can sense and control more of the physical world than your desktop computer. It's an open-source physical computing platform based on a simple microcontroller board, and a development environment for writing software for the board. Arduino can be used to develop interactive objects, taking inputs from a variety of switches or sensors, and controlling a variety of lights, motors, and other physical outputs. Arduino projects can be stand-alone, or they can be communicate with software running on your computer (e.g. Flash, Processing, MaxMSP.) The boards can be assembled by hand or purchased preassembled; the open-source IDE can be downloaded for free. The Arduino programming language is an implementation of Wiring, a similar physical computing platform, which is based on the Processing multimedia programming environment.
-
Arduino can be used to develop interactive objects, taking inputs from a variety of switches or sensors, and controlling a variety of lights, motors, and other physical outputs. Arduino projects can be stand-alone, or they can be communicate with software running on your computer (e.g. Flash, Processing, MaxMSP.) The boards can be assembled by hand or purchased preassembled; the open-source IDE can be downloaded for free.
+
 
-
The Arduino programming language is an implementation of Wiring, a similar physical computing platform, which is based on the Processing multimedia programming environment.
+
== What can I do with it&nbsp;? ==
== What can I do with it&nbsp;? ==
-
Promove kids or youngsters to program and build his own inventions.
+
Promove kids or youngsters to program and build his own inventions. Teach programming to anyone in a funny and easy way. Learn the basics of electronics. Make an introduction to Arduino, to people who didn’t have any contact with electronics or computer programming world.
-
Teach programming to anyone in a funny and easy way.
+
 
-
Learn the basics of electronics.
+
-
Make an introduction to Arduino, to people who didn’t have any contact with electronics or computer programming world.
+
Line 40: Line 37:
The uses are up to your imagination, but here are some examples that we used and you can replicate.
The uses are up to your imagination, but here are some examples that we used and you can replicate.
 +
Line 45: Line 43:
Anyone interested of electronics or programming and want to learn more or teach.
Anyone interested of electronics or programming and want to learn more or teach.
 +
== What do I need&nbsp;? ==
== What do I need&nbsp;? ==
-
*A board of Arduino, there are different models, the newest is Arduino Uno, but any one should work.  
+
*A board of Arduino, there are different models, the newest is Arduino Uno, but any one should work.
*A computer, with Linux, Windows or Mac.
*A computer, with Linux, Windows or Mac.
*Some electronic or robotic components, that you can buy or just save from old toys or electronic devices.
*Some electronic or robotic components, that you can buy or just save from old toys or electronic devices.
 +
Line 57: Line 57:
Basic Arduino and electronic knowledge of the components you are going to use. Or you can find how to connect them to the Arduino board or what they need for work,in this url: http://arduino.cc/en/Tutorial/HomePage , all information and schematics for how connect and work with all the basic components, like switches, leds, infraredsenors, servos, etc, is also there.
Basic Arduino and electronic knowledge of the components you are going to use. Or you can find how to connect them to the Arduino board or what they need for work,in this url: http://arduino.cc/en/Tutorial/HomePage , all information and schematics for how connect and work with all the basic components, like switches, leds, infraredsenors, servos, etc, is also there.
 +
Line 64: Line 65:
*Arduino: http://arduino.cc/en/Main/Software (The drivers come with the installer)
*Arduino: http://arduino.cc/en/Main/Software (The drivers come with the installer)
 +
Line 71: Line 73:
http://arduino.cc/en/Guide/HomePage
http://arduino.cc/en/Guide/HomePage
 +
Line 76: Line 79:
We provide some examples of what can be done, but as we said they are just exemples, what you can do only its limited by imagination.
We provide some examples of what can be done, but as we said they are just exemples, what you can do only its limited by imagination.
 +
Line 81: Line 85:
In this exemple we are going to explain how to build a robot made with one arduino board and two continuos rotation servomotors, controlled by another board with and acceleremeter, two leds and two botons.
In this exemple we are going to explain how to build a robot made with one arduino board and two continuos rotation servomotors, controlled by another board with and acceleremeter, two leds and two botons.
 +
==== What do we need? ====
==== What do we need? ====
-
 
'''Robot:'''
'''Robot:'''
Line 94: Line 98:
*1 x USB cable: http://www.sparkfun.com/products/512
*1 x USB cable: http://www.sparkfun.com/products/512
-
 
+
<br/>'''Remote Controler:'''
-
'''Remote Controler:'''
+
*1 x Arduino board: http://www.sparkfun.com/products/9950
*1 x Arduino board: http://www.sparkfun.com/products/9950
Line 106: Line 109:
-
====How to do it?====
 
-
Before starting with the exercise, we are going to make some tests for see how works both servos and accelerometer.
+
==== How to do it? ====
-
In the first exemple we need to plug the accelerometer to the Arduino board, using this model:
+
 +
Before starting with the exercise, we are going to make some tests for see how works both servos and accelerometer. In the first exemple we need to plug the accelerometer to the Arduino board, using this model:
-
[[File:Accelerometer_bb.png | center]]
+
<br/>[[Image:Accelerometer bb.png|center|Accelerometer bb.png]]
 +
<br/>The pins of the accelerometer for the power are GND and VDD, so we have to connect them to the board at GND and VDD at 5v. Pins Z, Y and X must be plugged at analogic 0, 1 and 2 respectively. This ones correspond to the three-dimensional coordinate axes ZYX (Z height, depth Y and X width) as you can see printed on it. The diagram below will clarify this concept:
-
The pins of the accelerometer for the power are GND and VDD, so we have to connect them to the board at GND and VDD at 5v. Pins Z, Y and X must be plugged at analogic 0, 1 and 2 respectively. This ones correspond to the three-dimensional coordinate axes ZYX (Z height, depth Y and X width) as you can see printed on it. The diagram below will clarify this concept:
+
<br/>[[Image:Acelerometro ejes.png|center|Acelerometro ejes.png]]
 +
<br/>The values given by the sensors of the accelerometer of every axis vary from 446 to 576 aprox. This means: If we take the board horitzontaly like we have it in the draw (leaving the Usb at Left, and Accelerometer at right)and we turn it clockwise 270 degrees (until usb its looking down and the accelerometer up) The y Axis will give us its minimum vale and should be above 446. if wereverse the movement, (USB above, accelerometer below), Will reach his maximum value and give us 576. The X axis will not have changed almost everything in this process, and if we had the board parallel to the ground, we will return a value of 511 roughly intermediate. Then a small theoretical calculation of this value:
-
[[File:Acelerometro ejes.png | center]]
+
<br/>''576-446 = 130''
-
 
+
-
 
+
-
The values given by the sensors of the accelerometer of every axis vary from 446 to 576 aprox. This means: If we take the board horitzontaly like we have it in the draw (leaving the Usb at Left, and Accelerometer at right)and we turn it clockwise 270 degrees (until usb its looking down and the accelerometer up) The y Axis will give us its minimum vale and should be above 446. if wereverse the movement, (USB above, accelerometer below), Will reach his maximum value and give us 576. The X axis will not have changed almost everything in this process, and if we had the board parallel to the ground, we will return a value of 511 roughly intermediate. Then a small theoretical calculation of this value:
+
-
 
+
-
 
+
-
''576-446 = 130''
+
''130: 2 = 65''
''130: 2 = 65''
Line 130: Line 128:
'''576-65 = 511 (or 446 + 65 = 511)'''
'''576-65 = 511 (or 446 + 65 = 511)'''
 +
<br/>In the exercise the first thing to do it's "calibrate" these values. so we gonna store these values in two variables. In this exercice we dont need the Z axis value. The calibration must be done with the board vertically, leaving the usb up and the accelerometer down.
-
In the exercise the first thing to do it's "calibrate" these values. so we gonna store these values in two variables. In this exercice we dont need the Z axis value. The calibration must be done with the board vertically, leaving the usb up and the accelerometer down.
+
<br/>[[Image:Sa1.PNG|center|Sa1.PNG]]
-
 
+
<br/>Create two variables AxisY and AxisX for continusly store the values of axis y (analog 2) and axis X (analog 3. The value of Axis Y will have its minimum value. we subtract this value which gives about 0. We will do the same with the X axis subtracting the value intermediate, as will be parallel to the ground.
-
[[File:Sa1.PNG | center]]
+
-
 
+
-
 
+
-
Create two variables AxisY and AxisX for continusly store the values of axis y (analog 2) and axis X (analog 3. The value of Axis Y will have its minimum value. we subtract this value which gives about 0. We will do the same with the X axis subtracting the value intermediate, as will be parallel to the ground.
+
For what we need every Axis? As we know the cordinate system of scratch in regarding the direction of an object varies somewhat with respect to normal:
For what we need every Axis? As we know the cordinate system of scratch in regarding the direction of an object varies somewhat with respect to normal:
 +
<br/>[[Image:PCS.png|center|PCS.png]]
-
[[File:PCS.png | center]]
+
<br/>So we are gonna use the X axis for control the threshold 0, To know when switch between negative to positive and Y axis to vary the direction of the object.How does not match the value of the Y-axis accelerometer with the direction of the scratch, we must do a small conversion, that is, if we turn the board to the right we see that the variable Y takes a value About 65 (which it confirms the calculation we have done before), and Scratch the right equals 90, so:
 +
<br/>'''90 / 65 = 1.384615385 (1.4 rounding)'''
-
So we are gonna use the X axis for control the threshold 0, To know when switch between negative to positive and Y axis to vary the direction of the object.How does not match the value of the Y-axis accelerometer with the direction of the scratch, we must do a small conversion, that is, if we turn the board to the right we see that the variable Y takes a value About 65 (which it confirms the calculation we have done before), and Scratch the right equals 90, so:
+
<br/>This is the factor that we use to pass the value of the Y axis in the direction Scratch. Please note that this factor is valid when the value of X axis is greater than 0, ie, when the board pointing to the right. If that points to the left, we will use the same factor but negative:
 +
<br/>[[Image:S4a02.png|center|S4a02.png]]
-
'''90 / 65 = 1.384615385 (1.4 Rounding)'''
+
<br/>We also added a block to move the object.
-
 
+
<br/>'''Example 2: Robot Controled with keyboard'''
-
This is the factor that we use to pass the value of the Y axis in the direction Scratch. Please note that this factor is valid when the value of X axis is greater than 0, ie, when the board pointing to the right. If that points to the left, we will use the same factor but negative:
+
-
 
+
-
 
+
-
[[File:S4a02.png | center]]
+
-
 
+
-
 
+
-
We also added a block to move the object.
+
-
 
+
-
 
+
-
'''Example 2: Robot Controled with keyboard'''
+
In the following example we will control the robot with the keyboard. The assemble scheme will be the following:
In the following example we will control the robot with the keyboard. The assemble scheme will be the following:
 +
<br/>[[Image:Servomotors bb.png|center|Servomotors bb.png]]
-
[[File:Servomotors_bb.png | center]]
+
<br/>We need to connect each servo at (5V) and to the ground (GND) and one connected to the pin 4 and the other to the pin 7, they will recive the signal form the board and the program.
-
 
+
-
 
+
-
We need to connect each servo at (5V) and to the ground (GND) and one connected to the pin 4 and the other to the pin 7, they will recive the signal form the board and the program.
+
When we got it, we can start to program. first we have to create a new project, (File> New)put two blocs of motors and then we select the pins where we have it connected:
When we got it, we can start to program. first we have to create a new project, (File> New)put two blocs of motors and then we select the pins where we have it connected:
 +
<br/>[[Image:Sers4a.png|center|Sers4a.png]]
-
[[File:Sers4a.png | center]]
+
<br/>Putting one in clockwise and the other counterclockwise and we start them making doble click on them, the robot should move forward (or backward depending of the order we plugged the servos). If we want to move it when we push a key we should do the follow:
 +
<br/>[[Image:S4a03.png|center|S4a03.png]]
-
Putting one in clockwise and the other counterclockwise and we start them making doble click on them, the robot should move forward (or backward depending of the order we plugged the servos). If we want to move it when we push a key we should do the follow:
+
<br/>Now we have to do the same for the other keys, (changing the direction of each engine). And adding the Space Key for Stop the robot:
 +
<br/>[[Image:S4a04.png|center|S4a04.png]]
-
[[File:S4a03.png | center]]
+
<br/>If we want the robot move when we push a key, and stop when we don't touch the keyboard we can do and alternative version:
 +
<br/>[[Image:S4a05.png|center|S4a05.png]]
-
Now we have to do the same for the other keys, (changing the direction of each engine). And adding the Space Key for Stop the robot:
+
<br/>'''Example 3: Robot Controlled with and accelerometer'''
-
 
+
-
 
+
-
[[File:S4a04.png | center]]
+
-
 
+
-
 
+
-
If we want the robot move when we push a key, and stop when we don't touch the keyboard we can do and alternative version:
+
-
 
+
-
 
+
-
[[File:S4a05.png | center]]
+
-
 
+
-
 
+
-
'''Example 3: Robot Controlled with and accelerometer'''
+
Now, we know how accelerometer and robot works, so we are ready for do the last exercice: Control the robot with the accelerometer.
Now, we know how accelerometer and robot works, so we are ready for do the last exercice: Control the robot with the accelerometer.
Line 200: Line 178:
The first we need its add two switches (botons) to the accelerometer board, like this:
The first we need its add two switches (botons) to the accelerometer board, like this:
 +
<br/>[[Image:Acceler.png|center|Acceler.png]]
-
[[File:Acceler.png | center]]
+
<br/>One of these switch it's for start and stop the robot, and the other for switch between forward and backward movement. Everyone requires a resistor of 10k acting as a pull down.
-
 
+
-
 
+
-
One of these switch it's for start and stop the robot, and the other for switch between forward and backward movement. Everyone requires a resistor of 10k acting as a pull down.
+
Now we can start to "Build" the program. We gonna start with the accelerometer board. The first step will be calibrate the acclerometer, like we did in the first exemple, but this time the only axis we need its X. How we got it plugged at Analogic pin 2 we gonna use analog 3. And we create a new Variable, (for all the other objects, because we gonna need to see them from arduino obect) where we gonna store the X axis value calibrated:
Now we can start to "Build" the program. We gonna start with the accelerometer board. The first step will be calibrate the acclerometer, like we did in the first exemple, but this time the only axis we need its X. How we got it plugged at Analogic pin 2 we gonna use analog 3. And we create a new Variable, (for all the other objects, because we gonna need to see them from arduino obect) where we gonna store the X axis value calibrated:
 +
<br/>[[Image:S4a06.png|center|S4a06.png]]
-
[[File:S4a06.png | center]]
+
<br/>This variable "direction" will give us 0, aproximately, when we got the board vertically with the usb cable pointed up.
-
 
+
The next step its create another bloc of instruccions for control the state of the bottons; We will create a few variables (only for this Object) to keep the button state. Also create two variables, one to know when the robot is started or stopped (motorsOn) and one for controlling the movement forward and backward (moveForward). The latter must be for all objects.
-
This Variable "Direction"  will give us 0, aproximatly, when we got the board vertically with the usb cable pointed up.
+
-
 
+
-
The next step its create another bloc of instruccions for control the state of the bottons;
+
-
We will create a few variables (only for this Object) to keep the button state. Also create two variables, one to know when the robot is started or stopped (motorsOn) and one for controlling the movement forward and backward (moveForward). The latter must be for all objects.
+
But the fact of using buttons raises a question: for example, in the case that control the movement forward or backward, we want to change direction only when you press the button or you continue until you give again? Obviously the second option is more practical (and also more complicated, though not much). Therefore, we will move only when it detects when you press the button, that is, if we were not pressed the (false) to down (true). In addition we will update the status of the button depending on whether or not the button is pressed:
But the fact of using buttons raises a question: for example, in the case that control the movement forward or backward, we want to change direction only when you press the button or you continue until you give again? Obviously the second option is more practical (and also more complicated, though not much). Therefore, we will move only when it detects when you press the button, that is, if we were not pressed the (false) to down (true). In addition we will update the status of the button depending on whether or not the button is pressed:
 +
<br/>[[Image:S4a07.png|center|S4a07.png]]
-
[[File:S4a07.png | center]]
+
<br/>''By this way if u press and hold the button, only goes one time to the conditional.'' because when it comes out, assing the value Digital1 (true) button1State to the variable, and repeats the loop when the condition is not met button1State as is true and not false. Now you should add what the condition has to do:
-
 
+
-
 
+
-
''By this way if u press and hold the button, only goes one time to the conditional.
+
-
because when it comes out, assing the value Digital1 (true) button1State to the variable, and repeats the loop when the condition is not met button1State as is true and not false. Now you should add what the condition has to do:''
+
-
 
+
-
 
+
-
[[File:S4a08.png | center]]
+
-
 
+
-
 
+
-
Now when it comes to conditional, will look the value of the variable moveForward. In case of that is true it will change to false and vice versa. So every time you press the button will shift from one sense to another. We do the same with the power button and the variable motorsOn and put it together with what we have:
+
-
 
+
-
 
+
-
[[File:S4a09.png | center]]
+
-
 
+
-
 
+
-
Now all that remains is initialize the variables and we will have the board with the accelerometer:
+
-
 
+
-
[[File:S4a10.png | center]]
+
<br/>[[Image:S4a08.png|center|S4a08.png]]
 +
<br/>Now when it comes to conditional, will look the value of the variable moveForward. In case of that is true it will change to false and vice versa. So every time you press the button will shift from one sense to another. We do the same with the power button and the variable motorsOn and put it together with what we have:
-
The following is create a new Arduino object for the robot. Here all you do is check the value of the variables motorsOn, moveForward and direction and act accordingly. For example, if the variable motorsOn is false means that the robot is stationary. Otherwise it means to be moved:
+
<br/>[[Image:S4a09.png|center|S4a09.png]]
 +
<br/>Now all that remains is initialize the variables and we will have the board with the accelerometer:
-
[[File:S4a11.png | center]]
+
<br/>[[Image:S4a10.png|center|S4a10.png]]
 +
<br/>The following is create a new Arduino object for the robot. Here all you do is check the value of the variables motorsOn, moveForward and direction and act accordingly. For example, if the variable motorsOn is false means that the robot is stationary. Otherwise it means to be moved:
-
And what we have to do when the engines are running? Directing them as the variables moveForward and direction. With the latter we choose one threshold value to know when we turn right, left or go straight ahead (for example we can use one value of 40 approximately). Then we will have three cases:
+
<br/>[[Image:S4a11.png|center|S4a11.png]]
 +
<br/>And what we have to do when the engines are running? Directing them as the variables moveForward and direction. With the latter we choose one threshold value to know when we turn right, left or go straight ahead (for example we can use one value of 40 approximately). Then we will have three cases:
-
'''if direction is less than -40: turn left.'''
+
<br/>'''if direction is less than -40: turn left.'''
'''if direction is greater than 40: turn right.'''
'''if direction is greater than 40: turn right.'''
Line 257: Line 218:
'''if not met any of the previous two (ie, direction is between -40 and 40): go straight.'''
'''if not met any of the previous two (ie, direction is between -40 and 40): go straight.'''
 +
<br/>Before starting we must stipulate what is the front and back of the robot to know when to go forward or back and what engine is for the right and wich is for left. In our case we designed this way:
-
Before starting we must stipulate what is the front and back of the robot to know when to go forward or back and what engine is for the right and wich is for left. In our case we designed this way:
+
<br/>[[Image:Servomotors2 bb.png|center|Servomotors2 bb.png]]
 +
<br/>The left engine is connected to pin 4 and right engine at pin 7. Below we have a table that summarizes in what sense should be the engines depending on the value of and direction in the case of the robot go forward, that is, when it meets moveForward is true:
-
[[File:Servomotors2 bb.png | center]]
 
-
The left engine is connected to pin 4 and right engine at pin 7. Below we have a table that summarizes in what sense should be the engines depending on the value of and direction in the case of the robot go forward, that is, when it meets moveForward is true:
+
{| style="width:400px; height:200px" align="center" border="1"
-
 
+
-
 
+
-
{| style="width:400px; height:200px" border="1" align="center"
+
|-
|-
-
| value of direction
+
| value of direction
| type of movement
| type of movement
| left servo (pin 4)
| left servo (pin 4)
Line 290: Line 249:
|}
|}
 +
<br/>In the case of "moveForward" its false, its the same but reversed:
-
In the case of "moveForward" its false, its the same but reversed:
 
-
{| style="width:400px; height:200px" border="1" align="center"
+
{| style="width:400px; height:200px" align="center" border="1"
|-
|-
-
| value of direction
+
| value of direction
| type of movement
| type of movement
| left servo (pin 4)
| left servo (pin 4)
Line 317: Line 276:
|}
|}
 +
<br/>Now the only thing to do its apply that to our program:
-
Now the only thing to do its apply that to our program:
+
<br/>[[Image:S4a12.png|center|S4a12.png]]
 +
<br/>And add it to what we had done:
-
[[File:S4a12.png | center]]
+
<br/>[[Image:S4a13.PNG|center|S4a13.PNG]]
 +
<br/>Enjoy!&nbsp;:)
-
And add it to what we had done:
 
-
 
-
 
-
[[File:S4a13.PNG | center]]
 
-
 
-
 
-
Enjoy! :)
 
=== [[Example 2: Script music workshop (Kandinsky)]] ===
=== [[Example 2: Script music workshop (Kandinsky)]] ===
-
 
Needed components:
Needed components:
-
1 x Arduino board: http://www.sparkfun.com/products/9950  
+
1 x Arduino board: http://www.sparkfun.com/products/9950
-
1 x Sensor infrared SHARP GP2Y0A21YK: http://www.sparkfun.com/products/242
+
-
1 x LED RGB: http://www.sparkfun.com/products/105
+
-
1 x usb cable: http://www.sparkfun.com/products/512
+
 +
1 x Sensor infrared SHARP GP2Y0A21YK: http://www.sparkfun.com/products/242
-
'''Step 1: Playing notes with the sensor'''
+
1 x LED RGB: http://www.sparkfun.com/products/105
-
Before anything else Create an Arduino object (or take what comes by default at the beginnig of new project), which set one number to a variable depending on the value of the sensor
+
1 x usb cable: http://www.sparkfun.com/products/512
 +
<br/>'''Step 1: Playing notes with the sensor'''
-
[[File:Selección_001.png | center]]
+
Before anything else Create an Arduino object (or take what comes by default at the beginnig of new project), which set one number to a variable depending on the value of the sensor
 +
<br/>[[Image:Selección 001.png|center|Selección 001.png]]
-
How we have to constantly monitor the value of the sensor we will use one endless loop where each iteraction store the value of the sensor into a variable. Depending on the value and if exceed or not certain thresholds, the variable will have one value or another value (from 1 to 7). In case of it is less than 160 (that is, if the sensor does not detect any obstacle) consider one value of 0.
+
<br/>How we have to constantly monitor the value of the sensor we will use one endless loop where each iteraction store the value of the sensor into a variable. Depending on the value and if exceed or not certain thresholds, the variable will have one value or another value (from 1 to 7). In case of it is less than 160 (that is, if the sensor does not detect any obstacle) consider one value of 0. Note: The variable value must be visible to all items!
-
Note: The variable value must be visible to all items!
+
We will create another Object that will be the main program. What what we have to do first is to choose an instrument. If you click at the block "set instrument to" a dropdown list must show with different types of instruments. Just memorize which number corresponds to:
We will create another Object that will be the main program. What what we have to do first is to choose an instrument. If you click at the block "set instrument to" a dropdown list must show with different types of instruments. Just memorize which number corresponds to:
 +
<br/>[[Image:Captura3.png|center|Captura3.png]]
-
[[File:captura3.png | center]]
+
<br/>The notes can also viewed at block "play note <> during <> pulse":
 +
<br/>[[Image:Captura4.png|center|Captura4.png]]
-
The notes can also viewed at block "play note <> during <> pulse":
+
<br/>Now we will create a new variable where we store the number of instrument and another for the note. Then make again an infinite loop where we must change the value depending of the value of variable "value"
-
 
+
-
 
+
-
[[File:captura4.png | center]]
+
-
 
+
-
 
+
-
Now we will create a new variable where we store the number of instrument and another for the note. Then make again an infinite loop where we must change the value depending of the value of variable "value"
+
Furthermore, if this is different from 0, and thus the value of the sensor is greater than 300, send a message playNote:
Furthermore, if this is different from 0, and thus the value of the sensor is greater than 300, send a message playNote:
Line 373: Line 322:
This part can be done on stage. When receives the message playNote, will set the instrument we have chosen and will play the corresponding note for a time. This process is repeated each time the message is relayed:
This part can be done on stage. When receives the message playNote, will set the instrument we have chosen and will play the corresponding note for a time. This process is repeated each time the message is relayed:
 +
<br/>[[Image:Selección 008.png|center|Selección 008.png]]
-
[[File:Selección_008.png | center]]
+
<br/>And with that we can start playing!
-
 
+
<br/>'''Step 2: Record the music'''
-
And with that we can start playing!
+
-
 
+
-
 
+
-
'''Step 2: Record the music'''
+
Now that we can play music through Arduino, we store each note on a list for when you want to play them. We must avoid touching any note with the sensor while the tune is playing, so we gonna use a "flag" variable named "playing", for example. In other words, we can only play in real time when playing = 0, ie, when not reproducing the list of notes. Otherwise, when one does not play any notes or stored.
Now that we can play music through Arduino, we store each note on a list for when you want to play them. We must avoid touching any note with the sensor while the tune is playing, so we gonna use a "flag" variable named "playing", for example. In other words, we can only play in real time when playing = 0, ie, when not reproducing the list of notes. Otherwise, when one does not play any notes or stored.
 +
<br/>[[Image:Selección 009.png|center|Selección 009.png]]
-
[[File:Selección_009.png | center]]
+
<br/>Then create a new object (in this case called PlayButton) to reproduce the melody when you press it with the mouse (the appearance of this object the user can create or take a picture with a built-button "play "or something like that). When this object is pressed, will begin to "search" in the list (with the help of the variable index) and play every note that is saved in this, but not before putting the variable streaming to 1 so that played the main program can not touch or keep any notes, as explained above. When reproduced the whole list, put it back to 0.
 +
<br/>[[Image:Selección 010.png|center|Selección 010.png]]
-
Then create a new object (in this case called PlayButton) to reproduce the melody when you press it with the mouse (the appearance of this object the user can create or take a picture with a built-button "play "or something like that). When this object is pressed, will begin to "search" in the list (with the help of the variable index) and play every note that is saved in this, but not before putting the variable streaming to 1 so that played the main program can not touch or keep any notes, as explained above. When reproduced the whole list, put it back to 0.
+
<br/>Also its needed to put 0 at the start of the program (see capture below)
-
 
+
<br/>'''Step 3: Change the rhythm'''
-
[[File:Selección_010.png | center]]
+
-
 
+
-
 
+
-
Also its needed to put 0 at the start of the program (see capture below)
+
-
 
+
-
 
+
-
'''Step 3: Change the rhythm'''
+
If we wanna use the sensor for change the rhythm of the melody, when this one is playing, we gonna use a variable "Tempo", which we gonna modify like the variable "note" (with other values), changing the code of this one and moving it apart:
If we wanna use the sensor for change the rhythm of the melody, when this one is playing, we gonna use a variable "Tempo", which we gonna modify like the variable "note" (with other values), changing the code of this one and moving it apart:
 +
<br/>[[Image:Selección 011.png|center|Selección 011.png]]
-
[[File:Selección_011.png | center]]
+
<br/>We can exchange the two parts when we are playing or in reproducing mode. For modify the tempo in real time, we need to do the following: (we can do it directly in the escenary)
 +
<br/>[[Image:Selección 012.png|center|Selección 012.png]]
-
We can exchange the two parts when we are playing or in reproducing mode. For modify the tempo in real time, we need to do the following: (we can do it directly in the escenary)
+
<br/>'''Step 4: Erase the Melody'''
-
 
+
-
 
+
-
[[File:Selección_012.png | center]]
+
-
 
+
-
 
+
-
'''Step 4: Erase the Melody'''
+
For finish we are going to create another object for erase/delete the melody, when this one it's pressed:
For finish we are going to create another object for erase/delete the melody, when this one it's pressed:
 +
<br/>[[Image:Selección 013.png|center|Selección 013.png]]
-
[[File:Selección_013.png | center]]
+
<br/>'''Step 5: Record Button'''
-
 
+
-
 
+
-
'''Step 5: Record Button'''
+
If we don't want the program to save automatically the notes that we are playing, we can make an additional button for recording control (like the "Rec" option of any media device). The main purpose of this is to change the variable named "Record" from 0 to 1 and viceversa:
If we don't want the program to save automatically the notes that we are playing, we can make an additional button for recording control (like the "Rec" option of any media device). The main purpose of this is to change the variable named "Record" from 0 to 1 and viceversa:
 +
<br/>[[Image:Selección 014.png|center|Selección 014.png]]
-
[[File:Selección_014.png | center]]
+
<br/>And when we are going to use this variable? At the main program, where we play the note depending of the value of the sensor:
-
 
+
-
 
+
-
And when we are going to use this variable? At the main program, where we play the note depending of the value of the sensor:
+
-
 
+
-
[[File:Selección_015.png | center]]
+
<br/>[[Image:Selección 015.png|center|Selección 015.png]]
 +
<br/>And that's all!
-
And that's all!
+
<br/><br/>
-
[[Category:Toolkits]]
+
[[Category:Toolkits]] <br/>

Revision as of 15:51, 8 June 2011



This Translation its in WIP state, need some revisions and things to finish :)

Template:Infobox user

Contents

What is it ?

S4ahardsoft.JPG
S4A is a Scratch modification that supports simple programming of the Arduino open source hardware platform. It provides new blocks for managing sensors and actuators connected to Arduino. There is also a sensor report board similar to the PicoBoard.

It has been created to attract people to the programming world. The goal is also to provide a high level interface to Arduino programmers with functionalities such as interacting with a set of boards through user events.


What is Scratch?

Scratch is an opensource programming environment oriented for initiate kids and youngsters in the world of programming. The programming language vinculated at Scratch’s interface it’s a simple language with the fundamental syntaxis of programming, with a lot of instructions (embedded in blocks) for make multimedia projects, like animations or games. You can drag and drop these blocks for build your program like a puzzle.


Scracth code.JPG

What is Arduino?

Arduino is a tool for making computers that can sense and control more of the physical world than your desktop computer. It's an open-source physical computing platform based on a simple microcontroller board, and a development environment for writing software for the board. Arduino can be used to develop interactive objects, taking inputs from a variety of switches or sensors, and controlling a variety of lights, motors, and other physical outputs. Arduino projects can be stand-alone, or they can be communicate with software running on your computer (e.g. Flash, Processing, MaxMSP.) The boards can be assembled by hand or purchased preassembled; the open-source IDE can be downloaded for free. The Arduino programming language is an implementation of Wiring, a similar physical computing platform, which is based on the Processing multimedia programming environment.


What can I do with it ?

Promove kids or youngsters to program and build his own inventions. Teach programming to anyone in a funny and easy way. Learn the basics of electronics. Make an introduction to Arduino, to people who didn’t have any contact with electronics or computer programming world.


Uses:

The uses are up to your imagination, but here are some examples that we used and you can replicate.


Who can use this?

Anyone interested of electronics or programming and want to learn more or teach.


What do I need ?


Requirements:

Basic Arduino and electronic knowledge of the components you are going to use. Or you can find how to connect them to the Arduino board or what they need for work,in this url: http://arduino.cc/en/Tutorial/HomePage , all information and schematics for how connect and work with all the basic components, like switches, leds, infraredsenors, servos, etc, is also there.


How to download


How to install

In the arduino homepage there is a guide for install the diferent models of arduino boards and for each O.S

http://arduino.cc/en/Guide/HomePage


Examples

We provide some examples of what can be done, but as we said they are just exemples, what you can do only its limited by imagination.


Example 1: Robot with a remote controller

In this exemple we are going to explain how to build a robot made with one arduino board and two continuos rotation servomotors, controlled by another board with and acceleremeter, two leds and two botons.


What do we need?

Robot:


Remote Controler:


How to do it?

Before starting with the exercise, we are going to make some tests for see how works both servos and accelerometer. In the first exemple we need to plug the accelerometer to the Arduino board, using this model:


Accelerometer bb.png


The pins of the accelerometer for the power are GND and VDD, so we have to connect them to the board at GND and VDD at 5v. Pins Z, Y and X must be plugged at analogic 0, 1 and 2 respectively. This ones correspond to the three-dimensional coordinate axes ZYX (Z height, depth Y and X width) as you can see printed on it. The diagram below will clarify this concept:


Acelerometro ejes.png


The values given by the sensors of the accelerometer of every axis vary from 446 to 576 aprox. This means: If we take the board horitzontaly like we have it in the draw (leaving the Usb at Left, and Accelerometer at right)and we turn it clockwise 270 degrees (until usb its looking down and the accelerometer up) The y Axis will give us its minimum vale and should be above 446. if wereverse the movement, (USB above, accelerometer below), Will reach his maximum value and give us 576. The X axis will not have changed almost everything in this process, and if we had the board parallel to the ground, we will return a value of 511 roughly intermediate. Then a small theoretical calculation of this value:


576-446 = 130

130: 2 = 65

576-65 = 511 (or 446 + 65 = 511)


In the exercise the first thing to do it's "calibrate" these values. so we gonna store these values in two variables. In this exercice we dont need the Z axis value. The calibration must be done with the board vertically, leaving the usb up and the accelerometer down.


Sa1.PNG


Create two variables AxisY and AxisX for continusly store the values of axis y (analog 2) and axis X (analog 3. The value of Axis Y will have its minimum value. we subtract this value which gives about 0. We will do the same with the X axis subtracting the value intermediate, as will be parallel to the ground.

For what we need every Axis? As we know the cordinate system of scratch in regarding the direction of an object varies somewhat with respect to normal:


PCS.png


So we are gonna use the X axis for control the threshold 0, To know when switch between negative to positive and Y axis to vary the direction of the object.How does not match the value of the Y-axis accelerometer with the direction of the scratch, we must do a small conversion, that is, if we turn the board to the right we see that the variable Y takes a value About 65 (which it confirms the calculation we have done before), and Scratch the right equals 90, so:


90 / 65 = 1.384615385 (1.4 rounding)


This is the factor that we use to pass the value of the Y axis in the direction Scratch. Please note that this factor is valid when the value of X axis is greater than 0, ie, when the board pointing to the right. If that points to the left, we will use the same factor but negative:


S4a02.png


We also added a block to move the object.


Example 2: Robot Controled with keyboard

In the following example we will control the robot with the keyboard. The assemble scheme will be the following:


Servomotors bb.png


We need to connect each servo at (5V) and to the ground (GND) and one connected to the pin 4 and the other to the pin 7, they will recive the signal form the board and the program.

When we got it, we can start to program. first we have to create a new project, (File> New)put two blocs of motors and then we select the pins where we have it connected:


Sers4a.png


Putting one in clockwise and the other counterclockwise and we start them making doble click on them, the robot should move forward (or backward depending of the order we plugged the servos). If we want to move it when we push a key we should do the follow:


S4a03.png


Now we have to do the same for the other keys, (changing the direction of each engine). And adding the Space Key for Stop the robot:


S4a04.png


If we want the robot move when we push a key, and stop when we don't touch the keyboard we can do and alternative version:


S4a05.png


Example 3: Robot Controlled with and accelerometer

Now, we know how accelerometer and robot works, so we are ready for do the last exercice: Control the robot with the accelerometer.

The first we need its add two switches (botons) to the accelerometer board, like this:


Acceler.png


One of these switch it's for start and stop the robot, and the other for switch between forward and backward movement. Everyone requires a resistor of 10k acting as a pull down.

Now we can start to "Build" the program. We gonna start with the accelerometer board. The first step will be calibrate the acclerometer, like we did in the first exemple, but this time the only axis we need its X. How we got it plugged at Analogic pin 2 we gonna use analog 3. And we create a new Variable, (for all the other objects, because we gonna need to see them from arduino obect) where we gonna store the X axis value calibrated:


S4a06.png


This variable "direction" will give us 0, aproximately, when we got the board vertically with the usb cable pointed up.

The next step its create another bloc of instruccions for control the state of the bottons; We will create a few variables (only for this Object) to keep the button state. Also create two variables, one to know when the robot is started or stopped (motorsOn) and one for controlling the movement forward and backward (moveForward). The latter must be for all objects.

But the fact of using buttons raises a question: for example, in the case that control the movement forward or backward, we want to change direction only when you press the button or you continue until you give again? Obviously the second option is more practical (and also more complicated, though not much). Therefore, we will move only when it detects when you press the button, that is, if we were not pressed the (false) to down (true). In addition we will update the status of the button depending on whether or not the button is pressed:


S4a07.png


By this way if u press and hold the button, only goes one time to the conditional. because when it comes out, assing the value Digital1 (true) button1State to the variable, and repeats the loop when the condition is not met button1State as is true and not false. Now you should add what the condition has to do:


S4a08.png


Now when it comes to conditional, will look the value of the variable moveForward. In case of that is true it will change to false and vice versa. So every time you press the button will shift from one sense to another. We do the same with the power button and the variable motorsOn and put it together with what we have:


S4a09.png


Now all that remains is initialize the variables and we will have the board with the accelerometer:


S4a10.png


The following is create a new Arduino object for the robot. Here all you do is check the value of the variables motorsOn, moveForward and direction and act accordingly. For example, if the variable motorsOn is false means that the robot is stationary. Otherwise it means to be moved:


S4a11.png


And what we have to do when the engines are running? Directing them as the variables moveForward and direction. With the latter we choose one threshold value to know when we turn right, left or go straight ahead (for example we can use one value of 40 approximately). Then we will have three cases:


if direction is less than -40: turn left.

if direction is greater than 40: turn right.

if not met any of the previous two (ie, direction is between -40 and 40): go straight.


Before starting we must stipulate what is the front and back of the robot to know when to go forward or back and what engine is for the right and wich is for left. In our case we designed this way:


Servomotors2 bb.png


The left engine is connected to pin 4 and right engine at pin 7. Below we have a table that summarizes in what sense should be the engines depending on the value of and direction in the case of the robot go forward, that is, when it meets moveForward is true:


value of direction type of movement left servo (pin 4) right servo (pin 7)
less than -40 turn left clockwise clockwise
more than -40 turn right anticlockwise anticlockwise
between -40 and 40 go forward anticlockwise clockwise


In the case of "moveForward" its false, its the same but reversed:


value of direction type of movement left servo (pin 4) right servo (pin 7)
less than -40 turn left anticlockwise anticlockwise
more than -40 turn right clockwise clockwise
between -40 and 40 go forward clockwise anticlockwise


Now the only thing to do its apply that to our program:


S4a12.png


And add it to what we had done:


S4a13.PNG


Enjoy! :)


Example 2: Script music workshop (Kandinsky)

Needed components:

1 x Arduino board: http://www.sparkfun.com/products/9950

1 x Sensor infrared SHARP GP2Y0A21YK: http://www.sparkfun.com/products/242

1 x LED RGB: http://www.sparkfun.com/products/105

1 x usb cable: http://www.sparkfun.com/products/512


Step 1: Playing notes with the sensor

Before anything else Create an Arduino object (or take what comes by default at the beginnig of new project), which set one number to a variable depending on the value of the sensor


Selección 001.png


How we have to constantly monitor the value of the sensor we will use one endless loop where each iteraction store the value of the sensor into a variable. Depending on the value and if exceed or not certain thresholds, the variable will have one value or another value (from 1 to 7). In case of it is less than 160 (that is, if the sensor does not detect any obstacle) consider one value of 0. Note: The variable value must be visible to all items!

We will create another Object that will be the main program. What what we have to do first is to choose an instrument. If you click at the block "set instrument to" a dropdown list must show with different types of instruments. Just memorize which number corresponds to:


Captura3.png


The notes can also viewed at block "play note <> during <> pulse":


Captura4.png


Now we will create a new variable where we store the number of instrument and another for the note. Then make again an infinite loop where we must change the value depending of the value of variable "value"

Furthermore, if this is different from 0, and thus the value of the sensor is greater than 300, send a message playNote:

This part can be done on stage. When receives the message playNote, will set the instrument we have chosen and will play the corresponding note for a time. This process is repeated each time the message is relayed:


Selección 008.png


And with that we can start playing!


Step 2: Record the music

Now that we can play music through Arduino, we store each note on a list for when you want to play them. We must avoid touching any note with the sensor while the tune is playing, so we gonna use a "flag" variable named "playing", for example. In other words, we can only play in real time when playing = 0, ie, when not reproducing the list of notes. Otherwise, when one does not play any notes or stored.


Selección 009.png


Then create a new object (in this case called PlayButton) to reproduce the melody when you press it with the mouse (the appearance of this object the user can create or take a picture with a built-button "play "or something like that). When this object is pressed, will begin to "search" in the list (with the help of the variable index) and play every note that is saved in this, but not before putting the variable streaming to 1 so that played the main program can not touch or keep any notes, as explained above. When reproduced the whole list, put it back to 0.


Selección 010.png


Also its needed to put 0 at the start of the program (see capture below)


Step 3: Change the rhythm

If we wanna use the sensor for change the rhythm of the melody, when this one is playing, we gonna use a variable "Tempo", which we gonna modify like the variable "note" (with other values), changing the code of this one and moving it apart:


Selección 011.png


We can exchange the two parts when we are playing or in reproducing mode. For modify the tempo in real time, we need to do the following: (we can do it directly in the escenary)


Selección 012.png


Step 4: Erase the Melody

For finish we are going to create another object for erase/delete the melody, when this one it's pressed:


Selección 013.png


Step 5: Record Button

If we don't want the program to save automatically the notes that we are playing, we can make an additional button for recording control (like the "Rec" option of any media device). The main purpose of this is to change the variable named "Record" from 0 to 1 and viceversa:


Selección 014.png


And when we are going to use this variable? At the main program, where we play the note depending of the value of the sensor:


Selección 015.png


And that's all!




Personal tools
Namespaces
Variants
Actions
Navigation
Toolbox