volumio lcd display factory

LCD display controlled by B4J Library jLCD_I2C which is converted from https://www.b4x.com/android/forum/threads/raspberry-b4j-i2c-hd44780-lcd-driver.61123/ classes (a BIG thanks to the author for developing).

Running Plugin Scripts Example:"node /volumio/app/plugins/system_controller/volumio_command_line_client/commands/setvolume.js 80" to set the volume to 80%.

Open a terminal (using f.e. Putty), create a folder /home/volumio/b4j, download the B4J-Bridge (wget http://www.b4x.com/b4j/files/b4j-bridge.jarhttp://www.b4x.com/b4j/files/b4j-bridge.jar), start sudo java -jar b4j-bridge.jar and connect from the B4J IDE.

One of the most awaited plugins for Volumio is finall here: the touchscreen plugin. With it you can easily show the gorgeous Volumio UI on any display, included the official Raspberry PI Display, available on our Shop. Let’s see how to easily achieve a fantastic touchscreen for your favourite music player in less than 10 minutes. This tutorial will explain how to connect the Raspberry PI display and enable the Volumio UI with the plugin.

Assuming you’ve already downloaded and flashed Volumio to your Raspberry PI (we suggest to use the newest  Raspberry PI 3), the first step is the wiring:First, let’s attach the ribbon cable going from the Raspberry PI Display to the PI itself. On the Raspberry PI Side, make sure the blue part of the ribbon cable is facing outwards. Your final goal should look like this:

Notoriously, feeding your PI with an adequate Power Supply is mandatory to have a reliable system. That’s especially true when we connect a power-hungry device like the Raspberry PI Display. Luckily, there’s a way to understand if your PSU is good enough: just power on your pi and observe the screen, if you see a coloured square on the top-right side of the screen, it means that power to your PI is not enough. Don’t you see it? Then all is good.

That’s the easy one. Just connect to Volumio’s WebUi as you would usually do, and navigate to the Plugins page from the settings menu. In Miscellanea category, you’ll find the Touchscreen plugin. Just click install, nothing more. PLEASE NOTE: The touchscreen plugin is compatible with volumio version from 2.001 onwards

The installation will last about 7 minutes, so wait patiently until you see “Installation Complete”. Now you can enable or disable the Display output to your likings.

I must admit that altough this display is not particularly brilliant when it comes to resolution and colour accuracy, it looks indeed very nice with Volumio’s UI. Also, usability is very good on the Raspberry PI 3 and the UI runs smoothly also with big libraries… So, folks, enjoy!

If you don’t have a Raspberry PI, or you’re simply looking for alternatives to the Official Raspberry PI Display, there are at least two extra options for you:

The Odroid display is not only a viable alternative, it also have several advantages over its PI counterpart:Since it takes power from USB and video signal from HDMI, it can be used virtually with any Computer with an HDMI output, not just the Odroid or the Raspberry PI.

UPDATE: Lot of time since I published the original article. The Odroid 7” does not seem to work properly with Raspberry PI (not tested with the Odroid). So, if you’re looking for a display for the Raspberry PI, get the official one.

The Waveshare 7” display has become rapidly a widely adopted display, thanks to its cheap price. However this particular touchscreen has shown several reliability issues (altough this seems fixed in latest models, thanks to a firmware update), it requires a particular touchscreen driver which is not always included in major distros and its colour reproduction is not the best.

Here we are folks! Hope you found this article helpful, you can share via comment below how you use your Volumio’s touchscreen setup and if there are other display alternatives!

Unfortunately, their “driver” is an SD card image containing a complete installation of Raspbian which has been preconfigured to use their display. Which is fine if you’re setting up a brand new system that doesn’t need to be a specific distro, but if you’re trying to add the display to an existing Raspberry Pi, already configured the way you want it, with software installed and data present, or if you want to use a specific distro such as Octopi, then it’s not terribly helpful.

Hello..I tired to interface this lcd “https://www.crazypi.com/raspberry-pi-products/Raspberry-Pi-Accessories/32-TOUCH-DISPLAY-RASPBERRY-PI” to my Raspberry pi model B+.I got a DVD containing image for LCD in the package.I burned it to the SD card and plugged in the display.But my lcd is completly blank.But green inidcation led (ACT LED) in board is blinking.Why my LCD is Blank ?

My Touchscreen is now working fine.The problem was for the ribbon cable on the back side of LCD.It was not connected properly.I just tighted the cable and it worked fine.Hope it will be useful tip.

Just got my Pi2 running Wheezy, working with the Eleduino 3.5 LCD without running the OEMs image… kinda. I didn’t want to rebuild the application environment again, so was avoiding flashing the SD.

thank you for your great tutorial, it got me on the right way. unfortunataly i only see some boot messages on the lcd and then it turns black. maybe you could give me a hint on how to get it working entirely.

i have a watterott display (https://github.com/watterott/RPi-Display) and changed the device-name to “rpi-display”. i use a rsapberrypi 2 and hae the latest raspian image installed.

I too have a raspberry pi 2, and a waveshare spotpear 3.2 RPi lcd (v3) and I just can’t get it to work! I suspect I have a faulty LCD, but thought I’ll try this forum for help before I sent it back.

Soon as the pi is powered, the LCD lights up all white, with a few vertical pixels coloured at one of the edges, and nothing else. I don’t think that should happen – not at least before the BOIS has started up.

It seems all appears to be working – just the LCD is still all white with a single line of coloured pixels on edge) and nothing else. Is there a way to output, like jeff G script, of touch points?

I had the same one, I finally found a driver for it here: http://www.waveshare.net/wiki/3.2inch_RPi_LCD_(B) you will need to translate the page, but unpack the driver then run sudo ./LCD-show/LCD32-show. It should reboot and all will be good with the screen :)

My system: Raspberry Pi 2 Model B with Raspian Wheezy from Febuary 2015. LCD display of Sainsmart 3.2 http://www.conrad.de/ce/de/product/1283498/Raspberry-Pi-Display-Modul-Touch-Display-81-cm-32/?ref=home&rt=home&rb=1

The LCD display shows the raspberry correctly. However, the touch screen input does not work. The mouse pointer can I move correctly with your finger, but I can not select things (function of the left mouse button).

Do not follow this article when you don’t know what kind of LCD module. In my case, I follow all of this and my raspberry pi cannot boot anymore. I will try to recover, but I think I should format my SD card and reinstall OS.

Expecting this would builtin driver module within kernel and help with avoiding mistakenly overwriting anything. But with this is cause LCD screen to go blank white and no boot activity. Also noticed on HDMI it get stuck on Initial rainbow screen and stuck on that.

Does anyone tried splash boot screen with waveshare v4 LCD and Rpi2? I tried to follow some example from https://github.com/notro/fbtft/wiki/Bootsplash but no success.

Great tutorial thanks; got an X session working great 1st time. Has anybody managed to get Kodi/XMBC working on the LCD either Kodi standalone, Raspbmc or Xbian?

I have exactly the same problem. I also installed a new version of Raspbian, and the LCD part works fine (except all the windows are way too large), but the touch part doesn’t work at all… I’m using Waveshare Spotpear 3.2″ V4.

I remember that I plugged in the screen wrongly one time, before configuring any of the GPIO pins. Can this have damaged the screen? Still it’s weird that the display part works well and the touch part not at all.

I am trying to use the sainsmart 2.8″ lcd sold through microcenter, using the sainsmart32_spi … seems to have the same pinouts, should I be able to get this to work? I am stuck at the white out screen on the lcd, doesn’t seem to recognize the module either.

Unfortunately I’ve tried that ( a few times actually) but the file still doesn’t exist. Thanks very much for the assistance anyway. I must be doing something wrong. My Raspian came from a Noobs installation, I’m wondering if I should try installing the OS from somewhere else. My LCD screen didn’t come with a CD or any docs so I’m completely in the dark here.

Well figured out that step 1 was causing my problems. I’m guessing it is shutting off my hdmi feed and trying to switch it over to the SPI, am I guessing right? If so, not sure how I’m suppose to complete the rest of the steps if my hdmi output gets turned off before the LCD is actually set up to work…that sounds kind of smartass-like, which is not my intention, just looking for some clarification on what is going on in that first step as I am fairly new to this stuff. Thanks.

Anyway, I was able to do the rest of the steps with no problem. LCD didn’t work, but I am using a Waveshare 3.5, which doesn’t look to be supported yet. Mostly I am trying to play around and see if I can get it working somehow. Anyone found a way to do this yet?

Here is a link to an updated image from waveshare. Upon install it got the display up and running, but I still do not have touch functionality. I’ve been playing around with it, but it has been to no avail…hopefully someone better at this stuff from me can get the touch working.

I am having an issue with getting the GUI back. Every time I use startx my pi just sits there for about two minutes saying “No protocol specified”, and then it just gives up. I went through this tutorial about four times now and am not certain why it is doing this. I have the exact same LCD as is in the tutotial (WaveShare 3.2b). any help would be great.

Thanks for the tutorial. It works, but I get the boot/command line stuff on the HDMI monitor and the LCD only comes on when I do startx. Is there a way to get everything to appear on the LCD screen?

Now the OS freezes at the emulation station loading screen, and if I connect my lcd it gives me a lot of error messages which I can only see on the 3.2 inch screen.

This was an excellent tutorial. I have gotten an output to the screen, but no touchscreen usage . I have the Waveshare SpotPear 3.2 Inch LCD V4 screen, but using Raspberry PI 2 with wheezy. Any ideas?

I actually used the driver from here http://www.waveshare.com/wiki/3.2inch_RPi_LCD_(B) , from a new wheezy build, did nothing except enable SPI in config, install driver, and change mmcblk0p2 to mmcblk0p6 in cmdline.txt and it all worked, no drama.

i have raspberry pi 2 with 3.2 inch rpi lcd v4 waveshare spotpear.i have done as per your instructions.the display is working but touch screen not working.error shows waveshare32b module not found as well as touch screen module not found messages.

Unfortunately I have lost the Touch facility on my Waveshare 3.5″ LCD Touchscreen? Can you offer any reasons as to why? I copied the Raspbian image to my Raspberry Pi from the Waveshare website first of all. The Touchscreen displays but is not reactive with any touch

I have purchased a raspberry pi B+ total kit and waveshare 3.2 TFT display online. In the package i have been given a pre-loaded NOOBS installed SD card. I did not even start anything yet. What should i do what r the things needed and how to connect the display i really want to know. I need help as i don’t know anything. Does the above solution help or will u suggest something………………..

Hi great article thanks. I am trying to get a waveshare 7 inch LCD with capacitive touch running it works with the suppled image but if you upgrade it breaks the capacitive touch. I have a sense-hat and GPS which require the latest kernel and RASPIAN image and the install program for the screen replaces the /lib/modules directory and the kernel with older ones. I need to be able to install the touch drivers into a new clean OS can anyone give me some pointers? Thanks

So I have the original image that came with my screen and it works fine with the LCD but my problem is that I want to use my LCD screen with other distros (at this time I am trying to use it with Kali Linux with TFT support by default https://www.offensive-security.com/kali-linux-vmware-arm-image-download/) What do I have to do to transfer the needed files from the original image that WORKS with the screen and use them with another image?

I originally bought this bundle http://www.amazon.com/gp/product/B013E0IJUK?psc=1&redirect=true&ref_=oh_aui_detailpage_o02_s00 with an RPi LCD V3 and no extra documentation on the specifics on the chipset. I tried with the bftft drivers but since I have no idea what to call this screen I just suppose it isn’t supported.

I am using the same LCD and followed your tutorial. Have your tested the guide lately? Are you certain that it works? I see the boot messages on console but I get white screen as GUI starts.

I have tried to set up waveshare 32b on my Pi B using the latest Raspian download. I learned a lot in the process using Windows Putty, Nano etc. I have repeated the setup process several times from scratch and included the corrections for possible overwriting. My Waveshare SpotPear 3.2 inch RPi LCD V4 just shows a white screen. Any suggestions?

Hi, I am using raspberry pi 2 with raspbian jessie installed. I the waveshare spotpear 3.2 v4. The above instructions are not working. and after completing the steps there was no display from hdmi or lcd. One things to notify is.: the etc/modules files only had i2c-dev and not snd-bcm2835.

I am trying to get this to work with Retro Pie 3.3.1 and the Waveshare3.2″ v4 but I only get the terminal on the lcd and emulation station starts on hdmi. to get it working with retro pie i just replaced startx with emulationstation. how do i get this to work?

Sir, Your post has very useful to me. i am using Tinylcd. but i cant get display. i am performing all the steps in your post. i cant get touch controller information from the product website and also i am using RASPberryPi B+ model. could u please give me best solution to my work. Than you.

i installed android OS in raspberry pi 2. can i use same LCD touch screen set up for android installed raspberry pi 2 which you are used for raspbian.

Is it normal the white back light during the whole process of initializing (I suspect that during the transportation trere is a deffect)? The problem is that I missed the step #1 and I performed it at the end. Unfortunately I don’t have any monitor available right now – neither “normal”, neither LCD :))))). Is it possible turning back the system or the only option is reinstallation of the Raspbian?

I’m trying to use an original Raspberry Pi model B with a cheap 3.5 inch 320×480 LCD which allegedly was manufactured to work with the Pi and has the correct fittings to fit over the GPIO pins. The operating system is the latest, downloaded yesterday and installed with NOOBS. I can’t get past step 2 of this guidance. When I reboot after using raspi-config I can see text generated as the Pi boots, then the HDMI fed screen goes blank apart from a flashing cursor in the top left hand corner. The LCD just remains white with nothing else on it. I have missed out step 1 and rebooted after step 2 and the screen functions as I would expect. Does anyone have any ideas please?

Thanks for the great tutorial. I do have a question. Once you install the drivers for the lcd are you effectively disabiling the hdmi port or is it still available to use and will the pi function with both displays. I have a pi 3

once you install the drivers it replaces the kernel by disabling hdmi output and enables it for LCD. i don’t think we have a solution to get em both working at the same time. ( you are encouraged to search for it )

i am sorry, but i am a naive , and i have this question, can we upload any file into it for the display? like have a software in which if i tap it gives back a feedback to the code?

I’d like to find the driver software for my 7″ LCD with touch (official Pi unit) so that I can use it in buildroot. I wanted to make sure this kernel is the one before I started digging further.

I started through your tutorial and completed step 3 and rebooted. After the Raspberry screen and some of the boot text on my HDMI monitor, I now have a black HDMI monitor and a white screen on my LCD. Does this mean that the bootloader was overwritten or something else is wrong? How am I supposed to enter in the proposed fixes to the bootloader, when I can’t get the RPi to boot? Do I have to interrupt the boot process at some point to reinstall the bootloader or what?

Its a script. Download and instead of running sudo ./LCD4-show run cat ./LCD4-show to simply display what it does without actually running it. The commands are fairly simple modifying a few files. I actually saved the LCD-show.tar.gz on my own server for faster future download but also for backup as it saved me tons of hours (if that’s a measuring unit for time :) )

I used this link though (smaller file ~ 50 KB, fast download) http://www.waveshare.com/w/upload/4/4b/LCD-show-161112.tar.gz and replaced LCD4-show with LCD32-show in the last line.

i bought a 3.5 inch tft lcd screen from banggood. and i have installed raspian jessie, the latest version, in my sd card. but when i power on my Pi, only a white backlit screen comes. there are no images or graphics whatsoever.

PLEASE DELETE this article. You have great power with this article showing up for so many people in their search results, and you display ZERO responsibility. This is terrible!

Will your system work with my SainSmart 2.8″ 2.8 inch TFT LCD 240×320 Arduino DUE MEGA2560 R3 Raspberry Pi ? I would like to know before not be able to back out. Thanks, Lee

I ‘m actually using a LCD Waveshare3.2” , I followed your steps to setup the lcd touchscreen for my rpi and it work but I have a problem with the resolution because if I open a repertory I do not see the whole contents on the screen .

it worked. but the resolution is for bigger screens. i got the menubar small, but the rest appears too big , and out of screen. the wastebasket icon is 1/6 of my 3.2″ screen. wich HAS the resolution capability too display the whole desktop. But i’m a PI newby and dunno how to adjust the screen resolution on this display. anybody?

I did a 5inch LCD for my raspberry pi. I dont use the touchscreen so i didnt have to install any drivers. It works out of the box but doesnt cover the whole screen unless you open the terminal and do:

In the case of the WaveShare driver, their setup script from their “LCD_show” repository will copy a device-tree overlay to /boot/overlays/ that provides most of the module config etc via boot-time device-tree patch.

6) Power on the Raspberry Pi and wait for a few seconds until the LCD displays normally. And the touch function can also work after the system starts.

