Electronic assembly for an automation system

Abstract

The invention relates to an electronic assembly (1) for an automation system for a technical installation, in particular a manufacturing or process installation, comprising: - at least one first terminal (2) for connecting the electronic assembly (1) to a field device (3) of the technical installation, - at least one second terminal (4a, 4b) for connecting the electronic assembly (1) to at least two automation components (5a, 5b) of the automation system, - a communication unit (6) which is designed to enable communication, based on the HART standard, between at least two automation components (5a, 5b) connected to the electronic assembly (1) at the second terminal (4a, 4b) and a field device (3) connected to the electronic assembly (1) at the first terminal (2). The electronic assembly (1) is characterised in that the communication unit (6) has a queue unit (8) and an identification unit and is designed - to receive and process in each case an initial request, based on the HART standard, from the two automation components (5a, 5b) and to forward same to the field device (3), - in response to further requests, based on the HART standard, of the two automation components (5a, 5b), said requests relating to their respective initial requests, to generate a response specific to the respective automation component (5a, 5b) and to transmit same, on the basis of the HART standard, to the relevant automation component (5a, 5b), wherein the identification unit is designed to read an identification of the respective automation component (5a, 5b) from the initial request thereof, and wherein the queue unit (8) is designed to temporarily store the initial requests together with the respective identification of the automation component (5a, 5b) in order to assign the response specific to the respective automation component (5a, 5b) to the relevant automation component (5a, 5b) on the basis of the stored identification.

Description

[0001] 202501735 Foreign version 05.02.2026

[0002] 1

[0003] Description

[0004] Electronic assembly for an automation system

[0005] The invention relates to an electronic assembly for an automation system. Furthermore, the invention relates to a control system for a technical plant, in particular a manufacturing or process plant. The invention also relates to a method for operating an electronic assembly for an automation system.

[0006] The HART fieldbus protocol is currently one of the most important in process automation. HART is a digital communication protocol based on a 4-20 mA current loop. The current value represents the primary process value. HART is also used for parameterization and monitoring of the field device. HART is a bidirectional communication protocol, but it only supports half-duplex operation and a data rate of 1.2 kBaud.

[0007] A HART field device cannot be directly connected to an automation system such as a programmable logic controller (PLC). Additional modules are required for this purpose, which transmit the analog current value as well as the HART communication via higher-level fieldbus protocols such as PROFIBUS DP or PROFINET (see https: / / www.profibus.com / download / hart-on-profibus-1).

[0008] Classic components in automation technology are the so-called remote I / O modules, such as the ET200 family from Siemens. The PROFIBUS User Organization (PNO) describes how HART is transmitted via higher-level protocols (HART on PROFIBUS, HART on PROFINET). The corresponding communication method is implemented in the relevant automation modules, such as the ET200 or the CFU from Siemens, as well as in the associated control system (e.g., SIMATIC PCS neo from Siemens) and corresponding engineering tools such as SIMATIC PDM from Siemens.

[0009] A request based on the HART standard is sent to a specific starting address, more precisely the index of the PROFIBUS or PROFINET address. The current processing status of the request and the response can be viewed on the 202501735 Foreign Version 05.02.2026

[0010] 2

[0011] The following index is queried. Typically, the starting address of the first channel of a HART module is index 80, and the query / polling address is index 81. The next channel accordingly has the corresponding communication index pair 82 and 83.

[0012] The indices used for HART communication are identical for all PROFINET communication participants. Simultaneous access, for example by engineering software and a programmable logic controller (PLC), leads to a communication conflict with known automation modules, as the modules cannot distinguish who is making the request. Known implementations are so-called "single-client solutions."

[0013] Current efforts in the process industry aim for parallel access to plant components such as field devices, as this is essential for comprehensive and precise operation and monitoring (the second data channel of the Namur Open Architecture, or NOA for short, is a key example here).

[0014] To access a HART channel of an I / O brewing unit, a client must check whether communication is already taking place by reading the query address (index 81 for channel 1). The status returned via the query address is encoded as follows:

