WO2007116798A1

WO2007116798A1 - Control system

Info

Publication number: WO2007116798A1
Application number: PCT/JP2007/056801
Authority: WO
Inventors: Eitarou Hioki
Original assignee: Mitsubishi Electric Corporation
Priority date: 2006-04-07
Filing date: 2007-03-29
Publication date: 2007-10-18
Also published as: JP4759048B2; JPWO2007116798A1

Abstract

Provided is a control system, which can transmit a user file from the outside between control devices without using a programming tool. The control system comprises a plurality of control devices (20, 40) connected with each other through a data bus and including internal storage means for storing the user file, and a portable memory card (30) capable of storing the user file. The memory card (30) stores the transfer file information stored in the control devices (20, 40) or the memory card (30) for designating the user file or a transfer target, and transfer parameters containing the transfer destination of the user file. One of the control devices (20, 40) includes a memory card interface (27) for having access to the memory card (30), and transfer means for transferring the user file designated with the transfer file information, to the transfer destination in accordance with the transfer parameters.

Description

Specification

Control system technology field

[0001] The present invention relates to a control system.

Background art

[0002] A programmable controller as a control device performs a predetermined process by controlling a control target according to a program, and processes and manufactures a product. As such a programmable controller, there is disclosed a configuration in which a CPU unit and a plurality of numerical control device units are connected to one mother board via a data bus to control a control target ( For example, see Patent Document 1). In the data RAM of the CPU unit of this conventional programmable controller, an area of 200 bytes for writing data to be transferred to each numerical controller unit is secured. Then, when the numerical control unit is started up, the data of the data RAM of the CPU unit is divided into a predetermined length and transferred to the numerical control unit corresponding to the area written in the data RAM.

[0003] In order to easily write data to the programmable controller and read data from the programmable controller, a memory cassette having a loader function capable of reading and writing programs is mounted on the programmable controller. Some of these have also been proposed (see, for example, Patent Document 2).

[0004] Patent Document 1: Japanese Patent Publication No. 8-16846

Patent Document 2: Japanese Patent Laid-Open No. 2001-175309

Disclosure of the invention

Problems to be solved by the invention

Incidentally, in recent years, a control system having a configuration in which a plurality of programmable controllers are mounted on a base unit and connected to each other via a bus is also used. In this case, each programmable controller has a user program RAM and is stored in the user program RAM according to the user program. The programmable controller can perform independent processing.

[0006] Even in such a control system, it is necessary to write user program user data to each programmable controller or to read user data to an external device. In this case, the method described in Patent Document 1 can transmit user data from the CPU unit to each numerical control device unit, but does not disclose the case of reading the data to an external device.

[0007] Further, it is disclosed that the user program is written in the user program RAM via a programming tool connected to the CPU unit. In such a user program writing method, when a control system (programmable controller) is installed in a location that is out of the reach of the operator, a programming tool is connected to the programmable controller to write the user program. There was a problem in that the work involved was labor intensive. Further, a system in which a plurality of programmable controllers having user program RAMs are connected has been proposed in the past, but a technique for transmitting a user program in this system is disclosed in Patent Document 1. I helped. This is because the numerical control unit of the programmable controller of Patent Document 1 should be considered for the transmission of the user program in the system as described above where the user program RAM is present.

[0008] On the other hand, Patent Document 2 describes a force that allows a user program to be exchanged with a built-in memory of a programmable controller using a memory cassette. In the control system consisting of programmable controllers, there is a problem that it is necessary to prepare the same number of memory cassettes as the programmable controllers. In addition, since a means for mounting a memory cassette is required for each programmable controller, the cost of the control system increases.

[0009] Further, when user data is transmitted by the method described in Patent Document 1, the data RAM on the CPU unit that holds the user data to be transmitted has a predetermined size for transfer to each numerical controller unit. This data area is allocated in advance. For this reason, the size of the user program and user data, S, and the program that varies depending on the programmable controller. In addition, there is a problem that an unused area is generated or a user program or user data does not fit in the data area, so that the storage area cannot be used effectively. In Patent Document 1, since the memory configuration and address are fixed, the memory configuration on the programmable controller side must be changed to change the memory configuration on the numerical controller side. There was also the problem that efficiency was bad. In addition to programmable controllers, control devices such as NC (Numerical Controller), MC (Motion Controller), RC (Robot Controller), and industrial controllers such as displays that are operating terminals are generally described above. There was a problem.

