JP6926841B2 - Control system, development support device, and control method - Google Patents

Description

The present invention relates to a control system, a development support device, and a control method.

During the operation of the plant system, some instruments may break down and normal values may not be captured. In such a case, the operator forcibly sets the value to the variable for substituting the value output from the failed instrument by using a monitoring device or the like in order to prevent the operation of the system from being affected. It may be required to set (hereinafter, the setting is also described as a compulsory setting, and the compulsorily set value is also described as a compulsory setting value) and continue the operation of the system. However, in many cases, the operator is not familiar with the program running within the controller of the system, which can make it difficult to perform forced settings, for example using engineering tools.

Japanese Unexamined Patent Publication No. 2010-122824

Programs that run in the system controller are often made into parts in order to improve development efficiency and quality. It cannot be said that the contents of a program that has been made into parts are likely to be seen by the operator, and the contents are often hidden so that the contents cannot be seen. Therefore, it is unlikely that the operator will forcibly set the value of the variable of the program that is partized for the normal processing of the system in the plant. Here, in compiling the program necessary for operating the system, even if a machine language object for forcibly setting is generated for the variables in the program that is made into parts, the forcible setting process using the machine language object is generated. Does not lead to reduction of the processing load by the operator, and such forced setting is often useless processing, and there is a problem that the execution time of the application may become unnecessarily long.

An object of the present invention is to generate an optimized machine language object in view of the above-mentioned current situation and to shorten the execution time of the control process.

The control system according to an example of the embodiment includes a development support device that generates a machine language object from each of one or more programs in the input source code, and a control device that executes the machine language object acquired from the development support device. Be prepared. The development support device is forcibly set for the first program included in the library and the calling program is also included in the library among the one or more programs by using the calling relationship between each of the one or more programs. Is generated, and the first machine language object is generated from the first program based on the forced setting possibility information. The control device controls the first controlled device corresponding to the first variable in the first program based on the first machine language object without forcibly setting.

It is possible to generate an optimized machine language object and shorten the execution time of control processing.

It is a figure which illustrates the structure of the control system which concerns on 1st Embodiment. It is a figure which illustrates the development environment provided to a user. It is a figure which illustrates the call relation information. It is a figure which illustrates the instance program correspondence information. It is a figure which illustrates the list of compulsory setting possibility information. It is a figure which illustrates the flow of the generation processing of the compulsory setting possibility information list by a front-end compiler. It is a figure which illustrates the flow of the acquisition process of the name of the calling program. It is a figure which illustrates the flow of processing by a back-end compiler. It is a figure which illustrates the machine language generated by the back-end compiler. It is a figure which illustrates the hardware configuration of the support device. It is a figure which illustrates the hardware configuration of a controller. It is a figure which illustrates the structure of the control system which concerns on 2nd Embodiment. It is a figure which shows the example of the image displayed on the forced setting screen. It is a figure which illustrates the forced setting instruction information generated by the monitoring apparatus which concerns on 2nd Embodiment. It is a figure which shows the display example of the compulsory setting support information list in 2nd Embodiment. It is a figure which illustrates the list of compulsory setting address information in 2nd Embodiment. It is a figure which illustrates the hardware configuration of the monitoring apparatus.

(First Embodiment)
FIG. 1 shows an example of the configuration of the programmable controller system 1 according to the present embodiment. The programmable controller system 1 may be referred to as a control system 1. The control system 1 includes one or more development support devices 2 and a control device 3, respectively. The development support device 2 may be referred to as a support device 2, and the control device 3 may be referred to as a controller 3. In FIG. 1, for easy understanding, one support device 2 and one controller 3 in the control system 1 are shown.

The support device 2 generates a machine language code executed by the controller 3 based on the source code input from the user. At this time, in the support device 2, whether or not the variable corresponding to the device controlled by the controller 3 (also referred to as the control target device) or the variable corresponding to the control target item of the control target device can be the target of the compulsory setting. Is determined, and a machine language corresponding to this is generated.

It is assumed that the variables here include, for example, members of a structure in C language, etc., in addition to the variables of the basic type. The variables are described in the source code of the program and are associated with the control target device and the control target item (the control target device and the control target item are collectively referred to as the control target device). By substituting the forced setting value into this variable, the controlled device is forcibly set. It should be noted that the assignment of the compulsory setting value to the variable in the program is also described as the compulsory setting of the program, the compulsory setting for the program, and the like.

The program refers to a program in a broad sense. For example, in IEC61131, it is a POU (Program organization unit) and has a broader meaning than a PG (Program).
In addition, the program converted into machine language is described as a machine language object.

The controller 3 controls the controlled device by acquiring the machine language object from the support device and executing the machine language object. The controller 3 is provided with a storage unit (first storage unit 32) described later, and one or more variables are assigned to the addresses of the storage units. Here, for the sake of comprehension, a case where one variable is assigned to one address will be described.

When executing the compulsory setting process, the controller 3 stores the compulsory setting value in the storage area of the address to which the variable to be the compulsory setting is assigned.

As shown in FIG. 1, the support device 2 includes a user interface 20, a project management unit 21, a compiler 22, a storage unit 23, a communication unit 24, and the like. The compiler 22 includes a front-end compiler 220 and a back-end compiler 221. The storage unit 23 stores a project program list 230, variable / address correspondence information 231, instance / program correspondence information 232, call-related information 233, forced setting availability information list 234, forced setting position information list 235, and the like. ..

The project management unit 21 is connected to the user interface 20, the compiler 22, and the storage unit 23. Further, the compiler 22 is connected to the storage unit 23 and the communication unit 24. Note that there may be a connection relationship other than these, and the connection relationship is not limited to the above.

The controller 3 includes a communication unit 30, a program execution management unit 31, a first storage unit 32, and a second storage unit 33. The program execution management unit 31 includes a program execution unit 310 and a compulsory setting management unit 311. The program execution management unit 31 is connected to the communication unit 30, the first storage unit 32, and the second storage unit 33. Further, the communication unit 30 is connected to the first storage unit 32 and the second storage unit 33. The connection relationship is not limited to the above.

The second storage unit 33 stores the forced setting address information list 330, the forced setting position information list 235, and the like.

First, each functional block of the support device 2 will be described. The user interface 20 is an interface for connecting an input device such as a keyboard or an output device such as a display device to the support device 2. Through the user interface 20, the support device 2 accepts input of a source code or the like from a user such as a developer, and displays an image for the user to develop on the display device.

The project management unit 21 provides a development environment to the user in order to support the development by the user. The project management unit 21 manages the source code input via the user interface 20 and outputs the source code to the compiler 22 as appropriate. Further, the project management unit 21 manages a list of project programs stored in the storage unit 23. Further, the project management unit 21 assigns a unique, for example, fixed-length number or the like to each of one or more programs to be managed. Each program in the support device 2 is managed by this number. In the following, when the program name or the program name is described, these may be such numbers.

