Lookout 6.6 - No Trends On 6.6 Client or NIMax

Today I upgraded my Lookout computer running my server process file from 6.5 to 6.6. I then upgraded one other computer running development version (which is also the backup to the server) to 6.6 from 6.5. Now, I am unable to get trends from the server on this machine when i open any of my client files. And, when I go to Max and try to access the database on the server machine (PRIMARY1) by clicking on the + sign next to the 6.6 database, it will not expand. (see attachment)
However, on my laptop that is runnning the development version of 6.5 I have trends on my process files and can access the database on the server from NIMax. Also, I can open these client files on my server computer and I get trends as well.
I have the firewall turned off on all machines and all 3 machines are running Windows 7 SP1.
Any ideas would be appreciated.
Thanks
Jason Phillips
Attachments:
NIMax pic.jpg ‏147 KB

Since I am not getting any responses from NI related to my earlier posts, can someone from NI just tell me when installing Lookout on a computer running Windows 7 are there any guidelines as far as disbaling/enabling certain things in windows 7 (other than the firewall).
I am still having the issue with my clients all being disconnected from my server at random times, and when I restart my server process file I get a "process registration failed" error if I do not stop the lkads service before restarting the server file. I can duplicate this problem over and over again. I have done repair install and full reinstalls - problem still exists. I changed my server computer - problem still exists. All I can figure is bug in Lookout 6.5/6.6 or Windows 7 issue.
I cannot go back to Windows XP so this problem needs to be solved. Any immediate help from NI would be appreciated.
Thank you.
Jason Phillips

Similar Messages

Lookout 6 Hiccups

Sorry, this is a bit long winded....
I seem to have found the case of some of our hiccups with Lookout 6.0. We had been having problems with client workstations and extremely slow or now historical data trending on their clients. I had checked many things, including rebuilding the server and client processes, using ActiveX Trend vs. Lookout Trend and visa-versa, we used both an upgraded database and new database from scratch, etc.... I had spoken with support numerous times and they all had me trying different fixes.
NOTE:
Client Computers Discussed are Windows XP Professional SP2
Server Computer is a Windows 2003 Server Machine
One of our new client computers would not update historical trends at all, live data was fine, it would read that data and you could see it updating, but any historical trending would not work at all. I noticed that there is a new folder structure under the following (this will vary depending on your server computer's name and your server's database you are connecting to) "C:\Program Files\National Instruments\Shared\Citadel\_LocalCache\_monet_\_c__program_files_national_instruments_lookout_6_0_database_". I noticed that on machines that were trending historical data properly (or at least as properly as they could be, still slower then 5.0), there were files in this directory that seemed to be duplicating the database file structure on the server's machine, on the machine not trending, there were no files or just a log file (don't really remember). This raised my question about how the server and client communicate when using trends, I never got a straight answer from support, except to say that they talked to R&D and supposedly this folder has nothing to do with the historical trending on the client computer.
***HOWEVER***
During a recent non-related software upgrade, we found an issue with user rights assignments on Windows XP Professional workstations where for some reason, if a user was part of more then one group and they were a part of the "USERS" group, they would receive restricted access on the local computer even if they were a part of "POWER USERS" or "ADMINISTRATORS". We ended up having to make users part of the "POWER USERS" group only, to solve the unrelated problem. After doing this, the user with the non-functioning client noticed that the trends started updating on his computer.....and low and behold, there is now over 200MB of data in that cache folder, something tells me that the cache folder just might have something to do with the historical trending on 6.0 client computers. Hopefully at some point this post will either give someone some insight to a similar problem or at least any other database related issues they may be having with Lookout 6.0......or at least amuse someone.
If this all sounds a little sarcastic, it probably is....
Don't get me too wrong here, I do appreciate the new functionality provided with 6.0 and the new Citadel 5.0 database structure, but I think there are some serious inefficiencies in how the database functions and it seems like there is a major lack in documentation and knowledge on how it operates in the background.

fixthis,
I am unclear on what exactly you are seeing. "hypertrend chart updates, but the signals do not always appear." Do you mean the chart keeps scrolling, but the signals disappear? When you say "data window that pops up for the hypertrend does not update the data while moving the cursor across the hypertrend chart." I assume you are referring to the cursor data window -- what method are you using to move the cursor -- by clicking the arrows on the Hypertrend, by clicking on the cursor itself and moving it, by clicking the arrows in the Cursor data window, or by manually changing the time in the Cursor data window, either by using the arrows or typing a new time in?
Does this happen with both the Lookout Hypertrend and the NI ActiveX Hypertrend object? Does it happen when only one trace is on the Hypertrend or only with a larger number of traces?
We are very interested in knowing about Hypertrend/Citadel issues customers are experiencing, but unless we can reproduce the issue or have a very clear understanding of what is going on, it is very difficult to determine what the cause is or any possible fixes -- is it possible for you to post screen shots, and a very simple process file that will reproduce this problem?
Doug M
Applications Engineer
National Instruments
For those unfamiliar with NBC's The Office, my icon is NOT a picture of me