The present invention has been made in view of the above, and is a control system in which a plurality of control devices are connected via a data bus. An external user file (user program and user data without using a programming tool) is provided. )) Can be transmitted between control devices. In addition, when writing a user file to a control device in the control system, a control having a data structure that can effectively use a storage area in a portable storage medium in which the user file is written. The purpose is to obtain a system.

Means for solving the problem

[0011] To achieve the above object, a control system according to the present invention is capable of storing a plurality of control devices connected to each other via a data bus and having internal storage means for storing user files, and user files. In the control system comprising a portable storage medium, the portable storage medium is a transfer file for designating a user file to be transferred stored in the control device or the portable storage medium. Information and a transfer parameter including a transfer destination of the user file are stored, and one control device among the plurality of control devices, according to the interface means for accessing the portable storage medium and the transfer parameter, Transfer means for transferring a user file specified by the transfer file information to the transfer destination; Characterized in that it comprises a.

The invention's effect

[0012] According to the present invention, it is easily carried without using a dedicated programming tool. The user file can be transferred between the possible storage medium and the control device. In addition, since an interface for a portable storage medium is provided in one control device, it is possible to obtain a cheaper control device or control system.

Brief Description of Drawings

FIG. 1 is a diagram schematically showing an overview of a control system according to the present invention.

FIG. 2 is a block diagram schematically showing the configuration of the first embodiment of the control system according to the present invention.

FIG. 3 is a diagram schematically showing the data structure of a memory card.

FIG. 4 is a diagram schematically showing the data structure of a memory card.

FIG. 5 is a diagram schematically showing the data structure of a memory card.

FIG. 6 is a diagram showing an example of transfer parameters.

FIG. 7 is a flowchart showing an example of a procedure of operation processing of a system program of a programmable controller.

FIG. 8 is a diagram illustrating an example of a data structure of transfer information.

FIG. 9 is a flowchart illustrating an example of a procedure of an operation process of a system program of a programmable controller.

FIG. 10 is a block diagram schematically showing a configuration of a third embodiment of the control system according to the present invention.

FIG. 11 is a diagram schematically showing an example of password information stored in the system work ROM.

FIG. 12 is a diagram schematically showing a data structure of a memory card.

[FIG. 13] FIG. 13 is a flowchart showing a procedure of a word collation process when a user file is transferred from the memory card to the programmable controller.

[FIG. 14] FIG. 14 is a flowchart showing a procedure of a word collation process when a user file is transferred from the programmable controller to the memory card.

Explanation of symbols

[0014] 10 base units 11 Data bus

20 Master programmer controller

21, 41 MPU

22, 42 System program ROM

23, 43 System work RAM

24, 44 Data node interface

25, 45 User program RAM

26, 46 User data RAM

27 Memory card interface

28, 47 Nos

29 System work ROM

30 Memory card

31 Memory card slot

40, 40a, 40b Slave programmable controller

BEST MODE FOR CARRYING OUT THE INVENTION

[0015] Hereinafter, a preferred embodiment of a control system according to the present invention will be described in detail with reference to the accompanying drawings. In the following embodiments, a programmable controller will be described as an example of a control device, but the present invention is not limited to these embodiments.

[0016] Embodiment 1.

FIG. 1 is a diagram schematically showing an overview of the control system according to the present invention, and FIG. 2 is a block diagram schematically showing the configuration of the control system according to the first embodiment. In this control system, a plurality of programmable controllers 20, 40a, and 40b are mounted on a base unit 10. In the embodiment described below, the unit (programmable controller) installed in the leftmost slot on the base unit 10 is the master programmable controller 20, and the unit installed in another slot (programmable controller). Is the slave programmable controller 40 (40a, 40b). In addition, here, only the master programmable controller 20 is provided with a memory card insertion slot 31, and The Mori card 30 can be attached and detached. Of the programmable controllers mounted on the base unit 10, which programmable controller is the master programmable controller 20 may be determined by another method. For example, if the base unit 10 has a plurality of slots and a plurality of programmable controllers are installed in the slots, the one installed on the leftmost side is set to a higher priority. The most expensive one is the master programmable controller.

As shown in FIG. 2, the base unit 10 is provided with a data bus 11, and user data and user programs (hereinafter referred to as user data) between the programmable controllers 20 and 40 via the data bus 11. Alternatively, a file containing a user program can be transmitted and received). The master programmable controller 20 includes an MPU (Micro Processing Unit) 21 that controls processing in the master programmable controller 20, and a system program ROM (which stores a system program that executes basic processing in the master programmable controller 20). Read-Only Memory) 22, system work RAM 23, which is a memory area used by the system program, and data bus 1

