JP5233544B2 - POU mounting method - Google Patents

Description

  The present invention relates to a POU mounting method in a programmable controller (PLC), and more particularly, to a configuration of a POU for executing a program compliant with IEC61131-3 (JISB3503), transfer of POU variables, and initialization processing.

(1) POU definition and instantiation In IEC61131-3 (JlSB3503), a program created by a user is registered as a type called POU (Program Organization Unit). As shown in FIG. 4, the POU includes a variable definition unit 10 and a body unit (algorithm) 20. When the POU is executed, the POU instance is assigned with the operation data area (instance) having the configuration defined by the variable definition unit 10. A POU is a type, and different POU instances can be obtained by preparing different instances for one POU.

  For example, in FIG. 4, when a POU called “pump operation” is created and there are pumps P1, P2, and P3 as calculation targets, three instances INS1, INS2, and INS3 are prepared, so that different pumps are the same. It can be calculated using POU.

  Such a process is called instantiation of the POU. The body part 20 that is an arithmetic algorithm is common to each instance.

  In IEC61131-3 (JISB3503), the POU definition and the POU instance are managed separately, and are usually managed as separate files in the programming tool (see, for example, Patent Document 1).

(2) Variable attributes In IEC61131-3 (JISB3503), attributes as shown in Table 1 can be given to variables.

  These designations can be made in the variable definition part of the POU definition or in the POU instance. For example, the variable definition unit 10 of the POU definition in FIG. 4 defines variable A as an initial value = 0, initial value = 1 in instance INS1, initial value = 2 in instance INS2, and initial value = 3 in instance INS3. be able to. That is, the attribute set in the variable definition unit 10 of the POU definition can be overwritten with the POU instance. With this function, different initial values can be set for each instance. The PLC executes the initialization of the instance area while referring to the attribute set at the start of calculation. That is, it is necessary to store the POU definition and the POU instance definition on the PLC main body side.

(3) POU definition file and POU instance definition file As described above, it is necessary to store the POU definition and the POU instance definition in the PLC body in order to initialize the instance area. Initialization processing is first executed according to the POU instance definition, and if there is no attribute setting in the POU instance definition, initialization is performed according to the POU definition. FIG. 5 shows a variable initialization process flow.

  In FIG. 5, among the plurality of variables, the first variable is read (S1), and whether or not the variable has a holding attribute (RETAIN) set in the POU instance (S2) is set as a holding attribute. If the check is not completed for all variables, the initialization process is started for the next variable (S4).

  When the holding attribute is not set in the POU instance (S2), it is checked whether an initial value or a constant (CONSTANT) is set in the POU instance (S5). The initial value or constant attribute is written (S6), and the next variable is checked (S3). If it is not set, it is checked whether or not an initial value or constant is set in the POU definition (S7). If it is set, the initial value or constant attribute is written in the instance area (S6). If not set, the default is the initial value, and the next variable is checked (S3).

  In order to perform the variable initialization process as described above, it is necessary to have both the POU definition and the POU instance definition in the PLC body. These are created by a programming tool and transferred to the PLC main body by a method such as communication. In general, these are more convenient for communication if treated as a file, as described below.

(A) POU definition file The POU definition file has a variable definition part and a body part. The variable definition section stores information such as variable names, types, attributes, initial values, and physical addresses. An algorithm is stored in the body part, specifically, a PLC machine code and an intermediate language image are stored.

(B) POU instance definition file The POU instance definition file only needs to have a variable definition section. This is because the algorithm of the POU definition file can be used. The variable definition part must be equivalent to the POU definition file.

(4) Variable definition In the POU definition file and the POU instance definition file, variables are individually defined in the variable definition section. Table 2 shows the variable definition items and their descriptions.

JP 2008-040996 A

  The POU definition file and the POU instance definition file become larger as the number of variables increases. Even if it is a Boolean variable, information about each one is required. In general, the PLC is mainly a program that handles BOOT data. Therefore, when there are many variables to be used, the POU definition file and the POU instance definition file become large.

  For example, if the variable definition shown in Table 2 requires 64 bytes for each variable, there are only 100 BOOL type variables, and the variable definition requires 6400 bytes. Essentially, such a large amount of information is required for a 100-bit variable. This causes the following problems.

  (1) The PLC main body requires a lot of memory.

  (2) Since the memory capacity is large, the cost of the PLC increases.

  (3) The data transfer time from the programming tool to the PLC main body becomes longer.

  An object of the present invention is to provide a POU mounting system that reduces the memory capacity for mounting POU variables and simplifies POU transfer and variable initialization processing.

  In order to solve the above problems, the present invention integrates the variable definition information of the POU definition file into the variable definition of the POU instance definition file, deletes the variable definition part from the POU definition file transmitted to the PLC body, and The variable definition part of the file has a file structure that defines variables for the entire instance area, and the variable definition part sets attribute data that specifies the initial value / constant area of the instance area and the value to be written to this specified area The instance area can be initialized by initial value data, and when the physical address is specified by the attribute data, the initialization process can be performed by adding the direct expression variable definition data. To change the initial value / constant of the instance area, add online change data. Obtained by the possible changes in inline, characterized by the following mounting method.

