Support for: 7″ Touchscreen Monitor for Raspberry Pi

hondagx35

Hi Morias,

Hi Perjan, I am finding that after I run Rune for a while I can't get the screen to come back to life.

This is because

xset dpms 0 0 600

switches off the display after 10min.

xset dpms <Standby> <Suspend> <Off>

Try standby and suspend.

2. DPMS

DPMS (Display Power Management Signaling) is a standard to reduce power consumption in monitors. Typically, both the monitor and the video card must support the DPMS standard in order to receive any benefit from it. DPMS specifies four modes of operation (in order of increasing power savings): "Normal", "Standby", "Suspend" and "Off". Two signal lines, "Horizontal Sync" and "Vertical Sync" provide a method for signaling these four different states to a DPMS monitor.

A good technical resource on DPMS is available at http://webpages.charter.net/dperr/dpms.htm.

2.1. Normal
Normal means just that -- the monitor is fully powered and on. LCD laptop panels and LCD flat screens use considerably less power than traditional CRT monitors.

2.2. Standby
Standby is used to describe a very minor power savings level. This setting usually involves blanking the screen by turning off the electron (RGB) gun. However, the power supply is left on and the tube filaments energized. When you need to use the monitor again, the monitor will come back on very quickly. This option requires DPMS monitor and video card support along with enabling DPMS in XFree86. Standby is sometimes referred to as hsync suspend mode since the horizontal sync signal is turned off to signal this power management state to a DPMS monitor.

2.3. Suspend
Suspend is used to describe a very strong low power state. This setting usually involves the same power conservation as Standby however in addition the power supply to the monitor is turned off. This option requires DPMS monitor and video card support along with enabling DPMS in XFree86. Suspend is sometimes referred to as vsync suspend mode since the vertical sync signal is turned off to signal this power management state to a DPMS monitor.

2.4. Off
Off usually means just that -- the computer monitor is turned off. Usually, a small auxiliary circuit stays on to monitor the signals from the computer to turn the monitor back on when data needs to be displayed to the screen. Obviously, this keeps power consumption to a bare minimum (if not zero). While the power saving is substantial, to reactivate the monitor may take several seconds. This option requires DPMS monitor and video card support along with enabling DPMS in XFree86. Both the horizontal and vertical sync signals are turned off to signal this power management state to a DPMS monitor.

Frank

morias

hondagx35 wroteTry standby and suspend.

I think my problem was I left the "&" off the end.

I spoke too soon. The screen is still not turning on if I leave it too long. I am trying some other things.

guardian

I have the same issue. The display comes back after shorter times of standby/suspend. If standby/suspend time is longer than approx. 2 hours, it stays black. But I can still access via ssh and webUI. I tried with dpms standby and suspend. But it makes no difference.
I think it is not the display itself, because the dpms function seems to work and I see not why its standby mode should be changed after a long time. Is it possible that the touch controller or something else goes into standby? So it doesn´t recognize the touch to wakeup. Is there a command to force the display to turn on manually?

hondagx35

Hi guardian,

Is there a command to force the display to turn on manually?

[root@runeaudio ~]# export DISPLAY=:0
[root@runeaudio ~]# xset dpms force off
[root@runeaudio ~]# xset dpms force on

Frank

morias

I have been trying various settings.

xset -display :0 q shows the various timings for the screen to turn sleep, suspend and turn off and whether the screen is currently on or off.

xset -display :0 dpms force off will turn it off.
xset -display :0 dpms force on will turn it on.

Initially if the screen turns off I can turn it on by touching the screen or running the force on command. The query command will correctly reports if the screen is on or off.

However, if I leave the raspberry pi running for some hours, the screen will have turned off and I cannot get it to come back on by either touching the screen or running the force on command.

Even after running the force on command the screen remains off but the query command will report the screen is on. I have had to go to work so will experiment again when I am at home.

guardian

Hi Frank,

CODE: SELECT ALL
[root@runeaudio ~]# export DISPLAY=:0
[root@runeaudio ~]# xset dpms force off
[root@runeaudio ~]# xset dpms force on

I will try that, thank you! But I think morias has already tried.
Hmm... there must be a way...

Best Regards
Carsten

nanoqui

Hi there.... what do i need to change to make it work / adjust it to the 5inch touchscreen from waveshare?

hondagx35

Hi nanoqui,

the Display has HDMI input, right?

If so it should work out of the box.
The only problem could be the touch driver, but this has to be tested.

Frank

Aquarius

hondagx35 wrotethe Display has HDMI input, right?

If you refer to the official 7" touchscreen, then the answer is "no" it's a DSI interface with the Raspberry Pi. It's seperate from the HDMI output. So much that you can drive both simultaneously if you need to (yeah for dual screen !!

)

nanoqui

Display works, only thing I don't know is how to adjust it so that the whole screen is filled. Right now I have the rune display a white stripe and 1-2cm black.
Can I modify that in the config.txt file or do I have to dig deeper...?
Thank you

morias

morias wroteHowever, if I leave the raspberry pi running for some hours, the screen will have turned off and I cannot get it to come back on by either touching the screen or running the force on command.

Hi Frank