A data bus interface (framed as data bus IZF in the figure) 24 that processes the user file framed and sent to the specified destination connected to 1, and receives the frame addressed to its own programmable controller, and its own programmable controller User program RAM (Random Access Memory) 25 that stores user programs that run on the machine, user data RAM 26 that stores data used by user programs, and a memory card interface that accesses the memory card 30 (in the figure, the memory card IZF 27). These processing units are connected via a bus 28.

[0018] It should be noted that the system program ROM 22 stores the user file in the memory card 30 when it is inserted into the memory card 30 memory card insertion slot 31, the own master programmable controller 20, or the data bus 11. There is also included a program for executing processing to be transmitted to the slave programmable controller 40 at a predetermined destination.

Here, the transfer means in the claims corresponds to, for example, the MPU 21 that executes the system program in the system program ROM 22. For example, it corresponds to the memory card interface 27, and the internal storage means corresponds to the user program RAM 25 and the user data RAM 26, for example.

In addition, the slave programmable controller 40 includes an MPU 41 that controls processing in the slave programmable controller 40 and a slave programmable controller 40.

42, the system work RAM 43, which is a memory area used by the system program, and the user file that is connected to the data bus 11 is framed and transmitted to a predetermined destination, and the frame addressed to the programmable controller is received. A data bus interface 44, a user program RAM 45 that stores a user program that operates on its own programmable controller, and a user data RAM 46 that stores data used by the user program are provided. These processing units are connected via a nose 47.

Here, the internal storage means in the claims corresponds to the user program RAM 45 and the user data RAM 46, for example.

In FIG. 2, only one slave programmable controller 40 is depicted. Actually, one or more slave programmable controllers 40 are connected to the data bus 11.

3 to 5 are diagrams schematically showing a data structure of the memory card. As shown in FIG. 3, in the memory card 30, a transfer parameter 70 in which information for transferring the included user file (user program or user data) to a predetermined programmable controller is described, and each programmable User files 71a to 71d (user programs 71a and 71c and user data 71b and 71d) to be transferred to the controllers 20, 40a and 40b, and the force S are stored. Here, the user programs 71a and 71c and the user data 71b and 71d are stored as files following the transfer parameter 70.

FIG. 4 is a diagram showing details of the transfer parameters. The transfer parameter 70 includes a transfer information number 80 indicating the number of files whose data is to be rewritten, and transfer information 8 la to 8 Id indicating details regarding the file to be transferred. The transfer information 81a to 81d is prepared in a number equal to the transfer information number 80. Figure 4 shows four user files 71a ~ Since 71d is prepared, transfer information 81a to 81d corresponding to each user file 71a to 71d is prepared.

FIG. 5 is a diagram showing details of transfer information. This transfer information 81 includes transfer file information 91 indicating the file name of the user file to be transferred, transfer programmable controller information 92 indicating the programmable controllers 20 and 40 to which the user file is to be transferred, and the transfer destination programmable. And transfer memory information 93 that designates the transfer destination of the user file in the controllers 20 and 40, more specifically, the transfer capability to the user program RAMs 25 and 45, and the transfer to the user data RAMs 26 and 46. This memory card 30 corresponds to a portable storage medium within the scope of the request.

FIG. 6 is a diagram showing an example of transfer parameters when a user file is stored in the memory card as shown in FIG. In this example, the user program 71a and user data 71b for the master programmable controller 20 and the user program 71c and user data 71d for the slave programmable controller 40a are transferred, so the number of transfer information 80 is "4". . In addition, transfer information 81a to 81d including transfer file information 91, transfer programmable controller information 92, and transfer memory information 93 is written in each user file 71a to 71d. For example, in the case of transfer information 81a of user file 71a, “user program for master programmable controller 20” is set as transfer file information 91, and “master programmable controller 20” is set as transfer programmable controller information 92. “User program RAM” is set as the memory information 93. This means that the user name of the user name “master programmable controller user program” is written in the user program RAM 25 of the master programmable controller 20.

By storing the transfer parameter 70 and the user files 71a to 71d to be transferred in the memory card 30 as described above, the master programmable controller 20 can change the user files 71a to 71d based on the transfer parameter 70. Can be written to the memory of the destination programmable controller 20, 40 (user program RAM 25, 45 or user data RAM 26, 46). Also, as shown in Fig. 3 to Fig. 5, user programs and user data to be transferred to each programmable controller 20, 40 can be specified by file names. Therefore, as described in the background art, it is not necessary to specify an area for writing a user file and its size, so a file of an arbitrary size can be transferred.

