JP5992776B2 - Programmable controller, program creation support device, program, and basic unit - Google Patents

Description

  The present invention relates to a programmable controller.

  A programmable controller (PLC) is known as a control device for comprehensively controlling various actuators installed in a factory or the like. In the PLC, a plurality of types of extension units can be connected to a basic unit that controls integrated control (for example, Patent Document 1). As the expansion unit, for example, an input / output unit that extends the number of input / output points, a communication unit that adds a communication function, a sensor unit that processes a sensor signal, and the like are known.

  When executing a control program such as a ladder program, the basic unit recognizes the extension unit that is actually connected, and identifies the correspondence with the extension unit defined in the control program. become.

JP 2011-28563 A

  Here, when developing a control program for a plurality of types of systems having basically the same unit configuration, the development efficiency may be improved by diverting the control program between systems.

  For example, for a unit configuration that is assumed in the future, a unit configuration that does not use some of the extension units at this time is adopted, and the same processing is executed for other extension units other than some extension units. Is the case. In this example, if a control program is created on the assumption of a future unit configuration, this control program may be diverted to the current unit configuration.

  However, because the future system configuration is partly different from the current system configuration, the control program that assumes the future unit configuration is the same as the extension unit that is defined in the control program and the extension unit that is actually connected. Can't be executed due to a flaw in the correspondence.

  Therefore, it can be considered that the identification information on the control program is corrected and then diverted. However, it takes time and the effect of improving the development efficiency by diverting the control program is diminished.

  An object of the present invention is to reduce the trouble of correcting identification information on a control program and to improve development efficiency when diverting a control program between different unit configurations.

According to the present invention, the basic unit and the setting for the plurality of extension units transmitted from the program creation support apparatus connected to the outside have a basic unit and a plurality of extension units connected to the basic unit. In a programmable controller that acquires information and operates based on the acquired setting information,
Created by the program creation support apparatus, the setting information sent to the programmable controller,
Identification information having order for identifying each of the plurality of extension units , and a control program in which processing for the extension unit identified by the identification information is described;
A unit configuration indicating a type of each of the plurality of extension units assumed to be connected to the basic unit , and a connection order of each of the plurality of extension units to the basic unit ;
From among the plurality of expansion units contained in the unit configuration, the specifying information connection to the basic unit to specify the connection undetermined expansion unit is unconfirmed,
Is included,
Setting information acquisition means for acquiring the setting information from the program creation support device;
A specifying means for specifying a type of each of the plurality of extension units actually connected to the basic unit in the programmable controller, and a connection order of each of the plurality of extension units to the basic unit ;
The types of the plurality of extension units specified by the specifying unit and the types of the plurality of extension units in the unit configuration included in the setting information acquired by the setting information acquisition unit are arranged in the order of connection to the basic unit. For the unconfirmed connection extension unit specified in the specification information included in the setting information, in addition to the type of the connection unconfirmed extension unit, the unit configuration included in the setting information Collation means for collating the types of the next expansion units along the connection order ;
Based on the collation result of the collation means, when the extension unit corresponding to the unconfirmed connection extension unit is not actually connected to the basic unit in the programmable controller, identification information to be assigned to the extension unit is omitted. In the above, a plurality of extensions specified by the specifying means so that the next identification information of the identification information that has been numbered is assigned to the next extension unit of the extension unit in the order of connection to the basic unit. Assigning means for assigning said identification information to each of the units;
Control means for executing the control program so that a specific instruction corresponding to the identification information skipped by the assigning means is excluded from processing targets ;
The programmable controller is provided, characterized in that it comprises a.

  ADVANTAGE OF THE INVENTION According to this invention, when diverting a control program between different unit structures, the effort of correction of the identification information on a control program can be reduced, and development efficiency can be improved.

The external view of the basic unit which concerns on one Embodiment of this invention. The block diagram of the basic unit of FIG. 1, an expansion unit, and a support apparatus. (A) is a flowchart showing a processing example of the support device, (B) and (C) are flowcharts showing a processing example of the basic unit. (A) is a figure which shows the example of a setting screen in a assistance apparatus, (B) is a figure which shows the example of unit setting information. The figure which shows the example of an edit screen in a assistance apparatus. Explanatory drawing of allocation of identification information. Explanatory drawing of allocation of identification information. Explanatory drawing of allocation of identification information. Explanatory drawing of allocation of identification information. The flowchart which shows the process example of a basic unit. The figure which shows the example of a definition of a control relay.

