LCD PROBLEM

mhmd.sh89 · Joined: 16 Mar 2013 Posts: 3

Hi friends

I have a problem with the flex lcd.c library.

When I connect the lcd on proteus , there is a warning about a logic detection (d4 to d7) , but the characters appear clear.
But on the board , I don’t see any thing clear , and I test the output of data , I saw that’s all are 5 v !
I don’t know what is the problem , but can you help about that?

My lcd pin map is :
#define LCD_DB4 PIN_C3
#define LCD_DB5 PIN_C2
#define LCD_DB6 PIN_C1
#define LCD_DB7 PIN_C0
#define LCD_E PIN_C7
#define LCD_RS PIN_C5
#define LCD_RW PIN_C6

If it’s impossible to help me about that , can you help me , how can I change the data pins as I like? In struct method in lcd.c , or any thing

Thanx

temtronic · Posted: Sun Mar 17, 2013 8:14 am

Not impossible but we need to see your whole program ! At least a small, compilable one that has the 'problem'.
The flex driver does work very well, has for years so my therory is that you're not setting it up correctly. As stated in the preamble of the driver, you need to list (define) the pins before the driver is installed.
Showing us your program will really help.

Also

Be advised that Proteus is full of bugs,errors,qirks,faulty DRCs and is NOT supported here.

So please, show us your code.

hth
jay

mhmd.sh89 · Joined: 16 Mar 2013 Posts: 3

hi temtronic

The issue isn't about the program because i used the lcd.c library and all's right and no problem appears.

but when i use the lcd_flex, the problem is that no thing clear on LCD.

I saw, 1 year ago, on another pc, a version of lcd driver by ccs, that has 2 choices, the structure or every pin Separately.

Has anyone seen this library ??

thanx very much temtronic for your reply

temtronic · Posted: Sun Mar 17, 2013 12:54 pm

Again, we'd have to see your program.
I've been using the flex_lcd driver for years now,in fact running as I type on a 18F46K22 test project,so I know it works fine.

hth
jay

Ttelmah · Joined: 11 Mar 2010 Posts: 19513

The normal thing would be that the pins are used by another peripheral, and your code does not configure them for normal I/O.
You need to simplify down to a minimum chip config, and test, verify the problem still exists, then post this.

Best Wishes

PCM programmer · Joined: 06 Sep 2003 Posts: 21708