What changes are needed in Server Operating system using OPC with Labview

[84576874]

I am a novice trying to connect Labview into KepwareEX OPC server. I am using MS Windos XP on both sides. at first I could see no OPC server I checked with the Kepware and they suggested me to fix the DCOM configuration on the Server. at last I saw the OPC Server and their client connected to it.
When I try to assign a Datasocket connected to a control on Front panel in to OPC. System Browses and see the OPC server but after selecting the tag. when I run the software, connection Lamp gets red and this Error comes up ""Can't connect to OPC server. Registery Access denied" . the Kepware  quick client is working OK. and Labview got connected when I tested it on the same server. I think there is something wrong with Server OS configuration cause I can not See the Labview OPC Server too, which is installed but I am not using it, Can anybody help me ?

[waldemar.hersacher]

If you have Win XP SP2 the Windows Firewall may be running and supressing the connection. Turn off the Firewall to see if it will connect. Look into any log information of the Firewall to let you detect which additional ports or applictions you must allow to connect.

Unfortunatly I have now expirience with the Windows Firewall because I use the Kerio Personal Firewall. Firewalls are often the reason not to connect over a network when running local is successful.

[unclebump]

What labview version are you using?? Do you have the DSC module??

[84576874]

I turned off firewall on both systems and I fixed the DCOM settings just as it is said in the Kepware documentation about DCOM. the Kepware quick client is connecting to the server and I can see the Kepware server on Labview browser but the Control on the front panel can not connect. Furthermore I can not see Labview OPC on the labview browser. I am not using any Directory service such as Active Directory. PCs are just normal Win XP SP2. Can it be the cause of the problem?

I am using Labview 8.2. I don't know what is DSC module. I did not buy any hardware...

[.avi file]

Hello:

     When you try creating a new I/O server and when you select OPC, you should be able to see the list of OPC servers installed in the system. You can select LabVIEW OPC and select a I/O item from the configure OPC client instance.

From what I understand you are able to connect from LabVIEW just fine. Are you able to use server explorer and connect to kepware? The following tutorial will step you through using OPC servers with LabVIEW.

http://zone.ni.com/devzone/cda/tut/p/id/3742

DSC is LabVIEW add-on for developing your HMI/SCADA or high-channel-count data-logging applications. With the DSC Module, you can interactively develop a distributed monitoring and control system with tags ranging from a few dozen to tens of thousands. The following link has a TCP modbus presentation that you will find useful.

http://www.ni.com/labview/labviewdsc/upgrade.htm

Please let us know the steps you are following to configure the OPC connections and post some snapshots. This will help in better understanding.

Thanks and hope this helps
Regards
Avi Harjani

[ebnelson]

I think I know how to fix your issue.  I had a very similar problem.  It turns out that the address (xml) that the OPC client in DSC is getting a bad address.  My OPC client in DSC was putting a ".1" on the end of the address.  Check by going to your shared variable library in the project explorer.  Then right click on your IO server and then select properties.  Look at the list of registered OPC servers.  Select the server you want to connect to and see that name populate the Prog ID field.  Now, if that Prog ID has a ".1" on the end of it then edit it off and click ok.  Deploy all the variable and try again. 

This little fucker took a full week of tweeking my system to find.  Thanks and good luck!

[84576874]

I think I've found the reason for the problem it seems that added to the normal permissions that Kepware OPC server needs for DCOM other permissions accessing the registery is needed for Labview. for temporary uses I added Everyone to administrator group of the server and problem was fixed. for permanent use I think I will connect my system to an Active directory system.