The front-end compiler 220 generates intermediate code from the source code. At this time, the front-end compiler 220 associates the variables in the source code with either the direct address or the indirect address in the first storage unit 32, which will be described later, to generate the intermediate code. The direct address is an address that directly indicates the position of the storage area in which the variable is stored, and here, it is assumed that a relative address is also included. The indirect address is, for example, a pointer or the like, and the address of the access destination first storage unit 32 cannot be specified unless the code including the indirect address or the code obtained by converting the code into a machine language is executed. be. The intermediate code contains operators and operands (also referred to as operands). Operands are direct or indirect addresses to which variables are assigned.

Further, as will be described later, the front-end compiler 220 generates call relationship information 233 related to the call relationship between each program that is the source of those instances, based on the mutual call relationship of one or more instances in the source code. .. At this time, the front-end compiler 220 uses the instance program correspondence information 232 stored in the storage unit 23. An instance is an instance in which data is added to a program, for example, a value is assigned to a variable in the program.

The front-end compiler 220 further generates a compulsory setting possibility information list 234 based on the generated call-related information 233. As will be described later, the forced setting availability information list 234 is information indicating whether or not forced setting can be performed for each program. For example, information indicating the name of the program and whether or not forced setting is possible for the program. And include.

The back-end compiler 221 generates machine language from the intermediate code generated by the front-end compiler 220. At this time, the back-end compiler 221 refers to the forced setting possibility information list 234, and includes a jump code to the forced setting process for the program that may perform the forced setting process based on the reference. For a program that generates a machine language object and does not perform forced setting processing, a machine language object that does not include a jump code to the forced setting processing is generated.

The front-end compiler 220 or the back-end compiler 221 generates forced setting position information 235, which will be described later, and stores this in the storage unit 23.

The project program list 230 stored in the storage unit 23 is a list of programs managed by the project management unit 21. Further, the project program list 230 includes programs directly input by the user, programs made into parts, and the like.

The variable / address correspondence information 231 is information in which the variable in the program is associated with the address of the first storage unit 32 of the controller 3. The front-end compiler 220 uses the variable / address correspondence information 231 to create an intermediate code including the address to which the variable is assigned, which is the direct address in the first storage unit 32, from the source code including the variable.

The instance program correspondence information 232 is generated by the project management unit 21, and is information in which the instance is associated with the original program. The front-end compiler 220 generates call-related information 233 using the instance program correspondence information 232.

The call-related information 233 is information generated by the front-end compiler 220, and is information indicating which program the program read by the front-end compiler 220 is called or which program is called.

The compulsory setting possibility information list 234 is information generated by the front-end compiler 220 and indicating whether or not the compulsory setting is possible for the program that is the source of each instance included in the source code. Here, the program that can be forcibly set by the front-end compiler 220 is a program that is not a hidden and componentized program or a program that is directly called from a program that is not a hidden componentized program. The front-end compiler 220 does not forcibly set a program that is a hidden and componentized program and is not directly called from a program that is not a hidden componentized program.

The forced setting position information list 235 is information generated by the front-end compiler 220 or the back-end compiler 221 and is the position of the jump code to the forced setting process in the machine language object (for example, the line of the jump code in the code of the machine language object). It is a list of information in which the number) is associated with the address indicating the storage area in which the variable to be the target of the forced setting process is stored. Although the address in the forced setting position information 235 is assumed to be a direct address here, it may be an indirect address.

The communication unit 24 transmits the machine language object generated by the back-end compiler 221, the forced setting position information list 235, and the like to the controller 3.

The forced setting instruction information may be transmitted from the support device 2 to the controller 3. The forced setting instruction information is, for example, information in which the address (direct address) of the first storage unit 32 in the controller 3 is associated with the forced setting value to be assigned to the variable stored in the storage area of this address. Is. The compulsory setting instruction information may not include the compulsory setting value. In this case, the controller 3 may set the initial value or the like for the variable. Values such as the initial value are stored in advance in the second storage unit 33 or the program execution management unit 31, which will be described later. In addition, the value such as the initial value in this case is also described as the compulsory set value.

When the compulsory setting instruction information is transmitted from the support device 2 to the controller 3, the variable name of the variable to be forcibly set by the user and the compulsory setting value assigned to this variable are set by the support device 2 via the user interface 20. Is entered in. The input variable name and forced setting value are input to a setting unit (not shown) in the support device 2. The setting unit is connected to the user interface 20, the storage unit 23, and the communication unit 24. However, there may be a connection relationship other than this. The setting unit refers to the variable / address correspondence information 231 of the storage unit 23, and acquires the address of the first storage unit 32 of the controller 3 in which the variable to be forcibly set is stored. Then, the setting unit outputs the compulsory setting instruction information in which the acquired address and the compulsory setting value are related to the communication unit 24. The communication unit 24 transmits the forced setting instruction information to the controller 3. The forced setting instruction information may be transmitted from the monitoring device described later to the controller 3 instead of the support device 2 or together with the support device 2.

The communication unit 30 of the controller 3 receives the machine language object, the forced setting position information list 235, the forced setting instruction information, and the like from the support device 2, and outputs these to the program execution management unit 31. The machine language object received from the support device 2 by the program execution management unit 31 via the communication unit 30 is processed by the program execution unit 310, and the forced setting position information list 235 is stored in the second storage unit 33 by the forced setting management unit 311. Is memorized in. Further, the compulsory setting instruction information from the support device 2 or the monitoring device is processed by the compulsory setting management unit 311 here, but may be processed by the program execution unit 310.

The program execution unit 310 in the program execution management unit 31 executes the machine language object. The program execution unit 310 executes the machine language object as it is without a jump code to the forced setting process, and jumps in the machine language object with a jump code to the forced setting process. The code in which the code is replaced with the NOP (No Operation) instruction or the code for the forced setting process of the jump destination indicated by the jump code is executed. The replacement of the jump code with the NOP instruction is performed by the program execution unit 310 or the compulsory setting management unit 311 prior to the execution of the machine language object of the program execution unit 310.

The code related to the forced setting process (also referred to as the jump destination code) of the jump destination is stored in the program execution unit 310, the forced setting management unit 311, the second storage unit 33, or other storage unit (not shown). There is.

The program execution unit 310 executes a NOP instruction instead of the jump code while the forced setting instruction information is not received. As a result, unnecessary execution of forced setting processing can be avoided.

When the compulsory setting management unit 311 (or the program execution unit 310) acquires the compulsory setting instruction information, the address in the compulsory setting instruction information is stored in the second storage unit 33 in the compulsory setting position information list 235. Search for. Then, the forced setting management unit 311 (or the program execution unit 310) acquires the position of the jump code in the machine language object associated with this address. When the forced setting management unit 311 acquires the position, the forced setting management unit 311 executes a program so as to return the code at the position replaced by the NOP instruction in the machine language object to the jump code and execute the process. Instruct unit 310. In response to this, the program execution unit 310 returns the NOP instruction at the position to the jump code and executes it. The process of changing the NOP instruction to the jump code may be performed by the forced setting management unit 311. When the program execution unit 310 acquires the above position, the program execution unit 310 returns the NOP instruction at the position to the jump code and executes it.

