James, I understand. I'm going to post the code in a couple of minutes. Thanks, rich! On 10/23/2015 2:27 AM, James Cameron wrote: > As r/s line never goes high, work on that. LCD_Send_data requires it > to go high in order to clock data out. It's the cause of the LCD > ignoring you. > > I suggest writing a new program just to set r/s high, and test it > against your LEDs. > > Pastebin won't have a trouble with a large C program. It won't be > private. Don't use it if you don't mind others seeing it, but as > you're posting to PIClist you should already be fine with that. > > As for compression, don't worry about it. As long as you have a > modern web browser, it will handle compression for you. > > On Fri, Oct 23, 2015 at 01:32:57AM -0500, Richard R. Pope wrote: >> James, >> I just finished installing the LEDs. I increased wait(); to about = 2 >> seconds instead of about 20ms. The e line goes high and low. The r/w >> line goes high and low. The r/s line never goes high. Can I zip the code >> and put it into pastebin? I have never used it before. We could go >> private but then others will miss out on what we are doing here. >> Thanks, >> rich! >> >> On 10/23/2015 1:14 AM, James Cameron wrote: >>> Thanks. >>> >>> The LCD might not be properly initialised for communication, yet it >>> might still have a flashing or movable cursor? >>> >>> Is the PIC moving the cursor, or is the LCD doing it alone? >>> >>> I'm looking through a peephole at your code. My experience is better >>> suited to looking at all the code. Is there some reason you can't >>> share all the code each time? Too big? Use a GitHub Gist, or a >>> Pastebin and share the link by mail? >>> >>> Removing the check for busy doesn't sound like a good idea; if you >>> send anything while it is busy, it has the right to ignore you. >>> >>> The symptom you describe sounds like it is ignoring you. >>> >>> https://en.wikipedia.org/wiki/Pastebin >>> >>> On Thu, Oct 22, 2015 at 09:54:48PM -0500, Richard R. Pope wrote: >>>> James, >>>> I have never doubted your abilities and I have a lot of respect= for >>>> you and David. I have a flashing cursor on the LCD. I can also move th= e >>>> cursor around on the LCD. That is how I know that the LCD has been >>>> properly initialized. I have two o-scopes but I never thought of LEDs. >>>> I'm going to install the LEDs. That is a great idea. Here is what I am >>>> doing in main: >>>> lcd_initialize(i); //Initialize the LCD >>>> >>>> LCD_set_position(3); //move the cursor to the third position >>>> LCD_send_char('a'); >>>> //LCD_send_string("Hello!"); >>>> /*LCD_clear(); */ >>>> This is the routine to actually send the charac= ter >>>> to the LCD: >>>> extern void >>>> LCD_send_char(char char_) >>>> { >>>> //unsigned char character; >>>> //character =3D char_; >>>> LCD_data =3D char_; >>>> LCD_e =3D 1; //pulse the enable line >>>> //LCD_Send_data(character); >>>> wait_ms(5); //wait_ms for 5 milliseconds (us) >>>> LCD_e =3D 0; >>>> wait_ms(10); >>>> //read_busy_flag(); //wait for the LCD to finish >>>> } >>>> The commented out lines are where I have tried >>>> different ways of doing this. All to no avail. When I originally wrote >>>> this it was for a 16f84a. It ran on that PIC. But I have not been able >>>> to get it to work on this PIC. >>>> Thanks, >>>> rich! >>>> >>>> --=20 http://www.piclist.com/techref/piclist PIC/SX FAQ & list archive View/change your membership options at http://mailman.mit.edu/mailman/listinfo/piclist .