Computer monitors are great for office work, gaming, and browsing, but these displays can be large and power consuming. One display found in both the commercial and hobby world is the HD44780 16 x 2 display, which can display two lines of alphanumeric characters. In this tutorial, we will learn how to connect one to a Raspberry Pi and code it using the Python programming language!

The HD44780 has a number of registers and commands that are used to control the display, but getting the display to work can be somewhat tricky, especially for inexperienced users. This is why most coders will turn to libraries. They include prewritten code that has been proven to work. In this tutorial, we will be relying on two libraries to control the LCD: RPLCD and RPi.GPIO. Before we can continue, we need to install the RPLCD library by using the following command in a terminal window:

First, we need to import the RPi.GPIO library as GPIO. This will allow us to use the GPIO library and refer to it as “GPIO”, which is easier than RPi.GPIO. The next library that we need to include is the RPLCD library, which allows us to use the LCD. Therefore, the first two lines of code in our Python program will be:

CharLCD is a Python library that lets users access Adafruit character LCDs from a Raspberry Pi. Next, we need to tell the RPLCD library what pins we have connected the LCD to. In the Scheme-It schematic above, we connected the LCD pins to the following GPIO (using the BOARD numbering scheme). The Pi has two numbering schemes; BOARD and BCM. The BOARD numbering scheme refers to the I/O header whereas the BCM scheme refers to the GPIO numbers from the Broadcom IC. It is often easier to use BOARD scheme as you can count the pins to determine which one you need to use whereas the BCM scheme requires you to first choose a GPIO and then determine its pin number (BOARD).

