How to extend the maximum number of MODBUS TCP Server managers which can be defined in the console?

[maroo303]

I am in the process of creating a WinCC OA project, which require the setup of a 1 Modbus driver (Client) on one machine and on a separate computer a set of Modbus TCP servers, whereby each has its own manager. My question is here: What is the maximum number of MODBUS TCP Server managers can be defined in the console, since I am planning to setup about 250 managers on the Modbus Server WinCC OA project? If there is a limitation, is it possible to extend the number of managers allowed?

An excerpt of the config file is attached below.

[adaneau]

Hi,

From a technical point of view the maximum number of managers from one type which can be connected to one system is 255 (manager number 1 up to 255).

Be careful, I think that modbus server is sharing numbers with OPC UA server / OPC DA server and probably some others.

Also 250 modbus server in one project seems for me very dangerous, from load point of view. I dont know if it is officially supported but you can probably ask etm support about it.

BR
Alex

[Gertjan van Schijndel]

Murwan Mohamed wrote:

What is the maximum number of MODBUS TCP Server managers can be defined in the console, since I am planning to setup about 250 managers on the Modbus Server WinCC OA project? If there is a limitation, is it possible to extend the number of managers allowed?

The console/pmon has a limitation of 100 managers, but with remote projects you could more managers to your project. With a distributed system you could divide the load over multiple machines and increase the complete project limitations.

Why do you need so much Modbus servers? Also with a single Modbus server it is possible to serve different data to different clients.

[maroo303]

Hi Guys,

many thanks for the prompt responses.

As I mentioned previously the project setup consists of 1 Modbus driver (Client) on one machine and around 250 Modbus TCP servers on another machine (distributed system). This configuration is meant to work as a simulator and is only restricted to the defined servers, which are all providing the data to the specified client.
For each of the 250 components all the associated files (mass configuration) DP list, including plant model CNS views, config file were generated. All worked fine and tested by importing the generated lists. Although the "progs" file contains all servers and numbers only a subset of WCCOAmodsvr were inserted into the console. I was wondering if there is a way to expand this limitation in order to allow for more managers?

[mkoller]

I'm not sure I understand your setup, but it seems you're trying to add 250 Managers into ONE project (progs file).
The hardcoded limit is 100 managers per project's progs file, so currently one Pmon on one machine can only handle 100 entries from the progs file.
If you really really need more than 100 managers, the only way would be to split this to multiple projects, each running its own pmon
and therefore having each 100 managers possible.