Method for initializing an automation network, substitute bus user, and automation network

Abstract

In a method for initializing an automation network including a plurality of bus users, for each bus user, the identification object assigned to the bus user in a target configuration is compared with an identification object read out from the bus user, wherein, if there is a discrepancy between the identification objects, a type identifier read out from the bus user is used to identify whether the bus user is a substitute bus user, wherein, if the type identifier indicates that the bus user is a substitute bus user, a substitute list read out from the bus user is used to identify whether the original bus user is able to be replaced by the substitute bus user, and wherein a fault state is triggered and the initialization is aborted if a permitted actual configuration is not identified when determining the actual configuration.

Description

[0001] Description

[0002] Method for initializing an automation network, exchange bus participants and automation network

[0003] The invention relates to a method for initializing an automation network. The method serves to detect, configure, and activate a function of an exchange bus participant in an automation network. Furthermore, the invention relates to an exchange bus participant for an automation network, an automation network, and a bus participant configured to detect, configure, and / or activate a function of the exchange bus participant.

[0004] The patent application claims priority from German patent application 10 2023 135 813 .8, the disclosure of which is hereby incorporated by reference.

[0005] Fieldbus systems that transmit messages based on the Ethernet protocol are often operated in the form of a control bus device, i.e. a central control unit or master device, and a subordinate bus device or subordinate unit in a system or machine, which is / are controlled by the control bus device. The control bus device is the central controller, which has bus access authorization and can output data to the fieldbus. The subordinate bus devices or subordinate units in the fieldbus system are the field devices, such as I / O devices, drives, measuring transducers, etc. They do not have bus access authorization and may only acknowledge received data and transmit data upon request from the control bus device.

[0006] The control bus device can, for example, form a so-called MainDevice (abbreviated to M Device), and the subordinate bus device can, for example, form a SubordinateDevice (abbreviated to SubDevice). In other words, the control bus device can dictate the communication behavior of the subordinate bus device.

[0007] Typically, in automation systems, a programmable logic controller (PLC) executes cyclic control processes to generate output data for these and / or other subordinate bus devices based on input data from subordinate bus devices. This output data is then sent by the control bus device. After completing a cyclic control process of the PLC, the control bus device sends the output data in the form of Ethernet data packets or Ethernet frames (also known as Ethernet telegrams) via the fieldbus. The subordinate bus devices extract the output data assigned to the respective subordinate bus device from the Ethernet data packets and use this output data to execute a local device process.The data acquired by the local node process is then transferred from the subordinate bus node to the control bus node, and then transferred from the control bus node to the PLC as input data for one of the next cyclic control processes. The subordinate bus node enters the input data into a telegram sent by the control bus node.

[0008] When using the real-time EtherCAT protocol within a control bus node and subordinate bus node system, the Ethernet data packets containing the EtherCAT datagrams are processed by the subordinate bus nodes in a single pass. Each subordinate bus node on the fieldbus is assigned its own data block area in the payload area of ​​the Ethernet data packet.

[0009] Instead of a control bus node-subordinate bus node system, a fieldbus system can also be operated using a provider-consumer model. In the provider-consumer model, each node—that is, both the control bus node and the subordinate bus nodes (field devices on the fieldbus)—provides data that can be requested by one or more of the other bus nodes. The data is provided cyclically. The real-time PROFINET protocol, for example, uses the provider-consumer model for Ethernet data packet exchange. The data in the payload area of ​​the Ethernet data packet is then intended for the consumer bus node specified in the destination address.

[0010] The individual bus devices of the automation network can be identified for the various transmission protocols and access methods – regardless of the hierarchical structure of the automation network – via the so-called identification object of a bus device. The identification object, or so-called "identity object," forms a first communication object that contains one or more data fields for identifying a bus device. The first data field of the identification object can be configured as the product code of the bus device, the second data field of the identification object can be configured as the version number (so-called "revision number") of the bus device, and the third data field can be configured as the manufacturer ID (so-called "vendor ID") of the bus device. In addition, a fourth data field can form a serial number. The first to fourth data fields can each contain UINT32 values.The version number can have a first data word (“Lo-Word”, bits 0-15) and a second data word (“Hi-Word”, bits 16-31).

[0011] However, for the above-mentioned identification of a bus participant in the automation network, it is preferable to use only the first to third data fields of the identification object, i.e. the product identifier, the version number and the manufacturer identifier.

[0012] Due to delivery difficulties or discontinuation of electronic components, e.g., chips (semiconductor technology), it happens that circuit components of a bus device are replaced by others, which then often acquire additional functionality in addition to the functionality of the original bus device being replaced, i.e., the original bus device, and / or are intended to replace several original bus devices. The bus devices whose circuit components have been replaced by others form so-called "replacement" bus devices. In other words, a replacement bus device is designed to functionally replace at least one original bus device, although it may have a wider range of functions than the original bus device.

[0013] A replacement bus device may differ from an original bus device, for example, in the product identifier and / or the first data word of the version number. This means that the actual configuration of the automation network does not match the target configuration of the automation network. The target configuration can correspond to a digital description of the automation network with multiple bus devices. This means that the target configuration can form a digital description of the fieldbus topology of the automation network: line, ring, tree, etc., the order of the bus devices connected to the fieldbus, the configuration data of the bus devices, a table with identification objects of the bus devices, etc. The digital description can be implemented, for example, as a digital description file or similar.The actual configuration can form a real description of the automation network, i.e. an initial situation of the fieldbus topology and the bus participants physically connected to the fieldbus, their real configuration data, etc. The actual configuration can be recorded, for example, by reading or reading out information from the individual bus participants from a control bus participant and thus recording the individual bus participants.

[0014] In automation technology, fieldbus systems can generally be divided into systems in which, for example, a control bus station actively reads the above-mentioned identification of, for example, subordinate bus stations (recording the above-mentioned actual configuration of the automation network), and systems in which, for example, the subordinate bus stations independently check the above-mentioned identification and, if necessary, transmit a confirmation to the control bus station. In the latter case, the control bus station does not actively read any identification of the subordinate bus stations.

[0015] Especially in the event that the control bus participant actively reads out the identification of the subordinate bus participants, i.e. records the above-mentioned actual configuration of the automation network, a subordinate bus participant whose circuit components have been replaced by others as mentioned above, i.e. a subordinate replacement bus participant, may, for example, have a distinction in the product identifier and / or the first data word of the version number compared to an original bus participant. It is also conceivable that the second data word of the version number of a replacement bus participant differs from the second data word of the version number of an original bus participant. It is also conceivable that the manufacturer identifier may differ between the original bus participant and the replacement bus participant.This is the case, for example, if the replacement bus participant comes from a different manufacturer than the original bus participant.

[0016] During the initialization phase of the automation network, e.g. during boot-up of the EtherCAT automation network, the control bus device can check whether the target and actual configurations of the subordinate bus devices match. The actual configuration can be obtained, for example, by reading the identification object of the corresponding bus device. As a rule, the product code and manufacturer ID must match. For the version number (revision number), the first data word, i.e. the low word (bits 0-15), must match, and a comparison can usually be made for the second data word, i.e. the high word (bits 16-31). The comparison can be carried out using relational operators, for example.The Hi-Word (bits 16-31) should meet the condition that the Hi-Word is larger or equal to the actual configuration than the target configuration (actual configuration >= target configuration), since this is incremented with progressive versions of a product.

[0017] If the replacement bus device were to replace the original bus device in an existing bus configuration, the control bus device would detect an incorrect identification during the initialization phase of the automation network—i.e., when capturing the actual configuration of the automation network—and enter an error state. The initialization phase could therefore not be completed successfully, and the replacement bus device would therefore not be activated with regard to its function.

[0018] One difficulty here is that the bus configuration is created at a time when it is still uncertain which bus devices might require or use a replacement bus device in the future. Consequently, a different product identifier and / or a different version number of the identification object of the replacement bus device may also be unknown at this time.

[0019] It is therefore an object of the present invention to provide an improved method for initializing an automation network and a corresponding automation network.

[0020] This object is achieved by the independent claims. Further advantageous embodiments of the invention are specified in the dependent claims.

[0021] Disclosure of the invention

[0022] A method for detecting a replacement bus device in an automation network is proposed. At least one bus device in the automation network is configured as a replacement bus device to replace an original bus device. The method comprises the following steps:

[0023] Providing a target configuration of the automation network in a first step, wherein the target configuration comprises a digital description of the automation network, determining an actual configuration of the automation network for detecting an exchange bus participant by sending at least one data packet to the plurality of bus participants in a second step, wherein the actual configuration forms a real description of the automation network, wherein the actual configuration is determined in the second step based on the data packet by reading a first data field and / or a second data field and / or a third data field of an identification object and / or by reading a type identifier and / or by reading an exchange list of the plurality of bus participants, wherein the identification object forms a first communication object that comprises one or more data fields for identifying a bus participant,wherein the type identifier indicates whether a bus subscriber is designed as an exchange bus subscriber and wherein the type identifier comprises in particular a data field and / or a second communication object, wherein the exchange list indicates which original bus subscribers can be replaced by an exchange bus subscriber, and,

[0024] Comparing the determined actual configuration with the target configuration based on the first and second step in a third step to identify a replacement bus participant.

[0025] Furthermore, a method for configuring a replacement bus subscriber in an automation network is proposed, comprising the following steps: providing a target configuration of an automation network in a first step and a replacement bus subscriber which is designed to replace at least one original bus subscriber, wherein the target configuration comprises a digital description of the automation network with the plurality of bus subscribers, of which at least one bus subscriber is designed as a replacement bus subscriber, and

[0026] Writing an exchange object for setting a function, i.e. a mode of operation of the exchange bus participant in relation to the at least one original bus participant by sending a further data packet to the plurality of bus participants in a second step, wherein the exchange object forms a third communication object which comprises at least one data field, or wherein the exchange object is designed as an identification object which comprises a first communication object according to the above-mentioned or the following features with one or more data fields for identifying a bus participant.