[0015] Bits 0-2 Processing state

[0016] 0 = inactive

[0017] 1 = inactive (reserved)

[0018] 2 = waiting

[0019] 3 = waiting, executing

[0020] 4 = successful, with data

[0021] 5 = successful, without data

[0022] 6 = faulty, with data

[0023] 7 = faulty, no data

[0024] Bit 3 0 = Burst mode not active 202501735 Foreign version 05.02.2026

[0025] 3

[0026] Bit 4 0 = Response data comes directly

[0027] Bit 5 0 = Response data in transparent message format

[0028] Bit 6 0 = SHC mode not active

[0029] 1 = SHC mode active

[0030] Bit 7 0 = HART response

[0031] Only when no communication takes place (response bit 0-2 = 0) can it send its request (index 80 for channel 1). However, this procedure has three potential sources of error (in PROFINET):

[0032] 1. Despite adherence to the procedure, simultaneous access to the query register (index 80 for channel 1) may occur for multiple participants.

[0033] 2. In the case of high-cycle communication of the controller of a programmable logic controller (e.g., the SIMATIC S7-410 from Siemens), a second communication participant has no possibility of writing its request to the request register (index 80 for channel 1), because the underlying PROFINET protocol grants the controller primary access.

[0034] 3. Prioritized access by a controller without checking the response register overwrites the response of the second client without the client's knowledge. Any misinterpretation of the controller request response by the client can therefore lead to unforeseen errors.

[0035] Figure 1 illustrates an exemplary communication sequence according to the state of the art. An electronics module 1, for example an ET200 module from Siemens, is connected to a field device 3 via a first connection 2. The electronics module 1 is also connected to two automation components 5a and 5b via a second connection 4. The electronics module 1 can also be connected via a further connection 202501735 (foreign version 05.02.2026)

[0036] 4

[0037] The electronics assembly 1 also includes a communication unit 6, the functionality of which is explained in more detail in FIG 2. It features a connection for implementing a dedicated second data channel (particularly within the framework of the NAMUR Open Architecture Initiative, or NOA).

[0038] Figure 2 shows a flowchart of a communication procedure according to the prior art (chronologically from top to bottom). An automation component 5b, designated "2nd Client," acts as a PROFINET client and, in this context, sends an initial request ("HART Request A") based on the HART standard to an address indexed with 80 ("Index 80") of the communication unit 6 of the electronic assembly 1. From there, the initial request is forwarded to a processing unit 7 of the electronic assembly 1. This unit transmits an acknowledgment ("Ack") to the automation component 5b via "Index 80." The processing unit 7 also processes the initial request and, in the process, transmits a request "Request A" to the field device 3.

[0039] An automation component 5a, designated "S7-1500 Client," also functions as a PROFINET client and, in this context, sends an initial request ("HART Request B") based on the HART standard to the address indexed with 80 ("Index 80") of communication unit 6 of electronic module 1. This request "HART Request B" follows the request "HART Request A." From Index 80, the initial request is forwarded to processing unit 7 of electronic module 1. This unit transmits an acknowledgment ("Ack") to automation component 5a via "Index 80." Processing unit 7 then processes the initial request and, in the process, transmits a request "Request B" to field device 3.

[0040] This is followed by several "Request Response" queries regarding the processing of the initial requests by automation components 5a and 5b. These receive a "Busy" response from processing unit 7. After processing unit 7 receives the "Response B" response from field device 3 regarding the initial request "HART Request B," the "2nd Client" automation component 5b, which happened to be the first to send the next "Request Response" query, receives the response currently available in processing unit 7 containing the data for the initial request "HART Request B," labeled "Data B." However, this data is not a response to the initial request.

[0041] 5

[0042] The request “HART Request A” is suitable. Therefore, incorrect interpretations of the response received by the electronics assembly 1 to its initial request “HART Request A” by the “2nd Client” automation component 5b may occur.

[0043] Parallel access to the electronics assembly 1 or the associated field device 3 is currently only possible if certain boundary conditions (for example, maximum number of requests per minute, timeouts, maximum retry attempts) are painstakingly defined manually and adhered to by all communication participants (clients) through appropriate project planning / configuration.

