JP5602643B2 - Schedule creation device, schedule creation method, and schedule creation program - Google Patents

Description

  The present invention relates to a schedule creation apparatus and a schedule creation program for creating a schedule for periodically executing a control loop composed of a plurality of functional blocks defined in a fieldbus segment.

  In the field where production processes are managed, various field devices with communication functions (for example, sensors and valves) are installed in the plant, and the signals transmitted from the field devices are connected to a network called a field bus. Is received by a management device and manages various production processes. For this reason, the field device is connected to a network called a field bus.

Fieldbus is a communication method that enables two-way communication using digital signals, and its communication specifications are standardized (Foundation fieldbus) by the Fieldbus Foundation ^TM established in 1994 (standardization). )

  Conventionally, in a fieldbus segment, using a sub-schedule created for each control loop as a schedule for periodically executing a control loop composed of a plurality of functional blocks defined in the segment. It is known to create a schedule (see, for example, Patent Document 1).

JP 2008-90841 A

  However, since the number of sub-schedules that can be set is limited by the performance of the link master device that controls the execution timing of the control loop, in the conventional schedule creation device, the number of control loop execution cycles can be set When the number is larger than the number of the control loop, the control loop cannot be executed in a desired execution cycle.

  Some aspects of the present invention have been made in view of the above-described problems. Even when the number of execution cycles of the control loop is larger than the number of sub-schedules that can be set, the control loop is executed at a desired execution cycle. It is an object to provide a schedule creation device, a schedule creation method, and a schedule creation program that can be executed.

  A schedule creation device according to the present invention is a schedule creation device for creating a schedule for periodically executing a control loop constituted by a plurality of functional blocks of a fieldbus using a plurality of sub-schedules. When a sub-schedule having a period i times the execution period (i is an integer equal to or greater than 2) is set, an execution data generation unit is provided that generates i execution data for executing the control loop in the sub-schedule. .

  According to this configuration, when a sub-schedule having a period i times (i is an integer of 2 or more) the execution period of the control loop is set, the execution data for executing the control loop in the sub-schedule is i. Generate. As a result, for example, in a sub-schedule having a period of T, the control loop can be executed i times at an execution period of T / i.

  Preferably, the execution data includes an offset time based on the start time of the sub-schedule.

  According to such a configuration, the execution data includes an offset time with reference to the start time of the sub-schedule. Thereby, when generating i pieces of execution data, the control loop can be easily executed i times in the sub-schedule by setting the interval of each offset time to the execution cycle.

  Preferably, when a plurality of sub-schedules having a period i times the execution period of the control loop and different from each other are set, the execution data generation unit I pieces of execution data are generated in the sub-schedule having the shortest cycle.

  According to such a configuration, when a plurality of sub-schedules having a period that is i times (i is an integer of 2 or more) the execution period of the control loop and different from each other are set, I pieces of execution data are generated in the sub-schedule having the shortest period among the sub-schedules. Thus, for example, compared with the case of generating execution data in the sub-schedule having the longest cycle, if execution data is generated in the sub-schedule having the shortest cycle, less execution data is required, and the number of execution data to be generated is reduced. Can be reduced. As a result, the size of the schedule to be created can be reduced.

  Preferably, a link master device that controls the operation timing of the control loop is further provided with a transmission unit that transmits the schedule via the field bus.

  According to this configuration, the link master device that controls the operation timing of the control loop is further provided with a transmission unit that transmits the schedule via the fieldbus. Thereby, the link master device can execute the schedule created by the schedule creation device.

  Preferably, the aforementioned link master device has a maximum configurable number that is the maximum number of sub-schedules that can be set, and when there are a plurality of link master devices in the field bus segment, A sub-schedule for setting a sub-schedule based on the minimum value of the maximum settable number of each link master device acquired and the settable maximum number acquisition unit for acquiring the maximum settable number of each link master device via And a setting unit.

  According to such a configuration, when there are a plurality of link master devices in the fieldbus segment, the settable maximum number acquisition unit that acquires the settable maximum number of each link master device via the fieldbus, and each acquired A sub-schedule setting unit configured to set a sub-schedule based on a minimum value of the settable maximum number of link master devices; Thereby, the number of sub-schedules that can be set by all the link master devices in the segment are set. Accordingly, a schedule that can be executed by all link master devices in the segment can be transmitted to each link master device.

  A schedule creation method and a schedule creation program according to the present invention are a schedule creation method for creating a schedule for periodically executing a control loop constituted by a plurality of functional blocks of a fieldbus using a plurality of sub-schedules. When a sub-schedule having a period that is i times the control loop execution period (i is an integer of 2 or more) is set, the execution data generation unit executes the execution data for executing the control loop in the sub-schedule. i generating step is provided.

  According to such a configuration, when a sub-schedule having a period i times (i is an integer equal to or greater than 2) the execution period of the control loop is set, the execution data generation unit executes the control loop in the sub-schedule. A step of generating i pieces of execution data to be executed. Thereby, for example, in a sub-schedule having a period of T, the control loop 135 can be executed i times at an execution period of T / i.

  Preferably, the execution data includes an offset time based on the start time of the sub-schedule.

  According to such a configuration, the execution data includes an offset time with reference to the start time of the sub-schedule. Thereby, when generating i pieces of execution data, the control loop can be easily executed i times in the sub-schedule by setting the interval of each offset time to the execution cycle.

  Preferably, when a plurality of sub-schedules having a period i times the execution period of the control loop and different from each other are set in the segment and stored in the storage unit, the generating step described above is performed The execution data generation unit generates i execution data in the sub-schedule having the shortest cycle among the plurality of sub-schedules.

  According to such a configuration, a plurality of sub-schedules having a period i times (i is an integer equal to or greater than 2) the execution period of the control loop and different from each other are set as segments and stored in the storage unit. The execution data generation unit generates i pieces of execution data in the sub-schedule having the shortest cycle among the plurality of sub-schedules. Thus, for example, compared with the case of generating execution data in the sub-schedule having the longest cycle, if execution data is generated in the sub-schedule having the shortest cycle, less execution data is required, and the number of execution data to be generated is reduced. Can be reduced. As a result, the size of the schedule to be created can be reduced.

  Preferably, the transmission unit further includes a step of transmitting the schedule via the field bus to the link master device that controls the operation timing of the control loop.

  According to this configuration, the transmission unit further includes a step of transmitting the schedule via the fieldbus to the link master device that controls the operation timing of the control loop. Thereby, the link master device can execute the schedule created by the schedule creation method or the schedule creation program.

  Preferably, the above-mentioned link master device has a settable maximum number that is the maximum number of subschedules that can be set, and can be set when there are multiple link master devices in a fieldbus segment. The number acquisition unit obtains the maximum settable number of each link master device via the fieldbus, and the sub-schedule setting unit determines the minimum number of the acquired maximum settable number of each link master device. And setting a sub-schedule.

  According to such a configuration, when there are a plurality of link master devices in a fieldbus segment, the settable maximum number acquisition unit acquires the settable maximum number of each link master device via the fieldbus; The schedule setting unit further includes a step of setting a sub-schedule based on a minimum value of the acquired maximum number of link master devices that can be set. Thereby, the number of sub-schedules that can be set by all the link master devices in the segment are set. Accordingly, a schedule that can be executed by all link master devices in the segment can be transmitted to each link master device.

  According to the present invention, for example, in a sub-schedule having a period of T, a control loop can be executed i times at a T / i execution period. Thereby, even when the number (type) of execution cycles of the control loop is larger than the maximum value (maximum number that can be set) of the settable sub-schedule, a sub-schedule having a cycle i times the execution cycle of the control loop is set If it is, the control loop can be executed at a desired execution cycle.

