Hi,
I want to use the OPCserver in a Local Area Network,I have two ideas: First,runing LoggerNet4.0 and Opcserver on the Server PC A, runing the OPC client software on the client PC B.
Second,runing LoggerNet4.0 on the Server PC A,running the OPCserver and the OPC client software on the client PC B.
I tried both methods in the local area network,but neither is ok. Is anybody can help me ?
Thanks.
DU
Your second option is the only one we support. You need to make sure that you have remote connections allowed by your LoggerNet server and also make sure your Windows Firewall isn't blocking the connection. Then, the OPC server can connect from remotely another PC.
Ok,I got it,thanks!
DU
Hi,
if I understand right I wil have one PC where LoggerNet is running. PC A
The OPC Server and OPC client I have to install at another PC.
PC B
How does the OPC Server knows which PC is the PC where LoggerNet is running.
By using the demo-version of CSI-OPC, I can't da any changes to give OPC Server the information about the LoggerNet server.
Best regards
DH
The CSI-OPC server demo just allows you to see if your OPC client will support our OPC server. It doesn't actually connect to a LoggerNet server or provide any real data.
The purchased version of the CSI-OPC Server will let you specify the IP-Address of your LoggerNet server. So if you have Allow Remote Connections enabled in LoggerNet on PC A, and PC B can talk to PC A, and your OPC-CLIENT can talk to the CSI-OPC server, you should be set.
We have Loggernet4.0, CSIOPC and OPCclient running on a Windows 2003 server running all ok (since 2010)
For a new project, we have a Windows 2008R2 server.
We have Loggernet4.2, CSIOPC and OPCclient (Matrikon OPC Explorer)running on the same server.
Loggernet and CSIOPC are OK.
OPCclient cannot find the CSIOPS server.
Installing CSIOPC and OPCCLient on a 2nd 2008r2 server, works fine, but we cannot use this in this project.
Installing Loggernet4.2, CSIOPC and OPCclient on the same Win7-64bit computer works also OK
We have already set all firewall setting and DCom and COM settings a found on many websites.
Please help.
Windows Server 2008 R2 introduced some server management schemes that are radically different than previous windows server versions (such as 2003 server, or 2008 sever [i.e. 2008 without the R2]). It was done with the intent of improving security, etc.
There are some roles and permissions that need to be configured on the machine to allow the installation of LoggerNet (such as installing the proper .NET framework, and making the server capable of website serving). I'm assuming that there are some server roles or security permissions that need to be configured on the machine as well in order to allow your OPC client to communicate with the CSIOPC server. In other words, I believe the default configuration of 2008 R2 is blocking the communication path
between the two products.
However, all of these configurations of the R2 server are fairly involved "server administrator" tasks (not for the
faint of heart!). I recommend you get an IT professional
involved (or someone with similar capability) who can look into the details of how the R2 server is configured and can understand the communication pathways of OPC (or search the web to obtain details like that) and adjust the server settings to accommodate that.
Since Server 2008 R2 is not an officially supported LoggerNet and CSIOPC operating system, CSI cannot provide much more support beyond that given above. However, I would recommend that you post the results here after you get it working, so that others can benefit from your hard-won knowledge.
I'm guessing that in the end there are probably just one or two settings that need to be changed. Finding out what those are is the task at hand.
Good luck.