Efficient slave parameter management method and device for communication infrastructure control system

A centralized slave parameter management system using a control unit with non-volatile memory efficiently manages and sets parameters for multiple slave devices, reducing setup time and travel risks while ensuring safe and efficient maintenance.

JP7579457B2Active Publication Date: 2024-11-07LS ELECTRIC CO LTD
View PDF 3 Cites 0 Cited by

Patent Information

Application Number
JP2023544486
Authority / Receiving Office
JP · JP
Patent Type
Patents
Current Assignee / Owner
Priority Date
2021-04-06
Filing Date
2022-03-16
Publication Date
2024-11-07
Estimated Expiration
2042-03-16

AI Technical Summary

Technical Problem

Existing control systems with a master-slave structure face challenges in efficiently managing and setting parameters for numerous remote slave devices, leading to increased maintenance costs, travel time, and potential safety hazards due to the need for individual configuration at each device.

Method used

A centralized slave parameter management system using a control unit with a non-volatile memory to store and manage parameters for all connected slave devices, allowing for centralized parameter setting and management, including generation of unique IDs and periodic status checks to ensure safe and efficient parameter transmission.

Benefits of technology

Reduces setup time and travel time for workers, enhances safety by eliminating the need for direct configuration at remote locations, and simplifies maintenance by managing complex slave devices in one place.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 0007579457000001
    Figure 0007579457000001
  • Figure 0007579457000002
    Figure 0007579457000002
  • Figure 0007579457000003
    Figure 0007579457000003
Patent Text Reader

Abstract

The present invention relates to a parameter management method for a communication-based master-slave control system, in which parameters of all slave devices are stored in a non-volatile memory in a master device and then applied to the master device, so that settings for slave devices in locations that are difficult or dangerous for workers to access can be set using the parameters stored in the master device, which simplifies maintenance of the slave devices and ensures the safety of users.
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

[0001] The present invention relates to a control system, and more particularly to a method for managing a control system having a master-slave structure. [Background technology]

[0002] Control systems such as PLC (Programmable Logic Controller) are evolving into a modularized form based on communication. As such control systems grow in size and complexity, master devices control slave devices. At this time, information that defines various operations of the slave devices is called parameters, and if these parameters are not stored in the slave devices in advance, the slave devices will not operate properly.

[0003] Since the slave devices are mainly located at the end of the control system, the number of slave devices increases exponentially as the system becomes larger in scale. Therefore, if the maintenance method of the slaves is inconvenient or dangerous, the maintenance cost also increases.

[0004] FIG. 1 shows an example of a conventional PLC system.

[0005] The master controller 1 is connected to the slave devices 2 and 3 through communication to control the slave devices 2 and 3. There may be two or more master controllers.

[0006] In the conventional control system setting method, because the type and size of parameters to be set for each slave device were different, it was necessary to connect PC5, 6, 7, etc. individually and program and set them.

[0007] If parameters must be downloaded to each slave device individually, there is a problem that the setting work may take an excessively long time or an accident may occur if the slave devices are far apart or located in a dangerous place.

[0008] The inventors of the present invention have been conducting intensive research to solve the above-mentioned problems with setting up slave devices in the prior art. As a result of their intensive efforts to complete a method and device for managing a communication-based control system that can reduce the time required to set up a variety of complicated slave devices and ease the difficulties of maintenance, the present invention has been completed. Summary of the Invention [Problem to be solved by the invention]

[0009] An object of the present invention is to provide a method for managing and setting parameters of many slave devices that are far apart from one another in a single location, thereby reducing the travel time of an operator and enabling safer management.

[0010] On the other hand, other objects of the present invention not explicitly stated will be considered within the scope that can be easily inferred from the following detailed description and its effects. [Means for solving the problem]

[0011] The slave parameter management device according to the present invention comprises:

[0012] The present invention includes a control unit including one or more processors and memories; and a storage unit consisting of a non-volatile memory for storing parameters; and the control unit receives parameters for all connected slave devices from the setting device and stores them in the storage unit.

[0013] The control unit generates a parameter ID for each of the received parameters and stores the generated parameter ID in the storage unit.

[0014] The control unit requests status information of the slave device, and if the slave device needs parameter reconfiguration and is not occupied by another master device, transmits the parameters stored in the storage unit to the slave device.

[0015] The control unit may periodically repeat the request for the status information when the slave device is occupied by another master device.

