Weighting of requests to an electronics assembly

Abstract

The invention relates to an electronics assembly (13a, 13b, 13c, 14a, 14b, 14c) for an automation system for a technical plant, in particular a manufacturing or processing plant, having: - at least one first connection (15) for connecting the electronics assembly (13a, 13b, 13c, 14a, 14b, 14c) to a field device (10, 11) of the technical plant, - at least one second connection (16) for connecting the electronics assembly (13a, 13b, 13c, 14a, 14b, 14c) to automation components (5a, 5b) of the automation system, - a communication unit (17) designed to enable communication, in particular based on the HART standard, between automation components (9a, 9b) connected to the second connection (16) via the electronics assembly (13a, 13b, 13c, 14a, 14b, 14c) and a field device (10, 11) connected to the first connection (15) via the electronics assembly (13a, 13b, 13c, 14a, 14b, 14c). The electronics assembly (13a, 13b, 13c, 14a, 14b, 14c) is characterised in that the communication unit (17) is designed to receive requests, in particular based on the HART standard, from the automation components (9a, 9b) to store them in a queue unit (18) of the electronics assembly (13a, 13b, 13c, 14a, 14b, 14c) and to forward them, in accordance with a sequence weighting, from the queue unit (18) to the field device (10, 11), wherein the sequence weighting for forwarding the requests to the field device (10, 11) depends on a respective priority weighting assigned to the automation components (9a, 9b) and a time weighting of the requests.

Description

[0001] 202501734 Foreign version 06.02.2026

[0002] 1

[0003] Description

[0004] Weighting of requests to an electronic assembly

[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] The combination of PROFINET and HART in industrial networks presents several challenges. A significant problem is the considerable speed difference. (202501734 Foreign version 06.02.2026)

[0010] 2

[0011] Difference between the two protocols. While PROFINET supports high data rates, HART operates at a comparatively low baud rate of 1200 bits / s. This discrepancy can lead to delays and bottlenecks in communication, especially when multiple PROFINET clients want to access HART devices simultaneously.

[0012] Another problem arises from the different priority levels defined in PROFINET communication relationships. Controller application relationships typically have the highest priority, followed by supervisor application relationships and device application relationships. When processing requests to HART devices via a remote I / O module, these priorities must be considered to ensure fair and efficient resource allocation. A simple first-in-first-out (FIFO) processing of requests would disregard these priorities and could lead to suboptimal system performance.

[0013] DE 102015219608 A1 describes a method for prioritizing communication requests in an industrial control system.

[0014] EP 3506052 A1 discloses the processing of messages in a fieldbus system taking into account different priorities.

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

[0016] 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.

[0017] US Patent 2010 / 205340 A1 discloses a method for determining the transmission priority of requests based on the content of the request and for transmitting the request according to this transmission priority using a fieldbus communication framework.

[0018] In DE 102021 123541 A1, a process control or factory automation field device with an interface and communication connection structure is disclosed, with which es202501734 foreign version 06.02.2026

[0019] 3

[0020] The field device is enabled to operate as a data server that communicates directly or indirectly with and supports multiple different applications or clients, while simultaneously performing standard process and factory automation control functions.

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

[0022] This problem is solved by an electronic assembly for an automation system having 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 10. The problem is also solved by a method for operating an electronic assembly for an automation system according to claim 11. Advantageous embodiments are described in the dependent claims.

[0023] 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:

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

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

[0026] - a communication unit designed to enable communication, in particular based on the HART standard, between (at least two) automation components connected to the second terminal of the electronic assembly and a field device connected to the first terminal of the electronic assembly.

[0027] The electronic assembly is characterized in that the communication unit is designed to receive requests from the automation components, particularly those based on the HART standard, to store them in a queue unit of the electronic assembly, and to process them according to a sequence weighting from 202501734 Foreign version 06.02.2026

[0028] 4

[0029] to forward the queue unit to the field device, whereby the sequence weighting for forwarding the requests to the field device depends on a respective priority weighting assigned to the automation components and a time weighting of the requests.

[0030] The HART standard refers to the standardized form of the HART protocol as it is part of the IEC 61158 standard.

[0031] The inventive design of the electronic assembly enables efficient and prioritized processing of (HART) requests from various automation components, leading to improved communication and control in the technical system.