(1) Transfer the POU definition file and POU instance definition file that was created in the programming tool to the PLC, a mounting method of POU PLC body to slide into initialize the variable data to be set to an instance area of the data memory at the time of start-up ,
The programming tool is a variable definition part of the POU instance definition file, and refers to the variable in the POU definition file only when the variable attribute is not set in the variable definition part. POU instance definition file that overwrites the variable definition information of the POU instance definition file with the value, and that the POU definition file is composed only of the body part and overwrites the setting values of the body part of the POU definition file and the variables of the POU definition file. and wherein the transfer of bets on the PLC main body.

  (2) The variable definition section of the POU instance definition file is characterized in that it has a file configuration for defining variables for the entire instance area set in the PLC main body.

  (3) The variable definition section of the POU instance definition file includes attribute data for specifying an initial value / constant area of the instance area, and initial value / constant data for setting a value to be written in the specified area, and the PLC The main body includes means for initializing the instance area with the attribute data and the initial value data.

  (4) The variable definition section of the POU instance definition file includes direct expression variable definition data that provides variable definition data when an instance area is specified by a physical address in the attribute data.

(5) The variable definition unit of the POU instance definition file is an online function that provides change data to the instance area to be changed when the initial value / constant of the instance area is changed online while the PLC body is executing an operation. It is characterized by having change data.

  As described above, according to the present invention, the variable definition information of the POU definition file is integrated into the variable definition of the POU instance definition file, the variable definition part is deleted from the POU definition file transmitted to the PLC main body, and the POU instance definition file The variable definition part has a file structure that defines variables for the entire instance area, and the variable definition part is the initial value that sets the attribute data that specifies the initial value / constant area of the instance area and the value that is written to this specified area. The instance area can be initialized by the value data, and when the physical address is specified by the attribute data, the initialization process can be performed by adding the expression variable definition data directly. To change the initial value / constant of the area, add online change data. Since you can also be changed in emissions, the initialization process of transferring or variables POU while being reduced memory capacity for implementing POU variables is simplified.

  FIG. 1 is a main part configuration diagram of a programmable controller (PLC) showing an embodiment of the present invention, and shows only a part related to a POU mounting system.

  The programmable controller (PLC) is configured by a PLC main body 100 and a programming tool (programming device) 200. The PLC main body 100 stores a main program, a POU definition file, and a POU instance definition file in the program memory 11, stores defined variables and input / output data in the data memory 12, and uses programs and data that are read sequentially from these. Then, the expected sequence calculation is executed by the calculation unit 13. Reference numeral 15 denotes a data input / output unit that inputs or outputs data to / from an apparatus to be controlled or processed by the controller 100.

  The programming tool 200 uses a personal computer or the like to define and create a POU definition file and a POU instance definition file, construct an application program by combining these, and transfer the program and data to USB, Ethernet (registered trademark), RS Transfer to the PLC main body 100 using the -232C port.

  In the programmable controller (PLC) as described above, the following POU mounting method is used in the embodiment of the present invention.

(1) Integration of POU definition initialization data into the POU instance definition file It is necessary to initialize variables when starting the PLC. FIG. 5 shows the procedure. In FIG. 5, initialization is performed according to the contents of the POU instance definition file and the POU definition file. Thereby, it is possible to cope with a case where the constant set in the POU definition and the constant set in the POU instance definition are different. Here, if no initial value or constant is set in the POU instance, the POU definition is referred to, and if there is an initial value / constant, initialization processing is performed using the initial value / constant as an initial value / constant.

  Therefore, integration is performed to include initialization information of the POU definition file in the variable definition part of the POU instance definition file. That is, only when the variable attribute is not set in the POU instance definition file, the variable in the POU instance definition file is referred to and the initial value / constant is set there. / Overwrite constants.

  By doing so, the PLC main body does not need to refer to the POU definition file for variable initialization, the variable initialization process at the start of the PLC operation is simplified, and the PLC startup time is shortened.

  From the above, the programming tool 200 includes the contents of the variable definition part A of the POU definition file 22 in the variable definition part a of the POU instance definition file 21 as pre-processing for transmitting the POU instance definition file to the PLC main body 100. It is converted into the (integrated) POU instance definition file 23 and transmitted. That is, the original POU instance definition file 21 is converted into a file called a POU instance definition file 23 and transferred to the PLC main body 100.

  In this way, by integrating the variable definitions in the POU definition file into the POU instance definition file, the variable initialization processing unit 14 of the PLC main body 100 performs initialization processing by directly referring to the variable definitions included in the same file. Therefore, the variable initialization process at the start of the PLC operation can be simplified, and the PLC activation time can be shortened.