When the address to be forcibly set in the forced setting instruction information is not stored in the forced setting address information list 330 stored in the second storage unit 33, the forced setting management unit 311 forcibly sets the address. Register in the address information list 330. The forced setting address information list 330 contains the address of the first storage unit 32 and the forced setting value set in the storage area indicated by the address in each of the one or more forced setting instruction information received by the controller 3. It is a list of information associated with each other.

When executing the jump destination code, the program execution unit 310 refers to the compulsory setting address information list 330 and acquires the compulsory setting value to be stored in the storage area pointed to by the address to be compulsorily set. Alternatively, the compulsory setting management unit 311 may notify the program execution unit 310 of the compulsory setting value acquired from the compulsory setting address information list 330.

When the controller 3 receives an instruction to cancel the forced setting from the support device 2 or the like, the forced setting management unit 311 deletes the information related to the address of the release instruction when the information related to the address of the release instruction is in the forced setting address storage unit 330. Alternatively, the fact that the cancellation instruction has been given may be added to the information.

When the controller 3 receives an instruction to cancel the forced setting from the support device 2 or the like, the forced setting management unit 311 sets the position of the code associated with the address in the release instruction to the forced setting position information list 235. Refer to and get. The forced setting management unit 311 instructs the program execution unit 310 to return the machine language object at the position to the NOP instruction, or returns the jump code at the position in the machine language object to the NOP instruction. Upon receiving an instruction from the forced setting management unit 311 to return the jump code to the NOP instruction, the program execution unit 310 returns the jump code to the NOP instruction.

As described above, variables and the like corresponding to the parameters related to the control of the control target device are stored in the storage area of each address of the first storage unit 32. By substituting the forced setting value for such a variable, it becomes possible to manually control the controlled device.

The second storage unit 33 stores the forced setting address information list 330, the forced setting position information list 235, and the like.

FIG. 2 illustrates a development environment provided to the user by the display device via the user interface 20 in the support device 2. The "project tree window" shown on the left side of the upper window in FIG. 2 shows the relationship between the programs in the project program list 230 stored in the storage unit 23. As shown here, it can be seen that the project, which is a set of programs, includes "LiveProject" as a library. It should be noted that the library is a collection of programs that have been made into parts, and here, it is assumed that the inside is hidden from the user. In addition, the project includes UFB2, LADDER, and the like as programs that are not included in the library.

The part from the center to the right side of the window shown above in FIG. 2 (the right side of the project tree window) is the editor part. By using this editor, the user can create an instance by assigning a value to a variable in the program. An instance (Lib1_1_1) is shown in the editor portion in FIG. The instance Lib1_1_1 is an instance of the program Lib1_1, and a value is assigned to the variable V000 of the program Lib1_1 and the value of V001 is output. Further, NewVar1 and 2 in the figure indicate terminals and correspond to the codes included in the program Lib1-1. The value of V000 is assigned to Lib1-1 via NewVar1, and the value of V001 is output from Lib1-1 via NewVar2.

With reference to the "project tree window" shown at the bottom of FIG. 2, it can be seen that the library "LibProject" includes the programs "Lib1_1" and "Lib1_2".
The development environment described with reference to FIG. 2 is generated by the project management unit 21.

FIG. 3 illustrates the call-related information 233. The call-related information 233 is hierarchically represented by associating the called program with the calling program when the front-end compiler 220 sequentially reads the input source code line. In the source code, the instance calls the instance. The front-end compiler 220 uses the instance program correspondence information 232 to generate the call-related information 233 in the generation of the call-related information 233. Here, an example of the instance program correspondence information is shown in FIG. With reference to FIG. 4, for example, it can be seen that each instance from "_siLAG2" to "_siLAG16" has data added to the program "_siLAG".

Returning to FIG. 3, the call-related information 233 shown at the upper part is a program name arranged line by line. In the call relationship information 233, the number shown on the left side represents the call hierarchy of the program whose name is shown on the right side. The program in FIG. 3 is shown in the project tree window of FIG. To specifically explain the call-related information 233 with reference to FIG. 3, first, an instance of the program "LADDER" is called by the front-end compiler 220 on the source code. The hierarchy of the instance of this "LADDER" is 1. Next, what is called by this "LADDER" instance is each instance of the program "Lib1-1" and the program "UFB2". Therefore, these layers are next to the layer 1 of the above-mentioned "LADDER" instance. Subsequently, the instance called from the instance of "Lib1_1" is an instance of the program "Lib1_2", and becomes 3 next to the layer 2 of the instance of the calling "Lib1_1".

As shown in FIG. 3, the front-end compiler includes the name of the program that is the source of the instance in the call relationship information 233 instead of the name of the instance together with the hierarchy of the instance. At this time, the above-mentioned instance program correspondence information 232 is referred to. From the call relationship information 233 of FIG. 3, it can be seen that the calling instance is in the hierarchy of the number obtained by subtracting 1 from the hierarchy of the called instance. Also, the name of the original program of the calling instance is placed before (upper line) the name of the original program of the called instance. Then, the line containing the name of the original program of the calling instance is placed closest to the line containing the name of the original program of the called instance compared to other lines containing the same name. NS. Therefore, the caller of "Lib1_1" in layer 3 becomes an instance of "UFB2" in layer 2. Further, the caller of the instance of "Lib1_2" in the layer 4 is the instance of "Lib1_1" in the layer 3.

The front-end compiler 220 may generate call-relationship information 233 that represents the call-relationship of the original program of the instance in a tree instead of the call-relationship information 233 that uses the number of layers. Call-related information 233 using this tree is shown at the bottom of FIG. From this figure, it can be seen that the instance of "LADDER" calls each instance of "Lib1_1" and "UFB2", and the instance of "Lib1_1" called by the instance of "LADDER" calls the instance of "Lib1_2". .. It can also be seen that the instance of "UFB2" called by the instance of "LADDER" calls the instance of "Lib1_1", and the called instance of "Lib1_1" calls the instance of "Lib1_2".

The call-related information 233 is generated by the front-end compiler 220 prior to the generation of the compulsory setting availability information list 234 described in detail below. The front-end compiler 220 uses the generated call-related information 233 to generate a forced setting availability information list 234. Since the method of generating the call-related information 233 is known, the description thereof will be omitted.

The compulsory setting possibility information list 234 will be described with reference to FIG. FIG. 5 illustrates a list of forced setting processing information 234. The forced setting availability information list 234 is for preventing the controller 3 from performing forced setting for a program included in the library (also referred to as the first program) that is not directly called from a program not included in the library. It is information, and it is possible to force settings for programs that are not included in the library or programs that are called directly from programs that are not included in the library (these programs are also referred to as the second program). Information to do.

