1. LCD_DI or Data/!Instruction is another name for R/S which is more commonly found in the documentation for the panels.
2. It's curious that you say you always use the R/!W pin, but the LCD-lite code defaults to having that option unused.
3. The delay functions are hard coded for a specific clock rate, but you don't seem to document that rate. Since most C compilers for PIC's have a built in delay macro (e.g. __delay_us(byte) shouldn't that be used? A good compiler shouldn't require that to be a function when stack levels are critical. Perhaps I'm wrong on that? ON 20110630@6:20:25 PM at page: On a web page you were interested in at: http://www.piclist.com/Techref/member/IMB-yahoo-J86/HD44780-tty.htm#40724.7591203704 James Newton[JMN-EFP-786] Replied to post 40724.7591203704 by JMN-EFP-786 |Insert 'Ah... I just found the "4Mhz" in the header. My bad.' at: '' James Newton of MassMind asks:
Couple of quick notes/questions/comments:ON 20110630@6:29:12 PM at page: On a web page you were interested in at: http://www.piclist.com/Techref/member/IMB-yahoo-J86/HD44780-tty.htm#40724.7591203704 Isaac Marino Bavaresco[IMB-yahoo-J86] Replied to post 40724.7591203704 by JMN-EFP-786 |Insert '1. Good point! 2. The project that originated this particular version was one of the few I didn't use R/!W because it was too resource constrained and also it was only required to meet human-interface sppeds, so some extra delays would not be a problem. 3. Not every C compiler's library have good delay routines (or any at all), and often they have different definitions, etc. Besides, unfortunately not every compiler can be called "good". ' at: '' James Newton of MassMind asks:1. LCD_DI or Data/!Instruction is another name for R/S which is more commonly found in the documentation for the panels.
2. It's curious that you say you always use the R/!W pin, but the LCD-lite code defaults to having that option unused.
3. The delay functions are hard coded for a specific clock rate, but you don't seem to document that rate. Since most C compilers for PIC's have a built in delay macro (e.g. __delay_us(byte) shouldn't that be used? A good compiler shouldn't require that to be a function when stack levels are critical. Perhaps I'm wrong on that?
Couple of quick notes/questions/comments:James Newton of MassMind replies: Ah... I just found the "4Mhz" in the header. My bad.1. LCD_DI or Data/!Instruction is another name for R/S which is more commonly found in the documentation for the panels.
2. It's curious that you say you always use the R/!W pin, but the LCD-lite code defaults to having that option unused.
3. The delay functions are hard coded for a specific clock rate, but you don't seem to document that rate. Since most C compilers for PIC's have a built in delay macro (e.g. __delay_us(byte) shouldn't that be used? A good compiler shouldn't require that to be a function when stack levels are critical. Perhaps I'm wrong on that?