It is a block diagram explaining the schematic structure of the field apparatus management system in 1st Embodiment of this invention. It is a block diagram explaining the relationship between the field device shown in FIG. 1, and a functional block. It is an image figure explaining the example of the control loop comprised by the functional block shown in FIG. It is an image figure explaining the example of the control loop comprised by the functional block shown in FIG. It is an image figure explaining the example of the control loop comprised by the functional block shown in FIG. It is an image figure explaining the example of the control loop comprised by the functional block shown in FIG. It is an image figure explaining the example of the control loop comprised by the functional block shown in FIG. It is a figure explaining the execution timing of the control loop shown in FIG. It is a figure explaining the execution timing of the control loop shown in FIG. It is a figure explaining the execution timing of the control loop shown in FIG. It is a figure explaining the execution timing of the control loop shown in FIG. It is a figure explaining the execution timing of the control loop shown in FIG. It is a flowchart explaining operation | movement of the schedule preparation apparatus shown in FIG. It is a block diagram explaining the schematic structure of the field apparatus management system in 2nd Embodiment of this invention. It is a flowchart explaining operation | movement of the schedule preparation apparatus shown in FIG.

  Embodiments of the present invention will be described below. In the following description of the drawings, the same or similar parts are denoted by the same or similar reference numerals. However, the drawings are schematic. Therefore, specific dimensions and the like should be determined in light of the following description. Moreover, it is a matter of course that portions having different dimensional relationships and ratios are included between the drawings.