[0027] Furthermore, a bus device for an automation network is proposed, which is configured to execute a method for detecting a replacement bus device according to the above-mentioned features and / or the following features and / or a method for configuring a replacement bus device according to the above-mentioned and / or the following features. The bus device is configured in particular as a main device, i.e., a control bus device, for controlling and coordinating subordinate devices, i.e., subordinate bus devices.

[0028] Furthermore, a method for activating a function, i.e., the mode of operation of a replacement bus device with respect to the mode of operation of at least one original bus device in an automation network, as well as a replacement bus device for replacing an original bus device for an automation network, is proposed. The replacement bus device is configured to execute the method explained below for activating a function of the replacement bus device. The method comprises the following steps:

[0029] Receiving an exchange object in a first step, wherein the exchange object forms a third communication object comprising at least one data field for setting the function of the exchange bus subscriber in relation to at least one original bus subscriber, or wherein the exchange object is designed as an identification object forming a first communication object according to the above and / or the following features, wherein the first communication object comprises one or more data fields for identifying a bus subscriber,

[0030] Checking the support of the function of at least one original bus participant by the replacement bus participant in a second step, wherein the checking of the support of the function of at least one original bus participant by the replacement bus participant is carried out in particular taking into account the replacement object, and

[0031] Activating the function of the replacement bus subscriber according to the exchange object and / or according to the identification object in a third step, provided that the check in the second step has been successfully carried out. Furthermore, an automation network is proposed. The automation network has a plurality of bus subscribers that are communicatively connected to one another via a bus system. At least one bus subscriber of the plurality of bus subscribers is designed as a replacement bus subscriber for replacing an original bus subscriber according to the above-mentioned and / or the following features. At least one bus subscriber is designed as a transmitter according to the above-mentioned features in order to recognize and / or configure a replacement bus subscriber based on one or more transmitted data packets.The automation network forms, in particular, an EtherCAT automation network, and the exchange bus device is configured as a subordinate device, i.e., a subordinate bus device that can be controlled by a main device, i.e., a control bus device. The bus device configured to detect and / or configure the exchange bus device, i.e., the aforementioned transmitter, is configured as a main device, for controlling and coordinating the subordinate devices. An exchange bus device is configured to execute a method for activating a function. The exchange bus device is configured as a receiver.

[0032] It is understood that the methods mentioned can be carried out by a computer or a similar unit, e.g. processing unit, processor, etc.

[0033] The above-mentioned method for detecting a replacement bus device provides a simple method for capturing the actual configuration of an automation network and comparing it with a target configuration. Advantageously, the method can be carried out fully automatically. Based on the above-mentioned method, the replacement bus device can advantageously be used to replace at least one original bus device without the transmitter executing the above-mentioned detection method, e.g., the control bus device or main device, detecting incorrect identification, e.g., during an initialization phase of the automation network, and, of course, without the target configuration being changed.

[0034] Based on the proposed methods and bus devices or automation networks, not only can delivery problems with electronic components be easily resolved or circumvented, but the method for detecting a replacement bus device is also advantageously suited for replacing a defective original bus device that would otherwise not be automatically detected, for example, during the initialization phase. In these cases, the replacement bus device can be easily deployed with new functionality. Products or bus devices can therefore be advantageously replaced without having to modify the user's control program or without having to reconfigure the automation network. This saves time, effort, and costs and avoids potential errors during adaptation.Inventory costs can also be reduced if a replacement bus device is designed to functionally replace several original bus devices, thus requiring fewer variants of the original bus device to be stocked. Furthermore, downtime of the automation system's machine due to a mismatch between the actual and target configurations can be advantageously reduced.

[0035] A flexible combination of the method for detecting an exchange bus participant, in which the reading or reading of information is the main focus, e.g. by reading the identification object, and the method for configuring an exchange bus participant, in which the writing of information is the main focus, e.g. by writing the identification object or another communication object or the exchange object, is possible. It is conceivable that the identification object and the exchange object are the same first communication object. In addition, the methods can also be used separately, or just one of the methods mentioned. It is conceivable that the exchange bus participant is configured, but the method for detecting the exchange bus participant is not carried out beforehand by the control bus participant.

[0036] The bus device that performs the process of identifying the exchange bus device (reading) and the process of configuring it (writing) can act as the sender, e.g., as a control bus device or main device. The bus device that performs the process of activating a function, i.e., an exchange bus device, can act as the receiver.

[0037] The original bus device can, for example, be an EL1002 input terminal from Beckhoff Automation (comprising a 2-channel digital input), while the replacement bus device can, for example, be an EL8601-8411 multifunction terminal from Beckhoff Automation (12-channel multi-interface). When the replacement bus device is a multifunction terminal, the replacement bus device must be configured, as the multifunction terminal inherently provides variable, i.e., adaptable, interfaces that can function as inputs (or alternatively as outputs) as needed.This example is not intended to be limiting, as the original bus device can alternatively be an EL2002 output terminal from Beckhoff Automation (2-channel digital output), a combined EL1259 input and output terminal from Beckhoff Automation (8-channel digital input and 8-channel digital output), or the multifunction terminal mentioned above. Likewise, the replacement bus device can be any of the above-mentioned terminals without restriction.

[0038] In another embodiment, the target configuration, as a digital description of the automation network, includes a description of a fieldbus topology of the automation system, in particular line, ring, tree, a sequence of the bus devices connected to the fieldbus, configuration data of the bus devices, and a table with identification objects of the bus devices. It is understood that this list is not exhaustive. For example, the digital description can be implemented as a digital description file.

[0039] In a further embodiment of the method for identifying a replacement bus subscriber, the first data field of the identification object is designed as a product identifier of the bus subscriber, the second data field of the identification object is designed as a version number of the bus subscriber, and the third data field is designed as a manufacturer identifier of the bus subscriber. The version number has a first data word and a second data word. An original bus subscriber has, in particular, a first version consisting of the product identifier and / or the version number, and a replacement bus subscriber has, in particular, a second version consisting of the product identifier and / or the version number, in particular in the replacement list of the replacement bus subscriber. The second version consisting of the product identifier and / or the version number differs from the first version, in particular in the first data word of the version number and / or the product identifier.

[0040] Advantageously, a replacement bus subscriber can be easily identified as such based on the second version from the product identifier and / or version number, in particular in the replacement list, and / or together with a type identifier, and an initialization phase of the automation network therefore does not have to be aborted prematurely, for example. In a further embodiment of the method for identifying a replacement bus subscriber, at least the second data word of the version number of the identification object is comparable using a comparison operator. The second data word of the version number of the identification object of the replacement bus subscriber is in particular configured in ascending order compared to the second data word of the version number of the identification object of the original bus subscriber.

[0041] This advantageously allows simple mathematical operations to be carried out, which facilitate the handling of the proposed method and ensure good compatibility.

[0042] In a further embodiment of the method for identifying a replacement bus subscriber, after reading the first data field and / or the second data field and / or the third data field of the identification object, a comparison with the target configuration is carried out in a first intermediate step. If the comparison in the first intermediate step reveals that there is a discrepancy between the determined actual configuration and the target configuration, the type identifier of a bus subscriber is read in a second intermediate step. If the type identifier of the bus subscriber indicates in the second intermediate step that the bus subscriber is configured as a replacement bus subscriber, the exchange list of the replacement bus subscriber is read in a third intermediate step and compared with the target configuration.

[0043] The sequence of the steps mentioned in the procedure can be varied as desired, thus offering the greatest possible flexibility. The individual steps can be performed successively. The best possible transparency and traceability can be achieved by performing a comparison between the target and actual configuration during each intermediate step. This allows an error message to be generated early on or the initialization phase to be aborted.

[0044] In a further embodiment of the method for identifying an exchange bus participant, the reading of the first data field and / or the second data field and / or the third data field of the identification object and / or the type identifier and / or the exchange list in the second step can be carried out based on a first transmitted data packet. The reading of the type identifier in the second intermediate step can be carried out based on a second transmitted data packet, and the reading of the exchange list in the third intermediate step can be carried out based on a third transmitted data packet.

[0045] This advantageously offers a clear division of the readout or reading steps carried out, better clarity, and less susceptibility to errors compared to reading out all information in one readout step / based on a single data packet.

[0046] In a further embodiment of the method for detecting a replacement bus node, an error message can be generated in a fourth intermediate step if the comparison of the detected actual configuration based on the type identifier in the second intermediate step and / or the comparison of the detected actual configuration based on the replacement list in the third intermediate step with the target configuration reveals a deviation from the target configuration. This advantageously offers the possibility of a defined termination of the method.

[0047] In a further embodiment of the method for detecting a replacement bus node, the aforementioned method is performed during an initialization phase of the automation network. The initialization phase can be aborted by generating the error message in the fourth intermediate step. This advantageously offers the possibility of a defined termination of the method.

[0048] In a further embodiment of the method for configuring an exchange bus participant in an automation network, the provision of the target configuration in the first step comprises sending the target configuration by means of a fourth data packet to the plurality of bus participants of the automation network.

[0049] In this way, the individual bus devices can check for themselves whether the actual configuration matches the target configuration. This is particularly conceivable if the bus devices have not been previously identified, i.e., if the procedure for detecting a replacement bus device has not been executed previously.

[0050] In a further embodiment of the method for configuring an exchange bus participant, before writing the exchange object in the second step, a method for detecting an exchange bus participant in an automation network according to one of the above-mentioned features can be carried out in order to determine an actual configuration of the automation network.

[0051] This advantageously enables improved compatibility and instantaneous configuration of the replacement bus node (write), since a replacement bus node has already been identified as such by the procedure for identifying a replacement bus node. Furthermore, this approach ensures that only one replacement bus node is actually configured.

[0052] In a further embodiment of the method for configuring an exchange bus participant, if the exchange object has been written to a bus participant that is not configured as an exchange bus participant, a configuration of the function of this bus participant remains unchanged.

[0053] This advantageously offers additional security, so that a configuration affects only one exchange bus participant and no other bus participant.