[0016] A method for managing parameters of a master-slave system according to another embodiment of the present invention includes:

[0017] The method includes the steps of: the master device receiving parameters for all slave devices connected to the master device from a parameter setting device; the master device requesting slave device information from the slave devices connected to the master device; the slave devices transmitting slave device information to the master device in response to the request; the master device transmitting a lock request to the slave devices if the received parameters for the slave devices are applicable according to the slave device information and the slave devices are not occupied by another master; the slave devices transmitting a response to the lock request to the master device; if the response to the lock request received by the master device is an acknowledgment (Ack), transmitting the parameters received from the parameter setting device to the slave devices; and if the slave devices receive the parameters, transmitting a parameter reception completion response to the master device.

[0018] A slave parameter management method according to still another embodiment of the present invention includes:

[0019] The method includes the steps of receiving parameters for all connected slave devices from a parameter setting device; storing the received parameters in a storage unit configured as a non-volatile memory; requesting status information from the connected slave devices; and, if the connected slave devices require parameter reconfiguration and are not occupied by another master device, transmitting the parameters stored in the storage unit to the connected slave devices.

[0020] The storing of the parameters may include generating an ID for each of the parameters and storing the ID together.

[0021] If the slave device is occupied by another master device after the step of requesting the status information, the request for the status information may be periodically repeated. Effect of the Invention

[0022] According to the present invention, the complex and difficult settings of various slaves of different types can be managed in one place, thereby reducing the time required to set up the slave devices.

[0023] In addition, since there is no need to directly configure slave devices that are far away from each other, the travel time of workers is reduced, saving work time and preventing dangerous situations.

[0024] On the other hand, it is noted that even if an effect is not explicitly mentioned herein, the effects and provisional effects thereof described in the following specification that are expected by the technical features of the present invention are treated as if they were described in the specification of the present invention. [Brief description of the drawings]

[0025] [Figure 1] 1 shows a connection structure of a control system according to the prior art.

[0026] [Diagram 2] 1 is a schematic structural diagram of a slave parameter management device according to a preferred embodiment of the present invention;

[0027] [Diagram 3] 10 is a schematic flowchart of a slave parameter management method according to another preferred embodiment of the present invention;

[0028] *It is clear that the attached drawings are illustrative and are for reference purposes only to aid in understanding the technical concept of the present invention, and are not intended to limit the scope of the present invention. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0029] Hereinafter, the configuration of the present invention and the effects resulting from the configuration will be described in detail with reference to the drawings, which are provided by various embodiments of the present invention. In describing the present invention, detailed description of related known functions will be omitted if it is deemed that such detailed description is obvious to a person skilled in the art and may unnecessarily obscure the gist of the present invention.

[0030] Terms such as "first" and "second" may be used to describe various components, but the components should not be limited by the terms. The terms may be used only to distinguish one component from another component. For example, a "first component" may be named a "second component" and a "second component" may be named a "first component" without departing from the scope of the present invention. In addition, singular expressions include plural expressions unless otherwise clearly expressed in the context. Terms used in the embodiments of the present invention may be interpreted in a manner commonly known to those skilled in the art unless otherwise defined.

[0031] Hereinafter, the configurations of the present invention and the effects thereof will be described in detail with reference to the drawings, which illustrate various embodiments of the present invention.

[0032] FIG. 2 is a schematic structural diagram of a slave parameter management device according to a preferred embodiment of the present invention.

[0033] The slave parameter management device 100 according to the present invention may include a control unit 110, a communication unit 120, an input unit 130, an output unit 140, and a storage unit 150.

[0034] A PLC device or the like can be used as the slave parameter management device 100 that can be used as a master device in a communication-based control system.

[0035] The control unit 110 includes one or more processors 112 and a memory 114. The processor 112 executes commands for managing slave parameters, and the memory 114 stores program codes and necessary data for operating the processor 112.

[0036] The input unit 130 is used to receive input data from a device corresponding to an input module among the connected slave devices. Using the input data, the control unit 110 executes a program set by a user.

[0037] The output unit 140 is used to transmit program execution results to devices corresponding to output modules among the connected slave devices, and the output data is transmitted to each slave output module through the output unit 140.

[0038] The communication unit 120 is used to exchange data with the slave device 300 and the setting device 200 such as a PC, and to control the state.

[0039] The storage unit 150 receives and stores parameters of all slave devices connected from the setting device 200, and transmits the stored parameters to the slave devices when necessary. For this purpose, the storage unit 150 is made of a non-volatile memory.