Next, the operation processing of the system program of each programmable controller in such a control system will be described with reference to the flowchart of FIG. First, when the control system is activated, the MPUs 21 and 41 of the programmable controllers 20 and 40 execute the system programs stored in the system programs ROM 22 and 42, and whether they are the master programmable controller 20 or the slave programmable controller 40. Master Z slave discrimination information is obtained (step S11), and it is discriminated whether it is the master programmable controller 20 (step S12).

If the result of the determination is that the master programmable controller 20 (Yes in step S 12), the master programmable controller 20 determines whether or not the memory card 30 is installed in the memory card installation slot 31. Judgment is made via the memory card interface 27 (step S13). If the memory card 30 is inserted as a result of the determination (Yes in step S13), the process reads the transfer parameter 70 in the memory card 30 (step S14), and the transfer parameter It is determined whether 70 exists in the memory card 30 (step S15).

[0030] If the transfer parameter 70 exists (Yes in step S15), the number of transfer information 80 is obtained from it (step S16), and then one transfer from the transfer parameter 70 is obtained. Information 81 is acquired (step S17). The transfer parameter 70 is read into the system work RAM 23. Thereafter, the user file (user program or user data) is transferred from the memory card 30 to the programmable controllers 20 and 40 according to the transfer information 81 (step S18). As described above, when the transfer process of the user file according to one transfer information 81 in the transfer parameter 70 is completed, it is determined whether the transfer of the user file with the transfer information number of 80 minutes acquired in step S16 is completed. (Step S19). If the transfer of the user file with the number of transfer information of 80 minutes is completed, if it is not (No in step S19), return to step S17 and execute the transfer process of the user file with the transfer information number of 80 minutes To do.

Here, for example, when a user file is stored in the memory card 30, The MPU 21 of the programmable controller 20 sequentially transfers the user program 71a for the master programmable controller 20, its user data 71b, the user program 71c for the slave programmable controller 40a, and its user data 71d. Note that the term “transfer” is used in this specification even when a user program and user data are written in the user program RAM 25 and the user data RAM 26 in the master programmable controller 20 in which the memory card 30 is mounted, respectively.

An outline of the flow of processing in the block diagram shown in FIG. 2 in the user file transfer processing in step S18 described above will be described. When writing the user program 71a or user data 71b to the user program RAM 25 or user data RAM 26 of the own programmable controller, the MPU 21 of the master programmable controller 20 reads the user file from the memory card 30 and includes it in the transfer parameters. Write to user program RAM 25 or user data RAM 26 according to the writing location.

[0033] When the MPU 21 of the master programmable controller 20 writes the user program 71c or the user data 71d into the user program RAM 45 or the user data RAM 46 of the slave programmable controller 40a, the user file is stored in the data bus interface 24. To pass. In the data bus interface 24, the received user file is divided into sizes that can be flowed on the data bus 11, and is sent to the data bus 11 in a frame with a destination.

On the other hand, the data bus interface 44 of the slave programmable controller 40a, which is the destination of the frame, monitors the data (frame) flowing on the data bus 11 and receives the frame addressed to its own programmable controller. Then, the data bus interface 44 removes the destination of the received frame and extracts the data, and the MPU 41 performs a process of writing the data into the user program RAM 45 or the user data RAM 46 as the write destination.

[0035] Returning again to FIG. 7, when the transfer of the user file with the number of transfer information of 80 minutes is completed (Yes in Step S19), or in Step S13, the memory card 30 is inserted into the memory card slot. If it is not attached to the 31st (if No in step S13) or transferred in step S15 If there is no parameter 70 for use (if No in step SI5), the master programmable controller 20 notifies the slave programmable controller 40a of the completion of transfer (step S20). Thereafter, the MPU 21 executes the user program stored in the user program RAM 25 (step S24).

On the other hand, if it is determined in step S12 that the self-programmable controller is not the master programmable controller 20 (No in step S12), the slave programmable controller 40a transmits the user file transferred from the master programmable controller 20. Is received (step S21), and the received user file is written into the user program RAM 45 or the user data RAM 46 (step S22). After that, it is determined whether or not a notification of completion of user file transfer has been received from the master programmable controller 20 (step S23). If not received (No in step S23), the process enters a wait state. . Thereafter, when a notification of completion of transfer of the user file is received (Yes in step S23), the slave programmable controller 40a executes the user program stored in the user program RAM 45 (step S24).

