Lookout

cancel
Showing results for 
Search instead for 
Did you mean: 

Hypertrend stopped working

I'm using Lookout 4.5 to control and monitor 3 mass flow controllers (MFCs) via a single master controller connected via serial line. I had a working process, which included plotting the MFC values in a hypertrend. On the day I put it into production, the hypertrend stopped working. There are no alarm messages. The software was developed on the production PC (Win2K). The hypertrend was set-up with 5 groups, each displaying different views (scales) of the data. Each group now only shows 0, 1 or 2 of the 4 graphed items (the 3 MFCs and the total flow). The hyper cursor shows that the ungraphed items have blank data, but my digital displays show the data is present and valid. Is this a corrupt database issue? Before going into production mode,
I did re-install Lookout after having my Win2K account set to administrator, so that the software could be accessed from various user accounts. I tried it under my own account after the re-install, and it was still working. A few hours later, a couple of users told me the graph was not displaying data. I tried it in my own account again, and it was not working for me either. Help.
0 Kudos
Message 1 of 3
(3,305 Views)
NetRanger,
Verify that you still are logging the items that are not showing up in the hypertrend. The hypertrend reflects what is in the database, so if it is not being logged then it will not show up. Go to Edit Data Member Configuration.
The other possibility is a corrupt database. The quickest way to check is to stop Lookout and then rename the database folder. When you restart Lookout the a new database will be created. If the trends come back then it was a corrupt database. See the KnowledgeBase for more information:
http://digital.ni.com/public.nsf/websearch/6fc62f75b74d706d8625694900768f69?OpenDocument

Carl L
National Instruments
0 Kudos
Message 2 of 3
(3,305 Views)
Thanks Carl. It was a corrupt database. I saw references to database corruption in some other slightly related discussion postings. Deleting the contents of the old database directory fixed it. Is there any specific action that causes database corruption (e.g., not closing serial com before closing Lookout)?
0 Kudos
Message 3 of 3
(3,305 Views)