Configuration of slave devices in industrial network systems

Abstract

To provide a method for configuring SDs in a communication system comprising a master device (MD) and slave devices (SD).SOLUTION: An MD and SDs are connected in chain via a commission line (CL) and in parallel via a field bus line (FBL). Each SD is indexed, and the SD of index 1 is connected to the MD to enroll the SD of index k (k being equal to or greater than 1). The MD sends, in broadcast via the FBL, an address configuration frame containing instructions for address configuration with a defined address (Add_k) of index k for the SD of index k, and sends, in broadcast via the FBL after having received a reply containing device information and the Add_k, a command for sending a commissioning signal via the CL to the SD of index k+1.SELECTED DRAWING: Figure 2

Description

Technical Field

[0001] The present invention relates to a network system including a serial bus slave device controlled by a master device. Specifically, the present invention relates to the configuration of slave devices during a configuration phase, such as during startup of a network system.

Background Art

[0002] In a wired communication network, it is necessary to assign addresses to slave devices (or nodes) present / added in the network. This can be done manually, but this approach takes a long time, is prone to input errors, and requires expertise from an operator who manually assigns addresses to slave devices.

[0003] Such a communication network can form a wireless gateway device that manages different wireless modules as slave devices that implement mixed critically important applications using various wireless protocols integrated modularly within the same gateway device. These wireless modules can use Zigbee, Bluetooth, and IO-Link wireless-based industrial IoT (Internet of Things), industrial control applications, but can also be used for other applications.

Summary of the Invention

Problems to be Solved by the Invention

[0004] Therefore, there is a need to scale up or scale down the deployment of slave devices in a communication system for Industry 4.0 applications in a flexible plug-and-play manner.

Means for Solving the Problems

[0005] This summary is provided to introduce the concept relating to the inventive subject matter. This summary does not identify essential features of the claimed subject matter, nor does it determine or limit the scope of the claimed subject matter.

[0006] A method is provided for configuring a slave device in a communication system comprising a master device and slave devices in one implementation form, wherein the master device and slave devices are connected in a chain via a commission line and in parallel via a fieldbus line, each slave device is indexed by one or more indices, the slave device with index 1 is connected to the master device to register the slave device with index k, where k is 1 or more, and the method includes operations performed by the master device, the operations being, In a broadcast over a fieldbus line, an address configuration frame containing an instruction for address configuration having the defined address of index k for the slave device of index k is transmitted, Sending a request for device information via a broadcast over a fieldbus line, wherein the request includes a defined address. After receiving a response containing device information and a defined address, a command is sent via a broadcast over the fieldbus line to the slave device at index k+1, through the commission line, to transmit a commissioning signal, wherein the command includes the defined address. The received device information is stored in an information table, wherein the device information includes the identifier of the slave device at index k and the type of the slave device at index k. The slave devices have a common default address before registration, and only the slave device at index k that has a common default address and detects a commissioning signal on the commission line receives an address configuration frame to change the common default address of the slave device at index k to the defined address.

[0007] Since the slave devices are connected in a chain via a commission line, it is advantageous that each slave device is registered one by one, and the registration of each slave device is initiated by receiving a commissioning signal on the commission line from the previous slave device in the chain that was registered. All slave devices are plug-and-play with no manual configuration required.

[0008] The method is advantageous because it allows for a flexible, plug-and-play approach, enabling the scaling up or down of deployments of wireless sensor or control devices, such as slave devices for Industry 4.0 applications (e.g., digital plants).

[0009] In one embodiment, the master device sends a commissioning signal to the slave device at index 1 on the commission line before sending an address configuration frame in a broadcast over the fieldbus line in order to register the slave device at index 1.

[0010] In the embodiment, the master device receives an acknowledgment frame before sending a request for device information, the acknowledgment frame includes a defined address, and the request includes a defined address.

[0011] In one embodiment, the registration of a slave device is terminated when the master device does not receive an acknowledgment frame containing a defined address from the slave device.

[0012] In one embodiment, during the startup of a communication system for addressing the slave device at index k, the master device transmits an address configuration frame in a broadcast over a fieldbus line, which includes an address configuration command having a defined address at index k and an identifier for the slave device at index k.

[0013] In one embodiment, during the startup of the communication system, the slave devices have a common default address, and the slave device at index k that receives the address configuration frame receives the address configuration frame in order to change the common default address of the slave device at index k to a defined address.

