element14 Community
element14 Community
    Register Log In
  • Site
  • Search
  • Log In Register
  • Community Hub
    Community Hub
    • What's New on element14
    • Feedback and Support
    • Benefits of Membership
    • Personal Blogs
    • Members Area
    • Achievement Levels
  • Learn
    Learn
    • Ask an Expert
    • eBooks
    • element14 presents
    • Learning Center
    • Tech Spotlight
    • STEM Academy
    • Webinars, Training and Events
    • Learning Groups
  • Technologies
    Technologies
    • 3D Printing
    • FPGA
    • Industrial Automation
    • Internet of Things
    • Power & Energy
    • Sensors
    • Technology Groups
  • Challenges & Projects
    Challenges & Projects
    • Design Challenges
    • element14 presents Projects
    • Project14
    • Arduino Projects
    • Raspberry Pi Projects
    • Project Groups
  • Products & Partners
    Products & Partners
    • Arduino
    • Avnet & Tria Boards Community
    • Dev Tools
    • Manufacturers
    • Multicomp Pro
    • Product Groups
    • Raspberry Pi
    • RoadTests & Reviews
  • About Us
    About the element14 Community
  • Store
    Store
    • Visit Your Store
    • Choose another store...
      • Europe
      •  Austria (German)
      •  Belgium (Dutch, French)
      •  Bulgaria (Bulgarian)
      •  Czech Republic (Czech)
      •  Denmark (Danish)
      •  Estonia (Estonian)
      •  Finland (Finnish)
      •  France (French)
      •  Germany (German)
      •  Hungary (Hungarian)
      •  Ireland
      •  Israel
      •  Italy (Italian)
      •  Latvia (Latvian)
      •  
      •  Lithuania (Lithuanian)
      •  Netherlands (Dutch)
      •  Norway (Norwegian)
      •  Poland (Polish)
      •  Portugal (Portuguese)
      •  Romania (Romanian)
      •  Russia (Russian)
      •  Slovakia (Slovak)
      •  Slovenia (Slovenian)
      •  Spain (Spanish)
      •  Sweden (Swedish)
      •  Switzerland(German, French)
      •  Turkey (Turkish)
      •  United Kingdom
      • Asia Pacific
      •  Australia
      •  China
      •  Hong Kong
      •  India
      •  Japan
      •  Korea (Korean)
      •  Malaysia
      •  New Zealand
      •  Philippines
      •  Singapore
      •  Taiwan
      •  Thailand (Thai)
      •  Vietnam
      • Americas
      •  Brazil (Portuguese)
      •  Canada
      •  Mexico (Spanish)
      •  United States
      Can't find the country/region you're looking for? Visit our export site or find a local distributor.
  • Translate
  • Profile
  • Settings
Raspberry Pi
  • Products & Partners
  • More
Raspberry Pi
Documents Raspberry Pi 7” Touchscreen Display
  • Blog
  • Forum
  • Documents
  • Quiz
  • Events
  • Polls
  • Files
  • Members
  • Mentions
  • Sub-Groups
  • Tags
  • More
  • Cancel
  • New
Join Raspberry Pi to participate - click to join for free!
Actions
  • Share
  • More
  • Cancel
Engagement
  • Author Author: joeman
  • Date Created: 11 Aug 2015 6:55 PM Date Created
  • Last Updated Last Updated: 16 May 2022 10:17 AM
  • Views 116535 views
  • Likes 20 likes
  • Comments 478 comments
Related
Recommended

Raspberry Pi 7” Touchscreen Display

image

Raspberry Pi 7” Touchscreen Display

Buy Here  Display Installation Guide

Install Virtual Keyboard* Other Pi Accessories  image

The 7” Touchscreen Monitor for Raspberry Pi gives users the ability to create all-in-one, integrated projects such as tablets, infotainment systems and embedded projects. The 800 x 480 display connects via an adapter board which handles power and signal conversion. Only two connections to the Pi are required; power from the Pi’s GPIO port and a ribbon cable that connects to the DSI port present on all Raspberry Pi’s.  Touchscreen drivers with support for 10-finger touch and an on-screen keyboard will be integrated into the latest Raspbian OS for full functionality without the need for a physical keyboard or mouse.

*Note: Your NEW Rasp Pi 7.0 needs you to Add a Virtual Keyboard….

imageimage

You don't have permission to edit metadata of this video.
Edit media
x
image
Upload Preview
image

 

 

Raspberry Pi Sense HAT

image

Learn More  image

Technical Specification:

image  7” Touchscreen Display

