Lilliput 619 USB/Driver Problems? Let's research this... (unknown device)

**akula169** · 08-10-2006, 12:59 PM

Ok, so add me to the group of people that can get the Touchscreen drivers on the Lilliput 619 working for about 2 minutes on the first install on a clean system - then nothing after that.

Here's the deal. I've been able to get the touchscreen USB drivers to recognize the device on three occasions. All three instance were on a fresh install of the latest drivers from egalax.com.tw - fresh meaning that this is the first time they were installed on the OS. I waited until the software was installed to plug in the USB connector. On first discovery, the drivers detected the device as USB Touchscreen Controller, USB bus discovered device as VID 0EEF, PID 0001 (vendor and product IDs, used to discover identity of USB device and apply the appropriate drivers). Great - this is what we expect.

Now, if you unplug the USB cable and replug it, the device all of a sudden becomes "Unknown Device". If you follow the normal steps, and click the Nexts and all that as if it were a normally discovered device, you should be able to go into device manager and find the device under "Universal Serial Bus controllers" as "Unknown Device" - double click it to get the properties and then the Details tab to see that the instance ID is now reported as VID: 0000 and PID: 0000 - these values cause windows to report Unknown Device, immediately...

This is the part that puzzles me. It is the hardware that reports these VID/PID values. How would it change from reporting the correct values on a "virgin" system and then fail (with 0000 0000) on all subsequent attempts? Could it be possible that some piece of software is somehow interfering with reporting the proper values for the USB device instance?

If we can figure out why this is happening, I think everyone's problems will be solved. I'm still working on investigation, but wanted to get this info out there - maybe it'll trigger some thoughts from others...

Here's a slice of my c:\windows\setupapi.log showing how the values changed:

Code:

[2006/08/10 10:47:24 1100.3 Driver Install]
#-019 Searching for hardware ID(s): usb\vid_0eef&pid_0001&rev_0100,usb\vid_0eef&pid_0001
#-018 Searching for compatible ID(s): usb\class_ff&subclass_ff&prot_ff,usb\class_ff&subclass_ff,usb\class_ff
#-198 Command line processed: C:\WINDOWS\system32\services.exe
#I022 Found "USB\VID_0EEF&PID_0001" in C:\WINDOWS\inf\oem11.inf; Device: "USB Touchscreen Controller(Universal)"; Driver: "USB Touchscreen Controller(Universal)"; Provider: "Touchkit"; Mfg: "Touchkit"; Section name: "usb_univ_Inst".
#I023 Actual install section: [usb_univ_Inst]. Rank: 0x00000001. Effective driver date: 03/22/2006.
#I393 Modified INF cache "C:\WINDOWS\inf\INFCACHE.1".
#-166 Device install function: DIF_SELECTBESTCOMPATDRV.
#I063 Selected driver installs from section [usb_univ_Inst] in "c:\windows\inf\oem11.inf".
#I320 Class GUID of device remains: {4D36E96F-E325-11CE-BFC1-08002BE10318}.
#I060 Set selected driver.
#I058 Selected best compatible driver.
#I063 Selected driver installs from section [usb_univ_Inst] in "c:\windows\inf\oem11.inf".
#I320 Class GUID of device remains: {4D36E96F-E325-11CE-BFC1-08002BE10318}.
#I060 Set selected driver.
#I058 Selected best compatible driver.
#-166 Device install function: DIF_INSTALLDEVICEFILES.
#I124 Doing copy-only install of "USB\VID_0EEF&PID_0001\5&817B42&0&1".
#-166 Device install function: DIF_REGISTER_COINSTALLERS.
#I056 Coinstallers registered.
#-166 Device install function: DIF_INSTALLINTERFACES.
#-011 Installing section [usb_univ_Inst.Interfaces] from "c:\windows\inf\oem11.inf".
#I054 Interfaces installed.
#-166 Device install function: DIF_INSTALLDEVICE.
#I123 Doing full install of "USB\VID_0EEF&PID_0001\5&817B42&0&1".
#I163 Device not started: Device has problem: 0x0a: CM_PROB_FAILED_START.
#I121 Device install of "USB\VID_0EEF&PID_0001\5&817B42&0&1" finished successfully.
[2006/08/10 10:51:00 1100.3 Driver Install]
#-019 Searching for hardware ID(s): usb\unknown
#-018 Searching for compatible ID(s): usb\unknown
#-198 Command line processed: C:\WINDOWS\system32\services.exe
#I022 Found "USB\UNKNOWN" in C:\WINDOWS\inf\usb.inf; Device: "Unknown Device"; Driver: "Unknown Device"; Provider: "Microsoft"; Mfg: "(Standard USB Host Controller)"; Section name: "BADDEVICE.Dev".
#I023 Actual install section: [BADDEVICE.Dev.NT]. Rank: 0x00000000. Effective driver date: 07/01/2001.
#-166 Device install function: DIF_SELECTBESTCOMPATDRV.
#I063 Selected driver installs from section [BADDEVICE.Dev] in "c:\windows\inf\usb.inf".
#I320 Class GUID of device remains: {36FC9E60-C465-11CF-8056-444553540000}.
#I060 Set selected driver.
#I058 Selected best compatible driver.
#-166 Device install function: DIF_INSTALLDEVICEFILES.
#I124 Doing copy-only install of "USB\VID_0000&PID_0000\5&316CB136&0&2".
#-166 Device install function: DIF_REGISTER_COINSTALLERS.
#I056 Coinstallers registered.
#-166 Device install function: DIF_INSTALLINTERFACES.
#-011 Installing section [BADDEVICE.Dev.NT.Interfaces] from "c:\windows\inf\usb.inf".
#I054 Interfaces installed.
#-166 Device install function: DIF_INSTALLDEVICE.
#I123 Doing full install of "USB\VID_0000&PID_0000\5&316CB136&0&2".
#I121 Device install of "USB\VID_0000&PID_0000\5&316CB136&0&2" finished successfully.
[2006/08/10 10:52:36 380.819]
#-199 Executing "C:\WINDOWS\system32\libusbd-nt.exe" with command line: system32\libusbd-nt.exe
#-166 Device install function: DIF_PROPERTYCHANGE.
#I292 Changing device properties of "USB\VID_0000&PID_0000\5&817B42&0&1".
#I303 DICS_PROPCHANGE: Device has been restarted.

