DG-16160, Problem with contrat HELP !

[Vric]

Hi

I know it's not a Crystalfontz product, but I need big help here. I started to work with the DG-16160-11-S1FTLY LCD. (it's a 160x160 pixel Grafic LCD on SED1335 controller)

Datasheet: http://personal.nbnet.nb.ca/dunnbarr//DG-16160-11-S1FTLY.PDF


I tried to wire it like this:

DataVision DG-16160-11 160x160 Pixels (SED133x)

JP1:

LCD    -> Description -> LPT
Pin 01 -> /WR         -> 1
Pin 02 -> /RD         -> 17
Pin 03 -> /CS         -> 14
Pin 04 -> A0          -> 16
Pin 05 -> /RES        -> 5 Volt
Pin 06 -> Data0       -> 2
Pin 07 -> Data1       -> 3
Pin 08 -> Data2       -> 4
Pin 19 -> Data3       -> 5
Pin 10 -> Data4       -> 6
Pin 11 -> Data5       -> 7
Pin 12 -> Data6       -> 8
Pin 13 -> Data7       -> 9

JP2:

LCD    -> Description -> LPT
Pin 01 -> Vss Ground  -> Ground Pin 18-25
Pin 02 -> Vcc         -> 5.0V
Pin 03 -> Vlc         -> Output: 0 .. -15.0V
Pin 04 -> Vadj        -> 10kOhm potentiometer to Pin 03 JP2
Pin 05 -> DISPOFF     -> 5V
Pin 06 -> LED +       -> 5 Volt + 100 Ohm Restistor
Pin 07 -> LED -       -> Ground

Wiring-Type: PowerLCD

Since i'm a visual man, I did this schema that I join.

The problem is, well it doesn't work. The Contrast part don't work at all. So problem look to be in Pin 02 03 04 05 of JP2.

Also, look at the data sheet (again: http://personal.nbnet.nb.ca/dunnbarr//DG-1...-11-S1FTLY.PDF)

on Page 11, you can see the Pin 3 of JP2 being INPUT, not output.

Also look on Page 13 for voltage regulation. I simply don't get it.

Please help me. I have 2 of those LCD and would not like to burn any of them.

Crystalfontz LCD Blog

Looking for additional LCD resources? Check out our LCD blog for the latest developments in LCD technology.

 

[cosmicvoid]

The data sheet indicates that pin 3 on JP2 is an input pin. With nothing connected to pin 3, is there any output voltage (perhaps being generated by a circuit on the display)? I suspect you will have to supply the -14v yourself. Until then, the display has essentially no bias, and will not show anything.

I think that tying the /RES signal high is not a good idea, as asserting /RES for a few milliseconds is part of the initialization procedure. Maybe it will work without doing that, but I think it is not guaranteed to do so.