JP4666172B2 - Control system setting management system - Google Patents

Description

  The present invention relates to a control system setting management system, and more specifically to a system for managing physical memory related to allocation information, variable information, and devices across physical memory of a control device.

  PLC (programmable controller) used in FA (factory automation) inputs ON / OFF information of input devices such as switches and sensors, and performs logical operations according to a sequence program (user program) written in a ladder language. Execute. Then, the PLC performs control by outputting a signal of ON / OFF information to an output device such as a relay, a valve, or an actuator according to the obtained calculation result.

  A control device such as a PLC is generally a building block method, and is used as a controller by combining an IO, a communication control device, a remote IO control device, a dedicated controller, and the like. Each device is also referred to as a unit.

  By the way, the physical memory of the control device is not only used for programming the control device itself, but also assigned to each IO, assigned to a communication control device, assigned to a remote IO control device, assigned to each dedicated controller. Used for assignment, etc., or used for setting each unit.

  The allocation of these physical memories is performed by each tool software on the computer system where the tool software operates, according to the allocation setting to the control device, the allocation setting to the communication control device, the allocation setting to the remote IO control device, and the dedicated controller. It is determined by assignment setting to assignment setting.

  On the other hand, the tool software for programming and setting of these devices assigns unique variables to the physical memory of the control device to improve the convenience of individual programming.

  On the other hand, a plurality of control devices such as PLCs may be connected to a network, and the plurality of control devices may execute cooperation / synchronization control while sharing data. One of these methods is called a data link method. This data link method is a method in which data is cyclically exchanged (linked) between a plurality of control devices.

  For example, each node as a control device has a memory table, and data is shared by exchanging data with each other so that the contents of the tables are the same. At this time, accesses for exchanging data are performed by designating memory addresses (physical addresses). Further, the table is collectively set by another tool other than the control device. This method has an advantage that communication is not required when developing a user program.

  Conventionally, physical memory allocation destinations and variables of a control device are defined on the desktop in the design process of the entire control system, and various device settings (configuration) and programming are performed on the basis of the tool software prepared individually. . Tool software can be programmed and allocated with a high degree of freedom without worrying about how other devices use physical memory based on desktop-defined data. Contains.

  If the desktop definition is changed due to a design change of the control system, it is likely to cause unexpected unauthorized use of physical memory and variables or unauthorized duplicate use in other devices. In control system maintenance, when it is necessary to decipher the physical memory or variable assignment destination that caused the failure, it is necessary to search quickly using multiple tool software or desktop design data. I can't. In particular, when using the data link function, the physical memory or variable that caused the failure is often caused by a problem in an area linked to a device other than the target device due to the data link function. It is necessary to decipher the usage of memory across the board. In addition to physical memory addresses that require various devices, the user may want to occupy a physical area for a specific purpose. In this case, it is difficult to manage whether it is not duplicated with other physical address assignments.

  An object of the present invention is to obtain and allocate physical memory allocation information and variable information of a control device determined by data individually generated and managed by various tool software, and memory allocation information across a plurality of devices at an arbitrary timing. It is an object of the present invention to provide a control system setting management system that can be set and reflected, and can detect / prevent unauthorized use and unauthorized duplicate use.

  (1) A control system setting management system according to the present invention includes a shared storage for holding setting data describing physical memory allocation information of a control device, and a plurality of types for accessing the shared storage and reading and writing the setting data. And tools. When the memory allocation to the physical memory is performed, the tool reads the allocation information already set stored in the shared storage and overlaps the memory area to which the memory allocation is to be performed based on the read allocation information. Determining means for determining whether or not an error has occurred; and means for adding information on memory allocation performed by the tool to the setting data of the shared storage on condition that an area duplication error is not detected by the determining means; And means for setting the device based on the memory allocation performed by the tool on condition that the area duplication error is not detected by the determining means.

  (2) Memory allocation to the physical memory performed by the tool includes either one automatically allocated according to the type of model, or one that the user independently declares occupation of the physical memory area.

  (3) The setting data stored in the shared storage also includes link information of the memory between the devices in a control system that links and uses physical memory between a plurality of devices, and the determination means is based on the link information. The memory can be configured to have a function of determining whether an area duplication error has occurred in the memory area to which the memory allocation is to be performed.

  (4) The setting data stored in the shared storage has a use attribute for each memory allocation, and the determination means determines whether or not duplication is permitted based on the use attribute when the allocation areas overlap. The control system setting management system according to any one of claims 1 to 3, further comprising a function of performing the following.

  (5) The variable information allocated to the physical memory is recorded, and the allocation information of the physical memory is linked to the variable information so that a plurality of tools can share the variable information belonging to the physical memory and the area.

  The plurality of tools are setting tools (application programs) for performing various settings on each unit (device) constituting the PLC, devices connected to a network including the PLC (programmable display or the like), and the like. This tool is installed in a computer and functions as a tool device. The plurality of tools may be implemented on separate computers or on the same computer. The shared storage may be implemented on the same computer as the tool, or may be realized as a device (storage server) separate from the tool.

  A PLC is usually composed of a plurality of units (devices), and each unit has a different setting tool, but each unit occupies a physical memory area of the PLC main body (control device). In addition, the use of memory is diverse, such as setting data links across devices, and the user's own use for programs.

  Therefore, the allocation information of the physical memory area set by each tool is stored in the shared storage, and the stored data can be accessed by each tool. Therefore, the management of physical memory can be unified between the tools, resulting in a duplicate error. Such memory allocation can be detected and avoided in advance. In other words, the usage status of the physical memory and the variables allocated to the memory can be displayed in a list on the tool without depending on the data defined on the desktop. It is possible to instantly know which assignment the addresses and variables used in the control program etc. are included in, and program mistakes such as illegal use of addresses and illegal double use can be detected at an early stage.

  In addition, each tool can be checked by linking memory areas that span multiple devices, linking memory areas and variables contained in the memory, and having usage information in the memory to check for misuse. When the address of the physical memory is specified, the software can immediately provide (display) the use, allocation destination, and variable as a guide. When linking memory across devices, it is possible to easily grasp the address of the linked PLC and its specification status from the memory address of one PLC, and cause a problem such as failure of interlock between multiple devices during debugging Easy to grasp. When the memory allocation is changed by changing the configuration of the device (unit) or the like, the address of the associated variable is automatically changed to reduce mistakes.

  In the present invention, the physical memory allocation information and variable information of the control device determined by data individually generated and managed by various tool software, memory allocation information across multiple devices, etc. are registered in the shared storage. Centralized management is possible, and unauthorized use and unauthorized duplicate use can be detected / prevented in advance.

  FIG. 1 shows an example of a system configuration diagram. The system shown in FIG. 1 includes a control system setting device 2 that creates a plurality of PLCs 1 and a network configuration diagram, and creates / updates user programs and setting files for the devices that make up the PLC 1. A display 3 and a control device 4 are connected to a network 5. The control system setting device 2 is a personal computer in which an application program (dedicated tool) and setting data for performing the above processing are installed. In the present embodiment, the control system setting device 2 is connected to each device / equipment via the network 5, but may be directly connected to each device / equipment using a serial interface such as RS-232C. good.

  The physical memory of the control device (Dev. A) constituting the PLC 1 is used for programming of the control device itself, as well as allocation to each IO, allocation to the communication control device (Dev. B), remote IO Used for assignment to the control device (Dev.C), etc., used for setting each unit, using each unit from the control device (Dev.A) in a program, and linking with a dedicated controller, display, etc. The The allocation of these physical memories is controlled by each tool software (Tool. A, Tool. B, Tool. C, etc.) on a computer system (PC.1, PC.2, PC.3) on which the tool software operates. Assignment setting (Cfg.A) to device (Dev.A), assignment setting (Cfg.B) to communication control device (Dev.B), assignment setting (Cfg.A) to remote IO control device (Dev.C) C) and the like.

  On the other hand, various tools for programming and setting of these devices assign unique variables (Prj.A, Prj.B, Prj.C, etc.) to the physical memory of the control device (Dev.A), and individually. The convenience of programming has been improved.

  The PLC 1 is configured by preparing a plurality of devices and connecting them to each other or attaching them to a backplane unit. A device is also referred to as a unit. The illustrated PLC 1 includes a main control device (Dev. A), an IO unit, a communication control device (Dev. B), and a remote IO control device (Dev. C).

  In the present embodiment, three control system setting devices 2 are connected to the network 5. Each control system setting device 2 has one or two dedicated tools installed. However, the number of installed control system setting devices 2 is arbitrary, and the number of dedicated tools installed in one control system setting device 2 is also arbitrary. The dedicated tool is tool software that performs assignment to a control device, programming, assignment of a remote IO to a management device, and the like. For example, tool A is a tool for creating a user program, tool B is a tool for creating a network configuration / system configuration, tool C is a remote IO setting tool, and tool D is A dedicated controller setting tool, and tool E is a programming tool for the display. Each tool includes “Prj.n”, which is variable data describing the name given to the address of the physical memory, and “Cfg.n”, which is setting data describing the relationship between the physical memory allocation destination and the memory link between devices. And is retained.

  The display 3 is a programmable display (PT), and is a device for displaying the control contents of the PLC 1 and making various settings for the PLC 1.

  The other control device 4 is another control device connected on the network 5. The network 5 is a connection environment for connecting the PLC 1 and the control system setting device 2 and can be realized by Ethernet (registered trademark) or the like.

  The shared storage 6 is a storage device for storing and holding a memory map database in which data is read and written by each tool, and is realized as an internal or external storage device of a computer constituting any one of the control system setting devices 2 Or realized as an independent database server on the network 5. The memory map database is an aggregate of “allocation information of physical memory of control device” and “table describing relationship information and variable information of memory allocation between devices”. Details will be described later.

  The memory map information stored in the shared storage 6 can be input / edited / displayed by the memory map management tool 8. The memory map management tool 8 may be incorporated as a partial function of each tool installed in the control system setting device 2.

  The database management system 7 is a database interface to the memory map database of the shared storage 6. The database management system 7 issues various keys for uniquely identifying each information according to a request from each tool, and constructs a memory map database in response to the request. The database management system 7 is mounted on a computer constituting any one of the control system setting devices 2 or is mounted on another computer connected to the network 5. The database management system 7 may be mounted on the same device as the shared storage 6 or may be mounted on a different device.

  The memory map database in the shared storage 6 stores project information, device information, memory map information, memory allocation information, a memory link table, and variable information. The data structure of each information is as shown in FIGS.

  The project information has a table structure in which a project key, a project name, and project individual information are associated (see FIG. 2A). The project key is an identifier for identifying a project, and is generated by the database management system 7 in accordance with a request from the tool. This project key exists uniquely and cannot be changed once generated. The project name is a representative name of the project and can be arbitrarily set by the user. The project individual information is attribute information necessary for the project.

  The device information has a table structure in which a device key, a project key, a device name, and device individual information are associated (see FIG. 2B). The device key is an identifier for identifying a device, and is generated by the database management system 7 in accordance with a request from the tool. This device key exists uniquely, and once generated, it cannot be changed. The device name is a representative name arbitrarily set for the device by the user. The device individual information is attribute information necessary for the device, and includes, for example, device model information and comments. The project key in the device information table is a project key reference in the project information table shown in FIG. 2A, and is selected from the project table.

  The memory map information has a table structure in which a map key, a project key, a device key, a map name, a type, and map individual information are associated with each other (see FIG. 2C). The map key is an identifier for identifying the memory map, and is generated by the database management system 7 in accordance with a request from the tool. This map key exists uniquely and cannot be changed once generated. The map name is a representative name arbitrarily set by the user to the device. The map individual information is attribute information necessary for the memory map, and includes, for example, unit model information, comments, and unit number. The project key and device key in the map information table are the project key reference in the project information table shown in FIG. 2A and the device key reference in the device information table shown in FIG. Yes, select from each table.

  Memory allocation information includes an allocation key, a project key, a device key, a map key, an allocation name, a usage, an area, a start address, an end address, a link destination key, and individual allocation information. The table structure is related (see FIG. 3A). The allocation key is an identifier for identifying the memory allocation, and is generated by the database management system 7 in accordance with a request from the tool. This assignment key exists uniquely and cannot be changed once it is generated. The allocation name is a representative name arbitrarily set by the user for memory allocation. The use specifies the use / type of data stored in the allocated memory area. The usage includes “input”, “output”, “input / output”, “system reservation”, etc., and is selected from the specified values displayed in a list. The area is an area type of the memory, and includes DM (Data Memory), CIO (Channel I / O), and the like. The start address and the end address are an allocation area start address and an allocation area end address for specifying the range of the allocated memory area, respectively. The allocation individual information is attribute information necessary for allocation. The project key, device key, and map key in this memory allocation information table are the project key reference in the project information table shown in FIG. 2A and the device in the device information table shown in FIG. 2B, respectively. This is a key reference, which is a map key reference of the memory map information table shown in FIG. 2C, and is selected from each table. The link destination key is a link key reference of a table of the memory link table shown below, and this is also selected from the table.

  The memory link table stores information for performing a data link between a plurality of PLCs, and includes a link key, a link number, a link name, an allocation source key, an allocation destination key, link individual information, Are related to each other (see FIG. 3B). The link key is an identifier for identifying a link, and is generated by the database management system 7 in accordance with a request from the tool. This link key exists uniquely, and once generated, it cannot be changed. The link number is the number of links included in one link group, and is generated by the database management system 7. The link name is a representative name arbitrarily set for the link by the user. The link individual information is attribute information necessary for the link, and includes a comment and a last update date. The allocation source key is an allocation key (reference to the allocation key in the memory allocation information table in FIG. 2D) that specifies a memory area in which data to be transmitted is stored, and is selected from the memory allocation information table. To do. Similarly, the allocation destination key is an allocation key (reference to the allocation key in the memory allocation information table of FIG. 3A) that specifies a memory area in which data to be transmitted is stored. Select from the table.

  The variable information has a table structure in which a variable key, a project key, a device key, a category, a variable name, an address, a data type, a size, an allocation key, and individual variable information are associated with each other. (See FIG. 3C). The variable key is an identifier for identifying a variable, and is generated by the database management system 7 in accordance with a request from the tool. This variable key exists uniquely and cannot be changed once generated. As the category, a category (group) to which the variable belongs is registered. This is a name for managing variables divided into categories (groups). The variable name is a name of the variable arbitrarily by the user. The address is the address of the memo mark indicated by the variable. The data type is registered from the data type and selected from the specified values. The size defines how many data types exist, and can be set arbitrarily. The allocation key is an allocation key for memory allocation including variables. The individual variable information is attribute information necessary for the variable, and is inconsistent. The project key, device key, and map key in this memory allocation information table are the project key reference in the project information table shown in FIG. 2A and the device in the device information table shown in FIG. 2B, respectively. This is a key reference, which is a map key reference of the memory map information table shown in FIG. 2C, and is selected from each table. The link destination key is a link key reference in the table of the memory link table shown below, and includes a comment and a last update date.

  Hereinafter, functions of each processing unit will be described while explaining procedures for executing various actual processes. 4 and 5 are flowcharts showing processing functions of the PLC setting tool (Tool. A).

  First, the user operates the input device of the control system setting device 2 to generate a new project. That is, the process of the PLC setting tool prompts the input of the project name, and the user inputs the project name, so that a common project name is set in the system configuration tool (S1). As an example, the project name is “PJ1”.

  The PLC setting tool sets the set project name in the memory map database of the shared storage 6 (S2). At this time, the project creation date and time, comments, etc. may be registered. Specifically, the PLC setting tool passes the project name to the database management system 7 and makes a new registration request. The database management system 7 generates a project key for the received project name, and registers the project key and the project name in association with each other in the project information table in the memory map database of the shared storage 6. When the registration is completed, the database management system 7 returns the generated project key (for example, “P_Key1”) to the PLC setting tool.

  FIG. 6 shows an example of the project information table generated by executing the processing step S2. As shown in the figure, the project name “PJ1” passed from the PLC setting tool and the project key “P_Key1” generated by the system are registered in association with each other. Further, in the illustrated example, date / time data in which the project information is registered is associated and stored as individual project information. The registered date / time data can be stored and held by, for example, referring to an internal clock when the database management system 7 performs registration processing and recording the date / time data at that time.

  Next, the PLC setting tool causes the user to input the PLC name, model information communication setting, and the like (S3). For example, it is assumed that the PLC name “PLC-1” and the model “CS1H” are input.

  The PLC setting tool registers this input information in the device information table in the memory map database of the shared storage 6 (S4). Here, the project key (P_Key1) acquired by the PLC setting tool at the time of project registration is passed as the project key. The database management system 7 generates a device key for the received device name (here, “D_Key1”) and stores it in the device information table together with the received information. Further, the database management system 7 returns the generated device key to the PLC setting tool.

  FIG. 7 shows an example of a device information table generated by executing the processing step S3. As illustrated, the device key “D_Key1” generated by the system, the project key “P_Key1” and the device name “PLC1” passed from the PLC setting tool are registered in association with each other. Further, in the illustrated example, the device type “CS1H” (this information is also passed from the PLC setting tool) is stored in association with the device individual information.

  Next, the PLC setting tool registers the system reserved area of the memory determined by the PLC type in the memory map information table or the like (S5). That is, when the PLC model is determined, it is determined how and which memory area of the physical memory of the control device is occupied by this model. Therefore, the PLC setting tool registers this information in the memory map information table in the memory map database of the shared storage 6 and the memory allocation information area via the database management system 7. Specifically, first, the fact that the memory is occupied as a system area is registered in the memory map information table. That is, as shown in FIG. 8, the project key and the device key each register a key acquired from the database management system 7. The PLC setting tool uniquely assigns the map name in response to input from the user. Here, “System1” is assumed. Since the type is occupied as a system area, “System” is set. Note that the memory map individual information is not particularly necessary and need not be input. When these registrations are made, the database management system 7 generates a map key, registers it in the memory map information table, and returns it to the PLC setting tool. Here, “M_Key1” is returned.

  Also, the memory area occupied by the PLC model is divided into several areas. For example, it is assumed that DM10000 channel to 12000 channel, CIO2000 channel to CIO2500 channel, and CIO3000 to CIO3500 channel are occupied. Then, the memory allocation information table is as shown in FIG. In this case, the project key, device key, and map key are those passed from the database management system 7 respectively. The assigned name is a name that is easy to understand the contents of the system reservation, and is set automatically by the PLC setting tool or set by user input. In the illustrated example, Sys1, Sys2, and Sys3 are set. The usage is selected from predetermined usage types. Here, the system area and the In area (S_I) or the Out area (S_O) are registered. Since the link key is not used at this stage, it is not registered. By executing this processing step S5, registration of the PLC (control device) is completed.

  Several units are attached to the PLC for control. Therefore, the unit (device) is registered next. That is, a tool for creating a PLCIO configuration is activated with the project name and PLC name as arguments (S6). The tool may be realized as a part of the function of the PLC setting tool or may be a separate tool.

  After the tool is activated, unit (device) addition / update processing is executed (S7). Specifically, the unit addition / update processing is executed by the flowchart shown in FIG. When the tool receives an input of unit addition / change processing from the user (S10), the tool determines the processing content (S11). When the processing content is changed, the tool changes the model information and unit registration information of the changed device (S12). When the processing content is added, the tool specifies the device type of the device used in the PLC designated by the user (S13).

  Units (devices) include simple IO units, high-function IO units, and CPU high-function units that perform communication and control. The way of occupying the memory differs depending on the unit (device). In some cases, the memory area to be automatically used is determined depending on the type of device, and in other cases, the area is determined by a tool in accordance with a user input.

  Therefore, the tool determines whether or not the memory allocation of the added / changed processing target device can be automatically performed (S14). When the memory allocation of the device to be processed can be automatically performed, the tool registers information on the specified model in the memory map database (S15). Next, the tool registers the memory information allocated by the unit (device) in the memory map information table of the memory map database (S16). At this time, the usage of the memory (IN, OUT, etc.) is also registered.

  When the unit type is determined in a simple IO unit, the memory area is occupied from the 0th channel of the CIO in ascending order of slot number. For example, when the AC 16-point input unit (CS1W-IA111) is placed in slot 0 and the relay contact 16-point output unit (CS1W-OC201) is placed in slot 2, 16 points of the CIO0 channel and CIO1 channel are occupied respectively.

  Thus, in the case where the memory allocation is automatically determined according to the type of device, the memory map information is registered (see FIG. 10). As the project key and device key, the project key and device key obtained from the database management system 7 are registered. The map name is a name that indicates the map. For example, a unit, a model name, a slot number, etc. are added. Since the (UNIT_CS1W_IA111_0, unit_CS1W_OC201_1) type IO unit is a normal IO unit, the IOUnit is registered. Model information is registered in the map information. When these pieces of information are registered in the database management system 7, the database management system 7 generates a map key, registers it in the database, and returns the map key to the tool.

  Next, the information of the occupied area is registered in the database as memory allocation information (see FIG. 11). For the project key, device key, and map key, key information acquired from the database management system 7 is registered. Assign a name that is easy for the user to understand. For example, “name + name indicating meaning of each area” attached in the memory map information is attached. In the above example, since only one area is occupied, the name assigned in the memory map information is used as it is. The application uses U_I / U_O indicating In and Out as a unit. For the area, start address, and end address, the type of the occupied area and the occupied address are registered. The database management system 7 generates allocation key information based on these pieces of information and returns it to the tool that issued the registration request.

  On the other hand, if automatic assignment is not possible, the tool activates the dedicated tool with the project name, PLC name, and unit information as arguments (S17). This dedicated tool is, for example, Tool. C, D, E, etc. The specific processing function of this processing step 17 is to execute the flowchart shown in FIG.

  The tool for each model takes over the project name, PLC model name, unit information, etc. from the activation source tool (S21). Such information may be acquired by input from the user. The model-specific tool connects to the memory map database based on the acquired information (S22).

  The model-specific tool acquires unit configuration information in accordance with the input from the user (S23), and compares the PLC memory allocation information determined from the configuration with the existing memory allocation information registered in the memory database 6 (S24). . At this stage, the memory allocation information generated by the tool for each model is stored in a storage device (temporary storage memory) in the tool and is not registered in the memory database.

  The existing memory allocation information read from the memory database 6 and the memory allocation information that is to be generated and registered by the model-specific tool are checked for duplication of the allocated memory areas and for improper use of the usage ( S25, S26). Memory areas include areas that can overlap and areas that should not overlap. Thus, “overlapping memory areas” means that both perform memory allocation for “areas that should not overlap”. The presence / absence of this “area duplication error” can be determined by, for example, registering areas that should not overlap in the memory map database, and reading and using the registered information by the tool for each model. Registration of such an area in the memory map database is performed by, for example, a PLC setting tool.

  Further, even if the memory area recognizes duplication, for example, when there is a difference in use such as outputting to an area to be output by another tool, it becomes “unauthorized use”. This determination as to whether or not the application is illegal is pre-registered in each tool with conditions for which the application is illegal, extracts the uses where the areas overlap in the two memory allocation information to be compared, and It may be determined whether or not the following condition is satisfied.

  If any of the branch determinations in the processing steps S25 and S26 is matched (Yes in S25 and S26), the user is warned of a setting error (S27). This warning is reported together with the type of setting error, such as duplication error or illegal use, and information specifying the area where the setting error has occurred. This warning allows the user to know that there is a duplication of memory or a difference in usage, so the memory allocation is reset. That is, it returns to process step S23 and performs a process.

  On the other hand, if a setting error has not occurred (both S25 and S26 are No), the model-specific tool adds the determined PLC memory allocation information to the memory map database. At this time, application information is also input. The actual registration process is performed via the database management system 7 (S28). Further, the model-specific tool downloads memory allocation information to the corresponding device (S29).

  The registration process using the model-specific tool will be described with a specific example. Depending on the unit (device), the area to be occupied cannot be determined simply by registering in the occupied area based on the device type, and the allocation area is determined separately based on the input of the unit setting parameter by the user. For example, in the case of a process control unit, in the unit setting, a transmission / reception area for data exchange with the PLC is registered with the setting tool of the process controller, and this information is set in the process control unit. Then, the process control unit communicates with the PLC ladder based on the set area. However, since the process control unit is set by its own tool, the PLC setting tool does not know which area the process control has set, so the area allocated by the process control unit tool is used for another purpose. there is a possibility.

  When a unit (device) is added to the device information table and the dedicated tool is activated, the process control unit setting tool is activated by taking over information such as the project key, PLC device key, and unit type.

  The process control unit setting tool accesses the memory map database based on the inherited information, and automatically generates a tool project based on the PLC name, format, and unit information. After that, register the process control program. In process control, by registering a user link table, which will be described later, data exchange between the PLC and the process control can be performed on the memory of the PLC. Here, it is assumed that the user sets the tag A on the process control to write in the CIO0 area on the PLC. In this case, the process control unit setting tool searches the memory allocation information table and checks whether the CIO0 area is not used. Then, it can be seen that this area is already used by UNIT_CS1W_IA111_0. Next, when the usage of this area is checked, it is understood that this area is an input area for U_I, that is, the PLC. Therefore, it can be understood that the assignment of the tag A in the user link table set as the output to the PLC by the process control unit has an overlapping use and is an error. Therefore, an error can be notified to the user at this point, and an error in memory allocation can be found instantly. In this way, when allocating memory with each tool, it is possible to check in advance with each tool, such as memory duplication and differences in usage.

  Next, data link setting will be described. The data link automatically updates each other's memory area using communication between a plurality of PLCs, and the memory conditions of other PLCs are always reflected in its own PLC. As shown in FIG. 13, when three PLCs (PLC1, PLC2, and PLC3) are performing data link settings, data stored in the memory area M11 of CIO000 to CIO0009 of PLC1 is stored in CIO000 to CIO0009 of PLC2. It is stored in the memory area M12 and the memory area M13 of CIO000 to CIO0009 of PLC3. Thereby, PLC2 and PLC3 share the data which PLC1 has. Similarly, the data stored in the memory area M22 of the CIO010 to CIO0019 of the PLC2 is shared by the PLC1 and the PLC3, and the data stored in the memory area M33 of the CIO020 to CIO0029 of the PLC3 is also shared by the PLC1 and the PLC2.

  When setting this data link, it is necessary to allocate memory for the shared memory area, but the memory area to be allocated overlaps with the memory area that has already been allocated by other tools. If left untouched, it may malfunction. Therefore, “memory allocation setting check” that is performed at the time of registration processing using the model-specific tool for the above-described device is also performed at the time of memory link setting. The function of the data link setting tool for executing the check process is as shown in the flowchart of FIG.

  The data link setting tool takes over the project name and the like from the activation source tool (S31). Such information may be acquired by input from the user. The data link setting tool connects to the memory map database based on the acquired information (S32).

  The data link setting tool acquires the memory allocation and link information shared by each communication unit, which is set in the device connected to the network and performs the data link in accordance with the input from the user (S23), and is determined from the configuration. The memory allocation information is compared with the existing memory allocation information registered in the memory database 6 (S34).

  Presence or absence of duplication of the allocated memory area and whether or not the application is illegally used between the existing memory allocation information read from the memory database 6 and the memory allocation information generated by the data link setting tool and to be registered in the memory map database Is checked (S35, S36). The determination of the presence of “area duplication error” and the determination of the presence of “unauthorized use” are the same as the determination in the above-described tool for each model.

  If any of the branch determinations in the processing steps S35 and S36 is met (Yes in S35 and S36), the user is warned of a setting error (S37). This warning is reported together with the type of setting error, such as duplication error or illegal use, and information specifying the area where the setting error has occurred. This warning allows the user to know that there is a duplication of memory or a difference in usage, so the memory allocation is reset. That is, it returns to process step S33 and performs a process.

  On the other hand, if a setting error has not occurred (No in S35 and S36), the data link setting tool adds the PLC memory allocation information determined from the configuration to the memory map database. At this time, application information is also input. The actual registration process is performed via the database management system 7 (S38). Further, the data link setting tool downloads the data link configuration information to the corresponding device (S39).

  Next, a specific example will be described. For example, when a data link is set between three PLCs (PLC1, PLC2, and PLC3), first, PLC information needs to be registered as device information. This information is registered by the PLC setting tool (Tool. A) or by the data link setting tool (Tool. B) (see FIG. 15). Here, the key registered with the PLC setting tool is used as the project key. In order to perform the data link, a communication unit is necessary, and this unit also occupies memory information for communication setting.

  Further, as shown in FIG. 16, in the memory map information table, map keys = “M_Key8”, “M_Key9”, “M_Key10” are registered as memory maps of data links for PLC1, PLC2, and PLC3. Since these three memory map information has the same map name as “CLK_DLK” and the type is DLK indicating a data link, it can be seen that they constitute the same data link.

  FIG. 17 shows a specific example of the memory allocation information table. As shown in FIG. 15, in order to perform data link between the three PLCs, three memory areas are allocated to each PLC. That is, the PLC1 is assigned three memory areas with the assignment keys = “O_K11”, “O_K12”, and “O_K13”, and the PLC2 has the three memory areas with the assignment keys = “O_K14”, “O_K15”, and “O_K16”. Is assigned to the PLC 3, and three memory areas of the assignment key = “O_K17”, “O_K18”, and “O_K19” are assigned. With the allocation keys = “O_K11”, “O_K14”, “O_K17”, the memory areas 0 to 9 of the respective CIOs are allocated, and with the allocation keys = “O_K12”, “O_K15”, “O_K18”, the respective CIOs are allocated. 10 to 19 memory areas are allocated. With the allocation keys = “O_K13”, “O_K16”, and “O_K19”, memory areas 20 to 29 of the respective CIOs are allocated. In the case of the present embodiment, the memory areas allocated by the data link are CIO 0 to 9, CIO 10 to 19, and CIO 20 to 29, and this memory area does not overlap with the memory areas already allocated by other tools. It is registered as it is without receiving an error warning due to a mistake. Of course, if there is a setting error such as duplication in already registered memory areas, the data link allocation information is not registered in the database.

  As shown in FIG. 18, the data link table sets an allocation key as a transmission source key and a transmission destination key. If there are two links, the link numbers are numbered 1 and 2. The direction is set to R, W, or RW depending on whether the transmission source is the Read area (data transmission from the transmission destination to the transmission source) or Write (data transmission from the allocation source to the allocation destination). The link name can be given an easy-to-understand name with a tool. For example, 1to2R (Read area from node 1 to node 3) may be added so that the direction of the link can be understood using the node number.

  As a result, when the memory is searched, if the address specified in the memory allocation table is the data link area, it can be understood from which device it is connected. For example, when the CIO 10 of the PLC 1 is searched from the memory allocation table, the usage is D_I in the DLK_CIO_RCV1 area, that is, the receive area of the data link. To see which area this is connected to, the memory link table is searched using L_K2 as a key. Then, the allocation destination key becomes O_K15, which is found to be CIO20 of M_Key9 of D_Key2 in the memory allocation table, and it is understood from D_Key2 that it is PLC2 (CJ1H) based on the device information table.

  FIG. 19 shows a variable registration process. When the user performs programming, programming using variables is convenient because only the variable table needs to be changed when the address changes, and there is no need to change the program. Even when a variable is registered, a usage check can be performed using a memory map.

  The variable registration process starts a PLC setting tool (programming tool). Then, the PLC setting tool acquires the name of the project to be processed by loading it from the user or from an existing project save file (S41). The PLC setting tool connects to the memory map database based on the acquired information (S42).

  The PLC setting tool acquires the variable name and variable address information for the corresponding PLC input from the user (S43), and compares the input address with the existing memory allocation information registered in the memory database 6 (S44). .

  The PLC setting tool determines whether or not the input address is an unusable area (S45). The unusable area is, for example, a work area of the system, and the PLC setting tool has knowledge. If the variable address is an unusable area (Yes in S45), the user is warned of a setting error (S47). This warning tells the user that he is trying to assign a variable address to the unusable area, so he can know that there is a duplication of memory or a difference in usage, so reset the memory allocation. . That is, the process jumps to the processing step S49, and No is determined in the branch determination “all variable registration complete?”, The process returns to the processing step S43 to execute the processing.

  On the other hand, if the variable address is not an illegal use area (No in S45), the user determines whether the variable being processed may be shared with other tools (S46). Such a determination is made by the user, but by inputting the determination result, the PLC setting tool recognizes the determination result of the user. If the information can be shared, the process proceeds to step S48, and the PLC setting tool registers the variable information in the memory map database. Thereby, the variable can be shared and used from other tools (S48).

  As a result, when registering a variable required for programming, if you enter the address or usage of the variable, this address does not use the system reserved area, or does not use the area input from another unit for output. Etc. can be checked when entering.

  FIG. 20 shows an example of the variable information table. For example, when the user tries to register a variable named “Input1” in the memory area of “CIO2000”, the memory allocation table is checked when the user inputs the variable table. At this time, it can be seen that CIO2000-CIO2500 is reserved as an input area by the system. Therefore, the programming tool issues a warning to the user such as "The set variable area is reserved as an input area for the system. Do you want to continue registration?" If the user chooses to register, it is registered in the variable table. When a project key, device key, variable name, address, data type, size, and comment are entered and registered in the memory map database, the database management system 7 returns a unique variable key. The category registers “¥” representing the route. Since the assignment key is not used in this case, it is blank. When a unit is registered, a memory area can be registered and a variable area can be automatically registered.

  FIGS. 21 to 24 show the functions of the memory area management tool (memory map management tool) 8. The memory map management tool 8 is a tool for accessing the memory map database to obtain memory allocation information and visually displaying the result as shown in FIG. As a result, the user can visually know what area is used for what.

  First, the memory map management tool 8 is activated, and the project name PLC model name to be processed is acquired according to the input from the user (S51). Next, the memory map management tool 8 connects to the memory map database based on the acquired project name and PLC model name, and acquires memory allocation list information (S52, S53). Based on the acquired memory allocation list information, the management tool displays the memory information on the display device (S54). An example of the display layout is shown in FIG. As shown in the figure, it can be seen at a glance which memory area is assigned with which type of data.

  Furthermore, the memory map management tool 8 of the present embodiment can select any one of “user definition area registration”, “area detailed information display”, “area link information display”, and “end processing as it is” based on a selection process from the user. It has a function to execute processing (S55 to S59).

  The “user definition area registration” process, the “area detailed information display” process, and the “area link information display” process execute the flowcharts shown in FIGS. 22, 23, and 24, respectively.

  The user-defined area registration process is a process for registering a user-defined area as memory information. The memory map management tool displays a screen for inputting user-defined area information and allows the user to input a memory allocation definition (S61). Next, the memory map management tool checks the memory map database based on the input contents (S62). That is, it is determined whether or not the address defined by the input memory allocation definition is an unusable area (S63). If it is a user-defined area or an unusable area (Yes in S63), the user is warned of a setting error (S64). Since this warning indicates that the user is about to allocate a user-defined area to an unusable area, the memory allocation is reset (S61).

  If the user-defined area is not an unusable area (No in S63), it is determined whether it is shared with other tools (whether or not memory overlap has occurred) (S65). If memory sharing has occurred, the user determines whether or not to allow such memory duplication (S66). Such a determination is made, for example, by displaying the overlapped contents on the display device, making the determination by the user while viewing it, and inputting the determination result into the tool.

  When not sharing with other tools (S65) and when duplication is allowed (S66 is Yes), the tool registers user allocation information in the memory map database (S67). Then, the tool reflects the registered contents in the memory information display area (see FIG. 25). On the other hand, when a situation occurs in which the memory area is shared with other tools and no overlap is allowed (No in S66), the process returns to the processing step S61 to reallocate the user-defined area.

  Thus, for example, when it is desired to reserve DM 10000 to 1000 channels as an area for storing recipe information of a program, these can be registered (see FIGS. 26 and 27). That is, each information is registered in the same manner as the registration of the memory map information and memory allocation information so far. The tool checks whether there are any overlaps in the area during the registration process. The usage of the memory allocation information registers A_O indicating that the user has allocated as an output area. When registration is completed, these pieces of information can be used as confirmation information for registering another memory information.

  FIG. 23 shows a display function of area detailed information. Since the user selects an area for which detailed information is to be displayed on the memory area list screen, the memory map management tool recognizes the selected area (S71). Based on the selected area information, the memory map management tool acquires area usage, allocation source unit information, variable information, and the like from the memory map database (S72), and displays the acquired detailed information (S73).

  FIG. 24 is a flowchart showing the memory area link information search / display processing function. Since the user selects an area for displaying link information on the memory area list screen, the memory map management tool recognizes the selected area (S81). The memory map management tool checks whether the corresponding area has link information from the memory map database based on the selected area information (S82). If the selected area has link information (Yes in S83), the link destination device information and memory allocation information are acquired from the memory map database based on the selected area information (S84). The device on the display screen is switched to the acquired device, the memory allocation information is displayed again, and the acquired link destination allocation information is displayed (S85). On the other hand, if the selected area does not have link information (No in S83), the fact is notified and the process is terminated (S86).

  FIG. 28 is a flowchart showing an address check function in the PLC setting tool (programming tool). Programming tools use a programming language such as ladder, ST, or FB for programming. Input memory information, output information to memory, and create a program. By executing this address check function, check the memory allocation information table to check in advance whether the corresponding area can be used. it can. For example, when a program that outputs to the area of CIO0 is described by the program, since this area is registered as an input area by UNIT_CS1W_IA111_0, it is determined that there is a program error and is notified to the user.

  Processing for realizing such a function is as follows. The PLC setting tool is a programming tool and connects to the memory map database based on the project name and PLC name (S91).

  In order to input address information used by the user during programming, the PLC setting tool acquires the address information, accesses the memory map database based on the acquired address, and acquires memory allocation information of the corresponding address (S92). , S93). Then, the PLC setting tool displays the acquired memory allocation information, usage information, and the like, and determines whether there is an address usage error (S95). If there is a usage error, the user is warned of a setting error. (S96).