**skidogg77** · 08-10-2006, 01:47 PM

I have found that once the device changes to UNKNOWN, if I do a reboot and hit F8 and choose "Last Known Good" everything goes back to working order. I still haven't been able to find the permenant combination.

A warning to anyone that plans to post "Send it back" this is not a solution. After doing many searches. This problem can effect any of the touchscreens used by our members. The only common trait are the drivers.

**akula169** · 08-10-2006, 02:07 PM

Grrrrr. F it all.

I now think that I have a flakey cable connector... looks like if I twist the screwdown part of the connector down as hard as I can that it seems to want to work ok.

I think I've seen similar reports of this - I might have to hardwire my own USB cable directly to the board to make sure it is more reliable.

Sorry for making this more complicated than it turned out to be...

I guess at least if you had symptoms like mine you now know the solution

**klp45** · 08-10-2006, 02:11 PM

I've had this problem for a while. I hooked my 619 up to my moms box with out pointing it to the drivers and it found it - universal touch screen controller - great - but it would let me calibrate it. Hooked it up to my test box and it loaded to universal drivers and had calibration. My epia would load it at all. used the lilli drivers that came with it and I continue to have the problems. I'm posting this as I am not sure if poeple are allowing windows to find it (Not sure that it make it stable). Both of the boxes I mentioned are xp pro with sp1. Might be of help to someone.

**MobiTekLink** · 08-10-2006, 05:44 PM

I'm having issues coming back from hibernation in XP, I'm currently re-installing XP because that issue was driving me nuts, I installed all the drivers and no luck

**cambo** · 08-26-2006, 06:18 PM

im avin unknown device problems

n no matter how i reinstall remove instal drivers touschscreen always wants t be classed as unknown

**akula169** · 08-28-2006, 11:47 AM

Originally Posted by cambo

im avin unknown device problems

n no matter how i reinstall remove instal drivers touschscreen always wants t be classed as unknown

You've got to make sure you've twisted the locking screw on the cable connection down as hard as you can.

I've had so many problems with this on my bench setup that I'm going to hardware a new usb cable direct from the controller board.

**MobiTekLink** · 09-04-2006, 10:51 AM

I've finally realized what its' doing; after installing every single driver out there the problem is that when returning from hibernation the touch screen wants to "right click" no matter even if you disable "right clicking through regedit".
It only goes to "left click" after you've used the mouse on the desktop and then it goes to normal mode.
I've tried disabling "right click" also on touchkit to no avail... Has anyone had this issue??!!

**akula169** · 09-07-2006, 04:51 AM

I finally solved my problem by soldering a new USB cable directly to the controller board.

**sxott** · 11-17-2006, 12:45 PM

Could you possibly post some pictures. I have a similar issue. The touchscreen works wonderfully, then randomly stops. It is not in the black screw connector though, rather it is where the 4 wire little white plug connects to the motherboard. There are 4 pads above it that I might be able to solder a bypass onto, but when I checked conductivity I got very strange results.

The plug layout is shown below (red, black, white, yellow) wires from left to right.

o o o o
----------
|x x x x|
----------

Basically there is all kinds of cross talk between the pins the plug hooks onto and any given pad. I guess there is a path back to other pads thru the circuits even though it does add some resistance. Because of this though I don't want to just randomly hook things up since I am not absolutely sure which connections go to what. The far left is ground (even though the wire is red) I am pretty sure.