[0037] According to the first embodiment, when the memory card 30 is installed, the MPU 21 of the master programmable controller 20 loads the user file stored in the memory card 30 according to the system program according to the predetermined programmable controller 20. Or, it can be transferred to the programmable controller 40 and written on the memory such as the user program RAM25 or the user program RAM45, the user data RAM26 or the user data RAM46, so it is easy to use without using a dedicated programming tool. It has the effect of being able to write user files to the programmable controllers 20, 40 on the control system. For example, a user file write operation by a user of the control system is only required to mount the memory card 30 in the memory card mounting slot 31 of the master programmable controller 20. In addition, by simply inserting the memory card 30 into the memory card installation slot 31 of the main programmable controller 20, it is possible to rewrite the user program of the programmable controller 20, 40 spontaneously, and rewrite the user program. This also has the effect of eliminating the need for an external device.

[0038] Furthermore, the user can connect to another slave programmable controller 40 via the data bus 11. Since the file is transferred, it is not necessary to provide memory card slot 31 and memory card interface 27 in all programmable controllers 20 and 40. Memory card slot 31 and memory card interface in one programmable controller (master programmable controller 20) Since it is sufficient to provide 27, it is possible to obtain a cheaper programmable controller 20, 40 or a control system. In addition, the user file to be written to each programmable controller is specified by the file name that is not specified by the address or area in the memory card 30, so an arbitrary size file can be stored in the memory card 30. And the memory area of the memory card 30 can be used effectively.

[0039] Embodiment 2.

In the first embodiment, the power of writing a user file stored in the memory card to the programmable controller is shown. In the second embodiment, the data in the user program RAM and user data RAM of each programmable controller is sucked up. We will explain the control system that can do this.

FIG. 8 is a diagram showing an example of the data structure of transfer information in the memory card. The transfer information 81 further includes transfer direction information 94 indicating the transfer direction of the user file to the memory card 30 in the transfer information of the first embodiment. This transfer direction information 94 includes, for example, the ability to write from the memory card 30 to the user program RAM 25, 45 or the user data RAM 26, 46, or from the user program RAM 25, 45 or the user data RAM 26, 46 to the memory card. Information indicating whether or not is read. Other information is the same as that in the first embodiment, and a description thereof is omitted. Further, the configuration of the control system and the memory card 30 is the same as that of FIG. 1 to FIG. 4 of the first embodiment, and therefore, these drawings are used in the following description and the detailed description thereof is omitted.

Next, the operation processing of the system program of each programmable controller in such a control system will be described with reference to the flowchart of FIG. First, the same processing as in steps S11 to S17 described in FIG. 7 of the first embodiment is performed, and the MPU 21 of the master programmable controller 20 determines the transfer parameters of the installed memory card 30. Transfer information number 80 and transfer information 81 are acquired from 70 (steps S51 to S57). In other words, when the programmable controller that executed the system program is the master itself and the memory card 30 is installed in the memory card installation slot 31, the memory card 30 also reads the transfer parameter 70 and the number of transfer information 80 And transfer information 81 is acquired.

[0042] Next, the MPU 21 of the master programmable controller 20 acquires the transfer direction information 94 from the transfer parameter 70 of the memory card 30 (step S58), and determines whether or not the user file has the transfer capability to the memory card 30 ( Step S59). When the transfer direction information 94 is a write (transfer of the user file from the memory card 30 to the programmable controller 20, 40) (No in step S59), as described in the first embodiment, the transfer information is transferred. The user file is transferred from the memory card 30 to the programmable controllers 20 and 40 according to 81 (step S60). On the other hand, when the transfer direction information 94 is read (transfer of the user file from the programmable controller 20, 40 to the memory card 30) (Yes in step S59), the programmable controller 20, 40 is transferred according to the transfer information 81. The user file is read from the user program RAM 25, 45 or the user data RAM 26, 46 and transferred to the memory card 30 (step S61). As described above, when the transfer processing of the user file according to one transfer information 81 in the transfer parameter 70 is completed, is the transfer of the user file with the transfer information number of 80 minutes acquired in step S56 completed? Is determined (step S62). If the transfer of the user file with the transfer information number of 80 minutes is not completed (No in step S62), the process returns to step S57, and the transfer process of the user file with the transfer information number of 80 minutes is executed.