[0014] In one embodiment, the master device identifies the slave device at index k as a faulty device if, after sending an address configuration frame containing an instruction for address configuration having a defined address at index k and an identifier for the slave device at index k, it does not receive an acknowledgment frame containing the defined address.

[0015] In this embodiment, the master device compares the signature of the configuration data stored in each slave device with the signature of the configuration data stored in the master device, and if the signatures are different, it synchronizes the configuration data stored in the slave device with the configuration data stored in the master device.

[0016] In one embodiment, when a new slave device with index n+1 is placed in the communication system during runtime, the new slave device is connected to the last slave device with index k in the communication system, where k is equal to n. The master device initiates the registration process by sending a command to enable the commission line in a broadcast on the fieldbus line so that each previously registered slave device with index k sends a commissioning signal on the commission line to the next slave device with index k+1. The master device then performs the steps of sending an address configuration frame with a defined address with index n+1, sending a request for device information with a defined address with index n+1, sending a command with a defined address with index n+1, and storing the received device information.

[0017] In one embodiment, when a new slave device replaces a failed slave device, replacement registration is initiated in the master device. The master device performs the steps of sending an address configuration frame (S2), sending a request for device information (S3), sending a command (S4), and storing the received device information (S5). The master device then uses an information table, the identifier of the new slave device, and the identifier of the failed slave device to detect that the new slave device has replaced the failed slave device.

[0018] In one embodiment, when a new slave device replaces a failed slave device, where the configuration data for the slave device is stored in the master device corresponding to the identifier of the failed slave device and the type of the failed slave device, and the new slave device and the failed slave device are of the same type, the master device uses the configuration data of the failed device to restore the configuration data for the new slave device.

[0019] Even if one slave device, such as a wireless module, fails, continuity of operation is guaranteed, and the replacement of the failed slave device requires no effort from the customer through automatic synchronization and configuration restoration, which is advantageous.

[0020] In other implementations, a master device is provided to configure slave devices in a communication system comprising a master device and slave devices, the master device and slave devices are connected in a chain via a commission line and in parallel via a fieldbus line, each slave device is indexed by one or more indices, the slave device with index 1 is connected to the master device to register the slave device with index k, where k is 1 or greater, and the master device is, A plurality of network interfaces for communicating with a slave device, A processor coupled to a network interface and configured to run one or more processes, Memory configured to store processes that can be executed by the processor and The process is equipped with, and when executed, In a broadcast through a field bus line, transmitting an address configuration frame including an instruction for an address configuration having a defined address of index k for a slave device of index k; In a broadcast through a field bus line, transmitting a request for device information, the request including a defined address; After receiving a response including device information and a defined address, in a broadcast through a field bus line, transmitting a command to transmit a commissioning signal through a commissioning line to a slave device of index k + 1, the command including a defined address; Storing the received device information in an information table, the device information including an identifier of a slave device of index k and a type of the slave device of index k; Operable to perform the above, the slave device has a common default address before being registered, and only the slave device of index k having the common default address and detecting a commissioning signal on the commissioning line receives an address configuration frame for changing the common default address of the slave device of index k to a defined address.

[0021] In other implementations, there is provided a computer-readable medium having a computer program for performing a method of configuring a slave device in a communication system including a master device and a slave device. The computer program comprises instructions for performing steps according to the method of the present invention.

[0022] In other implementations, there is provided a system including a master device and a plurality of slave devices chain-connected to the master device.

[0023] The detailed description will be given with reference to the accompanying drawings. In the drawings, the leftmost digit of a reference number identifies the figure in which that reference number first appears. The same numbers are used throughout the figures to refer to like features and components. Next, some embodiments of the system and / or method according to the embodiments of the present subject matter will be described by way of example only with reference to the accompanying drawings.

Brief Description of the Drawings

[0024] [Figure 1] FIG. 8 is a schematic block diagram of a communication system according to an embodiment of the present invention for configuring a slave device within an industrial network system. [Figure 2] FIG. 11 is a flow chart showing a method for configuring a slave device within an industrial network system according to an embodiment of the present invention.

Modes for Carrying Out the Invention

[0025] The same reference numbers represent the same elements or the same type of elements on all the drawings.

