Skip navigation
1 2 3 Previous Next

Raspberry Pi Accessories

69 posts

This is the first in a series we'll post about using BitScope Blade and the obvious place to start is unboxing and assembling it. Blade is a robust industrial deployment solution for Raspberry Pi. How you assemble it and the ways you can power and mount it will depend on how you want to use it. We'll follow up with more information about the power and software options and cover some new projects you can build with it. Read on here to get started...


BitScope Blade is available in three editions; Blade UnoBlade Uno, Blade DuoBlade Duo and Blade QuattroBlade Quattro. Each of them powers and mounts one, two or four Raspberry Pi. They also support a range of peripherals such as Raspberry Pi HATRaspberry Pi HAT, CamerasCameras, DisplayDisplay, BitScopeBitScope and a lot more.

We publish software for Raspberry Pi to make it easy to use and build solutions ranging from single test and measurement or embedded computing systems to full sized compute clusters. Check out this recent post to learn what Blade can do and some typical Blade applications.


In the post you're reading now we describe the Blade package and how to assemble it to get started.


In the package is the Blade (Uno, Duo or Quattro), a Quick Start Guide, Product Compliance Statement, a Safety Guide and set of screws, spacers and mounting tabs, shown here for Blade Quattro.

BitScope Blade Quattro Package Contents.

There are also 1, 2 or 4 red power shunts, one for each Raspberry Pi. The Raspberry Pi and a power supply are sold separately. Any software that runs on a Raspberry Pi and optional HATs stand-alone may be used with Raspberry Pi and HATs mounted in Blade. Blades also support specialised expansion (HUB Cards) and/or custom hardware via I2C, SPI, UART and GPIO on the underside of each Raspberry Pi.


A wide range of power sources, from plug packs to batteries or solar panels and more may be used with Blade.


We'll cover this in a separate post.

Assembling BitScope Blade

In principle, using Blade is as simple is plugging in one or more Raspberry Pi and optionally HAT, CAP or HUB cards, inserting a programmed SD card and connecting the power. However, there are few preparation steps first.

Step #1 Install Nylon Spacers

After unpacking your BitScope Blade, the first thing to do is install the nylon spacers.


Installing Nylon Spacers to BitScope Blade Reloaded.


These are required to mount the Raspberry Pi in each BAY and a HAT (if using Blade Uno). Repeat for each corner in each Raspberry Pi and the HAT BAY.


Step #2 Install Adhesive Stand-Offs (Optional)


The stand-offs make it easy to sit the Blade on a flat surface. Install them like this.


Installing Stand-Offs to BitScope Blade Reloaded.


There are four stand-offs supplied, one for each corner of the Blade. The stand-offs have adhesive feet so you can peel off the labels and stick the Blade to your desktop or use them to mount the Blade on a wall. Once they have been stuck onto a surface they cannot be removed (without destroying the adhesive) so choose where you want the Blade carefully before removing the labels. However, the Blade can be removed from the stand-offs by carefully squeezing the post.


Step #3 Check Power Shunt


The red power shunt should be pre-installed but if not, connect it as shown here.


BitScope Blade Raspberry Pi Power Shunt.


The power shunt allows the Raspberry Pi to be powered on and off without disconnecting power to the Blade itself. Normally it's connected and left as is. In a Blade rack or other type of multi-Blade installation and with Blade Duo and Quattro, it allows each Raspberry Pi to be individually powered down (e.g. to replace an SD card).


Step #4 The Raspberry Pi


If you're using Raspberry Pi 3 and plan to mount the Blade in an enclosure or a confined space with limited ventilation, we recommend you apply a heatsink like this.

BitScope Blade Raspberry Pi 3 Heatsink.

If the Blade is mounted vertically (e.g. on a wall) or in a ventilated Blade Rack a heatsink may not be necessary but if you're planning on doing some compute intensive work, we'd still recommend it. If you're using using Raspberry Pi 2 or Model B+ or A+ a heatsink is unlikely to be necessary. Heatsinks are sold separately.


Step #5 Camera & Display


The Raspberry Pi Camera and a touchscreen Display is supported, one for each Raspberry Pi on the Blade.

BitScope Blade Raspberry Pi Camera Installation.

BitScope Blade mounts each Raspberry Pi "upside down" and there is a slot in the Blade to pass through the camera cable. If you plan to use a camera, you will need to thread this cable through the slot before connecting to the Raspberry Pi. Once the cable is plugged into the camera connector, the Raspberry Pi is mounted on the Blade (see below).


If you want to use a Raspberry Pi Display as well, the connection is similar but located at the edge of the Blade. In this case you can connect it after the Raspberry Pi is mounted on the Blade. It's also possible to physically mount one Raspberry Pi Display on the Blade board itself. We'll devote a new post explaining how to do this. If you want to use an HDMI display, you can connect this to the Raspberry Pi in BAY 1.


Likewise you can connect an audio cable to the Raspberry in BAY 1 as well. In both cases, this can be done after the Blade is fully assembled.


Step #6 Install Raspberry Pi


Plug in a Raspberry Pi in each Pi BAY you plan to use on the Blade.


BitScope Blade Raspberry Pi Installation.


A reminder, if you're using a camera, you will need to connect the ribbon cable to the camera connector on the Raspberry Pi before installing the Raspberry on the Blade. And yes, the Raspberry Pi is meant to be installed "upside down" on the Blade! Ensure the Raspberry Pi is seated firmly before moving on.


Step #7 Install HUB Card (Optional)


If you're using one or more HUB Cards, connect them underneath each BAY as shown.


BitScope Blade HUB Card Installation.


It's probably best to install the card in BAY 1 before you connect the stand-offs. However, if the stand-offs are already installed they can be removed temporarily quite easily.


Step #8 Install HAT (Optional, Blade Uno Only)


If you're using Blade Uno, you can install almost any Raspberry Pi compatible HAT.


BitScope Blade Uno Raspberry Pi HAT Installation.


All the J8 connector signals from the Raspberry Pi are made available to the HAT BAY so regardless of whether the HAT uses GPIO, I2C, SPI or serial I/O, they will work with Blade. BitScope Blade also accepts BitScope "extended HATs" (which we call "CAPs"). These devices have the same form factor as Raspberry Pi and can be mounted on any Blade including Duo and Blade Quattro.


Step #9 Tighten Screws and Install SD Card


The last step before applying power is to tighten all the screws and install the SD cards.


BitScope Blade Tighten Screws and Install SD Card.


It's not strictly necessary to install the screws if you're planning to remove and reconnect the Raspberry Pi and/or HAT frequently as the friction of the connectors will hold both in place on a desktop. However, if you're using this in an installation we highly recommend all screws be used to ensure nothing comes loose.


When the SD card is plugged in, you're ready to connect power and use your Blade. Don't remove an SD card from a Raspberry Pi when power is applied to the Blade unless you have disconnected the BAY power from by removing the shunt. On Blade Duo and Quattro, it's also possible to signal or interrupt the Pi via this header.


Step #10 Connect Power via 2.1mm socket


Normally power is applied to the Blade via the 2.1mm power socket.


BitScope Blade Connect Power via 2.1mm Socket.