[0054] In a further embodiment of the method for configuring a replacement bus subscriber, the replacement bus subscriber is designed, if the replacement object has been written in the second step and no method for detecting a replacement bus subscriber according to the above-mentioned features has been carried out, the replacement bus subscriber is designed in a third step to carry out a check of the support of the function of at least one original bus subscriber, in particular taking into account the replacement object, and to transmit a confirmation of the configuration of the function of the replacement bus subscriber, i.e. a mode of operation of the replacement bus subscriber with regard to a mode of operation of at least one original bus subscriber, in a fourth step, provided that the check of the replacement object in the third step was successful.

[0055] This advantageously reduces network traffic, as the replacement bus node can perform the check for the presence of a replacement bus node itself. Consequently, the individual steps (reading) for detecting the replacement bus node or the reading step can be eliminated.

[0056] In a further embodiment of the method for activating a function, i.e. a mode of operation of an exchange bus participant, said method comprises a fourth step: sending a confirmation of the activation of the function of the exchange bus participant, provided that the third step has been successfully carried out.

[0057] This can advantageously ensure that the replacement bus participant has activated the desired function and as such can be fully used (within the scope of its function) in the automation network.

[0058] In a further embodiment, the exchange bus participant comprises at least one communication unit that is communicatively connected to at least one memory unit of the exchange bus participant. The memory unit comprises, in particular, a non-volatile memory. The communication unit is communicatively connected to a bus system.

[0059] This advantageously enables a simple structure of the exchange bus participant as well as a cost-effective implementation and good compatibility with known standards and systems.

[0060] In a further embodiment, the exchange bus participant further comprises a microcontroller unit communicatively connected to the communication unit for checking the exchange object and / or the identification object. The exchange bus participant comprises an object directory, wherein the identification object and / or the exchange object can be stored in the object directory.

[0061] The microcontroller unit can be designed as a microcontroller (PCI for short) and advantageously performs the testing of the exchange object and / or the identification object. This represents the preferred design of the exchange bus participant.

[0062] In a further embodiment, the exchange bus device is designed as a subordinate device, i.e., a subordinate bus device that can be controlled by a main device, i.e., a control bus device. If the exchange bus device is designed as a subordinate device, the communication unit is designed as an EtherCAT subdevice controller.

[0063] This makes it advantageous to use the well-known EtherCAT standard. It also enables clear hierarchical structures for the individual bus devices, with the subordinate device being configured, for example, as the aforementioned receiver and the main device as the aforementioned transmitter.

[0064] The above-described properties, features, and advantages of this invention, as well as the manner in which they are achieved, will become clearer and more readily understood in connection with the following description of exemplary embodiments, which are explained in more detail in conjunction with the schematic drawings. They show:

[0065] Fig. 1 is a schematic representation of a method for detecting an exchange bus participant according to a first embodiment;

[0066] Fig. 2 is a schematic representation of a method for detecting an exchange bus participant according to a second embodiment;

[0067] Fig. 3 is a schematic representation of a method for configuring an exchange bus subscriber according to a first embodiment;

[0068] Fig. 4 is a schematic representation of a method for configuring an exchange bus participant according to a second embodiment;

[0069] Fig. 5 is a schematic representation of a method for configuring an exchange bus subscriber according to a third embodiment;

[0070] Fig. 6 is a schematic representation of a method for activating a function, i.e. a mode of operation of an exchange bus subscriber according to a first embodiment;

[0071] Fig. 7 is a schematic representation of a method for activating a function, i.e. a mode of operation of an exchange bus participant according to a second embodiment;

[0072] Fig. 8 is a schematic representation of an automation network according to a first embodiment;

[0073] Fig. 9 is a schematic representation of an automation network according to a second embodiment; Fig. 10 is a schematic representation of an exchange bus participant according to a first embodiment;

[0074] Fig. 11 is a schematic representation of an exchange bus subscriber according to a second embodiment; and

[0075] Fig. 12 is a schematic representation of an exchange bus participant according to a third embodiment.

[0076] Please note that the figures are merely schematic and not to scale. Therefore, components and elements shown in the figures may be exaggerated or reduced in size for clarity. Furthermore, please note that the reference numerals in the figures have been chosen to be unchanged or similar when referring to identical or similarly designed elements and / or components.

[0077] The term "MainDevice" (abbreviated to "MDevice") refers to a "control bus device" designed to control and coordinate "SubordinateDevices" in the automation network. Typically, in automation systems, a programmable logic controller (PLC) executes cyclic control processes to generate output data for subordinate bus devices based on input data from these and / or other subordinate bus devices. The output data is then sent by the "MainDevice" or control bus device. The PLC uses control software for this purpose, e.g., TwinCAT from Beckhoff Automation. A "MainDevice" is a software module independent of the control software that controls and coordinates the subordinate bus devices. The terms "MainDevice" and "control bus device" can be understood as synonyms.

[0078] The term “SubordinateDevice” (short “SubDevice”) refers to a subordinate bus device that can be controlled by a “MainDevice”, i.e. a “control bus device”, where controllable also includes configurable. A “SubDevice” is therefore a subordinate unit in a system or machine that can be controlled by the main device, i.e. the “MainDevice”. The “SubDevice” processes the data packets sent by the “MainDevice”, e.g. Ethernet data packets, executes the tasks associated with the data packet, and forwards the data packet. “SubDevices” can, for example, form “original bus devices” and “replacement bus devices”. A “SubDevice” can, for example, be a terminal with an ASIC chip or a programmable FPGA as an EtherCAT Subdevice Controller (ESC) as the processing unit.Each EtherCAT subdevice includes such a processing unit designed as an ESC so that cyclic and acyclic process data can be exchanged from the main device with the subdevice via the EtherCAT fieldbus.

[0079] An “original bus participant” refers to a bus participant that is included in the original “target configuration” of the automation network.

[0080] A “replacement bus subscriber” is designed to functionally replace at least one “original bus subscriber”, ie with regard to a mode of operation of an “original bus subscriber” and / or a new functionality which the “original bus subscriber” to be replaced does not include, for example.

[0081] A "target configuration" of the automation network includes a digital description of the automation network with the majority of bus devices, i.e. a digital description of the fieldbus topology of the automation network: line, ring, tree, etc., the order of the bus devices connected to the fieldbus, the configuration data of the bus devices, a table with identification objects of the bus devices, etc. The digital description can be implemented, for example, as a digital description file or similar.

[0082] An "actual configuration" of the automation network forms a starting point, i.e. a real description of the automation network, i.e. a real description of the fieldbus topology and the bus devices physically connected to the fieldbus. The actual configuration can be recorded, for example, by reading or reading out information from the individual bus devices. Alternatively, in fieldbus systems where the bus devices are not actively recorded, the individual bus devices can read received information (e.g. a received "target configuration") to determine the "actual configuration" and compare it with their own information. If necessary, upon detection of the presence of a "replacement bus device" and successful activation of its function, transmit a short confirmation via the fieldbus so that cyclic control processes of the automation system can be executed based on this, including with the "replacement bus device".

[0083] An "identification object" forms a communication object, i.e. a digital description file of a product or a bus device, e.g. in EtherCAT systems and EtherCAT bus devices an ESI file, i.e. an EtherCAT Subordinate Device Information file. The identification object comprises several data fields for identifying a bus device. The data fields of the "identification object" can be read to determine the "actual configuration" of the automation network. The "identification object" of a "replacement bus device" can, for example, differ from the "identification object" of an "original bus device". The data fields of the "identification object" can, for example, be written to set the function of the "replacement bus device" when a "replacement bus device" is detected based on reading the "identification object" and / or reading a "type identifier" and / or reading an "exchange list".

[0084] A “communication object” forms a data structure, comprising a collection of data that is made available in the automation network, e.g. access rights of the individual bus participants, etc.

[0085] A “product identifier” is a device- or bus-subscriber-specific identifier or code that is designed differently for different devices or for different bus participants, e.g. terminals that each contain an ASIC chip (input, output, multi-function terminals, etc.).

[0086] A “manufacturer identifier” is a manufacturer-dependent identifier or code, which can be designed differently depending on the manufacturer of the device or bus participant.

[0087] A “version number” distinguishes individual versions of the same device or bus participant in order to clearly identify their further developments.

[0088] An "exchange object" can form a further, separate communication object to the "identification object," which has at least one data field that is written to set the function of the "exchange bus participant." The exchange object can form a separate digital file for writing or configuration. Alternatively, the "exchange object" can also correspond to the "identification object," i.e., form the same communication object. The "exchange object," or the "identification object" as the same communication object as the "exchange object," specifies how the exchange bus participant should behave functionally, i.e., in terms of its mode of operation. The exchange object can include the aforementioned target configuration of the automation network, i.e., have the identification object of the at least one original bus participant that the exchange bus participant can functionally replace.

[0089] A "type identifier" indicates whether a bus subscriber is configured as a "replacement bus subscriber" or not. For example, a "type identifier" can comprise a data field that was previously unused and assigned the value zero, and now contains a value indicating the presence of a "replacement bus subscriber." Alternatively or additionally, the "type identifier" can comprise a first additional communication object that, via the first additional communication object, indicates the presence of a "replacement bus subscriber" (an original bus subscriber, for example, would not comprise the first additional communication object or, alternatively, would contain it unused and with the value zero).

[0090] An “exchange list” indicates which “original bus participants” a “replacement bus participant” can functionally replace.

[0091] A “data word” is a specific amount of data that a computer can process in one step in an arithmetic-logical unit of a processing unit, e.g. a processor.

[0092] An "initialization phase" refers to the startup or start-up phase of an automation network. During the "initialization phase," various data packets are exchanged to read the properties of the bus devices and thus identify them.

[0093] “Control process” refers to the general, cyclically performed control operation of the automation network.