[First Embodiment]
1 to 13 are for illustrating a first embodiment of the present invention. FIG. 1 is a block diagram illustrating a schematic configuration of a field device management system according to the first embodiment of the present invention. As shown in FIG. 1, a field device management system 100 includes a fieldbus segment (hereinafter simply referred to as a segment) 10, a controller 20, and a schedule creation device 30 according to the present invention.

  The segment 10 includes a plurality of field devices 11A to 11J and a link master device 12. The field devices 11A to 11J and the link master device 12 are connected to the field bus F and can communicate with each other.

  The fieldbus F is a network that uses the above-mentioned standardized (standardized) Foundation fieldbus protocol as a communication specification. The segment 10 is a basic configuration of the fieldbus F and is a fieldbus term meaning one transmission path composed of one transmission medium.

  The field devices 11A to 11J are various devices installed in the plant, and are fieldbus-compatible devices that can communicate bidirectionally via the fieldbus F. As each field device 11A-11J, actuators, such as various sensors, such as a flow sensor, a pressure sensor, and a temperature sensor, valves (valves), such as a flow control valve and a pressure control valve, and a pump and a fan correspond, for example.

  The link master device 12 is a device having an LAS unit 121 having a link active scheduler (hereinafter referred to as LAS) function and a storage unit 122.

  The LAS unit 121 has a network control function for controlling all communications including periodic communications and aperiodic communications performed on the fieldbus F. The LAS unit 121 has functions such as sending a trigger frame for starting periodic communication and sending a frame for giving transmission permission to the field devices 11A to 11J for performing aperiodic communication. In the following, only periodic communication will be described unless otherwise required, and description of aperiodic communication will be omitted.

  The storage unit 122 is a storage unit such as a memory, and stores macro cycle data 122a, sub-schedule data 122b, and a schedule program 122c.

  Here, the schedule defines the execution timing of the periodic operation of the control loop described later. A macro cycle is a fieldbus term meaning a reference period of a schedule, and one macro cycle is set for a schedule. The sub-schedule includes execution data for executing the control loop, and a plurality of sub-schedules are set. In this embodiment, the schedule is implemented (executed) using a plurality of sub-schedules.

  The macro cycle data 122a includes information on the macro cycle, for example, information on the period. The sub-schedule data 122b includes information related to the sub-schedule, for example, information such as the period of each sub-schedule and the maximum number of sub-schedules that can be set (hereinafter referred to as the maximum number that can be set). The schedule program 122c is a program created by merging a plurality of sub-schedules and scheduled so that the periodic operation of the control loop is repeated at the period of the macro cycle. The LAS unit 121 controls the operation and communication in the segment 10 based on the schedule program 122c.

  The controller 20 includes, for example, a CPU (not shown), storage means (not shown) such as a memory, and an interface (not shown) for data communication (data transmission / reception). The controller 20 is connected to the field bus F, and can communicate with each of the field devices 11A to 11J and the link master device 12, and can also communicate with each other by connecting to the schedule creation device 30.

  The schedule creation device 30 is a device for creating a schedule program used by the link master device 12. The schedule creation device 30 includes an input / output interface unit 31, a storage unit 32, a setting unit 33, an execution data generation unit 34, a schedule program creation unit 35, and a data load unit 36.

  The input / output interface unit 31 is for performing data communication (data transmission / reception) between input means such as a keyboard and a mouse and output means such as a display and a printer. The input / output interface unit 31 may provide a GUI (Graphical User Interface) to the user, for example, by a program (software) executed by the schedule creation device 30.

  The storage unit 32 is a storage unit such as a memory, and stores macro cycle data 32a, sub-schedule data 32b, and a schedule program 122c similar to the storage unit 122 of the link master device 12. In addition, the storage unit 32 stores functional block data 13 including information on functional blocks to be described later, for example, functional block definition information.

  The setting unit 33 sets a plurality of sub-schedules based on an execution cycle of a control loop, which will be described later, input via the input / output interface unit 31.

  The execution data generation unit 34 generates execution data for executing the control loop in the sub-schedule set by the setting unit 33.

  The schedule program creation unit 35 creates the schedule program 32c using the sub-schedule including the execution data generated by the execution data generation unit 34.

  The data load unit 36 transmits data including the schedule program 32 c created by the schedule program creation unit 35 to the link master device 12 via the fieldbus F.

  A function block (Function Block) is a fieldbus term meaning a function block of unit functions necessary for constructing a control system. Specifically, the functional block defines a function to be executed by devices constituting the segment 10, for example, the field devices 11A to 11J. The functions defined in the function block include measurement values, for example, voltage values, temperature values, flow rate values, etc. acquired by the field devices 11A to 11J, and algorithms or calculations such as differentiation, integration, addition, subtraction, and multiplication. , Division, etc., instrumentation such as valve opening / closing, furnace adjustment, boiler adjustment, etc., or other functions are performed.

  FIG. 2 is a block diagram for explaining the relationship between the field device shown in FIG. 1 and functional blocks. As shown in FIG. 2, the functional block data 13 shown in FIG. 1 includes an AI functional block (AI1) 13a having an analog input (hereinafter referred to as AI) function, a proportional / integral / differential (hereinafter referred to as PID) function. PID functional block (PID1) 13b, AO functional block (AO1) 13c having analog output (hereinafter referred to as AO) function, AI functional block (AI2) 13d having AI function, PID functional block (PID2) having PID function 13e, an AO function block (AO2) 13f having an AO function, an AI function block (AI3) 13g having an AI function, a PID function block (PID3) 13h having a PID function, an AO function block (AO3) 13i having an AO function, AI function block (AI4) 13j having AI function, PI PID function block (PID4) 13k having a function, AO function block (AO4) 13l having an AO function, AI function block (AI5) 13m having an AI function, PID function block (PID5) 13n having a PID function, and AO function AO function block (AO5) 13o having information.

  The AI function block (AI1) 13a defines a function executed by the field device 11A, and the PID function block (PID1) 13b and the AO function block (AO1) 13c define a function executed by the field device 11B. The AI function block (AI2) 13d defines a function executed by the field device 11C, and the PID function block (PID2) 13e and the AO function block (AO2) 13f define a function executed by the field device 11D. The AI function block (AI3) 13g defines a function executed by the field device 11E, and the PID function block (PID3) 13h and the AO function block (AO3) 13i define a function executed by the field device 11F. The AI function block (AI4) 13j defines a function executed by the field device 11G, and the PID function block (PID4) 13k and the AO function block (AO4) 13l define a function executed by the field device 11H. The AI function block (AI5) 13m defines a function executed by the field device 11I, and the PID function block (PID5) 13n and the AO function block (AO5) 13o define a function executed by the field device 11J.

  In the present embodiment, only functional blocks executed by the field devices 11A to 11J constituting the segment 10 are shown, but the present invention is not limited to this, and other devices connected to the field bus F, for example, other The functions executed by the field devices constituting the segment may be defined as function blocks.

  3 to 7 are image diagrams for explaining examples of control loops configured by the functional blocks shown in FIG. As shown in FIGS. 3-7, each functional block 13a-13o shown in FIG. 2 includes at least one input and / or at least one output. The functional blocks 13a to 13o are connected (coupled) to each other, for example, by a user operation via the input / output interface unit 31. In this way, by connecting (coupling) the functional blocks, a control loop to be controlled by the schedule is formed (configured).

  In the example shown in FIG. 3, the output of the AI function block (AI1) 13a is connected to the input of the PID function block (PID1) 13b, and the output of the PID function block (PID1) 13b is connected to the AO function block (AO1) 13c. Connected to input. The output of the AO function block (AO1) 13c is connected to the input of the PID function block (PID1) 13b. In this manner, the control loop 131 is formed by connecting (coupling) the AI function block (AI1) 13a, the PID function block (PID1) 13b, and the AO function block (AO1) 13c.

  In the example shown in FIG. 4, the output of the AI function block (AI2) 13d is connected to the input of the PID function block (PID2) 13e, and the output of the PID function block (PID2) 13e is connected to the AO function block (AO2) 13f. Connected to input. The output of the AO function block (AO2) 13f is connected to the input of the PID function block (PID2) 13e. In this way, the control loop 132 is formed by connecting (coupling) the AI function block (AI2) 13d, the PID function block (PID2) 13e, and the AO function block (AO2) 13f.

  In the example shown in FIG. 5, the output of the AI function block (AI3) 13g is connected to the input of the PID function block (PID3) 13h, and the output of the PID function block (PID3) 13h is the output of the AO function block (AO3) 13i. Connected to input. The output of the AO function block (AO3) 13i is connected to the input of the PID function block (PID3) 13h. In this way, the control loop 133 is formed by connecting (coupling) the AI function block (AI3) 13g, the PID function block (PID3) 13h, and the AO function block (AO3) 13i.

  In the example shown in FIG. 6, the output of the AI functional block (AI4) 13j is connected to the input of the PID functional block (PID4) 13k, and the output of the PID functional block (PID4) 13k is connected to the AO functional block (AO4) 13l. Connected to input. The output of the AO function block (AO4) 13l is connected to the input of the PID function block (PID4) 13k. In this manner, the control loop 134 is formed by connecting (coupling) the AI function block (AI4) 13j, the PID function block (PID4) 13k, and the AO function block (AO4) 13l.

  In the example shown in FIG. 7, the output of the AI functional block (AI5) 13m is connected to the input of the PID functional block (PID5) 13n, and the output of the PID functional block (PID5) 13n is connected to the AO functional block (AO5) 13o. Connected to input. The output of the AO function block (AO5) 13o is connected to the input of the PID function block (PID5) 13n. In this way, the control loop 135 is formed by connecting (coupling) the AI function block (AI5) 13m, the PID function block (PID5) 13n, and the AO function block (AO5) 15o.

  In the present embodiment, only the control loop formed (configured) by the functional blocks 13a to 13o defined in the segment 10 is shown. However, the present invention is not limited to this. A function block defined in the segment may be included.

  FIG. 8 is a diagram for explaining the execution timing of the control loop shown in FIG. In the following description, it is assumed that the macro cycle is 4000 ms and the maximum number of sub-schedules that can be set is “4”, unless otherwise specified. When the execution cycle of the control loop 131 shown in FIG. 3 is 4000 ms, the setting unit 33 shown in FIG. 1 executes the control loop 131 as the cycle of the sub-schedule 210 constituting the schedule 200 as shown in FIG. The same 4000 ms as the period is set. As a result, the sub-schedule 210 is executed once in the schedule 200. The execution cycle of the control loop 131 is input by the user via the input / output interface unit 31 shown in FIG. Next, the execution data generation unit 34 illustrated in FIG. 1 assigns the sub-schedule 210 to the control loop 131. Further, in order to execute the AI function block (AI1) 13a, the PID function block (PID1) 13b, and the AO function block (AO1) 13c constituting the control loop 131 once in the sub-schedule 210, an execution data generation unit 34 generates execution data 211, 212, and 213. Further, the connection between the AI functional block (AI1) 13a and the PID functional block (PID1) 13b shown in FIG. 3 is different from that of the functional block of the field device 11A and the field device 11B as shown in FIG. The execution data generation unit 34 executes the communication (C1) 131a in the segment 10 in order to input the output of the AI function block (AI1) 13a to the PID function block (PID1) 13b. Data 214 is generated. As described above, the control loop 131 is executed once in the sub-schedule 210.

  Each of the generated execution data 211 to 214 includes an offset time from a reference time (0 ms in FIG. 3) in order to execute at a predetermined timing in the sub-schedule 210. In the example shown in FIG. 8, the execution data 211 has an offset time of 0 ms, the execution data 212 has an offset time of 200 ms, the execution data 213 has an offset time of 330 ms, and the execution data 214 has an offset of 170 ms. Time is set. Note that the offset time of each piece of execution data 211 to 214 is input by the user via the input / output interface unit 31.

  FIG. 9 is a diagram for explaining the execution timing of the control loop shown in FIG. When the execution cycle of the control loop 132 shown in FIG. 4 is 2000 ms, the setting unit 33 shown in FIG. 1 executes the control loop 132 as the cycle of the sub-schedule 220 constituting the schedule 200 as shown in FIG. The same 2000 ms as the period is set. As a result, the sub-schedule 210 is executed twice in the schedule 200. The execution period of the control loop 132 is input by the user via the input / output interface unit 31 shown in FIG. Next, the execution data generation unit 34 illustrated in FIG. 1 assigns a sub-schedule 220 to the control loop 132. Further, in order to execute the AI function block (AI2) 13d, the PID function block (PID2) 13e, and the AO function block (AO2) 13f constituting the control loop 132 once in the sub-schedule 220, an execution data generation unit 34 generates execution data 221, 222, and 223. Further, the execution data generating unit 34 connects the AI function block (AI2) 13d and the PID function block (PID2) 13e shown in FIG. 4 with different devices, that is, as shown in FIG. The execution of the communication (C2) 132a in the segment 10 is executed in order to input the output of the AI function block (AI2) 13d to the PID function block (PID2) 13f. Data 224 is generated. As a result, the control loop 132 is executed once in the sub-schedule 220.

  Each of the generated execution data 221 to 224 includes an offset time from a reference time (0 ms or 2000 ms in FIG. 9) in order to execute at a predetermined timing in the sub-schedule 220. In the example shown in FIG. 9, the execution data 221 has an offset time of 0 ms, the execution data 222 has an offset time of 140 ms, the execution data 223 has an offset time of 270 ms, and the execution data 214 has an offset of 110 ms. Time is set. The offset time of each piece of execution data 221 to 224 is input by the user via the input / output interface unit 31.

  FIG. 10 is a diagram for explaining the execution timing of the control loop shown in FIG. When the execution cycle of the control loop 133 shown in FIG. 5 is 1000 ms, the setting unit 33 shown in FIG. 1 executes the control loop 133 as the cycle of the sub-schedule 230 constituting the schedule 200 as shown in FIG. The same 1000 ms as the period is set. Thereby, in the schedule 200, the sub-schedule 210 is executed four times. The execution period of the control loop 133 is input by the user via the input / output interface unit 31 shown in FIG. Next, the execution data generation unit 34 illustrated in FIG. 1 assigns a sub-schedule 230 to the control loop 133. In addition, in order to execute the AI function block (AI3) 13g, the PID function block (PID3) 13h, and the AO function block (AO3) 13i constituting the control loop 133 once in the sub-schedule 230, an execution data generation unit 34 generates execution data 231, 232, and 233. Further, the AI function block (AI3) 13g and the PID function block (PID3) 13h shown in FIG. 5 are connected to different devices, that is, the function block of the field device 11E and the field device 11F as shown in FIG. In order to input the output of the AI function block (AI3) 13g to the PID function block (PID3) 13h, the execution data generation unit 34 executes the communication (C3) 133a in the segment 10 in order to input the output of the AI function block (AI3) 13g. Data 234 is generated. As a result, the control loop 133 is executed once in the sub-schedule 230.

  Each of the generated execution data 231 to 234 includes an offset time from a reference time (0 ms, 1000 ms, 2000 ms, or 3000 ms in FIG. 10) in order to execute at a predetermined timing in the sub-schedule 230. In the example shown in FIG. 10, the execution data 231 has an offset time of 0 ms, the execution data 232 has an offset time of 110 ms, the execution data 233 has an offset time of 240 ms, and the execution data 234 has an offset of 80 ms. Time is set. The offset time of each piece of execution data 231 to 234 is input by the user via the input / output interface unit 31.

  FIG. 11 is a diagram for explaining the execution timing of the control loop shown in FIG. When the execution period of the control loop 134 shown in FIG. 6 is 800 ms, the setting unit 33 shown in FIG. 1 executes the control loop 133 as the period of the sub-schedule 240 constituting the schedule 200 as shown in FIG. The same 800 ms as the period is set. Thereby, in the schedule 200, the sub-schedule 210 is executed five times. The execution cycle of the control loop 134 is input by the user via the input / output interface unit 31 shown in FIG. Next, the execution data generation unit 34 illustrated in FIG. 1 assigns a sub-schedule 240 to the control loop 134. Further, in order to execute the AI function block (AI4) 13j, the PID function block (PID4) 13k, and the AO function block (AO4) 13l constituting the control loop 134 once in the sub-schedule 240, an execution data generation unit 34 generates execution data 241, 242, and 243. Further, the connection between the AI functional block (AI4) 13j and the PID functional block (PID4) 13k shown in FIG. 6 is different between the functional blocks of the field device 11G and the field device 11H as shown in FIG. Since it is a connection with the functional block, the execution data generating unit 34 executes the execution data for executing the communication (C4) 134a in the segment 10 in order to input the output of the AI functional block (AI4) 13j to the PID functional block (PID4) 13k. 244 is generated. As a result, the control loop 134 is executed once in the sub-schedule 240.

  Each of the generated execution data 241 to 244 includes an offset time from a reference time (0 ms, 800 ms, 1600 ms, 2400 ms, or 3200 ms in FIG. 11) in order to execute at a predetermined timing in the sub-schedule 240. In the example shown in FIG. 11, the execution data 241 has an offset time of 0 ms, the execution data 242 has an offset time of 170 ms, the execution data 243 has an offset time of 300 ms, and the execution data 244 has an offset of 140 ms. Time is set. The offset time of each execution data 241 to 244 is input by the user via the input / output interface unit 31.

  When the execution cycle of the control loop 135 shown in FIG. 7 is 500 ms, the number of set sub-schedules 210 to 240 has reached the set maximum value (“4”). It is impossible to schedule, or a countermeasure has been taken such as changing the execution period of the control loop 135 to the nearest period, for example, 800 ms among the set periods of the four sub-schedules 210 to 240.

  FIG. 12 is a diagram for explaining the execution timing of the control loop shown in FIG. On the other hand, when the number of set sub-schedules 210 to 240 reaches the set maximum value (“4”), there are sub-schedules 210 to 240 having the same cycle as the execution cycle of the control loop 135. If not, the execution data creation unit 34 shown in FIG. 1 has a sub-schedule having a period that is i times (i is an integer equal to or larger than 2) the execution period of the control loop 135, as shown in FIG. A sub-schedule 230 having a period is assigned to the control loop 135. The execution period of the control loop 135 is input by the user via the input / output interface unit 31 shown in FIG. In order to execute the AI function block (AI5) 13m, the PID function block (PID5) 13n, and the AO function block (AO5) 13o constituting the control loop 135, i times, that is, twice in the sub-schedule 230, respectively. The execution data creation unit 34 generates execution data 235a, 236a, and 237a and execution data 235b, 236b, and 237b. Further, the connection between the AI function block (AI5) 13m and the PID function block (PID5) 13n shown in FIG. 7 is different between the function blocks of the field device 11I and the field device 11J as shown in FIG. Since it is a connection to the functional block, the schedule creation device 30 executes the communication (C5) 135a in the segment 10 twice in order to input the output of the AI functional block (AI5) 13m to the PID functional block (PID5) 13n. 238a and execution data 238b are generated. In this way, by generating two pieces of execution data of execution data 235a, 236a, 237a, 238a and execution data 235b, 236b, 237b, 238b for executing the control loop 135 in the sub-schedule 230, 1000 ms of In the sub-schedule 230 having a cycle, the control loop 135 can be executed twice at an execution cycle of 1000 ms / 2, that is, 500 ms.

  As described above, a plurality of sub-schedules 210, 220, and 230 having a period that is i times the execution period of the control loop 135 (i is an integer of 2 or more) and different from each other are set. In this case, the execution data creation unit 34 preferably generates i pieces of execution data, that is, two pieces, in the sub-schedule 230 having the shortest cycle. As a result, for example, when generating execution data in the sub-schedule 210 having the longest cycle, the control loop needs to be executed eight times, so that eight execution data are generated, whereas the shortest cycle is generated. When execution data is generated in the sub-schedule 230, only two pieces of execution data are required, and the number of execution data to be generated can be reduced.

  Each of the generated execution data 235a, 236a, 237a, and 238a includes an offset time from a reference time (0 ms, 1000 ms, 2000 ms, or 3000 ms in FIG. 12) in order to execute at a predetermined timing in the sub-schedule 230. In the example shown in FIG. 12, the execution data 235a has an offset time of 0 ms, the execution data 236a has an offset time of 230 ms, the execution data 237a has an offset time of 360 ms, and the execution data 238a has an offset of 200 ms. Time is set. The offset time of each piece of execution data 235a, 236a, 237a, 238a is input by the user via the input / output interface unit 31. In addition, each of the generated execution data 235b, 236b, 237b, and 238b has an offset time from a reference time (0 ms, 1000 ms, 2000 ms, or 3000 ms in FIG. 12) in order to execute at a predetermined timing in the sub-schedule 230. Including. In the example shown in FIG. 12, the execution data 235b has an offset time of 500 ms, the execution data 236b has an offset time of 730 ms, the execution data 237b has an offset time of 860 ms, and the execution data 238b has an offset of 700 ms. Time is set. The offset times of the execution data 235b, 236b, 237b, and 238b are calculated by adding the execution period of the control loop 135 to the offset time input by the user via the input / output interface unit 31. As described above, when generating two pieces of execution data 235a, 236a, 237a, 238a, 235b, 236b, 237b, and 238b, each offset time interval is set to an execution cycle, that is, 500 ms, so that In the sub-schedule 230, the control loop 135 can be executed twice.

  The schedule program creation unit 35 shown in FIG. 1 merges execution data created for each of the sub-schedules 210 to 240 to create a schedule program 32c. 1 loads the created schedule program 32c, the macro cycle data 32a and the sub-schedule data 32b in the storage unit 32 via the controller 20 and the field bus F shown in FIG. Transmit (load) to the device 12. Thereby, the link master device 12 can execute the schedule program 32c created by the schedule creation device 30.

  Next, a schedule creation method and a schedule creation program will be described with reference to FIG. FIG. 13 is a flowchart for explaining the operation of the schedule creation device shown in FIG. When a control loop is created by a user's operation and the execution period of the control loop is input via the input / output interface unit 31 shown in FIG. 1, the schedule creation device 30 shown in FIG. 1 starts processing S300. . That is, as shown in FIG. 13, the setting unit 33 shown in FIG. 1 reads the sub-schedule data 32b from the storage unit 32 shown in FIG. 1, and the number (type) of execution cycles of the input control loop is It is determined whether or not the maximum number of schedules that can be set is larger (S301). The number of control loop execution cycles means the number of types. For example, if all four control loops have the same execution cycle, the number of control loop execution cycles is “4”. Since the number of types is one, the setting unit 33 determines that the number (type) of execution cycles of the control loop is “1”.

  As a result of the determination in S301, when the number (type) of execution cycles of the input control loop is larger than the maximum number that can be set in the sub-schedule, the setting unit 33 can be set based on the execution cycle of the input control loop The sub-schedule period is set up to the maximum number (S302), and the sub-schedule data 32b is written (updated) in the storage unit 32. On the other hand, as a result of the determination in S301, when the number (type) of execution cycles of the input control loop is not larger than the maximum number that can be set in the sub-schedule, the setting unit 33 is based on the execution cycle of the input control loop. The sub-schedule cycle is set (S303), and the sub-schedule data 32b is written (updated) in the storage unit 32. In S302 or S302, the setting unit 33 may simultaneously set the least common multiple of the set sub-schedule periods as a macro cycle and update the macro cycle data 32a.

  In the case of the example shown in FIGS. 8 to 12, since the set maximum value of the sub-schedule is “4”, the execution cycles of the formed control loops 131 to 135 are five (five types). For example, the setting unit 33 sets 4000 ms, 2000 ms, 1000 ms, and 800 ms as the cycles of the sub-schedules 210 to 240 in the order of long execution cycles or the input sequence of execution cycles. The setting unit 33 sets 4000 ms, which is the least common multiple, as the macro cycle (cycle of the schedule 200).

  In the present embodiment, the sub-schedule period and the macro cycle are automatically set in S302 or S303 based on the input execution period of the control loop. However, the present invention is not limited to this. For example, the user may manually set the sub-schedule period and the macro cycle in advance. In this case, the process S300 starts from the next S304.

  After S302 or S303, the execution data creation unit 34 shown in FIG. 1 reads the sub-schedule data 32b from the storage unit 32, and based on the input execution period of the control loop and the period of each set sub-schedule. Then, it is determined whether or not a sub-schedule can be assigned to each control loop (S304). Specifically, the execution data creation unit 34 has a sub-schedule having the same cycle as the control loop execution cycle, or a cycle that is i times the control loop execution cycle (i is an integer of 2 or more). It is determined that a sub-schedule can be assigned. On the other hand, the execution data creation unit 34 is in other cases, i.e., when a sub-schedule having the same period as the execution period of the control loop is not set, and i times the execution period of the control loop (i is 2 or more). When a sub-schedule having a period of (integer) is not set, it is determined that the sub-schedule is not assignable (cannot be assigned).

  If the sub-schedule can be assigned as a result of the determination in S304, the execution data creation unit 34 reads the sub-schedule data 32b from the storage unit 32, assigns the sub-schedule to the formed control loop, and performs input / output. Based on the offset time input via the interface unit 31, each function block and communication execution data are generated for each control loop (S305). On the other hand, if it is determined in S304 that the sub-schedule cannot be assigned, the execution data creation unit 34 outputs an error via the input / output interface unit (S306), and the schedule creation device 30 ends the process S300.

  In S306, before outputting an error, the execution data creation unit 34 asks whether or not to change the execution cycle of the input control loop to a cycle based on the set sub-schedule cycle. May be. For example, if the sub-schedule cycle is set to 4000 ms, 2000 ms, 1000 ms, and 800 ms, and the input control loop execution cycle is 501 ms, the control loop execution cycle is 500 ms and the cycle is 1000 ms. Since the sub-schedule can be assigned, the execution data creation unit 34 outputs a message asking whether to change the execution period of the control loop to 500 ms via the input / output interface unit 31. In this case, when the execution period of the input control loop is changed to 500 ms, the execution data creation unit 34 performs step S305 without outputting an error.

  In the case of the control loops 131 to 134 shown in FIG. 3 to FIG. 6 and FIG. 8 to FIG. 11, the execution data creation unit 34 is a sub-schedule having the same period for each control loop 131 to 134 in S304. 210 to 240 are assigned. Next, in S305, the execution data creation unit 34 executes the execution data 211 to 214 of the control loop 131 in the schedule 210, the execution data 221 to 224 of the control loop 132 in the schedule 220, and the execution data of the control loop 133 in the schedule 230. The execution data 241 to 244 of the control loop 134 are generated in the schedule 240, respectively.

  Further, in the case of the example of the control loop 135 shown in FIGS. 7 and 12, the execution data creation unit 34 determines the execution cycle of the control loop 135 from among the set sub-schedules 210 to 240 in S304. A sub-schedule having a period of i times (i is an integer of 2 or more) is searched. In this case, the execution data creation unit 34 detects a sub-schedule 230 having a twice cycle, a sub-schedule 220 having a four-fold cycle, and a sub-schedule 210 having a eight-fold cycle. Here, the execution data creation unit 34 assigns the sub-schedule 230 having the shortest cycle to the control loop 135. Next, the execution data creation unit 34 generates two pieces of execution data 235a, 236a, 237a, and 238a and execution data 235b, 236b, 237b, and 238b that cause the control loop 135 to be executed in the assigned schedule 230. Thereby, in the sub-schedule 230 having a period of 1000 ms, the control loop 135 can be executed twice at an execution period of 1000 ms / 2, that is, 500 ms.

  The execution data 235 a, 236 a, 237 a, 238 a, 235 b, 236 b, 237 b, and 238 b generated by the execution data creation unit 34 preferably includes an offset time based on the start time of the sub-schedule 230. As a result, when generating two pieces of execution data 235a, 236a, 237a, 238a, 235b, 236b, 237b, 238b, the interval of each offset time is set to an execution period, that is, 500 ms, so that In the sub-schedule 230, the control loop 135 can be executed twice.

  As described above, a plurality of sub-schedules 210, 220, and 230 each having a cycle that is i times (i is an integer equal to or greater than 2) the execution cycle of the control loop 135 are set. When stored in the storage unit 32 as the sub-schedule data 32b, the execution data creation unit 34 preferably generates i, that is, two pieces of execution data in the sub-schedule 230 having the shortest cycle. As a result, for example, when generating execution data in the sub-schedule 210 having the longest cycle, the control loop needs to be executed eight times, so that eight execution data are generated, whereas the shortest cycle is generated. When execution data is generated in the sub-schedule 230, only two pieces of execution data are required, and the number of execution data to be generated can be reduced.

  After S305, the schedule program creation unit 35 creates a schedule program 32c by merging execution data created for each sub-schedule (S306), and writes the schedule program 32c in the storage unit 32.

  After S306, the data load unit 36 reads the macro cycle data 32a, the sub-schedule data 32b, and the schedule program 32c from the storage unit 32, and sends them to the link master device 12 via the controller 20 and the field bus F shown in FIG. Transmission (loading) is performed (S307), and the schedule creation device 30 ends the process S300. Thereby, the link master device 12 can execute the schedule created by the schedule creation method or the schedule creation program.

  The transmitted (loaded) macrocycle data 32a, sub-schedule data 32b, and schedule program 32c are stored in the storage unit 122 as macrocycle data 122a, sub-schedule data 122b, and schedule program 122c, respectively. Accordingly, the LAS unit 121 of the link master device 12 can control the periodic operation in the segment 10 based on the schedule program 32c.

  In the present embodiment, the schedule creation device 30 creates the schedule program 32c, but the present invention is not limited to this. As long as transmission (loading) to the link master device 12 is possible, another device such as the controller 20 or the link master device 12 itself may be used. The schedule program 32c is not limited to an apparatus, that is, hardware, and may be software (program) executed by hardware. Furthermore, the schedule program 32c may be a source program or an object program. Further, the schedule to be created may not be a program format as in the schedule program 32c, but may be a data format or a file format.

  As described above, according to the schedule creation device 30 in the present embodiment, when a sub-schedule 230 having a period that is i times (i is an integer of 2 or more) the execution period of the control loop 135 is set, Two pieces of execution data 235 a, 236 a, 237 a, and 238 a and execution data 235 b, 236 b, 237 b, and 238 b are generated to execute the control loop 135 in the schedule 230. Thereby, in the sub-schedule 230 having a period of 1000 ms, the control loop 135 can be executed twice at an execution period of 1000 ms / 2, that is, 500 ms. As a result, even when the number (type) of execution cycles of the control loop is larger than the maximum number that can be set in the sub-schedule, the sub-schedule having a cycle that is i times the execution cycle of the control loop is set. The control loop can be executed at a desired execution cycle.

  Further, according to the schedule creation device 30 in the present embodiment, the execution data 235 a, 236 a, 237 a, 238 a, 235 b, 236 b, 237 b, 238 b includes an offset time with reference to the start time of the sub-schedule 230. As a result, when generating two pieces of execution data 235a, 236a, 237a, 238a, 235b, 236b, 237b, 238b, the interval of each offset time is set to an execution period, that is, 500 ms, so that In the sub-schedule 230, the control loop 135 can be executed twice.

  Further, according to the schedule creation device 30 in the present embodiment, a plurality of sub-schedules 210, each having a cycle that is i times (i is an integer equal to or greater than 2) the execution cycle of the control loop 135, and each cycle being mutually different When 220 and 230 are set, two pieces of execution data 235a, 236a, 237a, 238a, 235b, 236b in the sub-schedule 230 having the shortest cycle among the plurality of sub-schedules 210, 220, and 230, 237b and 238b are generated. Thereby, for example, when generating execution data in the sub-schedule 210 having the longest cycle, it is necessary to execute the control loop 135 eight times. If execution data is generated in the sub-schedule 230, only two pieces of execution data are required, and the number of execution data to be generated can be reduced. Thereby, the size of the schedule program 32c to be created can be reduced.

  Further, according to the schedule creation device 30 in the present embodiment, the data load unit 36 that further transmits the schedule program 32 c via the fieldbus F to the link master device 12 that controls the operation timing of the control loops 131 to 135 is further provided. . Thereby, the link master device 12 can execute the schedule program 32c created by the schedule creation device 30.

  In addition, according to the schedule creation method and schedule creation program in the present embodiment, when the sub-schedule 230 having a period that is i times (i is an integer of 2 or more) the execution period of the control loop 135 is set, The data generation unit 34 includes two steps of generating execution data 235a, 236a, 237a, and 238a and execution data 235b, 236b, 237b, and 238b that cause the control loop 135 to be executed in the sub-schedule 230. Thereby, in the sub-schedule 230 having a period of 1000 ms, the control loop 135 can be executed twice at an execution period of 1000 ms / 2, that is, 500 ms. As a result, even when the number (type) of execution cycles of the control loop is larger than the maximum number that can be set in the sub-schedule, the sub-schedule having a cycle that is i times the execution cycle of the control loop is set. The control loop can be executed at a desired execution cycle.

  Further, according to the schedule creation method and schedule creation program in the present embodiment, the execution data 235a, 236a, 237a, 238a, 235b, 236b, 237b, 238b include an offset time with reference to the start time of the sub-schedule 230. . As a result, when generating two pieces of execution data 235a, 236a, 237a, 238a, 235b, 236b, 237b, 238b, the interval of each offset time is set to an execution period, that is, 500 ms, so that In the sub-schedule 230, the control loop 135 can be executed twice.

  Further, according to the schedule creation method and schedule creation program in the present embodiment, a plurality of sub-cycles having a cycle i times (i is an integer of 2 or more) the execution cycle of the control loop 135 and each cycle being different from each other. When the schedules 210, 220, and 230 are set, the execution data generation unit 34 includes two pieces of execution data 235a in the sub-schedule 230 having the shortest cycle among the plurality of sub-schedules 210, 220, and 230. 236a, 237a, 238a, 235b, 236b, 237b, 238b are generated. Thereby, for example, when generating execution data in the sub-schedule 210 having the longest cycle, it is necessary to execute the control loop 135 eight times. If execution data is generated in the sub-schedule 230, only two pieces of execution data are required, and the number of execution data to be generated can be reduced. Thereby, the size of the schedule program 32c to be created can be reduced.

  Further, according to the schedule creation method and schedule creation program in the present embodiment, the data load unit 36 sends the schedule program 32c to the link master device 12 that controls the operation timing of the control loops 131 to 135 via the fieldbus F. And further comprising the step of transmitting. Thereby, the link master device 12 can execute the schedule program 32c created by the schedule creation method or the schedule creation program.

