Your Smart IOT

The GPIO pins on a <a href="http://ift.tt/1o7SsLh" itemprop="url" target="_bank" title="Raspberry">Raspberry</a> Pi are a great way to interface physical devices like buttons and LEDs with the little Linux processor. If you’re a <a href="http://ift.tt/1LK8jLD" itemprop="url" target="_bank" title="Python">Python</a> developer, there’s a sweet library called RPi.GPIO that handles interfacing with the pins. In just three lines of code, you can get an LED blinking on one of the GPIO pins.
<h3>INSTALLATION</h3>
The newest version of <a href="http://ift.tt/1UhpgQn" itemprop="url" target="_bank" title="Raspbian">Raspbian</a> has the RPi.GPIO library pre-installed. You’ll probably need to update your library, so using the command line, run: 
<code>sudo python 
import RPi.GPIO as GPIO 
GPIO.VERSION</code> 
The current version of RPi.GPIO is 0.5.4 If you need to update to a newer version, run: 
<code>sudo apt-get update 
sudo apt-get upgrade</code> 
If you don’t have the RPi.GPIO library because you’re using an older version of <a href="http://ift.tt/1LIxY7j" itemprop="url" target="_bank" title="Raspbian">Raspbian</a>, there are great instructions on the <a href="http://ift.tt/1A7bky5" target="_blank">Raspberry Pi Spy</a> website on installing the package from scratch.
<h3>USING THE RPI.GPIO LIBRARY</h3>
Now that you’ve got the package installed and updated, let’s take a look at some of the functions that come with it. Open the Leafpad text editor and save your sketch as “myInputSketch.py”. From this point forward, we’ll execute this script using the command line:
<code>sudo <a href="http://ift.tt/1RBcFRc" itemprop="url" target="_bank" title="python">python</a> myInputSketch.py</code>
All of the following code can be added to this same file. Remember to save before you run the above command. To exit the sketch and make changes, press Ctrl+C.
To add the GPIO library to a Python sketch, you must first import it:
<code>import RPi.GPIO as GPIO</code>
Then we need to declare the type of numbering system we’re going to use for our pins:
<code>#set up GPIO using BCM numbering 
GPIO.setmode(GPIO.BCM) 
#setup GPIO using Board numbering 
GPIO.setmode(GPIO.BOARD)</code>
The main difference between these modes is that the BOARD option uses the pins exactly as they are laid out on the Pi. No matter what revision you’re using, these will always be the same. The BCM option uses the Broadcom SoC numbering, which differs between version 1 and version 2 of the Pi.
<a href="http://ift.tt/23yBl95" target="_blank"><img alt="GPIO BCM Descriptions" class="alignnone size-medium wp-image-377399" data-lazy-loaded="true" height="378" src="http://ift.tt/20EWHwb" width="620" /></a> 
from <a href="http://ift.tt/23yBl99" target="_blank">Meltwater’s Raspberry Pi Hardware</a>
In the image above, you’ll see that Pin 5 is GPIO01/03. This means that a v.1 Pi is GPIO 01, while a v.2 Pi is GPIO 03. The BCM numbering is what I’ll be using for the rest of this entry, because it’s universal across other programming languages.
<h3>BUILDING A CIRCUIT</h3>
Now we’re going to get into inputs and outputs. In the circuit shown below, two momentary switches are wired to GPIO pins 23 and 24 (pins 16 and 18 on the board). The switch on pin 23 is tied to 3.3V, while the switch on pin 24 is tied to ground. The reason for this is that the Raspberry Pi has internal pull-up and pull-down resistors that can be specified when the pin declarations are made.
<div class="ezAdsense adsense adsense-midtext" style="text-align:center;margin:12px;"><script async="" src="//pagead2.googlesyndication.com/pagead/js/adsbygoogle.js" type="text/javascript">
</script> <ins class="adsbygoogle" style="display:block" data-ad-client="ca-pub-2979805726071943" data-ad-slot="7471922310" data-ad-format="auto"></ins> <script type="text/javascript">
//<![CDATA[
(adsbygoogle = window.adsbygoogle || []).push({});
//]]>
</script></div>
<a href="http://ift.tt/20EWHwf" target="_blank"><img alt="Raspberry Pi Circuit" class="alignnone size-medium wp-image-377400" data-lazy-loaded="true" height="397" src="http://ift.tt/23yBlpn" width="620" /></a> 
To set up these pins, write:
<code>GPIO.setup(23, GPIO.IN, pull_up_down=GPIO.PUD_DOWN) 
GPIO.setup(24, GPIO.IN, pull_up_down=GPIO.PUD_UP)</code> 
This will enable a pull-down resistor on pin 23, and a pull-up resistor on pin 24. Now, let’s check to see if we can read them. The Pi is looking for a high voltage on Pin 23 and a low voltage on Pin 24. We’ll also need to put these inside of a loop, so that it is constantly checking the pin voltage. The code so far looks like this:
<code>import RPi.GPIO as GPIO 
GPIO.setmode(GPIO.BCM) 
GPIO.setup(23, GPIO.IN, pull_up_down = GPIO.PUD_DOWN) 
GPIO.setup(24, GPIO.IN, pull_up_down = GPIO.PUD_UP) 
while True: 
if(GPIO.input(23) ==1): 
print(“Button 1 pressed”) 
if(GPIO.input(24) == 0): 
print(“Button 2 pressed”) 
GPIO.cleanup()</code>
The indents in Python are important when using loops, so be sure to include them. You also must run your script as “sudo” to access the GPIO pins. The GPIO.cleanup() command at the end is necessary to reset the status of any GPIO pins when you exit the program. If you don’t use this, then the GPIO pins will remain at whatever state they were last set to.
<h3>THE PROBLEM WITH POLLING</h3>
This code works, but prints a line for each frame that the button is pressed. This is extremely inconvenient if you want to use that button to trigger an action or command only one time. Luckily, the GPIO library has built in a rising-edge and falling-edge function. A rising-edge is defined by the time the pin changes from low to high, but it only detects the change. Similarly, thefalling-edge is the moment the pin changes from high to low. Using this definition, let’s change our code slightly:
<code>import RPi.GPIO as GPIO 
GPIO.setmode(GPIO.BCM) 
GPIO.setup(23, GPIO.IN, pull_up_down = GPIO.PUD_DOWN) 
GPIO.setup(24, GPIO.IN, pull_up_down = GPIO.PUD_UP) 
while True: 
GPIO.wait_for_edge(23, GPIO.RISING) 
print(“Button 1 Pressed”) 
GPIO.wait_for_edge(23, GPIO.FALLING) 
print(“Button 1 Released”) 
GPIO.wait_for_edge(24, GPIO.FALLING) 
print(“Button 2 Pressed”) 
GPIO.wait_for_edge(24, GPIO.RISING) 
print(“Button 2 Released”) 
GPIO.cleanup()</code> 
When you run this code, notice how the statement only runs after the edge detection occurs. This is because Python is waiting for this specific edge to occur before proceeding with the rest of the code. What happens if you try to press button 2 before you let go of button 1? What happens if you try to press button 1 twice without pressing button 2? Because the code is written sequentially, the edges must occur in exactly the order written.
Edge Detection is great if you need to wait for an input before continuing with the rest of the code. However, if you need to trigger a function using an input device, then events and callback functions are the best way to do that.
<h3>EVENTS AND CALLBACK FUNCTIONS</h3>
Let’s say you’ve got the Raspberry Pi camera module, and you’d like it to snap a photo when you press a button. However, you don’t want your code to poll that button constantly, and you certainly don’t want to wait for an edge because you may have other code running simultaneously.
The best way to execute this code is using a callback function. This is a function that is attached to a specific GPIO pin and run whenever that edge is detected. Let’s try one:
<code>import RPi.GPIO as GPIO 
GPIO.setmode(GPIO.BCM) 
GPIO.setup(23, GPIO.IN, pull_up_down = GPIO.PUD_DOWN) 
GPIO.setup(24, GPIO.IN, pull_up_down = GPIO.PUD_UP) 
def printFunction(channel): 
print(“Button 1 pressed!”) 
print(“Note how the bouncetime affects the button press”) 
GPIO.add_event_detect(23, GPIO.RISING, callback=printFunction, bouncetime=300) 
while True: 
GPIO.wait_for_edge(24, GPIO.FALLING) 
print(“Button 2 Pressed”) 
GPIO.wait_for_edge(24, GPIO.RISING) 
print(“Button 2 Released”) 
GPIO.cleanup()</code>
You’ll notice here that button 1 will consistently trigger the printFunction, even while the main loop is waiting for an edge on button 2. This is because the callback function is in a separate thread. Threads are important in programming because they allow things to happen simultaneously without affecting other functions. Pressing button 1 will not affect what happens in our main loop.
Events are also great, because you can remove them from a pin just as easily as you can add them:
<code>GPIO.remove_event_detect(23)</code> 
Now you’re free to add a different function to the same pin!
<h3>ADDING FUNCTIONALITY</h3>
As convenient as callback functions are for the GPIO pins, it still doesn’t change the fact that the Raspberry Pi is just not ideal for analog inputs or PWM outputs. However, because the Pi has Tx and Rx pins (pins 8 and 10, GPIO 14 and 15), it can easily communicate with an <a href="http://ift.tt/1pCdnqV" itemprop="url" target="_bank" title="Arduino">Arduino</a>. If I have a project that requires an analog sensor input, or smooth PWM output, simply writing commands to the serial port to the Arduino can make things seamless.
<div id="huge-it-share-buttons-top" class="huge-it-share-buttons nobackground">
<h3>Share This:</h3>
<ul class="huge-it-share-buttons-list">
<li class=" nobackground"><a href="http://ift.tt/1LIxY7s" id="backforunical517" name="backforunical517" onclick="javascript:void window.open('http://ift.tt/1LIxY7s','1410949501326','width=700,height=500,toolbar=0,menubar=0,location=0,status=1,scrollbars=1,resizable=1,left=0,top=0');return false;" style="background-position: -0px -120px" target="_blank"></a></li>
<li class=" nobackground"><a href="https://twitter.com/share?status=http://yoursmart.mobi/feed&text=Raspberry%20Pi%20GPIO%20Pins%20and%20Python" id="backforunical517" name="backforunical517" onclick="javascript:void window.open('https://twitter.com/share?status=http://yoursmart.mobi/feed&text=Raspberry Pi GPIO Pins and Python','1410949501326','width=700,height=500,toolbar=0,menubar=0,location=0,status=1,scrollbars=1,resizable=1,left=0,top=0');return false;" style="background-position: -30px -120px" target="_blank"></a></li>
<li class=" nobackground"><a href="http://ift.tt/1LK8jvd%20Pi%20GPIO%20Pins%20and%20Python" id="backforunical517" name="backforunical517" onclick="javascript:void window.open('http://ift.tt/1LK8jvd Pi GPIO Pins and Python','1410949501326','width=700,height=500,toolbar=0,menubar=0,location=0,status=1,scrollbars=1,resizable=1,left=0,top=0');return false;" style="background-position: -60px -120px" target="_blank"></a></li>
<li class=" nobackground"><a href="http://ift.tt/1LIxZZ0" id="backforunical517" name="backforunical517" onclick="javascript:void window.open('http://ift.tt/1LIxZZ0','1410949501326','width=700,height=500,toolbar=0,menubar=0,location=0,status=1,scrollbars=1,resizable=1,left=0,top=0');return false;" style="background-position: -90px -120px" target="_blank"></a></li>
<li class=" nobackground"><a href="http://ift.tt/1H4sMpI%20Pi%20GPIO%20Pins%20and%20Python&mini=true&url=http://ift.tt/1LIxZZ4" id="backforunical517" name="backforunical517" onclick="javascript:void window.open('http://ift.tt/1H4sMpI Pi GPIO Pins and Python&mini=true&url=http://ift.tt/1LIxZZ4','1410949501326','width=700,height=500,toolbar=0,menubar=0,location=0,status=1,scrollbars=1,resizable=1,left=0,top=0');return false;" style="background-position: -120px -120px" target="_blank"></a></li>
<li class=" nobackground"><a href="http://ift.tt/1LK8jvf%20Pi%20GPIO%20Pins%20and%20Python" id="backforunical517" name="backforunical517" onclick="javascript:void window.open('http://ift.tt/1LK8jvf Pi GPIO Pins and Python','1410949501326','width=700,height=500,toolbar=0,menubar=0,location=0,status=1,scrollbars=1,resizable=1,left=0,top=0');return false;" style="background-position: -150px -120px" target="_blank"></a></li>
<li class=" nobackground"><a href="http://ift.tt/1WLPAQn%20Pi%20GPIO%20Pins%20and%20Python" id="backforunical517" name="backforunical517" onclick="javascript:void window.open('http://ift.tt/1WLPAQn Pi GPIO Pins and Python','1410949501326','width=700,height=500,toolbar=0,menubar=0,location=0,status=1,scrollbars=1,resizable=1,left=0,top=0');return false;" style="background-position: -180px -120px" target="_blank"></a></li>
<li class=" nobackground"><a href="http://ift.tt/1LK8gPS%20Pi%20GPIO%20Pins%20and%20Python" id="backforunical517" name="backforunical517" onclick="javascript:void window.open('http://ift.tt/1LK8gPS Pi GPIO Pins and Python','1410949501326','width=700,height=500,toolbar=0,menubar=0,location=0,status=1,scrollbars=1,resizable=1,left=0,top=0');return false;" style="background-position: -210px -120px" target="_blank"></a></li>
<li class=" nobackground"><a href="http://ift.tt/1LIxY7u" id="backforunical517" name="backforunical517" onclick="javascript:void window.open('http://ift.tt/1LIxY7u','1410949501326','width=700,height=500,toolbar=0,menubar=0,location=0,status=1,scrollbars=1,resizable=1,left=0,top=0');return false;" style="background-position: -240px -120px" target="_blank"></a></li>
<li class="none nobackground"><a href="http://ift.tt/1WLPAQr%20Pi%20GPIO%20Pins%20and%20Python" id="backforunical517" name="backforunical517" onclick="javascript:void window.open('http://ift.tt/1WLPAQr Pi GPIO Pins and Python','1410949501326','width=700,height=500,toolbar=0,menubar=0,location=0,status=1,scrollbars=1,resizable=1,left=0,top=0');return false;" style="background-position: -270px -120px" target="_blank"></a></li>
<li class="none nobackground"><a href="http://ift.tt/1LK8gPU%20Pi%20GPIO%20Pins%20and%20Python" id="backforunical517" name="backforunical517" onclick="javascript:void window.open('http://ift.tt/1LK8gPU Pi GPIO Pins and Python','1410949501326','width=700,height=500,toolbar=0,menubar=0,location=0,status=1,scrollbars=1,resizable=1,left=0,top=0');return false;" style="background-position: -300px -120px" target="_blank"></a></li>
<li class="none nobackground"><a href="http://ift.tt/1o7SuTq" id="backforunical517" name="backforunical517" onclick="javascript:void window.open('http://ift.tt/1o7SuTq','1410949501326','width=700,height=500,toolbar=0,menubar=0,location=0,status=1,scrollbars=1,resizable=1,left=0,top=0');return false;" style="background-position: -330px -120px" target="_blank"></a></li>
<li class="none nobackground"><a href="http://ift.tt/1WLPAQt%20Pi%20GPIO%20Pins%20and%20Python" id="backforunical517" name="backforunical517" onclick="javascript:void window.open('http://ift.tt/1WLPAQt Pi GPIO Pins and Python','1410949501326','width=700,height=500,toolbar=0,menubar=0,location=0,status=1,scrollbars=1,resizable=1,left=0,top=0');return false;" style="background-position: -360px -120px" target="_blank"></a></li>
<li class="none nobackground"><a href="http://ift.tt/1o7SuTs" id="backforunical517" name="backforunical517" onclick="javascript:void window.open('http://ift.tt/1o7SuTs','1410949501326','width=700,height=500,toolbar=0,menubar=0,location=0,status=1,scrollbars=1,resizable=1,left=0,top=0');return false;" style="background-position: -390px -120px" target="_blank"></a></li>
<li class="none nobackground"><a href="http://ift.tt/1LK8jvh%20Pi%20GPIO%20Pins%20and%20Python" id="backforunical517" name="backforunical517" onclick="javascript:void window.open('http://ift.tt/1LK8jvh Pi GPIO Pins and Python','1410949501326','width=700,height=500,toolbar=0,menubar=0,location=0,status=1,scrollbars=1,resizable=1,left=0,top=0');return false;" style="background-position: -420px -120px" target="_blank"></a></li>
<li class="none nobackground"><a href="http://ift.tt/1WLPCrs%20Pi%20GPIO%20Pins%20and%20Python&pic=&ralateUid=&" id="backforunical517" name="backforunical517" onclick="javascript:void window.open('http://ift.tt/1WLPCrs Pi GPIO Pins and Python&pic=&ralateUid=&','1410949501326','width=700,height=500,toolbar=0,menubar=0,location=0,status=1,scrollbars=1,resizable=1,left=0,top=0');return false;" style="background-position: -450px -120px" target="_blank"></a></li>
<li class="none nobackground"><a href="http://ift.tt/1LK8gPW%20Pi%20GPIO%20Pins%20and%20Python" id="backforunical517" name="backforunical517" onclick="javascript:void window.open('http://ift.tt/1LK8gPW Pi GPIO Pins and Python','1410949501326','width=700,height=500,toolbar=0,menubar=0,location=0,status=1,scrollbars=1,resizable=1,left=0,top=0');return false;" style="background-position: -480px -120px" target="_blank"></a></li>
<li class="none nobackground"><a href="http://ift.tt/1WLPAQv%20Pi%20GPIO%20Pins%20and%20Python" id="backforunical517" name="backforunical517" onclick="javascript:void window.open('http://ift.tt/1WLPAQv Pi GPIO Pins and Python','1410949501326','width=700,height=500,toolbar=0,menubar=0,location=0,status=1,scrollbars=1,resizable=1,left=0,top=0');return false;" style="background-position: -510px -120px" target="_blank"></a></li>
</ul>
<div class="clear"></div>
</div>
View more at: <a href="http://yoursmart.mobi/">http://yoursmart.mobi</a>

Raspberry Pi GPIO Pins and Python

The GPIO pins on a Raspberry Pi are a great way to interface physical devices like buttons and LEDs with the little Linux processor. If you...

Your Smart IOT

Triggering littleBits LEDs with Node.js Using Johnny-Five

Raspberry Pi GPIO Pins and Python

Contact Form