[0044] EP 3355 139 A1 discloses a method for operating an automation system with at least one controller and with several field devices.

[0045] In DE 102023 119 157 A1 a system for operating at least one field device of automation technology by means of an operating tool is described.

[0046] US 2015 / 148918 A1 and 2015 / 1537171 A1 disclose devices with HART communication interfaces for outputting HART instructions to HART instruments.

[0047] Based on the previously explained state of the art, the task is therefore to design secure and reliable communication between field devices and automation components based on the HART standard, even with parallel access by several automation components.

[0048] This problem is solved by an electronic assembly for an automation system with the features of claim 1. Furthermore, the problem is solved by a control system for a technical plant, in particular a manufacturing or process plant, according to claim 5. The problem is also solved by a method for operating an electronic assembly for an automation system according to claim 8. Advantageous further developments are described in the dependent claims. 202501735 Foreign version 05.02.2026

[0049] 6

[0050] An electronic assembly according to the invention for an automation system for a technical plant, in particular a manufacturing or process plant, comprises the following components:

[0051] - at least one initial connection for linking the electronic assembly to a field device of the technical system;

[0052] - at least one second connection for connecting the electronic assembly to at least two automation components of the automation system;

[0053] - a communication unit designed to enable communication based on the HART standard between at least two automation components connected to the electronic assembly at the second terminal and a field device connected to the electronic assembly at the first terminal.

[0054] The electronic assembly is characterized by the fact that the communication unit is designed to

[0055] - to receive an initial request from each of the two automation components, based on the HART standard, and to process and forward it to the field device in a specific sequence, and

[0056] - in response to further requests from the two automation components based on the HART standard, which refer to their respective initial requests, to generate a response specific to the respective automation component and transmit it to the automation component in question based on the HART standard.

[0057] The HART standard refers to the standardized form of the HART protocol as defined in the IEC 61158 standard. Automation components are all parts of a device for automating a technical system that can send (communication) requests to field devices. Examples of automation components include programmable logic controllers (PLCs), servers, clients, or specialized applications running on general-purpose computers.

[0058] The inventive design of the electronic assembly enables efficient multi-client support for HART communication without requiring any changes to 202501735 Foreign version 05.02.2026

[0059] 7

[0060] Existing automation components or configuration software are not required. This significantly improves the flexibility and scalability of the automation system in which the electronic assembly can be used.

[0061] The electronics assembly implements a queueing unit to enable temporary storage of initial requests based on the HART standard, specifically along with the current processing status of these initial requests. This implementation takes place within the communication unit.

[0062] The implementation of the queueing unit enables orderly processing of requests and effectively prevents conflicts between simultaneous accesses by different automation components.

[0063] The electronics assembly also implements an identification unit that is designed to read an identification of the automation components from their initial requests in order to enable the generation and dispatch of the answer or answers specific to the respective automation component.

[0064] The identification unit enables precise assignment of requests and responses to the respective automation components, which increases the reliability and efficiency of communication.

[0065] The communication unit can be trained to process requests originating from the automation components and / or the field device sequentially.

[0066] The sequential processing of requests ensures consistent and predictable handling of communication tasks, which improves the stability of the system.

[0067] The communication unit can be configured to process and forward the initial requests from the automation components based on a prioritization assigned to those components. 202501735 Foreign version 05.02.2026

[0068] 8

[0069] Prioritizing requests enables optimized resource utilization and faster response to critical requests, which improves the overall performance of the automation system.

[0070] The communication unit can be designed to communicate with the automation components based on the PROFINET or PROFI BUS standard.

[0071] Support for common industry standards such as PROFINET or PROFIBUS increases the compatibility and integrability of the electronic assembly into existing automation environments.

[0072] The task is also solved by a control system for a technical plant, in particular a manufacturing or process plant, which comprises at least two automation components, an electronic assembly configured as described above, and a field device. The automation components are connected to the electronic assembly via the second connection, and the field device via the first connection, to enable communication between the automation components and the field device.