The compulsory setting possibility information list 234 is generated by the front-end compiler 220, and the back-end compiler 221 generates a machine language based on the compulsory setting possibility information list 234. Even if the program is included in the library, for a program that is called directly from a program that is not included in the library, the user may store the forced setting value in the variable in the program. The setting is possible.

The compulsory setting availability information list 234 exemplified in FIG. 5 is generated by reading the call-related information 233 shown in the upper part of FIG. 3 by the front-end compiler 220. The compulsory setting availability information list 234 shown at the upper part of FIG. 5 is in the initial state. Further, the compulsory setting possibility information list 234 shown at the lower part of FIG. 5 is generated by reading up to "2 UFB2" which is the fourth line in the call relation information 233 at the upper part of FIG. 3 by the front-end compiler 220.

The "management number" is a serial number assigned to the program that is the source of the instances that the front-end compiler 220 sequentially reads from the call-related information 233. Further, "whether or not compulsory setting is possible" indicates whether or not the program can be subject to compulsory setting, and "no" is registered in the case of the first program and "possible" is registered in the case of the second program. .. In the compulsory setting possibility information list 234 in the initial state, the initial value NULL is registered in each column in which the program name and the compulsory setting propriety are registered.

From FIG. 3, the front-end compiler 220 first reads the program name "LADDER" (control number: 1). Since this program "LADDER" is not included in the library with reference to FIG. 2, the front-end compiler 220 determines that forced setting is possible. The determination process will be described in detail later.

Similarly, the front-end compiler 220 then reads the program name "Lib1-1" from the call-related information 233 (FIG. 3) (control number: 2). This program "Lib1-1" is included in the library with reference to FIG. 2, but is directly called by the program "LADDER" not included in the library. Therefore, the front-end compiler 220 determines that the forced setting process can be performed on the program "Lib1-1".

In the call-related information 233 shown at the upper part of FIG. 3, there is another line in a later line that includes "Lib1-1" of the same program name. And in the different lines, even if the program name is the same, the caller, hierarchy, etc. of the instance may be different. As a result, in the call relationship information 233, even if a certain program is the second program in the previous line, it may become the first program in the later line. Then, in this case, once the front-end compiler 220 enables forcible setting for the program on the previous line in the call relationship information 233, this is on that line for the program with the same name on the line after that line. Even if it is the first program, the compulsory setting remains possible on the compulsory setting possibility information 234 for that program. This makes it possible for the machine language object generated by the backend compiler 221 from such a program to include a jump code to the forced setting process. The same is true for other programs included in the library. Details will be described later.

Similarly, the front-end compiler 220 reads the program name "Lib1_2" next (control number: 3) in the call-related information 233 (FIG. 3). From FIG. 2, it can be seen that the program "Lib1-2" is included in the library, and from the call-related information 233 (FIG. 3), it can be seen that the program is not directly called from a program not included in the library. As a result, the program "Lib1_2" is the first program, and the front-end compiler 220 does not perform compulsory setting processing on this program "Lib1-2". In the call-related information 233, when the line containing the program name "Lib1-2" is also in a line after this, and the program "Lib1-2" in that line is directly called from a program not included in the library. Is updated to "Yes" in the forced setting processing information 232, so that the machine language object corresponding to the program "Lib1-2" can include a jump code to the forced setting processing. become.

FIG. 6 illustrates a flow of forced setting processing information generation processing by the front-end compiler 220.

First, the front-end compiler 220 reads the first line of the call-related information 233 and sets 1 in the “processed line” (step S100). When the front-end compiler 220 acquires the program name and the hierarchical information (also described as the hierarchical information) of the instance of the program (step S101: Yes), the program name is already registered in the compulsory setting availability information list 234. It is searched for whether or not it has been performed (step S102). When the program name is not registered (step S103: No), the front-end compiler 220 registers this program name in the compulsory setting availability information list 234 and also registers "No" as the compulsory setting availability for this program. (Step S104).

Subsequently, the front-end compiler 220 executes a search process for the program name read in step S100 (or step S111) in the library in the project program list 230 (step S105).

In step S103, if the program name read in step S100 (or step S111) is already registered in the compulsory setting availability information list 234 (step S103: Yes), the front-end compiler 220 is set in step S104. The process of step S105 is executed without performing the process.

In step S105, when the program read in step S100 (or step S111) does not exist in the library (step S106: No), the front-end compiler 220 can forcibly set the program in the compulsory setting availability information list 234. As a result, "possible" is registered in "possible or not forcible setting" (step S107). By this process, the front-end compiler 220 can extract a program whose name is sequentially read out in the call-related information 233 and which is not in the library, and can make a compulsory setting for the program.

In step S105, if the program read in step S100 (or step S111) is in the library (step S106: Yes), the front-end compiler 220 acquires the name of the program that called the program (step S108). ). The process of step S108 will be described in more detail later.

The front-end compiler 220 searches the library for the program name acquired in step S108 (step S109).

When the program name acquired in step S108 is not in the library (step S110: No), the front-end compiler 220 considers that the program whose name is searched in step S105 can be forcibly set, and "whether or not forcible setting is possible". Is registered in "OK" (step S107). By this process, the front-end compiler 220 can extract a program that is directly called from a program that is not included in the library from the programs whose names are sequentially read out in the call-related information 233, and can make a compulsory setting for the program.

The front-end compiler 220 adds 1 to the "processed line", reads the next line in the call relationship information 233 (step S111), and describes the program in this line from step S101 to step S107 (Yes in step S106). In the case, the process of steps S108 to S110 is included) is repeated.

The program determined as the second program by each process in step S106 and step S110 is registered in the compulsory setting possibility information list 234 as a program that can be compulsorily set in step S107. Then, once the program is registered as a program that can be forcibly set, even if the same name is subsequently read from the call-related information 233, "No" is registered in "Forcible setting" in the "Forced setting availability information list 234". Not done. Similarly, even if the program name is read from a certain line of the call-related information 233 and "No" is registered in "Forcible setting" in the Forced setting availability information list 234, the call-related information 233 is registered. The same program name is called from the line after, and it is determined as the second program, and forced setting may be possible.

FIG. 7 illustrates a flow of processing in step S108. First, the front-end compiler 220 sets the processing target line-1 in the "caller search line" (step S400). If the caller search line is 0 (step S401: Yes), the front-end compiler 220 returns without the caller's program name (step S402), and proceeds to the process of step S109 described above. In this case, the determination result of step S110 following step S109 is No.

If the caller search line is not 0 in step S401 (step S401: No), the front-end compiler 220 acquires the hierarchical information of the program of the caller search line in the call relationship information 233 (step S403). When the hierarchy in the hierarchy information acquired in step S403 is the number obtained by subtracting 1 from the hierarchy of the program in the processing target line (step S404: Yes), the front-end compiler 220 uses the program in the caller search line as the caller. , Acquires the name of the calling program and returns (step S405). The front-end compiler 220 subsequently executes the above-described processing in step S109.

