HK1144344A - Control node for a network of control nodes - Google Patents

Description

Control node of a network of control nodes

Technical Field

The present invention relates to a control node of a network of control nodes, and to a system comprising such a control node.

Background

The industrial automation of today's concept is based on the concept of decentralized control. The control tasks to be performed are separated into control nodes of the decentralized control system in a geographically and functionally optimal manner. The control nodes may communicate with each other and with superior systems via an industrial local network. In distributed control, the time and effort involved in the communication procedure can be reduced, since the respective control node automatically takes over the control tasks with respect to its own respective area and only needs to communicate with other control nodes and/or with the upper level system for coordination purposes.

In this connection, the basic concept of decentralized control is to subdivide the automation task into modules which are functionally and logically complete and which are then arranged in the vicinity of the program, thus reducing the writing and installation involved. By subdividing into multiple modules, complexity can be reduced, thereby enabling a simpler function.

The ethernet concept is the most widespread communication standard in Local Area Networks (LANs), which are based on a LAN arrangement in which a plurality of control nodes, e.g. computers or machines, are connected to one another via a shared transmission medium. The ethernet protocol packages the data to be transmitted into data packets (in the following, also referred to as telegrams) having a predetermined format.

The ethernet protocol is heavily used in office communication networks. Ethernet communication is increasingly used in industrial manufacturing and for exchanging data between control nodes, since the ethernet concept has the advantage that it makes it possible to achieve high data transmission rates while using simple network technology, so that standard hardware and software components can be used.

When controlling machines in industrial automation, it is necessary to process control tasks cyclically without time fluctuations, i.e. only small deviations in the range of a few microseconds (microsecond) are possible compared to the required cycle time, so that the control demand can be reacted with predictable reaction times. However, the real-time functionality and fast reaction time required in industrial automation, which is of only marginal importance in standard data processing applications typically used for ethernet communication, is of great importance. In order to ensure real-time functionality and fast reaction times when using ethernet in industrial automation, methods for priority handling of ethernet telegrams have been developed for real-time applications. Furthermore, in such modern data transmission procedures, networks are often used in parallel for real-time as well as non-real-time applications.

Although decentralized open control systems for data transmission based on ethernet protocols are increasingly used and can thus also be cost-effective, there is still a return on investment problem in industrial automation due to the ever-shortening of the product cycle time, and although new products have been developed in such a way that they can be easily produced automatically, the automation systems for the production of these products are usually designed specifically for the products to be produced and therefore can only be achieved with a great deal of time and effort if they are to be adapted to the product and the program changes.

Disclosure of Invention

It is an object of the present invention to provide a control node for a network of control nodes and a system comprising such a control node, which allows for a more flexible system management.

According to the invention, this object is solved by a control node according to claim 1 and a system according to claim 11. Preferred embodiments are presented in the dependent claims.

According to the invention, the control node comprises a transmitter module for exchanging data with other control nodes in the network in the form of data packets, wherein the transmitter module is configured to manage data to be transmitted in an output program image, to convert the output program image into a data packet, and to output the data packet onto the network at a predetermined point in time. Furthermore, the control node also includes a receiver module configured to log in the data packet to one or more transmitter modules of other control nodes and to convert a received data packet into an input process image.

The architecture of the control node according to the invention enables distributed control to be implemented in the form of an open system with high compatibility and adaptability with respect to the functionality of the control node. In fact, all control nodes comprise simple and consistent communication services that can accommodate any required production, or manufacturing, procedure without requiring a lot of time and effort to be involved. The transmitter-receiver communication model according to the invention also allows for representing the data exchange between the control nodes by external system operators in the form of a simple program image. Due to the fact that a control node can log in data packets to a plurality of control nodes by means of its receiver module, the communication relationship between the control nodes is determined in a flexible manner in order to carry out the required production and manufacturing processes in the system.

According to a preferred embodiment, the receiver module of the control node is configured to associate a quality date with a received packet, wherein the quality date refers to the age of the data packet, and the control node can determine the quality of the data communication based on the time delay between the transmission and arrival of the data. The application in the control node may then respond to the quality value.