[0032] The priority weighting assigned to each automation component can depend on a communication relationship between the respective automation component and the electronic assembly, in particular on the type of communication relationship.

[0033] This prioritization based on the communication relationship ensures that critical requests from important automation components are given preferential treatment, thereby improving the overall performance and reliability of the system.

[0034] A high priority weight can be assigned to the respective automation component if the automation assembly is a programmable logic controller (PLC), a medium priority weight can be assigned to the respective automation component if the automation component is parameterization software, and a low priority weight can be assigned to the respective automation component if the automation component is another, equally ranked electronic assembly.

[0035] This differentiated prioritization enables optimal resource utilization by ensuring that critical control tasks take precedence over less time-critical ones. 202501734 Foreign version 06.02.2026

[0036] 5

[0037] Parameterization tasks are performed while simultaneously managing communication between components of equal rank efficiently.

[0038] Preferably, the order weighting at the time of depositing a request in the queue unit corresponds to the priority weighting.

[0039] This initial weighting based on priority ensures that important requests have a higher chance of being processed quickly from the outset, thus improving the system's response time for critical tasks.

[0040] The communication unit can be trained to forward to the field device, at a specific time, the request stored in the queue unit that has the highest sequence weighting at that specific time.

[0041] This functionality optimizes the use of communication resources by ensuring that the most important request is sent as soon as the field device is ready, thus increasing communication efficiency and system responsiveness.

[0042] Optionally, the communication unit can forward the request only if the field device has signaled its readiness to receive a request before the specified time. This signaling can be initiated actively by the field device. However, it is also possible that the communication unit itself has queried the field device's readiness as part of a (cyclical) polling process.

[0043] In an advantageous further development of the invention, the communication unit is configured to forward to the field device, in the event that two or more requests in the queue unit have an identical sequence weighting at the given time, the request stored in the queue unit that has the highest priority weighting.

[0044] In other words, the communication unit identifies the request with the highest priority based on its communication relationship with the electronics assembly. 202501734 Foreign version 06.02.2026

[0045] 6

[0046] In an advantageous further development of the invention, the communication unit is configured to forward to the field device, in the event that two or more requests in the queue unit have an identical sequence weighting and an identical priority weighting at the specified time, the request stored in the queue unit which was received earliest by the communication unit.

[0047] In other words, the communication unit identifies the request that has been in the queue the longest in this case. It is irrelevant how the queue is structured internally (e.g., as a linked list of requests or as requests with a timestamp indicating their receipt in the communication unit) – the communication unit only needs to be able to identify the earliest / oldest request in order to forward it to the field device for processing.

[0048] This regulation ensures that requests with the same priority are handled unambiguously and prevents older requests from remaining in the queue indefinitely, thus improving the overall performance of the electronics assembly.

[0049] The communication unit can be trained to remove the request from the queue unit after forwarding it to the field device.

[0050] Removing processed requests optimizes storage requirements and simplifies queue management, leading to more efficient resource utilization.

[0051] Preferably, the communication unit is designed to communicate with the automation components based on the PROFINET or PROFI BUS standard.

[0052] Support for common industry standards such as PROFINET or PROFIBUS increases the compatibility and flexibility of the electronic assembly, facilitating its integration into various automation environments. 202501734 Foreign version 06.02.2026

[0053] 7

[0054] The previously described task is also solved by a control system for a technical plant, in particular a manufacturing or process plant. The control system comprises at least two automation components, an electronic assembly according to one of the previous aspects, and a field device, wherein the automation components are connected to the electronic assembly via the second connection, and the field device via the first connection, in order to enable a communication link between the automation components and the field device.

[0055] This training of a control system enables seamless integration of various automation components and field devices, leading to improved overall performance and controllability of the technical system.

[0056] 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."

[0057] In this context, a control system is understood to be a computer-aided, technical system that includes functionalities for representing, operating, and controlling a technical manufacturing or production plant. The control system can include sensors for determining measured values ​​as well as various actuators. Furthermore, the control system can include so-called process- or production-related components, such as the electronic assembly, which serves to control the actuators or sensors. In addition, the control system can include, among other things, means for visualizing the technical plant and for engineering purposes. The term control system also encompasses additional computing units for more complex control systems and systems for data storage and processing. 202501734 Foreign version 06.02.2026