[0094] The proposed methods for detecting and configuring a replacement bus device, as well as the proposed method for activating a function of a replacement bus device and the individual bus devices of the automation network configured to execute the methods, offer a way to replace bus devices in an automation network without having to modify a user's control program. A replacement bus device intended to functionally replace at least one original bus device can be automatically detected and configured to perform the corresponding function. The replacement bus device can also automatically activate its function and be fully used for cyclic control processes. This can also significantly simplify the maintenance of complex automation networks.

[0095] Figures 1, 2 and 8, 9 are described together below. However, it is to be understood that the following explanation is not exclusively limited to the figures mentioned, but the features described can also be used in combination with the other figures. Fig. 1 shows a schematic representation of a method 100 for detecting an exchange bus participant 815, 915, 917, 919, 1000, 1100, 1200 according to a first embodiment, and Fig. 2 shows a schematic representation of a method 200 for detecting an exchange bus participant 815, 915, 917, 919, 1000, 1100, 1200 according to a second embodiment. Fig. 8 shows a schematic representation of an automation network 800 according to a first embodiment, and Fig. 9 shows a schematic representation of an automation network 900 according to a second embodiment.

[0096] Figures 8 and 9 each show different embodiments of automation networks 800, 900, each having a plurality of bus devices 805, 905. The plurality of bus devices 805, 905 are communicatively connected to one another via a bus system 810, 910 (a fieldbus system). At least one of the plurality of bus devices 805, 905 is configured in both automation networks 800, 900 as a replacement bus device 815, 915, 917, 919 for replacing an original bus device. For example, the automation network 800 in Fig. 8 has a first and second original bus subscriber 820, 825, as well as a replacement bus subscriber 815, while the automation network 900 in Fig. 9 has, for example, a first to third replacement bus subscriber 915, 917, 919. It is understood that the two views of the automation networks 800, 900 each show the already performed exchange of original bus subscribers, i.e. Fig.Figure 8 illustrates the replacement of an original bus device (not shown) with the replacement bus device 815, and Figure 9 illustrates the replacement of the first to third original bus devices (not shown). The automation network 900 in Figure 9 specifically shows that a replacement bus device can functionally replace multiple original bus devices, which will be explained in more detail below. This can have the advantage for the user of only having to manage one type of bus device.

[0097] At least one bus participant 830, 930 of the automation networks 800, 900 is designed to recognize and / or configure an exchange bus participant 815, 915, 917, 919, 1000, 1100, 1200. The said bus subscriber 830, 930 is designed to carry out a method 100, 200 for detecting a replacement bus subscriber 815, 915, 917, 919, 1000, 1100, 1200, which will be explained below, and / or to carry out a method 300, 400, 500 for configuring a replacement bus subscriber 815, 915, 917, 919, 1000, 1100, 1200, which will be explained below with reference to Figs. 3 to 5. The mentioned bus participant 830, 930 can, for example, be designed as a main device, i.e. as a control bus participant, for controlling and coordinating subordinate devices, i.e. subordinate bus participants, which can form exchange bus participants 815, 915, 917, 919, 1000, 1100, 1200.It is understood, however, that the aforementioned methods 100, 200, 300, 400, 500 are not limited to a control bus participant-subordinate bus participant of an automation network.

[0098] Preferably, the automation networks 800, 900 in Figs. 8 and 9 each form an EtherCAT automation network, and an exchange bus device 815, 915, 917, 919, 1000, 1100, 1200 is each configured as a subordinate device, i.e., a subordinate bus device that can be controlled by the main device, i.e., the control bus device 830, 930. The bus device 830, 930, which is configured to detect and / or configure the exchange bus device 815, 915, 917, 919, 1000, 1100, 1200, is configured as a main device, for controlling and coordinating the subordinate devices.

[0099] An exchange bus participant 815, 915, 917, 919, 1000, 1100, 1200 is each designed to carry out a method for activating a function 600, 700 of the exchange bus participant 815, 915, 917, 919, 1000, 1100, 1200, wherein the method for activating the function 600, 700 will be explained with reference to Figures 6 and 7.

[0100] The above-mentioned method 100 according to the first embodiment in Fig. 1 for detecting an exchange bus participant 815, 915, 917, 919, 1000, 1100, 1200 in an automation network 800, 900, which is designed, for example, according to Figures 8 and 9, comprises, for example, in a first step 105, providing a target configuration of the automation network 800, 900. The target configuration comprises a digital description of the automation network 800, 900 with the plurality of bus participants 805, 905. The target configuration comprises, as a digital description of the automation network, a description of a fieldbus topology of the automation system, e.g. line, ring, tree, a sequence of the bus participants connected to the fieldbus, configuration data of the bus participants, a table with identification objects of the bus participants, etc. It is understood that the list is not exhaustive.For example, the digital description can be implemented as a digital description file.

[0101] A second step 110 of the method 100 comprises determining an actual configuration of the automation network 800, 900 for detecting a replacement bus node 815, 915, 917, 919, 1000, 1100, 1200 by sending at least one data packet to the plurality of bus nodes 805, 905, wherein the actual configuration forms a real description of the automation network 800, 900. The actual configuration of the automation network 800, 900 forms a starting situation, i.e., a real description, e.g., of the fieldbus topology and the bus nodes physically connected to the fieldbus, etc.

[0102] In this case, the actual configuration is determined in the second step 110 based on the at least one data packet by reading a first data field and / or a second data field and / or a third data field of an identification object and / or by reading a type identifier and / or by reading an exchange list 833, 933, 937, 939 of the plurality of bus participants 805, 905.

[0103] The identification object forms a first communication object that includes one or more data fields for identifying a bus device. The first data field of the identification object is configured as the product identifier of the bus device, the second data field of the identification object is configured as the version number of the bus device, and the third data field is configured as the manufacturer identifier of the bus device.

[0104] The version number has a first data word and a second data word. An original bus device, for example, has a first version consisting of the product identifier and / or the version number, while a replacement bus device 815, 915, 917, 919, 1000, 1100, 1200, for example, has a second version consisting of the product identifier and / or the version number. The second version consisting of the product identifier and / or the version number can differ from the first version, for example, in the first data word of the version number and / or the product identifier. It is understood that the reading of the aforementioned information can be performed by the control bus device 830, 930, which sends the data packet for reading the information from the bus devices and thus forms the sender.

[0105] The first data word of the version number forms, for example, the low word (bits 0-15). The second data word of the version number of the identification object can be compared, for example, using a comparison operator, provided that the second data word of the version number of the identification object of the replacement bus station (815, 915, 917, 919, 1000, 1100, 1200) is in ascending order compared to the second data word of the version number of the identification object of the original bus station. The second data word forms the high word (bits 16-31). The comparison can be carried out, for example, using greater than or equal to (>=) comparison operators, whereby the comparison is carried out based on the second data word of the version number of the identification object of the original bus participant with the second data word of the version number from the exchange list 833, 933, 937, 939 of the exchange bus participant 815, 915, 917, 919, 1000, 1100, 1200.This is done under the condition that the manufacturer identifier, product identifier and the first data word of the version number of the replacement bus device 815, 915, 917, 919, 1000, 1100, 1200 match the corresponding values ​​from the identification object of the original bus device.

[0106] An original bus device can be designated EL1002-0000-0016, for example, where "EL1002" is the product identifier, "0000" is the first data word of the version number, and "0016" is the second data word of the version number of the original bus device. The target configuration of the automation network 800, 900, comprising, for example, only the specified bus device, would then be EL1002-0000-0016. The replacement list 833, 933, 937, 939 of a replacement bus device 815, 915, 917, 919, 1000, 1100, 1200 could contain EL1002-0000-0019, for example. For the example, EL1002-0000-0019 would therefore represent the actual configuration of the automation network 800, 900. The second data word of the version number of the replacement bus device 815, 915, 917, 919, 1000, 1100, 1200 is configured with "0019" in ascending order compared to the second data word of the version number of the identification object of the original bus device with "0016".The replacement bus device 815, 915, 917, 919, 1000, 1100, 1200 with the aforementioned replacement list 833, 933, 937, 939, having EL1002-0000-0019, can therefore replace the original bus device with "0016" as the second data word of the version number of the original bus device, since 19 >= 16. The type identifier indicates whether a bus device is configured as a replacement bus device 815, 915, 917, 919, 1000, 1100, 1200 and includes, for example, a data field and / or a second communication object.

[0107] The replacement list 833, 933, 937, 939 indicates which original bus nodes can be functionally replaced by a replacement bus node 815, 915, 917, 919, 1000, 1100, 1200. For this purpose, the replacement list 833, 933, 937, 939 includes the product identifier of the original bus node to be replaced and at least the first data word of the version number (low word). According to the example above, the replacement list 833, 933, 937, 939 can also include the second data word of the version number (high word) in order to perform the comparison described above using the comparison operator. For example, the replacement list 833 of the replacement bus node 815 in Fig. 8 includes the product identifier PC2 and the first data word of the version number RL2.

[0108] It is understood that the product identifier PC2 and the first data word of the version number RL2 of the exchange list 833 of the exchange bus node 815 have been chosen merely representatively to illustrate the principle. Specific values ​​for the product identifier and the first data word of the version number of the exchange bus node 815 in Fig. 8 can be selected similarly to the above example. It is also understood that this applies not only to the content of the exchange list 833 of the exchange bus node 815 in Fig. 8, but is also transferable to a first to third exchange bus node 915, 917, 919 with the first to third exchange lists 933, 937, 939 in Fig. 9. Furthermore, it is understood that the representative principle of clarification also applies at least to the own product identifier and the own first data word of the version number of the replacement bus participant 815 in Fig. 8 as well as the first to third replacement bus participants 915, 917, 919 in Fig. 9.Concrete values ​​for at least the own product identifier as well as the own first data word of the version number can be selected similarly to the above example for the replacement bus participant 815 in Fig. 8 as well as for the first to third replacement bus participants 915, 917, 919 in Fig. 9.

