Raspberry Pi GPIO
Sadly, there is no other way than CTRL+P

GPIO – general purpose input/output

Yes! These guys! Sticking out there like sore 40 thumbs. I’m sure, you have the general idea what these are for! This is where you attach those fancy cables to, before realising that nothing works. The pins are split in 4 main types

  • GPIO
  • 3.3V
  • 5V
  • Ground

I hope you read this before you messed about with the pins and cables as there is a chance of killing the individual pins, sensors or your precious RPI alone!

Voltage pins are self explanatory – RPI can supply power to your sensors or boards, either at 3.3V level or 5V. 3.3V is limited to 50mA (split pins 1 and 17) while 5V draws it directly from the microUSB and can have whatever is left after RPI has been powered up. Ground – is used to close the circuit, and any of the pins can be used interchangeably. Be careful not to short the 3.3V and 5.V pins as this can lead to the board damage.

Each GPIO pin is able to carry up to 17mA with limitation of 51mA being available across all pins.  For more power hungry projects consider a separate power source.

GPIO is where magic happens, as  behaviour of these pins depends on the software that uses it. The header provides 17 Pins that can be configured as inputs and outputs. By default they are all configured as inputs except GPIO 14 & 15.  They are also grouped in interfaces that are additionally available to you – expanding connectivity of your RPI.

Plugging cables randomly won’t get you anywhere, and can cause serious damage to your circuits or RPI. Despite 5V pins  provided, RPI operates on up to 3.3V current. If you connect higher voltage to any GPIO you will end up damaging it.


[code language=”python”]

import RPi.GPIO as GPIO

# to use GPIO number not the pin physical number
GPIO.setmode(GPIO.BCM)

#or to use the physical pin numbers (1-40) instead of GPIO number
#GPIO.setmode(GPIO.BOARD)

# setting up pins as I/O
GPIO.setup(3, GPIO.IN) #sets GPIO3 as INPUT
GPIO.setup(4, GPIO.OUT) #sets GPIO4 as OUTPUT

# to assign pin input value to a variable
input_value = GPIO.input(3)

# output to GPIO4
GPIO.output(4, True)

[/code]

 

To use any pin in a script you have to describe the pin in question ie. GPIO3 (for pin no 5) and declare how the pin is used. You can assign the pin as an Input or Output, or declare a specific interface. RPI will measure voltage levels on the pins and translate this into following states HIGH (3.3V present) and LOW (0V present) with about 10% tolerances.

When dealing with sensors or boards that output higher than 3.3V current – it has to be stepped down  to prevent damage. You can do so by ie using Logic Level Converter.

 

Interfaces:

pi3_gpio

In addition to general use of pins on the RPI, we have several interfaces available on the board expanding connectivity of our microcomputer. Trading off few pins at the same time we can provide additional functions and cross connectivity with other microboards.  To have a closer look at what interfaces are available on your board – have a  look on this interactive guide.

DPI (Display Parallel Interface)

This interface allows you to add  VGA connection directly from the pins itself. Supported resolution  ranges  from 640 x 480 up to 1920 x 1024 @ 60fps. If you don’t want to use HDMI connection – simply wire these pins accordingly and the video output will  be sent  to your display . You would be able to drive another desktop through the pins, but bear in mind you will use 22 pins to do so!

GPCLK (General Purpose CLock)

This interface allows you to ouput a specific hardware driven frequency. You will sacrifice 3 pins to use it. Available frequencies are predefined.

JTAG (Joint Test Action Group)

Interface uses 11 pins and allows to test and debug circuits on your RPI. Chances are you will never need this. But since you have asked…

PCM (Pulse-Code Modulation)

If you are looking for another way of outputting high quality audio – you can use 4 pin digital output that can be translated to DAC standard.

I2C (Inter Integrated Circuit)

4 of the pins are available as I2C connections, allowing to communicate with range of other devices supporting this standard. This way you can save other GPIOs on your RPI, for other purposes and communicate with various microcontrollers  via this bus. You would be able to connect an expansion boards to overcome RPI limitations. Using these allow also to reduce the GPIO hungry expansions like LCD displays, GSM/GPS etc. So if you ever find yourself lacking inputs/outputs on your RPI – look into expanding this bus.

SPI (Serial Peripheral Interface)

This is another standard that expands the connections of your RPI, using  11 pins allows  chaining your compatible devices together and read out the output on separate pins. This interface allows to link several slave devices to a single master.

UART (Universal Asynchronous Receiver Transmitter)

One of the older interfaces that allows for interactions with a lot of controllers. Receiving end is required to have UART hardware on board and commands are issued as 8-bit transfers with 1st and the last bits marking start and the end of the message. Voltage levels are ignored, so message can be coded using 3.3V, 5v or at even bigger current level.

2 COMMENTS

  1. A very nice roundup. There were a couple of things I hadn’t seen mentioned in a while, so that’s great! 🙂

    Of course you can buy/design hats to take the place of some of those output functions. For example, I prefer Adafruit’s “PWM/Servo Pi Hat” because I can control 16 PWM channels *per hat* via the I2C channel, and they can be stacked, with the stacking headers–for a maximum of 992 servos/PWM channels controlled from ONE PI! Note that each hat requires a separate power supply sufficient to run the devices attached. (For all LEDs, or even RGB LEDs, power output is minimal, so you could use small batteries. For servos you need more amps an AH. 🙂

    OK, sorry, I digress.

    Great article! Keep ’em coming,
    Leland…

    • Thanks for that Leland, I will be going into details with Arduino boards as well soon as my starting pack from the competition is already in the UK, scheduled for monday. It is good to know single RPI can hangle this many connections, as sometimes I was thinking that these 40 GPIOs may not be enough!! 🙂

Comments are closed.