Share via

WaveShare touch problem

Question

Tuesday, August 25, 2015 10:04 AM | 1 vote

Just got today my brand new WaveShare 7" display with capacitive touch for Raspberry Pi 2. After few hours fighting with USB current supply (display gets powered via USB touch) I got display part working. Second struggle is with touch... Windows seems to recognize it with:

- ID: USB\VID_0EEF&PID_0005

- Description: Usb Input Device

- Class: HIDClass

- Manufacturer: (Standard system devices)

- StatusCode: 25190410

Still touch doesent seem to work at all. Does anyone have any advice how to proceed with troubleshooting or just wait for new WinIoT release and hope for the best? Please ask if you need more info about display.

All replies (29)

Friday, January 22, 2016 7:41 PM âś…Answered

Make sure you contact WaveShare though. The more people telling them it's needed, the greater chance there is that they do this.

Whoever does a working IoT touch screen that works are going to make a lot of money. They only one that is known to work has been sold out for months.

/Morten
twitter: http://www.twitter.com/dotMorten
blog: http://www.sharpgis.net

Tuesday, August 25, 2015 8:10 PM

I haven't seen any touch screens work out of the box with 10 IoT.

I have the exact same screen as you and I've been searching for a C# driver for that Goodix GT811 touch chip but to no avail. There is a C-driver provided on GitHub but I lack the skills to port it.

I would also appreciate any help that anyone can provide.

Wednesday, August 26, 2015 4:14 AM

There seems to be some displays with resistive touch from Adafruit that should work out of the box as they mimic mouse. I would have ordered one of them but needed capacitive one...

I try to ask from Goodix support of they are planning to provide driver for Windows 10 IoT Core. I come back with response if I get one.

Thursday, August 27, 2015 10:31 AM

Unfortunately no response from Goodix... Have you Phoenixke got it working on any device? I mean have you tried to connect it on PC try to get touch alive that way? I tried with no luck. PC seems to find some kind of HID drivers but touch still not working. Just thinking that is my touch broken or is it just meant for Linux devices...

Thursday, August 27, 2015 10:01 PM

I've tried it on Raspbian and works fine there. I've also written an email to WaveShare if they have a driver but they replied:

Dear Sir,

Sorry that the RaspBerry PI does not release the official windows 10 IOT yet, so we also don't have the touch driver for it neither.

Sorry for this.

Best regards

Johanna

I replied asking if there was a timeline for a touch driver, will keep you updated if I get more info.

Saturday, September 5, 2015 12:22 PM

Hi ,

I think we are talking about the Goodix GT811 134501A F18CF0

i have actually the same problem, i tryed to get a datasheet but i only found chinese version, but it was a wrong chip version.

http://www.datasheet-pdf.com/datasheet/Goodix/785436/GT811.pdf.html

In the description they talk about an I2C conncetion, but we have an USB interface.

If some one find a working Universal driver im happy, too.

Sunday, September 20, 2015 5:16 PM

I managed to get my 5" Waveshare LCD touch working using this code:

https://www.hackster.io/peteroakes/raspberry-pi-2-480-320-colour-lcd-displays-on-a-windows-10

It's not a touch driver though - it would be custom app code to listen for touch events. But it's a big step in the right direction. Trying to figure out if I somehow can figure out how to make touch driver based on this...

/Morten
twitter: http://www.twitter.com/dotMorten
blog: http://www.sharpgis.net

Thursday, September 24, 2015 5:11 AM

Nice demo, but like you said it would be nice to have actual driver. My display also has touch connected as USB and has different touch controller.

It would be interesting to try to make driver for it but problem with my touch controller (Goodix GT811) is that only datasheets I found were in Chinese :)

 

Wednesday, January 6, 2016 11:22 PM

The Waveshare LCD 7 in (C) 1024x600 capacitive touch screen works with both the built in drivers of Debian Linux (Wheezy and Jessie) as well as Windows 10.  However, you may have to repeatedly plug in and out the USB to get the touch to work.  It seems that this LCD panel has some initialization issues.  Anyone else have the same experience?

Thursday, January 7, 2016 5:25 AM