[0073] The technical installation can be a plant from the process industry, such as a chemical, pharmaceutical, petrochemical, or food and beverage plant. This also includes any plant from the manufacturing industry, such as factories where cars or goods of all kinds are produced. Technical installations suitable for carrying out the process according to the invention can also originate from the energy generation sector. Wind turbines, solar power plants, or power plants for energy generation are likewise included in the term "technical installation."

[0074] In this context, a control system is understood to be a computer-aided, technical system that includes functionalities for displaying, operating, and controlling the process plant. The control system can also include sensors for determining measured values ​​as well as various actuators. Furthermore, the control system can include so-called process- or production-related components that are used for control.

[0075] 9

[0076] The control system serves as a control unit for actuators and sensors. Furthermore, it can include, among other things, tools for visualizing the process plant and for engineering purposes. Optionally, the control system can also include additional computing units for more complex control systems and systems for data storage and processing.

[0077] An automation component can be a programmable logic controller (PLC) for executing an automation program. Integrating PLCs as automation components enables flexible and efficient control of the automation system using multi-client HART communication.

[0078] However, it is also possible, for example, that an automation component represents a computing unit for operation and monitoring, a so-called "Operator Station Server." In this context, such a server is understood to be a server that centrally collects data from an operator and monitoring system, as well as, typically, alarm and measurement data archives from a control system of a technical plant, and makes this data available to users. The Operator Station Server usually establishes a communication link to the automation systems of the technical plant and forwards data from the technical plant to so-called Operator Station Clients for visualization. These clients are used to operate and monitor the operation of the individual functional elements of the technical plant. The Operator Station Server can have client functions to access the data (archives, messages, tags, variables) of other Operator Station Servers.

[0079] This allows images of the operation of the technical system on the Operator Station Server to be combined with variables from other Operator Station Servers (server-to-server communication). The Operator Station Server can be, but is not limited to, a SIMATIC PCS 7 Industrial Workstation Server from Siemens.

[0080] An operator of the technical system can access the Operator Station Server via the Operator Station Client, which can be, for example, a tablet, a smartphone, a personal computer, or similar device, for the purpose of operating and monitoring the technical system. 202501735 Foreign version 05.02.2026

[0081] 10

[0082] The field device can be a sensor, an actuator, or a transmitter. Support for various field device types increases the application versatility of the control system and enables comprehensive monitoring and control of the technical plant.

[0083] The task is also solved by a method for operating an electronic assembly for an automation system, comprising the electronic assembly:

[0084] - at least one initial connection for linking the electronic assembly to a field device of the technical system

[0085] - at least one second connection for connecting the electronic assembly to at least two automation components of the automation system,

[0086] - a communication unit designed to enable communication based on the HART standard between at least two automation components connected to the electronic assembly at the second terminal and a field device connected to the electronic assembly at the first terminal, the method comprising the following steps:

[0087] a) Directing an initial request to the communication unit based on the HART standard by a first automation component of the automation system

[0088] b) Directing a second initial request to the communication unit based on the HART standard by a second automation component of the automation system,

[0089] c) In a specific sequence, the communication unit processes the two initial requests and forwards them to the field device,

[0090] d) Reading an identification of the respective automation component from its initial request by the identification unit and temporarily storing the initial requests together with the respective identification in the queue unit; e) In response to one or more further requests from the two automation components, based on the HART standard and directed to the communication unit and relating to their respective initial requests, generating one or more responses specific to the respective automation component and transmitting the specific response(s), based on the HART standard, to the automation component(s) in question. 202501735 Foreign version 05.02.2026

[0091] 11

[0092] This method enables efficient and orderly processing of multiple client HART requests, improving communication efficiency and system performance in complex automation environments.

[0093] The properties, features and advantages of this invention described above, as well as the manner in which they are achieved, will become clearer and more easily understood in connection with the following description of an exemplary embodiment, which is explained in more detail in connection with FIG 3 and FIG 4.