Now that we have configured the LCD, it’s time to do a few tasks with it! The first function that we should learn to use is “write_string()”, which is used to write text to the LCD. Try the following command:

Writing predefined strings is not entirely helpful, and displaying variables can be very beneficial. Luckily for us, Python allows typecasting, where one variable can be converted into another variable. The example below shows how we can display a counter, which displays an integer on the LCD, along with a simple “Count” message.

Next, we’ll learn how to clear the display. Displays like those based around the HD44780 are static, and they remember what you tell them to display. However, this also means that when you want to write new data, you may need to clear the entire display. Therefore, you can use this clear function to clear the display:

Sometimes printing text on the top left of the display may not be desirable. In this case, you will need to change the cursor’s position. To do this, we can set the cursor_pos variable to a specific value. The example below sets the cursor position to row 2 (x) and column 0 (y).

At the end of your program, you should include the function “lcd.close()”, as this will free up the GPIO for other programs that may need to use them.

ER-EPM027-1B is e-paper/e-ink display module that is 2.7 inch e-paper display panel attached with a breakout board, 264x176 resolution with white/black color,EK79652AC controller,running both 3.3V and 5V power supply,super wide viewing angle,sunlight readable and easily controlled by MCU such as PIC, AVR, ARDUINO,ARM and Raspberry PI. One fantastic aspect of the ePaper display is the fact they don"t need any power to keep the image on the screen. Just like a Kindle, you can read whatever is on your screen in daylight without any reflection.It"s optional for 3-wire or 4-wire serial interface,pin header or FFC with ZIF connector connection.