I just tried to plug and unplug my Waveshare ~30 times without touch working a single time. Have been using it (tho haven't tried touch every time) daily basis 4 months now and haven't noticed anything like that.

Wednesday, January 20, 2016 1:38 AM

I would *love* to get mine working.  What build and board version are you running?  I tried this, didn't seem to matter. 

Thursday, January 21, 2016 9:17 AM

I've officially given up.

Last release of IoT10 did not resolve the touch issue and Waveshare still does not provide a way to get touch working.

So unless you're running Linux or variants, don't ever buy Waveshare.

Friday, January 22, 2016 1:34 PM

Totally agree. Seems that Waveshare is protecting their products against piracy by not using standard touch drivers. Because I don't use Linux this is just expensive display for me.

Wednesday, February 10, 2016 3:05 PM

Are you refering to Windows 10IoT or the standard Windows 10? I have the same Waveshare 1024x600 touch screen. The display  in 1024x600 resolution through HDMI works fine, but the touch screen, even connected to an USB port, does not work with Windows 10.

Do you know a driver that could emulate the touch screen under the standard Windows 10? Help on this would be highly appreciated.

Friday, May 27, 2016 4:01 PM

I got the same issue, did you find a solution ?

Monday, June 20, 2016 9:12 PM

It looks like they have a revision 2.1 of their screens that would be compatible with Win10.

If anyone wants to give it a try, it doesn't specifically say IoT but I would imagine it'd work (perhaps not multitouch, but single could work).

Tuesday, June 21, 2016 10:22 AM | 2 votes

Hello,

I have the V2.1 - with Win10 it's working well, also on a Mac.
With Windows IOT official build it's also working on my RPI2.
With the insider preview it's not well working. Scroll OK, but click on a button is not OK.
The button changes like it is pressed, but the click event is not triggerd. If you tap many times very quick then it's fireing sometimes the click event -> see: https://social.msdn.microsoft.com/Forums/en-US/18d22938-ea6f-40a5-86ac-81b736f3108c/hid-touch-problem-with-insiderpreview?forum=WindowsIoT

BR

Walter

Tuesday, July 5, 2016 10:44 PM | 1 vote

Hi Walter,

If you are in contact with WaveShare, can you confirm that their device indeed passes the hardware certification tests for Windows 10 HLK / HCK? The supposition at this point is that the Waveshare firmware is incorrectly clearing the confidence bit in the HID reports upon finger lift but the certification tests will tell them for sure what is going on. 

Sincere thanks,

IoTGirl

Friday, July 8, 2016 3:24 PM

Hello IoTGirl,

I've send Waveshare a Mail.
I put also a link to this topic in and asked them to reply or give a statement here.

Let's wait for the answer.

Best Regards
Walter

Friday, July 8, 2016 5:16 PM

Many thanks Walter! Please do let us know when you hear back.

Monday, July 18, 2016 11:19 AM | 1 vote

Hi everyone,

I got response from Waveshare. They said this is a common issue and they can upgrade firmware in your display but you have to pay shipping costs to China. It's really strange that we can't do it manually via USB.

I asked for some workaround and I'm waiting for response again..

Monday, July 18, 2016 11:28 AM

Hello,

many thank's for this Info.
I got since over one week no response from Waveshare....

BR
Walter

Monday, July 18, 2016 5:01 PM

Hi Folks,

My recommendation is to keep pinging Waveshare.  Maybe returning the screens that have the defective firmware for a refund and ordering a new screen would get you the new firmware?

Sincerely,

IoTGirl

Sunday, August 14, 2016 10:47 AM

I use this: http://www.waveshare.com/product/mini-pc/raspberry-pi/7inch-hdmi-lcd-c.htm
In the older version of Windows 10 IoT 2015. Everything worked perfectly.
On the Windows 10 version of the IoT 10.0.14393.0 interface greatly retarding.
Touch input does not work properly: scroll work, pressing the button works from 5-15 attempts. The behavior is very strange. Moreover, the button itself is clearly a response by pressing (falls, obscured), but that that should be fulfilled not when you press the button.

Monday, August 15, 2016 4:04 PM

if you go to the website there are instruction for modifying config.txt.

http://www.waveshare.com/wiki/7inch_HDMI_LCD\_(B)\_(Firmware_Rev_2.1)

this has worked for me for several months. but note that after anniversary update , the touch isn't firing events (at least I think it's the update haven't had a chance to load previous version)

Thursday, August 18, 2016 12:30 AM

grsw92, Were you able to find out a workaround? How much is the shipping and how long does it take? I agree that the firmware should be user-upgradeable.

Thursday, August 18, 2016 7:24 AM

They said there is no workaround and firmware upgrade is impossible without sending display to them.. I've decided to use display for different purpose with my Windows PC (where touch works great) and for RPi I'm going to buy another, working one (not from waveshare for sure).

If you can't contact Waveshare or they are not responding I recommend to try reach them by a chat on their webpage.

Friday, November 4, 2016 6:47 PM | 1 vote

Hello,

I don't own the (C) touchscreen from waveshare, but I was confronted to the same issue with the 800x480px version of the display (B model). As I faced the same issue with the Waveshare support ("we don't know about the problem" / "we don't know how to solve it") I went the DIY route.

If any of you is interested I'd like to have a chat about getting my (B) model custom firmware for the touch display to work on the (C) version (given its hardware design is close enough).

Here's the project on Github: https://github.com/pysco68/waveshare-hid

If the (C) model's circuitry is based around an STM32F103 (or GD32F103) and the GT811 (that seems to be the case) then there's a good chance of it being just a matter of tweaking some configuration.

Cheers!

Wednesday, November 23, 2016 6:47 AM | 1 vote

I just wanted to report that one of my blog readers flashed the firmware on a (C) version of the touchscreen and reported that it is fully working now.