image  Screen Dimensions: 194mm x 110mm x 20mm (including standoffs)

image  Viewable screen size: 155mm x 86mm

image  Screen Resolution 800 x 480 pixels

image  10 finger capacitive touch

image  Connects to the Raspberry Pi board using a ribbon cable connected to the DSI port

image  Adapter board is used to power the display and convert the parallel signals from the display to the serial (DSI) port on the Raspberry Pi

image  Will require the latest version of Raspbian OS to operate correctly

 

Features and Benefits

image  Turn your Raspberry Pi into a touch screen tablet, infotainment system, or standalone device.

image  Truly Interactive - the latest software drivers will support a virtual ‘on screen’ keyboard, so there is no need to plug in a keyboard and mouse.

image  Make your own ‘Internet of Things’ (IoT) devices including a visual display. Simply connect your Raspberry Pi, develop a Python script to interact with the display, and you’re ready to create your own home automation devices with touch screen capability.

image  A range of educational software and programs available on the Raspberry Pi will be touch enabled, making learning and programming easier on the Raspberry Pi.

Kit Contents

image  7” Touchscreen Display

image  Adapter Board

image  DSI Ribbon cable

image  4 x stand-offs and screws (used to mount the adapter board and Raspberry Pi board to the back of the display

image  4 x jumper wires (used to connect the power from the Adapter Board and the GPIO pins on the Pi so the 2Amp power is shared across both units)

NOTE: THE RASPBERRY PI AND POWER SUPPLY ARE NOT INCLUDED IN THIS KIT AND ARE SOLD SEPARATELY.

Compatible With:

Raspberry Pi 3 Model B

Raspberry Pi 2 Model B

Raspberry Pi Model B+

Raspberry Pi Model A+

The display will technically work with the Model A and Model B boards (connecting it to the DSI port on the Pi board), however the mounting holes on the back of the display will only line up with the newer board design (A+, B+, Pi 2 and Pi 3).

 

How to Install the Matchbox-Keyboard for your Pi

image

1. Connect a physical keyboard to the Raspberry Pi (or SSH into it if that’s your thing.)

2. Connect to the internet via WiFi or Ethernet.

3. Open the terminal.

4. Type sudo apt-get install matchbox-keyboard

5. Let the program download & install (takes 30s-1min depending on your connection.)

6. Exit the terminal & reboot your Pi.

7. The keyboard can be found by clicking the Menu -> Accessories -> Keyboard.

 

Operating System Support

In order to be sure you’re running the latest version of Raspbian, connect your Raspberry Pi to the Internet and then open LX Terminal.  Type ‘sudo apt-get update’ to download the latest version of the OS.  Once that’s complete, type ‘sudo apt-get upgrade’ to apply the download to your Raspberry Pi.  That way you’ll have all of the latest drivers and software needed to support the touch screen display.

Step 1

image

Step 2

image

Step 3

image

Step 4

image

Step 5

image

Step 6

image

Step 7

image

Step 8

image

Step 9

image
  • pi_guide
  • raspberry
  • pi
  • pi_display
  • raspberry_pi
  • matchbox_keyboard
  • display
  • touchscreen
  • 7”
  • guide
  • installation
  • 7_inches
  • Share
  • History
  • More
  • Cancel
  • Sign in to reply

Top Comments

  • shabaz
    shabaz over 9 years ago in reply to idometeor +3
    Jason Does Meteor wrote: As mentioned, I tried that. Actually you didn't, you stated: I have tried everything and I cannot get the display to rotate in Raspbian. I have written many X configuration files…
  • softweyr
    softweyr over 11 years ago in reply to ejohnfel +2
    Yeah, this is not a bad price for a 7" display, plus you get the touchscreen, integrated keyboard, etc. And tomorrow is my birthday!
  • bwelsby
    bwelsby over 11 years ago in reply to phantomski +2
    The reduced screen size is because Overscan settings are enabled. you can either comment out the settings in /boot/config.txt or just run raspi-config and select the advanced options then Overscan , Disable…
  • e14 Contributor
    e14 Contributor over 10 years ago in reply to e14 Contributor

    Hi Scot, The only solution for touch screen I have found and works for me is to use Kivy with Python. Check this out:

    CheersRichard

    mrichardson23/rpi-kivy-screen

     

     

     

     

     

     

     

     

    mrichardson23/rpi-kivy-screenrpi-kivy-screen - Using Raspberry Pi's Official Touch Display with Kivy and GPIO

    View on github.com

    Preview by Yahoo

     

     

     

     

     

          From: scottoo <messages@element14.com>

    To: Richard Kulaga <richardkulaga@rogers.com>

    Sent: Tuesday, January 19, 2016 9:01 AM

    Subject: Re:  - Raspberry Pi 7” Touchscreen Display

        

    #yiv1446460318 * #yiv1446460318 body {font-family:Helvetica, Arial, sans-serif;}#yiv1446460318 #yiv1446460318 h1, #yiv1446460318 h2, #yiv1446460318 h3, #yiv1446460318 h4, #yiv1446460318 h5, #yiv1446460318 h6, #yiv1446460318 p, #yiv1446460318 hr {}#yiv1446460318 .yiv1446460318button td {}

    | 

    The first online community specifically for engineers.       Login

    Topics

    Resources

    Content

    Design Center

     

     

    Raspberry Pi 7” Touchscreen Display

    new comment by Scott Tyack View all comments on this documentThanks Peter and Clem, both good explanations to help me go looking for a solution. I'll take this elsewhere and see if a python/pygame forum can help. I will post any solution I find here as it might help someone who wants to use this excellent touchscreen outside of the Xwindow environment. Scott.

    Reply to this email to respond to Scott Tyack's comment.

     

    |

    Feedback & Support

    Terms of Use

    FAQ

    About element14

     

     

    **************************Disclaimer************************** The contents of this e-mail and any file transmitted with it are confidential and intended solely for the individual or entity to whom they are addressed.  The content may also contain legal, professional or other privileged information. If you received this e-mail in error, please destroy it immediately.  You should not copy or use it for any purpose nor disclose its contents to any other person. The views stated herein do not necessarily represent the view of the Company. Please ensure you have adequate virus protection before you open or detach any documents from this transmission. The Company does not accept any liability for  viruses. Premier Farnell plc

    150 Armley Road

    Leeds

    LS12 2QQ

    Telephone +44 (0) 870 129 8608

    Fax +44 (0) 870 129 8610 Registered in England

    Company Number 876412

    Registered Office: Farnell House, Forge Lane, Leeds LS12 2NE ************************************************************  

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • More
    • Cancel
  • e14 Contributor
    e14 Contributor over 10 years ago

    Thanks Peter and Clem, both good explanations to help me go looking for a solution. I'll take this elsewhere and see if a python/pygame forum can help. I will post any solution I find here as it might help someone who wants to use this excellent touchscreen outside of the Xwindow environment.

     

    Scott.

    • Cancel
    • Vote Up +1 Vote Down
    • Sign in to reply
    • More
    • Cancel
  • clem57
    clem57 over 10 years ago in reply to e14 Contributor

    Python relies on OS under the covers. When Xwindows not started, Python tries to use something else which is not calibrated..

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • More
    • Cancel
  • Robert Peter Oakes
    Robert Peter Oakes over 10 years ago in reply to e14 Contributor

    touch screen presses are not keyclicks, there touch events, the physical keyboard should still work though

    I am not sure of the exact way to respond to touch events outside of the xwindow though, you may have to hook into the touch events, workout the co-ordinates of the ouch event and then figire out if you have something of note there

     

    This is how it works under windows 10IoT right now till MS get a proper touch driver working

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • More
    • Cancel
  • e14 Contributor
    e14 Contributor over 10 years ago in reply to Robert Peter Oakes

    Hi Peter,

     

    Thanks for the links and the videos. Very good watching material. However, under the conditions you use in the 'Test Display' video I also have a fully functional touch screen. The issue for me seems to come about when you are not running within the Xserver (startx) environment and trying to access the key clicks through python/pygame scripts. The code below is my test code hacked together from another project using the screen. I'd be interested to know if it works for anyone else outside of the gui.

     

    #touchTEST.py
    
    # using pygame to test the accuracy of Element14 touchscreen
    
    import pygame
    
    pygame.init()
    
    
    screen = pygame.display.set_mode((800,480))
    
    font24n = pygame.font.SysFont("arial", 24)
    
    screensaverBlackSURF = pygame.Surface((800,480))
    screensaverBlackSURF.fill((100,20,20))
    screensaverBlackSURF.convert()
    screen.blit(screensaverBlackSURF, (0,0))
    pygame.display.flip()
    
    done = False
    #null onjects
    coordRenderRect = ''
    while not done:
    
        for event in pygame.event.get():
        #KEYBOARD
            if event.type == pygame.QUIT:
                done = True
            if event.type == pygame.KEYDOWN and event.key == pygame.K_ESCAPE:    #hit 'esc' to quit
                done = True
        #MOUSECLICKS
            if event.type == pygame.MOUSEBUTTONUP:
                if coordRenderRect != '':
                    blankSurf = pygame.Surface((coordRenderRect.right, coordRenderRect.bottom))
                    blankSurf.fill((100,20,20))
                    screen.blit(blankSurf, (10,10))
                pygame.draw.circle(screen, (0,105,163), event.pos, 3)
    
                coordRender = font24n.render(str(event.pos), True, (255,255,255))
                screen.blit(coordRender, (10,10))
    
                pygame.display.flip()
               
    pygame.quit()

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • More
    • Cancel
  • Robert Peter Oakes
    Robert Peter Oakes over 10 years ago in reply to e14 Contributor

    A boot up with the latest Raspbian (Jessie) 1.5.0 on an SD card is all you need to prove it is software / driver related, this version works out of the box (SD Card) with NO additional action asside from connecting it to the PI

     

    I have 2 videos showing detailed process of creating the Raspbian SD Card image, assembling the Display and attaching to the PI, then testing with the just created SD card.

     

    see here:-

    Create Boot SD Card

    Install Raspbian and test without display

    Assemble Display

    Test Display

     

    if the hardware is working and you follow the instructions then this WILL work

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • More
    • Cancel
  • e14 Contributor
    e14 Contributor over 10 years ago in reply to e14 Contributor

    Hi Pete,

     

    Thanks for the suggestion. I have dismantled everything before but i tried it again anyway. No improvement but I did find one interesting thing out that I have added to my post above. I think it could be a software/driver issue.

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • More
    • Cancel
  • e14 Contributor
    e14 Contributor over 10 years ago in reply to e14 Contributor

    Scott,

     

    I don't know if this is the cause of your issue, but hope this helps you and others:

     

    My touchscreen was behaving erratically, not just off position, but it was scattering the touch events everywhere.  If I had four or five sliders on the screen, when I moved one, others would start to randomly move  :-)   

     

    The cause in my case was an improperly seated ribbon cable between the Pi B+ and 7" Pi Screen.  This happened either during installation, or when inserting and removing the micro SD card over and over (unfortunately, the ribbon cable wraps right around SD card, impeding access, so I tend to bump and slightly pull on the ribbon cable when inserting and removing the card.).

     

    I reseated the ribbon cable on both ends and it solved all my touchscreen issues.

     

    Cheers,

     

    -Pete

    • Cancel
    • Vote Up +2 Vote Down
    • Sign in to reply
    • More
    • Cancel
  • e14 Contributor
    e14 Contributor over 10 years ago

    Inaccurate touch location detection? Calibration possible?

     

    The screen runs fine, detects touches but fails dismally at the location of the touch. I wrote a small python script using pygame to draw a circle at the x,y co-ordinates of the touch. In some cases the detected point was half a screen away. Testing my script with a mouse and the circles are drawn precisely at the point of click. When repeatedly touching at the same location the erroneous location is repeatedly detected (ie. not randomly reporting a location).

     

    Power seems fine with no low power warnings. Mixing up any of the cables would result in nothing working rather than this? Can the screen be calibrated?

     

    Thanks and happy to try anything that is suggested.

     

    Scott.

     

    EDIT: 18th Jan. I tried running my code from within the graphical interface (ie. startX/Xserver). The touches became precise and everything worked perfectly. I went back to running the python/pygame code and the touches continued to be horridly inaccurate. Sounds like we have a driver issue? Is there something I could call from Xserver to gain the touchscreen control?

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • More
    • Cancel
  • e14 Contributor
    e14 Contributor over 10 years ago in reply to e14 Contributor

    I also had to rotate the display, but all I had to do was add one line to the /boot/config.txt :

    lcd_rotate=2

     

    That rotated the display and the touch together.  I also turned off overscan in raspi-config so the touch would line up with the display.

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • More
    • Cancel
<>
element14 Community

element14 is the first online community specifically for engineers. Connect with your peers and get expert answers to your questions.

  • Members
  • Learn
  • Technologies
  • Challenges & Projects
  • Products
  • Store
  • About Us
  • Feedback & Support
  • FAQs
  • Terms of Use
  • Privacy Policy
  • Legal and Copyright Notices
  • Sitemap
  • Cookies

An Avnet Company © 2026 Premier Farnell Limited. All Rights Reserved.

Premier Farnell Ltd, registered in England and Wales (no 00876412), registered office: Farnell House, Forge Lane, Leeds LS12 2NE.

Follow element14

  • X
  • Facebook
  • linkedin
  • YouTube