Thread: lilliput kills USB GPS

I get it the other way round... gps works but my lilliput TS doesn't. I've using a usb hub and it simply needs a power source attaching. It all works fine when I give it 5v. I think the gps antennas or TS are power hungry components.

Originally Posted by johnymd

Well I think thats whats happening......I nead help....its driving me made. My setup is: M1000, U2 fortura USB GPS, Lilliput 7" touchscreen, XP pro, Auto route 2004. The problems I'm having are this. Everything seems to be installed OK but when I try to use the gps in AR2004 I get initiallizing and no data. Now here is the odd bit. If I plug in a standard CRT monitor then it all works OK, then if I swap back to the TFT its OK untill I reboot. Any ideas? This has been driving me made for 2 days solid now. Any suggestions please as I'm running out of ideas........Please.

What version number of the touchscreen drivers are you using?

Also what are your USB GPS drivers? Do you have a version number for those or type/manufacturer (I.E. A lot of different GPS units use 'Prolific' USB-Serial chipset drivers)

Oh another thought...

Can you use hyperterminal to connect to the COM port that the GPS is on?

If you can connect at the right baud (maybe 9600) you should see the NMEA lines popping up. If so then it could be your Lilliput is too close to the GPS and the EMF affecting the signal.. Just a though..

I've searched these forums and the various website to get all the latest drivers and I don't think it is a driver problem, although I think the gps and touch screen are using the same com port. The touchscreen and gps work fine if I plug a crt monitor in so I think it may be todo with the monitor driver. Can't find any .inf files for this monitor...are there any? What are others installing it as..Default, plug and play(which it isn't) or anything else?

Originally Posted by johnymd

I've searched these forums and the various website to get all the latest drivers and I don't think it is a driver problem, although I think the gps and touch screen are using the same com port. The touchscreen and gps work fine if I plug a crt monitor in so I think it may be todo with the monitor driver. Can't find any .inf files for this monitor...are there any? What are others installing it as..Default, plug and play(which it isn't) or anything else?

The touchscreen part of the screen is completely seperate from the 'screen' bit, and if you have the USB touchscreen it doesn't expose itself as a COM port.

The touchscreen works even if the screen is not powered. Do you have the same problem with the touchscreen plugged into USB, but the monitor power unplugged and MB connected to the normal CRT? (you'll notice you should be able to use the touchscreen still)

Had'nt thought of using hyperterminal...I'll try that tomorrow. Any other ideas of testing the gps without having to loadup autoroute. And yes it is the prolific driver.

With the touchscreen pluged in and the crt connecteed it all works OK. Touchscreen and gps don't seem to have a problem.......its only when I connect the TFT part of it. Justcan't get my head round how the monitor driver can effect the gps. The reason I mentioned touchscreen and com port is a message flashes up when you install the driver saying checking com 3.

Originally Posted by johnymd

Had'nt thought of using hyperterminal...I'll try that tomorrow. Any other ideas of testing the gps without having to loadup autoroute. And yes it is the prolific driver.

Hyperterm is a great way, otherwise download SIRFDEMO from here:
http://www.holux.co.uk/Products/gm-210/download.htm

The exact drivers I am using are:
GPS http://www.stevegoodman.plus.com/gps_usb_prolific.zip
Touchscreen http://www.egalax.com.tw/Beta/Win2000_XP_3.2.3.3122.zip

And you can download updated touchscreen drivers from:
http://www.egalax.com.tw/Download.htm

A friend of mine had a similar sounding problem. He found if he set his lilliput desktop refresh rate above 60hz, it blocked or distorted the signals of his GPS unit. He originally had his desktop set to 85hz or 100hz. Dropping it to 60hz (I think this is the default setting) fixed it.

He posted his troubleshooting woes here:
epia m10k + lilliput => gps blocker?


-Scea