[0058] 8

[0059] At least one of the automation components may be a programmable logic controller (PLC).

[0060] The integration of PLCs as automation components enables flexible and efficient control of the automation system using multi-client (HART) communication.

[0061] 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.

[0062] 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.

[0063] 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 the like, for the purpose of operating and monitoring the technical system.

[0064] 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. 202501734 Foreign version 06.02.2026

[0065] 9

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

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

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

[0069] - a communication unit designed to enable communication, in particular based on the HART standard, between automation components connected to the second port of the electronic assembly and a field device connected to the first port of the electronic assembly, - a queuing unit,

[0070] the procedure includes the following steps:

[0071] a) Directing requests, particularly those based on the HART standard, to the communication unit by automation components of the automation system,

[0072] b) Storing the requests in the queue unit,

[0073] c) Forwarding the requests to the field device according to a sequence weighting, wherein the sequence weighting for forwarding the requests to the field device depends on a respective priority weighting assigned to the automation components and a time weighting of the requests.

[0074] This process enables efficient management and prioritization of requests, leading to improved overall performance of the automation system.

[0075] If the field device has signaled its readiness to receive a request before a certain time, the communication unit can forward the request stored in the queue unit to the field device at that specific time, provided that the request has the highest sequence weighting at that specific time.

[0076] This functionality optimizes communication with the field device by ensuring that the most important requests are processed first when the field device is ready. 202501734 Foreign version 06.02.2026

[0077] 10

[0078] In the event that two or more requests in the queue unit have an identical order weighting at the given time, the communication unit can forward the request stored in the queue unit to the field device that has the highest priority weighting at that given time.

[0079] In the event that two or more requests in the queue unit have identical sequence weighting and identical priority weighting at the specified time, the communication unit can forward to the field device the request stored in the queue unit that was received earliest by the communication unit at that specified time.

[0080] This method ensures fair treatment of requests with equal priority and prevents older requests from being overlooked.

[0081] After forwarding the request to the field device, the communication unit can remove the request in question from the queue unit.

[0082] Removing processed requests from the queue keeps it up-to-date and efficient, leading to improved management of system resources.

[0083] 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 readily understandable in connection with the following description of an exemplary embodiment, which is explained in more detail in conjunction with the figures. These show:

[0084] FIG 1 shows a guidance system in a topological schematic diagram;

[0085] FIG 2 shows an electronic assembly in a structural schematic; and

[0086] FIG 3 a tabular flow of handling requests to an electronic assembly 202501734 Foreign version 06.02.2026

[0087] 11

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

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

[0090] As indicated in FIG 1, the Operator Station Server 2 can have multiple server units that can handle different tasks. It is also possible for them to be designed for redundant operation – and thus handle the same tasks in parallel.

[0091] The Operator Station Server 2 has a device interface that is connected to a plant bus 8. Via this device interface and the plant bus 8, the Operator Station Server 2 is connected to two automation devices 9a and 19 and can communicate with them. The plant bus 8 can, but is not limited to, use Industrial Ethernet, in particular PROFINET, for communication.

[0092] Automation devices 9a and 19 can, for example, be programmable logic controllers (PLCs) running a pre-programmed automation program to control / regulate subordinate process components. Automation devices 9a and 19 acquire data from various input devices. 202501734 Foreign version 06.02.2026

[0093] 12

[0094] such as sensors, switches, and pushbuttons 10, 11 of the process plant. This input data is then processed in the automation devices 9a, 19 to generate corresponding control commands. After processing, the automation devices 9a, 19 transmit the control commands to various output devices 10, 11, such as motors, valves, lights, and other actuators, to execute the desired actions in the process plant. The automation devices 9a, 19 are assigned to control level B of the control system 1.

[0095] Automation devices 9a and 19 are each connected via a bus 12a and 12b to electronic modules 13a, 13b, 13c, 14a, 14b, and 14c. Buses 12a and 12b can use PROFINET or PROFIBUS DP for communication. Electronic modules 13a, 13b, 13c, 14a, 14b, and 14c are each connected to sensors and / or actuators 10 and 11 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 13a, 13b, 13c, 14a, 14b, and 14c, as well as sensors and actuators 10 and 11, are assigned to field level C of the control system 1.