<Configuration example>
FIG. 1 is an external view of a basic unit 100 according to an embodiment of the present invention. In the case of this embodiment, the basic unit 100 constitutes a CPU unit, and the terminal block 1 is provided on the top of the housing. The terminal block 1 includes a plurality of output terminals and a plurality of input terminals. An output device can be connected to the output terminal, and an input device can be connected to the input terminal. Output devices include actuators such as relays, solenoids, and motors, or actuator drivers. The input device includes a sensor or a signal processing circuit of the sensor.

  The connection unit 2 is an expansion bus for connecting an expansion unit (not shown). In FIG. 1, the connection part 2 is covered with a cover member 2a for protecting terminals, and is exposed by removing the cover member 2a. An extension unit can be further connected to the extension unit, and the connection unit 2 can connect a plurality of extension units in series. In this way, a PLC including the basic unit 100 and a plurality of extension units can be constructed. In the present embodiment, a plurality of extension units are connected in series. However, for example, they may be connected in parallel, or the extension units may be connected in a star shape with the basic unit 100 as the center. Well, the connection form is not questioned.

  A display unit 3, an operation unit 4, and a connection unit 5 are provided on the front surface of the base unit 100. The display unit 3 can display various information such as device information. The operation unit 4 is composed of a plurality of buttons, and a user's instruction such as switching display contents on the display unit 3 can be manually input to the basic unit 100. A communication cable that enables wired communication between the basic unit 100 and an external device is connected to the connection unit 5. In addition, an error notification LED or the like may be provided.

  FIG. 2 is a block diagram of the basic unit 100, a program creation support apparatus 200 (hereinafter referred to as support apparatus 200) as an external device, and an expansion unit 300. The support device 200 is, for example, a personal computer, and a creation support program that supports creation of a control program by the user is installed.

  The support device 200 includes a control unit 50. The control unit 50 includes a CPU 51, a storage unit 52, and an IF (interface) unit 53. The storage unit 52 is, for example, a ROM, a RAM, or a hard disk, and the above creation support program can be stored in the storage unit 52. The IF unit 53 includes, for example, a display unit 60, an I / O interface for the operation unit 61, and a communication interface for communication with the basic unit 100. The display unit 60 displays information to the user. The operation unit 61 is, for example, a keyboard or a mouse.

  The basic unit 100 includes a control unit 10, a storage unit 20, and an ASIC 30. The control unit 10 is a general-purpose one-chip microcomputer, for example, and includes a CPU 11, a storage unit 12, and an IF unit 13. The storage unit 12 is, for example, a ROM or a RAM. The IF unit 13 includes, for example, a display unit 3, an I / O interface for the operation unit 4, and a communication interface for communication with the support apparatus 200.

  In the present embodiment, the storage unit 20 includes a flash ROM 21 and an SDRAM (Synchronous Dynamic RAM) 22, but may be another type of memory or a single memory. The flash ROM 21 stores, for example, a control program (intermediate code) downloaded from the support device 200 and setting information including various setting information described later, or a program for each processing described later. A program for compiling intermediate code can also be stored. For example, an execution format control program is stored in the SDRAM 22. The storage unit 20 can also be used as a device, but by using the storage unit 12 as a device, the device information read / write time can be shortened.

  During the control operation, the CPU 11 reads out and executes the execution type control program stored in the SDRAM 22. For example, the CPU 11 acquires information from the input terminal and updates device information indicating an input state from the input device (input refresh). Thereafter, while executing one scan of the control program, the device information (device information indicating the output state to the output device) in the storage unit 12 is updated therein. In the updated device information, the device information for the output device connected through the output terminal is output from the output terminal (output refresh). Control is executed by repeating these processes. The ASIC 30 is a circuit specialized for communication processing with the expansion unit 300 via the connection unit 2.

  Each expansion unit 300 includes an ASIC 301 and connection units 302 and 303, and further includes a circuit (not shown) corresponding to the function of the expansion unit. The ASIC 301 is a circuit specialized for communication processing with the basic unit 100 or another extension unit 300 via the connection units 302 and 303. The connection unit 302 is an expansion bus connected to the basic unit 100 or another expansion unit 300, and the connection unit 303 is an expansion bus connected to the connection unit 302 of the other expansion unit 300.

  As shown in FIG. 2, the connection unit 2 of the basic unit 100 and the connection unit 302 of the extension unit 100 are connected, and the connection unit 303 is connected to the connection unit 302 of another extension unit 100 to sequentially expand. By connecting the units 100, a plurality of extension units 100 can be connected in series to the connection portion 2 of the basic unit 100.

<Processing example>
Next, a processing example executed by the CPU 11 of the basic unit 100 and a processing example executed by the CPU 51 of the support apparatus 200 will be described. First, a processing example of the support device 200 will be described.

