TommieB
unread,Jun 26, 2009, 4:52:14 PM6/26/09Sign in to reply to author
Sign in to forward
You do not have permission to delete messages in this group
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to ezLCD+ Support Group
Has anyone had trouble with the ezLCD suddenly locking up or freezing
(i.e., no longer responding to commands)? I have tried calling the
favr-32.dll directly using LabVIEW, and also I had someone put a .NET
wrapper around the DLL and tried calling it that way. Either case,
the screen stops updating after a few minutes. I wrote a program to
update the clock every second. After 30 seconds to 5 minutes, the
clock stops updating. No errors, just stops responding.
One of the commands listed in the manual is Favr32SetRefreshFunction,
which hints at screen lockups. However, I haven't seen any examples
of using this function. I tried using it, but there never seems to be
any event that triggers the callback.
If anyone has any examples (such as in C) of using this function, or
has similar problems with lockups, please let me know. Any help would
be greatly appreciated.
For background, we wanted to use the ezLCD-103 as a simple operator
interface for our test system. Basically, we want a Start button and
also display any warnings or other messages to the operator. We are
using bitmaps to generate the buttons, using touch protocol 1, BUTTON
STATE, BUTTON_DEF_LONG, and other commands. I'll be happy to answer
any questions that might help someone diagnose this problem for me.
Oh, we are using firmware 2.2c.
Thanks!
Tom