Control device
By introducing group management functions in PLC, the complexity of variable state diagnosis across multiple namespaces is solved, unified variable state management and diagnosis is realized, and operation efficiency is improved.
Patent Information
- Application Number
- CN202280093900.8
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2022-03-30
- Publication Date
- 2024-11-05
AI Technical Summary
In PLC, in programs spanning multiple namespaces, each namespace needs to be managed separately when diagnosing or confirming variable status, resulting in complicated operations and difficult to manage in a unified manner.
Provides a control device that manages variable definition information through memory and storage unit, has functions such as accepting group editing requests, generating reference information and managing group, allowing users to group management of variables across multiple namespaces, and generate reference information for for inquiry and diagnosis.
It realizes unified management and diagnosis of variable status in multiple namespaces, reducing operational complexity and improving program debugging and maintenance efficiency.
Smart Images

Figure CN118901047A_ABST
Abstract
Description
Technical Field
[0001] The invention relates to a control device for group management of variables and signals in a plurality of namespaces. Background Art
[0002] In PLC, for example, specific functions are defined for each system in association with variables of a sequence program. In addition, when programming is performed in combination with a program organization unit (POU) standardized by IEC61131-3, variables are also defined for each POU (for example, refer to Patent Document 1).
[0003] Specifically, from the viewpoint of variable definition, a system or POU is included in the concept of a namespace in which variables are defined, and variable management of each system or POU is equivalent to variable management of each namespace.
[0004] In this way, in the variable management in the namespace, the variables belonging to the same namespace can be set uniformly by setting them as management variables for each namespace, and the variables belonging to the same namespace can be centrally confirmed or diagnosed on the screen for each namespace. On the other hand, variables set in different namespaces cannot be confirmed from the namespace.
[0005] Figure 8 1 is a diagram showing Group 1, which shows and explains how variables are set for each namespace. Figure 8 As shown, when the user wants to check or diagnose the variables set in the plurality of namespaces A, B, and C, the user needs to check or diagnose the variables set in each namespace individually.
[0006] Prior art literature
[0007] Patent Literature
[0008] Patent Document 1: Japanese Patent Application Publication No. 2005-301520 Summary of the invention
[0009] Problems to be solved by the invention
[0010] As described above, in PLC, for example, specific functions are defined for each system in association with variables of a sequence program. In addition, when programming is performed in combination with a program organization unit (POU: Program Organization Unit) standardized in IEC61131-3, variables are also defined for each POU.
[0011] Therefore, although variable names need to be uniquely defined in a namespace, there is no need to be aware of duplication with variable names defined in other namespaces. This is a convenient function when a program is divided into modules and developed for each module.
[0012] However, when it is necessary to confirm or diagnose the status of variables associated with a function, such as when debugging a program function or when a function fails during program execution, and when the variables are defined in different systems or different POUs, Figure 8 As shown, it is necessary to check or diagnose the variables set in each namespace while switching the display for each namespace, which is very complicated.
[0013] Therefore, in a program created across multiple namespaces, it is desirable to be able to browse through the multiple namespaces and generally check or diagnose the status of any variable defined in the program.
[0014] The present invention has been completed in view of such a problem, and its purpose is to provide a control device, which, in a program created across multiple namespaces, can browse multiple namespaces and simultaneously confirm or diagnose the status of any variable as a whole by providing a structure for group management of information used to refer to variable definitions across multiple namespaces.
[0015] Means for solving problems
[0016] One embodiment of the present disclosure is a control device, which is communicatively connected to a PLC device, the PLC device comprising: a memory unit, which records data of addresses that can be used on the PLC and current values of the addresses; a storage unit, which manages a sequence program executed according to each namespace and variable definition information related to variables defined at the addresses of the memory unit used in the sequence program according to each namespace, wherein:
[0017] The control device includes a control unit and an input unit, and the control unit includes: a group editing request receiving unit, which is input with an arbitrary address recorded in the memory unit or an arbitrary variable registered in the storage unit according to each namespace via the input unit, and receives a request for making or editing a group; a reference information generating unit, which generates reference information indicating where the address or the variable received by the group editing request receiving unit is recorded in the storage unit or in the storage unit; a group management unit, which, when a request for making a group is received by the group editing request receiving unit, creates a new group based on members including the reference information, and when a request for editing a group is received by the group editing request receiving unit, registers members including the reference information additionally to the group; and a query request receiving unit, which receives a query request for any group managed by the group management unit via the input unit,
[0018] The group management unit obtains an address and a current value from the memory unit and variable definition information from the storage unit in response to a query request received by the query request receiving unit, based on reference information registered in the group to which the query request is made, and provides the information as query information of members included in the group.
[0019] Effects of the Invention
[0020] According to the present invention, in a program created across multiple namespaces, a structure is provided for group management of information for referencing variable definitions across multiple namespaces, thereby enabling the states of arbitrary variables to be checked or diagnosed collectively while browsing through multiple namespaces. BRIEF DESCRIPTION OF THE DRAWINGS
[0021] Figure 1 This is a schematic diagram showing functional blocks of a control device according to one embodiment.
[0022] Figure 2 This is a schematic diagram showing an example of reference information indicating where an address or a variable is recorded across a namespace in a control device according to one embodiment.
[0023] Figure 3 This is a schematic diagram showing an example of generating reference information for variables satisfying designated conditions in a control device according to one embodiment.
[0024] Figure 4A This is a conceptual diagram showing a method of checking the state of a variable in groups in a control device according to one embodiment.
[0025] Figure 4B This is a schematic diagram showing an example of display content showing the state of variables in groups in a control device according to one embodiment.
[0026] Figure 5 This is a schematic diagram showing an example of setting whether or not members included in a group can browse and edit and the display order in a control device according to one embodiment.
[0027] Figure 6 This is a diagram showing an example of subgroups included in a group in a control device according to an embodiment.
[0028] Fig. 7A This is a flowchart showing the operation of the control device according to one embodiment.
[0029] Figure 7B This is a flowchart showing the operation of the control device according to one embodiment.
[0030] Figure 8 This is a diagram showing a conventional method of setting variables for each namespace. DETAILED DESCRIPTION
[0031] Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings. First, the configuration of a control device according to an embodiment of the present invention will be described.
[0032] 〔1 Overall structure〕
[0033] Figure 1 A configuration example of a control device according to the present embodiment is shown.
[0034] like Figure 1 As shown, the control device 1 is communicably connected to the PLC device 2. The control device 1 and the PLC device 2 may be directly connected to each other via a connection interface (not shown).
[0035] like Figure 1 As shown, the PLC device 2 includes a PLC_CPU 20 , a memory unit 202 , and a storage unit 22 .
[0036] The memory unit 202 records the current value of an address that can be used on the PLC. For example, the value of a variable used in a sequence program is stored in an address corresponding to the variable.
[0037] The storage unit 22 stores variable definitions related to variables used in the sequence program (also called "local variables"). As described above, variable definitions are set for each namespace. For example, for each system, the variable name defined by the sequence program is defined in association with the address where the value of the variable is recorded. The same is true in the case of the POU, for example, the variables (local variables) defined by the sequence program are defined for each POU. In addition, in the case of the POU, addresses are assigned to variables related to external input and output (also called "global variables"), but since the memory allocation for the variables (local variables) used in the program is automatically processed, there is no need to define the variable name in association with the address.
[0038] In the following description, unless otherwise specified, the case where the namespace is applied to the system name is described, but the same is true for the case where the namespace is applied to the POU name. In addition, the namespace is not limited to the system name and the POU name, but can be applied to any namespace.
[0039] The PLC_CPU 20 is a processor for executing a sequence program and performing various controls, calculation processing, signal input / output processing, etc. according to the sequence program. The PLC_CPU 20 reads a sequence program stored in a ROM via a bus, for example, and performs sequence control according to the sequence program.
[0040] In addition, PLC_CPU20 has an input / output interface unit (not shown) with the control device 1 described later, and can respond to, for example, variable definition information recorded in the storage unit 22 and the current value recorded in the address corresponding to the variable recorded in the memory unit 202 according to an access request to the memory unit 202 and the storage unit 22 from the control device 1.
[0041] like Figure 1 As shown, the control device 1 includes a control unit 10 , a storage unit 12 , an input unit 16 , and a display 17 .
[0042] The control unit 10 is, for example, a processor well known to those skilled in the art and configured to be able to communicate with a ROM, a RAM, a CMOS memory, and the like via a bus.
[0043] The control unit 10 is configured to read a program for executing the functions specific to the present invention described later from, for example, a storage unit 12 storing the program, and execute the program using data stored in a main storage device (not shown) such as a RAM for storing data temporarily required when executing the program, thereby executing the program. Figure 1 As shown, the control unit 10 realizes the functions of a group edit request accepting unit 101, a reference information generating unit 102, a group managing unit 103, and a query request accepting unit 104. These functional units will be described later.
[0044] As described later, the storage unit 12 stores the reference information corresponding to each variable name included in the group, which is generated by the reference information generating unit 102 . Figure 2 This is a diagram showing an example of reference information indicating where an address or a variable definition is recorded in the memory unit 202 or the storage unit 22 .
[0045] like Figure 2 As shown, variable definitions are performed for each system. For example, in system PLC1, variable definition 1-1 is defined with variable name INPUT1 and address X8.0, and variable definition 1-2 is defined with variable name *ESP_X and address X8.4. In addition, in another system PLC2, variable definition 2-1 is defined with variable name INPUT2 and address X9.0, and variable definition 2-2 is defined with variable name *ESP and address G8.4.
[0046] In this state, when the user confirms the variable name INPUT1 and the variable name *ESP_X in the system PLC1, the user himself needs to refer to the variable definition in the system PLC1 and confirm the value stored in the variable through the corresponding address. On the other hand, when confirming the variable name INPUT2 and the variable name *ESP in the system PLC2, the user needs to refer to the variable definition in the system PLC2 and confirm the value stored in the variable through the corresponding address.
[0047] In order to solve this problem, in the present invention, Figure 2 As shown, the variable name INPUT1 and the variable name *ESP_X in the system PLC1 and the variable name INPUT2 and the variable name *ESP in the system PLC2 are defined as one group (Group 1) for management.
[0048] Specifically, in a group (group 1), each variable name is defined in association with reference information indicating in which system the variable name is defined. For example, the variable name INPUT1 is defined in the system PLC1, so as reference information, it is defined as, for example, PLC1_INPUT1. Similarly, the variable name INPUT2 is defined in the system PLC2, so as reference information, it is defined as, for example, PLC2_INPUT2.
[0049] Thus, by managing the variables set in different systems as one group, as described later, the user can collectively check or diagnose the variables included in the group at the same time.
[0050] The input unit 16 is constituted by an input device such as a keyboard, a mouse, a touch panel, or a microphone, and receives input of information to the control device 1 from a user through the input unit 16 .
[0051] The display 17 is composed of a display device such as LCD (Liquid Crystal Display), CRT (Cathode Ray Tube), organic EL, LED (Light Emitting Diode), etc., and as described later, displays, for example, inquiry information of members included in the group requested by the user.
[0052] Next, functional units included in the control device 1 will be described.
[0053] The group edit request accepting unit 101 accepts a request to create or edit a group from a user via the input unit 16. Specifically, it accepts an arbitrary address recorded in the memory unit 202 or an arbitrary variable name registered in the storage unit 22 for each namespace from the user via the input unit 16, and accepts a request to create a new group.
[0054] Furthermore, as described later, the group edit request accepting unit 101 may accept any condition from the user via the input unit 16. In this case, as described later, the reference information generating unit 102 may generate reference information for variables satisfying the condition specified via the input unit 16, and generate a group satisfying the condition based on the generated reference information.
[0055] Furthermore, the input of a set group name can be accepted from the user via the input unit 16 , and a request to edit the group can be accepted.
[0056] When receiving an arbitrary address recorded in the memory unit 202 or an arbitrary variable name registered in the storage unit 22 according to each namespace accepted by the group editing request acceptance unit 101, the reference information generation unit 102 generates reference information indicating where the address or the variable is recorded in the memory unit 202 or the storage unit 22.
[0057] Specifically, as mentioned above, for example Figure 2 As shown, the reference information generating unit 102 defines each variable name in association with reference information indicating in which system the variable name is defined. Figure 2 As shown, for example, the variable name INPUT1 is defined in the system PLC1, and therefore is defined as, for example, PLC1_INPUT1 as reference information. Similarly, the variable name INPUT2 is defined in the system PLC2, and therefore is defined as, for example, PLC2_INPUT2 as reference information.
[0058] Furthermore, the reference information generating unit 102 may generate reference information for a variable that satisfies a condition specified via the input unit 16 .
[0059] Figure 3 is a schematic diagram showing an example of generating reference information for variables that satisfy specified conditions. Figure 3 As shown, for example, in system PLC1 and system PLC2, all variable names with a value of 0 are searched, and for all variable names that meet this condition, reference information indicating in which system the variable name is defined is created. Figure 3 In the example shown, the variable name INPUT1 belonging to the system PLC1 and the variable name *ESP belonging to the system PLC2 satisfy the condition, so the reference information generating unit 102 generates reference information for the variable name INPUT1 belonging to the system PLC1 and the variable name *ESP belonging to the system PLC2, respectively.
[0060] Furthermore, the reference information generating unit 102 may generate reference information for variable names that satisfy the conditions, for example, in response to the specification of the system to which the variable belongs and any conditions that the variables belonging to each system should satisfy.
[0061] Thus, when the user wants to collectively check or diagnose variables that satisfy a certain condition, the user can automatically generate reference information for the variables that satisfy the condition by simply inputting the condition. As a result, as described later, the group management unit 103 can generate a group including the variables that satisfy the condition and collectively check or diagnose the status of the variables that satisfy the condition.
[0062] When the group edit request accepting unit 101 accepts a request to create a group, the group management unit 103 creates a new group based on the members including the reference information generated by the reference information generating unit 102 as described above.
[0063] When the group edit request accepting unit 101 accepts an edit request to add a variable name to an already set group, the group management unit 103 additionally registers the reference information corresponding to the variable name generated by the reference information generating unit 102 in the group.
[0064] Furthermore, when the group edit request accepting unit 101 accepts an edit request to delete a designated variable name from an established group, the group management unit 103 deletes the reference information corresponding to the variable name from the group.
[0065] In addition, the group management unit 103 obtains the variable definition information from the storage unit 22 based on the reference information registered in the group requested for inquiry, and obtains the current value stored in the address from the memory unit 202, in response to the query request of the group accepted by the query request acceptance unit 104 described later, thereby providing the query information of the members included in the group requested for inquiry. Specifically, for example, by providing the query information of the members included in the group requested for inquiry to the display 17, the display 17 displays the query information of the members.
[0066] Thus, by providing a structure for group management in a program generated across a plurality of namespaces, it is possible to browse through a plurality of namespaces and to check or diagnose the status of any variable in a comprehensive manner.
[0067] Figure 4A This is a conceptual diagram showing how to check the status of variables in groups. Figure 4A As shown, by generating a group including variable x included in namespace A, variable y included in namespace B, and variable e included in namespace C, the user can collectively confirm variables x, a, and variable e at the same time.
[0068] Figure 4B 4 is a schematic diagram showing an example of display contents showing the state of variables in group units. Figure 2 As shown in FIG4 , by querying Group 1, for example, the address of the variable name INPUT1 and the variable name *ESP_X in the system PLC1 and the current value stored in the address, and the address of the variable name INPUT2 and the variable name *ESP in the system PLC2 and the current value stored in the address can be displayed simultaneously.
[0069] Furthermore, the group management unit 103 may set at least one of the attribute information including the creation date of the group, the variable name and address contained in the group, and whether the current value stored in the address can be read (also referred to as "read protection"), and whether the current value stored in the variable contained in the group can be edited (also referred to as "edit protection") for each created group, and the display order of the members contained in the group. The creation date, read protection, and edit protection of these attribute information may be set by the group creator. Furthermore, the display order of the members contained in the group may be set by the user who can read or edit the group when the group is displayed.
[0070] Figure 5 This is a schematic diagram showing an example of whether or not members included in a group can be viewed and edited, and the display order. Figure 5As shown, the creation date of Group 1 is January 1, 2021, and attribute information set to edit protection (i.e., non-editable) is assigned. In addition, since reading protection is not assigned to Group 1, the display order can be set when reading. In addition, in Group 2, the attribute information of reading protection is set to non-reading, so the default setting for editing is non-editable.
[0071] Thus, the user can manage the group by setting attribute information for the group and the display order of the members included in the group, and can change the order of displaying the members according to the user's needs when displaying the list.
[0072] Furthermore, the group management unit 103 may create a group in a hierarchical structure based on the related information indicating the correlation between the groups so that the group includes a plurality of subgroups.
[0073] Figure 6 is a diagram showing an example of a subgroup included in a group. Figure 6 As shown, group 1_1 is in Figure 2 , Figure 4A as well as Figure 5 , group 1 is created on January 1, 2021. Thereafter, the group management unit 103 creates group 1_2 on January 2, 2021, which is related to group 1_1, and similarly creates group 1_3 on January 3, 2021, and similarly creates group 1_4 on January 4, 2021, and creates group 1 on January 4, 2021 as a group (parent group) including them.
[0074] In this way, the group management unit 103 can create a plurality of groups in a hierarchical structure. In addition, the created groups can be edited so as to belong to a parent group in a hierarchical structure.
[0075] In this way, the user can improve the convenience of use by, for example, dividing members who are related to the group into subgroups.
[0076] The query request accepting unit 104 receives a query request for an arbitrary group managed by the group management unit 103 from the user via the input unit 16. Thus, as described above, the group management unit 103 obtains variable definition information from the storage unit 22 and obtains a current value stored in an address from the memory unit 202 in response to the query request for the group accepted by the query request accepting unit 104, based on the reference information registered in the group requested for query, thereby providing query information of members included in the group requested for query.
[0077] In the above, the functional units included in the control device 1 have been described.
[0078] Next, the operation of the control device 1 will be described. Fig. 7A and Figure 7B Each of them is a flowchart showing the operation of the control device 1 . Fig. 7A This is a flowchart showing the operation when creating or editing a group. Figure 7B This is a flowchart showing the operation when the definition information of the members (variables) included in the designated group and the current values of the variables are displayed.
[0079] Reference Fig. 7A In step S10, the group edit request accepting unit 101 accepts a group creation request or an edit request, and in the case of a group creation request, the process proceeds to step S11. In the case of an edit request, the process proceeds to step S20.
[0080] In step S11 , the group edit request accepting unit 101 accepts a variable name or a condition for specifying a grouping target, and when accepting a variable name, the process moves to step S13 . When accepting a condition, the process moves to step S12 .
[0081] In step S12 , the reference information generating unit 102 searches for all variable names that satisfy the conditions for each designated system, and acquires all variable names that are to be grouped. Thereafter, the process moves to step S13 .
[0082] In step S13 , the reference information generating unit 102 generates reference information for each of all variable names to be grouped.
[0083] In step S14 , the group management unit 103 creates a new group based on the members including the generated reference information, and ends the process.
[0084] In step S20, if the edit request is to add a variable name, the group management unit 103 proceeds to step S21. If the edit request is to delete a member belonging to the group, the group management unit 103 proceeds to step S23.
[0085] In step S21 , the reference information generating unit 102 generates reference information for each designated variable name.
[0086] In step S22 , the group management unit 103 adds the member included in the reference information generated in step S21 to the designated group, and ends the process.
[0087] In step S23, the group management unit 103 deletes the designated member from the group and ends the process.
[0088] The above has described the processing flow showing the operation of the control device 1 when creating or editing a group.
[0089] Next, a description will be given of a processing flow of the control device 1 when a group query request is received and definition information of members (variables) included in a designated group and current values of the variables are displayed.
[0090] Reference Figure 7B In step S30, the query request accepting unit 104 accepts a query request for a group.
[0091] In step S31 , the group management unit 103 acquires all reference information registered in the group requested for inquiry in step S30 .
[0092] In step S32 , the group management unit 103 acquires the variable definition information from the storage unit 22 based on each reference information acquired in step S31 , and acquires the current value stored in the address from the memory unit 202 .
[0093] In step S33 , the group management unit 103 outputs the inquiry information of the members included in the group for which the inquiry is requested, for example, to the display 17 .
[0094] The above has described a process flow showing the operation of the control device 1 during group query. The above has described a process flow showing the operation of the control device 1.
[0095] An embodiment of the control device has been described above, but the control device 1 is not limited to the above embodiment, and includes modifications, improvements, etc. within a range that can achieve the purpose.
[0096] <Modification 1>
[0097] In the above-mentioned embodiment, the PLC device 2 is communicatively connected to the control device 1, but the present invention is not limited thereto. For example, the control device 1 may include the PLC device 2. In addition, the PLC device 2 may also include the functional unit, the input unit 16, and the display 17 included in the control device 1.
[0098] In addition, each function included in the control device 1 in one embodiment can be realized by hardware, software, or a combination thereof. Here, realization by software means realization by a computer reading and executing a program.
[0099] The program can be stored and provided to the computer using various types of non-transitory computer readable media (Non-transitory computer readable medium). Non-transitory computer readable media include various types of tangible recording media (Tangible storage medium). Examples of non-transitory computer readable media include magnetic recording media (e.g., floppy disks, magnetic tapes, hard disk drives), optical magnetic recording media (e.g., optical magnetic disks), CD-ROM (Read Only Memory), CD-R, CD-R / W, semiconductor memories (e.g., mask ROM, PROM (Programmable ROM), EPROM (Erasable PROM), flash ROM, RAM). In addition, the program can also be provided to the computer via various types of transient computer readable media (Transitory computer readable medium). Examples of transient computer readable media include electrical signals, optical signals, and electromagnetic waves. Transient computer readable media can provide the program to the computer via a wired communication path such as wires and optical fibers or a wireless communication path.
[0100] Furthermore, the steps described in the program recorded in the recording medium naturally include processing performed in time series according to the order, but are not necessarily processed in time series and also include processing executed in parallel or individually.
[0101] In other words, the control device of the present disclosure can take various embodiments having the following structures.
[0102] (1) The control device 1 of the present embodiment is communicatively connected to the PLC device 2, wherein the PLC device 2 has: a memory unit 202 that records data of addresses and current values of addresses that can be used on the PLC; a storage unit 22 that manages variable definition information related to variables defined at addresses of the memory unit 202 used in the sequential programs executed according to each namespace and in the sequential programs according to each namespace, wherein the control device 1 has: a control unit 10 and an input unit 16,
[0103] The control unit 10 includes: a group edit request receiving unit 101, which receives an arbitrary address recorded in the memory unit 202 or an arbitrary variable registered in the storage unit 22 for each namespace via the input unit 16, and receives a request to create or edit a group; a reference information generating unit 102, which generates reference information indicating where the address or variable received by the group edit request receiving unit 101 is recorded in the memory unit 202 or the storage unit 22; a group management unit 103, which, when a request to create a group is received by the group edit request receiving unit 101, creates a new group based on members including the reference information, and, when a request to edit a group is received by the group edit request receiving unit 101, registers members including the reference information additionally to the group; and a query request receiving unit 104, which receives a query request for an arbitrary group managed by the group management unit 103 via the input unit 16,
[0104] In response to the query request received by the query request receiving unit 104, the group management unit 103 obtains the address and current value from the memory unit 202 and the variable definition information from the storage unit 22 based on the reference information registered in the group requested for query, and provides it as query information of the members included in the group.
[0105] Thus, in a program generated across multiple namespaces, a structure is provided for group management of information for referring to variable definitions across multiple namespaces without relying on a single namespace, thereby enabling the states of any variables to be checked or diagnosed in general while browsing through multiple namespaces. Furthermore, since only the states of variables registered in the group can be displayed, the processing load of the display can be reduced.
[0106] (2) In the control device 1 described in (1), the name space may be expressed by either a POU name or a system name of the PLC device 2 .
[0107] Thus, in a program created across multiple systems or POUs, a structure is provided for group management of information for reference variable definitions across multiple systems or POUs, not depending on the system or POU alone, so that the status of any variable can be checked or diagnosed overall while browsing multiple systems or POUs. Furthermore, only the status of the variables registered in the group can be displayed, so the processing load of the display can be reduced.
[0108] (3) In the control device 1 described in (1) or (2), the group management unit 103 may set at least one of the group creation date, attribute information including browsing and editing permissions, and display order of members included in the group.
[0109] Thus, by setting attribute information on a group and the display order of members included in the group, it is possible to manage the group and change the list display format according to the needs of the user.
[0110] (4) In the control device 1 described in any one of (1) to (3), the group management unit 103 may create a plurality of subgroups based on related information indicating a correlation between the groups.
[0111] Thus, for a group, members in a related relationship are further divided into subgroups, thereby improving the convenience of use for the user.
[0112] (5) In the control device 1 described in any one of (1) to (4), the reference information generating unit 102 may generate reference information for variables satisfying a condition specified via the input unit 16, and generate a group satisfying the condition based on the generated reference information.
[0113] Thus, when the user wants to collectively check or diagnose variables that satisfy a certain condition, the user can easily check or diagnose by simply inputting the condition to generate a group of variables that satisfy the condition.
[0114] (6) In the control device 1 according to any one of (1) to (5), the control device 1 may include a PLC device 2 .
[0115] (7) In the control device 1 according to any one of (1) to (5), the control device 1 may be included in the PLC device 2 .
[0116] Description of Reference Numerals
[0117] 1. Control device,
[0118] 10. Control Unit,
[0119] 101 Group Editing Request Acceptance Department,
[0120] 102 reference information generating unit,
[0121] 103 Group Management Department,
[0122] 104 Inquiry Request Acceptance Department,
[0123] 12 Storage unit,
[0124] 16 Input unit,
[0125] 17 Display,
[0126] 2PLC device,
[0127] 20PLC_CPU,
[0128] 202 memory unit,
[0129] 22 Storage unit.
Claims
1. A control device connected to a PLC device in a communicative manner, the PLC device comprising: A memory unit that records addresses that can be used on the PLC and data of current values at the addresses; as well as a storage unit that manages a sequence program executed in accordance with each namespace and variable definition information related to a variable defined at an address of the memory unit and used in the sequence program in accordance with each namespace, It is characterized in that The control device comprises: Control Department; and Input section, The control unit comprises: a group edit request accepting unit that receives an arbitrary address recorded in the memory unit or an arbitrary variable registered in the storage unit for each namespace via the input unit and accepts a request to create or edit a group; a reference information generating unit configured to generate reference information indicating where the address or the variable accepted by the group edit request accepting unit is recorded in the memory unit or the storage unit; a group management unit that creates a new group based on the members including the reference information when the group edit request accepting unit accepts a request to create a group, and that additionally registers the members including the reference information in the group when the group edit request accepting unit accepts a request to edit a group; and a query request receiving unit that receives, via the input unit, a query request for any group managed by the group management unit, The group management unit obtains an address and a current value from the memory unit and variable definition information from the storage unit in response to a query request received by the query request receiving unit, based on reference information registered in the group to which the query request is made, and provides the information as query information of members included in the group.
2. The control device according to claim 1, characterized in that: The namespace is represented by either a POU name or a system name of a PLC device.
3. The control device according to claim 1 or 2, characterized in that: The group management unit sets, for the group, at least one of attribute information including a creation date of the group, browsing and editing permissions, and a display order of the members included in the group.
4. The control device according to any one of claims 1 to 3, characterized in that: The group management unit creates a plurality of subgroups based on related information indicating a correlation relationship among the groups.
5. The control device according to any one of claims 1 to 4, characterized in that: The reference information generating unit generates reference information for a variable satisfying a condition specified by the input unit, and generates a group satisfying the condition based on the generated reference information.
6. The control device according to any one of claims 1 to 5, characterized in that: The control device includes the PLC device.
7. The control device according to any one of claims 1 to 5, characterized in that: The control device is included in the PLC device.