[0043] When the transfer of the user file with the number of transfer information of 80 minutes is completed (Yes in Step S62), or when the memory card 30 is not inserted into the memory card insertion slot 31 in Step S53 (Step S53). If there is no transfer parameter 70 in Step S55 (No in Step S55), the master programmable controller 20 notifies the slave programmable controller 40 of the transfer completion (Step S63). . Thereafter, the MPU 21 executes the user program stored in the user program RAM 25 (step S66).

On the other hand, in step S52, the self-programmable controller becomes the master programmable controller. If it is not Roller 20 (No in Step S52), Slave Programmable Controller 40 uses User Program RAM 45 or User Data RAM 46 of its own programmable controller in the user file in memory card 30 mounted on Master Programmable Controller 20. The user file is read from the user program RAM 45 or the user data RAM 46 of the self-programmable controller and written to the memory card 30 mounted on the master programmable controller 20 (step S64). Thereafter, it is determined whether or not a user file transfer completion notice has been received from the master programmable controller 20 (step S65). If not received (No in step S65), the process waits. Thereafter, when a user file transfer completion notification is received (Yes in step S65), the slave programmable controller 40 executes the user program stored in the user program RAM 45 (step S66).

In the second embodiment, both writing of a user file from the memory card 30 to each of the programmable controllers 20 and 40 and writing of a user file from each of the programmable controllers 20 and 40 to the memory force 30 are performed. A control system configured to have only the function of writing a user file from each programmable controller 20, 40 to the memory card 30 can be constructed.

[0046] According to the second embodiment, in addition to the effects of the first embodiment, the user files of the programmable controllers 20 and 40 constituting the control system are connected to the control system. There is an effect that the data can be easily read out to the memory card 30 attached to the master programmable controller 20.

[0047] Embodiment 3.

In the third embodiment, the case where a password is set and protected so that data in the memory card or the programmable controller is not illegally read or rewritten in the first and second embodiments will be described.

FIG. 10 is a block diagram schematically showing a configuration of the control system according to the third embodiment. This control system permits the execution of processing using the memory card 30 when the memory card 30 is inserted in the master programmable controller 20 of FIG. 2 of the first embodiment. The system work ROM 29 is further provided for storing a password set in advance to determine whether the password is valid. In addition, when the memory card 30 is inserted into the system program ROM 22, the password information stored in the memory card 30 is compared with the password information stored in the system work ROM 29, and the passwords of both are compared. Stores a program that defines the processes that can be executed according to the presence or absence and the matching status. The same components as those in FIG. 2 of the first embodiment are denoted by the same reference numerals, and the description thereof is omitted. The system work ROM 29 corresponds to the password information storage means in the claims, and the password information stored in the system work ROM 29 also corresponds to the second password information, and the password information stored in the memory card 30. Corresponds to the first password information.

FIG. 11 is a diagram schematically showing an example of password information stored in the system work ROM. As shown in this figure, the system work ROM 29 stores password information 101 that can be accessed only by a user having a specific authority from the outside. The password information 101 may be, for example, information created for each master programmable controller 20 (for example, information identifying the master programmable controller 20), and identifies the user or administrator of the master programmable controller 20. Information.

FIG. 12 is a diagram schematically showing the data structure of the memory card. As shown in FIG. 12, the data structure of the memory card 30 is the same as that shown in FIG. 3 of Embodiment 1 except that the master programmable controller 20 having the password information 101 can be used to determine whether it can be used. It has a data structure to which information 72 is further added. Note that the same components as those in FIG. 3 of the first embodiment are denoted by the same reference numerals, and description thereof is omitted.

[0051] Here, when the password information 101, 72 is set only in either the master programmable controller 20 or the memory card 30, the password information 101, 72 is set and the data in which the password information 101, 72 is set. Can't perform rewrite process if read process. In addition, when the password information 101 and 72 are set in the two, if the two do not match, the process ends there. Furthermore, password information 101, 72 is set in both the master programmable controller 20 and the memory card 30, and if both match, or When the password information 101, 72 is not set for both, the processing described in the first and second embodiments can be performed without any limitation.

Here, the password verification process in the control system having such a configuration will be described. The following explanation is divided into (1) when the user file is transferred from the programmable controller to the programmable controller, and (2) when the user file is transferred from the programmable controller to the memory card.

(1) When Transferring User File from Memory Card to Programmable Controller FIG. 13 is a flowchart showing the procedure of password verification processing when a user file is transferred from the memory card to the programmable controller. This password verification process is performed between step S13 and step S14 in the system program process of FIG. 7 of the first embodiment, or step S53 and step of the system program process of FIG. 9 of the second embodiment. It is executed between S54.