[0096] Furthermore, in FIG. 1, some of the electronic assemblies 13a, 13b, 13c are connected via bus 12a to an automation component 9b, which is designed as a so-called "edge device". This collects data from the electronic assemblies 13a, 13b, 13c (and processes it if necessary) and sends the data via a data center 20 of the control system 1 to a client 21, which is accessible via the internet. In the reverse direction, the edge device 9b can transmit data and requests to the electronic assemblies 13a, 13b, 13c.

[0097] FIG 2 refers to the configuration of a combination consisting of one of the automation devices 9a, the Operator Station Server 2, one of the electronic assemblies 13a, and two field devices 10a, 10b (sensors, actuators, etc.), as explained above with reference to FIG 1. The electronic assembly 13a (the other electronic assemblies 13b, 13c, 14a, 14b, 14c can be configured analogously) includes a communication unit 17 and a queuing unit 18. 202501734 Foreign version 06.02.2026

[0098] 13

[0099] The electronics assembly 13a also has a first connector 15 for connecting the electronics assembly 13a to the two field devices 10a, 10b and a second connector 16 for connecting the electronics assembly 13a to the automation device 9a or the operator station server 2 and to the automation component 9b, which is configured as an edge device. The communication unit 17 is configured to enable communication based on the HART standard between the automation components (9a, 9b) connected to the electronics assembly 13a at the second connector 4 and the field devices 10a, 10b connected to the electronics assembly 13a at the first connector 15.

[0100] The communication unit 17 receives requests from the automation components 9a and 9b for the field devices 10a and 10b and initially stores these requests in the queue unit 18. The requests are then forwarded from the queue unit 18 to the field devices 10a and 10b according to a sequence weighting. This sequence weighting for forwarding the requests to the field device depends on a priority weight assigned to each automation component and a time weighting of the requests. The precise determination of this sequence weighting is explained in more detail using the following embodiment and the tabular list of various requests and their processing shown in FIG. 3.

[0101] At the first time point (Cycle = 0), an initial request (Request 1) is received from the automation device 9a by the electronics assembly 13a and stored in queue unit 18. The communication relationship (AR-Type) between the automation device 9a, which is configured as a programmable logic controller (PLC), and the electronics assembly 13a is of the type "Controller" according to the PROFINET specification, which is why this request is assigned a high priority weight of 3 (Prio = 3). The sequence weight (Leveling) corresponds to the priority weight at the time the request is stored in queue unit 18, which is why the sequence weight has the value 3. The time weight (Time) is 0. The position of the request (Request 1) from the automation device 9a in queue unit 18 (Queue Pos) is 1, since no further requests are stored in queue unit 18.The execution position of the request is also 1. Initially, the first request (Request 1) is in the "Wait" status, i.e., it is waiting to be processed by the electronics assembly 13a.202501734 Foreign version 06.02.2026.

[0102] 14

[0103] One cycle later, at a second point in time (Cycle = 1), electronics assembly 13a receives a second request (Request 2) from automation component 9b, which is configured as an edge device, and also places this request in queue unit 18. Its position in the queue is 2, as it was placed in queue unit 18 after the first request. This second request is assigned the type "Device" because automation component 9b is assumed to be an equal communication partner. Therefore, the second request is assigned the low priority weight of 1.

[0104] The first request from automation device 9a (Request 1) is processed at the second time by electronics assembly 13a (status “Execute”), which means that the request is forwarded to the relevant field device(s) 10a, 10b and their response is awaited.

[0105] One cycle later for electronics module 9a, i.e., at a third point in time (Cycle / Cycle = 2), electronics module 9a receives a third request (Request 3) from Operator Station Server 2 or an application implemented on it and also places this request in queue unit 18. This third request is assigned the type "Supervisor" because Operator Station Server 2 or the application implemented on it is parameterization software. Therefore, the third request is assigned a medium priority weight of 2.

[0106] The first request (Request 1) is still being processed and therefore has the status "Execute". The second request (Request 2) must continue to wait for processing and receives a time weight of +1 based on the time that has elapsed since its receipt in electronics assembly 13a (duration: 1). This time weight increases the leveling weight (priority weight 1 + time weight 1) of the second request to the value 2.