When the hierarchy in the hierarchical information acquired by the front-end compiler 220 in step S403 is not equal to the program hierarchy in the processing target line minus 1 (step S404: No), the front-end compiler 220 uses the caller search line. Subtracting 1 from is replaced with a new caller search line (step S406), the process returns to step S400, and the same process is repeated.

By the processing of the front-end compiler 220 shown in FIGS. ..

Here, the front-end compiler 220 creates call-relationship information 233 between programs with reference to the instance program correspondence information 232, and uses this to create compulsory setting availability information 234, but instead of this, the front-end compiler 220 The compiler 220 may generate call relationship information 233 related to the call relationship between instances, and may use this to generate forced setting processing information 234. In this case, in step S100, the front-end compiler 220 acquires the instance name instead of the program name, and the front-end compiler 220 follows step S101 and prior to step S102, instance program correspondence information 234. The program name is acquired from the instance name acquired in step S100 with reference to.

The back-end compiler 221 generates a machine language object based on the compulsory setting possibility information 234 generated by the front-end compiler 220.

FIG. 8 illustrates a processing flow by the back-end compiler 221. First, in step S500, the back-end compiler 221 executes a process for acquiring the name of the first program to be processed in the intermediate code. Here, when the program name cannot be acquired (step S501: No), the back-end compiler 221 outputs the machine language generated up to that point to, for example, the communication unit 24 (step S502). When the program name can be acquired (step S501: Yes), the back-end compiler 221 searches the acquired program name in the compulsory setting availability information list 234 and acquires the information related to the compulsory setting availability of the program (step S501: Yes). Step S503).

When the program can be forcibly set (step S504: Yes), the back-end compiler 221 generates a machine language of the program including a jump code related to the forcible setting process as appropriate (step S505).

In the forced setting possibility information list 234, when "No" is registered in the "Forced setting possibility" of the program (step S504: No), the backend compiler 221 does not include the jump code related to the forced setting process. , Generate the machine language of the program (step S506).

The back-end compiler 221 temporarily holds the machine language generated in step S505 or step S506 until it is output in step S502. This retention does not have to be temporary.

After step S505 or step S506, the back-end compiler 221 executes a process for acquiring the name of the next program to be processed in the intermediate code (step S507). If the back-end compiler 221 cannot acquire the name of the next program to be processed in step S507 (step S501: No), the back-end compiler 221 executes the process of step S502. At this time, the back-end compiler 221 outputs the temporarily held machine language to the communication unit 24 or the like.

On the other hand, when the back-end compiler 221 can acquire the name of the program to be processed (step S501: Yes), the back-end compiler 221 repeats the operations after step S503 described above for the program with the program name acquired in step S507.

FIG. 9 illustrates the machine language generated by the backend compiler 221. The machine language when there is no forced setting process is shown in the upper part of FIG. 9, and the machine language when there is a forced setting process is shown in the lower part of the figure. Both of these two machine languages are generated from the same intermediate code, but the machine language shown at the bottom of FIG. 9 includes a jump code to the forced setting process.

More specifically in FIG. 9, "LD", "ADD", and "ST" indicate a load instruction, an addition instruction, and a write (memory) instruction, respectively. In the present embodiment, the jump code of the forced setting process is added to the write command. As described above, the first storage unit 32 has a storage area for storing the variables of each controlled device, but when an abnormality occurs in the plant system or the like, the controller 3 jumps to the forced setting process in the write command. This is because the presence of the code makes it possible to write the forced setting value to the storage area of the address corresponding to the controlled device, thereby preventing the writing of an invalid value to the storage area. However, the present invention is not limited to this, and a jump code to the forced setting process may be included in an instruction other than the write instruction in the machine language.

The code related to the forced setting process in FIG. 9 is the code of the portion surrounded by the broken line square. Of these, "LDR pc, [wk1, # 64]" is a jump code to the forced setting process. Further, "MOV lr, pc" is a code for returning from the jump destination.

Note that the machine language of the program in which the "possibility of forced setting" is "no" in the forced setting possibility information list 234 does not include the code related to the forced setting process.

By executing the machine language object acquired from the support device 2, the project execution unit 310 of the controller 3 executes the forced setting process when the forced setting process is required, and does not perform unnecessary processing when the forced setting process is not required.

FIG. 10 illustrates the hardware configuration of the support device 2. Here, the support device 2 has hardware as a general computer, and the processing by the support device 2 is executed by specifically using the hardware 5 shown below. The hardware 5 includes a processor 51, a memory 52, a storage device 53, a communication interface circuit 54, and a user interface circuit 55, which are connected to each other by a bus 50.

The processor 51 is, for example, a single-core, dual-core, or multi-core processor.

The memory 52 is, for example, a ROM (Read Only Memory), a RAM (Random Access Memory), or a semiconductor memory.

The processor 51 executes various programs stored in the memory 52 by using the information stored in the memory 52 or the information read from the storage device 53 described later into the memory 52, thereby causing the project management unit 21 and the compiler 22 to execute various programs. Each function of is realized. Further, the memory 52 may realize some functions of the storage unit 23. For example, the memory 52 temporarily stores the call-related information 233 generated by the compiler 22, and the storage device 23 described below temporarily stores the project program list 230, the variable / address correspondence information 231 and the instance / program correspondence information 232. The setability information list 234 and the forced setting position information list 235 may be stored.

The storage device 53 is, for example, a hard disk drive, an optical disk device, or the like, and may be an external storage device or a portable storage medium. The storage device 53 realizes all or part of the functions of the storage unit 23.

The communication interface circuit 54 is an interface for enabling the support device 2 to communicate with the controller 3 and the like via a LAN (Local Area Network), the Internet, an intranet, and the like. The function of the communication unit 24 is realized by the communication interface circuit 54.

The user interface circuit 55 is a circuit for connecting an input device such as a keyboard or a touch panel, or a display device such as a liquid crystal display, to the support device 2. The function of the user interface 20 is realized by the user interface circuit 55.

In addition to the above cases, all or a part of the functions of the functional blocks of the support device 2 can be appropriately realized by dedicated hardware.

FIG. 11 illustrates the hardware configuration of the controller 3. Here, the controller 3 has hardware as a general computer, and the processing by the controller 3 is executed by specifically using the hardware 6 shown below. The hardware 6 includes a processor 61, a first memory 62, a second memory 63, a storage device 64, and a communication interface circuit 65, which are connected to each other by a bus 60.

The processor 61 is, for example, a single-core, dual-core, or multi-core processor.

The first memory 62 and the second memory 63 are, for example, a ROM (Read Only Memory), a RAM (Random Access Memory), and a semiconductor memory.

The processor 61 executes various programs stored in the first memory 62 by using the information stored in the first memory 62 or the information read from the storage device 64 described later into the first memory 62. The function of the execution management unit 31 is realized. Further, a part of the functions of the second storage unit 33 may be realized by the first memory 62. For example, the first memory 62 may store the compulsory setting address information list 330 and the like.

