GLCD and TouchScreen trouble

[skimask]

I keep going back to that grounding thing, static or EMI...
Neither of the datasheets has any helpful hints as to what might be going on.
Maybe try hooking a 'grounding wire' up to the touchscreen to the LCD frame, first with a 1K resistor (maybe less), then maybe a direct connection.
I'm thinking it's some sort of static buildup causing the controllers on the GLCD to go nuts.
Maybe try it sitting on a regular character LCD and see what happens? Not that a touch panel on a character LCD is any good, but it might lead to something...

[SteveB]

Maybe try it sitting on a regular character LCD and see what happens? Not that a touch panel on a character LCD is any good, but it might lead to something...

I just happened to have a 4X20 breadboarded up with this project, and the TS has no effect on it.

I'll look into the resistor idea tomorrow (or whenever I can get back to it this week). Not a lot of options to connect it to though, the lcd bezel is painted and there is nothing exposed on the TS. The "FrameGround" pin on the lcd is connected to GND. (I've also tried it not connected)

SteveB

[Ron Marcus]

I bet that the touch screen is creating an EM field due to the high frequency switching going on. Just for a test, take some of the static protective translucent poly bag material, and sandwich it between the two. If this doesn't relieve the problem, it should reduce the distance. You do have a wierd ground loop problem going on there. What is the hookup of your GLCD?
Ron

[SteveB]

As an update to my trouble shooting:
I can't think of a good way to hook up the resistor, but along that idea, I took a piece of 12gauge (maybe 10) bare copper wire, created a U shape and laid that across the bezel on three sides, from the bottom, around the right edge, then to the top. Laid the TS on top of this and it worked.

I am going to try and find a smaller wire and try that (or pound the 12gauge into a flat frame), possibly tonight if time permits. I'll also give Ron's suggestion a try at the same time. I was also thinking about an EM field, but not to much as that stuff is way over my head. BTW, the TS scan occurs every about every 10-20ms.

As for the GLCD hookup, Here is the pin arrangement. (I just noticed i put a 2620 in the above schematic, I am actually using a 4620)

Pin   		Connection
1	VSS 	0v 		– Ground
2 	VDD 	+5.0v 		– Supply voltage for logic
3 	VO 	None		– Supply voltage for driving LCD
4	RD 	PortC.2		- 8080 mode 1 = No operation 0 = Read
5	WR 	PortC.3		- 8080 mode 1 = No operation 0 = Write
6 	A0 	PortC.5		- 
7-14 	DB0-7	PortD		- Data Bits 
15 	CS 	PortC.4		- Chip select, Active L
16 	RES 	PortE.2		- Controller reset signal, Active L
17 	VEE 	None		- Negative voltage output
18 	FGND 	0v 		- Frame ground
19 	DISPOFF +5.0v 		- Display L: No Display
20 	WAIT 	None

Thanks for the help,
Steve

[skimask]

From what you just described, it sounds like you just need a chunk of wire to run from the frame of the touchscreen (maybe epoxy it on there?) to the frame of the GLCD...and that's it. If there is an issue with EMI, then that direct connection would effectively drain the field away, for lack of a better phrase...
Is the bezel of the touchscreen or the GLCD painted? Maybe that's why it isn't getting a good ground?

[Ron Marcus]

Where does the frame ground go? (pin 18)

[mister_e]

Silly questions:
1. What happen if you remove ALL ferrite beads?
2. what happen if you leave all unused i/o to input when you do ADC reading instead of setting them to LOW or HIGH
3. do you have any 10uF-47uF tantalum capacitor close to the GLCD Vdd rails
4. What happen if you use lower voltage for ADC convertion.
5. what happen if you tie VEE to GND with a 10k resistor
6. what happen if you load WAIT pin to GND or VDD with a resistor?
7. What happen if you slow down the ADCs readings?
8. How far the GLCD is away of the PIC?
9. What happen if you use some resistor in serie to the adc pins + 0.1 uF to GND?

[SteveB]

Skimask:
Is the bezel of the touchscreen or the GLCD painted? Maybe that's why it isn't getting a good ground?(pin 18)
The GLCD is painted black

Ron:
Where does the frame ground go? (pin 18)
I've got it tied to the GND rail on the breadboard

Steve:
1. What happen if you remove ALL ferrite beads?
No Change, thats what I started with.
2. What happen if you leave all unused i/o to input when you do ADC reading instead of setting them to LOW or HIGH?
I assume you mean the i/o connected to the TS. If this is the case, any pins connected to the TS that don't need to be driven a specific direction are made inputs so the pin floats. Typical, you drive one direction (X+ to X-) then read the opposite neg (Y-), and leave the other pin (Y+) floating. The exception are the pins used for ADC (A0 and A1), those are stuck with being analog inputs (at least A0 is).
3. do you have any 10uF-47uF tantalum capacitor close to the GLCD Vdd rails
Nope, good idea, and I imagine it can't hurt.
4. What happen if you use lower voltage for ADC convertion.
haven't tried it yet, I could drive it with 3v, probably using some MOSFETs I guess. I will put this in the hopper to try if/when I can
5. what happen if you tie VEE to GND with a 10k resistor
Don't know yet, into the hopper
6. what happen if you load WAIT pin to GND or VDD with a resistor?
Don't know yet, into the hopper
7. What happen if you slow down the ADCs readings?
By slow down, do you mean the frequency of readings or the actual ADC aquasition time?
8. How far the GLCD is away of the PIC?
They are at least 6 inches apart, at times as much as 8 or 9. I've use an old floppy drive cable to plug into the GLCD and break out to the breadboard.
9. What happen if you use some resistor in serie to the adc pins + 0.1 uF to GND?
I'll try this with the caps on the GLCD rails. Quick and easy to implement. Got a suggestion for the resistors, I'm thinking 330, or maybe even lower.

I'll start with the decouple caps first (and the suggestions from above posts, like Ron's poly bag for trouble shooting purposes), as they should be there anyway, then work through the list as I get time. Busy week at work. (I've written the last two posts on lunch/dinner breaks).

Thanks to all for the helping hand,
Steve