[0040] The control unit 110 receives parameters of all connected slave devices from the setting device 200 and stores them in the storage unit 150. At this time, an ID (Identification) for identifying which slave device each parameter is applied to may be stored together. The control unit 110 can determine which parameters have been applied to each slave device using the parameter ID and can transmit appropriate parameters to each slave device as necessary.

[0041] The control unit 110 requests status information of the connected slave device 300 to grasp the status of the slave device 300, and if a parameter reset is required due to a malfunction or an error, the control unit 110 checks the ID of the parameter stored in the storage unit 150 and transmits the corresponding parameter to the slave device 300.

[0042] If the slave device 300 is in an occupied state by another master device, it may periodically send a request to check whether the occupied state has been released.

[0043] As described above, the slave parameter management device 100 according to the present invention has the advantage of managing the parameters of the slave devices in one place, thereby eliminating the inconvenience and risk of setting parameters by directly connecting a setting device such as a PC or a notebook computer to each slave device in the conventional method.

[0044] FIG. 3 is a schematic flowchart of a slave parameter setting method according to another preferred embodiment of the present invention.

[0045] A specific example of a slave parameter management method performed between a master device 100, which is a slave parameter setting device according to the present invention, and a slave device 300 will be described.

[0046] The control unit of the master device 100 first receives all parameters of the master device 100 and each slave device from a setting device such as a PC. These are stored in a storage unit consisting of a non-volatile memory. At this time, the control unit generates a parameter ID that can distinguish the parameters and stores it together.

[0047] The master device 100 transmits a request to read information of the slave device 300 to the slave device (S10).

[0048] In response to the request, the slave device 300 transmits information about the slave device 300, which is received by the master device 100 (S12).

[0049] The information on the slave device 300 includes status information indicating errors or malfunctions of the slave device 300, information required for parameter setting, master information, various parameter setting states, and the like.

[0050] The status information includes whether the slave device 300 is normal, or an error has occurred, etc. Errors include both hardware errors and software errors.

[0051] Information required for parameter setting includes the I / O (Input / Output) type and I / O size of the slave device 300 .

[0052] An example of the slave device 300 may be an additional driver device such as XGL-DBDT. The additional driver device may be equipped with a plurality of I / O modules, and each I / O module has individual parameters. Therefore, the master device 100 must select appropriate parameters according to the type of the slave device 300 or the type of the module installed in the slave device 300, and transmit the appropriate parameters to the slave device 300 so that the parameters are applied. Examples of parameters applied to the I / O module may include an operating channel, an input / output voltage (current) range, an input / output data type, an averaging method, a channel output state, an average value, etc.

[0053] The master information may include information on whether the slave device 300 is occupied by a master device, which master device the slave device 300 is connected to, and so on.

[0054] The various parameter setting states may also include parameter IDs generated by the master device 100.

[0055] The master device 100 determines whether the slave device is available for occupation based on the received slave information, and then requests a slave lock (S20).

[0056] The requirements for determining whether a slave is occupyable include checking whether the slave status is normal in the slave device information, comparing the received parameter setting information to determine whether the parameters received by the setting device are applicable, and checking the master information to determine whether the slave is occupied by another master.

[0057] If these requirements are met, a lock request to occupy the slave device 300 is sent.

[0058] If other requirements are met but the state is already occupied by another master, the slave device 300 can periodically transmit a slave information request to check whether the occupied state of the slave device 300 has been released.

[0059] When the slave device 300 receives the lock request, it transmits an ACK (Acknowledge) response to the master device 100 if it is not occupied by another master device, or a NACK (Negative Acknowledge) response to the master device 100 if it is already occupied by another master device (S22).

[0060] Basically, the master device 100 sends a lock request only when the slave device 300 is not in an occupied state. That is, the master device 100 does not send a lock request to a slave device 300 occupied by another master device. However, since the method of implementing the software of the master device 100 and the slave device 300 may differ depending on the developer, or occupation by another master device may occur between the occupation confirmation and the lock request, a NACK response may be generated to the lock request. Therefore, even after confirming the occupation state of the slave device 300, the master device 100 checks again for a response to the lock request and then proceeds to the next step.

[0061] If the master device 100 receives a normal ACK response from the slave device 300, it transmits the parameters together with the parameter ID to the slave device 300 (S30).