[0094] Figure 3 shows the topological structure of a control system 9. In this example, the control system 9 is used to operate and monitor an automated process plant. At process control level A, the control system 9 comprises an operator station server 10, two operator station clients 11a and 11b, a web-based operator station client 12, an engineering station server 13, and an archive server 14. The aforementioned components of process control level A of the control system 9 are connected to each other and to other possible components of the control system 9 (not shown in Figure 3) via a terminal bus 15. The terminal bus 15 can, but is not limited to, use Ethernet for communication.

[0095] The Operator Station Server 10 includes, among other things, a visualization service and a process image. The visualization service integrated into the Operator Station Server 10 initiates the transmission of visualization information to the Operator Station Clients 11a, 11b, and the web-based Operator Station Client 12. The Operator Station Clients 11a, 11b, and the web-based Operator Station Client 12 are configured to display a visualization, i.e., a graphical representation, particularly of plant images, for operating and monitoring the process plant.

[0096] As indicated in FIG. 3, the Operator Station Server 10 can have multiple server units capable of handling different tasks. It is also possible for them to be configured for redundant operation, handling the same tasks in parallel. 202501735 Foreign version 05.02.2026

[0097] 12

[0098] The Operator Station Server 10 has a device interface that is connected to a plant bus 16. Via this device interface and the plant bus 16, the Operator Station Server 10 is connected to and can communicate with two automation components configured as automation devices 5a and 18. The plant bus 16 can, but is not limited to, use Industrial Ethernet, in particular PROFINET, for communication.

[0099] Automation devices 5a and 18 can, for example, be programmable logic controllers (PLCs) running a pre-programmed automation program to control / regulate subordinate process components. Automation devices 5a and 18 acquire data from various input devices, such as sensors, switches, and pushbuttons 3 of the process plant. This input data is then processed in automation devices 5a and 5b to generate corresponding control commands. After processing, automation devices 5a and 18 transmit the control commands to various output devices 3, such as motors, valves, lights, and other actuators, to execute the desired actions in the process plant. Automation devices 5a and 5b are assigned to control level B of the supervisory control system 9.

[0100] Automation devices 5a and 18 are each connected via a bus 17a and 17b to electronic modules 1a, 1b, 1c, 1d, 1e, and 1f. Buses 17a and 17b can use PROFINET or PROFIBUS DP for communication. Electronic modules 1a, 1b, 1c, 1d, 1e, and 1f are each connected to sensors and / or actuators 3 of the process plant. This connection is based, for example, on the 4-20 mA current loop in conjunction with the HART standard. Electronic modules 1a, 1b, 1c, 1d, 1e, and 1f, as well as sensors and actuators 3, are assigned to field level C of the control system 9. Furthermore, in FIG. 3, part of the electronic assemblies 1a, 1b, 1c are connected via bus 17a to an automation component 5b, which is designed as a so-called "edge device". This collects data from the electronic assemblies 1a, 1b, 1c (and processes it if necessary) and sends the data via a data center 19 of the control system 9 to a client 20, which is accessible via the Internet.Conversely, the Edge Device 5b can transmit data and requests to the electronic assemblies 1a, 1b, and 1c. 202501735 Foreign version 05.02.2026.

[0101] 13

[0102] While FIG. 3 generally illustrates the topological arrangement of the electronic assemblies 1a, 1b, 1c, 1d, 1e, 1f within the control system 9, FIG. 4 refers specifically to the structure of a combination of automation components 5a, 5b, an electronic assembly 1 (as also shown in FIG. 3), and a field device 3, as explained above with reference to FIG. 1. Extending the communication unit 6, as used by the electronic assembly 1 described with reference to FIG. 2 according to the prior art, the communication unit 6 according to the embodiment of the invention in FIG. 4 additionally includes a queueing unit 8. The queueing unit 8 could also be implemented outside the communication unit 6, for example, in an I / O unit (not shown) of the electronic assembly 1.

