JP2005038063A - Programmable controller system, support tool, and unit for programmable controller and method for securing connection - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To connect a new version PLC(programmable logic controller) to an existing old version support tool when it is substantially operated as an old version PLC by using an old version user program or the like. <P>SOLUTION: In this system equipped with a PLC 20 and a support tool 10 connected to the PLC, the PLC(CPU unit 22) is made to store and hold application version information showing the functions of a stored user program. A support tool acquires at least application information stored and held in the PLC, and the PLC decides whether or not it can cope with the version on the basis of the acquired application version information. Thus, when the stored user program is made to correspond to the old version even in the case of the new version PLC, it is possible to secure the connection of the old version support tool to the new version PLC. <P>COPYRIGHT: (C)2005,JPO&NCIPI

Description

[0001]
BACKGROUND OF THE INVENTION
The present invention relates to a programmable controller system and a support tool, a programmable controller unit, and a connection guarantee method.
[0002]
[Prior art]
The PLC (programmable logic controller) that controls the FA (factory automation) system installed at the production factory (manufacturing site) takes the signal input from the input unit into the I / O memory of the CPU unit (IN refresh), Performs logical operation based on a user program written in the registered ladder language (operation execution), writes the operation execution result to the I / O memory, sends it to the output unit (OUT refresh), and then performs so-called peripheral service processing To do it cyclically and repeatedly.
[0003]
The user program is downloaded via a support tool connected to the PLC and stored in a user memory of the PLC (CPU unit). When modifying a user program stored in the PLC, connect the support tool to the PLC, upload the user program stored in the PLC, make necessary modifications, and then modify the new program. The user program is downloaded again to the PLC. The support tool is realized by a personal computer or a dedicated peripheral device.
[0004]
By the way, there are various versions of PLC such as development of new models with new functions and improvement of specifications as well as enhancement of functions of on-board software, as production methods become more advanced, diversified, and technology advances. Up. This version upgrade improves processing speed, adds functions, etc., but basically has compatibility with conventional models, and the functions of the old version of the PLC are inherited by the new version of the PLC. Therefore, the user program used in the old version of the PLC can be directly installed in the new version of the PLC.
[0005]
The support tool corresponds to each PLC, and when the PLC is upgraded, the support tool is upgraded accordingly. That is, when the function is extended in the new version of the PLC, the support tool of the old version cannot support the extended function, and a support tool corresponding to the extended function is required to support the extended function. Of course, since the support tool is also designed to inherit the functions of the conventional support tool, the upgraded support tool can be connected to the old version of the PLC so that the user program can be downloaded, created, modified, etc. It has become.
[0006]
As described above, the new version of the support tool guarantees the connectivity with the old and new versions of the PLC, and the old version of the support tool guarantees only the connection with the old version of the PLC. When the support tool is connected to the PLC so that the old version of the support tool does not connect to the new version of the PLC and perform predetermined support processing (addition / update of user program, etc.), The support tool reads out the PLC model information through communication, and the support tool checks the compatible PLC model information held by itself to determine whether the connection can be guaranteed. That is, the PLC and the support tool are connected via a communication line such as serial communication, a communication command for acquiring PLC model information is issued from the support tool to the PLC, and the PLC that has received the communication command PLC model information is returned as a response. Since the support tool stores and holds a list of PLC model information that can be connected to itself, the support tool that has received the response stores the data of the list that has been stored and the currently connected PLC acquired as a response. A check is made with the PLC model information to determine whether or not connection is possible. For example, Patent Literature 1 discloses a technique for model confirmation.
[0007]
[Patent Document 1]
JP 10-97310 A
[0008]
[Problems to be solved by the invention]
By the way, since the new version of the PLC inherits the functions of the old version of the PLC, for example, the old version of the user program may be operated in a mounted state. In this way, even if the hardware is a new version of the PLC but is operating substantially as an old version of the PLC, the old model support tool has a Connection was not possible because the PLC model information of the version of the PLC is not retained.
[0009]
Therefore, when a user uses a new version of the PLC that has been expanded in this way, the user must use a new version of the support tool corresponding to the PLC regardless of the version of the installed user program. did not become. In other words, when purchasing and installing a new version of the PLC, it is necessary to purchase a new version of the support tool corresponding to the PLC or upgrade the support tool.
[0010]
However, even if the PLC is upgraded, it is not necessary to use the extended function, and there are not a few users who can suffice if it is possible to operate with the old version of the user program created by the support tool of the old version. For these users, the new version of the support tool supports functions that they do not use, and the functions added to the support tool are unnecessary for that user. Purchasing or upgrading a support tool requires useless cost and effort, and often has a sense of resistance.
[0011]
On the other hand, in view of the above-mentioned circumstances, the PLC manufacturer is required to use the old version of the user program created by the old version of the support tool even if a new version of the PLC is developed. Versions of PLC were still manufactured and sold. However, manufacturing new and old versions of PLC in this way cannot be expected to reduce costs by mass production, and as a result, both new and old versions of PLC become expensive.
[0012]
The present invention makes it possible to connect to an existing old version support tool even when a new version of a PLC operates as an old version of a PLC using an old version of a user program or the like. It is an object of the present invention to provide a programmable controller system and support tool that can be used, a programmable controller unit, and a connection guarantee method.
[0013]
[Means for Solving the Problems]
In the programmable controller system according to the present invention, in a system including a programmable controller and a support tool connected to the programmable controller, the programmable controller stores application version information indicating the functionality of the stored user program. The support tool has a function of acquiring application version information stored and held in the programmable controller, and a function of determining whether the programmable controller is a version that the programmable controller can support based on the acquired application version information. It was configured with. Here, “self can handle” means that the support tool can perform support processing (creation, addition, modification, etc.) for the user program stored in the programmable controller (the same applies hereinafter).
[0014]
As another solution, in a system including a programmable controller and a support tool connected to the programmable controller, the programmable controller includes application version information indicating the functionality of a stored user program, Unit version information indicating the functionality of the device itself is stored and held. The support tool stores storage means for storing application version information indicating the functionality of the user program together with the user program, a function for acquiring application version information stored in the programmable controller, and storage in the programmable controller. The programmable controller can respond to itself based on the function of acquiring the stored unit version information, at least one of the acquired application version information and unit version information, and the application version information stored and held by itself. It is also possible to provide a function for determining whether or not a version is present.
[0015]
Based on the above inventions, the application version information stored and held in the programmable controller is stored with a value indicating an unstored state when no user program is stored in the programmable controller. It is good to. Here, the unstored state corresponds to the initialized state in the embodiment.
[0016]
Furthermore, the application version information and the unit version information may be configured by numerical data. In this way, it is possible to easily determine whether the version is new or old.
[0017]
The support tool according to the present invention is a support tool for a programmable controller that stores and holds application version information indicating the functionality of a stored user program, and acquires the application version information stored and held in the programmable controller. And a function for determining whether or not the programmable controller is a version that can be supported by the programmable controller based on the acquired application version information.
[0018]
Furthermore, another solution is a support tool for a programmable controller that stores and holds application version information indicating the functionality of a stored user program and unit version information indicating the functionality of the device itself, And a storage unit for storing application version information indicating the functionality of the user program, a function for acquiring application version information stored and held in the programmable controller, and unit version information stored and held in the programmable controller. Based on the function, at least one of the acquired application version information and unit version information, and the application version information stored in the storage unit, the programmable controller can handle the bar. It may be configured to include a function of determining whether tio down or not.
[0019]
Furthermore, the programmable controller unit according to the present invention is a programmable controller unit in which unit version information indicating the functionality of the device is set, and stores application version information indicating the functionality of the stored user program. As a response to the read request from the support tool and the storage means to hold, it has a function of returning the application version information. Here, the programmable controller unit has been described by taking the CPU unit as an example in the embodiment, but the present invention is not limited to this and can be applied to a high-functional unit and other various units.
[0020]
When no user program is stored, a value indicating an unstored state may be stored as the application version information stored in the storage unit.
[0021]
Furthermore, the connection guarantee method according to the present invention is a support tool connection guarantee method for a programmable controller, and the programmable controller stores application version information indicating the functionality of a stored user program. Then, the support tool acquires the application version information stored and held in the programmable controller, and determines whether the programmable controller is a version that can be supported by the programmable controller based on the acquired application version information. As a result, the connection is allowed and communication is continued only when it is possible.
[0022]
As another solution, the programmable controller stores and holds application version information indicating the functionality of the stored user program and unit version information indicating the functionality of the device itself. The application version information indicating the functionality of the user program is stored together with the program, and the support tool acquires at least the unit version information stored and stored in the programmable controller, and the functionality indicated by the acquired unit version information. If the range of functionality indicated by the application version information stored and held by the self is greater than the range, connection permission is not given, and the range of functionality indicated by the application version information stored and held by the self is acquired. Shown in unit version information The following range of potential, and the application version information which the programmable controller is stored and held, if the application version information stored in itself held match can also be adapted to allow the connection.
[0023]
Further, the functionality range indicated by the application version information stored and held by the self is equal to or less than the functionality range indicated by the acquired unit version information and does not match the application version information stored and held by the programmable controller. Is preferably provided with a step of permitting connection on condition that the application version information stored and held in the programmable controller is permitted to be changed.
[0024]
The programmable controller (unit) and the support tool for use in the present invention are improved in functionality (version up), but the new version of the product (programmable controller, support tool) is the product of the old version. For example, a user program created according to the old version can be implemented in a new version of the programmable controller. Similarly, the new version of the support tool can be connected to the old version of the programmable controller to perform support processing.
[0025]
According to each of the above-described premises, an application version indicating functionality in a user program stored in the programmable controller (unit) is stored in the programmable controller (unit). Thereby, by acquiring the application version, whether the programmable controller stores and operates the user program corresponding to the unit version, or stores the old version user program and substantially the old version programmable controller. It can be easily determined whether it is operating as a device.
[0026]
Therefore, even if the unit version indicating the functionality of the device itself is a higher version (new version) that cannot be supported by the support tool, if the application version of the actually stored user program is compatible, the old version Support processing can be performed using support tools.
[0027]
As a result, there is no need to force users to purchase / upgrade a new version of support tools with the development of a new version of the programmable controller, and the new version of the programmable controller can be used as long as the old version of the user program is used. You can continue to use the old version of the support tool even if you purchase and use it. Therefore, when the manufacturer develops a new version of the programmable controller, the production of the old version of the programmable controller can be stopped at a relatively early timing.
[0028]
DETAILED DESCRIPTION OF THE INVENTION
FIG. 1 shows the entire system for realizing a preferred embodiment of the present invention. As shown in FIG. 1, a support tool 10 composed of a personal computer and a PLC (CPU unit 22) 20 are connected via a predetermined communication line 30. The communication line 30 is realized by, for example, direct cable connection using a serial line such as RS232C. Of course, the direct connection is not limited to this, and a configuration in which the PLC 20 and the support tool 10 are connected via a network using another communication line may be adopted. Then, the user program created (including correction) by the support tool 10 is downloaded to the PLC 20 via the communication line 30.
[0029]
The PLC 20 is composed of a plurality of units. That is, the power supply unit 21 of the power supply source, the CPU unit 22 that controls the entire PLC, the input unit 23 for inputting signals of switches and sensors installed at appropriate places in the FA production equipment and facility equipment, and the control output Various units such as an output unit 24 for outputting and a communication unit 25 for connecting to a communication network are appropriately combined. The user program downloaded from the support tool 10 in this system is stored and held in the CPU unit 22 and executed there. The communication line 30 is connected to the communication unit 25, and the support tool 10 and the CPU unit 22 communicate with each other via the communication unit 25, or the CPU unit 22 has a built-in serial line interface to directly support the support tool 10. It can be connected to the CPU unit 22 to download a user program or the like.
[0030]
As shown in FIG. 2, the support tool 10 includes a personal computer, and includes an input device 11 such as a keyboard and a pointing device, a display device 12 such as a display, a CPU 13, and a storage unit 14. . In relation to the present invention, the support tool 10 is set with a version indicating the range of functionality for each of a plurality of connectable PLC models (it is an application version and may be different for each PLC model). The version information (application version) is stored in a user file (described later) in the storage unit 14. The application version is selected and set by the user. Further, a user program mounted on the connected PLC 20 (CPU unit 22) is also stored in the storage unit 14.
[0031]
On the other hand, the internal structure of the CPU unit 22 is configured as shown in FIG. That is, the system program is stored in the system ROM 22a, and the system program is called by the MPU 22b. The MPU 22b executes a predetermined process according to the program while appropriately using the system RAM 22c as a work memory. . During operation, a user program that is one of user data is stored in a user memory (UM) 22d. Further, I / O data and parameters are stored in the IO memory 22e.
[0032]
The PLC model and hardware version (unit version) information as a model are stored in, for example, the system ROM 22a. When a call request is received from the support tool 10, the PLC model and version information is received as a response to the support tool 10. To be sent back to.
[0033]
That is, when a PLC (CPU unit) that has been upgraded (function expanded) is manufactured, the version (application version) of the user program that uses the upgraded function is set to be the same as the unit version. Further, the same application version as the application version of the user program is set in the support tool 10 that can cope with the user program using the upgraded function. As a result, communication is performed when the support tool 10 is connected to the PLC 20, and the support tool 10 determines whether or not the application versions held by the two match, and if they match, the predetermined support processing is performed as it is. To do. Although referred to as a PLC model, since it is actually the model name of the CPU unit, it can also be referred to as a CPU model.
[0034]
Furthermore, in this embodiment, the version information attached to the PLC (CPU unit) and the support tool is represented by numerical values, and the numerical values are increased each time the version is upgraded. That is, it can be said that the larger the numerical value is, the newer the version is. Therefore, it is possible to easily determine which is the new version by comparing the magnitude relation of the numerical values of such versions. Since the new version of the support tool 10 and the PLC 20 (CPU unit 22) inherit the functions of the old version, the numerical value of the version of the PLC (CPU unit) acquired by the support tool 10 is the numerical value of its own version. If it is smaller than that, it can be determined that it can be handled. The numerical value of the version may be only an integer (only so-called “major version”), or a minor version using a decimal point or the like as appropriate.
[0035]
Here, in the present invention, as shown in FIG. 4, the user memory 22d of the CPU unit 22 stores the version (application version) of the user program stored in the CPU unit 22, and the support tool 10 is connected to the PLC (CPU App version is acquired together with the model version of the unit, and if the app version can be handled by itself, the connection is continued and the predetermined processing can be performed. That is, even if the version of the PLC itself is the new version “1.2”, if the application version of the user program implemented there is created with the function of the old version “1.1”, the application version “ 1.1 "is also stored in the PLC 20 (CPU unit 22).
[0036]
When the support tool 10 is connected to the PLC 20, a PLC model information call request is issued to the PLC 20, and the PLC that receives the request sets the application version in addition to the PLC model and the unit version of the device itself. And return as a response. Assuming that the version of the support tool 10 that has received this response is 1.1, the currently connected PLC is not compatible with the conventional device because the version of the device itself (unit version) is 1.2. When it is recognized that the application version is 1.1 that can be handled by itself, the connection state is continued and processing can be performed within the range of the function of version 1.1. Of course, it is assumed that the PLC models are the same when determining the difference in version and the size relationship.
[0037]
As a result, even if the PLC 20 of the new version (1.2) is substantially operating as a device of the old version (1.1), the old version (1.1) recognizes it by the old version. Even the support tool 10 corresponding to the version can be connected to perform predetermined support processing (downloading, uploading, creating, correcting, etc. of the user program).
[0038]
Furthermore, when a user program already created in a predetermined version is stored in the support tool 10 and downloaded to the PLC 20 (CPU unit 22), the user program stored in the support tool 10 is stored. The application version is compared with the unit version of the PLC (CPU unit) and the application version, and the following processing is performed.
(1) When the application version of the user program in the user data on the support tool is equal to or lower than the unit version on the PLC
(A) Connection is permitted when the application version of the user data on the support tool is equal to the application version on the PLC
(B) If the application version of the user program in the user data on the support tool is not equal to the application version on the PLC, connection is prohibited or the application version on the PLC is rewritten with the application version on the support tool Allow connection above (download user program etc.)
(C) When the user program is not stored in the PLC and there is no application version (value at initialization), the connection is permitted after rewriting the application version on the PLC to the application version on the support tool ( After that, download the user program etc.)
(2) When the application version of the user program in the user data on the support tool is larger than the unit version on the PLC
Since the application version of the user program on the support tool is large, there is a risk of malfunction when downloaded to the PLC, so connection is prohibited.
[0039]
In the above description, in response to the PLC model information call request, it has been described that the PLC model, unit version, and application version are returned as a set, but the present invention is not limited to this. It may be configured to issue a call request one by one in order and return a response one by one from the PLC that receives it, and it is of course possible to acquire information in any combination.
[0040]
And in order to perform the process which concerns, specifically, it comprised so that the function which performs the process shown in the flowchart after FIG. That is, the support tool 10 selects a menu for each function mainly by a user operation on the input device 11 such as a keyboard / pointing device, and operates according to the selected menu. Therefore, the processing flowchart of the entire support tool is as shown in FIG.
[0041]
That is, first, an event by the above-described user operation is received (ST1). Then, it is determined whether the content of the received event is “connection process based on PLC model and version of open user file” and “connection process based on automatic recognition of PLC model”. (ST2, ST3). The user file referred to here is a data file created by the user operating the support tool 10 and exists in the storage unit 14 in the present embodiment. Further, the user data described in the present embodiment is stored in this user file.
[0042]
If it is not any process, it is determined whether or not it is an end instruction (ST4). If it is an end instruction, a predetermined end process is executed and the process is ended (ST5). Although not described in this flowchart, there are events that execute functions other than those described above as events by user operations. Of course, when events of other functions are received, predetermined processing is executed. .
[0043]
Here, in the present invention, when the accepted event is “connection process based on PLC model and version of open user file”, the branch determination in Step 2 is Yes, so the process jumps to Step 6 and the predetermined event is performed. Execute the process. That is, the application version of the user program stored in the user file of the open support tool 10 and the PLC model and version information (unit version & application version) of the PLC (CPU unit 22) to be connected at present are acquired. Then, it is determined whether or not connection is possible and processing based on the determination result is executed. Specifically, the flowcharts shown in FIGS. 6 and 7 are executed, and the description thereof will be described later.
[0044]
If the process specified in step 6 is executed, the process proceeds to step 8 to determine whether or not the online connection process is permitted in the process of step 6. If permitted, the process for online connection with the PLC is performed. Processing is started (ST9). Thereafter, the process proceeds to step 10 and waits for an event input by the next user operation. If such an event is received, it is determined whether or not the content of the received event is to go offline (ST11), and no transfer is made. If so, the process returns to step 10, and if the process proceeds, the process returns to step 1 to wait for the reception of the next event.
[0045]
In other words, after the online connection is permitted and the online connection is established, when a menu of each online function is selected, the operation is performed according to the selected menu (ST10 and ST11 are repeatedly executed). In this state, when an operation requesting to go offline is selected, the operation goes offline (return to ST1). If online connection permission is not permitted, the branch determination in step 8 is No, so the process proceeds to step 4 to execute a predetermined process.
[0046]
On the other hand, if the event accepted in step 1 is “connection process by automatic recognition of PLC model”, the branch determination in step 3 is Yes, so the process jumps to step 7 to execute the predetermined process. That is, the PLC model and application version information (application version) of the PLC (CPU unit 22) that is currently connected are acquired, and whether or not connection is possible and processing based on the determination result are executed. Specifically, the flowchart shown in FIG. 8 is executed, and the description thereof will be described later.
[0047]
If the process specified in Step 7 is executed, the process proceeds to Step 8 to determine whether or not the online connection process is permitted in the process of Step 7. If permitted, the process for online connection with the PLC is performed. Processing is started (ST9). Thereafter, the process proceeds to step 10 to perform the same processing as described above. If online connection permission is not permitted, the branch determination in step 8 is No, so the process proceeds to step 4 to execute a predetermined process.
[0048]
Next, a specific process of “connection process based on PLC model and version of user file being oven” defined in step 6 will be described. As shown in FIGS. 6 and 7, first, a communication command for inquiring about the PLC model (CPU model) is issued to the PLC 20 (CPU unit 22) (ST21). As a response to this communication command, the PLC model (CPU model) is sent from the PLC (CPU unit). Therefore, if such a response is received, it is connected to the PLC model on the user file on the support tool 10 side. It is determined whether the PLC models on the PLC side match (ST22). If they do not match, the support tool 10 does not support the currently connected PLC 20 (CPU unit 22) and cannot be processed, so a warning message is output to the display device 12 of the support tool 10. Display (ST33), and the process ends. An example of the warning message is “PLC model of connected PLC (CPU unit) and PLC model of user file do not match, so connection is not possible. Please match user file model”.
[0049]
On the other hand, if both PLC models (CPU models) match, a communication command for inquiring the unit version is issued to the PLC 20 (CPU unit 22) (ST24). Then, since the unit version is sent from the PLC (CPU unit) as a response to this communication command, if such a response is received, the acquired unit version and the application version on the user file on the support tool 10 side are received. Are compared to determine whether the application version is equal to or lower than the unit version (ST25).
[0050]
If the application version is larger than the unit version, the user program cannot be downloaded to the PLC, so a warning message is output, the connection is prohibited, and the process is terminated (ST26). An example of the warning message is “The connected PLC (CPU unit) version is smaller than the user file version and cannot be connected. Please match the user file version”.
[0051]
On the other hand, if the application version of the user file is equal to or less than the PLC unit version, the branch determination in step 25 is Yes, so that the application version on the user file and the application version of the PLC (CPU unit) match next. It is determined whether or not (ST27). If they match, it is possible to cope with them, so the process jumps to step 33, permits connection with the PLC (CPU unit) and ends the process (ST33).
[0052]
As a result of executing the process as described above, when it is determined that “permit connection with PLC” is determined, when the process returns to the flowchart of the entire support tool, the state of “permit connection with PLC” is displayed. Make it available in the flowchart for the entire support tool.
[0053]
If the application version on the user file does not match the application version of the PLC (CPU unit), the branch determination in step 27 is No, so the process jumps to step 28 and the application of the PLC (CPU unit). It is determined whether the version is in the PLC initialization state, that is, whether the version is unused and the user program is not registered. In the case of the initialization state, since the user tool of the support tool 10 can be downloaded to the PLC side, the process jumps to step 31 and clears the user program in the user data stored in the PLC (CPU unit). Next, a communication command for writing the application version on the user file to the PLC (CPU unit) is issued (ST32). Thereby, the application version on the PLC side is set to the user version of the user file opened in the support tool 10. Then, it progresses to step 33 and a connection with PLC is permitted.
[0054]
On the other hand, if the branching determination in step 28 is No, that is, if it is not in the initialization state, it is possible to support the PLC to which the support tool 10 is connected, but if the processing is continued as it is, it is currently set to the PLC side. Since the application version will be changed, the user is warned to that effect and permission to update is received. Therefore, first, the process proceeds to step 29, and a predetermined update confirmation message is displayed. The update confirmation message is, for example, “Cannot connect because the application version of the connected PLC (CPU unit) does not match the version of the user file. Do you want to write the user file version to the CPU unit? , PLC (CPU unit) memory is cleared. "
[0055]
Then, after such a message, it waits for a selection instruction from the user, and determines whether or not “forcibly rewrite application version” is selected. If it is selected, the process proceeds to step 31 to execute the above-described processing. If it is not selected, the connection is prohibited and the process is terminated as it is.
[0056]
Next, a specific process of “connection process by automatic recognition of PLC model” in step 7 will be described. As shown in FIG. 8, first, a communication command for inquiring about the PLC model is issued to the PLC (CPU unit) (ST41). Since the PLC model information returned from the PLC side is acquired as a response to this communication command, it is determined whether or not the acquired model information is supported by its own support tool. That is, it is checked whether the PLC model to be connected is supported by this support software (ST42).
[0057]
If the result of this branch determination is Yes, a communication command for inquiring the application version to the PLC (CPU unit) is issued (ST43). Since the current application version of the PLC is returned as a response to this communication command, the support tool 10 supports the application version of the PLC to be connected obtained by receiving this response with this support software. Is checked (ST44).
[0058]
If not supported, the connection is prohibited and the process is terminated. If it is supported, the branch determination in step 44 is Yes, so the support tool automatically generates a user file of the PLC model / application version read from the PLC (CPU unit) (ST45). Thereafter, a state of “permitting connection with PLC” is set (ST46). As a result of executing the process as described above, when it is determined that “permit connection with PLC” is determined, when the process returns to the flowchart of the entire support tool, the state of “permit connection with PLC” is displayed. Make it available in the flowchart for the entire support tool. For example, a flag indicating a state of permitting connection with the PLC is provided, the flag is set in step 33 or step 46, and in step 8, whether online connection processing is permitted depending on whether the flag is set or not. Judging.
[0059]
In the above-described embodiment, the CPU unit that stores the user program is applied. However, the present invention is not limited to this, and the present invention can also be applied to a high-function unit and other PLC units.
[0060]
In addition, since there is a user program as a typical one managed by the application version, in the above-described embodiment, the application version for the user program is checked. In addition to the user program, there are parameters (data that allows the user to define the basic specifications of the CPU unit in software, data relating to a communication path when data is transmitted and received between networks, and the like). Therefore, such parameters and the like may be checked and managed. The user data includes such parameters.
[0061]
【The invention's effect】
As described above, in the present invention, the programmable controller (unit) stores the application version and determines whether or not the support tool can be supported based on at least the application version. Even in such a case, when an old version of the user program or the like is used to operate substantially as an old version of the programmable controller, the connection can be made using the existing old version of the support tool.
[Brief description of the drawings]
FIG. 1 is a diagram showing an embodiment of a system of the present invention.
FIG. 2 is a diagram showing an internal configuration of a support tool.
FIG. 3 is a diagram showing an internal configuration of a CPU unit.
FIG. 4 is a diagram for explaining the outline of the present embodiment;
FIG. 5 is a flowchart showing functions of a support tool.
FIG. 6 is a part of a flowchart showing an example of a specific algorithm for connection processing based on the PLC model and version of an open user file.
FIG. 7 is a part of a flowchart showing an example of a specific algorithm for connection processing based on the PLC model and version of an opened user file.
FIG. 8 is a part of a flowchart showing an example of a specific algorithm for connection processing by automatic recognition of a PLC model.
[Explanation of symbols]
10 Support tools
11 Input device
12 Display device
13 CPU
14 Storage unit
20 PLC
21 Power supply unit
22 CPU unit
22a System ROM
22b MPU
22c RAM
22d user memory
22e IO memory
23 Input unit
24 output unit
25 Communication unit
30 Communication line

Claims (11)

In a system comprising a programmable controller and a support tool connected to the programmable controller,
The programmable controller stores and holds application version information indicating the functionality of the stored user program,
The support tool has a function of acquiring application version information stored and held in the programmable controller, and a function of determining whether the programmable controller is a version that the programmable controller can support based on the acquired application version information. A programmable controller system characterized by that. In a system comprising a programmable controller and a support tool connected to the programmable controller,
The programmable controller stores and holds application version information indicating the functionality of the stored user program and unit version information indicating the functionality of the device itself,
The support tool is
Storage means for storing application version information indicating the functionality of the user program together with the user program;
A function of acquiring application version information stored in the programmable controller;
A function of acquiring unit version information stored and held in the programmable controller;
Based on the acquired application version information and / or unit version information, and the application version information stored and held by itself, the programmable controller has a function of determining whether or not the version can be supported by the programmable controller. Programmable controller system characterized by The application version information stored and held in the programmable controller stores a value indicating an unstored state when a user program is not stored in the programmable controller. The programmable controller system described. The programmable controller system according to any one of claims 1 to 3, wherein the application version information and the unit version information are configured by numerical data. A support tool for a programmable controller that stores and holds application version information indicating the functionality of a stored user program,
A function of acquiring application version information stored in the programmable controller;
A support tool comprising a function for determining whether or not the programmable controller is a version that the programmable controller can support based on the acquired application version information. A support tool for a programmable controller that stores and holds application version information indicating functionality of a stored user program and unit version information indicating functionality of the device itself,
A storage unit that stores application version information indicating the functionality of the user program together with the user program;
A function of acquiring application version information stored in the programmable controller;
A function of acquiring unit version information stored and held in the programmable controller;
Based on the acquired application version information and / or unit version information, and the application version information stored in the storage unit, the programmable controller has a function of determining whether or not the version can be supported by itself. Support tool characterized by that. A unit for a programmable controller in which unit version information indicating the functionality of the device is set,
Storage means for storing application version information indicating the functionality of the stored user program;
A programmable controller unit comprising a function of returning the application version information as a response to a read request from a support tool. 8. The programmable controller unit according to claim 7, wherein when a user program is not stored, a value indicating an unstored state is stored as application version information stored in the storage unit. A support tool connection guarantee method for a programmable controller,
The programmable controller stores and holds application version information indicating the functionality of the stored user program,
The support tool acquires application version information stored in the programmable controller,
Based on the acquired application version information, determine whether the programmable controller is a version that can be supported by itself,
A connection guarantee method characterized in that a connection is permitted and communication is continued only when the determined result is compatible. A support tool connection guarantee method for a programmable controller,
The programmable controller stores and holds application version information indicating the functionality of the stored user program and unit version information indicating the functionality of the device itself,
The support tool stores and holds application version information indicating the functionality of the user program together with the user program,
The support tool acquires at least unit version information stored and held in the programmable controller,
If the range of functionality indicated by the application version information stored and held by the self is larger than the range of functionality indicated by the acquired unit version information, connection permission is not given,
The range of functionality indicated by the application version information stored and held by itself is equal to or less than the range of functionality indicated by the acquired unit version information, and the application version information stored by the programmable controller and stored by the self A connection guarantee method, wherein connection is permitted when the application version information matches. If the range of functionality indicated by the application version information stored and held by the self is equal to or less than the range of functionality indicated by the acquired unit version information and the application version information stored and held by the programmable controller does not match, 11. The connection guarantee method according to claim 10, wherein the connection is permitted on condition that the application version information stored and held in the programmable controller is permitted to be changed.

Images