[0107] It can be seen that both the second request (Request 2) and the third request (Request 3) each have a sequence weighting at the third time point (Cycle = 2). 202501734 Foreign version 06.02.2026

[0108] 15

[0109] The third request (Request 3) is placed in position 2 (Execute Pos = 2) for subsequent processing, while the second request (Request 2) is placed in position 3. This is because, with identical order weighting, the third request has a higher priority weight.

[0110] One cycle of electronics assembly 13a later, i.e., at a fourth point in time (Cycle = 3), the processing of the first request is completed and its status is now "Done". Due to its priority processing position, the third request is now being processed (Status = "Execute").

[0111] After the first request is forwarded and processed, this request is removed from queue unit 18, which can be seen at a fifth point in time (Cycle / Cycle = 4).

[0112] One cycle of electronics assembly 13a later, at the sixth time point (Cycle = 5), the third request (Request 3) was processed. Although a fourth request (Request 4) from a communication participant of type "Device" and a fifth request from a communication participant of type "Controller" had been received in the meantime, and the fifth request had a high priority weight of 3, at this sixth time point the second request (Request 2) from a communication participant of type "Device" with the low priority weight of 1 was processed. The reason for this is that the second request, due to its long "waiting time" and the associated high time weighting, has a sequence weight of 5.

[0113] 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

202501734 Foreign version 06.02.2026 16 Patent claims 1. Electronic assembly (13a, 13b, 13c, 14a, 14b, 14c) for an automation system for a technical plant, in particular a manufacturing or process plant, comprising: - at least one first connection (15) for connecting the electronic assembly (13a, 13b, 13c, 14a, 14b, 14c) to a field device (10, 11) of the technical system, - at least one second connection (16) for connecting the electronic assembly (13a, 13b, 13c, 14a, 14b, 14c) to automation components (9a, 9b) of the automation system, - a communication unit (17) designed to enable communication, in particular based on the HART standard, between automation components (9a, 9b) connected to the electronic assembly (13a, 13b, 13c, 14a, 14b, 14c) at the second terminal (16) and a field device (10, 11) connected to the electronic assembly (13a, 13b, 13c, 14a, 14b, 14c) at the first terminal (15), characterized by the fact that the communication unit (17) is designed to receive requests from the automation components (9a, 9b), in particular requests based on the HART standard, to store them in a queue unit (18) of the electronic assembly (13a, 13b, 13c, 14a, 14b, 14c) and to forward them from the queue unit (18) to the field device (10, 11) according to a sequence weighting, wherein the sequence weighting for forwarding the requests to the field device (10, 11) depends on a respective priority weighting assigned to the automation components (9a, 9b) and a time weighting of the requests.

2. Electronic assembly (13a, 13b, 13c, 14a, 14b, 14c) according to claim 1, wherein the priority weighting assigned to each automation component (9a, 9b) depends on a communication relationship between the respective automation component (9a, 9b) and the electronic assembly (13a, 13b, 13c, 14a, 14b, 14c), in particular on a type of communication relationship. 202501734 Foreign version 06.02.2026 17 3. Electronic assembly (13a, 13b, 13c, 14a, 14b, 14c) according to claim 2, wherein the respective automation component (9a, 9b) is assigned a high priority weighting if the automation component (9a, 9b) is a programmable logic controller, and wherein the respective automation component (9a, 9b) is assigned a medium priority weighting if the automation component (9a, 9b) is parameterization software, and wherein the respective automation component (9a, 9b) is assigned a low priority weighting if the automation component (9a, 9b) is another assembly of equal rank, in particular an electronic assembly (13a, 13b, 13c, 14a, 14b, 14c).

4. Electronic assembly (13a, 13b, 13c, 14a, 14b, 14c) according to any of the preceding claims, wherein the sequence weighting at a time of depositing a request in the queue unit (18) corresponds to the priority weighting.

5. Electronic assembly (13a, 13b, 13c, 14a, 14b, 14c) according to one of the preceding claims, wherein the communication unit is configured to forward, in the event that the field device (10, 11) has signaled its readiness to receive a request before a certain time, the request stored in the queue unit (18) to the field device (10, 11) at that certain time which has the highest sequence weighting at that certain time.