[Second Embodiment]
14 and 15 are for illustrating a second embodiment of the present invention. Unless otherwise specified, the same components as those in the above-described embodiment are denoted by the same reference numerals, and the description thereof is omitted. Further, components not shown in the figure are the same as those in the above-described embodiment.

  FIG. 14 is a block diagram illustrating a schematic configuration of a field device management system according to the second embodiment of the present invention. As shown in FIG. 14, the segment 10 includes a plurality of link master devices 12A, 12B, and 12C having the same configuration as the link master device 12 of the first embodiment.

  Each link master device 12A, 12B, 12C has a maximum number of sub-schedules that can be set, that is, a maximum number that can be set. The storage units 122A, 122B, and 122C of the link master devices 12A, 12B, and 12C each store the maximum number that can be set. The maximum number of link master devices 12A, 12B, and 12C that can be set depends on the capability (performance) of the link master device, and can be set by each link master device 12A, 12B, and 12C in a multi-vendor compatible fieldbus F. The maximum number may be different. In the following description, “4” is stored in the link master device 12A, “3” is stored in the link master device 12B, and “2” is stored in the link master device 12C, unless otherwise specified. Shall.

  When there are a plurality of link master devices 12A, 12B, and 12C in the segment 10, only one link master device is operating in the segment 10, but when the operation of the link master device is stopped for some reason, The system automatically switches to another waiting link master device, and continues execution of the schedule in the segment 10. For example, when the maximum number of link master devices 12A, 12B, and 12C that can be set is all “2”, when the active link master device 12A stops, the link master device 12B or the link master device 12C is switched to the schedule. Continue to execute.

  The schedule creation device 30 </ b> A includes a settable maximum number acquisition unit 37. The settable maximum number acquisition unit 37 acquires the settable maximum number from each link master device 12A, 12B, 12C via the fieldbus F and the controller 20. The settable maximum number acquisition unit 37 acquires the settable maximum number when, for example, a new link master device is connected (installed) to the segment 10.

  The setting unit 33 is based on the execution period of the control loop input via the input / output interface unit 31 and the minimum value among the plurality of settable maximum numbers acquired by the settable maximum number acquiring unit 37. Set multiple sub-schedules.

  In the above example, since the maximum settable number “2” stored in the link master device 12C is the minimum value, the setting unit 33 sets two sub-schedules. Thereby, the number of sub-schedules that can be set by all the link master devices 12A, 12B, and 12C in the segment 10 are set.

  The data load unit 36 transmits data including the schedule program 32c created by the schedule program creation unit 35 to each link master device 12A, 12B, 12C via the fieldbus F.

  Next, a schedule creation method and a schedule creation program will be described with reference to FIG. FIG. 15 is a flowchart for explaining the operation of the schedule creation device shown in FIG. Before executing the process S300 illustrated in FIG. 13, the schedule creation device 30A illustrated in FIG. 14 starts the process S400. That is, the settable maximum number acquisition unit 37 transmits an inquiry control signal of the maximum settable number to each link master device 12A, 12B, 12C via the fieldbus F and the controller 20, and each link master device 12A, 12B, The maximum number that can be set is acquired from 12C (S401).

  Next, the settable maximum number acquisition unit 37 receives the settable maximum number from each of the link master devices 12A, 12B, and 12C, and determines whether or not it has been acquired (S402). The settable maximum number acquisition unit 37 determines that the settable maximum number has been acquired when the settable maximum number has been received from all of the link master devices 12A, 12B, and 12C. If at least one of the settable maximum numbers is not received, it is determined that it has not been acquired.

  As a result of the determination in S402, when the settable maximum number has been acquired from each link master device 12A, 12B, 12C, the settable maximum number acquisition unit 37 can be set acquired from each link master device 12A, 12B, 12C. The minimum value of the maximum number is determined (S403), and the sub-schedule data 32b is written (updated) in the storage unit 32 with the minimum value set as the maximum settable number. After S403, the schedule creation device 30A ends the process S400. On the other hand, as a result of the determination in S402, when the settable maximum number has not been acquired from each link master device 12A, 12B, 12C, the settable maximum number acquisition unit 37 performs S401 again after a predetermined time has elapsed.

  After the process S400, in the process S300 shown in FIG. 13, the setting unit 33 reads the sub-schedule data 32b from the storage unit 32 in S301, and sets the sub-schedule period up to the maximum settable number determined in S403 in S302. . In S307, the data load unit 36 reads the macro cycle data 32a, the sub-schedule data 32b, and the schedule program 32c from the storage unit 32, and each link master device 12A, 12B, 12C via the controller 20 and the fieldbus F. Send (load) to.

  In the above-described example, in S401 and S402, the settable maximum number acquisition unit 37 sets the maximum settable number “4” from the link master device 12A and the settable maximum number “3” from the link master device 12B. The maximum configurable number “2” is acquired from 12C. In S403, the settable maximum number acquisition unit 37 sets “2” as the maximum settable number to the sub-schedule data 32b of the storage unit 32 because the maximum settable number “2” acquired from the link master device 12C is the minimum value. Write to (update). Next, the setting unit 33 sets two sub-schedules in S302. Thereby, the number of sub-schedules that can be set by all the link master devices 12A, 12B, and 12C in the segment 10 are set.

  In the present embodiment, the maximum settable number acquisition unit 37 acquires the maximum settable number from each of the link master devices 12A, 12B, and 12C. However, the present invention is not limited to this. For example, the settable maximum number of each link master device 12A, 12B, 12C is stored in another device connected to the fieldbus F, and the settable maximum number acquisition unit 37 stores each of the link master devices 12A, 12B, 12C stored in the device. The settable maximum number of link master devices 12A, 12B, and 12C may be acquired.

  As described above, according to the schedule creation device 30A in the present embodiment, when there are a plurality of link master devices 12A, 12B, and 12C in the segment 10 of the fieldbus F, each link master device 12A, A sub-schedule is set based on the settable maximum number acquisition unit 37 that acquires the settable maximum number of 12B and 12C, and the minimum value of the acquired settable maximum numbers of the link master devices 12A, 12B, and 12C. And a setting unit 33. Thereby, the number of sub-schedules that can be set by all the link master devices 12A, 12B, and 12C in the segment 10 are set. Accordingly, the schedule program 32c that can be executed by all the link master devices 12A, 12B, and 12C in the segment 10 can be transmitted to each link master device 12A, 12B, and 12C.

  Thus, according to the schedule creation method and schedule creation program in the present embodiment, when there are a plurality of link master devices 12A, 12B, 12C in the segment 10 of the fieldbus F, the settable maximum number acquisition unit 37 The step of acquiring the maximum settable number of each link master device 12A, 12B, 12C via the fieldbus F, and the setting unit 33 out of the acquired maximum settable number of each link master device 12A, 12B, 12C Setting a sub-schedule based on the minimum value of. Thereby, the number of sub-schedules that can be set by all the link master devices 12A, 12B, and 12C in the segment 10 are set. Accordingly, the schedule program 32c that can be executed by all the link master devices 12A, 12B, and 12C in the segment 10 can be transmitted to each link master device 12A, 12B, and 12C.

  Note that the configurations of the above-described embodiments may be combined or a part of the components may be replaced. The configuration of the present invention is not limited to the above-described embodiment, and various modifications may be made without departing from the scope of the present invention.

  DESCRIPTION OF SYMBOLS 10 ... Segment, 12, 12A, 12B, 12C ... Link master device, 30, 30A ... Schedule creation apparatus, 33 ... Setting part, 34 ... Execution data generation part, 36 ... Data load part, 37 ... Settable maximum prime acquisition part , 131 to 135 ... control loop, 200 ... schedule, 210 to 240 ... sub-schedule, F ... field bus