It is a figure which shows an example of the system schematic diagram in this invention. It is a figure which shows an example of the data structure of a memory map database. It is a figure which shows an example of the data structure of a memory map database. It is a flowchart which shows a PLC setting tool process. It is a flowchart which shows a unit addition / update process. It is a figure which shows the specific example of a project information table. It is a figure which shows the specific example of a device information table. It is a figure which shows the specific example of a memory map information table. It is a figure which shows the specific example of a memory allocation information table. It is a figure which shows the specific example of a memory map information table. It is a figure which shows the example of a memory allocation information table. It is a flowchart which shows the tool process of an apparatus separate. It is a figure explaining a data link. It is a flowchart which shows a data link setting tool process. It is a figure which shows the specific example of a device information table. It is a figure which shows the specific example of a memory map information table. It is a figure which shows the specific example of a memory allocation information table. It is a figure which shows the specific example of a data link table. It is a flowchart which shows the registration process of a variable. It is a figure which shows the specific example of a variable information table. It is a flowchart which shows the management tool process of a memory area. It is a flowchart which shows the registration process of a user definition area. It is a flowchart which shows the display process of area detailed information. It is a flowchart which shows the display process of area link information. It is a figure which shows an example of a memory map display layout. It is a figure which shows the specific example of a memory map information table. It is a figure which shows the specific example of a memory allocation information table. It is a flowchart which shows an address check process.