[0026] It should be understood by those skilled in the art that any block diagrams herein represent conceptual views of exemplary systems embodying the principles of the present subject matter. Similarly, any flow charts, flow diagrams, state transition diagrams, pseudocode, etc. represent various processes that may be substantially represented within a computer-readable medium and that can be executed by a computer or processor, whether or not such a computer or processor is explicitly shown.

[0027] The figures and the following description illustrate specific exemplary embodiments of the present invention. Therefore, the parties will be able to devise various configurations that, while not expressly stated or shown herein, embody the principles of the present invention and fall within its scope. Furthermore, any examples described herein are intended to aid in understanding the principles of the present invention and should be construed as not being limited to such specifically enumerated examples and conditions. Consequently, the present invention is limited by the "Claims" and their equivalents, rather than by any specific embodiments or examples described below.

[0028] Referring to Figure 1, the communication system comprises a master device MD and a slave device SD. The slave device SD forms a plurality of N slave devices SD (SD.1, SD.k-1, SD.k, ..., SD.N), where N is an integer greater than or equal to 2, and k is an index that varies between 1 and N. Each slave device is indexed by an index greater than or equal to 1, and the slave device with index 1 is connected to the master device.

[0029] The master device MD is connected to a chain of slave devices SD via the commission line CL and the fieldbus line FBL. The slave devices SD form a "daisy" chain via the commission line CL.

[0030] The commission line CL is a unidirectional signal transmission line that carries the commissioning signal. When the slave device SD detects the commissioning signal from the commission line CL and receives a commissioning request from the master device, the slave device SD enters the commissioning state.

[0031] For example, the commissioning signal can be a clock signal, a code signal, or any signal containing a specific pattern. If the commissioning signal is a clock signal of a specific frequency, the slave device will only enter the commissioning state if it receives a signal containing such a specific frequency clock from the commission line CL.

[0032] The fieldbus line (FBL) can be a half-duplex fieldbus such as RS485 or I2C for communication between a master device (MD) and a slave device (SD).

[0033] The slave device SD is a communication module that uses an application, a dedicated sensor, and a communication protocol. In one embodiment, the slave device SD is a wireless module that uses Zigbee, Bluetooth, WiFi, and IO-Link wireless-based industrial IoT (Internet of Things). The master device MD and the slave device SD form a wireless gateway device that manages mixed critically important applications using various wireless protocol radios modularly integrated within the same gateway device. In one embodiment of an industrial application, the slave device SD is arranged stacked on top of the master device, forming a wireless gateway system in the form of a column.

[0034] By default, all slave devices may initially have a common default address, such as 0XFE.

[0035] The master device (MD) can initiate a registration process that runs during the commissioning of installed slave devices, i.e., during wireless gateway commissioning. The registration process registers the slave devices sequentially and can automatically terminate when the registration of the last slave device in the system is complete. The master device can then create an information table containing the slave device information and store it in local memory, such as NVM (non-volatile memory).

[0036] The master device MD may send a commissioning signal on the commission line CL at the start of the registration process. The commissioning signal is sent to the first slave device connected to the master device.

[0037] The master device MD can transmit an address configuration frame in a broadcast on the fieldbus line FBL. The address configuration frame contains instructions for address configuration, which have a defined address for the slave device at index k.

[0038] After the master device MD receives an acknowledgment for a defined address from the slave device at index k on the fieldbus line FBL, the master device MD can send a request for device information via broadcast on the fieldbus line FBL, the request containing the defined address. Only the slave device at index k, which acknowledged the previous address configuration frame, will process the request.

[0039] After the master device MD receives device information on the fieldbus line FBL, the master device MD can send a command to enable the commission line CL from the slave device at index k to the slave device at index k+1. The slave device at index k is then ready to send a commissioning signal on the commission line CL to the next slave device at index k+1.

[0040] The master device MD can then store the device information of the slave device at index k in its information table. The device information includes, for example, the name of the slave device at index k, the identifier of the slave device at index k, and the type of the slave device at index k. The slave device identifier can be a unique serial number stored in the slave device's memory during manufacturing. The slave device type can be a support function code stored in the slave device's memory during manufacturing. Slave devices having the same one or more functions are designed to use slave devices of the same type.