The second memory 63 is a memory in which all or a part of the storage area is associated with the control target device, and is a memory to be processed by the program execution management unit 31. The function of the first storage unit 32 is realized by the second memory 63. The function of the first storage unit 32 may be realized by a storage device such as a hard disk drive instead of or in combination with the second memory 63.

The storage device 64 is, for example, a hard disk drive, an optical disk device, or the like, and may be an external storage device or a portable storage medium. The storage device 64 realizes the function of the second storage unit 33.

The communication interface circuit 65 is an interface for allowing the controller 3 to communicate with the support device 2 or the like via a LAN (Local Area Network), the Internet, an intranet, or the like. The function of the communication unit 30 is realized by the communication interface circuit 65.

In addition to the above cases, all or a part of the functions of the functional blocks of the controller 3 can be appropriately realized by dedicated hardware.

According to the control system 1 according to the present embodiment, the support device 2 generates a machine language that does not include the code related to the forced setting process for the componentized program that the operator does not target for the forced setting. Further, the controller 3 does not perform the forced setting process for the variable that does not require the forced setting process based on the machine language. As a result, the time spent for executing the code by the controller 3 can be reduced, and the control process of the controlled device in the plant becomes faster.

(Second Embodiment)
In the plant system, if necessary, a plurality of operators use a compulsory setting function such as generation of compulsory setting instruction information via a monitoring device assigned to each operator. However, in each monitoring device, although there is history information at the time of compulsory setting, it is not possible to comprehensively manage the information of the variables that are the target of compulsory setting in the entire plant system. In other words, at some point, the operator could not recognize which value was forcibly set for which variable. The control system 1'according to the present embodiment is for solving such a problem.

FIG. 12 illustrates the configuration of the control system 1'according to the present embodiment. The control system 1'according to the present embodiment includes one or more monitoring devices (HCI device, HCI: Human Computer Interaction) 7, a controller 3', and the support device 2 described above. In FIG. 12, one monitoring device 7, one controller 3', and one support device 2 in the control system 1'are shown.

The monitoring device 7 includes a user interface 70, a storage unit 71, a processing unit 72, a communication unit 73, and the like. The processing unit 72 is connected to the user interface 70, the storage unit 72, and the communication unit 73. Note that there may be a connection relationship other than this.

The controller 3'includes a compulsory setting management unit 311'in place of the compulsory setting management unit 311 included in the controller 3 in the above embodiment, and includes a program execution management unit 31'instead of the program execution management unit 31. Further, the controller 3'provides a second storage unit 33'instead of the second storage unit 33 in the above embodiment. Then, the second storage unit 33'stores the forced setting address information 330'instead of the forced setting address information list 330 in the above embodiment.

The user interface 70 of the monitoring device 7 connects an output device such as a display device or an input device such as a touch panel to the monitoring device 7. The operator who has confirmed the state of the controlled device displayed on the display device or the like inputs a forced setting instruction to the monitoring device 7 via the input device as necessary.

The storage unit 71 has its own identification information 710 uniquely assigned to the monitoring device 7, TAG information 711 related to one or more TAGs to be monitored by the monitoring device 7, forced setting support information list 712, and the support device. The variable / address correspondence information 231 and the like acquired from 2 via the communication unit 73 are stored.

Here, the TAG means a parameter related to the control of the control target device, and is associated with the above variable. The TAG information 711 includes a TAG number (also referred to as TAGNo) equivalent to or corresponding to the variable name in the code of each TAG, and the TAG name are related to each other. Here, taking a valve as an example, the TAG corresponds to a variable indicating the degree of opening / closing of the valve, and the name of the TAG is "the degree of opening / closing of the valve" or the like.

The compulsory setting support information list 712 is generated based on the compulsory setting support information received from the controller 3', and is for the operator to support the compulsory setting.

The processing unit 72 reads necessary information from the storage unit 71 based on the forced setting instruction input via the user interface 70, and generates forced setting instruction information for transmission to the controller 3'.

Further, when the processing unit 72 acquires the forced setting support information described later from the controller 3'via the communication unit 73, the processing unit 72 stores this in the forced setting support information list 712 of the storage unit 72, or the forced setting support information list. 712 is updated as appropriate. At the time of this accumulation, the treatment unit 72 may convert the forced setting support information for display on the display device via the user interface 70. Further, the processing unit 72 may use the display instruction of the compulsory setting support information list 712 from the operator as a trigger to perform processing for processing the information and output it to the display device via the user interface 70.

The compulsory setting support information list 712 may store all the compulsory setting support information from the beginning of the operation of the monitoring device 7 to the present, or may store the compulsory setting support information for a certain period of time.

The communication unit 73 is a functional block for the monitoring device 7 to exchange information with the controller 3'and the support device 2. The communication unit 73 transmits the forced setting instruction information to the controller 3'according to the instruction of the processing unit 72, receives the forced setting support information from the controller 3', and outputs this to the processing unit 72.

The compulsory setting management unit 311'of the controller 3'acquires compulsory setting instruction information from the monitoring device 7 via the communication unit 30. Then, when the address in the forced setting instruction information is not registered in the forced setting address information list 330', the forced setting management unit 311'registers the information included in the forced setting instruction information. On the other hand, when the address in the forced setting instruction information is already registered in the forced setting address information list 330', the forced setting management unit 311 forcibly sets the record in the forced setting address information list 330' related to the address. It may be updated based on the instruction information, and the communication unit 30 is not updated for the record for which the forced setting has not been released for the variable at the address, that is, the record for the variable currently being forcibly set. A notification to the effect that the compulsory setting cannot be performed may be sent to the source of the compulsory setting instruction information. In the controller 3', a priority may be provided for each of the support device 2 and the monitoring device 7 of 1 or more, which are the transmission sources of the forced installation instruction information. In this case, the compulsory setting management unit 311'based on the compulsory setting value or the like already set by the monitoring device 7 or the like having a lower priority based on the compulsory setting instruction information acquired from the monitoring device 7 or the like having a higher priority. It may be overwritten, and the forced setting value or the like already set by the monitoring device 7 or the like having a higher priority is not overwritten according to the forced setting instruction information from the monitoring device 7 or the like having a lower priority. May be good.

The compulsory setting management unit 311'generates compulsory setting support information using the compulsory setting address information list 330', triggered by the monitoring device 7 requesting the transmission of the compulsory setting support information or the activation of the monitoring device 7. Then, the information is transmitted to the monitoring device 7 via the communication unit 30. The forced setting support information includes all or a part of the contents of the forced setting address information list 330'necessary for the forced setting process of the operator using the monitoring device 7.

The compulsory setting management unit 311'reads the value set for each address related to the compulsory setting of the compulsory setting address information list 330' from the first storage unit 32 when generating the compulsory setting support information, or The parameter value of the controlled device corresponding to each address related to the forced setting of the forced setting address information list 330'is read from the controlled device, etc., and the forced setting address information list 330'is set as the source value of the controlled device. Add it and include it in the compulsory setting support information.