<Example of support device processing>
FIG. 3A is a flowchart illustrating a processing example of the support device 200. In this embodiment, as a premise for creating a control program, first, a unit configuration is set. In S <b> 1, the unit configuration is set based on a user operation on the operation unit 61. The unit configuration setting is a setting related to the basic unit 100 and the expansion unit (also referred to as an assumed expansion unit) 300 assumed in the control program, and the connection mode setting of the assumed expansion unit to the basic unit 100 and each assumed expansion. For example, individual unit settings. Details will be described later.

  In S <b> 2, the control program is edited based on a user operation on the operation unit 61. Here, the creation of a ladder diagram by the user is supported and accepted. One example will be described later.

  In S3, in accordance with a user instruction to the operation unit 61, the unit configuration information set in S1 and the setting information (also referred to as project data) including the control program (intermediate code) edited in S2 are transmitted to the basic unit 100. This project data is stored in the flash ROM 21 of the basic unit 100. In this way, the basic unit 100 acquires the setting information.

<Unit configuration settings>
The setting of the unit configuration in S1 will be described with reference to FIG. FIG. 4A shows a display example of the display unit 60. The configuration display unit 70 displays the unit configuration currently selected by the user. In the example of the figure, a provisional PLC configuration including the basic unit 100, five assumed expansion units 300 selected by the user, and end units is displayed. In the present embodiment, the end unit is provided, but it is of course possible to omit it.

  The five assumed extension units 300 include four kinds of assumed extension units. For convenience of explanation, the types of extension units are indicated by AD. That is, there are two assumed expansion units B, and each of the other assumed expansion units A, C, and D is one. The type can be distinguished by, for example, the type of the extension unit as a unit. Although not particularly shown, the user can select the basic unit 100 as well. The end unit is a unit for specifying the end of the PLC, and is connected to the extension unit located at the end.

  In the unit selection display unit 73, the types of assumed expansion units 300 that can be selected by the user are displayed classified by function. For example, in the example shown in the figure, the display is divided into functions such as an I / O unit and an analog unit. When the user selects a desired extension unit and operates the add button 74 or drags it to the configuration display unit 70, the user is added to the PLC displayed on the configuration display unit 70.

  In the identification information display unit 71, identification information of each assumed expansion unit 300 is displayed. The identification information is information for identifying each expansion unit on the control program. In the case of this embodiment, the identification information is automatically assigned according to an assignment rule defined by the order of connection to the basic unit 100. This method has an advantage that the expansion unit can be identified relatively easily. In the example shown in the figure, from the basic unit 100 side, # 1, # 2,. . . The identification information is assigned by the number, but other than the number (for example, a, b, c, etc.) may be used as long as the connection order is followed. The basic unit 100 is assigned # 0 for convenience.

  For example, the user can change the connection order of the assumed expansion units 300 by selecting the displayed expected expansion unit 300 and performing a drag operation. In this case, the identification information is renumbered. Further, when the user selects the assumed expansion unit 300 displayed on the configuration display unit 70 and operates the cancel button 75, the assumed expansion unit 300 can be deleted from the PLC displayed on the configuration display unit 70. In this case, the identification information is renumbered.

  The reservation display unit 72 indicates whether connection reservation is selected for each assumed expansion unit 300. In the example of the figure, connection reservation is selected for the assumed expansion unit A # 1. In the connection reservation, the user declares that there is a possibility that the connection is not actually made. That is, the user declares that the extension unit is not yet connected to the basic unit. The user can select the assumed expansion unit 300 displayed on the configuration display unit 70 and operate the connection reservation button 76 to specify a connection unconfirmed expansion unit that is a connection reservation target. A connection reservation is accepted for the unit 300.

  This connection reservation function is intended to facilitate the diversion of the control program. For example, this connection reservation is made for the extension unit 300 that is included in the future unit configuration but is not included in the currently assumed PLC. Then, if a control program that assumes a future unit configuration is created, it becomes easy to divert that control program to the PLC that is currently assumed. Details will be described later.

  Next, when the user selects the assumed expansion unit 300 displayed on the configuration display unit 70 and operates the individual setting button 77, a screen for individually setting the assumed expansion unit is displayed (not shown). Detailed settings can be made. For example, in the case of an analog unit, the detailed settings include the range and the like, and are necessary settings when the expansion unit 300 actually operates.

  When the user operates the setting button 78, the unit configuration setting is confirmed and unit setting information is created. The unit setting information indicates contents set by the user in the setting of the unit configuration in S1, and includes at least unit setting information D1 shown in FIG.

  The unit setting information D1 shown in FIG. 4B shows the connection mode of the assumed expansion unit to the basic unit 100, which is assumed in the control program to be created by the user, and includes order information, type, and connection reservation information. . The order information indicates the order of connection of each assumed expansion unit 300 to the basic unit 100. In this embodiment, since the identification information indicates the connection order of the assumed expansion unit 300, this is used as the order information. However, any information can be used as long as the connection order can be specified. Good. In the example of FIG. 4B, it is assumed that the setting content is confirmed with the configuration example of the PLC of FIG. In this embodiment, the identification information is used as the order information. In short, any identification information that can identify each unit may be used.

  From the unit setting information D1 in FIG. 4B, five extension units 300 are connected to the basic unit 100, and the types are A, B, B, C, and D in order from the basic unit 100 side. It can be recognized. Also, from the connection reservation information, it is possible to recognize that the connection reservation is set for the extension unit A # 1 as an unconfirmed connection extension unit. This unit setting information D1 is stored in the storage unit 52 and transmitted to the basic unit 100 together with the control program in the transmission process of S3. In the basic unit 100, the received unit setting information D1 can be stored in the flash ROM 21 or the storage unit 12.