[0103] Figure 4 shows a flowchart of a communication method according to the invention (from top to bottom in chronological order). Analogous to Figure 2, an automation component 5b, designated "2nd Client," acts as a PROFINET client and, in this capacity, sends an initial request ("HART Request A") based on the HART standard to an address indexed with 80 ("Index 80") of the communication unit 6 of the electronic assembly 1. From there, the initial request is first forwarded to the queue unit 8 and stored there. As part of the initial request from the 2nd Client 5b, which in this case uses the PROFINET protocol ("HART on PROFINET"), an identification unit of the communication unit 6 determines an identification of the automation component 5b ("2nd Client") and stores the identification together with the initial request ("HART Request A") in the queue unit 8.

[0104] In this case, the initial request from automation component 5b is the first request stored in queue unit 8. It can therefore be immediately forwarded to processing unit 7 for further processing. Communication unit 6 can also derive a prioritization of requests from the communication relationships defined in PROFINET (here between automation component 5b and electronic assembly 1) and, based on this (theoretically, not shown in FIG. 3), prioritize the processing of specific requests. 202501735 Foreign version 05.02.2026

[0105] 14

[0106] In response to the initial request “HART Request A”, queue unit 8 of automation component 5b transmits an acknowledgment (“Ack”) via “Index 80”. Additionally, processing unit 7 processes the initial request and, in the process, transmits a request “Request A” to field device 3.

[0107] An automation component 5a, designated "S7-1500 Client," also functions as a PROFINET client and, in this context, sends an initial request based on the HART standard ("HART Request B") via "PROFINET on HART" to the address indexed with 80 ("Index 80") of communication unit 6 of electronic module 1. This request, "HART Request B," follows the request "HART Request A." From Index 80, the initial request is forwarded to the queue unit 8 of electronic module 1. This unit transmits an acknowledgment ("Ack") to automation component 5a via "Index 80." No further processing of the second initial request, "HART Request B," occurs at this time because queue unit 8 has not yet received confirmation from field device 3 that it has already processed the first initial request, "HART Request A."Therefore, there are no multiple overlapping requests to field device 3.

[0108] This is followed by a “Request Response” regarding the processing of the initial request “HART Request A” by the automation component 5b. This and all subsequent requests shown in FIG 3 are directed to the address indexed with 81 (“Index 81”) of the communication unit 6 of the electronic assembly 1.

[0109] Queue unit 8 can specifically assign the demand to automation component 5b because it knows an identification from the initial request "HART Request A". Automation component 5b receives the message "Busy" as a response from queue unit 8. After queue unit 8 receives the response "Response A" from field device 3 regarding the initial request "HART Request A", it creates "Data A" in queue unit 8 and forwards the second initial request "HART Request B" to field device 3 via processing unit 7. This process is based on two consecutive requests ("Request Response") regarding the 202501735 foreign version 05.02.2026

[0110] 15

[0111] When the automation component 5a processes the initial request “HART Request B”, it receives the message “Busy” as a response from the queue unit 8.

[0112] Upon a subsequent request “Request Response” regarding the processing of the initial request “HART Request A” by the automation component 5b, it receives a response from the queue unit 8 containing the “Data A” specific to the initial request “HART Request A”.

[0113] The field device has now processed the request "Request B" and transmitted the "Data B" to queue unit 8 in a corresponding response "Response B". Upon a subsequent inquiry "Request Response" regarding the processing of the initial request "HART Request B" by automation component 5a, the queue unit receives a response containing the "Data B" specific to the initial request "HART Request B".

[0114] Regardless of the method used to forward requests to the connected field device 3, a significant advantage of the electronic assembly according to the invention lies in the fact that native "multi-client" support can be implemented without any impact on the automation components 5a and 5b through specific responses. The automation components 5a and 5b do not need to be modified.

[0115] Although the invention has been illustrated and described in detail by the preferred embodiment, the invention is not limited by the disclosed examples and other variations can be derived by the person skilled in the art without leaving the scope of protection of the invention.

Claims