[0109] The product identifier of the replacement bus device 815, 1000, 1100 in Fig. 8 can be, for example, PC20, and the first data word of the version number of the replacement bus device 815, 1000, 1100 in Fig. 8 can be RL20. The product identifier of the first original bus device 820 can be, for example, PC1, and the first data word of the version number of the first original bus device 820 can be, for example, RL1. The product identifier of the second original bus device 825 can be, for example, PC3, and the first data word of the version number of the second original bus device 825 can be, for example,

[0110] RL3.

[0111] Similarly, the own product identifier of the first replacement bus node 915 in Fig. 9 may be PC20, and the own first data word of the version number of the first replacement bus node 915 in Fig. 9 may be RL20. The exchange list 933 of the first replacement bus node 915 in Fig. 9 may, for example, have the product identifier PC1 with the associated first data word of the version number RL1, as well as the product identifier PC2 with the associated first data word of the version number RL2, and the product identifier PC3 with the associated first data word of the version number RL3.

[0112] The own product identifier of the second exchange bus participant 917 in Fig. 9 can be, for example, PC20, and the own first data word of the version number of the second exchange bus participant 917 in Fig. 9 can be RL20. The exchange list 937 of the second exchange bus participant 917 in Fig. 9 can, for example, have the product identifier PC1 with the associated first data word of the version number RL1, as well as the product identifier PC2 with the associated first data word of the version number RL2, and the product identifier PC3 with the associated first data word of the version number RL3.

[0113] The own product identifier of the third exchange bus participant 919 in Fig. 9 can be, for example, PC20, and the own first data word of the version number of the third exchange bus participant 919 in Fig. 9 can be RL20. The exchange list 939 of the third exchange bus participant 919 in Fig. 9 can, for example, have the product identifier PC1 with the associated first data word of the version number RL1, as well as the product identifier PC2 with the associated first data word of the version number RL2, and the product identifier PC3 with the associated first data word of the version number RL3.

[0114] It is understood, as mentioned above, that the values ​​given for the product identifier and the first data word of the version number are only examples and can be implemented differently. Alternatively, the manufacturer identifier can also be considered. In the examples given, the manufacturer identifier for the original bus device and the replacement bus devices 815, 915, 917, 919, 1000, 1100, and 1200 was chosen to be identical and is therefore not explained explicitly. It is also understood here that the manufacturer identifier can vary if the configuration differs between the original bus device and the replacement bus device 815, 915, 917, 919, 1000, 1100, and 1200.

[0115] A third step 115 of the method 100 comprises comparing the determined actual configuration with the target configuration based on the first and second steps 105, 110 for identifying the replacement bus device 815, 915, 917, 919, 1000, 1100, 1200. In Fig. 8, when the control bus device 830 reads the identification object of the replacement bus device 815, a deviation between the target and actual configuration would be detected, i.e., its own product identifier PC20 instead of PC2 of the original bus device and its own first data word of the version number RL20 instead of RL2 of the original bus device. In conventional automation systems, an error message would then be generated. However, since the method 100 includes further information that can be read out, such asthe type information and the exchange list 833, in the example mentioned, when reading the type information and / or the exchange list, it could be determined that the bus participant is actually a replacement bus participant 815, which, for example, according to the exchange list 833, is designed to functionally replace the previously connected original bus participant with the product identifier PC2 and the first data word of the version number RL2.

[0116] The original bus device mentioned can, for example, be an EL1002 input terminal from Beckhoff Automation (comprising a 2-channel digital input), while the replacement bus device 815 in Fig. 8 can, for example, be a multifunction terminal of the EL8601-8411 type from Beckhoff Automation (12-channel multi-interface). As a multifunction terminal, the replacement bus device 815 therefore includes both inputs and outputs. Therefore, the replacement bus device 815, designed as a multifunction terminal, is suitable for replacing the original bus device designed as an input terminal, provided its comprehensive interfaces are configured accordingly, e.g., with 2 digital inputs.

[0117] This example is not intended to be limiting, as the original bus device can alternatively be an EL2002 output terminal from Beckhoff Automation (2-channel digital output), a combined EL1259 input and output terminal from Beckhoff Automation (8-channel digital input and 8-channel digital output), or the multifunction terminal mentioned above. Likewise, the replacement 815 bus device can then be an alternative to the above-mentioned terminals without restriction, provided it is functionally suitable for replacing the alternatively designed original bus device.

[0118] The method 100 is therefore suitable for fieldbus systems in which, for example, an identification of the subordinate bus participants is actively read out by a control bus participant, ie an actual configuration of the automation network is recorded.

[0119] The method for detecting a replacement bus user 815, 915, 917, 919, 1000, 1100, 1200 according to a second embodiment 200 in Fig. 2 can be designed in a first step 205 and a second step 210 similar to the method for detecting a replacement bus user 815, 915, 917, 919, 1000, 1100, 1200 according to the first embodiment 100 in Fig. 1, namely that the first step 205 of the method for detecting a replacement bus user 815, 915, 917, 919, 1000, 1100, 1200 according to the second embodiment 200 comprises, for example, providing the target configuration. The second step 210 of the method for detecting an exchange bus participant 815, 915, 917, 919, 1000, 1100, 1200 according to the second embodiment 200 forms, for example,determining the actual configuration by reading the first data field (product identifier) ​​and / or the second data field (version number) and / or the third data field (manufacturer identifier) ​​of the identification object, for example the exchange bus participant 815 in Fig. 8 as mentioned above.

[0120] To avoid repetition, reference is therefore made to the above explanation. Reading the first data field and / or the second data field and / or the third data field of the identification object in the second step 210 of the method for recognizing an exchange bus participant 815, 915, 917, 919, 1000, 1100, 1200 according to the second embodiment 200 can be carried out, for example, similarly to determining the actual configuration in the second step 110 of the method for recognizing according to the first embodiment 100 in Fig. 1, based on a first sent data packet. In Fig. 1, in the second step 110, all information can be read out with the first data packet, whereas in the second step 210 in Fig. 2, for example, only the identification object is read out with the first data packet. It is understood that this does not represent a restriction and can also be implemented alternatively.

[0121] After reading the first data field (product identifier) ​​and / or the second data field (version number) and / or the third data field (manufacturer identifier) ​​of the identification object in the second step 210, the comparison with the target configuration is performed in a first intermediate step 215 of the method for identifying a replacement bus subscriber 815, 915, 917, 919, 1000, 1100, 1200 according to the second embodiment 200 in Fig. 2. This can be done as explained above, wherein the first intermediate step 215 of the method for identifying a replacement bus subscriber 815, 915, 917, 919, 1000, 1100, 1200 according to the second embodiment 200 can form a branch.If the comparison in the first intermediate step 215 of the method for identifying a replacement bus subscriber 815, 915, 917, 919, 1000, 1100, 1200 according to the second embodiment 200 reveals that there is a discrepancy between the determined actual configuration and the desired configuration (j-branch), the type identifier of the bus subscriber is read in a second intermediate step 220. Reading the type identifier in the second intermediate step 220 can be performed, for example, based on a second transmitted data packet. The second intermediate step 220 can form a further branch.

[0122] If the type identifier of the bus node in the second intermediate step 220 indicates that the bus node is configured as a replacement bus node 815, 915, 917, 919, 1000, 1100, 1200 (j-branch of the second intermediate step 220), the replacement list 833, 933, 937, 939 of the replacement bus node 815, 915, 917, 919, 1000, 1100, 1200 is read in a third intermediate step 230 and compared with the target configuration. This can also be done according to the example explained above. The third intermediate step 230 can also form a branch. Reading the exchange list 833, 933, 937, 939 in the third intermediate step 230 can be carried out, for example, based on a third sent data packet.

[0123] If the third intermediate step 230 of the method according to the second embodiment 200 results in a match between the exchange list and the target configuration (j-branch of the third intermediate step 230), a third step 240 of the method according to the second embodiment 200 can be executed. The third step 240 of the method according to the second embodiment 200 can include, for example, that the corresponding bus subscriber has been recognized, for example, as the exchange bus subscriber 815. A fourth step 245 of the method according to the second embodiment 200 can include, for example, that the method for recognizing a exchange bus subscriber according to the second embodiment 200 is continued for the next bus subscriber physically connected to the bus system 810, for example the second original bus subscriber 825.If the comparison of the detected actual configuration based on the identification object in the first intermediate step 215 of the method according to the second embodiment 200 with the target configuration does not include a deviation from the target configuration (n-branch), the fourth step 245 can be executed, i.e. the method for recognizing a replacement bus subscriber according to the second embodiment 200 can be executed for the next bus subscriber physically connected to the bus system 810. If the type identifier of the bus subscriber in the second intermediate step 220 indicates that the bus subscriber is not configured as a replacement bus subscriber 815, 915, 917, 919, 1000, 1100, 1200 (n-branch of the second intermediate step 220), an error message can be generated in the fourth intermediate step 235.If the third intermediate step 230 of the method according to the second embodiment 200 results in a discrepancy between the exchange list and the target configuration (n-branch of the third intermediate step 230), an error message can be generated in the fourth intermediate step 235. The fourth intermediate step 235 can therefore correspond to the n-branch of the second intermediate step 220 and the third intermediate step 230, respectively.

[0124] It is understood that reading the aforementioned information, ie, sending the individual data packets, can be performed by the control bus user 830, 930. The fourth intermediate step 235 can also be performed by the control bus user 830, 930, and, for example, the initialization phase 201 can be aborted with an error message. Similarly, the third step 240 of the method according to the second embodiment 200 can be performed by the corresponding control bus user 830, 930.

[0125] It is understood that the above explanation also applies to the subsequent figures and vice versa. Figures 3 to 5 are explained together below. Fig. 3 shows a schematic representation of a method 300 for configuring an exchange bus participant 815, 915, 917, 919, 1000, 1100, 1200 according to a first embodiment. Fig. 4 shows a schematic representation of a method 400 for configuring an exchange bus participant 815, 915, 917, 919, 1000, 1100, 1200 according to a second embodiment, and Fig. 5 shows a schematic representation of a method 500 for configuring an exchange bus participant 815, 915, 917, 919, 1000, 1100, 1200 according to a third embodiment.

