Posted: Mon Jun 24, 2002 1:14 am
This is part 2 of my saga of using a brand new BLK 202A-WB with i2c. While waiting for the resolution of the keypad issue (in another post) I wrote a quick program to basically blast text to the LCD.
I'm running the i2c bus at 100khz (what khz does the lcd run at? The manual never says). When I blast the LCD with text, eventually the LCD locks up completely. Powering on/off the embedded system doesn't make any difference, nor disconnecting/connecting the +5V pullup's for the i2c bus. Only power cycling the LCD will bring it back.
This lockup is highly related the how fast the text is being blasted to it. Putting in delays between characters and delays between start/stop's greatly reduced the amount of lockups. But they still happen eventually.
This setup is currently configured on a breadboard so I expect it's slightly noisy.
The display with the white text on blue background looks really good. Definitely the best looking matrix orbital LCD I have, maybe even better then your VFD. If only i2c reliably for me...
I'm running the i2c bus at 100khz (what khz does the lcd run at? The manual never says). When I blast the LCD with text, eventually the LCD locks up completely. Powering on/off the embedded system doesn't make any difference, nor disconnecting/connecting the +5V pullup's for the i2c bus. Only power cycling the LCD will bring it back.
This lockup is highly related the how fast the text is being blasted to it. Putting in delays between characters and delays between start/stop's greatly reduced the amount of lockups. But they still happen eventually.
This setup is currently configured on a breadboard so I expect it's slightly noisy.
The display with the white text on blue background looks really good. Definitely the best looking matrix orbital LCD I have, maybe even better then your VFD. If only i2c reliably for me...