Losing hypertrend data on remote computers in Lookout 6.1

I know this issue has occurred in the past, but because we ares still losing trends too often, I am at the point where I am going to have to create expressions on my client process file for every data member I want to have on a hypertrend so that I can have each client machine get its trend data from a local database rather than pulling the data from the database on the server. Before beginning this tedious task, I wanted to get some input on why this might be happening.
When we lose trends I have to restart the server in order for the trends to come back. At first I thought is was caused by nicitdl5.exe crashing but I went into the settings for this service and set it to restart everytime it crashes. This did not fix the problem.
My client process file contains approximately 250-300 hypertrends with 24hr. time periods trending both numeric and logical data members (water levels and pump run statuses). Could the number of trends I have in my process file could be causing the issue (too many)?
Also, when I lose trends I have opened NIMax to try and create a trace for one of the members being trended and I cannot view the trace either - (no data) is displayed in the trace description.
And, another strange thing that occurs is immediately after closing my server process file, the trends appear on the client machine before I restart the server process file.
Some things I have done to try and correct the problem are:
1.) reduced the resolution for the numerics from .001 to 0.01.
2.) the resolution for the logicals from .001 (default) to 0.1.
3.) reduced the lifespan from perpetual to 15 days (did that today).
My server machine is a Dell PWS690 with 3.25 GB of RAM running Windows XP Pro, Service Pack 2, and the lookout version I am running is 6.1 (build 3)
Due to the size and location of our client computers, they have to go through 2-3 subnets to get to our server where the database resides.
Could this be a network issue where Lookout for whatever reason is disallowing access to the database after a period of time or because of a networking "hiccup"?
Plus, would using a local database to to display the info on these trends be a viable option in your opinion?
Please note: I AM NOT losing communication with my server as far as information coming from my plcs and being transmitted to the clients from the server.
Thanks for any quick response.
Jason Phillips