[0126] The configuration methods mentioned in the first to third embodiments

[0127] 300, 400, 500 in Figs. 3 to 5 can be carried out independently of the methods for detecting a replacement bus participant 815, 915, 917, 919, 1000, 1100, 1200 according to the first and second embodiments 100, 200 in Figs. 1 and 2. This is because fieldbus systems in automation technology are typically divided into systems in which, for example, an identification of the, for example, subordinate bus participants is actively read out by a control bus participant, i.e. the actual configuration of the automation network is recorded, and into systems in which, for example, the subordinate bus participants each independently check an identification and, if necessary, transmit a confirmation to the control bus participant. In the second case, the control bus participant does not actively read out any identification of the subordinate bus participants.The method for configuring a replacement bus participant according to the first to third embodiments 300, 400, 500 can therefore be applied independently. In the former case, the method for detecting a replacement bus participant 815, 915, 917, 919, 1000, 1100, 1200 according to the first and second embodiments 100, 200 can also be combined with the method for configuring it according to the first to third embodiments 300, 400, 500 and, for example, executed earlier.

[0128] The method for configuring an exchange bus subscriber 815, 915, 917, 919, 1000, 1100, 1200 according to the first embodiment 300 in Fig. 3 in an automation network 800, 900 according to Figs. 8, 9 comprises, in a first step 305, providing a target configuration of the automation network 800, 900 (as mentioned above). Furthermore, the first step 305 of the configuration method according to the first embodiment 300 can comprise providing an exchange bus subscriber 815, 915, 917, 919, 1000, 1100, 1200. If the method for detecting a replacement bus participant 815, 915, 917, 919, 1000, 1100, 1200 according to the first and second embodiments 100, 200 has preceded the method for configuration according to the first embodiment 300 in terms of execution, the target configuration can, for example, have already been provided to the control bus participant 830, 930 and / or the plurality of bus participants 805, 905.The corresponding replacement bus user 815, 915, 917, 919, 1000, 1100, 1200 can also have been identified as such and thus provided. If the aforementioned method for identifying a replacement bus user 815, 915, 917, 919, 1000, 1100, 1200 according to the first and second embodiments 100, 200 has not been previously performed, the target configuration can be provided, for example, to the control bus user 830, 930 and / or the plurality of bus users 805, 905.A second step 310 of the method for configuring a replacement bus user 815, 915, 917, 919, 1000, 1100, 1200 according to the first embodiment 300 comprises writing a replacement object for setting a function, i.e. a mode of operation of the replacement bus user 815, 915, 917, 919, 1000, 1100, 1200 with respect to the at least one original bus user that the replacement bus user 815, 915, 917, 919, 1000, 1100, 1200 is to replace, by sending a further data packet, e.g. a fourth data packet, to the plurality of bus users 805, 905. The replacement object can form a third communication object that comprises at least one data field, or the replacement object can be the above-mentioned first Identification object, i.e. the communication object that includes the above-mentioned one or more data fields for identifying a bus participant.

[0129] If the exchange object is designed as a separate third communication object, then in the configuration method according to the first embodiment 300, only the exchange object is written, while the identification object can be read as the first communication object. If the exchange object and the identification object form the same communication object, e.g., the same first communication object, then this, e.g., first communication object, can first be read, e.g., within the scope of the application of the method for recognizing an exchange bus participant 815, 915, 917, 919, 1000, 1100, 1200 according to the first and second embodiments 100, 200 in Figs. 1 and 2, e.g., by means of the above-mentioned first data packet or by means of the above-mentioned second and third data packets, and then be written within the scope of the configuration method according to the first embodiment 300. The writing can, for example, be based on the fourth data packet, which, for example,the control bus participant 830, 930 as a transmitter transmits to the majority of bus participants 805, 905.

[0130] For example, the exchange object or the identification object could be written according to the exchange list 833 of the exchange bus participant 815 in Fig. 8 to: product identifier PC2 and the first data word of the version number RL2. A similar procedure can be followed with the exchange bus participants 915, 917, 919 in Fig. 9. For the values ​​to be written for the exchange objects or the identification objects, reference is made to the exchange lists 933, 937, 939 of the exchange bus participants 915, 917, 919 in Fig. 9 (see description above). In the context of the above-mentioned application example, this could mean that the replacement bus participant 815 designed as a multifunction terminal is set with regard to its comprehensive interfaces so that, for example, two digital inputs are activated, provided that the original bus participant was designed as an input terminal with two comprehensive digital inputs, for example.The additional interfaces of the replacement 815 bus device, designed as a multifunction terminal, such as outputs, could also be activated at a later date if necessary. These would provide additional functions that the original bus device does not include.

[0131] Providing the target configuration in the first step 305 of the configuration method according to the first embodiment 300 in Fig. 3 can comprise sending the target configuration by means of a further, e.g. fifth, data packet to the plurality of bus participants 805, 905 of the automation network 800, 900 by the control bus participant 830, 930. This is particularly conceivable if the configuration method according to the first embodiment 300 has been carried out without prior detection of the bus participants, i.e. without recognition of a replacement bus participant 815, 915, 917, 919, 1000, 1100, 1200, so that the individual bus participants can carry out the comparison between the target and actual configuration themselves.

[0132] As already mentioned, before writing the exchange object or the identification object in the second step 310 of the configuration method according to the first embodiment 300, the method for detecting an exchange bus participant 815, 915, 917, 919, 1000, 1100, 1200 according to the first and second embodiments 100, 200 can be carried out according to the features described above for determining the actual configuration of the automation network 800, 900.

[0133] If the exchange object or the identification object has been written to a bus node that is not configured as an exchange bus node 815, 915, 917, 919, 1000, 1100, 1200, the functional configuration of this bus node remains unchanged. In other words, this means that the execution of the configuration method according to the first embodiment 300 in Fig. 3 specifically affects only one exchange bus node 815, 915, 917, 919, 1000, 1100, 1200, and not other bus nodes.

[0134] In contrast to Fig. 3, Fig. 4 shows a combination of the method for detecting a replacement bus participant 815, 915, 917, 919, 1000, 1100, 1200 according to the second embodiment 200 in Fig. 2 and the above-explained method for configuring the replacement bus participant 815, 915, 917, 919, 1000, 1100, 1200 according to the first embodiment 300 in a configuration method according to the second embodiment 400 with a higher level of detail. The first step 405 and the second step 410 of the configuration method according to the second embodiment 400 can be designed similarly to the first and second steps 305, 310 of the configuration method according to the first embodiment 300 in Fig. 3. Therefore, reference is made to the above explanation.

[0135] Between the first and second steps 405, 410 of the configuration method according to the second embodiment 400, the individual steps of the method for detecting an exchange bus participant 815, 915, 917, 919, 1000, 1100, 1200 according to the second embodiment 200 can be carried out. If the target configuration is located in the exchange list 833, 933, 937, 939 of the respective exchange bus participant 815, 915, 917, 919, 1000, 1100, 1200 in Figs. 8 and 9 or if the target configuration matches the exchange list 833, 933, 937, 939, and the exchange bus participant 815, 915, 917, 919, 1000, 1100, 1200 has been identified as such, the second step 410 of the configuration method according to the second embodiment 400 is carried out, i.e. the writing of the exchange object or the identification object, for example by the control bus participant 830, 930.If the target configuration is not found in the respective exchange list 833, 933, 937, 939 of the corresponding exchange bus participant 815, 915, 917, 919, 1000, 1100, 1200, the fourth intermediate step 235 of the detection method according to the second embodiment 200 would be executed, namely the error message would be generated and the control bus participant 830, 930 would, for example, abort the initialization phase 201.

[0136] If the second step 410 of the configuration method according to the second embodiment 400 has been successfully carried out, the control bus participant 830, 930 can, for example, carry out the fourth step 245 of the method for detecting a replacement bus participant 815, 915, 917, 919, 1000, 1100, 1200 according to the second embodiment 200, that is to say continue the initialization phase 201 with the next bus participant.

[0137] A first and second step 505, 510 of the method for configuring an exchange bus subscriber 815, 915, 917, 919, 1000, 1100, 1200 according to the third embodiment 500 in Fig. 5 can be designed similarly to the first and second step 305, 310 of the method 300 for configuring an exchange bus subscriber 815, 915, 917, 919, 1000, 1100, 1200 according to the first embodiment 300 in Fig. 3, therefore reference is made to the above explanation. It is conceivable that the exchange object or the identification object has been written in the second step 510 of the method for configuring an exchange bus participant 815, 915, 917, 919, 1000, 1100, 1200 according to the third embodiment 500 and no method for identifying an exchange bus participant 815, 915, 917, 919, 1000, 1100, 1200 according to the first and second embodiments 100, 200 has been carried out according to the above-mentioned features.In this case, the replacement bus subscriber 815, 915, 917, 919, 1000, 1100, 1200 can be configured to perform a check of the support of the function of at least one original bus subscriber, for example, taking into account the replacement object or the identification object, in a third step 515 of the configuration method according to the third embodiment 500. This can be carried out, for example, by reading or comparing with the exchange list 833, 933, 937, 939 of the corresponding replacement bus subscriber 815, 915, 917, 919, 1000, 1100, 1200. The third step 515 of the configuration method according to the third embodiment 500 can form a branch in this case.

[0138] In a fourth step 517 of the configuration method according to the third embodiment 500, the exchange bus participant 815, 915, 917, 919, 1000, 1100, 1200 can transmit a confirmation 517 of the configuration of the function of the exchange bus participant 815, 915, 917, 919, 1000, 1100, 1200 to the control bus participant 830, 930, provided that the check of the exchange object or the identification object in the third step 515 of the configuration method according to the third embodiment 500 was successful (j-branch of the third step 515 of the method according to the third embodiment 500). Furthermore, it is conceivable that the exchange bus participant 815, 915, 917, 919, 1000, 1100, 1200 activates the function according to the exchange object.Otherwise (n- branch of the third step 515 of the method according to the third embodiment 500), the exchange bus participant 815, 915, 917, 919, 1000, 1100, 1200 can execute a fifth step 535 of the method according to the third embodiment 500, i.e. transmit an error message to the control bus participant 830, 930.