[0041] To continue the registration process, the master device MD can broadcast on the fieldbus line FBL an address configuration frame with a defined address for the slave device at index k+1, a request for device information, and then a command to enable the commission line CL from the slave device at index k+1 to the slave device at index k+2. The master device MD can then store the device information for the slave device at index k+1 in its information table.

[0042] The master device MD continues the registration process for each slave device and terminates the registration process after it no longer receives an acknowledgment from the slave device for the defined address.

[0043] The slave device sets its local fieldbus address to define a preset value such as the hexadecimal value "FF" and sets the commission line CL to signal low at startup. Only slave devices that have a default fieldbus address and detect the commissioning signal on the commission line CL can receive the address commissioning frame.

[0044] After the registration process is complete, the master device (MD) stores the device information in a table. During the next startup, the address is lost, and the master device (MD) needs to send an address configuration command to the slave device again.

[0045] In one embodiment, an address configuration frame from the master device MD includes a unique address and an identifier for the slave device at index k to change the common default address of the slave device at index k. These instructions are for the slave device at index k (other slave devices ignore the frame because the identifier does not match). The unique address can have the same format as the common default address (e.g., a number and two letters), and the slave device index k can be coded as 101.k. For example, the address of the first slave device at index 1 could be, for example, 0XAA or 0X01. The unique address at index k may be included in the command payload.

[0046] In the next startup, if there is a failed slave device, the master will no longer receive an acknowledgment of an address configuration frame from that failed slave device. The master device can then detect the location and identifier of the failed slave device, not only to support easy and quick troubleshooting, but also to keep the communication system running with the remaining healthy slave devices that continue to function properly.

[0047] The master device MD can also detect new slave modules that have been added to a stack, for example, formed by slave devices connected to the communication system. After a new slave device is hot-plugged into the communication system, the master device MD may restart the registration process by broadcasting a command to enable the commission line CL on the fieldbus line FBL. Each previously registered slave device at index k is then ready to send a commissioning signal on the commission line CL to the next slave device at index k+1.

[0048] The new slave device, regardless of its location, will receive a broadcast command and a commissioning signal on the commission line CL from any slave device connected to the new slave device via the commission line CL.

[0049] The new slave module is then registered, as previously described, by receiving from the master device via the fieldbus line an instruction for address configuration with a new default address for the slave device, a request for device information from the master device, and a command to enable the commission line with the next slave device. The master device MD can then store the device information of the new slave device in its information table.

[0050] Each slave module has its own configuration data regarding the operation of the slave device. For example, a slave device may be associated with a specific sensor, and the configuration data defines how the slave device is configured to communicate with that specific sensor.

[0051] For slave devices, configuration data can be stored as configuration data associated with the slave device type and the slave device address, corresponding to the device information in the master device MD's information table. New configuration data, or changes to configuration data, can be supplied by the master device or the slave device.

[0052] During startup, the master device addresses all modules to synchronize the configuration data of the slave devices. The master device compares the signature of the configuration data stored in the slave devices (e.g., through checksums) with the signature of the local configuration data. If the signatures are different, the master device initiates a synchronization of the configuration data with the slave modules.

[0053] When a new slave device replaces a failed one, the master device can automatically detect the new slave device with the help of device information in its information table and restart the registration process. In addition, the master device can restore the configuration data for the new slave device with the help of backup configuration data.

[0054] The embodiment comprises a master device MD in the form of an apparatus, comprising one or more processors, an I / O interface, a network interface, and memory coupled to the processors. The processors may be implemented as one or more microprocessors, microcomputers, microcontrollers, digital signal processors, central processing units, state machines, logic circuits, and / or any device that manipulates signals based on operational instructions. The processors may be a single processing unit or several units, all of which may include multiple computing units. Among other capabilities, the processors are configured to fetch and execute computer-readable instructions stored in memory.

[0055] The functions realized by a processor may be brought about through the use of dedicated hardware, as well as hardware capable of running software in conjunction with appropriate software. When brought about by a processor, the functions may be brought about by a single dedicated processor, a single shared processor, or by multiple individual processors, some of which may be shared. Furthermore, the explicit use of the term “processor” should not be interpreted as referring exclusively to hardware capable of running software, and may implicitly include, but is not limited to, digital signal processor (DSP) hardware, network processors, application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), read-only memory (ROM), random-access memory (RAM), and non-volatile storage for storing software. Other hardware, conventional and / or custom, may also be included.