Any power source terminated with a 2.1mm (centre-positive) plug and rated between 9V and 48V of 20W or more (10W minimum for Blade Uno and Duo) may be used.


IMPORTANT: the original Blade boards used a 2.5mm socket. The new ones use 2.1mm. There are a number of reasons for this change which we'll explain an a forthcoming post. Adapters to convert between them are available.


Step #11 Connect Power via the tabs


There is an alternative way to power any Blade, via the mounting tabs.

BitScope Blade Connect Power via the mounting tabs.

Alligator leads are shown here to make polarity clear but normally this method of power is used in Blade Packs and Blade Racks to minimise power wiring like this:

BitScope Blade Cluster Pack Example - It's Alive!

It's not necessary to use the tabs, indeed they can be shorted together and power applied via the 2.1mm power sockets on each Blade (because Blades include a blocking diode). At this point you're ready to go. There are quite a few things we've mentioned but not yet explained such as BitScope CAPs, BitScope Blade Cluster Packs and Racks, power supply options, software choices and more. We'll publish full details in new posts soon.


Post reprinted with permission from the BitScope Blog.

Following our post about the Blade weather station in Nepal, this one describes an interactive exhibit created with BitScope Blade UnoBitScope Blade Uno, BitScope CAP and a Raspberry Pi 3Raspberry Pi 3. The BitScope Blade was used to conveniently power and mount the Raspberry Pi and BitScope to create a stand-alone oscilloscope and spectrum analyzer as part of the museum exhibit.


The MAAS PowerHouse Museum sought to create an interactive exhibit to demonstrate how a Theremin works. They originally thought they'd bundle up a bulky and expensive oscilloscope and associated electronics to display the Theremin output but after meeting us the Sydney Maker Faire they decided to try something smaller and easier to mount which operated without user intervention.


They ultimately built this impressive exhibit.


Why did they do this?

The Powerhouse Museum offers visitors a wide range of interactive exhibits.

Advocates of learning by doing and having fun while you do it, they sought to create an entertaining exhibit where visitors could play the theremin hear the results.

However, it was not enough just to be able to hear the instrument play, they wanted to be able to visualise the sounds it produced to help explain how the instrument works.

They sought a cost effective solution that could be built into the exhibit itself. It needed to be reliable, start without operator intervention and continue to work 24x7 when powered on.

Built with BitScope, Blade Uno and Raspberry Pi

MAAS used BitScope Blade UnoBitScope Blade Uno together with a Raspberry Pi, BitScope and LCD monitor to build the exibit.


Together with the off-the-shelf accessories shown here they had everything needed to build the installation.

The Raspberry Pi, powered and mounted on the BitScope Blade Uno, provided the compute platform to drive the display (via HDMI) and it ran the BitScope application.

The BitScope itself, also mounted on the Blade, was connected (via USB) to the Raspberry Pi and powered by the Blade.

The Theremin output was connected via splitters (so they could also be connected to a sound amplifier) and BNC terminated coaxial cables to the analog inputs via a BitScope probe adapter.

The entire assembly was mounted on the exhibit via the Blade's M3 mounting tabs, and the power, HDMI and audio cables routed through the back and is powered by a single 12V adapter.

BitScope Pi on Display

The team at MAAS decided this assembly should be part of the exhibit itself, so they housed it in a transparent case.


Mounted on the exhibit next to the display and above the Theremin it resulted in a visually appealing exhibit for visitors to interact with, hear the sounds produced and watch the waveforms as they played.

We enjoyed working with the MAAS team to put this together and we're impressed with the museum exhibit they built.

BitScope Pi Industrial

This exhibit proved to be a great example of what a Raspberry Pi, BitScope and a BitScope Blade Uno can do but it's not limited to just exhibit installations.

With the launch of the new BitScope Blade range with our friends at element14 last week, we'll publish more examples like this explaining how BitScope, Blade and Raspberry Pi can be deployed.

For example, shown here is a Blade Uno with a Raspberry Pi, a PiFace Digital 2PiFace Digital 2 and a pair of BitScopes (underneath).


An assembly like this offers the ability to capture, analyse and display four high speed analog channels and 16 digital via the BitScopes while also controlling up to ten digital outputs (two via relays).

All sorts of industrial modules like this can be built with Raspberry Pi, BitScope and the full range of Raspberry Pi HATs from third parties using BitScope Blade Uno.

If you have specific application requests or examples of your own, contact us!

About the Theremin

An test instrument like BitScope MicroBitScope Micro is the perfect tool to display and analyze what the Theremin can do and we're big fans of all sorts of electronic musical instruments, so we thought we'd post some information about the Theremin itself.

Leon Theremin plays his instrument.

The Theremin is the world's first electronic musical instrument.

Invented in 1920 by Lev Termen, also known as Leon Theremin, it was a by-product of research into proximity sensors in Russia around that time.

It's played without touching it.

The Theremin consists of a box-like body with two antennas: one is a straight vertical rod which controls the pitch (usually on the right for right-handed players), the other is a horizontal loop (usually on the left) shaped somewhat like a cane handle which controls the volume. The pitch and volume of the note are controlled by the distance of the hands from the antennas.

The block diagram below outlines the basic circuit.

The Theremin employs heterodyning, an electronic technique that mixes two oscillators operating at different frequencies to produce a new lower frequency equal to the difference between them.

In the case of the Theremin, it's the pitch you hear.


The pitch oscillator operates at a very high (RF) frequency making it very senstive to any changes in the capacitance in resonsant circuit from which it's built. Moving your hand around the pitch antenna changes the capacitance which changes the frequency of this oscillator and therefore the heterodyne pitch that is produced.The volume control also works via proximity of the performer's hand to the other antenna.

In this case it changes the "efficiency" of the a separate RF oscillator. The closer your hand is to the antenna the lower the amplitude of the oscillator. This amplitude is turned into a volume signal using an envelope detector (a diode rectifier) and applied to the output changing the volume heard at the output.

In the case of the MAAS exhibit, the Theremin output is displayed as a waveform and (optionally) as a spectrum. As visitors play the Theremin they can see the waveform pitch (visible as a changing number of waveform cycles on the display) and the volume (visible as the vertical size of the waveform).

While they did not do this, it would be possible to use the BitScope to display the operation of the pitch and volume oscillators inside the Theremin and analyse how its electronic circuits work but we'll leave that for another day!

Post reprinted with permission from the BitScope Blog.

We launched the new BitScope Blade product range exclusively with element14 last week. To help explain how BitScope Blade works and what you can use it for, we'll be publishing a series of posts, of which this is the first, describing some example applications that can benefit from using Blade to power and mount Raspberry Pi, sometimes in quite challenging circumstances.


In this case, a team lead by Prabesh Sapkota and Binod Kandel from the Robotics Association of Nepal↗ built a battery backed solar powered weather station at very low cost using BitScope Blade UnoBitScope Blade Uno, Raspberry Pi and Arduino. The result of a series of STEM workshops created and lead by Australian educator Michelle Jensen↗ in 2016 and run with the help of Nepalese enthusiasts, this amazing project showed how BitScope Blade can be used to power electronics and computers in remote areas without access to reliable power.