Explanation of symbols

1 PLC
2 Control system setting device 3 Display 4 Control device 5 Network 6 Shared storage 7 Database management system 8 Memory map management tool

Claims (5)

A shared storage for holding configuration data describing the allocation information of the physical memory of the control device;
A plurality of tools for accessing the shared storage and reading and writing the setting data,
The tool is
When performing the memory allocation for the physical memory, an already set allocation information held in the shared storage is read, and an area duplication error occurs in a memory area to which the memory allocation is performed based on the read allocation information. A determination means for determining whether or not
Means for adding information on memory allocation performed by the tool to the setting data of the shared storage on condition that the area duplication error is not detected by the determination means;
A control system setting management system comprising: a setting unit configured to set a device based on memory allocation performed by the tool on condition that an area duplication error is not detected by the determination unit. The memory allocation for the physical memory performed by the tool includes one automatically allocated according to the type of model or one that the user independently declares occupation of the physical memory area. Control system setting management system. The setting data stored in the shared storage also includes link information of the memory between the devices in a control system that links and uses physical memory across a plurality of devices,
3. The function according to claim 1, wherein the determination unit has a function of determining whether an area duplication error has occurred in a memory area to which the memory allocation is to be performed based on the link information. Control system setting management system. The setting data stored in the shared storage has usage attributes for each memory allocation,
4. The method according to claim 1, wherein the determination unit has a function of determining whether or not duplication is permitted based on the use attribute when the allocation areas overlap. 5. The control system setting management system described. The variable information allocated to the physical memory is recorded, and the allocation information of the physical memory is linked to the variable information so that the plurality of tools can share the variable information belonging to the physical memory and the area. The control system setting management system according to any one of claims 1 to 4.

Images