According to another preferred embodiment, the transmitter module sends the data packets directly to one or more other control nodes, whereby non-real-time data is transmitted, preferably in an acyclic manner. Alternatively, however, the transmitter module may also forward the data packet to all control nodes present in the network, to thereby transmit real-time data preferably in a round-robin fashion. Therefore, parallel data transmission of real-time data and non-real-time data can be realized through the framework. While the real-time data is distributed cyclically to all control nodes, the non-real-time data is transmitted in a desired non-cyclic manner, so that the communication between the control nodes can be adapted ideally to production and manufacturing conditions.

According to another preferred embodiment, the data transfer between clients in the control node is performed in the form of a data image processing procedure, each client in the control node being configured to directly access the control node program image transmitted between clients, and this direct access in the internal data transfer within the control node makes possible a very fast data exchange involving a small number of protocols.

According to another preferred embodiment, each client in the control node comprises an organization unit, a finite state machine for processing the determined mode and state of operation, and a function unit for executing applications associated with the respective finite state machine. This configuration allows the respective clients in the control node to be constructed as independent modules with a minimum amount of external interfaces, thereby enabling improved distributed functionality of the control system while also reducing module complexity. The segmentation of the client into an organizational unit comprising the finite state machine and a functional unit for executing applications allows the client to be constructed in any desired way and allows them to be associated, thus ensuring simplified system control and ideal adaptation to manufacturing and production procedures.

According to another preferred embodiment, each client includes an event-recording unit configured to classify and understand events, and a data-recording unit configured to understand the data. This architecture allows the external interface of each client to be reduced to two common interfaces, i.e., one for event logging and one for data logging.

According to a further preferred embodiment, the i/o unit of the client is constructed in a variable form, wherein the i/o connection is defined as a local variable (local variables) comprising a universal character address (wildcard address), which can be freely constructed. This procedure enables an adaptive process flow in the control node for any desired production and manufacturing procedure to be achieved without complex hardware and software modifications.

According to the present invention, a system having a network of control nodes includes a network configurator configured to determine communication relationships between control nodes and/or between clients in the control nodes. By means of this architecture it is possible to react in a simple manner to an enlargement and modification of the production process and, with simple reprogramming, the network configurator can carry out a corresponding adaptation to the communication relationships between the respective control nodes and/or between the clients in the control nodes.

Drawings

FIG. 1 is a schematic diagram of a network having control nodes and a network configurator;

FIG. 2 is a schematic diagram of an initial phase in a network;

FIG. 3 is a schematic diagram of a control node architecture;

FIG. 4 is a detailed schematic diagram of the control node architecture shown in FIG. 3; and

fig. 5 is a schematic diagram of a data exchange between two control nodes having two clients, respectively.

Detailed Description

The use of decentralized control systems is constantly increasing in industrial automation operations, i.e. technical programs with software control and monitoring. In such decentralized control systems, the control tasks are split into multiple control nodes. The control nodes may communicate with each other via an industrial local network and, if desired, with superordinate systems. Fig. 1 shows such a decentralized control system, which comprises three control nodes 1A, 1B, 1C and a network configurator 2 for configuring and monitoring the network. The control node 1 and the network configurator 2 form a local communication network, known as a Local Area Network (LAN), which is a local communication network confined within a geographical area and comprising one or more servers or workstations, known as control nodes, connected to each other via a communication line 3, for example a twisted pair cable, or a fiber optic cable. Furthermore, various network configurations are possible for LANs, most commonly bus-based (bus), ring, star, and tree structures. Fig. 1 shows a LAN configuration having a bus structure.

A necessary requirement for LANs, when utilized in industrial automation known as a field-bus system, is real-time functionality. The fieldbus system has to guarantee that each transmitted data packet will arrive at the receiver within a defined guaranteed time. Since LANs operate using a network operating system and a unified network protocol, the preferred communication standard would be the Ethernet (Ethernet) concept, which in fact offers the possibility of using standard hardware and software components. Furthermore, while the ethernet concept is well known for simple networking technologies, it also has a high data transfer rate.

In the OSI layer model, which is an international reference model for transmitting data in a network, consisting of a stack of seven layers, wherein the total number of protocols is defined by each layer allocating its service to the respective next higher level, the internet protocol is allocated to the second layer, which is known as the transport layer. In this transport layer, data to be transmitted is bundled to form packets, and specific information of the respective communication protocols is added to the packets. Within the context of a network, the transport layer is responsible for transporting data packets from control node to control node and for error detection. In the ethernet concept, the transport layer is divided into two layers, the first layer adding a first header section (header) to the data, the header data including information required for a correct data transmission by the receiving protocol. At the second level, the data packets to be transmitted are then packed with a further header section and an end section for transport from the control node to the control node. Data with a length of up to 1500 bit groups can be transmitted by such Ethernet packets (also known as Ethernet packets).