Why did they do this?


Weather forecasting in Nepal is difficult because there is no national weather service and the high mountains produce highly variable conditions within just a few kilometres. A reliable and inexpensive weather station is therefore a vital tool for farmers and those living in remote villages. The weather station design had to be very low cost, reliable, easy to maintain, operate on solar power and use readily available motorcycle batteries for when the sun does not shine.


Raspberry Pi, BitScope Blade and Arduino

Clearly Raspberry Pi and Arduino are ideal as the basis for building a system like this. The problem for both platforms is how to get a reliable source of uninterrupted 5V power to run them.


BitScope Blade Uno offered the perfect solution, powering the Raspberry Pi directly and the Arduino via one of its auxiliary power ports. Shown here are the core components put together initially as a prototype with a breadboard just to prove it all worked when powered from a 12V source. It did, so Prabesh and Binod pulled together all other materials required:

  1. Arduino UNO
  2. Raspberry Pi 3
  3. Raspberry Pi 7" Touch Screen Display
  4. GPS Module (NEO-6M-0-001)
  5. Pressure sensor (BMP180)
  6. Humidity sensor (DHT11)
  7. 12V Lead Acid Battery
  8. 20 Watt Solar Panel
  9. Hall Effect Sensor (anemometer)
  10. Reed Switch (8 pcs) (wind direction)
  11. PVC pipes, wood, bearings
  12. PCB (Printed Circuit Board)

The Weather Station has sensors for temperature, barometric pressure, humidity, wind direction and speed as well GPS coordinates. All the sensors are connected to the Arduino to record data which is then sent to the Raspberry Pi for capture and display on a dashboard. Prabesh and his team wrote the weather station software and created the display dashboard all running in Raspbian Jessie for the Raspberry Pi.


Building the Prototype


Binod built the prototype assembling all the electronics using the breadboard before the PCB was ready.


Key to the project was BitScope Blade Uno because without it, it would not have been possible to power the system. When deployed, power is provided by a 12V lead acid motorcycle battery. A 20 Watt solar panel charges the battery and can also provide direct power.


As the sunlight varies during the day and as the battery charges and discharges, the supply voltage in a simple system like this can vary considerably. The system works well because BitScope Blade has an efficient built-in voltage regulator to manage the variable supply accepting any input voltage from 9V to 48V and producing a reliable 5V at up to 4A output for the Raspberry Pi, Arduino and all the sensor electronics. As Prabesh said, "The Weather Station would not be possible without the Blade. It made the whole project for us."


Weather Station One

With all the components assembled and testing the first weather station was installed.


The assembly was mounted on the roof.

The electronics was housed in a simple waterproof plastic container and the 12V battery positioned beside it under the adjoining roof.

The solar panel was mounted beside the electronics and the anemometer for wind speed and the wind vane for wind direction mounted on wooden panels next to it.

It was a fascinating and highly educational experience for the people involved.

Having proven reliable in operation since September 2016, the team are now planning to run a series of regional workshops on basic electronics with the assistance of their Australian sponsors and install more weather stations in rural schools and remote areas. Arduino made connecting and using the sensors easy. Raspberry Pi was at the heart of the monitoring and display system and BitScope Blade Uno provided the platform required to mount the Raspberry Pi and power the Pi, Arduino and all sensors. All that was required was a 20W solar panel and a standard 12V lead acid motorcycle battery (as the uninterruptible power supply battery) to run the station 24x7.

Raspberry Pi is increasingly popular in developing countries but reliable power is often not available. Blade offers a low cost solution enabling the use of Raspberry Pi and other electronics when grid or other power sources are unreliable.

Post reprinted with permission from the BitScope Blog↗.

Having had some fun playing with the display on the Sense Hat I moved on to trying to utilise the Joystick. However copying the examples set out in the Sense Hat API results in the following error


AttributeError: 'SenseHat' object has no attribute 'stick'


Upon further investigation it turns out that the library doesn't include any functionality for the joystick, trying to run sudo apt remove --purge sense-hat then sudo apt-get update and sudo apt-get install sense-hat only installs the same version without the joystick functions.


Navigating to the github repositories shows that there is an updated version that does include the joystick functions, to get the updates were going to have to manually install them.


Time to implement the update!!


Step 1.


Open up a terminal on the Raspberry Pi (or if your going over ssh just use the terminal your already in).


Navigate to the sense_hat python directory

cd /usr/lib/python2.7/dist-packages/sense_hat


delete the existing files

sudo rm __init__.pyc sense_hat.pyc


Step 2.


Download the new files straight from github


sudo wget 
sudo wget 
sudo wget 


Step 3.


We just need to make a slight alteration to the file that was downloaded, open the file using nano:

sudo nano



Line 17 (highlighted in the picture below) reads


from .stick import SenseStick


the .  needs deleting from in front of the work stick so it reads:

from stick import SenseStick


Press ctrl+o then enter to save changes and ctrl+x to exit nano.




Thats it! happy playing!!


Here's an example code and video showing how to move a pixel around using the joystick:


from sense_hat import SenseHat
sense = SenseHat()

x = 3
y = 3

def draw_dot():

def pushed_up():
 global y
 y = y - 1
 if y < 0:
  y = 0

def pushed_down():
 global y
 y = y + 1
 if y > 7:
  y = 7

def pushed_left():
 global x
 x = x - 1
 if x < 0:
  x = 0

def pushed_right():
 global x
 x = x + 1
 if x > 7:
  x = 7

sense.stick.direction_up = pushed_up
sense.stick.direction_down = pushed_down
sense.stick.direction_left = pushed_left
sense.stick.direction_right = pushed_right




Product development specialists, Think Engineer are set to launch a revolutionary new accessory for the Raspberry Pi hardware. CapHat is a new HAT for all versions of the Raspberry Pi, featuring  an easy to use capacitive keypad that gives creators and educators an unlimited array of possible functions to add to their Raspberry Pi hardware.


Simply clicking on to the Raspberry Pi GPIO Header, the CapHat offers a full, numbered keypad, so you can keep on adding accessories as you create. Fully licenced with the Raspberry Pi, the CapHat is officially hardware compatible with the A+, B+ and 2, as well as the brand new Raspberry Pi 3.


This product will go live on Kickstarter on 14th November 2016. Please take a look at some of our fantastic early bird pledges.



Sense HAT in Pi IoT

Posted by jwatson element14 Team Sep 6, 2016

Raspberry Pi Sense HAT Projects

Pi@Night Competition

This competition is now over! Look out for the opportunity to vote on the finalists on the 18th of May!


Get snapping for your chance to win a Raspberry Pi Camera Bundle Kit!

With the launch of both the Pi Camera V2 and the PiNoir Camera, we’ve decided to give away 5 Raspberry Pi Camera bundles, and here’s how you can win;


Step 1: Take a picture of a location, building or similar that looks visually stunning (during or after sunset)

Step 2: Post that picture on one of our social media channels (Twitter, Facebook, Google Plus) using #GetConnected

Step 3: Sit back and relax knowing you’re in with a chance of winning!


We’ll pick the five best images to win...but that’s not all!


