> What I did is that I set aside 32 bytes of memory and each byte of memory
> represents one ASCII character on the LCD (16 bytes for Line 1 and the
> others for Line2).  Then I store the A/D results in appropriate
"coordinate"
> in the memory.  After that, I "copy" the entire memory block (the 32 bytes
> block) to the LCD.  Whenever I want to update a certain A/D number, I go
to
> its memory location and update the number, then do the "copy" to the LCD
> again.
>
> Is there a better way to do this?  There must be...

This is not necessarily such a bad way of doing it.  Having one routine that
always sends everything simplifies the code and therefore makes it more
reliable and maintainable.  I'm not that familiar with these types of LCDs,
but sending 32 bytes doesn't sound like much of a burden on the system.  As
long as the cycles and buffer memory are available, I think this is a very
reasonable approach.


********************************************************************
Olin Lathrop, embedded systems consultant in Littleton Massachusetts
(978) 742-9014, olin@embedinc.com, http://www.embedinc.com

--
http://www.piclist.com hint: The list server can filter out subtopics
(like ads or off topics) for you. See http://www.piclist.com/#topics