In order to be able to use the ethernet concept also in industrial automation operations requiring real-time functionality, each control node 1 comprises a network interface 11 for real-time operation, so that, in terms of hardware and software technology, the network interface 11 can be implemented within the scope of the control node. The network interface 11 within the scope of the control node 11 may also allow parallel use of the bus system 3 for determining data for real-time applications as well as non-real-time applications. The data for real-time applications is prioritized by the network interface 11, so that first the transmission of real-time data takes place, and then the data for non-real-time applications are not transmitted for the remaining time until the next real-time application is transmitted.

For data transmission via the bus system 3, the network interface 11 of the control node 1 is subdivided into a transmitter module 12 and a receiver module 13. The transmitter module 12 manages data to be transmitted in an output process image (output process image). The data packets are transmitted, for example, in the form of ethernet telegrams. The transmitter module 12 of the transmission control node 1 converts the output program image into a data packet according to the network protocol, and then outputs the data packet on the network at a predetermined time point. The receiver module 13 of the receiving control node 1, the receiver module 13, logs in to receive data packets output by one or more transmitter modules 12 of another control node 1, and then converts the received data packets into input program images that can be processed by the control node 1.

With this configuration, it is possible to flexibly determine the communication relationship between the control nodes in the network even during the system cycle time, that is, dynamically, and to achieve a distributed control system having high compatibility with the used devices and apparatuses in a simple manner. Modification of the production and manufacturing procedure (e.g. extending, or changing the scope of the production) can also be achieved in a simple manner by changing the communication relationship, i.e. re-deciding the transmitter-receiver-module relationship indicating which control node has to transmit data to which further nodes.

The determination of the communication relationship of the transmitter and receiver modules is preferably done in an initial phase of the architecture by means of the network configurator 2. Thus, the network configurator 2 comprises a logging module 21 for determining the control nodes connected to the network. The registration module 21 is connected to a configuration module 22 in the network configurator 2, and the configuration module 22 determines which control node 1's transmitter and receiver modules 12, 13 have determined the communication relationship, i.e. which control node is to log in to which other control node via its receiver module for receiving data from its transmitter module. The configuration module 22 is then connected to a planning module (planning module)23, and the planning module 23 then transmits the communication relationships between the control nodes in the network determined by the configuration module to these control nodes.

However, after the start-up phase, the network configurator 2 can also dynamically adapt the communication relationships between the control nodes and/or the clients within the control nodes as well. By this arrangement, a reaction to an extension, or modification, of the product range is possible in a simple manner. The network configurator 2 then allows a corresponding adaptation of the communication relationships between the respective control nodes and/or the clients within the control nodes to be carried out with a simple re-planning.

The details of the initial phase of the distributed control system shown in fig. 1 are shown in fig. 2, wherein the arrows in the figure indicate the data exchanges performed. In a first step of the initial phase, the network configurator 2 records the control nodes 1 connected to the network. Thus, the control nodes comprise an explicit address associated with the respective control node, and the control nodes can be addressed via this address. For example, during the boot-up of the bus system, the control node may obtain this address via a Dynamic Host Configuration Protocol (DHCP), or via an automatic IP.

In order to automatically identify the control node 1, the network configurator 2 may use various mechanisms. The recording module of the network configurator 2 can transmit what is known as a broadcast message to all control nodes 1 connected to the network 3, and the control nodes 1 then respond to the broadcast message with a reply message, thereby notifying them of the effective address. Alternatively, it is also possible that each control node automatically transmits an identification telegram containing its address to the logging module of the network configurator 2 during the start-up.

In parallel to the address detection, the logging module of the network configurator 2 may also retrieve from the control node the device specification representing the network characteristics and functions of the control node, and/or the control node may automatically transmit the device specification to the logging module of the network configurator during power-up.

Based on the determined number of control nodes and their device characteristics, the configuration module 22 of the network configurator 2 then determines the communication relationships between the control nodes of the network, i.e. which control node should log into which other control node via its receiver module in order to receive the data of its transmitter module. For this purpose, the configuration module preferably comprises a system object model (system object model) and, for defining the communication relationship, the system object model comprises a standardized system description in combination with the determined device characteristics of the control node and a program description. As an alternative to inputting the device specification via the control node, the device specification may also be read via an external database or directly input into the network configurator 2 via a human machine interface. The system description and program description may also be provided to the network configurator, for example, via an engineering system.