The 5 winners will also feature in an online poll on the element14 Community where our members will vote for the supreme winner who will then receive another Prize which includes the 7" Touchscreen, Cirrus Logic Audio Card and both the new 8mp Camera and  the 8mp Pi NoIR Camera!


This competition is now over! Look out for the opportunity to vote on the finalists on the 18th of May!


T&Cs apply- full terms and conditions here.

1. This Competition is run by Premier Farnell plc (Premier Farnell or we (including our or us) on the following terms and conditions. Anyone who enters this prize draw is referred to in these terms and conditions as entrant or you.

2. In entering this competition you agree to be bound by the terms and conditions applicable to this prize draw at any time (the T&Cs). Please note that this includes agreeing to your name and town and country of residence being disclosed as a winner if requested by any other entrant in accordance with 6 below.

3. Premier Farnell reserves the right to change these T&Cs at any time; amended T&Cs referring to this giveaway will be updated in situ at the URL where you found them.

4. This competition will run during the period from 9:00 GMT on 25 April 2016 until 15:00 GMT 9th May 2016 unless decided otherwise and updated as referenced in point 3.

5. This prize draw is not open to:

    • Anyone below the age of 18 years;
    • Anyone who is a public sector employee;
    • Anyone who is an employee of Premier Farnell, any company in the Premier Farnell group of companies or any agency representing Premier Farnell, or anyone employed by Premier Farnell within the last 3 months of the date of the prize draw running start date as in point 4.
    • More than one person per household, typically, this decision is at the discretion of the element14 Community and Social Media staff or other Premier Farnell employees deciding on qualifying entrants to the prize draw.
    • Any business, corporation, company or otherwise reasonably understood trading business entity, or any social media account representing any such company or entity.

6. To enter the competition, entrants must post a photograph of a landscape, building or other location along with the hashtag: #GetConnected in the messaging - to one or all of available social media channel(s) such as: Twitter, Google+, or Facebook. Only one entry, that is, one post from any social media channel, will be accepted per person, regardless of the number of entries posted.

7. Any post which includes material which we consider to be offensive, abusive, derogatory, inflammatory or likely to cause offence will be excluded from this prize draw.  Premier Farnell, element14, element14 Community and Social Media staff’s decision on this will be final and no correspondence on this issue will be entered into.

8. No purchase is necessary to enter this competition.

9. Premier Farnell will choose 5 entrants to be shortlisted, with their images being placed on the element14 Community where members will vote for the outright winner.

10. The 5 shortlisted entrants will all win the new Pi Camera V2 and the overall winner will also win the Pi NoIR V2, 7" Touchscreen, Cirrius Logic Audio

11. The Prize is non-negotiable and non-refundable and no cash alternative will be offered. We reserve the right to replace the Prize with other goods of similar, lesser or greater value as we see fit in its sole discretion. There is no right to any refund or replacement or maintenance in respect of any Prize returned.

12. Winners must supply a valid postal address and contact name in order to receive a Prize. The Prize will be sent by a delivery method chosen as fit by the organizer and is not restricted to any singular method. Premier Farnell is not liable if the Prize is lost or damaged in transit. Premier Farnell reserves the right to refuse to supply a Prize in the event that doing so would be in breach of any import or export regulations to which Premier Farnell is subject or if any licences or permissions are required to supply or ship a Prize and in such event the relevant Winner will be disqualified and no replacement prize will be provided.

12. No responsibility will be accepted for entries which fail to be received for any reason, including technical error. Premier Farnell is not responsible for hardware or software failures of any kind for any attempted entries; lost or unavailable network connections; failed, incomplete or garbled computer or telephone transmissions; typographical or systems errors; problems or technical malfunctions of any telephone network or lines, computer online systems, servers, providers or computer equipment; or technical problems or traffic congestion on the Internet or any combination thereof. Premier Farnell is not responsible for any injury or damage to entrant's or any other person's computer related to or resulting from this prize draw or other telecommunications malfunctions, which may limit an entrant's ability to participate.

13. Premier Farnell reserves the right to verify the eligibility of any winner before a Prize is sent or offered and may require proof of identification and age. If Premier Farnell suspects fraud or misconduct, (including without limitation any attempting to undermine the legitimate operation of the prize draw by cheating, hacking, deception, or other unfair practices or intending to annoy, abuse, threaten or harass any other entrants or our representatives) or a winner or potential winner does not meet the eligibility requirements, his or her Prize may be withheld or withdrawn and another potential winner selected. The eligibility requirements include the requirements of 15 below.

14. To the extent that we may lawfully do so, we reserve the right to withdraw or amend the prize draw or extend the period of participation in our sole discretion, including (without limitation, in circumstances where such withdrawal or amendment results from events beyond our control or is undertaken to comply with any law or regulation binding on us in any country. Premier Farnell will not be liable for any such withdrawal or change to the prize draw. If, for any reason, this prize draw is not capable of running as planned due to infection by computer virus, bugs, tampering, unauthorized intervention, fraud or any other causes beyond our control, which corrupt or affect the administration, security, fairness, integrity, or proper conduct of the prize draw, we reserve the right at our sole discretion to cancel, terminate, modify or suspend the prize draw.

15. Entrants and winners are responsible for all applicable taxes, duties or other charges payable in relation to this prize draw or any Prize.

16. You may not enter the prize draw if, by doing so, you may cause Premier Farnell and/or you to be in breach of any agreement (including but not limited to any contract of employment) to which you are a party or in breach of any duty, law, regulation or rule having the force of law to which you or Premier Farnell may be subject. Premier Farnell reserves the right to disqualify any entry made in breach of this condition.

17. Premier Farnell respects the policies of employers which forbid entry to and/or the acceptance of prizes by their employees. If requested to do so by Premier Farnell, a winner must obtain signed authorisation from duly authorised senior employee of his or her employer confirming the winner’s permission to accept the Prize.

18. The Prize is not supplied with the benefit of any warranties from Premier Farnell and is only supplied with the benefit of any warranty which may be provided by the manufacturer of the relevant item. All further warranties or representations are hereby expressly excluded to the fullest extent permitted at law. Without limiting the generality of this exclusion, Premier Farnell hereby excludes all and any liability arising out of the prize draw or the acceptance, use, quality condition, suitability or performance of the Prize, even where arising from Premier Farnell’s negligence.

19. Premier Farnell does not exclude liability for death, personal injury arising or damage to property from its negligence, or for breach of Part II of the Consumer Protection Act 1987, for fraud or for any matter in relation to which it would be illegal for Premier Farnell to exclude or attempt to exclude our liability.

20. Any dispute or claim arising out of or in connection with it or its subject matter shall be governed by and construed in accordance with the law of England and Wales and you irrevocably agree that the courts of England and Wales shall have exclusive jurisdiction to settle any dispute or claim that arises out of or in connection with this prize draw.

21. Please address any queries relating to this prize draw


After a forced pause the Essential Raspberry Pi Peripherals articles series finally restarts with a new proposal. The Pi-Scope lab tool is the first of a series of tools to empower the electronic lab based on the Raspberry PI 2Raspberry PI 2 , Raspberry PI lcdRaspberry PI lcd and Bitscope microBitscope micro

There is already an interesting Ben Heck episode, Episode 223: Ben Heck’s Raspberry Pi Bitscope Mod Episode modding these three devices creating an oscilloscope. It is my opinion that this proposed version has some limitations, so I have searched how to develop a device architecture based on the Raspberry Pi integrating different features to support in the best way the daily lab activity.

First of all I aimed to make a robust support for the components keeping in the same time all the expansions ports open to any possible integration and development. It is not the first time that I try to box in a elegant way the Raspberry PI together with other parts like in this case, but this always means limiting some features of the device. The container has been based on the model presented on Instructables Raspberry PI Touch Screen Frame and Case Assembly Guide with some changes and adaptions.


Project goals

  • Bitscope micro has a form-factor useful for usage as a probe with status LEDs that should remain exposed for the best use
  • The touch screen should be easily accessible and visible while the oscilloscope probe can be easily used nearby to the tested parts
  • The Raspberry PI ports should be easily accessible, for some kind of usages also while the oscilloscope is connected (e.g. an external keyboard)
  • All the case components should be 3D printable and easy to assemble to simplify the creation of the system
  • A "Super Interface" should be provided to control the different working modes of the Bit Scope software and other future tools
  • The device should be able to access the Internet when needed
  • The entire system should be open for future developments and enhancements


The 3D model

The images below shows the assembled model of the components (the stl files are available in attach to this article).

3D View Front.png

The front view of the model

3D View Back.png

The back view of the model

3D View cut01.png

The section view of the parts

Pi-Scope in use

IMG_20160402_154135.jpg IMG_20160402_154142.jpg

The following short video shows the Pi-Scope usage while testing the state of a stepper motor PWM signals


Next setps

As the Bitscope mini software is a suite of several applications it is needed a startup interface, specifically designed for the Raspberry touch screen as the main launcher when the system starts. The same interface will host software to control other tools connected to the device.

I love the Pi Screen, there are a few cases out there now but no open source ones that can be laser cut [that I know of], well now you have one.


The Case:






The Files:

Also I dislike not using the full sheet when cutting, the design includes two Pi Zero Cases [Made by alan of ]



Finding a Laser cutter in your area:


There are loads of places around the globe that will give you some free time on a laser cutter, try google for :

>FabLabs in your Area



[Any ive missed guys?]


Want to buy one?

If you are in the Uk I can make these and sell them for £15 +p&P [Email:], shipping might get expensive for america but Another E14 member has another case for sale at that side of the pond:

Essential Raspberry Pi Peripherals #2 (annex 2): 7" LCD touch screen display installation notes


In this fourth article of the series Essential Raspberry Pi Peripherals we will see how to install the Pi CameraPi Camera and the 2.4" Touch Panel2.4" Touch Panel on the Raspberry PI 2Raspberry PI 2. In the next article we will use this base setup to make a PI Camera where the PiFace CAD LCD display is be replaced by the 2.4" Touch Panel.

The components we are using are shown in the image below including a small and almost inexpensive (about 5$) LinkSys WiFi USBLinkSys WiFi USB dongle and a class 10 8Gb Micro SD card.


Note: if you have only one of the two devices you can follow this guide excluding the parts that refers to the other (the camera or the touch panel) alternatively.



But it's not all! As we are trying to modernise the PiFace CAD based Raspberry Camera, why not starting with Jessie, the new, updated Debian Linux distribution for the Raspberry PI 2?


Raspbian Jessie installation

Jessie is the latest updated distribution of the Raspian version, a Debian distro for the Raspberry PI. This new version in my opinion it is the worth to use it because the new 4.x Linux kernel and a series of improvements specific for the Raspberry PI platforms gives the clear impression to be a mature version than the previous. After creating the bootable image on a microSD card you should just insert it in the board and power it on. There is plenty of tutorials online on how to prepare the Raspbian bootable microSD card but the better way, covering all the desktop platforms is on the site from where you can also download the last updated Jessie image file.


Just from the first boot you immediately see that process is extremely fast. Better if you have done this with the previous Linux versions to see the difference.

The most notable feature is the new version of the Raspberry setup directly accessible from the setup. All the options available in the raspi-config command are now accessible through a more comfortable user interface.

Screen Shot 2015-11-17 at 10.33.46.png Screen Shot 2015-11-17 at 10.33.56.png

Screen Shot 2015-11-17 at 10.34.05.png Screen Shot 2015-11-17 at 10.34.20.png

The four images above shows the four sections of the Graphical User Interface version of the Raspberry PI settings with the suggested settings for the setup we need.


Note: as far as I know it is not mentioned anywhere but confirming every panel you are asked for reboot despite the changes you apply. I suggest to follow this method (that means four reboot if you change at least one parameter on every panel to be sure that changes are saved permanently. For those who has problems with the previous wheezy version on the locale and keyboard settings, this issue has been solved. After setting the parameters in the fourth panel Localisation the settings are correct and the terminal warning of a wrong locale never appear.


Camera setup

After the linux installation, power off the Raspberry PI and connect the camera cable to the camera plug as shown in the following images. Pay attention to the side of the flat cable else the camera is not recognized by the system. If your Raspberry PI does not recognises the camera, the most probable issue depends on the incorrect cable orientation.

IMG_20151117_085538.jpg IMG_20151117_085546.jpg

The camera software installation is easy. The most complete and simple tutorial to follow is in the Element14 Pi Camera introductory guide.

After the installation and testing as shown in the tutorial, it is not needed you go ahead, we will step back to this device when all the parts are set correctly.


Two words before the touch panel installation...

I think that the 2.4 inches HAT component from 4D and Element14 is really a great device. For the project we aim to make it sounds simply perfect! It is true that this small screen, despite the small size and the resolution limits is able to show the Raspberry PI desktop acting as primary screen. The following video gives an idea of what you can see after the setup.

As a matter of fact, what we need is something more specific for this kind os screen.


Last tip before the touch panel installation

The last couple of things you should do before proceeding to the next step installing the touch panel is to be sure that the network is connected and check your Raspberry PI IP address. You can use the ifconfig command from the terminal and write down the assigned IP address: maybe on the eth0 or wlan0 interface, depending on how you have connected the Raspberry PI to your network.


It is also strongly recommended that you enable the Raspberry PI for remote access before starting the setting of the touch panel. In my case I have used the SSH connection from Mac but any other method to access the PI remotely is good. This will be very useful for any further setup and programming.


Installing the touch panel

At this point our system is ready for the last step, the touch panel setup and installation. It is not needed that you insert the device in the Raspberry PI GPIO pin array for first. You can do it at the end of the installation, as you prefer it's up to you.


There is a very good tutorial for the basic setup of this device accessible from the introductory document of the product page 2.4" HAT Primary Display for the Raspberry Pi  (the same pdf document can also be downloaded from the bottom of this post).


Follow the installation instructions until you are asked for the last reboot after inserting the touch panel in the Raspberry PI. After the reboot we see the desktop running on the touch panel.


Note: There is an easy-to solve issue in the installation manual: you are asked to set the sudo su before the installation commands; this means that all the further commands are sent as super user. The last command in the manual is preceded by sudo again: write the command without the sudo word because you are already in a super-user environment. That's all.


Using the Raspberry PI with the 2.4" HAT Touch Panel


Nice eh? Yes but almost unusable. This is the reason that we do somethings to make it better...


Touch Panel post-install notes

The installation of the touch panel replace some components of the original Jessie Linux Kernel with custom ones. This means that some features you have set in the kernel maybe lost. In particular, the Raspberry PI Consiguration settings (the four panels explained above) should be reviewed and applied again (depends on the settings you have used before).


When also this operation has been completed and the last reboot has been executed we are ready to move to the next step.


Forget Kivy (for now

The Kivy installation has been already explained in the previous article of this series Essential Raspberry Pi Peripherals #3: The kivy framework for small display and touch screens Just to avoid difficulties due the limitations of the 2.4" Touch Pane, Not only but the Raspbian Jessie kivy installation has been updated, extremely simplified and optimised: it can be done in few stepsSo, why not? Unfortunately the 4D Touch Panel is connected to the GPIO and can't be managed by the fast video channel used by Kivy (that means no hardware acceleration). If you try installing this framework, running the provided examples everything seems working but the screen does not change. We should find a different way to solve the User Interface design for a more comfortable use of the screen.


The PyGame Framework for UI design

The reason we can use the PyGae Framework depends on the possibility to address the UI design in Python without the graphic acceleration.

Again, if we try to launch one of the games examples we find in the Python Games folder of the Raspbian installation we see nothing.


As a matter of fact we have missed to address the graphic interface to the display on /dev/fb1 framebutter. To have the Python graphic framework working properly we should add on top of every program the following two lines:


import os
os.environ["SDL_FBDEV"] = "/dev/fb1"

In the next post we will see in detail how to create a touch user interface to manage the Raspberry PI camera to shoot images.


Available for the Raspberry PI at the actual date the market offers a number of touch screen displays; the recent launched Raspberry PI 7" LCD touch screen displayRaspberry PI 7" LCD touch screen display and the 2.4" HAT display2.4" HAT display are the top accessories in their range. These devices can be used as primary display including the touch screen they can replace the standard HDMI display, USB keyboard and mouse.


It is almost obvious that the 2.4 inches screens are less useful than larger screen (i.e. 15 inches or more): but represent a great solution for a large number of projects and applications.

A common UI design is difficult to manage and more difficult to interact with when the user should manage a 2.4 inches (or less) small screen or trying to use complex interactive interfaces also on a 7 inches screen.


Take a look to the following video.

If you like this kind of interface you are in the right place. Full colour graphics, multi-touch management, easy and visible interaction widgets also on small screen sizes, reasonably fast and responsive interfaces and more. The features shown in the video above are only some of what can be achieved with the Kivy python framework.

Note: the frame assembly of the Raspberry PI LCD Touch Screen display shown in the images of this post is available on the Drobott site. Don't forget to apply the Element14 discount code W0E49MYQ (10% off) reserved to the community users!


The framework

The adoption of this framework for the User Interface with the Raspberry PI is the better solution when the touch screen is the main tool to interact with the application. For the developers this framework is simple to manage, entirely developed in Python and very well documented with plenty of examples.


Wikipedia reports the definition of the Kivy framework as

Kivy is an open source Python library for developing mobile apps and other multitouch application software with a natural user interface (NUI). It can run on Android, iOS, Linux, OS X, and Windows. Distributed under the terms of the MIT license, Kivy is free and open source software.

but the term library is reductive; kivy is a set of libraries integrating features of many different environments. The recent porting available for the Raspberry PI Raspbian makes kivy one of the best solution for the UI design on touch screens and small displays.


The X desktop (the Raspbian desktop is an example) has never been though to be controlled by a touch-screen or an on-screen keyboard. In fact the kivy framework works perfectly just in these cases, so it's time to move on the Raspberry PI terminal and start the installation.


Installing Kivy on Raspberry PI

The main reference site is On the site - not reported in the documentation index - there is a short page with a tutorial on Installing kivy on Raspberry PI. Unfortunately this is the only page I have found and is a bit outdated. The actual available version of the framework runs perfectly on all the Raspberry PI models including the PI 2, despite that the documentation report as untested.


Installation options

Two installation options are possible: the manual installation under Raspbian and the Kivy distribution image for the Raspberry PI.

I have tested both. The special PI distribution (derived by Raspbian) can be downloaded from the site KivyPie - Kivy on RaspberryPI but seems not well working so we will exclude this option and take in consideration just the manual installation.


Manual installation

The first thing to do is adding the repository to the list. From the terminal launch the editor


$>sudo nano /etc/apt/sources.list


and add the following line: deb . main

The resulting file will show like in the image below.

Screen Shot 2015-10-01 at 23.09.03.png

Save the file then launch the next commands:


$>sudo apt-get update
$>sudo apt-get upgrade


Before installing the framework you should install the dependencies of the packages:


sudo apt-get update
sudo apt-get install pkg-config libgl1-mesa-dev libgles2-mesa-dev \
  python-pygame python-setuptools libgstreamer1.0-dev git-core \
  gstreamer1.0-plugins-{bad,base,good,ugly} \
  gstreamer1.0-{omx,alsa} python-dev


Note: you will receive a warning for some uncertified packages. Ignore this message and confirm when required to proceed.


The next step needs to install pip from the sources. Pip, aka Pipi is the Python Package Index; It is a specific python packages repository working in a similar way of the apt-get (the aptitude Debian package manager). A full detailed list of the available packages in pip is available on the pipi-python site.


sudo python


Installing and compiling the pip package manager on the Raspberry PI may require 10 minutes or more. Don't worry and wait ... During the installation you will get some error messages due the wheel command is not found; don't stop the process and ignore these messages. Wheel is a package image builder not intended for use in our case. The error message you get is shown in the image below.

Screen Shot 2015-10-01 at 14.21.33.png

Cython is the c-extension for python and is used by some components of kivy. For a detailed description see the cython wiky.

At the end of the process described above cython should be installed in your system. We use the pip repository to acquire the last updated version, avoiding the eventually outdated version available in the Debian packages.


sudo pip install cython


At this point, we are are ready to clone kivy from GitHub and compile it locally


git clone
cd kivy


Fine! We have completed the most boring part. The kivy sources now are in the user home directory, for example the user pi. It is also possible to install kivy only in the user folder but this way creates many issues when developing applications that will rung accessing other folders so we install the framework globally.


python build
sudo python install


The two commands above should be launched from inside the kivy directory in the user folders. You should already be there when the step ends. This operation requires 5-15 minutes or more, depending on the hardware model and processor speed of your Raspberry PI board.

A couple of other steps and our newly installed framework is ready for the first run.


Post-install settings

There are some features of the kivy framework requiring some external components to be installed afte the framework installation is complete.


sudo pip install pyglet docutils
sudo pip install pygments


The last operation is to edit the user kivy configuration file to set the raspberry PI touch screen replacing the mouse. Edit the kivy configuration file with the command


nano ~/.kivy/config.ini


and add the following lines in the [input] section (other similar lines should be replaced)


mouse = mouse
mtdev_%(name)s = probesysfs,provider=mtdev
hid_%(name)s = probesysfs,provider=hidinput


Save the file and reboot the system. Now you are ready to launch your application or run the examples in the folders you find in ~/kivy/examples



There is a considerable number of places on the Internet, including the Element14 site, showing useful information on the installation and settings of this brand new device; in the meantime a number of doubts and questions has raised about the touch screen settings, the on-screen keyboard installation and more. The goal of these notes is to depict a setup scenario as much complete as possible. The Raspberry PI 7" LCD Touch Screen displayRaspberry PI 7" LCD Touch Screen display is the perfect replacement of a dedicated screen, with the plus of the optional on-screen keyboard.


To use this device in a Raspberry PIRaspberry PI project requiring User Interaction it sounds almost difficult in applications like robotics, machines control, informative point, web access, sensors gauges etc.

A reliable solution exists and its name is Kivy: open source, not too difficult to install and is based on Python.


Note: the frame assembly of the Raspberry PI LCD Touch Screen display shown in the images of this post is available on the Drobott site. Don't forget to apply the Element14 discount code W0E49MYQ (10% off) reserved to the community users!


What raspbian release?


The first thing to do it to decide what raspbian image should be installed on the PI. If you have already a Raspberry PI with an existing raspbian version on it, you should install the hardware then power on the system and proceed with the software.


If you should start from scratch instead, I suggest to download the last raspbian updated image (2015-05-05-raspbian-wheezy.img at the date) from the site to create a bootable microSD card; you  can choose between two different flavours: raspbian based on Debian wheezy or Debian jessie; this choice is up to you. At the actual date it seems that the Raspberry PI porting of the Jessie distribution has again some issues.


In both cases, the next step is an update/upgrade of the system.


$sudo apt-get update
$sudo apt-get upgrade


You should have noted that the system, also on first-boot will recognise the new display device without any special setting or display drivers to be installed.


Showing full HD videos on the screen

If you plan to use the screen to show full HD videos (1080x1920 pix) the better performances can be obtained reserving 128 Mb of shared memory to the video card. The amount of shared memory (64 Mb by default) can be changed with the raspi-config command and selecting the menu options shown below.

Screen Shot 2015-08-29 at 16.34.05.png

Select Advanced Options from the main menu.

Screen Shot 2015-08-29 at 16.34.19.png

Select Memory Split from the next screen.

Screen Shot 2015-08-29 at 16.34.32.png

Then, write 128 instead of 64 (the default settings). Confirm and exit, reboot.


On-Screen keyboard

Installing the on-screen keyboard is not the solution to develop software or write long text documents on the Raspberry PI, but it is a must-to-have to make complete the user interaction options. Installing the keyboard is a very simple operation that can be done with a single command from the terminal:


sudo apt-get install matchbox-keyboard


just as it is explained in the product document page on Element14. The documentation says that the keyboard (after installation and reboot) is accessible on-screen from the Menu->Accessories->Keyboard. Doing several installations I have verified that the keyboard is not always listed as a new menu option; one of the reasons depends on the previous presence of a physical keyboard connected to the Raspberry or not. To be sure that the on-screen keyboard is added to the desktop menu after installation the better choice is to manage the Raspberry PI from remote via SSH.


The on-screen keyboard can be shown by your applications or bash scripts with the command




Enabling the touch-screen

Depending on the current status of the linux settings, maybe you don't see the mouse pointer on the screen and the touch screen is unresponsive; the touch screen uses SPI to communicate with the Raspberry PI so it should be enabled, while by default the SPI kernel modules are not loaded.


From the terminal launch the command


sudo raspi-config


then from the character graphic menu follow the steps shown below.


Select Advanced Options from the main menu.


Select the SPI menu option.


Confirm to enable the SPI module and the next screen to load the SPI kernel modules on boot by default. Then, exit and reboot the system.



Now your system is ready to use the full features of the 7 inches LCD display and touch screen.


This post and few other will appear as annex to the Essential Raspberry Pi Peripherals #2. The reason is that when it was planned this series of tutorials the 7" touch-LCD created for the PI was not yet on the market. When the first unit has been received, I started immediately to study the hardware and software; in these #2 annexes we explore some mods and installation that can be helpful for the users to get the best from this incredible accessory inside their projects.


Taking advices and suggestions here and there and seeing some issues that may occur with the 7" touch screen display for the Raspberry PI I have done a prototype of a frame to secure the display when mounted with the control board and the Raspberry PI. My actual usage is for an Info-Point based on the Raspberry PI 2 Mod B.


Note that this blog post will show the prototype building of a full working frame for the display while the "commercial" version will be done with white plastic laser-cut based on the same design. The second part will show the building of the back side enclosure to cover the electronic parts. Until now I have not yet found a protective frame of the display also for the front side including the back parts.

Where to find it

You can find the product at Don't forget to apply the Element14 discount code W0E49MYQ (10% off) reserved to the community users!

How the product appears

IMG_20150930_153223.jpg IMG_20150930_153150.jpg IMG_20150930_151106.jpg

The full description by images can be found on the following Google Album.


Creating the frames

Measuring the display on both sides I have created three different frames: one front-frame and two back frames.


Front frame


Front view of the front-frame; the two extra-area corresponding to the top and bottom sides are used to keep the front and back frames together. This model is so shaped because these are also the supports that keep the display inside the info-pointsupport. A further version with a full thick border will be producer with the same characteristics.


IMG_20150924_192620.jpg IMG_20150924_192635.jpg

Back of the front-frame. The two elements that are part of the structure will also help to keep correctly positioned the touch surface over the LCD surface.


Back frames

There are two frames on the back side of the screen. The first is locked with four allen screws with the front-frame while the second frame protect the remaining part and offers the base for the back cover of the electronic parts (cables, dipslay control board and Raspberry PI). The opacity in the frames of the images below depends on the prototype manual refining. In this prototype I have used a 2.5 mm thick acrylic but the right final material should be opaque, white 3 mm thick.



First back-frame, the nearest to the screen surface.



Second back-frame.



After the pieces are done, the assembly phase is very easy:



1) Put the front-frame on a flat surface and the screen device on it (the Raspberry PI should not yet be fixed with screws on the display controller board) remember to remove the protective label from the front side of the screen.


2) Place the first back-frame on the screen and insert the four allen screws. Then close firmly the four nuts.


3) place the second back-frame and fix it to the aluminium display four holes with screws. Last, fix with the four screws the Raspberry PI over the display control board.

In the image above the top frame is locked with two black pieces of plastic, that can be replaced with a 3D printed cover to protect all the electronic parts.


Ready to use

The following image shows the finished frame.


The first peripheral we'll take a look at is the HDMI monitor, connected to the Raspberry Pi. As connecting an HDMI monitor to the board is extremely simple it's surprisingly difficult to find information on the Internet about how to solve issues and setup the monitor visualisation that best reflects our needs, so this is actually a great starting place for us.


What Your Need for HDMI on Raspberry Pi

As the Raspberry Pi includes a standard, full-size HDMI connector (as opposed to the smaller, micro-HDMI connectors that are starting to appear on similar devices) the only thing you need is a cable like the one shown below.


Ok, so there's nothing easier than connecting the monitor to the Raspberry PI, yes? Well, almost.


Standard Screen Configuration on Raspberry Pi

There's no standard, default configuration that relates to a Raspberry Pi's screen, and this can confuse new users. As a matter of fact, there are two important factors that influence the screen characteristics.


The first is the display memory. In the Raspberry Pi (all models) the video memory is a part of the system memory (the RAM) that's shared to manage the graphical display. This means that any memory space we reserve for the display means the less system RAM we have (and vice-versa). This is a parameter to take in account when obtaining the best results we need from the user interface; keeping sufficient memory to run the system and the applications.


Note: As almost all the same things run well on the Raspberry Pi 2 and the previous models with only the half of the memory available (the Pi 2 has 1GB of RAM against the 512MB of the other models) on the Pi 2 we are free to be more tolerant when reserving video memory.


My suggestion for a better optimisation is to start reserving an initial amount of 64MB for the GPU memory (the Graphic Processing Unit) and eventually increasing this value if we need higher resolution images. The tests done in several working conditions show better graphic results without compromising the processor speed and capabilities suggests that it's possible to share up to 128MB of RAM for the GPU on a Raspberry PI 2 (1/4 of the entire RAM in the previous models!).


The easiest way to configure the GPU memory is through th raspi-config utility. The images below shows the menu sequence to set the desired GPU memory in the system.


Note: It is possible to set any amount of memory but it is the worth testing the suggestions of the script screen, selecting multiples of 16MB of RAM for the better management of the GPU.


From a terminal, launch the command:

sudo raspi-config


From the main menu select Advanced Options.

Screen Shot 2015-08-29 at 16.34.05.png

Then select Memory Split.

Screen Shot 2015-08-29 at 16.34.19.png

Finally, select the desired amount of memory and confirm with the <Ok> button.

Screen Shot 2015-08-29 at 16.34.32.png


HDMI Audio on Raspberry Pi

The Raspberry Pi includes a good quality stereo audio Jack (output only). Due to several potential issues, most depending on the other peripherals connected to the board, it's not unusual that the audio quality decreases at times, producing a worse sound than expected.

However, from the Advanced Options menu it's possible to configure the audio output, forcing the sound sent to via the HDMI output instead of the 3.5mm Jack.

Screen Shot 2015-08-29 at 16.52.54.png

Also in the case where the display is not needed (which occurs in lot of portable projects) or, for example, we are using the PiFace CADPiFace CAD or the 2.4" Raspberry Pi Touch Panel2.4" Raspberry Pi Touch Panel, we can still take advantage of the quality of the HDMI audio using a specific HDMI audio cable, as shown in the example below.



Fine-tuning the Screen Resolution

We have at least two reasons to fine-tune the screen resolution in the Raspberry Pi settings; the first is that there are HDMI screens with different aspect-ratios, and the second is that we need to change the screen resolution depending on the kind of use, the display size etc.


Those who are used to working with the PC know that these parameters are set up and/or detected when the system starts, and in most cases part of the settings are done by changing some BIOS parameters. Other settings - inside a predefined range - can be changed further with proper screen configuration programs like those in Ubuntu desktop and Windows.


As the Raspberry Pi does not have a conventional BIOS, most of the configuration parameters, including the screen settings, are loaded by the GPU before the kernel starts from a simple text file named config.txt stored in the system folder /boot


Note: the raspi-config utility script we have used above to set the audio channel or the GPU's dedicated RAM make automatic changes to this configuration file, but we can also edit the file directly.


The /boot/config.txt file doesn't just contain the graphic display and screen settings, but a lot of other useful information to tailor the behaviour of our system when it starts; in particular for the screen, we can set the resolution, size, aspect ratio, and scan frequency.


Take a look at the following group of settings from the config.txt file (some settings are generated automatically by the NOOBS while installing the operating system):


# NOOBS Auto-generated Settings:


The format of the file is really simple to read and with a minimum of experience, and also to change without damaging the Raspberry Pi's performance. The character '#' is used for a comment line while every parameter is set in the format; <parameter>=<value>


Yes, just as in the unbelievable Windows .ini files and some other settings in the Linux environment. So, the only thing we should know is what is the exact meaning of these parameters to set the values in a consistent way. Some parameters are numeric (with a range of accepted values) and some parameters are boolean (can assume only the value yes or no).


Before Changing the config.txt Settings

First of all, temporarily disable the automatic graphic desktop when the system starts with the raspi-config configuration script as shown in the following images:

Screen Shot 2015-08-29 at 19.41.52.png

Screen Shot 2015-08-29 at 19.42.17.png

After setting the text console at start up, the system needs to reboot.


This operation is for preserving the automatic desktop start up if we see that any settings have gone wrong and the display is unreadable. In this configuration after the system boots we only see the Login prompt; after logging in to launch the graphic desktop we should launch the command startx


After every change to the display settings, we reboot and if, after launching the startx command the desktop is unreadable, we can simply roll back the settings to the last correct value.


Display Setup Parameters

To correctly manage the display settings we should know the exact aspect ratio and scan frequency of the monitor we will use. The following settings shows an example of the standard PAL settings for Europe on a 1024x768 resolution monitor.


# Set sdtv mode to PAL (as used in Europe)
# Force the monitor to HDMI mode so that sound will be sent over HDMI cable
# Set monitor mode to DMT
# Set monitor resolution to 1024x768 XGA 60 Hz (HDMI_DMT_XGA_60)
# Make display smaller to stop text spilling off the screen


A full, comprehensive and detailed look at all the parameters we can set for the best screen performance is described in the attached document RpiConfig, from


An Overview on the Next Posts

What you will see soon in this series:


#3 Kivy: an open source solution for the User Interaction

How to install and use Kivy, a powerful python framework on the Raspberry PI for the best User Interaction on small touch screen devices..


#4 An introductory approach to wired and wireless networking

There are more options than simply plugging the LAN cable in the Ethernet port of the Raspberry PI. In this post we'll see how the Raspberry Pi can be a flexible networking device, acting as bridge, access point, wireless device and more.


#5 The Raspberry Pi camera beyond the webcam limits

Thanks to the power of Python and the specific characteristics of the Pi Camera it's possible to specialise the Raspberry Pi as a video/photo station: shooting, filming, image processing for a lot of possible applications; from photography to security, from stop-motion to the time-lapse filming.


#6 Lirc and IR controller: extending the limits of keyboard and mouse

With a very simple hardware approach we introduce the first non-conventional peripheral connection. Thanks to the Linux lirc library we can use a simplified HID (Human Interface Device) - a TV infrared control - to manage programs, device behaviour, and more.


#7 Enhancing our Pi projects with the Pi touchscreen

We will see how we can setup and integrate in our projects the Raspberry Pi 2.4" touch screen device.


#8 Enhancing our Pi projects with the PiFaceCAD LCD display

When a simple message is sufficient to control the Raspberry Pi behaviour but some control buttons would be useful, the PiFaceCAD (Control and Display) is the ideal device, which can be stacked on our Raspberry Pi for mobile, battery-powered applications.


#8 A multi-sensor system with the Raspberry PI Sense HAT

Coming soon ...