Further, the compulsory setting management unit 311'associates the time when the compulsory setting is performed for each address in the compulsory setting address information 330' or the time when the compulsory setting instruction information for each address is received with the address to the second. It is stored in the storage unit 33 and used when generating the forced setting support information.

Further, the second storage unit 33 assigns a number (also referred to as a station No. and ST No.) for identifying the station including the controlled target device corresponding to the address of the compulsory setting address information list 330'corresponding to the address. You may attach and remember. In this case, the compulsory setting management unit 311'adds the station No. associated with each address in the compulsory setting address information list 330'to the compulsory setting support information. However, the monitoring device 7 may hold information related to the correspondence between the address (or variable) of the second storage unit 33 and the station No. When the monitoring device 7 displays the compulsory setting support information, the monitoring device 7 may hold the information. The station No. may be acquired from the address (or variable) in the compulsory setting support information.

The processing unit 72 of the monitoring device 7 that has acquired the forced setting support information registers it in the forced setting support information list 712, or updates the forced setting support information list 712.

FIG. 13 shows an example of an image displayed on the screen subjected to forced setting by the operator via the monitoring device 7. A screen used for forced setting or monitoring of such an operator is also described as a forced setting screen. The forced setting screen of FIG. 13 shows a white background and black characters, but the present invention is not limited to this, and for example, the background may be black and the characters may be displayed in white or the like.

In FIG. 13, "PID001.PV" is a TAG No of a certain TAG. Here, the TAG No. is shown for the TAG of "PID001.PV". In addition, the name of TAG is usually displayed in the column of "This_is_Tagname".

The “Source Value” shown in FIG. 13 means the source value of TAG. ^{Here, 100.0 kg / m 2} is shown as the source value of TAG with a TAG No of "PID001.PV". In the figure, kg / m ² is represented as “kg / m 2”. The unit is displayed when the TAG has a definition of the unit. Also, when the setting is analog, such a unit is displayed. That is, when the setting is, for example, only "ON" and "OFF", the unit is not displayed. "Force Value" means a compulsory setting value, and here, ^{it can be seen that 100.0 kg / m 2} is input or set as a compulsory setting value for the TAG of TAG No. "PID001.PV". ..

“FON” in FIG. 13 is displayed when the forced setting has already been made for the TAG, and is displayed in a color that stands out as compared with other characters. For example, when the background is black and other characters are displayed in white, "FON" is displayed in red, for example. Here, it can be seen that the TAG No. is forcibly set for the TAG of "PID001.PV". This "FON" is displayed for the TAG associated with the registered address in the compulsory setting address information list 330'in the controller 3'and the address for which the compulsory setting instruction has not been released. Will be done.

“USER” is information (also described as a user ID) that identifies an operator or the like who is using the forced setting screen, and here it can be seen that the user ID of the operator is “user001”. "Remark" means a remark such as a reason for performing compulsory setting, and the column immediately below corresponds to a remark column for inputting or displaying the remark. By touching or clicking the rectangular parallelepiped mark to the right of this remarks column, the operator can delete the contents described in the remarks column.

"Force" is a display for instructing the monitoring device 7 to forcibly set the value input by the operator in the "Force Value" field to the TAG, and by touching the "Force" part or the like, the TAG is displayed. The instruction is given. As a result, the processing unit 72 of the monitoring device 7 generates the compulsory setting instruction information in the present embodiment described later.

"UnForce" is a display for instructing a TAG for which a forced setting has been made to cancel the setting. By touching the "UnForce" part on the screen or the like, the monitoring device 7 gives an instruction to cancel the forced setting to the controller 3'.

"Cancel" is a display for canceling the input on the compulsory setting screen and discarding the input contents. Such a stop process is performed by the operator touching the "Cancel" part or the like.

FIG. 14 illustrates the compulsory setting instruction information generated by the monitoring device 7 according to the present embodiment. As shown in FIG. 14, the compulsory setting instruction information includes the variable to be the compulsory setting and the identification information 710 in addition to the address information and the compulsory setting value included in the compulsory setting instruction information of the first embodiment. Is done. In the compulsory setting instruction information in FIG. 15, the address to be forcibly set is "M, WI, 65552", the compulsory setting value set in the storage area pointed to by the address is "100", and the compulsory setting value is substituted. The variable is "V002", and the identification information 710 of the monitoring device 7 that is the instruction source of the forced setting is "XXX". Although not shown, the forced setting instruction information includes the user ID of the operator who performed the forced setting, the reason for the forced setting, and the like.

The compulsory setting instruction information is represented in a table format in FIG. 14, but is not limited to this, and each value such as an address, a compulsory setting value, a variable, and identification information 710 is related to each other, and these The compulsory setting instruction information is not limited to the tabular format as long as the monitoring device 7 and the controller 3'and the like can recognize what each value of is indicated.

FIG. 15 shows a display example of the compulsory setting support information list 712 in this embodiment. In FIG. 15, each of “ST101”, “ST20C”, and “ST11C” is a station No. of the station where the control target device that is the target of the forced setting is arranged. The station No. is represented here by STmnk (numbers, letters, etc. are entered in m, n, and k), but the station number is not limited to this.

"Force Time" is the date and time when the compulsory setting was made. Further, "Force User" is a user ID of the operator who performed the forced setting process. Further, "Place" is identification information (identification information 710) for identifying the monitoring device 7 for which the forced setting has been performed.

In the forced setting support information list 712 of FIG. 15, for example, referring to the first line, at 13:15:05 on September 1, 2015, the operator of the user ID "user001" was asked to "Sensor bad (sensor malfunction). ) ”, Using the monitoring device 7 of the identification information“ XOS3000-1 ”, the TAG of the TAG No.“ PID001.PV ”at the station of the station No.“ ST101 ”and the source value is“ 0.0 ”. It can be seen that the forced setting value "100.0" was forcibly set for the TAG.

FIG. 16 illustrates the compulsory setting address information list 330'in this embodiment. The compulsory setting address information list 330'shown here is generated by the compulsory setting management unit 311'when the controller 3'acquires only one compulsory setting instruction information shown in FIG. As shown in FIG. 16, in the row where the control number is 1, "M, WI, 65552" is in the address column, "V002" is in the variable column, and "XXX" is in the identification information (identification information 710) column. Is registered. The management number here is a number assigned by the forced setting management unit 330', and is different from the management number in the forced setting processing information list 232 attached by the front-end compiler 210 of the support device 2. Is. Although not shown in the compulsory setting address information list 330', the information in each line includes the user ID of the operator who performed the compulsory setting, the reason for the compulsory setting, the compulsory setting value, and the like. Hereinafter, the generation of the compulsory setting address information list 330'by the compulsory setting management unit 311' will be briefly described.

