Email: Password: Remember Me | Create Account (Free)

Back to Subject List

Old thread has been locked -- no new posts accepted in this thread
???
10/02/08 14:26
Read: times


 
#158767 - come conufusion with the file
Responding to: ???'s previous message
sorry michael, what happened was there were two versions of the header file . lcd_en, LEN and EN are one and the same thing .(in the latest ver. i have replaced all the En & LEN to only LCD_EN ) {i assumed there was a conflict some where so i went about again sorry for the confusion.

as you can see from the pin connections
p3.7 - EN
and p3.5 - RS .

so p3.7 corisponds to the MSB ( hence i have used 0X80 [1000 0000] )
and p3.5 is the 6th bit (hence 0x20 [0010 0000 ])

about your suggestion michale
as far as my knowledge goes ( which is very limited indeed )
doen't the LCD only accept data or commands only then the Enable pit is toggled (high to low ) ??
if this is true then in the command

void lcd_data (unsigned char dat)
{
lcd_port = (((dat >> 4) & 0x0F)|RS);
lcd_port = (((dat >> 4) & 0x0F)|EN|RS);
lcd_port = (((dat >> 4) & 0x0F)|RS);


the first line

lcd_port = (((dat >> 4) & 0x0F)|RS);
will simply be ignored .





List of 29 messages in thread
TopicAuthorDate
lcd port switching problem            01/01/70 00:00      
   P0 does not have internal pull-ups            01/01/70 00:00      
   P1 or P2 should work similarly            01/01/70 00:00      
   i do know that about P0            01/01/70 00:00      
      But how about the control defs            01/01/70 00:00      
         yes i have moved them as well            01/01/70 00:00      
         here is the lcd part of the code            01/01/70 00:00      
            correct me if i am wrong            01/01/70 00:00      
               Tried everything?            01/01/70 00:00      
      Again, I guess you are mixing            01/01/70 00:00      
         could you please poin it out in the code            01/01/70 00:00      
   header file            01/01/70 00:00      
      the above show NOTHING, but here is a guess            01/01/70 00:00      
   hardware problem?            01/01/70 00:00      
      errors not consistent            01/01/70 00:00      
         I am somewhat puzzeled...            01/01/70 00:00      
            come conufusion with the file            01/01/70 00:00      
               My suggestion was to...            01/01/70 00:00      
                  will try that michael            01/01/70 00:00      
         Multimeter is enough            01/01/70 00:00      
            will try that out            01/01/70 00:00      
               Tests both sw and hw            01/01/70 00:00      
   lcd simulator (from keil)            01/01/70 00:00      
      i do not know your chip ...            01/01/70 00:00      
         keep in reset as in ?            01/01/70 00:00      
            if open collector supervisor and reset low            01/01/70 00:00      
   the lcd worked on P0 with pull ups            01/01/70 00:00      
      which processor?            01/01/70 00:00      
         AT89C52            01/01/70 00:00      

Back to Subject List