You say you have changed the timings, but I don't know how far you have gone. I use a wide variety of LCDs, and find the following parameters work with all of them.
DEFINE LCD_COMMANDUS 2500
DEFINE LCD_DATAUS 200
|
You say you have changed the timings, but I don't know how far you have gone. I use a wide variety of LCDs, and find the following parameters work with all of them.
DEFINE LCD_COMMANDUS 2500
DEFINE LCD_DATAUS 200
Charles Linquist
|
what happen when you play with the contrast voltage?
What if you use..
how about the usual..Code:Start: PAUSE 2000 LCDOUT $FE,1,"Hello" Here: Goto here
is a simple Led Blink work
How about your config fuses
how about your crystal speed
Sorry to asked but sometimes we have
Steve
It's not a bug, it's a random feature.
There's no problem, only learning opportunities.
|
LCD still vexing
I just tried your ideas but to no avail. I previously tried several values for COMMANDUS and DATAUS out to 5000 and 250 µS each. I also tried several PAUSES of 1000 to 5000 mS in various spots in the program. I didn't try mister e's idea, though, because I think that I need the list of DEFINES to make the 16F690 work. Right? This display did work with a 16F84a and a simple program like that one.
Thank you for your consideration,
Dennis
|
I hate that datasheet... see table 9-2
ANSEL=0 will solve the problem.
Steve
It's not a bug, it's a random feature.
There's no problem, only learning opportunities.
|
Vexing LCD Solved!
Dear mister e,
That was it!! Thank you so very much. I did use the ANSEL = 0 but on a bit level. I guess that maybe I over thought it, or not. Again, thank you.
Best Regards,
Dennis
Members who have read this thread : 0You do not have permission to view the list of names.
Posting Permissions
Bookmarks