Matrix Orbital Corp

i have the first original GLK12232-25, not -SM or -WBL, and i was wondering if there is anything special i have to do to set it up to use I2C mode. I am trying to interface the LCD with a PIC16F876. I see for -SM there are a couple steps you must take to activate I2C mode, but no such mention in the other manual / datasheet.

and by any chance, would someone know if i need pullup resistors on the SDA and SCL pins?

thanks!

Check this: http://www.matrixorbital.com/manuals/gl ... /index.htm

On 2002-06-19 08:34, Pheonix wrote:
Check this: http://www.matrixorbital.com/manuals/gl ... /index.htm

I don't have the -SM. The back of my LCD looks very different from the image in that manual. I looked through both the -SM and the -WBL (replacement for regular GLK12232-25) and neither are really helping me, unless I am totally missing something in these manuals (probably )

/me shouts Heeeeeeeeeeeeeeeeeeeeeenrrrrry

HEHEHEHE.. I'm here, I'm here..

Dexter, the GLK12232-25 and GLK12232-25-WBL are almost the same thing... (the -WBL has hardware scrolling). As for the pull up resistors, the display does not have pull up resistors on the display or have spots on the board for them. I would add 2.7K resistors onto the master (or in the cable it self)..

To talk to the LCD is not much different then over RS232...

Here is more info from the manual (it's not in the graphic ones yet, sorry)

The idea of ACK is to indicate when the data has been received correctly. ACK does not indicate data incorrectly received. ACK simply fails to indicate when data is correctly received. Clearly, this is of limited usefulness and even less so with Matrix Orbital modules. Matrix orbital modules are not capable of failing to acknowledge an incorrectly received byte in response to that bytes transition. They are only capable of failing to acknowledge the bytes following the byte, which was not received. To fully understand the reasons for this one needs to understand something about how a Matrix Orbital module processes data. Basically the reason why a Matrix Orbital module might fail to receive a byte correctly is that it was unable to process the byte previous before the failed byte was transmitted. Because the module cannot possibly know that it would be unable to store the byte before the next byte was received it cannot know to not ACK. The reason for this situation in deference to situations you might be familiar with (i.e. memory chips, etc

mmmmm info....thanks henry. thanks alot!
important stuff there, with all that 7 / 8 bit stuff.
so the module is ready to go to use I2C, just start sending data to it and it will know? no jumpering / cutting connections?

yup...

On 2002-06-19 11:22, Henry wrote:
yup...

sweetness. thanks again, im gonna make a feeble atttempt at getting I2C up and running later when i get home.

Good Luck...

Wrong button


<font size=-1>[ This Message was edited by: CriticalPoint on 2002-06-19 18:39 ]</font>

Henry,
I tried getting this going and I am having MAJOR problems. After doing extensive testing, I am thinking the LCD is at fault. I will email you with more detail.

OK.. got the e-mail... I will post some of the stuff here for others to read.

On 2002-06-24 05:23, Henry wrote:
OK.. got the e-mail... I will post some of the stuff here for others to read.

thanks Henry.
im at work now, and for some reason i cant check my email from here (company wont let me log onto my POP3, yet whenever i walk around the office i see all these desk jockeys logged onto hotmail lol ).

On 2002-06-24 08:13, Dexter wrote:

On 2002-06-24 05:23, Henry wrote:
OK.. got the e-mail... I will post some of the stuff here for others to read.

thanks Henry.
im at work now, and for some reason i cant check my email from here (company wont let me log onto my POP3, yet whenever i walk around the office i see all these desk jockeys logged onto hotmail lol ).

We got smart and blocked all hotmail accounts from our mail servers

any...um...updates? lol