[0056] Memory may include any computer-readable media known in the art, including volatile memory such as static random-access memory (SRAM) and dynamic random-access memory (DRAM), and / or non-volatile memory such as read-only memory (ROM), erasable programmable ROM, flash memory, hard disks, optical disks, and magnetic tape. Memory includes modules and data. Modules include routines, programs, objects, components, data structures, etc., that perform a particular task or implement a particular abstract data type. Data, among other things, serves as a repository for storing data that is processed, received, and generated by one or more modules.

[0057] Those skilled in the art will readily recognize that the steps of the methods presented above can be performed by a programmed computer. In this specification, some embodiments also include programmable storage devices, such as digital data storage media that are machine- or computer-readable and encode machine-executable or computer-executable programs of instructions, the instructions performing some or all of the steps of the described methods. Programmable storage devices can be, for example, digital memory, magnetic disks and tapes, magnetic storage media such as hard drives, or optically readable digital data storage media.

[0058] Referring to Figure 2, a method for configuring a slave device in a communication system according to one embodiment of the present invention includes steps S1 to S8.

[0059] In the first step S1, the master device MD initiates the registration process for all slave devices and sends a commissioning signal on the commission line CL. The commissioning signal is sent to the first slave device connected to the master device, i.e., slave device SD with index 1.

[0060] In step S2, the master device MD initiates the registration process for the slave device at index k and sends an address configuration frame in a broadcast on the fieldbus line FBL. The address configuration frame contains an instruction for address configuration with a defined address Add_k for the slave device at index k. The instruction commands the slave device at index k to change its common default address to the unique address Add_k for index k.

[0061] All slave devices receive an address configuration frame, but only the slave device that has received a commissioning signal on the commission line CL from the previous slave device it is connected to (or the master device if the slave device has index 1) can receive the address configuration frame; other slave devices will ignore or reject the address configuration frame.

[0062] As the slave devices are connected in a chain through the commission line CL, the master device MD performs the registration process for each slave device in the chain by incrementing the index k in the address configuration frame containing the defined address Add_k.

[0063] If the slave device at index k receives a commissioning signal on the commission line CL from the slave device at index k-1, or from the master device if k=1, it receives an address configuration frame containing the defined address Add_k and sets the local address for the fieldbus line FBL to Add_k.

[0064] After the local address is set, the slave device at index k sends an acknowledgment frame to the master device via the fieldbus line FBL, and the acknowledgment frame contains the defined address Add_k.

[0065] In step S3, the master device MD sends a request for device information via broadcast on the fieldbus line FBL, the request including the defined address Add_k.

[0066] The slave device at index k that acknowledged the previous address configuration frame retrieves device information from memory, which includes the name of the slave device at index k, the identifier of the slave device at index k, and the type of the slave device at index k.

[0067] The slave device at index k sends a response to the master device on the fieldbus line FBL, and the response includes device information and the defined address Add_k.

[0068] In step S4, the master device MD sends a command via broadcast on the fieldbus line FBL, the command including a defined address Add_k and an instruction to enable the commission line CL from the slave device at index k to the slave device at index k+1.

[0069] The slave device at index k sends a commissioning signal on the commission line CL to the next slave device at index k+1. After the commissioning signal is sent, the slave device at index k sends an acknowledgment frame to the master device, which contains the defined address Add_k.

[0070] In step S5, the master device MD stores the device information of the slave device at index k in the information table, corresponding to the address Add_k defined for index k.

[0071] Steps S2 to S5 are repeated for an index k that increases up to a number N, where N represents the number of slave devices in the communication system. N is not known in advance by the master device and is determined only after the registration process is completed.

[0072] The registration process is terminated when the master device does not receive an acknowledgment frame from the slave device containing the defined address Add_k (as in step S2).

[0073] In step S6, the communication system startup occurs, and the master device MD repeatedly sends address configuration commands to the slave device iteratively, as in step S2. At this time, the address configuration frame further includes the identifier of the slave device at index k, which is stored corresponding to the defined address Add_k at index k.

[0074] The slave device at index k receives an address configuration frame containing the identifier of the slave device at index k by comparing the received identifier with the identifier stored in local memory.

[0075] If the master device does not receive an acknowledgment frame containing the defined address Add_k after a specified time, the master device identifies the slave device at index k as a failed device. For example, a warning is displayed on the master device's HMI (Human-Machine Interface).