[0062] At this time, the parameter ID is checked in the slave information received from the slave device 300, and if it is identical to the parameter ID received from the setting device, the parameter does not need to be transmitted. Since the parameter ID is a unique value, it is possible to check the identity of all the parameters by the parameter ID without comparing all the parameters.

[0063] Since the parameter ID is a unique value that is recalculated and generated by the master device 100 every time a parameter is changed, the slave device 300 should not change the parameter ID. In addition, the parameters and the parameter ID can be stored together in the non-volatile memory of the slave device 300, taking into account the power on / off status.

[0064] When the slave device 300 receives the parameters, it transmits a reception completion response to the master device (S32).

[0065] After the parameters have been transmitted and set, the master device 100 transmits a message to inquire whether the slave device is ready to operate (S40).

[0066] After receiving the parameters, the slave device 300 can apply the parameters required for operation to its internal system, back up the received parameters, and then transmit a ready response (S42).

[0067] If the application and backup of parameters takes a long time, a NAK response can be sent first, and then an ACK response can be transmitted again when preparations are complete.

[0068] When the master device 100 receives ACK responses from all slave devices indicating that they are ready, it begins to control the entire system.

[0069] According to the slave parameter management device and method of the present invention as described above, the master device centrally stores and manages parameters for the slave devices, so that the settings for the slave devices that are in locations that are difficult or dangerous for workers to access can be set using the parameters stored in the master device. This simplifies the maintenance of the slave devices and ensures the safety of users.

[0070] The scope of protection of the present invention is not limited to the description and expression of the embodiments explicitly described above. It is also reiterated that the scope of protection of the present invention cannot be limited by obvious modifications or substitutions in the technical field to which the present invention belongs.

Claims

1. A method for managing slave parameters, the method being performed by a control unit including one or more processors and memory in a master device, comprising: receiving parameters for a plurality of slave devices connected to the master device from a parameter setting device; storing the received parameters in a storage unit configured as a non-volatile memory of the master device; requesting slave information from the plurality of slave devices; transmitting a lock request to a first slave device for which parameters are applicable based on the slave information and to a second slave device which is occupied by another master device and is not occupied by another master device; transmitting the parameters for the first slave device stored in the storage unit to the first slave device if the response to the lock request received from the first slave device is an acknowledgment (Ack); and periodically requesting slave information from the second slave device if the response to the lock request received from the second slave device is a Nack. A slave parameter management method comprising:

2. 2. The method of claim 1, wherein the storing of the parameters comprises generating an ID for each of the parameters and storing the ID together with the parameter.

3. A method for managing parameters in a master-slave system including a master device and one or more slave devices, comprising: the master device receiving parameters for all slave devices connected to the master device from a parameter setting device; the master device requests slave information from a connected slave device; the slave device transmitting slave information to the master device in response to the request; The master device transmits a lock request to a first slave device for which parameters are applicable based on the slave information and which is not occupied by another master device and a second slave device which is occupied by another master device; the first slave device and the second slave device transmitting a response to the lock request to the master device; transmitting the parameters received from the parameter setting device to the first slave device if the response to the lock request received from the first slave device is an acknowledgment (Ack); transmitting a parameter reception completion response to the master device when the first slave device receives the parameter; and the master device periodically requests slave information from the second slave device if the response to the lock request received from the second slave device is a Nack. A method for managing parameters of a master-slave system, comprising:

4. A controller including one or more processors and a memory; and A slave parameter management device including a storage unit consisting of a non-volatile memory for storing parameters, The control unit is receiving parameters for a plurality of slave devices connected to the slave parameter manager from a parameter setting device; storing the received parameters in the storage unit; requesting slave information from the plurality of slave devices; Based on the slave information, parameters are applicable, and the device transmits a lock request to a first slave device that is not occupied by another master device and a second slave device that is occupied by another master device; If the response to the lock request received from the first slave device is an acknowledgment (Ack), the parameters for the first slave device stored in the storage unit are transmitted to the first slave device; The slave parameter management device further comprises: a locking unit that periodically requests slave information from the second slave device if a response to the locking request received from the second slave device is a negative (Nack) signal.

5. The slave parameter management device of claim 4, wherein the control unit generates a parameter ID for each of the received parameters and stores the generated parameter ID in the storage unit.

Citation Information

Patent Citations

  • Remote i / O transmission system of programmable controller

    JP1994161521A

  • Communication unit, communication system, control method, and program

    JP2014119906A

  • Support apparatus, support program, and control system

    JP2020027460A