Since building a couple of Raspberry Pi-based music streamers, I’ve been on the hunt for the perfect music playback software package. I started out with the comprehensive Volumio program, but I found it struggled a bit with my large local digital music collection, and it appears to be transitioning to a subscription-based service for advanced features.

At first glance, its feature set looks similar to Volumio, but moOde is entirely free. That’s a win in my books, so I decided to give it a whirl. What follows are my experiences and observations, what I like and what I do not.

If you are currently a Volumio user or are new to the Raspberry Pi music player scene, you owe it to yourself to try moOde Audio out and see if it is a fit for you. moOde Audio development is far from static and is continually evolving and adding feature support. Version 7 is a polished and mature offering, and I look forward to checking out v8 whenever it appears.

A primary difference between Volumio and moOde is that Volumio uses plugins that can be installed, removed, and individually configured, while moOde incorporates all its options into the configuration menu.

The user interface is simple and relatively attractive. It’s broken into three main sections with the playlist on the left, volume and track completion represented as two circles in the middle, and album art and information on the right. I find the Volumio interface a bit prettier overall, but it is busier compared to the cleaner moOde design.

Once I hammered out how to get everything working, using moOde has proven to be relatively trouble-free. The only real bug that seems to crop up frequently is that the Pi display changes over to the default Chrome browser “Aw, Snap! Something went wrong while displaying this web page” error after a while. Clicking the Reload button refreshes the screen and brings back the moOde user interface, so it’s just moderately annoying rather than a deal-breaker.