(2) Deleting the variable definition part from the POU definition file By integrating the variable definition part, the PLC main body 100 does not use the variable definition part of the POU definition file. Therefore, when the programming tool 200 transmits the POU definition file 22 to the PLC main body 100, it is converted into the POU definition file 24 from which the variable definition part is deleted and transferred. That is, the original POU definition file 22 is transferred as a POU definition file 24 only for the body part B.

  Thus, since the POU definition file 24 to be transferred to the PLC main body 100 does not have the variable definition part A, the size of the POU definition file 24 to be transferred is reduced, and the memory size required for the PLC main body 100 can be reduced and transferred. You can save time.

(3) Configuration of POU Instance Definition File The variable definition part a in the POU instance definition file 21 includes information such as variable attributes and variable names of each variable. When the PLC main body 100 initializes a variable, what is really necessary is an attribute of each variable, an initial value / constant, and a variable address. Therefore, instead of having one variable definition at a time, the variable definition is for the entire instance area. Specifically, the file structure (data items and contents) shown in Table 3 below is used.

Of the items in the table, the file header writes the header information of the POU instance definition file. Specifically, the layer data such as the size of attribute data and initial value data has the same size as the instance area, and indicates where in the instance area is the initial value / constant. When the target data is BOOL, the initial value / constant is in units of bits, and in the case of WORD, it is in units of 16 bits. This makes it possible to initialize without considering the data type of the target variable. For example, 1 is an initial value / constant attribute, and 0 is a holding attribute.

  The initial value data has the same size as the instance area, and sets a value to be written in the area designated as the initial value / constant in the attribute data. When the target data is BOOL, the initial value / constant is in units of bits, and in the case of WORD, it is in units of 16 bits. This makes it possible to initialize without considering the data type of the target variable.

  Thus, the variable definition for the entire instance area reduces the size of the POU instance definition file 23. For example, when 100 INT type variables are defined, if the original POU instance definition file uses 64B with one variable, 64B × 100 = 6400B is required. However, in the variable definition method for the entire instance area, the attribute data is 100 W (200 B), the initial value data is 100 W (200 B), the file header is several words, the size is 500 B or less, and the size is 1/10 or less. Become.

  Thus, by changing the configuration of the POU instance definition file 23, the file size transmitted to the PLC main body 100 can be greatly reduced. For this reason, the memory size required for the PLC main body 100 can be reduced, and the transfer time can be shortened.

(4) Variable initialization process By integrating the variable definitions and changing the configuration of the POU instance definition file, the variable initialization process performed at the start of the operation of the PLC main body 100 becomes very simple.

  Specifically, using the attribute data and initial value data of the POU instance definition file 23, the instance area can be initialized in units of 16 bits or 32 bits. Moreover, it can be initialized at once regardless of the data type of the variable.

  FIG. 2 shows a variable initialization processing flow by the variable initialization processing unit 14, which is a case where initialization is performed in units of 16 bits, which is much simpler than FIG. FIG. 3 is a schematic diagram of the initialization process according to FIG. 2, and the initialization process will be described with reference to this figure.

  In FIG. 1, the attribute data of the instance area of the data memory 12 has the same size as the instance area from the definition of Table 3 above, and where (which bit) of the instance area is the initial value / constant. In FIG. 3, the first 16 bits are logical “1”, and the corresponding 16 bits of the instant area are associated with the initial value / constant. In addition, the initial value data has the same size as the instance area from the definition in Table 3, and the initial value written in the area designated as the initial value / constant in the attribute data is set. Is written with an initial value (binary number).

  In FIG. 2, first, the top instance area of the POU instance definition file 23, its attribute data, and initial value data are obtained (S11). Of these data, the negative logical product of the instance area (16 bits) and the attribute data (16 bits) is stored in the work memory (S12). By this processing, 16-bit data in which all the bits in which the initial value / constant of the instance area is written is set to “0” is stored in the work memory WM1 shown in FIG.

  Next, the logical product of the attribute data (16 bits) and the initial value data (16 bits) is stored in the work memory WM2 (S13). By this processing, 16-bit initial value data is stored in the work memory WM2 shown in FIG.

  Next, the logical sum of the work memory WM1 and the work memory WM2 is stored in the instance area (16 bits) (S14).

  By these processes, the initial value data is written in the instance area as it is, and the initialization of the instance area is completed. When all the attribute data is “0”, all “0” is stored in the work memory WM2, the instance area data is stored in the work memory WM1, and the logical sum is updated to the instance area data itself. Is done.

  It is checked whether or not initialization has been completed for one instance area (S15). If not, the next instance area (16 bits), attribute data, and initial value data are obtained. It is repeated that the instance area is initialized.

  Thus, by providing the attribute data and the initial value data as the configuration of the POU instance definition file, the variable initialization process at the start of the PLC operation can be simplified, and the PLC activation time can be shortened.