6. Electronic assembly (13a, 13b, 13c, 14a, 14b, 14c) according to claim 5, wherein the communication unit (17) is configured to forward, in the event that two or more requests in the queue unit (18) have an identical sequence weighting at the specified time, the request stored in the queue unit (18) which has the highest priority weighting to the field device (10, 11) at the specified time.

7. Electronic assembly (13a, 13b, 13c, 14a, 14b, 14c) according to claim 5 or 6, wherein the communication unit (17) is configured to, in the event that two or more requests are in the queue unit (18) at the specified time, 18 have identical sequence weighting and identical priority weighting, to forward to the field device (10, 11) at the specified time the request stored in the queue unit (18) that was received earliest by the communication unit (17).

8. Electronic assembly (13a, 13b, 13c, 14a, 14b, 14c) according to any one of claims 5 to 7, wherein the communication unit (17) is configured to remove the request from the queue unit (18) after forwarding the request to the field device (10, 11).

9. Electronic assembly (13a, 13b, 13c, 14a, 14b, 14c) according to one of the preceding claims, wherein the communication unit (17) is configured to perform communication with the automation components (9a, 9b) on the basis of the PROFINET or PROFI BUS standard.

10. Control system (1) for a technical plant, in particular a manufacturing or process plant, comprising at least two automation components (9a, 9b), in particular programmable logic controllers (PLCs), an electronic assembly (13a, 13b, 13c, 14a, 14b, 14c) according to one of claims 1 to 9 and a field device (3), wherein the automation components (9a, 9b) are connected to the electronic assembly (13a, 13b, 13c, 14a, 14b, 14c) via the second connection (16), and the field device (10, 11) is connected to the electronic assembly (13a, 13b, 13c, 14a, 14b, 14c) via the first connection (15) in order to enable a communication link between the automation components (9a, 9b) and the field device (10, 11).

11. Method for operating an electronic assembly (13a, 13b, 13c, 14a, 14b, 14c) for an automation system comprising the electronic assembly (13a, 13b, 13c, 14a, 14b, 14c): - at least one first connection (15) for connecting the electronic assembly (13a, 13b, 13c, 14a, 14b, 14c) to a field device (10, 11) of the technical system - at least one second connection (16) for connecting the electronic assembly (13a, 13b, 13c, 14a, 14b, 14c) to automation components (9a, 9b) of the automation system, 202501734 Foreign version 06.02.2026 19 - a communication unit (17) designed to enable communication, in particular based on the HART standard, between automation components (9a, 9b) connected to the electronic assembly (13a, 13b, 13c, 14a, 14b, 14c) at the second terminal (16) and a field device (10, 11) connected to the electronic assembly (13a, 13b, 13c, 14a, 14b, 14c) at the first terminal (15), - one queue unit (18), the procedure includes the following steps: d) Directing requests, in particular those based on the HART standard, to the communication unit (17) by automation components (9a, 9b) of the automation system, e) Storing requests in the queue unit (18), f) Forwarding the requests to the field device (10, 11) according to a sequence weighting, wherein the sequence weighting for forwarding the requests to the field device (10, 11) depends on a respective priority weighting assigned to the automation components (9a, 9b) and a time weighting of the requests.

12. Method according to claim 11, wherein the communication unit (17), in particular in the case that the field device (10, 11) has signaled its readiness to receive a request before a certain time, forwards to the field device (10, 11) at that certain time the request stored in the queue unit (18) which has the highest sequence weighting at that certain time.

13. The method of claim 12, wherein, in the event that two or more requests in the queue unit (18) have an identical priority weight at the specified time, the communication unit (17) forwards to the field device (10, 11) the request stored in the queue unit (18) that has the highest priority weight at that specified time. 202501734 Foreign version 06.02.2026 20 14. Method according to claim 12 or 13, wherein, in the event that two or more requests in the queue unit (18) have an identical sequence weighting and an identical priority weighting at the specified time, the communication unit (17) forwards to the field device (10, 11) at the specified time the request stored in the queue unit (18) which was received earliest by the communication unit (17).

15. Method according to any one of claims 12 to 14, wherein the communication unit (17) removes the request in question from the queue unit (18) after forwarding the request to the field device (10, 11).

Images