202501735 Foreign version 05.02.2026 16 Patent claims 1. Electronic assembly (1) for an automation system for a technical plant, in particular a manufacturing or process plant, comprising: - at least one first connection (2) for connecting the electronic assembly (1) to a field device (3) of the technical system, - at least one second connection (4a, 4b) for connecting the electronic assembly (1) to at least two automation components (5a, 5b) of the automation system, - a communication unit (6) designed to enable communication based on the HART standard between at least two automation components (5a, 5b) connected to the electronic assembly (1) at the second terminal (4a, 4b) and a field device (3) connected to the electronic assembly (1) at the first terminal (2), characterized by the fact that the communication unit (6) comprises a queuing unit (8) and an identification unit and is designed to to receive and process an initial HART-based request from each of the two automation components (5a, 5b) and forward it to the field device (3), - in response to further HART-based requests from the two automation components (5a, 5b) relating to their respective initial requests, to generate a response specific to each automation component (5a, 5b) and transmit it to the relevant automation component (5a, 5b) based on the HART standard, wherein the identification unit is configured to read an identification of the respective automation component (5a, 5b) from its initial request, and wherein the queueing unit (8) is configured to temporarily store the initial requests together with the respective identification of the automation component (5a, 5b) in order to retrieve the information required for the respective automation component (5a, 5b) 202501735 Foreign version 05.02.2026 17 to assign a specific answer based on the stored identification of the relevant automation component (5a, 5b).

2. Electronic assembly (1) according to claim 1, wherein the communication unit (6) is configured to sequentially process requests originating from the automation components (5a, 5b) and / or the field device (3).

3. Electronic assembly (1) according to one of the preceding claims, wherein the communication unit (6) is configured to process and forward the initial requests of the automation components (5a, 5b) based on a prioritization assigned to the automation components (5a, 5b).

4. Electronic assembly (1) according to one of the preceding claims, wherein the communication unit (6) is configured to perform communication with the automation components (5a, 5b) on the basis of the PROFINET or PROFI BUS standard.

5. Control system for a technical plant, in particular a manufacturing or process plant, comprising at least two automation components (5a, 5b), an electronic assembly (1) according to one of claims 1 to 4 and a field device (3), wherein the automation components (5a, 5b) are connected to the electronic assembly (1) via the second connection (4) and the field device (3) via the first connection (2) in order to enable a communication link between the automation components (5a, 5b) and the field device (3).

6. Control system according to claim 5, wherein at least one of the automation components (5a, 5b) is a programmable logic controller (PLC).

7. Control system according to claim 5 or 6, wherein the field device (3) is a sensor, an actuator or a transmitter. 202501735 Foreign version 05.02.2026 18 8. Method for operating an electronic assembly (1) for an automation system comprising the electronic assembly (1): - at least one first connection (2) for connecting the electronic assembly (1) to a field device (3) of the technical system - at least one second connection (4a, 4b) for connecting the electronic assembly (1) to at least two automation components (5a, 5b) of the automation system, - a communication unit (6) comprising a queueing unit (8) and an identification unit, wherein the communication unit (6) is configured to enable communication based on the HART standard between at least two automation components (5a, 5b) connected to the electronic assembly (1) at the second terminal and a field device (3) connected to the electronic assembly (1) at the first terminal (2), the procedure includes the following steps: f) Directing a first initial request based on the HART standard to the communication unit (6) by a first automation component (5b) of the automation system g) Directing a second initial request based on the HART standard to the communication unit (6) by a second automation component (5a) of the automation system, h) Reading an identification of the respective automation component (5a, 5b) from its initial request by the identification unit and temporarily storing the initial requests together with the respective identification in the queue unit (8), i) Processing of the two initial requests and forwarding to the field device (3) by the communication unit (5), j) In response to one or more further requests from the two automation components (5a, 5b) to the communication unit, based on the HART standard and referring to their respective initial requests, generate and transmit a response specific to each automation component (5a, 5b) based on the identification stored in the queue unit (8), based on the HART standard. 202501735 Foreign version 05.02.2026 19 Answer or answers to the relevant automation component (5a, 5b) or automation components (5a, 5b).

Images