[0139] Figures 6 and 7 are described together below. Fig. 6 shows a schematic representation of a method for activating a function, i.e. a mode of operation of an exchange bus participant 815, 915, 917, 919, 1000, 1100, 1200 according to a first embodiment 600, and Fig. 7 shows a schematic representation of a method for activating a function, i.e. a mode of operation of an exchange bus participant 815, 915, 917, 919, 1000, 1100, 1200 according to a second embodiment 700. The two methods for activating the function according to the first and second embodiments 600, 700 can, for example, each be carried out by the exchange bus participants 815, 915, 917, 919, 1000, 1100, 1200 as receivers. The methods for activating a function according to the first and second embodiments 600, 700 each comprise receiving an exchange object (writing) in a first step 605, 705.Writing the exchange object for the corresponding exchange bus subscriber 815, 915, 917, 919, 1000, 1100, 1200 can be done, for example, using the fourth data packet mentioned above. However, this is not to be understood as restrictive. The exchange object, as mentioned above, can form the third communication object, which includes at least one data field for setting the function of the exchange bus subscriber 815, 915, 917, 919, 1000, 1100, 1200 with respect to at least one original bus subscriber, and / or the exchange object can be designed as the identification object and form the same first communication object according to the above features with one or more data fields for identifying a bus subscriber. Reference is made to the above description at this point.

[0140] In a second step 610, 710 of the method for activating a function according to the first and second embodiments 600, 700, the replacement bus device 815, 915, 917, 919, 1000, 1100, 1200 can check whether the replacement bus device 815, 915, 917, 919, 1000, 1100, 1200 supports a function of at least one original bus device. This check can be performed, for example, taking into account the replacement object and / or the identification object. The testing in the second step 610, 710 of the methods for activating a function according to the first and second embodiments 600, 700 is shown as a branch in Fig. 6 and 7. If the testing in the second step 610, 710 of the methods for activation according to the first and second embodiments 600, 700, i.e. the branches in Fig.6 and 7, has been successfully carried out (j-branch of the second step 610, 710 of the activation methods according to the first and second embodiments 600, 700), an exchange bus participant 815, 915, 917, 919, 1000, 1100, 1200 can, in a third step 615, 715 of said activation methods 600, 700, respectively, activate the function of the exchange bus participant 815, 915, 917, 919, 1000, 1100, 1200 according to the exchange object and / or according to the identification object. The activation of the function can, for example, be carried out as explained in connection with Figs. 3 to 5, i.e. the activation, for example, of the 2 digital inputs of the replacement bus participant 815 designed as a multifunctional terminal for the original bus participant not shown in Fig. 8, which can, for example, be designed as an input terminal (comprising two digital inputs).If the replacement bus user 815, 915, 917, 919, 1000, 1100, 1200 determines during the test in the second step 610, 710 of the activation methods 600, 700 that it does not support the function of the at least one original bus user (n-branch of the second step 610, 710 of the methods 600, 700), the replacement bus user 815, 915, 917, 919, 1000, 1100, 1200 can execute a fourth step 635 of the activation method according to the first embodiment 600 or a fifth step 735 of the activation method according to the second embodiment 700, which in each case can include an error message, for example to the control bus user 830, 930. The error message can be transmitted via the bus system 810, 910, i.e. the fieldbus, e.g. the EtherCAT fieldbus.

[0141] The activation method according to the second embodiment 700 in Fig. 7 differs from the activation method according to the first embodiment 600 in Fig. 6 only in that it comprises a fourth step 717 following the third step 715 of the activation method according to the second embodiment 700, wherein the fourth step 717 comprises sending a confirmation of the activation of the function of the exchange bus participant 815, 915, 917, 919, 1000, 1100, 1200.

[0142] Figures 10 to 12 are described together below. Fig. 10 shows a schematic representation of a replacement bus subscriber 1000 according to a first embodiment, Fig. 11 shows a schematic representation of a replacement bus subscriber 1100 according to a second embodiment, and Fig. 12 shows a schematic representation of a replacement bus subscriber 1200 according to a third embodiment. For example, the replacement bus subscribers 1000, 1100 according to the structure of Figures 10 and 11 can be used in the automation network 800 in Fig. 8 to replace a single original bus subscriber, while the replacement bus subscriber 1200 according to the structure of Fig. 12 can be used in the automation network 900 in Fig. 9 to functionally replace several original bus subscribers.

[0143] The exchange bus participant with the structure according to the first to third embodiments 1000, 1100, 1200 in Figs. 10 to 12 has at least one communication unit 1005, 1105, 1205, 1207, 1209, which is communicatively connected to at least one memory unit 1010, 1110, 1210, 1211, 1213 of the exchange bus participant according to the first to third embodiments 1000, 1100, 1200. Specifically, the replacement bus participants according to the first and second embodiments 1000, 1100 in Figs. 10 and 11 each have a communication unit 1005, 1105, while the replacement bus participant according to the third embodiment 1200 in Fig. 12 has, for example, a first to third communication unit 1205, 1207, 1209 in order to be able to replace a first to third original bus participant.It is understood that in the case of a different implementation, i.e. when more than three original bus participants are replaced by an exchange bus participant 915, 917, 919 or fewer than three original bus participants, the number of communication units 1205, 1207, 1209 in Fig. 12 can also vary.

[0144] The memory unit 1010, 1110, 1210, 1211, 1213 comprises, for example, a non-volatile memory and can each be embodied as a so-called ESI-EEPROM. The exchange bus participants according to the first and second embodiments 1000, 1100 in Figs. 10 and 11 each comprise a memory unit 1010, 1110 embodied as an ESI-EEPROM, and the exchange bus participant according to the third embodiment 1200 in Fig. 12 comprises three memory units 1210, 1211, 1213 embodied as ESI-EEPROMs.

[0145] The communication units 1005, 1105, 1205, 1207, 1209 of the exchange bus participants according to the first to third embodiments 1000, 1100, 1200 are communicatively connected to the bus system 810, 910. The communicative connection can enable bidirectional communication between the bus participants. If the bus system is configured as a fieldbus system, specifically an EtherCAT fieldbus system, or if the automation network 800, 900 is configured as an EtherCAT automation network, the communication units 1005, 1105, 1205, 1207, 1209 of the exchange bus participants according to the first to third embodiments 1000, 1100, 1200 are configured as EtherCAT SubDevice Controllers (ESCs for short).

[0146] The replacement bus subscriber according to the second and third embodiments 1100, 1200 in Figs. 11 and 12 further comprises a microcontroller unit 1115, 1215, in contrast to the replacement bus subscriber according to the first embodiment 1000 in Fig. 10. The microcontroller unit 1115, 1215 can be designed as a microcontroller (pC for short) or can comprise a microcontroller. The microcontroller unit 1115, 1215 is communicatively connected to the communication unit 1105, 1205, 1207, 1209 for checking the support of the function of at least one original bus subscriber, e.g., taking into account the replacement object according to the methods for activating a function according to the first and second embodiments 600, 700 in Figs. 6 and 7, and for writing the replacement object and / or the identification object.In other words, the test in the second step 610, 710 of the activation methods according to the first and second embodiments 600, 700 is performed by the microcontroller unit 1115, 1215. The communicative connection between the microcontroller unit 1115, 1215 and the communication unit 1105, 1205, 1207, 1209 can be established via a serial or parallel interface on the communication unit 1105, 1205, 1207, 1209. The exchange bus participant according to the first embodiment 1000 does not include a microcontroller unit; therefore, the exchange object or the identification object can be implemented more simply in this case, for example, than the above explanation.

[0147] Preferably, the exchange bus user 815 in Fig. 8 and the first to third exchange bus users 915, 917, 919 in Fig. 9 are designed according to Fig. 11 (for the exchange bus user 815 in Fig. 8) and according to Fig. 12 (for the first to third exchange bus users 915, 917, 919 in Fig. 9).

[0148] The exchange bus participant according to the second and third embodiments 1100, 1200 in Figs. 11 and 12 each comprises an object directory 1120, 1220. The identification object and / or the exchange object can be stored as a communication object to be written or as independent communication objects to be written in the object directory 1120, 1220. The type identifier can also be stored in the object directory 1120, 1200 if configured as an independent second communication object. Furthermore, the exchange list 833, 933, 937, 939 can be stored in the object directory 1120, 1200. For example, the object dictionary 1120, 1220 may be part of the microcontroller unit 1115, 1215, wherein the microcontroller unit 1115, 1215 may, for example, have a microcontroller memory that includes the object dictionary 1120, 1220.

[0149] It is understood that the original bus subscriber may have a similar structure to the replacement bus subscriber according to the first embodiment 1000 in Fig. 10 or to the replacement bus subscriber according to the second embodiment 1100 in Fig. 11.

[0150] The exchange bus devices 815, 915, 917, 919, 1000, 1100, 1200 shown in Figs. 8 to 12 can each be configured as subordinate devices, i.e., as subordinate bus devices that can be controlled by a main device, i.e., the control bus device 830, 930. If the exchange bus device 815, 915, 917, 919, 1000, 1100, 1200 is configured as a subordinate device, the communication unit 1005, 1105, 1205, 1207, 1209, as already mentioned, is configured as an EtherCAT Subdevice Controller (ESC). The exchange bus device 1200 shown in Fig. 12 according to the third embodiment can, for example, form a terminal with multiple physical connections (interfaces). It is understood, however, that the exchange bus participant 815, 915, 917, 919, 1000, 1100, 1200 according to the third embodiment 1200 is not limited to the embodiment explained.