First, when the memory card 30 is installed in the memory card installation slot 31 of the master programmable controller 20 in step S13 of FIG. 7 of the first embodiment or step S53 of FIG. 7 of the second embodiment, the master The MPU 21 of the programmable controller 20 checks whether the password information 101 is registered in the system work ROM 29 in the programmable controller (step S101). If password information 101 is registered in system work ROM 29 (Yes in step S101), the password information in the installed memory card 30 is read (step S102), and the password information 72 (Step S103). If the password information 72 is present (Yes in step S103), the password information 101 in the system work ROM 29 of the master programmable controller 20 and the password information 72 in the read memory card 30 are collated (scene). Step S104). If the two match as a result of the collation (Yes in step S105), transfer in the memory card 30 in step S14 in FIG. 7 in the first embodiment or step S54 in FIG. 7 in the second embodiment. Processing of the system program after the processing for reading parameter 70 is continued (step S106), and the password verification processing ends.

[0055] If the two password information does not match in step S105 (in the case of No in step S105), the password information 101 in the master programmable controller 20 and the memory Assuming that the password information 72 in the card 30 does not match, a password verification mismatch error is detected in each case (step S107), the system program processing is terminated (step S108), and FIG. Alternatively, the processing in FIG. 9 of the second embodiment is completed.

[0056] Furthermore, if the password information 72 does not exist in the memory card 30 in step S103 (if No in step S103), the password information 101 exists only in the master programmable controller 20. Therefore, the parameters for transfer in the memory card 30 in step S14 in FIG. 7 in the first embodiment or in step S54 in FIG. 7 in the second embodiment under the condition that the data rewrite in the programmable controllers 20 and 40 is prohibited. The processing of the system program after the reading process of 70 is continued (step S109), and the password verification process ends.

[0057] If the password information 101 is not registered in the system work ROM 29 of the master programmable controller 20 in step S101 (No in step S101), the MPU 21 is stored in the installed memory card 30. The password information 72 is read (step S110), and it is confirmed whether the password information 72 is present (step S111). If there is no password information 72 (No in step S111), no password is set in both the master programmable controller 20 and the memory card 30, so both collate. Then, the process proceeds to step S106, and the processing of the system program is continued as described above.

[0058] Also, when the password information 72 exists in the memory card 30 inserted in step S111.

In the case of Yes in step S111, the password information 101 does not exist in the master programmable controller 20, the password information 72 exists in the memory card 30, and the data in the memory card 30 exists. Under the read prohibition condition, the processing of the system program after the read processing of the transfer parameter 70 in the memory card 30 in the step S14 of FIG. 7 of the first embodiment or the step S54 of FIG. 7 of the second embodiment is performed. Continue (step S112) and the word verification process ends.

[0059] (2) Programmable Controller Power When Transferring User Files to Memory Card Figure 14 Transfers User Files from Programmable Controller to Memory Card It is a flowchart which shows the procedure of the password verification process in a case. This password verification process is performed between step S13 and step S14 in the system program process of FIG. 7 of the first embodiment, or step S53 and step of the system program process of FIG. 9 of the second embodiment. It is executed between S54.

First, when the memory card 30 is installed in the memory card installation slot 31 of the master programmable controller 20 in step S13 of FIG. 7 of the first embodiment or step S53 of FIG. 7 of the second embodiment, the master The MPU 21 of the programmable controller 20 checks whether the password information 101 is registered in the system work ROM 29 in the programmable controller (step S151). If password information 101 is registered in system work ROM 29 (Yes in step S151), the password information in the installed memory card 30 is read (step S152), and the password information is stored. Check if 72 is present (step S153). If there is password information 72 (Yes in step S 153), the password information 101 in the system work ROM 29 of the master programmable controller 20 and the password information 72 in the read memory card 30 are collated (success). Tape S154). If the two match as a result of the verification (Yes in step S155), transfer in the memory card 30 in step S14 in FIG. 7 of the first embodiment or step S54 in FIG. 7 in the second embodiment. Processing of the system program after the processing for reading parameter 70 is continued (step S156), and the password verification processing ends.

[0061] If the two password information does not match in step S155 (No in step S155), the password information 101 in the master programmable controller 20 and the password information 72 in the memory card 30 are For each case, a password verification mismatch error is detected (step S157), the system program processing is terminated (step S158), and the processing shown in FIG. 7 of Embodiment 1 or FIG. 9 of Embodiment 2 is performed. Processing ends.