[0076] In step S7, which can be performed iteratively for each slave device, or after step S6 is completed, i.e., after all slave devices have been addressed, the master device compares the signature of the configuration data stored in each slave device with the signature of the configuration data stored in the master device. If the signatures are different, the master device initiates a synchronization of the configuration data with the slave device.

[0077] In step S8, during runtime, a new slave device is placed in the communication system and connected via the commission line to the last slave device at index k in the chain, where k is equal to N. The master device MD initiates the registration process by broadcasting a command to enable the commission line CL on the fieldbus line FBL. Each previously registered slave device at index k is then ready to send a commissioning signal on the commission line CL to the next slave device at index k+1. Thus, any slave device previously connected to the new slave device in the chain can send a commissioning signal on the commission line CL to the new slave device.

[0078] Next, steps S2-S5 are performed by the master device to send an instruction for address configuration with a newly defined address, a defined address Add_N+1 with index N+1 for the new slave device, a request for device information, and a command to enable the commission line with the next slave device. The master device MD can then store the device information of the new slave device in its information table.

[0079] In a communication system, when a new slave device replaces a faulty slave device, the operator initiates replacement registration in the master device MD, repeating steps S2 to S5.

[0080] In step S3, the master device uses the retrieved device information to detect that a new slave device has replaced a failed slave device. Specifically, the master device detects that the identifier of the slave device has changed relative to the address corresponding to the failed slave device.

[0081] Assuming the new slave device and the failed slave device are of the same type, the master device can restore the configuration data for the new slave device with the help of backup configuration data corresponding to the failed device.

[0082] Optionally, the master device may request permission from the operator to restore the configuration, and perform the configuration restoration after permission is granted.

[0083] Although the present invention has been described above with reference to specific embodiments, it is not limited to the specific forms described herein. Rather, the present invention is limited only by the appended "Claims," ​​and other embodiments other than the specific details described above may equally fall within the scope of the appended "Claims."

[0084] Furthermore, while exemplary embodiments are described above in several exemplary combinations of components and / or functions, it should be understood that alternative embodiments may be brought about by different combinations of components and / or functions without departing from the scope of this disclosure. In addition, it is explicitly intended that certain features described individually or as part of an embodiment may be combined with other individually described features or parts of other embodiments. [Explanation of Symbols]

[0085] MD Master Device SD Slave Device CL Commission Line FBL Field Bus Line

Claims

1. A method for configuring a slave device in a communication system comprising a master device (MD) and slave devices (SD), wherein the master device and the slave devices are connected in a chain via a commission line (CL) and in parallel via a fieldbus line (FBL), each slave device is indexed by one or more indices, the slave device at index 1 is connected to the master device to register the slave device at index k, where k is 1 or more, and the method includes an operation performed by the master device (MD), the operation being, In the broadcast over the field bus line (FBL), an address configuration frame is transmitted that includes an address configuration instruction having the defined address (Add_k) of index k for the slave device at index k (S2). In a broadcast over the fieldbus line (FBL), the sender transmits a request for device information (S3), wherein the request includes the defined address (Add_k). After receiving a response containing device information and the defined address (Add_k), S4 broadcasts a command via the fieldbus line (FBL) to the slave device at index k+1, sending a command via the commission line (CL) to transmit a commissioning signal, wherein the command includes the defined address (Add_k). (S5) The received device information is stored in an information table, wherein the device information includes the identifier of the slave device at index k and the type of the slave device at index k. A method comprising the following: the slave device has a common default address before registration, and only the slave device at index k that has the common default address and detects a commissioning signal on the commission line (CL) receives the address configuration frame to change the common default address of the slave device at index k to the defined address (Add_k).

2. The method according to claim 1, wherein the master device (MD) transmits a commissioning signal to the slave device at index 1 on the commission line (CL) (S1) before transmitting an address configuration frame in a broadcast over the field bus line (FBL) (S2) in order to register the slave device at index 1.

3. The method according to claim 1, wherein the master device (MD) receives an acknowledgment frame before transmitting a request for device information (S3), the acknowledgment frame includes the defined address (Add_k), and the request includes the defined address (Add_k).

4. The method according to claim 3, wherein the registration of the slave device is terminated when the master device does not receive an acknowledgment frame containing a defined address (Add_k) from the slave device.

