使用搜索功能查看 Kepware 的信息库,其中包含 500 多篇知识库文章。缩小搜索结果范围,或在下面的搜索字段中输入您的查询。

或者,如果您无法找到解决方案,我们还有另一个资源:我们的 PTC eSupport Portal。 如果系统提示您登录 eSupport Portal,您可以使用“我的 Kepware”凭据。需要一个“我的 Kepware”帐户吗?在此处创建

搜索解决方案结果:
View All Solutions

Kepware Knowledge Base: Solution


Why Is There a Limit on the Number of OPC .Net Clients that Can Connect to the Server?


Last Update: 2018/11/12
Problem:
A user has several OPC .Net clients to connect to the server, but notices it fails after connecting five clients.

Possible Cause:
The OPC .Net interface is designed around the Windows Communication Foundation (WCF) framework. The default setting supports 16 concurrent sessions, calls, and instances. This framework assumes that there is one CPU. OPC .Net clients consume two sessions for each client connection.

Solution:
Edit the OPC .Net Interface's configuration file to increase the number of available connections. This amount is based on the number of CPUs available in the PC. Set the throttling properties to a value greater than 16 times the number of CPUs. For example, if the PC on which the server is running has 8 CPUs, the value would be greater than 16*8 (128). For more information, refer to the example instructions below (which assume that an 8 CPU PC is being used).

1. To manually change the settings, first open "xi_server_runtime.exe.config" (located at ProgramData\Kepware\KEPServerEX\V5\Xi) in an XML editor or Notepad.
2. Next, locate the element <behavior name="XiServer"> in the file. Then, insert the following:
<serviceThrottling
maxConcurrentCalls="200"
maxConcurrentSessions="200"
maxConcurrentInstances="200" />

Note: For more information, refer to Microsoft MSDN's Optimizing WCF Web Service Performance.