[0062] Further, if the password information 72 does not exist in the memory card 30 in step S153 (No in step S153), the password information 101 exists only in the master programmable controller 20. Step S14 in FIG. 7 of Embodiment 1 or Embodiment 2 under the condition of prohibiting data reading in the programmable controllers 20, 40 The processing of the system program subsequent to the reading processing of the transfer parameter 70 in the memory card 30 in step S54 of FIG. 7 is continued (step S159), and the password verification processing ends.

[0063] If password information 101 is registered in system work ROM 29 of master programmable controller 20 in step S151! If this is not the case (if No in step S151), MPU21 is installed. A process of reading the password information 72 in the memory card 30 is performed (step S160), and it is confirmed whether the password information 72 exists (step S161). If there is no password information 72 (No in step S161), no password is set in both the master programmable controller 20 and the memory card 30. Then, the process moves to step S156, and the processing of the system program is continued as described above.

[0064] When the password information 72 exists in the memory card 30 mounted in step S161

In the case of Yes in step S161, the password information 101 does not exist in the master programmable controller 20, the password information 72 exists in the memory card 30, and the data rewrite in the memory card 30 occurs. Under prohibition conditions, continue the system program processing after step S14 in Fig. 7 of the first embodiment or read processing of the transfer parameter 70 in the memory card 30 in step S54 of Fig. 7 in the second embodiment. (Step S 162), and the nosword collation process ends.

According to the third embodiment, when accessing the user program RAMs 25 and 45 and the user data RAMs 26 and 46 of the programmable controllers 20 and 40 using the memory card 30, the memory card 30 and the master programmable controller 20 are accessed. Since password information is set and only accessible when the two match, it is possible to prevent unauthorized writing and reading of user files in the programmable controllers 20, 40 and to build a safe control system. If possible, it has a positive effect.

[0066] In the above description, in addition to the force programmable controller described as an example of a programmable controller as a control device, it is mounted on a base unit 10 such as an NC, MC, RC, or display device as an operation terminal The present invention can be applied to any industrial controller. In the first to third embodiments described above, the master programmable controller 20 includes the memory card insertion slot 31, and the memory card 30 is used to write a data file from the memory card 30 or data to the memory card 30. The memory card 30 is not limited as long as it is a portable storage medium that can read files. For example, instead of the memory card 30, an RFID (Radio Frequency Identification) tag may be used. In this case, instead of the RFID interface, the memory card interface 27 communicates with the RFID tag by a predetermined wireless communication method to read and write data. Also, a USB (Universal Serial Bus) memory may be used.

Industrial applicability

As described above, the control system according to the present invention reads out user programs and user data in a control system in which a plurality of control devices that execute independent user programs are connected via a bus. Useful for Z write processing.

Claims

The scope of the claims

[1] a plurality of control devices connected to each other via a data bus and having internal storage means for storing user files;

A portable storage medium that can store user files;

In a control system equipped with

The portable storage medium stores transfer file information specifying a transfer target user file stored in the control device or the portable storage medium, and transfer parameters including a transfer destination of the user file. And

One of the plurality of control devices is

Interface means for accessing the portable storage medium;

Transfer means for transferring a user file designated by the transfer file information to the transfer destination according to the transfer parameters;

A control system comprising:

[2] The transfer parameter may be a transfer capacity of a user file from the portable storage medium to a predetermined control device among the plurality of control devices, or from the predetermined control device among the plurality of control devices. The control system according to claim 1, further comprising transfer direction information indicating whether the user file is transferred to a possible storage medium.

[3] When the transfer direction information is transfer of a user file to the portable storage medium, the transfer means controls the plurality of controls according to the transfer file information of the transfer parameter and the transfer destination. 3. The control system according to claim 2, further comprising a function of reading a user file stored in an internal storage unit of a predetermined control device of the device and transferring it to the portable storage medium.

[4] When the transfer direction information is transfer of a user file to the control device, the transfer means is portable according to the transfer file information of the transfer parameter and the transfer destination. The control system according to claim 2, further comprising a function of reading a user file stored in a storage medium and transferring it to a predetermined control device among the plurality of control devices. The portable storage medium further stores first password information for determining whether or not access from the control device is possible,

The controller is

Password information storage means for storing second password information for restricting access to the user file;

The transfer means, when accessing the portable storage medium, collates the second password information with the first password information, and restricts access according to the collation result. The control system according to any one of claims 1 to 4.