<Edit control program>
An example of editing the control program in S2 will be described with reference to FIG. FIG. 5 shows a display example of the display unit 60. In the editing area 80, a ladder diagram is displayed based on a user operation. At this time, the processing related to the assumed expansion unit 300 is specified and described by the identification information. The ladder diagram 80a of the figure illustrates the processing of the # 1 assumed expansion unit A. The function button group 81 is a function button group that simplifies the creation of a ladder diagram by the user. For example, symbols of a standard ladder diagram can be drawn by a button operation.

  As shown in FIG. 5, it can be said that the process of the assumed expansion unit A is a specific command based on the identification information (# 1) for identifying the assumed expansion unit. The actual ladder program has a wide range from hundreds to thousands of lines, and this specific instruction is scattered everywhere. Conventionally, when the assumed expansion unit A is connected to the basic unit 100, for example, in order to describe the processing of the assumed expansion unit C, it has been necessary to describe using the identification information (# 4).

  On the other hand, when the assumed expansion unit A is not connected to the basic unit 100, in order from the basic unit 100, the assumed expansion unit B is # 1, the assumed expansion unit B is # 2, the assumed expansion unit C is # 3, and the assumed expansion Since each unit number of # 4 is assigned to the unit D, for example, in order to describe the processing of the extension unit C, it is necessary to describe using the identification information (# 3). This means that the user must store two types of control programs, assuming that the expansion unit A is connected to the basic unit and not, that is, do double management. It took a lot of work. In order to avoid double management, it was necessary to rewrite the unit number of the control program in each case, and in some cases, it was necessary to correct dozens of places, which was very laborious.

  The basic unit 100 according to the present embodiment is useful as a device that saves such trouble. In the present embodiment, “unit number” is used as an example of identification information, but various other forms such as a relay number associated with a unit number are possible.

  When the ladder diagram is completed, the support apparatus 200 converts the ladder diagram into an intermediate code (for example, a mnemonic code) according to a user instruction. The intermediate code is stored in the storage unit 52 and transmitted to the basic unit 100 together with the unit setting information in the transmission process of S3. In the basic unit 100, the received intermediate code can be stored in the flash ROM 21.

<Example of basic unit processing>
Next, a processing example of the basic unit 100 will be described. First, a process in which the basic unit 100 recognizes the extension unit 300 connected thereto, collates it with the unit setting information, and assigns identification information will be described with reference to FIG. FIG. 3B is a flowchart showing the collation / allocation process, which is executed when the basic unit 100 is turned on or when the project data is updated.

  In S11, processing for specifying the actual unit configuration is performed. Here, the actual expansion unit 300 that is the expansion unit 300 actually connected to the connection unit 2 is specified by communication with the expansion unit 300 via the connection unit 2. In the case of the present embodiment, the specific contents include the type of the actual extension unit 300 and the order of connection to the basic unit 100. As long as these can be specified, any communication method may be used. For example, there is a method of acquiring the type of the actual expansion unit 300 sequentially from the actual expansion unit 300 on the basic unit 100 side to the actual expansion unit 300 at the end on the end unit side.

  That is, the basic unit 100 sends a connection confirmation command to the adjacent assumed expansion unit 300, and sets the assumed expansion unit 300 to unit number # 1 based on the response. The basic unit 100 sends a connection confirmation command to the assumed extension unit 300 adjacent to the unit number # 1, and sets the assumed extension unit 300 to the unit number # 2 based on the response. By repeating this, unit numbers can be assigned to all assumed expansion units 300. On the other hand, the actual extension unit 300 may notify the basic unit 300 of its type and connection position.

  In S12, the unit setting information D1 and the actual unit configuration specified in S11 are collated in S12. Specific examples will be described later. If the verification is established, the process proceeds to S13, and if not, the process proceeds to S14. In S13, identification information is assigned to each real extension unit 300 recognized in S11. The identification information and the corresponding type of the actual expansion unit 300 are stored in the SDRAM 22 or the storage unit 12 as actual unit configuration setting information (hereinafter also referred to as actual unit setting information).

  This identification information is for distinguishing the actual expansion unit 300 in executing the control program, and is assigned according to the same assignment rule as the unit configuration setting described with reference to FIG. Basic. The allocation rule is not limited to the rule described in the present embodiment, and various methods can be adopted.

  In S14, error processing is performed. Here, for example, the identification information is not assigned to the actual expansion unit 300, and the fact that the assignment of the identification information has failed is notified by display on the display unit 3. Thus, one unit of processing is completed.

<Example of assignment>
Next, specific examples of collation in S12 and allocation in S13 will be described with reference to FIGS. First, the example of FIG. 6 will be described.

  In FIG. 6, the actual connection information D2 is a result of specifying the actual unit configuration in S11. In the example of FIG. 6, the actual connection information D2 indicates that four actual expansion units 300 are connected, and the types are B, B, C, and D in order from the basic unit 100 side. The unit setting information D1 downloaded from the support apparatus 200 is the same as that illustrated in FIG.

  In the collation in S12, for example, first, the type of the first extension unit 300 is compared in the order of connection. Then, since the type is B in the actual connection information D2 and A in the unit setting information D1, the two do not match. However, in the unit setting information D1, a connection reservation is set for the first extension unit A in the order of connection, and there is a possibility that the unit is not actually connected. Therefore, it is compared with the second extension unit 300 of the unit setting information D1. Then, the type of the extension unit 300 is B, which matches the type of the first extension unit 300 in the actual connection information D2.

  Subsequently, when the types of the second to fourth expansion units 300 in the actual connection information D2 and the types of the third to fifth expansion units 300 in the unit setting information D1 are sequentially compared, they all match.

  Therefore, it is determined that the verification has been established, and the allocation result is information D3. That is, since the connection of the assumed expansion unit A that is the unconfirmed connection expansion unit specified by the connection reservation information has not been confirmed from the actual connection information D2, the order corresponding to the connection order of the assumed expansion unit A (No. 1 ) Are applied in the order of skipping (No. 2). As a result, identification information # 2, # 3, # 4, and # 5 are assigned to each real extension unit B, B, C, and D, respectively. Thereby, it is possible to prevent wrinkles from occurring in the assignment of identification information. As a result, even if the control program is diverted, rewriting becomes unnecessary and development efficiency can be improved.

  Note that the method described with reference to FIG. 6 is an example. In addition, for example, based on the actual connection information D2, first, # 1, # 2, # 3, and # 4 are assigned as temporary identification information. Then, based on the assumption that the assumed extension unit A is the assumed extension unit specified by the connection reservation information, # 1 is a missing number, and # 2, # 3, # 4, and # 5 are reassigned. As a result, a result similar to the allocation result information D3 is obtained.

  Next, the example of FIG. 7 will be described. In FIG. 7, the actual connection information D2 indicates that five actual expansion units 300 are connected, and the types are A, B, B, C, and D in order from the basic unit 100 side. The unit setting information D1 is the same as that illustrated in FIG.

  As in the case of the example of FIG. 6, first, the types of the first extension units 300 are compared in the order of connection. Then, since the type is A in the actual connection information D2 and A in the unit setting information D1, the two match. However, in the unit setting information D1, a connection reservation is set for the first extension unit A in the order of connection, and there is a possibility that the unit is not actually connected. Therefore, it is compared with the second extension unit 300 of the unit setting information D1. Then, the type of the extension unit 300 is B, which does not match the type of the first extension unit 300 in the actual connection information D2. Therefore, in this case, it can be determined that the extension unit A that has been reserved for connection is actually connected.

  Subsequently, when the types of the second to fifth extension units 300 in the actual connection information D2 are sequentially compared with the types of the second to fifth extension units 300 in the unit setting information D1, they all match.

  Therefore, it is determined that the verification has been established, and the allocation result is information D3. That is, in the example of FIG. 7, since the connection of the assumed expansion unit A, which is the unconfirmed connection extension unit specified by the connection reservation information, has been confirmed from the actual connection information D2, the allocation rules are applied in the same order. As a result, identification information # 1, # 2, # 3, # 4, and # 5 are assigned to each real extension unit A, B, B, C, and D, respectively. Thereby, it is possible to prevent wrinkles from occurring in the assignment of identification information.

  Here, the example of FIG. 6 and the example of FIG. 7 differ only in the presence or absence of the expansion unit A, and the types of the remaining expansion units B, B, C, and D are the same. Therefore, if a connection program is set and a control program is created on the assumption that the expansion unit A exists, this control program can be used even when the expansion unit A does not actually exist (in the example of FIG. 6). Can be diverted. At that time, it is not necessary to correct the identification information of the expansion unit. As described above, in the present embodiment, it is possible to prevent the occurrence of wrinkles in assignment of identification information when diverting a control program between different unit configurations.

  In addition, in this embodiment, the programmable controller which can divert a control program simply can be implement | achieved by devising allocation of a unit number (an example of identification information) in this way. For example, the present invention can be applied even if the identification information is other than numbers such as a, b, and c. For example, in FIG. 6, when it is assumed that the order information of the unit setting information D1 is a, b, c, d, e in order from the left and the assumed extension unit specified by the connection reservation information is A, When the allocation process is performed based on the above, b, c, d, and e are allocated in order from the left without a being allocated. As a result, when executing the control program, it is not necessary to rewrite the identification information of b to e described in the control program (if a, b, c, d are assigned in order from the left, the identification information is Must be rewritten).

  However, since the description of the identification information a remains in the control program, the basic unit 100 executes the control program so that the specific command based on the identification information a is excluded from the processing target. For example, a specific command based on the identification information a may be skipped (ignored or omitted), or a specific command based on the identification information a may be invalidated in advance. In addition, the CPU 11 of the basic unit 100 may not output the execution result to the expansion unit even if a specific instruction based on the identification information a is executed. Alternatively, the CPU 11 of the basic unit 100 may A specific instruction based on a is executed and an execution result is output to the actual extension unit 300, but this output is blocked in the ASIC 30 so that the actual extension unit 300 does not substantially receive the execution result. Also good.

  Thus, the basic unit 100 according to the present embodiment, based on the collation result, when there is no assumed extension unit A specified by the connection reservation information, the identification information for identifying the assumed extension unit in the control program ( In the above-described example, the specific command based on # 1 and a) operates so as to be excluded from the processing target.

  Next, the example of FIG. 8 will be described. In FIG. 8, the actual connection information D2 indicates that four actual extension units 300 are connected, and the types are C, B, C, and D in order from the basic unit 100 side. The unit setting information D1 is the same as that illustrated in FIG.

  As in the case of the examples of FIGS. 6 and 7, first, the types of the first extension units 300 are compared in the order of connection. Then, since the type is A in the actual connection information D2 and C in the unit setting information D1, the two do not match. However, in the unit setting information D1, a connection reservation is set for the first extension unit A in the order of connection, and there is a possibility that the unit is not actually connected.

  Therefore, it is compared with the second extension unit 300 of the unit setting information D1. Then, the type of the extension unit 300 is B, which does not match the type of the first extension unit 300 in the actual connection information D2. Therefore, in this case, the unit configuration is not assumed in the unit setting information D1, and an error is assumed that the control program cannot be executed (S14 in FIG. 3B).

  By checking the type of the extension unit 300 in this way, it is possible to detect a connection error of the extension unit 300 or that a control program or unit setting information has been downloaded by mistake to another system.

  Next, the example of FIG. 9 will be described. In FIG. 9, the actual connection information D2 indicates that four actual expansion units 300 are connected, and the types are A, B, C, and D in order from the basic unit 100 side. The unit setting information D1 is different from that illustrated in FIG. 4B only in connection reservation information, and the # 2 assumed expansion unit B is a connection reservation target.

  As in the example of FIGS. 6 to 8, first, the types of the first extension units 300 are compared in the order of connection. Then, since the type is A in the actual connection information D2, and the unit setting information D1 is also A, the two match.

  Next, the types of the second extension units 300 are compared in the order of connection. Then, since the type is B in the actual connection information D2, and the unit setting information D1 is also B, the two match. However, in the unit setting information D1, a connection reservation is set for the second assumed expansion unit B in the connection order, and there is a possibility that the unit is not actually connected.

  Therefore, it is compared with the third assumed expansion unit 300 of the unit setting information D1. Then, the type is B, which matches the type of the second real extension unit 300 in the real connection information D2. In this case, it is determined that the extension unit B that has been reserved for connection is not actually connected.

  Subsequently, when the types of the third to fourth expansion units 300 in the actual connection information D2 and the types of the fourth to fifth expansion units 300 in the unit setting information D1 are sequentially compared, they all match.

  Therefore, it is determined that the verification has been established, and the allocation result is information D3. That is, since the connection of the # 2 assumed expansion unit B specified by the connection reservation information has not been confirmed from the actual connection information D2, the order corresponding to the connection order of the # 2 assumed expansion unit B (No. 2) The allocation rules are applied in the order of skipping (No. 1, No. 3). As a result, identification information # 1, # 3, # 4, and # 5 are assigned to each real extension unit A, B, C, and D, respectively. Thereby, it is possible to prevent wrinkles from occurring in the assignment of identification information.

<Processing of expansion units reserved for connection>
When the assumed expansion unit 300 that is a connection unconfirmed expansion unit that has been reserved for connection is not actually connected, the control program is executed normally by excluding the instruction related to the expansion unit 300 from the processing target as described above. it can.

  Therefore, when executing the control program, it is possible to branch the processing by referring to the actual unit setting information and confirming whether or not an unconfirmed connection extension unit actually exists. This process can be set, for example, when compiling the intermediate code of the control program.

  FIG. 3C shows an example of conversion processing in which the basic unit 100 converts the intermediate code of the control program into an executable code. This conversion can be performed by the CPU 11 executing the compiler stored in the flash ROM 21 after setting the actual unit setting information, and the code of the execution format control program is stored in the SDRAM 22 as described above. be able to.

  In S21, an intermediate code for one unit is read, and in S22, this is converted into an executable code. At this time, for the processing related to the extension unit 300, a process for determining whether the extension unit 300 exists (executable) is incorporated based on the actual unit setting information. Time processing). The target expansion unit 300 is at least a connection unconfirmed expansion unit that is a target of connection reservation, but in this embodiment, all the expansion units 300 are targeted.

  In S23, it is determined whether conversion has been completed for all intermediate codes. If not, the process returns to S21 and the same processing is repeated.

  Next, processing in the case where the basic unit 100 executes the control program thus converted into the executable code will be described with reference to FIG.

  In S31, an instruction word is acquired from the control program. In S32, it is determined based on the actual unit setting information whether or not the extension unit 300 specified by the operand of the instruction word in S31 actually exists. This process is incorporated in the process of S22 described above. If the expansion unit 300 exists, the process proceeds to S33 to execute the instruction word processing. That is, this command word operates without being excluded from the processing target. If it does not exist, the process proceeds to S34, and the process when not confirmed is performed.

  In S34, the instruction word is not executed and the process proceeds to S35. That is, it operates so that this instruction word is excluded from the processing target. As described above, even if the instruction word is executed, it is sufficient if the execution result is not transmitted to the expansion unit 300. In that case, you may alert | report that the process of the expansion unit 300 which does not actually exist was not performed. The notification may be, for example, display by the display unit 3, or may be notification by an error LED or an error relay. By performing the notification, the presence or absence of the extension unit 300 can be recognized, and the user can be made aware that the control program is being executed based on the recognition result.

  In S35, it is determined whether or not processing of all instruction words in the control program has been completed. If not, the process returns to S31 to process the next instruction word, and if applicable, ends one unit of processing (one scan). To do.

  In this example, an executable judgment is incorporated at the time of compilation. However, when creating a ladder diagram, it is allowed to define a process on the condition that the extension unit 300 is actually connected in the grammar of the program. It may be.

  For example, in the example of FIG. 11, a control relay CR that determines whether or not the assumed extension unit # 1 actually exists is added to the ladder diagram 80a illustrated in FIG. Is defined so that subsequent processing is executed on the condition that it actually exists. Also in this case, the target of the control relay CR need not be limited to the expansion unit that is the target of the connection reservation.

  By enabling such programming, it is possible to make an executable determination as intended by the user.

  In the present embodiment, when the expansion unit 300 is not actually connected, the control program process related to the expansion unit 300 is not executed. For example, the control program process is executed, but the output is not performed. It is also possible to adopt a measure not to output data to the expansion unit 300 in the refresh.

Claims (8)

It has a basic unit and a plurality of extension units connected to the basic unit, and acquires and acquires setting information for the basic unit and the plurality of extension units transmitted from the program creation support apparatus connected to the outside In the programmable controller that operates based on the set information,
Created by the program creation support apparatus, the setting information sent to the programmable controller,
Identification information having order for identifying each of the plurality of extension units , and a control program in which processing for the extension unit identified by the identification information is described;
A unit configuration indicating a type of each of the plurality of extension units assumed to be connected to the basic unit , and a connection order of each of the plurality of extension units to the basic unit ;
From among the plurality of expansion units contained in the unit configuration, the specifying information connection to the basic unit to specify the connection undetermined expansion unit is unconfirmed,
Is included,
Setting information acquisition means for acquiring the setting information from the program creation support device;
A specifying means for specifying a type of each of the plurality of extension units actually connected to the basic unit in the programmable controller, and a connection order of each of the plurality of extension units to the basic unit ;
The types of the plurality of extension units specified by the specifying unit and the types of the plurality of extension units in the unit configuration included in the setting information acquired by the setting information acquisition unit are arranged in the order of connection to the basic unit. For the unconfirmed connection extension unit specified in the specification information included in the setting information, in addition to the type of the connection unconfirmed extension unit, the unit configuration included in the setting information Collation means for collating the types of the next expansion units along the connection order ;
Identification information to be assigned to the extension unit when it is determined that the extension unit corresponding to the unconfirmed connection extension unit is not actually connected to the basic unit in the programmable controller based on the check result of the check means Is specified by the specifying means so that the identification information next to the identification information assigned to the extension unit is assigned to the next extension unit of the extension unit in the order of connection to the basic unit. Assigning means for assigning the identification information to each of the plurality of extension units;
Control means for executing the control program so that a specific instruction corresponding to the identification information skipped by the assigning means is excluded from processing targets ;
Programmable controller, characterized in that it comprises a. Said assigning means, based on the collation result of the collating means, when said expansion unit corresponding to the connection undetermined expansion unit in the programmable controller is actually connected to the base unit, including the extension unit The programmable controller according to claim 1, wherein the identification information is assigned to each of a plurality of expansion units specified by the specifying unit . Provided with an informing means for informing that the specific command was excluded from processing and operated.
The programmable controller according to claim 1 or 2 characterized by things. Conversion means for converting the intermediate code of the control program into an executable code including processing for determining whether or not the connection unconfirmed extension unit actually exists for processing related to the connection unconfirmed expansion unit The
The programmable controller according to any one of claims 1 to 3 . A program creation support device connectable to the basic unit of the programmable controller according to claim 1,
Designation accepting means for accepting designation by the user of the extension unit that is the target of the unconfirmed extension unit;
Means for transmitting the setting information including information indicating the unconfirmed connection extension unit received by the designation receiving means to the basic unit;
A program creation support apparatus characterized by comprising: An editing means for editing the control program based on a user operation,
The editing means includes
Allows definition of processing on condition that the unconfirmed extension unit is actually connected to the basic unit;
The program creation support apparatus according to claim 5 . A program creation support device connectable to the basic unit of the programmable controller according to claim 1,
Designation accepting means for accepting designation by the user of the extension unit that is the target of the unconfirmed extension unit;
Means for transmitting the setting information including information indicating the unconfirmed extension unit received by the designation receiving means to the basic unit;
Program to function as. It has a basic unit and a plurality of extension units connected to the basic unit, and acquires and acquires setting information for the basic unit and the plurality of extension units transmitted from the program creation support apparatus connected to the outside A basic unit in a programmable controller that operates based on the set information ,
Created by the program creation supporting device, the Setting Information sent to the programmable controller,
Identification information having order for identifying each of the plurality of extension units , and a control program in which processing for the extension unit identified by the identification information is described;
A unit configuration indicating a unit configuration indicating a type of each of the plurality of extension units assumed to be connected to the basic unit , and a connection order of each of the plurality of extension units to the basic unit ;
From among the plurality of expansion units contained in the unit configuration, the specifying information connection to the basic unit to specify the connection undetermined expansion unit is unconfirmed,
Is included,
Setting information acquisition means for acquiring the setting information from the program creation support device;
A specifying means for specifying a type of each of the plurality of extension units actually connected to the basic unit in the programmable controller, and a connection order of each of the plurality of extension units to the basic unit ;
The types of the plurality of extension units specified by the specifying unit and the types of the plurality of extension units in the unit configuration included in the setting information acquired by the setting information acquisition unit are arranged in the order of connection to the basic unit. For the unconfirmed connection extension unit specified in the specification information included in the setting information, in addition to the type of the connection unconfirmed extension unit, the unit configuration included in the setting information Collation means for collating the types of the next expansion units along the connection order ;
With
Identification information to be assigned to the extension unit when it is determined that the extension unit corresponding to the unconfirmed connection extension unit is not actually connected to the basic unit in the programmable controller based on the check result of the check means Is specified by the specifying means so that the identification information next to the identification information assigned to the extension unit is assigned to the next extension unit of the extension unit in the order of connection to the basic unit. Assigning means for assigning the identification information to each of the plurality of extension units;
Control means for executing the control program so that a specific instruction corresponding to the identification information skipped by the assigning means is excluded from processing targets ;
Basic unit, characterized in that it comprises a.

Images