04-01-2003 09:20 AM
04-02-2003 02:06 PM
04-02-2003 02:47 PM
04-07-2003
09:29 AM
- last edited on
02-25-2025
11:25 AM
by
Content Cleaner
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
04-10-2003 07:39 AM