5. The method according to claim 1, in the startup of the communication system for addressing the slave device of index k, the master device (MD) transmits an address configuration frame in a broadcast over the field bus line (FBL) that includes an address configuration instruction having the defined address (Add_k) of index k and the identifier of the slave device of index k (S6).

6. The method according to claim 5, wherein, in the startup of the communication system, the slave device has a common default address, and the slave device at index k that receives the address configuration frame receives the address configuration frame in order to change the common default address of the slave device at index k to the defined address (Add_k).

7. The method according to claim 6, wherein the master device (MD) identifies the slave device at index k as a faulty device if, after the master device has transmitted the address configuration frame which includes an instruction for address configuration having the defined address (Add_k) at index k and the identifier of the slave device at index k, it has not received an acknowledgment frame which includes the defined address (Add_k).

8. The method according to claim 1, wherein the master device (MD) compares the signature of the configuration data stored in each slave device with the signature of the configuration data stored in the master device (S7), and if the signatures are different, synchronizes the configuration data stored in the slave device with the configuration data stored in the master device.

9. The method according to claim 1, wherein during runtime, when a new slave device with index n+1 is placed in the communication system, the new slave device is connected to the last slave device with index k in the communication system, with k equal to n, and the master device (MD) initiates a registration process by sending a command to enable the commission line (CL) in a broadcast on the fieldbus line (FBL) so that each previously registered slave device with index k transmits a commissioning signal on the commission line (CL) to the next slave device with index k+1, the master device then performs the steps of: sending an address configuration frame having a defined address (Add_n+1) with index n+1 (S2); sending a request for device information having a defined address (Add_n+1) with index n+1 (S3); sending a command having a defined address (Add_n+1) with index n+1 (S4); and storing the received device information (S5).

10. The method according to claim 7, wherein when a new slave device replaces a failed slave device, replacement registration is activated in the master device, the master device performs the steps of transmitting an address configuration frame (S2), transmitting a request for device information (S3), transmitting a command (S4), and storing the received device information (S5), and the master device detects that a new slave device has replaced a failed slave device using the information table, the identifier of the new slave device, and the identifier of the failed slave device.

11. The method according to claim 8, wherein a slave device has failed, and configuration data for the slave device is stored in the master device corresponding to an identifier of the failed slave device and the type of the failed slave device, and when a new slave device replaces the failed slave device, if the new slave device and the failed slave device are of the same type, the master device uses the configuration data of the failed device to restore the configuration data for the new slave device.

12. A master device (MD) for configuring slave devices in a communication system, wherein the communication system comprises the master device (MD) and slave devices (SD), the master device and the slave devices are connected in a chain via a commission line (CL) and in parallel via a fieldbus line (FBL), each slave device is indexed by one or more indices, the slave device at index 1 is connected to the master device to register the slave device at index k, where k is 1 or more, and the master device is One or more network interfaces for communicating with the slave device (SD), A processor coupled to the network interface and configured to execute one or more processes, A memory configured to store processes that can be executed by the aforementioned processor and The process is provided, and when executed, In the broadcast over the field bus line (FBL), an address configuration frame is transmitted that includes an address configuration instruction having the defined address (Add_k) of index k for the slave device at index k. In a broadcast over the fieldbus line (FBL), the sender transmits a request for device information, wherein the request includes the defined address (Add_k). After receiving a response containing device information and the defined address (Add_k), the system broadcasts a command via the fieldbus line (FBL) to the slave device at index k+1, sending a command via the commission line (CL) to transmit a commissioning signal, wherein the command includes the defined address (Add_k). The received device information is stored in an information table, wherein the device information includes the identifier of the slave device at index k and the type of the slave device at index k. A master device (MD) is operable to perform the following actions: the slave devices have a common default address before being registered, and only the slave device at index k that has the common default address and detects a commissioning signal on the commission line (CL) receives the address configuration frame to change the common default address of the slave device at index k to the defined address (Add_k).

13. A non-temporary computer-readable storage medium, wherein a computer program is stored, and the computer program, when executed by a processor, comprises instructions for performing the steps of the method according to any one of claims 1 to 11.

14. A system comprising a master device (MD) as described in claim 12, and a plurality of slave devices (SD) connected in a chain to the master device (MD).

Images