The communication relationship between the control nodes 1 determined by the network configurator 2 indicates the transmitter module transmitting data and the receiver module receiving data, and the data transmission type and the data type, respectively. Data to be transmitted is divided into event data (acquired data), device data (device data), and process data (process data). Event data is used, for example, to determine and/or monitor the operating mode and operating state of control nodes, or to transmit device data that is not subject to real-time demands among nodes. Such event data may be the occurrence of an error, notification of an operational state, modification of a program signal, etc. The device data may be calibration data, program and product parameters, or other data. Generally, event data and device data are exchanged between control nodes in a non-cyclic manner, whereas program data is typically functional data necessary in the process and manufacturing flow. To ensure the defined data transmission, program data required for real-time applications are exchanged between the control nodes in a cyclic manner, while data required for non-real-time transmissions, such as program and product parameters, i.e. device data, are transmitted between the control nodes in a non-cyclic manner.

By means of the planning module 23 of the network configurator 2, data records comprising communication relationships can be written into the control node 1 via the bus system 3. The network configurator 2 may also transmit the product and process parameters for performing the desired production and manufacturing processes on the control nodes. After the initial process is completed, the distributed control system switches to mechanical operation to perform the desired production and manufacturing process. In this mode of operation, the network configurator 2 is no longer required. The network configurator 2 is then either shut down or takes over the monitoring functions in the production and manufacturing process, i.e. for example fault monitoring and diagnostics.

During the production and manufacturing process, the control node performs the exchange of program and event data according to the communication relationships provided by the network configurator. In a peer-to-peer connection, the transmitter module of the transmitting control node may transmit data directly to the receiver module of the receiving control node, or alternatively, the transmitter module of the transmitting control node may also send data to the receiver modules of the receiving control nodes. Furthermore, it is also possible to transmit data to the receiver modules of all control nodes connected to the network via the transmitter module of the transmitting control node. The general principle is that non-real-time data is exchanged via a point-to-point connection and in a non-cyclic manner, since such non-real-time data is event data and program parameters, while on the other hand program data required for executing real-time applications is transmitted to all control nodes in a cyclic manner, and in the case of real-time data point-to-multipoint connections and/or broadcast transmissions are possible.

Fig. 3 schematically shows a possible configuration of control nodes, wherein each control node comprises, in addition to the network interface 11 comprising the transmitter module 12 and the receiver module 13, device specifications representing the functionality and communication characteristics of the control node. Preferably, the device specification is in a form that is standardized for all control nodes and is stored as a file in the memory area 14 of the control node. The device specification can be accessed by the superior system or by the network configurator, as explained earlier, it can also be modified externally (i.e. instead of using the network configurator and/or the superior system, or the man-machine interface) to adapt the functionality and communication characteristics of the control node to the current state.

The device specifications of the control node, which describe the hardware of the control node and its functions and/or external interfaces, are associated with a mechanical model 15 in the control node, which mechanical model 15 converts device characteristics into images in the form of functions and separates the device functions from the real hardware control. By means of the mechanical model, the system and/or the functions within the control nodes can be modularized in a simple and efficient manner, thus constituting a decentralized control system. Since the mechanical model contains device functions, it provides automated modular units that operate in a self-supporting manner (i.e., without the need for a management system) for all devices, communications, and functional units, and each of which follows a unified abstract operational flow.

Therefore, the mechanical model 15 is divided into the organization unit 151 and the function unit 152. The organization unit 151 decides the state of the control node. The state of the control node is used to indicate the mode of operation, i.e. whether the machine is operating manually, semi-automatically or automatically, and whether the machine is in an initial mode or in a mechanical mode of operation. Further, the operation state of the control node is defined in the organization unit 151. The operating state may be, for example, a start, stop or error mode, and may be explicitly defined and processed by means of the organization unit 151 of the mechanical model 15 in the control node 1. The organization unit 151 of the mechanical model 15 in the control node 1, which provides clear transitions between operating states. Thus, organization unit 151 represents a finite state machine that provides the conditions for a desired state to be achieved by a control node without relying on external events.