[0151] The determination of the actual configuration in the second step 110, 210 of the method for detecting an exchange bus participant 815, 915, 917, 919, 1000, 1100, 1200 according to the first and second embodiment 100, 200 in Fig. 1, 2, which is carried out by reading the first data field and / or the second data field and / or the third data field of the identification object, can preferably be carried out by reading the memory unit 1110, 1210, 1211, 1213, which is designed as an ESI-EEPROM, for example, by means of a first data packet, which comprises the identification object.

[0152] It is also conceivable to carry out the combined method for configuring an exchange bus participant 815, 915, 917, 919, 1000, 1100, 1200 according to the second embodiment 400 in Fig. 4, which also includes steps of the method for detecting an exchange bus participant 815, 915, 917, 919, 1000, 1100, 1200 according to the second embodiment 200, by reading the memory unit 1110, 1210, 1211, 1213 designed as an ESI-EEPROM as described above. Furthermore, it is conceivable to read the type identifier, for example in the second intermediate step 220 of the method 200 for identifying a replacement bus participant 815, 915, 917, 919, 1000, 1100, 1200 according to the second embodiment 200 in Fig. 2, by reading the memory unit 1110, 1210, 1211, 1213 designed as an ESI-EEPROM. The same applies to the method for configuring a replacement bus participant 815, 915, 917, 919, 1000, 1100, 1200 according to the second embodiment 400 in Fig.4, comprising the second intermediate step 220. Furthermore, it is conceivable to perform the reading of the exchange list 833, 933, 937, 939 in the third intermediate step 230 of the method for identifying an exchange bus participant 815, 915, 917, 919, 1000, 1100, 1200 according to the second embodiment 200, 400 in Fig. 2 by reading the memory unit 1110, 1210, 1211, 1213 designed as an ESI-EEPROM. The same applies to the method for configuring an exchange bus participant 815, 915, 917, 919, 1000, 1100, 1200 according to the second embodiment 400 in Fig. 4, comprising the third intermediate step 230.

[0153] The exchange list 833, 933, 937, 939 can alternatively also be found in the object directory 1120,

[0154] 1220. Then, in the alternative, when reading the exchange list 833, 933, 937, 939, the object directory 1120, 1220 of the exchange bus participant 1100, 1200 would be read, instead of the memory unit 1110, 1210, 1211, 1213 designed as an ESI EEPROM.

[0155] The writing of the exchange object and / or the identification object, for example in the second step 410 of the method for configuring an exchange bus participant 815, 915, 917, 919, 1000, 1100, 1200 according to the second embodiment 400 in Fig. 4, can be carried out from the object directory 1120, 1220, for example by the control bus participant 830, 930. Alternatively, the writing of the exchange object and / or the identification object, for example in the second step 410 of the method for configuring an exchange bus participant 815, 915, 917, 919, 1000, 1100, 1200 according to the second embodiment 400 in Fig. 4, could also include the writing of the memory unit 1110, 1210, 1211, 1213, which is designed, for example, as an ESI-EEPROM.

[0156] The invention has been described in detail using preferred embodiments. Instead of the described embodiments, further embodiments are conceivable, which may include further modifications or combinations of the described features. For this reason, the invention is not limited to the disclosed examples, since other variations may be derived therefrom by a person skilled in the art without departing from the scope of the invention.

[0157] List of reference symbols

[0158] 100 Method for detecting an exchange bus participant according to a first embodiment

[0159] 105 first step

[0160] 110 second step

[0161] 115 third step

[0162] 200 Method for detecting an exchange bus participant according to a second embodiment

[0163] 201 Initialization phase

[0164] 205 first step

[0165] 210 second step

[0166] 215 first intermediate step

[0167] 220 second intermediate step

[0168] 230 third intermediate step

[0169] 235 fourth intermediate step

[0170] 240 third step

[0171] 245 fourth step

[0172] 300 Method for configuring an exchange bus participant according to a first embodiment

[0173] 305 first step

[0174] 310 second step

[0175] 400 Method for configuring an exchange bus participant according to a second embodiment

[0176] 405 first step

[0177] 410 second step

[0178] 500 Method for configuring an exchange bus participant according to a third embodiment

[0179] 505 first step

[0180] 510 second step

[0181] 515 third step

[0182] 517 fourth step

[0183] 535 fifth step 600 Method for activating a function, i.e. a mode of operation of an exchange bus participant according to a first embodiment

[0184] 605 first step

[0185] 610 second step

[0186] 615 third step

[0187] 635 fourth step

[0188] 700 Method for activating a function, i.e. a mode of operation of an exchange bus participant according to a second embodiment

[0189] 705 first step

[0190] 710 second step

[0191] 715 third step

[0192] 717 fourth step

[0193] 735 fifth step

[0194] 800 Automation network according to a first embodiment

[0195] 805 majority of bus participants

[0196] 810 bus system

[0197] 815 exchange bus participants

[0198] 820 first original bus participants

[0199] 825 second original bus participant

[0200] 830 control bus participants

[0201] 833 Exchange list

[0202] 900 Automation network according to a second embodiment

[0203] 905 majority of bus participants

[0204] 910 bus system

[0205] 915 first exchange bus participants

[0206] 917 second exchange bus participant

[0207] 919 third exchange bus participant

[0208] 930 control bus participants

[0209] 933 first exchange list

[0210] 937 second exchange list

[0211] 939 third exchange list

[0212] 1000 Exchange bus participants according to a first embodiment 1005 Communication unit

[0213] 1010 storage unit

[0214] 1100 exchange bus participants according to a second embodiment

[0215] 1105 Communication Unit

[0216] 1110 storage unit

[0217] 1115 Microcontroller unit

[0218] 1120 Object directory

[0219] 1200 exchange bus participants according to a third embodiment

[0220] 1205 first communication unit

[0221] 1207 second communication unit

[0222] 1209 third communication unit

[0223] 1210 first storage unit

[0224] 1211 second storage unit

[0225] 1213 third storage unit

[0226] 1215 microcontroller unit

[0227] 1220 Object directory

Claims

Patent claims 1. A method (100, 200) for initializing an automation network, wherein the automation network (800, 900) has a plurality of bus participants (805, 905), comprising the steps: Providing a target configuration of the automation network that contains identification objects assigned to the bus participants, Determining an actual configuration of the automation network (800, 900), wherein for each bus subscriber, the identification object assigned to the bus subscriber in the target configuration is compared with an identification object read from the bus subscriber, wherein, if there is a discrepancy between the identification objects, it is determined on the basis of a type identifier read from the bus subscriber whether the bus subscriber is a replacement bus subscriber, wherein, if the type identifier indicates that the bus subscriber is a replacement bus subscriber, it is determined on the basis of an exchange list read from the bus subscriber whether the original bus subscriber can be replaced by the replacement bus subscriber, and Triggering an error condition and aborting the initialization if no permitted actual configuration is found when determining the actual configuration.

2. The method according to claim 1, wherein the exchange list indicates which bus participants can be functionally replaced by an exchange bus participant.

3. The method according to claim 1 or 2, wherein, if the replacement list indicates that the replacement bus subscriber can replace the original bus subscriber, a replacement object that specifies how the replacement bus subscriber is to operate functionally, in particular with respect to the functions of the original bus subscriber, is written into the replacement bus subscriber.

4. The method according to claim 3, wherein the replacement object comprises the identification object of the original bus participant that the replacement bus participant replaces.

5. Method according to one of claims 1 to 4, wherein the identification object forms a first communication object which contains one or comprises a plurality of data fields for identifying a bus subscriber, wherein the identification object has as a data field a product identifier of the bus subscriber, a version number of the bus subscriber, and / or a manufacturer identifier of the bus subscriber.

6. The method according to claim 5, wherein a data field of the identification object is designed as a version number of the bus subscriber, wherein the version number has a first data word and a second data word, wherein the replacement bus subscriber (815, 915, 917, 919, 1000, 1100, 1200) in the replacement list (833, 933, 937, 939) contains a data field with a version number, wherein the version number has a first data word and a second data word, wherein a version number comparison is carried out between the original bus subscriber and the replacement bus subscriber, wherein, if the original bus subscriber is replaceable by the replacement bus subscriber, the first data word must match and the second data word is larger or equal to the actual configuration than the target configuration.

7. Replacement bus subscriber (815, 915, 917, 919, 1000, 1100, 1200) for replacing an original bus subscriber for an automation network (800, 900), which is designed to carry out a method according to one of claims 1 to 6.

8. Exchange bus participant according to claim 7, wherein the exchange bus participant (815, 915, 917, 919, 1000, 1100, 1200) comprises at least one communication unit (1005, 1105, 1205, 1207, 1209) which is communicatively connected to at least one memory unit (1010, 1110, 1210, 1211, 1213) of the exchange bus participant (815, 915, 917, 919, 1000, 1100, 1200), wherein the memory unit (1010, 1110, 1210, 1211, 1213) comprises in particular a non-volatile memory, wherein the communication unit (1005, 1105, 1205, 1207, 1209) is communicatively connected to a bus system (810, 910).

9. Exchange bus participant according to claim 8, wherein the exchange bus participant (815, 915, 917, 919, 1100, 1200) further comprises a microcontroller unit (1115, 1215) communicatively connected to the communication unit (1105, 1205, 1207, 1209) for checking the exchange object and / or the identification object, and wherein the exchange bus participant (815, 915, 917, 919, 1100, 1200) comprises an object directory (1120, 1220), wherein the identification object and / or the exchange object can be stored in the object directory (1120, 1220).

10. An automation network (800, 900) comprising a plurality of bus subscribers (805, 905) communicatively interconnected via a bus system (810, 910), wherein at least one bus subscriber of the plurality of bus subscribers (805, 905) is configured as a replacement bus subscriber (815, 915, 917, 919, 1000, 1100, 1200) for replacing an original bus subscriber according to one of claims 7 to 9.

11. An automation network (800, 900) according to claim 10, wherein, during the initialization phase of the automation network, a control bus subscriber checks the correspondence between the target and actual configurations of the bus subscribers by reading the identification objects of the bus subscribers.

12. Automation network (800, 900) according to claim 11, wherein the automation network (800, 900) forms an EtherCAT automation network.

Images