Maybe Ryan and crew can clear this up....
All that is needed for the discreet object connection form a remote client to the server is an IP address of the server and firewall ports on the server to be properly opened. There are references online for the Firewall settings.
Hypertrend connections are a different animal and I would like NI to step in and explain this if possible:
What I have observed is that the traces must be using a commonly blocked (by ISP's) port. I have to use a VPN to get the traces to work from an internet client. I also must either be logged on to the domain of the server machine or map a local network drive to the server Citadel (Database) directory. The map only needs read permissions.
I haven't been able to find any documentation online explaining the differences between live oject data (Logos?) and trace data connections (also Logos?...but different somhow?) over the Internet with Lookout and/or DSC and I would like to understand this better myself.
Ed
Message Edited by erblock on 04-01-2008 09:29 AM

Lookout locks up upon startup

Hi and Happy Holidays
I have just changed computers (upgrade) from older computer running windows xp home to newer computer with windows xp pro. I am using the same version of lookout with same process file. When the computer starts up from boot up and launchs lookout it freezes and goes into a state that only ctrr-alt-delete can be used to dump lookout program. Since the process uses OPC client, my first thought is serial port conflict with RS Linx. I also notice that in the earlier computer RS Linx had to be running in back ground before process would work correctly. Lookout for some reason starts OPC client automatically. This may be causing some problem as well.
If I disconnect the serial cable and allow lookout to fully load and wait for the missing serial cable alarm in lookout, then reconnect the serial cable the process works normal as long as the computer is up and running.
Info windows XP pro, Service Pack 2, Lookout 6.01 build 1, RS Linx 2.30.02 build 79
RS232 cable is connected to 1747-pic adapter to SLC503
I sorry if this has been discussed before, I did not see any recent activity.
Thanks Dan

I suggest you to upgrade toLookout 6.0.2 and its updates
It has fixed some OPC client's bugs.
Message Edited by Support on 02-04-2009 04:46 PM
Ryan Shi
National Instruments

Lookout WebClient Not Showing the Same data as on Server

Dear All,
I want to acquired/view the same process data on the lookout web client computer as i have develped on the Server, I completed the following steps.
Server Machine Steps.
1. I created the Lookout process on the development machine.
2. I created the LKWebClient on the C Drive root e.g C:\LKWebClient
3. I configured the web Directory as        c:\lkwebclient\
4. The Server URL was       http://server/llkwebclient/
5. I exported WebServer Files.
Note: I saved the process file process1.l4p in the root directory of lookout    e.g C:\program files\National Instruments\Lookout 5.0\
as it was suggested by lookout process.
Client Machine Steps.
1. I went to Internet Explorer
2. I type the following     //server/LKWebClient\Process1.htm
3. It is showing me the same Panel which i have created on the server computer
than what is problem???
When i change the value of contorl (Bush Button, Pot ), it is not reflecting on my Client Computer.
How i can view the changes on my Client Computer.

Which process do you compare with the web client process?
You should firts create a client process which connects to the server process. Then compile it into web client process. When you run the .htm file, you will see the client process in IE, and you should also run the server process in Lookout at the same time. The web client process connects to the server process directly.
If you run the client process in Lookout, does it work fine? Assume you use symbolic link in client process, take care the URL of the symbolic link, it should be absolute path.
Ryan Shi
National Instruments

Windows 7 lookout opc server problems

Hello,
I am not able to successfully read from my OPC server 2011 within Lookout 6.6 on one of my pcs. I had built a process on a different pc that worked. Now on a new pc, after installing NiMax and configuring a NIDAQ PCI-6052E device and building the NI-DAQmx Global virtual channels using AI1-AI8 points then installing and configuring Lookout and building up a process, I can see the AI1 - AI8 points in lookout when I traverse the object browser and find process1>OPCClient1>computername>system>DAQmx>AI1 (for example). Once I do that, lookout alarms with priority-8, object name ...OPCclient1, area-comm description - Internal error (2): Processing read data (50): Can't convert data to Lookout format (00000004).
This has worked on a different pc, when I run lookout as Administrator... Any help would be appreciated.
David Istre

Hello, I replied once, but my response did not show up on the discussion forum.
Both PCs are running Windows 7.
I have placed the opcclient.ini file within the Lookout folder and then ran lookout 2 times. The first time I ran lookout, I was getting data from my opc client. The log file shows that (from 8:11am). I closed lookout and did some other things for about an hour and then ran lookout again. This time I could not get data from my opc client. Again, the log shows that (around 9:50am).
Is there a way to use a NIDAQ card within lookout 6 without having to use OPCClient? Also, is there a way to get better lookout support than through these forums?
David
Attachments:
OPCclient1log.txt ‏64 KB

Lookout executable encountered problem

Hi guys,
We have lookout 5.0 installed(one server and 3 clients). Before all systems were working ok. But last one month, im facing several issues like:
1. one or two clients get stucked.And when i Restart the server all start working again.
2. Sometimes graphs are not get plotted then again restarting the server solve the problem. But restarting server everyday or two!!!! I reformated the server but same problem persists. system specs are 3 gb ram, 500 gb harddisk and win xp.
3. another issue im facing since yesterday whenever i try to make changes and save them... it get stucked and message pops up lookout encountered problem and needs to close......
please help me its quite urgent

Thank you for this update, Ryan.
The OS on this PC is WindowsXP Pro, with the lastest SP3. It has just updated Windows few weeks ago.
I thought that the problem might be with this oleaut32.dll, but if you don't recommend replacing it I will not do it.
One additional comment regarding this error: I have noticed some time ago that when I use AB driver (OPC) the process edits faulted very often. It was happening often when I tried to create a new object with AB OPC driver. I thought at that time that the issue might be with OPC driver, but I was never sure of that. Now I use Automation Direct OPC driver and it also stops running, but less often. My OPC servers run fine as far as I can see it. This might be just a coincidence, you might be more familiar with Lookout and errors. If it comes from Windows I will try to create a new process and follow your recommendations.
Darek

Lookout client wont start.

After installing Lookout client software it will not start up. When you run it it begins to startup and then I recieve an error saying
Part Of Logos
Part of Logos has encountered a problem and needs to close. We are sorry forthe inconvenience.
Under Errors Signature it says
szAppName: lkads.exe szAppVer:4.6.0.1046 szModName: lksock.dll
szModVer: 4.6.0.1046 offset: 0002b0a0
any help would be appreciated.

Well to make things more confusing if i dissable my network card before i run the lookout client, it starts up just fine.
after it starts up i can re enable my nic and open up my client processes and everythign works fine.
Im thinking it has to do with our Lookout server and Client Liscenses. Our lookout server use to say we had 1 client liscense and now it doesnt.
When you install the client software and connect to a process does the client liscense get permanatley assigned to that client computer ?
And if that is the case how can you re assign the client liscense ?
Any help or comments appreciated

Client Disconnected From Database

I'm running lookout 5.0 on one computer and logging its citadel to another machine. There is more than one lookout process on the PC that is actually running lookout itself. Different processes are logging to different designated database folders on the other computer. When you can actually get lookout to show the history info (i.e hypertrend data and such) on the computer it all works great. However if you ever restart the computer requiring to shutdown lookout, then the next time it boots up it is nearly impossible to get lookout to display the trend info again. You always get the "client disconnected from database" alarm. All the network paths and folder locations are correct. I am lost on this one.

Did you get this error every time you reboot Lookout or sometimes ?
If you get it sometimes:
Simply delete the /database/ Folder in Lookout directory
when you restart Lookout it will creat a new one.
From experience when you get this message the database is realy damage
i dont know why this happens.

How to speed up the BEA weblogic workshop perforkmance?

Hi,
Does anybody knows how to speed up the BEA weblogic workshop,as it consumes heavy memory.
I've configured the settings in workshop.cfg file and set the maximum memory size as 1024m midium size 516m and minimum size as 256m
and deleted all the files from .workshop directory before open up the workshop file.
But it hanging up the system when i opened the worshop file after some time. what could be the problem . i am using 2GB ram size

Hi Vishnu,
I agree this can also be one of the reason for the performance. There is Trend Micro Office Scan client installed on my system, but i couldn't not do any settings ,as it is disabled by sys admin .
however, i removed all the scanning processes from task manager and set the high priority for the java process! still, no improvement. There are only few jpd files not even 500kb size, but when i open them, weblogic cried and utilized lots lots of memory! :-(
I am afraid to open the weblogic which had jpd files,as it hanged my whole system, unable to perform any other tasks!

Unable to connect to NIOPCServers

I have Lookout 6.5 installed with the Integrator license. I have configured the NIOPCServer to communicate to an Allen Bradley PLC. I can open the NI OPC Quick Client and see live data from the PLC.
However, I am unable to connect to the NIOPCServer from any other OPC client. I have tried connecting with a Lookout client, ServerExplorer, and a few other 3rd-party OPC clients. I get an error "No such interface supported. Status Code: 0x80004002"
As a part of my troubleshooting
- I setup RSLinx. I was able to connect to RSLinx as an OPC client using Lookout, ServerExplorer, and the other 3rd party OPC clients.
- I have tried re-installing NIOPCServer.
What else do I try?
Thanks for any help you can provide.
Solved!
Go to Solution.

You can only use QuickClient, Lookout or LabVIEW DSC module to connect NI OPC Server.
So, you should be able to use OPClient object in Lookout 6.2/6.5 to connect the NI OPC Server. But ServerExplorer or other 3rd-party OPC clients don't work.
Actually even if you don't activate the license, the 6.5 evaluation license is able to connect NI OPC Server without error.
So please make sure the "lookout client" you said is either from 6.2 or 6.5. What's the alarm message you see in lookout?
Ryan Shi
National Instruments

Server wont launch

New install of Lookout 6.7 Integrator on Windows 8. Went through licensing and it says that it is licensed. When I launch Lookout 6.7.1 it always launches a client with a default demo. It won't allow me to File/New to start a new application server.

Suspect it may be related to Windows 8 ( Have not tested), works fine on multiple installs of Windows 7 x64
Forshock - Consult.Develop.Solve.

OPC will not write to AB L32E - Will Read

OPC will not write to AB L32E - Will Read.
I have been able to set up a OPC Server using the NI OPC Server, using the ControlLogix Ethernet driver for the AB 1769-L32E PLC.
All of the tags can be seen. The Lookout 6.7.1 will see real time data, but anything I write too, never shows up in the PLC.
Using the OPCclient in Lookout. Their is No alarm's, other than a value has been adjusted by direct user input..
Their is no comm errors.
I just purchased this software last month.
The NI OPC Server, Events, no errors.
Thanks.
Dave
Solved!
Go to Solution.

Thanks for your posts because I knew this should be possible. Here is what I found. Check step 4 of your channel in case your value updating is wrong or Step 11 of device is set to do not create on startup.
Thanks to the folks at Kepware. I was able to get this working for CompactLogix L32E.
Step 1: In NI OPC Server Create a new Channel. Channel Name can be whatever you want.
Step 2: Device driver will be ControlLogix Ethernet. You can also enable diagnostics if you want.
Step 3: Network adapter. I used default setting.
Step 4: Write only latest values. Duty at 10. ( These are default settings and are recommended.)
Step 5: Finish new Channel setup
Step 6: Click on Icon to create new device
Step 7: Device Name can be whatever you chose.
Step 8: Select Device Model in this case CompactLogix 5300
Step 9: Device ID For me was IP Address XXX.XXX.XXX.XXX,1,0 (Note the 1 directs path to backplane. The 0 to the slot where processor is)
Step 9: Device timing. Leave at defaults.
Step 10: Auto demotion leave unchecked.
Step 11: Leave at defaults Do not generate on startup Delete on create and allow subgroups
Step 12: Port and watchdogs at default settings
Step 13: Project options leave at default. (In my case I changed to short as that is what most of my tags were)
Step 14: Create tagname from device.
Step 14: Finish Device setup.
You now have two options.
Option 1: Start creating tags as you need them. (This is what I did)
Option 2: Right Click newly created device and select properities. Then select database creation and click auto create.
Go To Lookout and create new driver.
Select OPC Client
Server name will be from dropdown menu. National Instruments:NIOPCServers
Click okay
You should be done and smiling.

Can not find driver for Thinkpad T500

I can not find driver for Thinkpad T500? Could you please help me?
Moderator edit: Matched Subject to content.

Thanks to the folks at Kepware. I was able to get this working for CompactLogix L32E.
Step 1: In NI OPC Server Create a new Channel. Channel Name can be whatever you want.
Step 2: Device driver will be ControlLogix Ethernet. You can also enable diagnostics if you want.
Step 3: Network adapter. I used default setting.
Step 4: Write only latest values. Duty at 10. ( These are default settings and are recommended.)
Step 5: Finish new Channel setup
Step 6: Click on Icon to create new device
Step 7: Device Name can be whatever you chose.
Step 8: Select Device Model in this case CompactLogix 5300
Step 9: Device ID For me was IP Address XXX.XXX.XXX.XXX,1,0 (Note the 1 directs path to backplane. The 0 to the slot where processor is)
Step 9: Device timing. Leave at defaults.
Step 10: Auto demotion leave unchecked.
Step 11: Leave at defaults Do not generate on startup Delete on create and allow subgroups
Step 12: Port and watchdogs at default settings
Step 13: Project options leave at default. (In my case I changed to short as that is what most of my tags were)
Step 14: Create tagname from device.
Step 14: Finish Device setup.
You now have two options.
Option 1: Start creating tags as you need them. (This is what I did)
Option 2: Right Click newly created device and select properities. Then select database creation and click auto create.
Go To Lookout and create new driver.
Select OPC Client
Server name will be from dropdown menu. National Instruments:NIOPCServers
Click okay
You should be done and smiling.

On XP Machine dedicated to Lookout 6.5. The Hypertrends are not moving at proper pace according to the scale at the bottom of the trend graph. After 60 seconds it is 40 seconds behind, so the trace makes up the time with a straight line an repeats.

On XP Machine dedicated to Lookout 6.5. The Hypertrends are not moving at proper pace according to the scale at the bottom of the trend graph. After 60 seconds it is 40 seconds behind, so the trace makes up the time with a straight line and then repeats. Even without any traces on the graph, it does the same thing.
I've uninstalled and reinstalled the 6.5 software. Nothing else runs on this machine. It is dedicated to Lookout. I've installed a gauge object, with the same datapoint that the hypertrend is trying to graph, that updates very rapidly with no problem, so doesn't appear to be a network problem.
I'm only tracking one datapoint, at this time, until this issue is solved. Help please?

Here is the screen shot.
Definitions for this post:
- "streaming data" = Data coming in over ethernet from datapoint that is being polled.
- "1 scale-second" = 1 second of time based on the scale on the bottom of the graph
Remember that data continues to trace. However, according to the scale at the bottom of the graph, the graph traces 60 seconds of streaming data in @10 scale-seconds, then displays .01 second of streaming data over 50 scale-seconds. The .01 second of data is the long straight lines that you see between the rapid data traces that appear to be 50 scale-seconds.
Even without any datapoints being traced, the graph clicks forward 1 scale-second every 6 real-time seconds. It does this for @10 seconds then clicks forward @50 scale seconds, instantly. Then repeats, as you can see in the graph.
The gauge that is on the same control panel, that you see in the screen shot, is tracking the same data point as the graph. It is polling the data point at real time and never stops updating, so I know that the network is streaming just fine.
513.850.9509 - if I can help clear things up.
Attachments:
LookoutFunkyGraph.jpg ‏347 KB

Lookout 6.6 - No Trends On 6.6 Client or NIMax

Similar Messages

Maybe you are looking for