Lookout

cancel
Showing results for 
Search instead for 
Did you mean: 

WHEN DRILLING DOWN FROM A LOCAL MACHINE TO TAGS IN LOOKOUT 5 ON A REMOTE BOX, THE TREE BECOMES CYCLICAL AT THE REMOTE MACHINE LEVEL RATHER THAN SERVING UP THE TAG LIST.

THIS OCCURS USING KEPWARE SERVER AND QUICK CLIENT, AND FROM VISUALPLANT ADMIN. BOTH THE REMOTE AND LOCAL MACHINES ARE RUNNING ON WIN2K. ANY INSIGHT?
0 Kudos
Message 1 of 5
(3,491 Views)
Hi,

It was not completely clear to me what the situation is, but it seems that from lookout you cannot browse to a remote third party OPC server, confirm if that is the case.

I would advise you to run in the machine where lookout is installed the two command lines:

1. regsvr32 "c:\program files\national instruments\logos\lkopc.dll"
2. "c:\program files\national instruments\logos\lkopc.exe" /regserver"

See if that fix the problem. If not which OPC server exactly you cannot browse ? Do the OPC server provider has a demo version that we can use to try to reproduce the behavior ?


I hope it helps


Best Regards

Andre Oliveira
Applications Engineer
National Instruments
0 Kudos
Message 2 of 5
(3,491 Views)
Andre,

The problem occurred when attempting to browse into Lookout using Kepware's OPC server and their OPC Quick Client, or VisualPlant's Administrator.

We've already registered the above .dll and .exe, which had solved the problem of not being able to see the Lookout server at all.

We have learned that Lookout does not use OPCEnum and requires that you be logged in as an Administrator in order to browse down through the tree structure. Is there a way to use OPCEnum, as it is not practical to be logged onto a plant floor machine as an Administrator full time?
0 Kudos
Message 3 of 5
(3,491 Views)

In addition to Andre's answers/questions I've following:

I assume for the future National Instruments updates the OPC Client to use OPCEnum.exe. (Lookout 5.1)

Here is an additional KB which might help further as a workaround:
Setting Proper Access for Remote OPC Server When Using National Instruments OPC Clients 

In addition, I did not really understand from your description what you mean by cyclical. If you are using Lookout in a Server-Client architecture, you should not use the OPC client object. You should use the built-in Lookout network capability. (Logos)

The Lookout OPC Server interface (aka Logos OPC interface) is an interface that publishes all Loo
kout/Logos Real-Time points on the network through OPC. If you want to limit that the "publisher" interface browses for all Logos items on the network to just this certain computer items, you would need to change a registry key.
Normally you have a key like:
HKEY_LOCAL_MACHINE\SOFTWARE\National Instruments\OPC Logos Interface\1.2
Logos Root URLs: mycomputername=\\.,network=\

If you don't want your Lookout OPC Server to browse for the whole network for Logos Real-Time points you need to delete the part ',network=\' in the Logos Root URL key. Or you could add some specific other computernames seperated with a comma.

Hope this helps
Roland

0 Kudos
Message 4 of 5
(3,491 Views)
By "CYCLICAL" I mean that as the tree expandes each branch simply repeats the previous branch. Again, we found that this was corrected by logging into the plant floor machine that has Lookout running on it as an Administrator.

Perhaps one of the folks at NI could respond to my previous query?
0 Kudos
Message 5 of 5
(3,491 Views)