Claims (7)

A schedule creation device for creating a schedule for periodically executing a control loop constituted by a plurality of functional blocks of a fieldbus using a plurality of sub-schedules,
Execution for generating i execution data for executing the control loop in the sub-schedule when the sub-schedule having a period i times (i is an integer of 2 or more) the execution period of the control loop is set A data generator ;
A link master device that controls the operation timing of the control loop, and a transmission unit that transmits the schedule via the fieldbus,
The link master device has a settable maximum number that is the maximum number of subschedules that can be set,
When there are a plurality of link master devices in the fieldbus segment, a settable maximum number acquisition unit that acquires the settable maximum number of each link master device via the fieldbus;
A schedule creation apparatus , further comprising: a sub-schedule setting unit configured to set the sub-schedule based on a minimum value among the settable maximum numbers of the acquired link master devices . The schedule creation apparatus according to claim 1, wherein the execution data includes an offset time based on a start time of the sub-schedule. When a plurality of sub-schedules having a period i times the execution period of the control loop and different from each other are set, the execution data generation unit The schedule creation device according to claim 1, wherein i pieces of the execution data are generated in the sub-schedule having the shortest cycle. The control loop constituted by a plurality of functional blocks of the fieldbus, a scheduling method for creating a periodically scheduled to be executed using a plurality of sub-schedules,
Execution data that causes the execution data generation unit to execute the control loop in the sub-schedule when the sub-schedule having a period that is i times (i is an integer of 2 or more) the execution period of the control loop is set Generating i pieces ,
The link master device for controlling the operation timing of the control loop, the transmission unit transmits the schedule via the field bus,
The link master device has a settable maximum number that is the maximum number of subschedules that can be set,
When there are a plurality of link master devices in the fieldbus segment, a settable maximum number acquisition unit acquires the settable maximum number of each link master device via the fieldbus; and
A sub-schedule setting unit, further comprising: setting the sub-schedule based on a minimum value among the settable maximum numbers of the acquired link master devices . The schedule creation method according to claim 4 , wherein the execution data includes an offset time based on a start time of the sub-schedule. When the plurality of sub-schedules having a period that is i times the execution period of the control loop and different from each other are set, the generation step includes the execution data generation unit scheduling method according to claim 4 or 5, characterized in that the execution data to i number generated in the sub-schedule with the shortest period of the sub-schedule. 請 Motomeko 4 to schedule creation program including the steps of scheduling method according to any of the 6.

Images