The functional units 152 of the mechanical model 15 in the control node 1 comprise applications associated with respective operating states initiated by the functional units 152 in accordance with the operating states set by the organizational unit. The applications in the functional units of the control node can be accessed via the corresponding identifications. Thus, the organization unit 151 includes identification and functional parameters to be accessed in the functional unit 152, and implements the access. Therefore, the functional unit provides a basic function that can be externally set by parameters, and then the overall function can be obtained by the configuration of the basic function, wherein the basic functions can include the lower basic functions and the basic super functions formed in sequence.

The control node may be subdivided into clients 16A, 16B, 16C, which may define accessible functions of the control node separately and in a self-supporting manner. The subdivision of the control nodes into clients is freely configurable and independent of the actual hardware control. The client is then divided, in a manner similar to the machine model, into, in turn, an organization unit 161 for handling finite state machines that determine the operating mode and operating state, and a function unit 162 for executing applications associated with the respective operating type and the respective operating state. Thus, the clients of the control node are organized equally or hierarchically according to their function, in particular the function of the client may be subdivided sequentially into several sub-functions, including a plurality of sub-clients structured in a similar way as the upper clients. Therefore, the subdivision of the control nodes into client-side behaviors may provide even further simplification for grooming (particularly, the required determiners with respect to communication relationships). Clients and/or functional units 162 are included herein as functionally independent units that can be independently constructed and accessed.

By subdividing the control nodes into clients, the data communication rate can be further optimized and, in the case of data transmission between the control nodes, the data transmission can be carried out according to a network protocol, i.e. in particular according to the ethernet protocol, so that the transmission control node can convert the output program image to be transmitted into network data packets (i.e. for example ethernet telegrams) by means of its transmitter module, then output the data packets to the network at predetermined points in time, and then log in to the control node of this transmitter module by means of its receiver module, reconverting the received data packets into the input program image. Conversely, however, if data communication is carried out within a control node between clients in the control node, the data exchange is preferably carried out transparently by means of a data image processing program and is accompanied by direct data access by the clients to the control program images transmitted between the clients. Furthermore, these direct data image processing procedures of the clients in the control node can provide fast data exchange without requiring a large number of conversion procedures and/or transmission procedures via the transmitter and receiver.

Preferably, the data transfer process (i.e., direct data image processing between clients and network protocol conversion between control nodes) is provided by the network configurator during the initialization process described above. Thus, the communication relationships between clients in the control nodes are subdivided into events, parameters, and program data streams in a manner similar to the communication relationships between control nodes. At the same time, the data transmission type between the clients is also determined, i.e. the data transmission is performed in a cyclic or acyclic manner.

Fig. 4 shows the potential data flows in the control node 1 shown in fig. 3 with the machine model 15, wherein the machine model 15 comprises three clients 16, each of which encapsulates a device function, wherein the organization unit represents the interface to the event data flow and the function unit represents the interface to the program data flow, which transmits information on the operational type and, preferably, is exchanged in a non-cyclic manner. The program data stream comprises program data exchanged cyclically on the one hand and products and program operations or further static data, i.e. device data, transferred in a non-cyclic manner on the other hand. Thus, the flow of events, parameters and program data between clients in the control node can be carried out from one client to the next, or also in parallel to a plurality of clients or all clients.

To handle events, parameters, and program data flows, each of the control nodes obtains an event-logging module 17 and a data-logging module 18, which are connected to the network interface 11 including the transmitter module 12 and the receiver module 13 as shown in fig. 3. Wherein events (i.e., indications, notifications, errors in ongoing machine operations, etc.) are classified and understood by the event logging module 17. Furthermore, in particular, the superordinate control node has the possibility of accessing understood events, which are therefore classified into events that have to be acknowledged and events that do not have to be acknowledged, wherein they have to be acknowledged by an authenticated unit before they are removed from the event logging module 17. The data logging module 18 stores the parameters and program data and further enables, in particular, the upper level clients and/or control nodes to access the program data.

Fig. 5 shows a segment of a distributed control system comprising two control nodes 101, 102, and the machine model is subdivided into four clients 111, 121, 122, 123 with different functions, and each client comprises in turn two sub-clients 111A, 111B, 121A, 121B, 122A, 122B, 123A, 123B representing independent device functions. In fig. 5, the data transmission paths are illustrated between control nodes and/or in clients and/or control nodes between such clients. The data transmission in each control node is thus carried out in the form of a data image processing program, which allows an efficient and fast data exchange, and the data transmission between the control nodes is carried out in the form of a network telegram, which is converted into a program image.