(5) Correspondence to Physical Address In the POU instance definition file 23 shown in FIG. 1, when the instance area is specified by the physical address in the attribute data, the variable cannot be initialized with the initialization process flow of FIG.

  Therefore, the structure of the POU instance definition file shown in Table 4 below is used, and the direct expression variable definition data is used only when the physical address is designated as the variable.

  Of Table 4 above, the difference from Table 3 is that the file header is changed and expression variable definition data is added directly. The file header indicates header information of the POU instance definition file. Specifically, in addition to the size of attribute data and initial value data, the number of direct expression variables is required. The direct expression variable definition data is variable definition data when a physical address is specified by a variable attribute, and is arranged in the required number. The configuration is the same as in Table 2 above.

In this way, by directly adding the expression variable definition data as an item of the POU instance definition file, when the physical address is specified by the variable attribute, it can be handled using the expression variable definition data directly.

(6) Response to online change The POU instance definition file may be changed online while the PLC main body 100 is performing a calculation operation. That is, the initial value / constant is changed online. Although the initialization process for the instance area is performed at the start of the PLC calculation, it is necessary to initialize only the changed part even when the online change is performed.

Therefore , the POU instance definition file is configured by adding online change data in addition to the configuration of Table 4. Similar to the attribute data, this data also has a meaning in bit units, and only the logic “1” part is subject to online change.

  Specifically, as in the initialization process of FIG. 2, the logical product (A) of the initial value data and the online change data and the negative logical product (B) of the instance data and the online change data are obtained, and A and B Can be written in the instance data.

  Thus, by adding online change data as an item of the POU instance definition file, it becomes possible to cope with online change of variables.

The principal part block diagram of the programmable controller (PLC) which shows embodiment of this invention. Variable initialization process flow. The schematic diagram of an initialization process. POU definition and instantiation. Variable initialization process flow.

Explanation of symbols

DESCRIPTION OF SYMBOLS 100 PLC main body 200 Programming tool 11 Program memory 12 Data memory 13 Calculation part 14 Variable initialization process part 15 Input / output part 21, 23 POU instance definition file 22, 24 POU definition file

Claims (5)

Transfer the POU definition file and POU instance definition file that was created in the programming tool to the PLC, a mounting method of POU PLC body to slide into initialize the variable data to be set to an instance area of the data memory at startup,
The programming tool is a variable definition part of the POU instance definition file, and refers to the variable in the POU definition file only when the variable attribute is not set in the variable definition part. POU instance definition file that overwrites the variable definition information of the POU instance definition file with the value, and that the POU definition file is composed only of the body part and overwrites the setting values of the body part of the POU definition file and the variables of the POU definition file. mounting method of POU, characterized in that to transfer the bets on the PLC main body.   2. The POU mounting method according to claim 1, wherein the variable definition section of the POU instance definition file has a file configuration that performs variable definition for the entire instance area set in the PLC main body.   The variable definition section of the POU instance definition file includes attribute data that specifies an initial value / constant area of an instance area, and initial value / constant data that sets a value to be written to the specified area. 3. The POU mounting method according to claim 1, further comprising means for initializing the instance area using attribute data and initial value data.   The variable definition unit of the POU instance definition file includes direct expression variable definition data that provides variable definition data when an instance area is specified by a physical address in the attribute data. The POU mounting method according to any one of the above items. The variable definition part of the POU instance definition file stores online change data that gives change data to the change target instance area when the initial value / constant of the instance area is changed online while the PLC main body is executing an operation. The POU mounting method according to claim 1, wherein the POU mounting method is provided.

Images