When the compulsory setting management unit 311'acquires the compulsory setting instruction information, it determines whether the address in the compulsory setting instruction information is included in the compulsory setting address information list 330'. If the address is not included in the compulsory setting address information list 330', the compulsory setting management unit 311'has not registered the address in the compulsory setting address information list 330', such as NULL being registered for the address. The address, variable, identification information 710, etc. in the received forced setting instruction information are recorded in the line having the smallest management number among the lines of. On the other hand, when the address in the received compulsory setting instruction information is included in the compulsory setting address information list 330', the compulsory setting management unit 311'is used as identification information (identification information 710) in the line in which the address is registered. Each of the compulsory setting values and the like is updated to the corresponding information included in the received compulsory setting instruction information.

As described above, when the forced setting management unit 311'receives an instruction to cancel the forced setting from the monitoring device 7, the forced setting management unit 311'deletes or records the corresponding address in the forced setting address information list 330'. Is added to the effect of cancellation.

The compulsory setting address information list 330'in FIG. 16 is represented in a table format, but is not limited to the table format as long as the addresses, variables, identification information 710, and the like are related to each other and stored.

FIG. 17 illustrates the hardware configuration of the monitoring device 7. Here, the monitoring device 7 has hardware as a general computer, and the processing by the monitoring device 7 is executed by specifically using the hardware 8 shown below. The hardware 8 includes a processor 81, a memory 82, a storage device 83, a communication interface circuit 84, and the like connected to each other by a bus 80.

The processor 81 is, for example, a single-core, dual-core, or multi-core processor.

The memory 82 is, for example, a ROM (Read Only Memory), a RAM (Random Access Memory), or a semiconductor memory.

The function of the processing unit 72 is realized by the processor 81 executing various programs stored in the memory 82 by using the information stored in the memory 82 or the information read from the storage device 83 described later into the memory 82. Will be done.

The storage device 83 is, for example, a hard disk drive, an optical disk device, or the like, and may be an external storage device or a portable storage medium. The storage device 83 realizes the function of the storage unit 71.

The communication interface circuit 84 is an interface for enabling the monitoring device 7 to communicate with the controller 3 and the like via a LAN (Local Area Network), the Internet, an intranet, and the like. The function of the communication unit 73 is realized by the communication interface circuit 84.

The user interface circuit 85 is a circuit for connecting an input device such as a keyboard or a touch panel, or a display device such as a liquid crystal display, to the monitoring device 7. The function of the user interface 70 is realized by the user interface circuit 85.

In addition to the above cases, all or a part of the functions of the functional blocks of the monitoring device 7 can be appropriately realized by dedicated hardware.

Since the hardware of the support device 2 and the controller 3 is the same as that of the above embodiment, the description thereof will be omitted.

According to the present embodiment, the operator can confirm from the monitoring device 7 how and which controlled device is forcibly controlled based on the instruction from which monitoring device, which is a useless forced setting. In addition, it is possible to eliminate forced settings that contradict each other and forced settings that are excessively added to the controlled device, and the operation of the controlled device in the plant becomes easier and safer.

The present invention allows for various embodiments and modifications without departing from the broad spirit and scope of the present invention. Moreover, the above-described embodiment is for explaining the present invention, and does not limit the scope of the present invention. Various modifications made within the scope of the claims and within the equivalent meaning of the invention are also considered to be within the scope of the present invention.

1, 1'control system, programmable controller system 2 support device, development support device 3, 3'controller, control device 5, 6, 8 hardware 7 monitoring device 20, 70 user interface 21 project management department 22 compiler 23, 71 storage Units 24, 30, 73 Communication unit 31, 31'Program execution management unit 32 First storage unit 33, 33'Second storage unit 50, 60, 80 Bus 51, 61, 81 Processor 52, 82 Memory 53, 64, 83 Storage device 54, 65, 84 Communication interface circuit 55, 85 User interface circuit 62 First memory 63 Second memory 72 Processing unit 220 Front-end compiler 221 Back-end compiler 230 Project program list 231 Variable / address correspondence information 232 Instance program support Information 233 Call-related information 234 Forced setting availability information list 235 Forced setting position information list 310 Program execution unit 311, 311'Forced setting management unit 330, 330' Forced setting address information list 710 Identification information 711 TAG information 712 Forced setting support information list

Claims (7)

A development support device that generates a machine language object from each of one or more programs in the input source code, and a control device that executes the machine language object acquired from the development support device.
With
The development support device is
Using the calling relationship between each of the one or more programs, the first program among the one or more programs that is included in the library and the calling program is also included in the library is not forcibly set. Generates compulsory setting availability information and
Based on the forced setting availability information, the first machine language object is generated from the first program, and the machine language object is generated.
The control device is
Based on the first machine language object, the first controlled device corresponding to the first variable in the first program is controlled without forcibly setting.
A control system that features that. The development support device is
From the above one or more programs, a second program in which the program not included in the library or the calling program is not included in the library is extracted.
Of the one or more programs, the program not extracted as the second program is defined as the first program.
The control system according to claim 1. The development support device is
For the second program, the compulsory setting enable / disable information that enables the compulsory setting is generated, and based on the compulsory setting enable / fail information, the second machine language object is generated.
The control device is
When a forced setting instruction is received for the second controlled device corresponding to the second variable in the second program, the second control is performed based on the forced setting instruction and the second machine language object. Control the target device,
The control system according to claim 2. The control system further
It is equipped with one or more monitoring devices that accept the input of the forced setting instruction.
The monitoring device to which the forced setting instruction is input is
Notifying the control device of the forced setting instruction,
The control device is
Based on the forced setting instruction and the second machine language object, the second controlled device is forcibly set.
The forced setting support information for the second control target device that is the target of the forced setting is generated, and the forced setting support information is notified to the one or more monitoring devices.
The one or more monitoring devices display the forced setting support information notified from the control device.
The control system according to claim 3. The forced setting support information includes the identification information of the monitoring device that has notified the control device of the forced setting instruction and the forced setting value of the second control target device that is the target of the forced setting. The control system according to claim 4. Using the calling relationship between each of the one or more programs in the input source code, for the first program among the one or more programs that is included in the library and the calling program is also included in the library. A front-end compiler that generates information on whether or not forced setting is possible, and a front-end compiler that does not perform forced setting.
A back-end compiler that generates a first machine language object from the first program based on the forced setting availability information, and
A communication unit that transmits the machine language object to a control device that controls the first controlled device corresponding to the first variable in the first program based on the first machine language object.
A development support device characterized by being equipped with. A development support device that generates a machine language object from each of one or more programs in the input source code, and a control device that executes the machine language object acquired from the development support device.
A method performed in a control system that comprises
The development support device
Using the calling relationship between each of the one or more programs, the first program among the one or more programs that is included in the library and the calling program is also included in the library is not forcibly set. Generates compulsory setting availability information and
Based on the forced setting availability information, the first machine language object is generated from the first program, and the machine language object is generated.
The control device
Based on the first machine language object, the first controlled device corresponding to the first variable in the first program is controlled without forcibly setting.
A control method characterized by that.

Images