Control program, control system, and control method for multiplexed system
The control program for multiplexed systems addresses the limitations of current development environments by enabling user-defined library functions to manage intermediate calculation values, facilitating advanced control functions and efficient data transfer, thus overcoming the challenges of data tracking and calculation cycle constraints.
Patent Information
- Application Number
- PCT/JP2024/003352
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2023-05-30
- Filing Date
- 2024-02-01
- Publication Date
- 2024-12-05
AI Technical Summary
Current development environments for multiplexed systems face challenges in handling advanced control functions like AI due to limitations in data tracking, calculation cycle time, and constraints on CPU processing and memory, making it difficult to implement complex control logic across multiple execution environments.
A control program and system that allows for the calling of user-defined library functions to manage intermediate calculation values across execution environments, using an interface area for data tracking, enabling advanced control functions without altering the basic configuration of the control logic, and allowing for efficient data transfer between active and standby sides.
Enables the realization of advanced control functions in multiplexed systems by optimizing data tracking and reducing communication time, preventing system unrecoverability and maintaining control cycle compliance.
Smart Images

Figure JP2024003352_05122024_PF_FP_ABST
Abstract
Description
Control program, control system, and control method for multiplexed system
[0001] This application claims priority to Japanese Patent Application No. 2023-088710, filed on May 30, 2023, with the Japan Patent Office, the contents of which are incorporated herein by reference.
[0002] For example, in a control system for controlling the constituent equipment of a power plant or the like (e.g., Patent Document 1), various controls are realized by installing control logic prepared for each device to be controlled and each function to be realized in an execution environment such as a controller.
[0003] Japanese Patent Application Laid-Open No. 2004-199658
[0004] In a control system that controls a plant facility consisting of numerous pieces of equipment, an equivalent execution environment is prepared in redundancy on the working side and the standby side, and if any abnormality occurs in the working execution environment, the execution environment on the working side and the standby side are switched back and forth, thereby improving the reliability of the system. In such a redundancy system, in order to prevent a sudden change in the control state when switching between the working and standby execution environments, so-called data tracking is required, in which the control state on the working side is handed over to the standby side.
[0005] Incidentally, a known method for constructing control logic for use in plant facilities is, for example, a method using a so-called MBD (Model Based Design) tool, which utilizes a development environment based on a control model. MBD tools are one of the de facto standard tools for describing control models, and known examples include MATLAB (registered trademark) and Simulink. These MBD tools also have a standard function or a plug-in function that allows for the automatic generation of source code corresponding to the created control model using a general-purpose programming language.
[0006] When constructing control logic for the aforementioned multiplexed system in a development environment using such an MBD tool, various data that are the subject of data tracking exchanged between multiplexed execution environments can be treated as global variables (including static variables) that apply across these execution environments. However, if all of the various data included in the control model created for each execution environment were subject to data tracking, the calculation process would take a long time, making it difficult to complete data tracking communication within the calculation cycle. For example, some of this data does not require data tracking because it is initialized and used each time calculation begins. Therefore, limiting the data to be subject to data tracking could shorten the time required for data tracking communication. However, automatically extracting such data to be subject to data tracking is difficult. For these reasons, development environments using MBD tools have been limited to the use of single-configuration SCADA (Supervisory Control and Data Acquisition), and have not yet been applied to more complex multiplexed systems.
[0007] On the other hand, in the current development environment for control logic for multiplexed systems, an area for storing intermediate calculation values is provided for each calculation element (POL: Problem-Oriented Language) included in the control logic, and the intermediate calculation values are data-tracked between the active side and the standby side. In this case, although the data size subject to data tracking varies depending on the amount of control logic, there is an upper limit to the amount of control logic, and therefore there is also an upper limit to the data size of data tracking.
[0008] Current development environments for control logic for multiplexed systems may offer a function for describing the processing details of arithmetic elements in a general-purpose programming language to accompany the control logic, but the number of lines of code that can be written is limited. This makes it impossible to describe advanced control function models such as AI. Furthermore, interpreted execution requires time, so processing may not be completed in time for the control cycle. (On the other hand, compiling and generating binaries in the execution environment is difficult due to limitations on CPU processing and calculation capabilities, memory, and storage capacity.) Therefore, current development environments for multiplexed systems are unable to handle advanced control functions such as AI.
[0009] At least one embodiment of the present disclosure has been made in consideration of the above-mentioned circumstances, and aims to provide a control program, a control system, and a control method for a multiplexed system that can realize advanced control functions in control logic targeted at the multiplexed system.
[0010] In order to solve the above problem, a control program for a multiplexing system according to at least one embodiment of the present disclosure is a control program for a multiplexing system including control logic for controlling a multiplexed first execution environment and a multiplexed second execution environment, and is capable of executing the following steps on a computer device: calling a user-defined library function from at least one calculation element constituting the control logic; and fetching an intermediate calculation value of the user-defined library function in the standby side of the first execution environment or the second execution environment from an interface area in which the intermediate calculation value of the user-defined library function in the active side of the first execution environment or the second execution environment is pre-stored.
[0011] In order to solve the above problem, a control device of a multiplexing system according to at least one embodiment of the present disclosure includes a calculation unit capable of executing a control program for the multiplexing system according to at least one embodiment of the present disclosure.
[0012] In order to solve the above-mentioned problems, a control method for a multiplexed system according to at least one embodiment of the present disclosure is a control method for a multiplexed system including control logic for controlling multiplexed first and second execution environments, and includes the steps of: calling a user-defined library function from at least one calculation element constituting the control logic; fetching an intermediate calculation value of the user-defined library function in the standby side of the first execution environment or the second execution environment from an interface area in which the intermediate calculation value of the user-defined library function in the active side of the first execution environment or the second execution environment is stored in advance; and writing the intermediate calculation value of the user-defined library function in the active side of the first execution environment or the second execution environment to the interface area.
[0013] According to at least one embodiment of the present disclosure, it is possible to provide a control program, a control system, and a control method for a multiplexed system that can realize advanced control functions in control logic for the multiplexed system.
[0014] 1 is a schematic diagram showing a development process of a control program according to one embodiment; FIG. 2 is a diagram showing an example of the control logic of FIG. 1; FIG. 3 is an example of a user-defined library function that can be called by the function of FIG. 2; FIG. 4 is a flowchart showing a control method implemented by the control logic CL of FIG. 2; FIG. 5 is a modified example of steps S22 and S23 of FIG. 3; FIG. 6 is a diagram showing an example of the relationship between the execution process of a controller and a user-defined library function; FIG. 7 is a schematic diagram showing a development process of control logic using an MBD tool; and FIG. 8 is a schematic diagram showing a development process according to another reference technology targeted at a multiplexed system.
[0015] Hereinafter, several embodiments of the present invention will be described with reference to the accompanying drawings. However, the configurations described as the embodiments or shown in the drawings are merely illustrative examples and are not intended to limit the scope of the present invention.
[0016] <Reference Technology> First, the reference technology on which the present invention is based will be described with reference to Figures 7A and 7B. Figure 7A is a schematic diagram showing the development process of control logic using an MBD tool. In Figure 7A, the development target is control logic to be installed in a single-configuration SCADA (Supervisory Control and Data Acquisition).
[0017] First, an MBD tool is used to construct a control model M including an advanced control model such as AI (step S30). With the MBD tool, an operator can construct the control model M by combining components such as functions and operators. Fig. 7A shows a simplified control model M constructed using the MBD tool, which includes a predictive control model MPC and a plant model MP.
[0018] Next, the source code automatic generation function of the MBD tool is utilized to automatically generate source code SC corresponding to the control model M constructed in step S30 (step S31). The MBD tool is equipped with a function, as a standard function or a plug-in function, for describing (converting) the source code SC corresponding to the control model into a general-purpose programming language such as C. In step S31, the source code SC corresponding to the control model M constructed in step S30 is generated using such a function of the MBD tool.
[0019] Next, the source code SC generated in step S31 is imported into a development environment (step S32), compiled to create a binary file BF (step S33), and installed in an execution environment E (step S34). The execution environment E is a standalone control device (controller) such as SCADA (Supervisory control and data acquisition).
[0020] The development process using the MBD tool described above with reference to FIG. 7A has the following issues. If a multiplexed system with redundancy between two execution environments is developed using an MBD tool, data tracking is required between control models constructed to correspond to the two execution environments. In source code automatically generated from such a control model with data tracking, data tracking can be treated as global variables (including static variables) common to the control models corresponding to each execution environment. However, if all of the various data contained in the control models corresponding to each execution environment were subject to data tracking, the calculation process would require a long time, potentially making it difficult to perform data tracking communication within the calculation cycle. This data includes, for example, data that is initialized and used each time a calculation starts and therefore does not require data tracking. Therefore, limiting the data subject to data tracking could potentially shorten the time required for data tracking communication. However, automatically extracting such data subject to data tracking is difficult. For these reasons, development processes using MBD tools have been limited to using a single-configuration SCADA as the execution environment E, making it difficult to apply to multiplexed systems.
[0021] Next, FIG. 7B is a schematic diagram showing a development process according to another reference technology targeting a multiplexed system. The reference technology shown in FIG. 7B targets two execution environments (first execution environment E1, second execution environment E2) that are multiplexed with each other, such as a programmable logic controller (PLC) or a distributed control system (DCS). In this type of multiplexed system, one of the two execution environments is active and the other is standby. If a malfunction occurs in the active execution environment, the active and standby execution environments are swapped. In particular, when the active and standby execution environments are swapped, the control state of the active side is inherited by the standby side (data tracking) to prevent a sudden change in the control state. Note that, unless otherwise specified, the following description will be based on the assumption that the first execution environment E1 is active and the second execution environment E2 is standby, but this is not limited to this.
[0022] First, an operator uses a design tool to draw a control logic CL (step S40). In step S40, the control logic CL is drawn by combining operational elements. Information regarding the combination of operational elements in the drawn control logic CL is generated as intermediate code CC (step S41). The intermediate code CC generated in step S41 is installed by being loaded into each of the execution environments to be multiplexed (first execution environment E1, second execution environment E2) (step S42). In FIG. 7B , the intermediate code CC is loaded into the first execution environment E1, which is the active side, and the second execution environment E2, which is the standby side. As a result, various data required for multiplexing is transmitted and received by data tracking between the first execution environment E1 and the second execution environment E2 into which the intermediate code CC has been loaded.
[0023] The development process for the multiplexed system described above with reference to FIG. 7B has the following problems. While this type of development process may include a function for describing the processing details of the arithmetic elements in a general-purpose programming language that accompanies the control logic CL, the number of lines of program that can be written is limited. Therefore, it is not possible to describe advanced control function models such as AI. Furthermore, because interpreted execution requires time, processing may not be completed in time for the control cycle. (On the other hand, compiling and generating binaries in an execution environment is difficult due to limitations on the CPU processing and arithmetic functions and memory and storage capacity.) Therefore, the current development environment for multiplexed systems cannot handle advanced control functions such as AI.
[0024] The problems with the development process according to the reference technology shown in FIGS. 7A and 7B can be preferably solved by the control programs according to the embodiments described below.
[0025] <Embodiments> Next, a control program according to several embodiments will be specifically described. Here, Fig. 1 is a schematic diagram showing a development process of a control program according to one embodiment.
[0026] First, an MBD tool is used to construct a control model M including an advanced control model such as AI (step S10). In the MBD tool, an operator combines components such as functions and operators to construct the control model M. Fig. 1 shows a simplified view of the control model M, which includes a predictive control model MPC and a plant model MP, constructed using the MBD tool.
[0027] Next, the source code automatic generation function of the MBD tool is utilized to automatically generate source code SC corresponding to the control model M constructed in step S10 (step S11). The MBD tool is equipped with a function, as a standard function or a plug-in function, for writing (converting) the source code SC corresponding to the control model into a general-purpose programming language such as C. In step S11, this function of the MBD tool is used to generate the source code SC corresponding to the control model M constructed in step S10. Next, the source code SC generated in step S11 is imported into a development environment (step S12) and compiled to create a binary file BF (step S13). The binary file BF created in step S13 is installed in each of the multiplexed first execution environment E1 and second execution environment E2 (step S14).
[0028] Meanwhile, the design tool generates control logic CL by drawing (step S15). Then, intermediate code CC for the control logic CL generated in step S15 is generated (step S16). This intermediate code CC is loaded into the first execution environment E1 and the second execution environment E2 (step S17), thereby realizing data tracking between the first execution environment E1 and the second execution environment E2 (step S18).
[0029] 2 is a diagram showing an example of the control logic CL of FIG. 1, and FIG. 3 is an example of a user-defined library function cfunc1 that can be called by the function CFN1 of FIG.
[0030] 2 shows a configuration centered around function CFN1 as an example of control logic CL. Function CFN1 is constructed so that execution condition X1, input data X2, and input parameter X3 are input, and output data Y1 and execution result Y2 are output from function CFN1. The control logic CL also includes an interface area IA in which data to be tracked (data tracking target data) among various data handled by function CFN1 is stored, and an intermediate calculation value acquisition unit AP for acquiring intermediate calculation values from the interface area IA.
[0031] The interface area IA can store analog data, digital data, and integer data handled by the function CFN1 according to their respective data types. The intermediate calculation value acquisition unit AP can acquire the data stored in the interface area IA. Specifically, in the first execution environment E1, which is the active side, the intermediate calculation values (the latest intermediate calculation values) obtained in the calculation processing of the function CFN1 are stored by being written to the interface area IA as appropriate. Meanwhile, in the second execution environment E2, which is the standby side, the intermediate calculation values stored in the interface area IA can be imported, thereby reproducing a control state corresponding to the first execution environment E1, which is the active side.
[0032] 2, a function CFN1 associated with the control logic CL is written in a general-purpose programming language. In this example, the function CFN1 is defined using a variable X1, which is Din indicating a digital input type; variables X2 and X3, which are Ain indicating an analog input type; variables Y1, which is Aout indicating an analog output type; and variables Y2, which is Dout indicating a digital output type. Specifically, when the execution condition X1 == 1 is satisfied, Y2 = cfunc1(X2, X3, &Y1) is executed. The function cfunc1 is a user-defined library function having variables X2 and X3 as arguments and Y1 as a return value, and is called from the function CFN1, which is an arithmetic element (POL) of the control logic CL. In this manner, in this embodiment, the user-defined library function cfunc1 is configured to be called from the function CFN1, which is an arithmetic element constituting the control logic CL. The arguments of the user-defined library function cfunc1 called by the function CFN1 are merely an example, and the order and number of arguments can be defined appropriately by the user.
[0033] 3 shows an example of the specific content of the user-defined library function cfunc1 in FIG. 2. The user-defined library function cfunc1 defines a variable inp1 as the first input (input 1), a variable prm1 as the second input (parameter 1), and a variable out1 as the third input (output 1). The function includes a portion (step S51) that calls a subfunction cfunc1_main (step S53), which defines the variables inp and prm as arguments and the variable out as an argument indicating the storage location (address) of the execution result, by specifying inp1 as the first argument, prm1 as the second argument, and &out1 as the third argument. The return value of the subfunction cfunc1_main is stored in the variable ret (step S51, Y2 in FIG. 2). Note that int indicates a signed integer type, float indicates a single-precision floating-point type, and double indicates a double-precision floating-point type.
[0034] In the user-defined library function cfunc1, the subfunction cfunc1_main is executed, and the execution result is stored in the variable out1 (Y1 in FIG. 2). Meanwhile, the calculation intermediate value (the intermediate calculation value cfa[0] of the user-defined library function cfunc1) is stored in the global variable gval and written to the interface area IA, which stores data to be tracked (step S52). The intermediate calculation value cfa[0] written to the interface area IA is acquired by the intermediate value acquisition unit AP in FIG. 2 in the second execution environment E2 on the standby side, and thereby data is tracked. This makes it possible to reproduce the control state of the first execution environment E1 on the active side in the second execution environment E2 on the standby side.
[0035] 4 is a flowchart showing the control method executed by the control logic CL of FIG. 2. In this control method, it is first determined whether the execution environment to be controlled (first execution environment E1 or second execution environment E2) is on standby (step S20). If the execution environment is on standby (step S20: YES), any data tracking reception data is fetched from the data tracking reception buffer into the interface area IA (step S21). After that, or if the execution environment is not on standby (step S20: NO), the calculation elements of the control logic CL begin execution (step S22).
[0036] When the control logic CL is executed, it is determined whether execution of all the arithmetic elements included in the control logic CL has been completed (step S23). If execution of all the arithmetic elements has not been completed (step S23: NO), the process branches as follows depending on the type of the arithmetic element being executed (step S24). If the arithmetic element being executed is an input element in the interface area IA, a read process from the interface area IA is performed (step S25a). If the arithmetic element being executed is an output element in the interface area IA, a write process to the interface area IA is performed (step S25b). If the arithmetic element being executed is a call element of the user-defined library function cfunc1, a call process for the user-defined library function cfunc1 is performed (step S25c). If the arithmetic element being executed is another element, normal element arithmetic processing is performed (step S25d). When the processing corresponding to each type of arithmetic element has been executed for all elements (step S23: YES), the execution of the arithmetic elements of the control logic CL ends (step S26).
[0037] Next, it is determined whether the execution environment is the active side (step S27). If it is the active side (step S27: YES), and if it is the data tracking transmission period, data is written from the interface area IA to the data tracking reception buffer (step S28). After that, or if it is not the active side (step S27: NO), the series of control methods ends.
[0038] When the control logic CL is executed in this manner, the user-defined library function cfunc1 is called during the execution process. For example, when the second execution environment E2 is the standby environment, the second execution environment E2 acquires the intermediate calculation value of the user-defined library function cfunc1 by fetching it from the interface area IA. Strictly speaking, the first execution environment E1, which is the active environment, also fetches the intermediate calculation value from the interface area IA, but the intermediate calculation value fetched by the active execution environment E1 is the previous value of its own calculation. This intermediate calculation value is the most recent previous value in the active execution environment E1, which is stored in the interface area IA in advance. This allows the standby execution environment E2 to reproduce the control state of the active execution environment E1. Next, the active execution environment E1 writes the intermediate calculation value of the user-defined library function cfunc1 to the interface area IA. Strictly speaking, the second execution environment E2, which is the standby side, also writes intermediate calculation values to the interface area IA, but these are overwritten by data tracking from the first execution environment E1, which is the active side. At this time, the intermediate calculation values in the first execution environment E1, which is the active side, are stored in the interface area IA, and can be obtained as intermediate calculation values on the standby side from the next time onwards. Note that there are no limitations on the method of transferring tracking data from the active execution environment to the standby execution environment.
[0039] In this way, the control logic CL is configured so that the user-defined library function cfunc1 can be called from at least some of the calculation elements (e.g., POL). This allows for the implementation of advanced control and calculation functions by modifying the user-defined library function cfunc1 included in the control logic CL without modifying the overall basic configuration of the control logic, such as the embedded software of a PLC / DCS. The user-defined library function cfunc1 pre-stores intermediate calculation values in the first execution environment E1 (the active side of the multiplexed system) in the interface area IA, and the second execution environment E2 (the standby side) retrieves these values from the interface area IA, thereby achieving multiplexed control with data tracking that can be achieved by the advanced control and calculation function. Meanwhile, intermediate calculation values of the user-defined library function cfunc1 in the first execution environment E1 (the active side) are written to the interface area IA. The intermediate calculation values of the user-defined library function cfunc1 written in this manner to the interface area IA are imported into the user-defined library function cfunc1 in the second execution environment E2 on the standby side, thereby realizing data tracking between the two execution environments.
[0040] Furthermore, the global variables that are the targets of data tracking are logically defined in the user-defined library function cfunc1. This allows the data included in the control logic CL to be clearly narrowed down to the data that is the target of data tracking, thereby suppressing an increase in tracking data communication. As a result, it is possible to effectively prevent a situation in which the redundant configuration becomes unable to be restored due to data tracking communication not being completed within the specified time when starting the standby execution environment E2.
[0041] 5 shows a modified example of steps S22 and S23 in FIG. 3. In this modified example, it is possible to specify variables to be subject to data tracking in the user-defined library function cfunc1. In FIG. 5, the variable gval is specified as the subject of data tracking. The variable gval, which is an intermediate calculation value of the control logic CL in the first execution environment E1 on the active side, is written to the interface area IA, and the variable gval stored in the interface area IA can be imported into the second execution environment E2 on the standby side.
[0042] In this way, the specification of whether or not each piece of data exchanged between the control logic CL and the user-defined library function cfunc1 is to be subject to data tracking is not written by describing the operation elements (POL) as input elements of the logic, but is automatically assigned within the user-defined library function cfunc1 written in a general-purpose programming language. This makes it possible to effectively avoid the operator forgetting to write logic for specifying data as subject to data tracking, compared to when the operator specifies the data to be subject to data tracking.
[0043] 6, a linker option may be used to limit the scope of variable symbols from the operation object of the control logic CL to the object of the user-defined library function cfunc1 so that only the operation element (POL) in the interface area IA between them is permitted to read and write. An example of a linker option that can specify disclosure in such a shared library is the LD version script of the open source gcc compiler. On the other hand, the scope of function symbols may be limited from the user-defined library function cfunc1 to the object of the user-defined library function so that only the user-defined library function cfunc1 is permitted to be called.
[0044] This makes it possible to effectively avoid the introduction of software bugs due to compilation errors or interference from unrelated variables caused by accidental duplication with variable symbols or function symbols of existing embedded software in the PLC / DCS when creating user-defined scripts by automatically generating source code written in the general-purpose programming language C from advanced control models such as model predictive control or AI written in MBD tools such as MATLAB or Simulink.
[0045] As described above, according to the above embodiments, it is possible to provide a control program, a control system, and a control method for a multiplexed system that can realize advanced control functions in control logic for the multiplexed system.
[0046] In addition, within the scope of the present disclosure, the components in the above-described embodiments may be replaced with well-known components as appropriate, and the above-described embodiments may be combined as appropriate.
[0047] The contents described in each of the above embodiments can be understood, for example, as follows.
[0048] (1) A control program for a multiplexing system according to one embodiment is a control program for a multiplexing system including control logic for controlling a multiplexed first execution environment and a multiplexed second execution environment, and is capable of executing the following steps on a computer device: calling a user-defined library function from at least one calculation element constituting the control logic; and fetching an intermediate calculation value of the user-defined library function in the standby side of the first execution environment or the second execution environment from an interface area in which the intermediate calculation value of the user-defined library function in the active side of the first execution environment or the second execution environment is pre-stored.
[0049] According to the above aspect (1), the control logic is configured so that user-defined library functions can be called from at least some of the calculation elements (e.g., POLs). This allows for the implementation of advanced control and calculation functions by modifying the user-defined library functions included in the control logic, without modifying the overall basic configuration of the control logic, such as the embedded software of a PLC / DCS. The user-defined library functions store intermediate calculation values in an interface area in advance in the execution environment of the active side of the multiplexed system, and then retrieve the values from the interface area in the execution environment of the standby side, thereby achieving multiplexed control with data tracking that can be achieved by the advanced control and calculation functions.
[0050] (2) In another aspect, in the aspect (1) above, the method further comprises a step of writing intermediate calculation values of the user-defined library function in at least the operating side of the first execution environment or the second execution environment to the interface area.
[0051] According to the above aspect (2), at least intermediate calculation values of the user-defined library function in the active execution environment are written to the interface area. The intermediate calculation values of the user-defined library function written to the interface area are then imported into the user-defined library function in the standby execution environment, thereby realizing data tracking between the two execution environments.
[0052] (3) In another aspect, in the aspect (1) or (2), the intermediate calculation value is data to be tracked between the first execution environment and the second execution environment.
[0053] According to the above aspect (3), by setting intermediate calculation values of user-defined library functions as data tracking target data, it is possible to clearly narrow down which of various global variables in the control logic are to be data tracking targets. This prevents the amount of data tracking target data from increasing more than necessary. As a result, when starting up the standby execution environment of a multiplexed system, it is possible to effectively prevent the multiplexed configuration from becoming unable to recover due to data tracking communication not being completed within a specified time. Note that there are no limitations on the method of transferring tracking data from the active execution environment to the standby execution environment.
[0054] (4) In another aspect, in the aspect (3), the user-defined library function identifies the data to be tracked from among a plurality of global variables included in the user-defined library function.
[0055] According to the above aspect (4), the data to be tracked is specified in the user-defined library function. This allows the data to be automatically allocated by the program, rather than being specified as an arithmetic element (e.g., POL), which is a basic configuration of the control logic.
[0056] (5) In another aspect, in any one of the above (1) to (4), the user-defined library functions are written in a general-purpose programming language.
[0057] According to the above aspect (5), the user-defined library functions called by the arithmetic elements that make up the control logic can be suitably written using a general-purpose programming language.
[0058] (6) A control device for a multiplexing system according to one aspect includes a calculation unit capable of executing the control program according to any one of the above aspects (1) to (5).
[0059] According to the above aspect (6), by executing the above control program by the calculation unit, it is possible to realize a control device capable of multiplexed control accompanied by data tracking that can be realized by an advanced control calculation function.
[0060] (7) A control method for a multiplexed system according to one embodiment is a control method for a multiplexed system including control logic for controlling a multiplexed first execution environment and a multiplexed second execution environment, comprising: a step of calling a user-defined library function from at least one calculation element constituting the control logic; a step of fetching an intermediate calculation value of the user-defined library function in the standby side of the first execution environment or the second execution environment from an interface area in which the intermediate calculation value of the user-defined library function in the active side of the first execution environment or the second execution environment is stored in advance; and a step of writing the intermediate calculation value of the user-defined library function in the active side of the first execution environment or the second execution environment to the interface area.
[0061] According to the above aspect (7), the control logic is configured so that user-defined library functions can be called from at least some of the calculation elements (e.g., POLs). This allows for the implementation of advanced control and calculation functions by modifying the user-defined library functions included in the control logic, without modifying the overall basic configuration of the control logic, such as the embedded software of a PLC / DCS. The user-defined library functions store intermediate calculation values in the execution environment on the active side of the multiplexed system in an interface area in advance, and then retrieve them from the interface area in the execution environment on the standby side, thereby achieving multiplexed control with data tracking that can be achieved by the advanced control and calculation functions.
[0062] M Control model CC Intermediate code CL Control logic SC Source code BF Binary file IA Interface area AP Intermediate calculation value acquisition unit E1 First execution environment E2 Second execution environment
Claims
1. A control program for a multiplexing system including control logic for controlling a multiplexed first and second execution environments, the control program being capable of executing on a computer device the steps of: calling a user-defined library function from at least one calculation element constituting the control logic; and fetching an intermediate calculation value of the user-defined library function in the standby side of the first execution environment or the second execution environment from an interface area in which the intermediate calculation value of the user-defined library function in the active side of the first execution environment or the second execution environment is pre-stored.
2. A control program for a multiplexing system as described in claim 1, further comprising a step of writing intermediate calculation values of the user-defined library function in at least the active side of the first execution environment or the second execution environment to the interface area.
3. A control program for a multiplexing system according to claim 1 or 2, wherein the intermediate calculation value is data to be tracked between the first execution environment and the second execution environment.
4. A control program for a multiplexing system according to claim 3, wherein said user-defined library function identifies said data to be tracked from among a plurality of global variables included in said user-defined library function.
5. The control program for a multiplexing system according to claim 1 or 2, wherein said user-defined library functions are written in a general-purpose programming language.
6. A control system for a multiplexed system having a calculation unit capable of executing the control program according to claim 1 or 2.
7. A control method for a multiplexed system including a control logic for controlling a multiplexed first execution environment and a multiplexed second execution environment, comprising: a step of calling a user-defined library function from at least one calculation element constituting the control logic; and a step of fetching an intermediate calculation value of the user-defined library function in the standby side of the first execution environment or the second execution environment from an interface area in which the intermediate calculation value of the user-defined library function in the active side of the first execution environment or the second execution environment is pre-stored.
Citation Information
Patent Citations
Duplex control system, duplex control method and duplex control program
JP2013250591A
Open control system architecture for mobile autonomous systems
US20070112700A1