Thus, the data transmission path starts in the control node 101, i.e. in the client 111 and in the secondary client 111A, and then proceeds from there to the secondary client 111B. Thereafter, the data transmission path from the secondary client 111B of the client 111 to the secondary client 121A of the client 121 to the secondary client 121B of the client 121 is followed by further data exchange across the control node boundary from the secondary client 121B of the client 121 of the control node 101 to the secondary client 122A of the client 122 and the secondary client 123A of the client 123 of the control node 102. The data exchange is performed according to a network protocol via the transmitter-receiver module of the control node, wherein the transmitter module converts the output program image of the secondary client 121B into data packets and transmits the data packets to the receiver module of the control node 102, and the receiver module sequentially converts the data packets into an input program image and transmits the data packets to the secondary client 122A in the client 122 and the secondary client 123A in the client 123. The data transmission in the control node 102 is then carried out from the secondary client 122A to the secondary client 122B of the client 122, from there to the secondary client 123B of the client 123 and further to the secondary client 123A of the client 123. At the same time, a data transmission is also performed from the secondary client 123A of the ue 123 to the secondary client 123B of the ue 123.

Claims (16)

1. A control node for a network of control nodes,

wherein the content of the first and second substances,

data transmission between the control nodes in the network takes place in the form of data packets;

the control node comprises a transmitter module (12) configured to manage data to be transmitted in an output program image, to convert the output program image into a data packet, and to output the data packet onto the network at a predetermined point in time, and the control node comprises a receiver module (13) configured to log in the data packet to one or more transmitter modules of other control nodes, and to convert a received data packet into an input program image.

2. The control node according to claim 1, wherein the receiver module (13) is configured to associate a quality date with the received packet, and the quality date refers to the age of the data packet.

3. The control node according to claim 1 or 2, wherein the transmitter module (12) is configured to send the data packet directly to one or more other control nodes.

4. The control node of claim 1, wherein the transmitter module (12) is configured to transmit non-real-time data directly to one or more other control nodes in an acyclic manner.

5. The control node according to any one of claims 1 to 4, wherein the transmitter module (12) is configured to forward the data packet to all control nodes present in the network.

6. The control node according to claim 5, wherein the transmitter module (12) is configured to transmit real-time data to all control nodes present in the network in a round-robin fashion.

7. The control node according to any of claims 1 to 6, wherein a data transmission between clients (16) is carried out in the control node in the form of a data image processing procedure.

8. The control node according to claim 7, wherein each client (16) comprises an organization unit (161) for processing a finite state machine determining the mode and state of operation, and a function unit (162) for executing applications relating to the respective current operation model and the respective current operation state.

9. The control node according to any of claims 1 to 8, further comprising an event-logging unit (17) configured to classify and understand events, and a data-logging unit (18) configured to understand the data.

10. The control node according to any of claims 1 to 9, further comprising an input/output unit (11) configured to define input/output variables as local variables, and the local variables comprise configurable universal character addresses.

11. A system comprising a network having a control node (1) according to any one of claims 1 to 10 and a network configurator (2), wherein the network configurator is configured to determine communication relationships between the control nodes and/or between the clients in the control nodes.

12. The system according to claim 11, wherein a recording module (21) of the network configurator (2) transmits a broadcast message transmission in the connected network (3) for recording the control node (1) connected to the system, and the control node connected to the network responds to the broadcast message with an identification message.

13. The system according to claim 12, wherein the logging module (21) of each control node (1) sends an identification telegram to the network configurator (2) immediately after power-on.

14. A system according to any one of claims 11 to 13, wherein each control node (1) has an effective address, and the effective address is either explicitly predetermined or obtainable via DHCP or via auto-IP, and the effective address is communicated to the network configurator (2).

15. The system of any of claims 11 to 14, wherein the network configurator (2) is configured to determine event and process data flows between the control nodes (1) in the network (3), and the control nodes are configured to perform an image process across the network by transforming a control node process image.

16. The system according to any of claims 11 to 15, wherein the network configurator (2) is configured to determine event and process data flows between the clients (16) in the control node (1) in the form of a control node process image, and the clients in the control node are configured to perform a zone mapping by exchanging data with the process image.