WOW!! Thats a perfect solution...can't believe I did not think of it...thanks

I have an LK202-25 and I will be managing the display and keypad via a VB 6 application. I have managed to create an app which exercises most of the features of the display but I can not find a way to discover (read) the setting (ie. contrast, brightness, etc) values.

Are there any functions for ...

Thanks again for the help.

The display (in this application) does not use a backlight. So am I correct in assuming that I can just connect pins 1-14 and simply leave 15 and 16 unconnected?

Oh one other quick question. I will be managing the display and keypad via a VB 6 application. I have ...

Hi Steve,

I can't find a datasheet for your display. I know it s an Emerging Display Technology product, but I suspect it's obsolete.

EDT only has 1 current offering in the 24x2 and as far as I can tell, it is pin compatible with the LK control board. But that determination is based on a lot of ...

Hi Steve,

Unfortunately it's not as simple as replacing the display. The MO board has a fixed character layout that cannot be changed by swapping display. If you swap the display, and assuming all other parameters remaining the same, the display will still function as a 20x2. The additional 4 ...

Well the display dimensions (including bezel) are 4.02" x 1.12" (L x H).
The PCB dimensions are 4.65" x 1.41.

There are 14 pins (2 rows of 7) on the left side of the board labeled 1 -14. Connections labeled 15 and 16 are on the right side of the board.

As to thepart number I do not know but this ...

I am not sure what else I can provide. I need precisely the functionality of the LK202-25 only with a 24X2 display (well actually I don't need any of the GPO functionality).

I have an older piece of equipment which has a custom 14 key matrix-style membrane keypad with a 24X2 LCD. This keypad ...

I need this solution (the LK202-25) but with a 24X2 display. I have a display can I simply remove the 20X2 display from the LK202-25 and replace it with my 24X2?

Thanks,
Steve