Thanks for the input!  I will probably change the code to do a paint only
when the contents of the display have changed.  The best reason I heard for
not continuously strobing the display is for EMI considerations.  It's nice
to know that I'm not the only person to ever try this, though.  Thanks
again.

;-)

michael brown

> I'm doing a project now that may actually end up being used in the real
> world on a wide scale.  It's the firmware for an escape-sequence
processing
> serial interface to a Hitachi based 2line X 20char LCD text display.  The
> program is written in C and uses a RAM based virtual display.  This
virtual
> screen is periodically "painted" to the LCD.  Right now I am "painting"
the
> LCD every 50ms (20 full screen paints/second) when there is nothing else
to
> do.
>
> Now, my question is, "Is this advisable?".  IOW, is it ok to strobe the
> display rapidly?  It looks ok, under incandescent lighting, but I worry
that
> fluorescent lighting may cause "beat" problems.  Should I just change the
> code to only paint the screen when necessary?  I did it this way thinking
> that
> watch-dog timeouts or other reset issues could be handled invisibly, since
> RAM doesn't change on a reset (8052 type).
>
> --
> Michael Brown
> Instant Net Solutions
> www.KillerPCs.net
>
> "In the land of the blind, he who has one eye is king"
>
> --
> 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
>
>

--
http://www.piclist.com hint: The PICList is archived three different
ways.  See http://www.piclist.com/#archives for details.