I haven't been able to fix this problem. Unless someone has a solution, perhaps as a workaround, would it be possible to have a button on the playback screen which if pressed would run the xset dpms force off command? That way dpms could be disabled and the screen would remain on unless the "turn off screen" button was pressed. Once the force off command is run, the screen will come to life again if it is touched.

I have set my player up this way this morning. It is running and I have forced the screen off. I will see if the problem with getting it back on manifests itself at the end of the day.

hondagx35

Hi Aquarius,

it's a DSI interface with the Raspberry Pi.

I know that, i made the image for the 7" TFT.

The question was for the 5inch touchscreen from waveshare.

@ nanoqui

Display works, only thing I don't know is how to adjust it so that the whole screen is filled.

This is strange, because it has the same resolution (800 x 480) as the 7" Pi TFT.
Maybe it doesn't report correct mode, so please try:

hdmi_group=2
hdmi_mode=1
hdmi_mode=87
hdmi_cvt 800 480 60 6 0 0 0

in /boot/config.txt

Frank

hondagx35

Hi morias,

the "turn off screen" button was pressed. Once the force off command is run, the screen will come to life again if it is touched.

And this also works after a longer off time?

would it be possible to have a button on the playback screen which if pressed would run the xset dpms force off command?

At the moment i have other priorities, so sorry.

Framk

Aquarius

hondagx35 wroteHi Aquarius,

it's a DSI interface with the Raspberry Pi.
I know that, i made the image for the 7" TFT.

The question was for the 5inch touchscreen from waveshare.

oups... sorry for the misunderstanding

drlbradley

Complete noob here , just got a Pi and the 7inch tft to build an Internet radio for my kitchen (get crappy fm reception in there)
I've got runeaudio installed and running , but the thing that's going to compel me to use rune is this new build ,with the built-in browser. Great work ! (Donation coming soon!)

/David

morias

I believe I have found a solution to my screen issue when setting it to sleep.

The clue was that after some hours when the screen would no longer come back on when pressing it, if I ssh'd to my pi, after a while I could get the screen back. When doing this, it would take a few goes to get the ssh connection going. It would still fail again later, but at least hopefully that meant something.

I stopped thinking it was a software problem and started thinking it was a hardware problem.

I changed power supplies, but that made no difference.

I then started changing wifi dongles. I switched out the Edimax dongle and tried a couple more. Finally i used my Comfast dongle. So far so good. 14 hours going strong. Hopefully I don't have to retract this post again tomorrow.

Edit:. Hi Frank, thanks for your post below. I did speak too soon again as it wasn't working in the morning. I did have out go all day which was the longest yet. Looking forward to a solution when it is available as I am really liking the music box.

hondagx35

Hi morias,

i now was able to reproduce your "wake up" issue.

It's exactly like you described, after 2h i'm unable to wake the display by touch events.
So i started to debug the issue:
- the touch controller is alive

cat /dev/input/mouse0

will show you the touch events.

-

export DISPLAY=:0
xset dpms force on

does nothing

-

echo 1 > /sys/class/backlight/rpi_backlight/bl_power
echo 0 > /sys/class/backlight/rpi_backlight/bl_power

and the display was back on!

- check dmesg:

[141995.213217] rpi-backlight rpi_backlight: Backlight change failed
[142596.057794] rpi-backlight rpi_backlight: Backlight change failed
[236727.917929] rpi-backlight rpi_backlight: Backlight change failed
[238294.198989] pcm512x 1-004d: No SCLK, using BCLK: -2

So it seems to be a backlight issue.
I think we have to wait for a fix, see here.

Frank

nanoqui

Thanks, that worked like a charm!

Maybe it doesn't report correct mode, so please try:

hdmi_group=2
hdmi_mode=1
hdmi_mode=87
hdmi_cvt 800 480 60 6 0 0 0

in /boot/config.txt

Frank

nanoqui

Hi morias, hi hondagx35,

how about enabling the screensaver

 xset s on

instead of dealing with the energy saving feature?

 xset -dpms ? ? ?

Just an idea. It worked for me... playing more than two hours without touching. Haven't tried so far if it also works if you don't use it longer for two hours.

nanoqui

Hi hondagx35,

I noticed some "bugs"...
1) the keyboard is not popping up when I want to add webradio stations, also when I want to save a playlist, the same issue...
2) I don't know if that's also the case if you use the 7inch touchscreen (I have a 5inch), but I have a small space over the header where I see the main screen scrolling past when using e.g. playlist. The gap over the header bar dissapears when I use command out the custom midori style sheet to have the smaler fonts...
3) Everytime I "click" on something, a little framed box showing the link address is popping up either on the bottom left or right side... can this be avoided?
4) How do I get rid of the small colour square in the top-right, it's kind of blocking the visibility of the menu drop bar.
5) Rotating of the screen doesn't seem to do anything... changing

lcd_rotate=2

lcd_rotate=0

should rotate the screen by 180° but its still the same. I'd like to try how it looks like when I turn it 90°, how can I do that?
6) Do you have a solution for the occasional crashing when you click fast in a row? Anthing promissing yet with other browsers?

Thanks for this great piece of art!

« Previous Page Next Page »