I’m not entirely enamored with the plain screens displayed when using RoonBridge or Spotify Connect, which just show the active connection name and a “disconnect” button mid-screen. I prefer the album art and simple controls displayed by Ropieee when playing tracks from Roon – after all, that’s the point of having a screen on the Pi in the first place. So only seeing “RoonBridge Active” is a bit of a disappointment.

Now that I’ve spent time with moOde Audio, Volumio, and Ropieee, I can appreciate that they all offer different things to users with a variety of needs. moOde and Volumio are very similar programs, and although Volumio has a slightly prettier interface and more intuitive plugin support, its decision to paywall some features behind a subscription fee means that I have to give the nod to moOde.

Ropieee is a different beast. It’s far more streamlined, with a focus on Roon playback and little else. However, it offers onscreen controls, cover art support, Spotify Connect, and a useful clock display when not active. This means that it fits my particular set of requirements almost perfectly. As always, YMMV.

If you are currently a Volumio user or are new to the Raspberry Pi music player scene, you owe it to yourself to try moOde Audio out and see if it is a fit for you.

I had RPi working with Volumio in the Raspberry 7" display and had it running for two weeks. It then would boot intermittently, and then it died. I took the RPi out of it"s display case, flashed several new good quality microSD cards with Volumio and Moode, but neither would boot. I"d get a solid red light (power), and 8 green light flashes and then nothing. With a little research it appears that 8 green light flashes indicate bad SDRAM. So it seems my RPi is faulty. I"ve tried to communicate with the EBay seller that the RPi he sold me isn"t working, but I"ve heard no reply. Thus, I"m assuming I just have a bad RPi and nothing can be done about it. I"m contemplating buying another RPi, but at $100 I"m hesitating.