JP6012918B1 - Control system and control method - Google Patents

Abstract

The programmable controller monitors a value representing the status of the monitoring target hardware, a backup target storage unit that stores data or a program used for machine control, a backup storage unit that stores data or a program in a backup manner, and When the state monitoring unit determines whether or not the value has reached a predetermined threshold, and when the state monitoring unit determines that the value has reached the threshold, the data or program is read from the backup target storage unit and stored in the backup A backup processing unit for writing to the unit for backup.

Description

  The present invention relates to a programmable controller, a control system, and a control method for controlling an industrial machine.

  Conventionally, a programmable controller for controlling an industrial machine is used in a production line of a factory.

  Generally, a control program and control parameters for controlling an industrial machine with a programmable controller are created by executing an engineering tool program on a computer and transmitted from the computer to the programmable controller.

  By the way, a control program and a control parameter may be changed or adjusted on a programmable controller while operating an industrial machine. Thereafter, when a trouble exemplified by a failure occurs in the programmable controller, the control program and the control parameters after being changed or adjusted are lost. Therefore, there is a request for backing up the control program and control parameters in the programmable controller.

  As a related technique, Patent Document 1 includes an error detection unit WDT (watchdog timer) that detects an abnormality in the operation of the central processing unit 170, and the access element 178 is connected to the central processing unit 170 by the error detection unit WDT. A programmable controller 120 is described that saves the data in the backup storage unit 182 to the backup storage unit 184 when an operation trouble is detected (summary).

Further, in Patent Document 2, when the power supply voltage for supplying power to the information processing unit is cut off, the CPU 22 operates the power supply for operating the circuits constituting the information processing unit from when the power supply voltage is cut off. Programmable to move predetermined information out of the information stored in the SRAM 24 to an empty area of the flash memory 23 within a time until the voltage V _CC exits a normal operating voltage area where the information processing unit can operate normally. -The information processing unit of the controller is described (summary).

JP 2014-81700 A JP 2000-305610 A

  Generally, the watchdog timer is a circuit for canceling software trouble by transmitting an interrupt signal to the CPU when a software trouble exemplified by an infinite loop or deadlock occurs in the CPU. Therefore, in the technique described in Patent Document 1, if a software trouble occurs, the data in the backup storage unit 182 can be saved to the backup storage unit 184. However, even if a trouble other than software occurs, the data stored in the backup storage unit 182 Data cannot be saved in the backup storage unit 184.

  Also, with the technology described in Patent Document 2, information stored in the SRAM 24 can be moved to the flash memory 23 when the power supply voltage for supplying power to the information processing unit is cut off. In other words, in the technique described in Patent Document 2, if a trouble of power supply voltage disconnection outside the information processing unit occurs, information stored in the SRAM 24 can be moved to the flash memory 23. Even if this occurs, the information stored in the SRAM 24 cannot be moved to the flash memory 23.

  This invention is made | formed in view of the above, Comprising: It aims at obtaining the programmable controller which can back up data or a program suitably.

  In order to solve the above-described problems and achieve the object, the present invention includes a backup target storage unit that stores data or a program used in machine control, and a backup storage unit that stores data or a program as a backup. A state monitoring unit that monitors a value representing the state of the monitored hardware and determines whether or not the value has reached a predetermined threshold; and a state monitoring unit that determines that the value has reached the threshold A backup processing unit that reads data or a program from the backup target storage unit, writes the data or program in the backup storage unit, and backs up the data or program.

  The programmable controller, control system, and control method according to the present invention have an effect that data or a program can be suitably backed up.

The figure which shows the structure of the programmable controller concerning Embodiment 1. FIG. 1 is a flowchart showing processing of a programmable controller according to a first embodiment; The figure which shows the structure of the programmable controller concerning Embodiment 2. FIG. The figure which shows the structure of the non-volatile semiconductor memory part of the programmable controller concerning Embodiment 2. FIG. The figure which shows the structure of the programmable controller concerning Embodiment 3. FIG. The figure which shows the structure of the programmable controller concerning Embodiment 4. FIG. The figure which shows the structure of the control system concerning Embodiment 5. FIG. The figure which shows the hardware constitutions of the external apparatus of the control system concerning Embodiment 5. The figure which shows the functional block of the external device of the control system concerning Embodiment 5. 10 is a flowchart showing processing of an external device of the control system according to the fifth embodiment. The figure which shows the display surface of the display part of the external apparatus of the control system concerning Embodiment 5. The figure which shows the structure of the programmable controller concerning the example of the other control system of Embodiment 5. FIG. The figure which shows the structure of the control system concerning Embodiment 6. FIG. The figure which shows the structure of the master programmable controller of the control system concerning Embodiment 6. FIG. The figure which shows the content of the backup memory | storage part of the master programmable controller of the control system concerning Embodiment 6 The figure which shows the structure of the slave programmable controller of the control system concerning Embodiment 6. FIG. A flowchart which shows a process of a slave programmable controller of a control system concerning a 6th embodiment. A flowchart which shows a process of a master programmable controller of a control system concerning a 6th embodiment. The figure which shows the structure of the control system concerning Embodiment 7. The figure which shows the functional block of the external device of the control system concerning Embodiment 7. The figure which shows the structure of the master programmable controller of the control system concerning Embodiment 7. FIG. The figure which shows the structure of the slave programmable controller of the control system concerning Embodiment 7. FIG. FIG. 10 is a sequence diagram showing processing of the control system according to the seventh embodiment. The figure which shows the display surface of the display part of the external apparatus of the control system concerning Embodiment 7.

  Below, a programmable controller, a control system, and a control method concerning an embodiment of the invention are explained in detail based on a drawing. Note that the present invention is not limited to the embodiments.

Embodiment 1 FIG.
FIG. 1 is a diagram illustrating a configuration of a programmable controller according to the first embodiment. A programmable controller (JIS B 3502: 2011, programmable controllers (PLC)) 1 includes a main board 1a and sub boards 1b and 1c. The main board 1a is communicably connected to the sub boards 1b and 1c via the bus B2.

  A machine 2 is connected to the sub board 1b, and a machine 3 is connected to the sub board 1c. The main board 1a controls the machine 2 through the sub board 1b and controls the machine 3 through the sub board 1c.

  The main board 1a includes a bus interface 1a9 that is a bus bridge circuit that connects the bus B1 and the bus B2 that are internal buses of the main board 1a.

  The main board 1a includes a communication interface 1a7 for communicating with an external device. The communication interface 1a7 is connected to the bus B1. The communication is exemplified by Ethernet (registered trademark, IEEE 802.3) or wireless LAN (IEEE 802.11a / b / g / n / ac).

  The main board 1a includes a USB (Universal Serial Bus) interface 1a8 for communicating with an external device. The USB interface 1a8 is connected to the bus B1.

  The main board 1a includes a non-volatile semiconductor storage unit 1a10 that stores project data 1a10a. The nonvolatile semiconductor memory unit 1a10 is connected to the bus B1. The nonvolatile semiconductor storage unit 1a10 is exemplified by an SSD (Solid State Drive) or an eMMC (embedded Multi Media Card). The SSD or eMMC is configured using a flash memory (registered trademark).

  The project data 1a10a includes a control program 1a10a1 for controlling the machines 2 and 3, a control parameter 1a10a2 that is referred to when the control program 1a10a1 is executed, and a device memory that defines a device that is a work area when the control program 1a10a1 is executed. 1a10a3, and connection information 1a10a4 that defines the connection relationship between the sub-board 1b and the machine 2 and the connection relationship between the sub-board 1c and the machine 3.

  The main board 1a includes a CPU 1a1. The CPU 1a1 is connected to the bus B1. The machine control unit 1a1a that controls the machines 2 and 3 is realized by the CPU 1a1 executing the control program 1a10a1.

  The main board 1a includes a RAM (Random Access Memory) 1a2 and a volatile semiconductor storage unit 1a3 for storing data or a control program 1a10a1 used when controlling the machines 2 and 3. The data includes the device. The RAM 1a2 and the volatile semiconductor storage unit 1a3 are connected to the bus B1.

  The volatile semiconductor storage unit 1a3 is exemplified by SRAM (Static Random Access Memory) or DRAM (Dynamic Random Access Memory).

  In the first embodiment, the volatile semiconductor storage unit 1a3 corresponds to the backup target storage unit of the present invention.

  The main board 1a includes a battery 1a4 that supplies electric power P for the volatile semiconductor storage unit 1a3 to hold data or a control program 1a10a1.

  In the first embodiment, the battery 1a4 corresponds to the monitoring target hardware of the present invention.

  Main board 1a includes a voltage sensor 1a5 for detecting the voltage of battery 1a4. The voltage sensor 1a5 is connected to the bus B1.

  The volatile semiconductor storage unit 1a3 is a case where the power supply of the programmable controller 1 is turned off or the system power supply supplying the system power to the programmable controller 1 is interrupted by receiving the supply of power P from the battery 1a4. In addition, the data or the control program 1a10a1 can be kept.

  In the first embodiment, the volatile semiconductor storage unit 1a3 is a system that turns off the power of the programmable controller 1 or supplies system power to the programmable controller 1 if the voltage supplied from the battery 1a4 is 1.2V or higher. It is assumed that the data or control program 1a10a1 can continue to be retained even when the power supply fails.

  That is, when the battery 1a4 is consumed, deteriorated, or failed and the voltage supplied from the battery 1a4 falls below 1.2V, the volatile semiconductor storage unit 1a3 is turned off or the programmable controller 1 is turned off. If a system power supply that supplies system power fails, the data or the control program 1a10a1 cannot be retained. That is, when the voltage supplied from the battery 1a4 falls below 1.2V, the data in the volatile semiconductor storage unit 1a3 or the control program 1a10a1 disappears.

  When executing the control program 1a10a1, the CPU 1a1 loads the control program 1a10a1 into the RAM 1a2 or the volatile semiconductor storage unit 1a3 and executes it. Whether the control program 1a10a1 is loaded into the RAM 1a2 or the volatile semiconductor storage unit 1a3 is described in the control program 1a10a1.

  A part of the control program 1a10a1 may be arranged in the RAM 1a2, and another part of the control program 1a10a1 may be arranged in the volatile semiconductor storage unit 1a3, or the whole control program 1a10a1 may be arranged in the volatile semiconductor storage unit 1a3. May be.

  When executing the control program 1a10a1, the CPU 1a1 arranges data to be used in the RAM 1a2 or the volatile semiconductor storage unit 1a3. The data includes the device. Whether the data is stored in the RAM 1a2 or the volatile semiconductor storage unit 1a3 is described in the control program 1a10a1 or the device memory 1a10a3.

  A part of the data may be arranged in the RAM 1a2, and another part of the data may be arranged in the volatile semiconductor storage unit 1a3, or the whole data may be arranged in the volatile semiconductor storage unit 1a3.

  The main board 1a includes a backup storage unit 1a6a that stores data stored in the volatile semiconductor storage unit 1a3 or the control program 1a10a1 as a backup.

  In the first embodiment, the backup storage unit 1a6a is a removable nonvolatile storage member, and is inserted into the slot 1a6 connected to the bus B1. The backup storage unit 1a6a is exemplified by an SD card (registered trademark), CompactFlash (registered trademark), USB memory, or DVD (Digital Versatile Disc).

  If the backup storage unit 1a6a is a removable nonvolatile storage member, the portability of the backed up data or the control program 1a10a1 is improved.

  Note that the backup storage unit 1a6a may be a non-removable nonvolatile storage member. The non-removable nonvolatile memory member is exemplified by SSD or eMMC.

  If the backup storage unit 1a6a is a non-removable nonvolatile storage member, the slot 1a6 is not necessary, so that the mounting area of the main board 1a can be suppressed.

  The nonvolatile semiconductor memory unit 1a10 stores threshold data 1a10c. The threshold data 1a10c includes a predetermined threshold “1.2V” for comparison with a voltage that is a value representing the state of the battery 1a4 that is the monitoring target hardware.

  In the first embodiment, the value indicating the state of the monitoring target hardware is a value indicating the degree of consumption, deterioration, or failure of the monitoring target hardware.

  In the first embodiment, the monitoring target hardware is the battery 1a4. Assuming that the initial voltage of the battery 1a4 is 1.5V, the voltage of the battery 1a4 gradually decreases from 1.5V according to the degree of consumption, deterioration, or failure. Therefore, the voltage of the battery 1a4 is a value representing the degree of consumption, deterioration, or failure of the battery 1a4.

  The nonvolatile semiconductor storage unit 1a10 stores a backup program 1a10b. As the CPU 1a1 executes the backup program 1a10b, the backup unit 1a1b is realized.

  The backup program 1a10b monitors a voltage that is a value representing the state of the battery 1a4 that is the monitoring target hardware, and determines whether or not the voltage has reached a predetermined threshold “1.2V”. 1a10b1.

  When the CPU 1a1 executes the state monitoring program 1a10b1, a state monitoring unit 1a1b1 that monitors a value indicating the state of the monitored hardware and determines whether the value has reached a predetermined threshold is realized. .

  When the state monitoring unit 1a1b1 determines that the voltage, which is a value representing the state of the battery 1a4 that is the monitoring target hardware, has reached the threshold “1.2V”, the backup program 1a10b stores the data or program in the backup target storage unit. It includes a backup processing program 1a10b2 that reads from a certain volatile semiconductor storage unit 1a3, writes to the backup storage unit 1a6a, and backs up.

  When the CPU 1a1 executes the backup processing program 1a10b2 and the state monitoring unit 1a1b1 determines that the value representing the state of the monitored hardware has reached the threshold value, the data or program is stored in the volatile semiconductor memory that is the backup target storage unit. A backup processing unit 1a1b2 that reads from the unit 1a3 and writes to the backup storage unit 1a6a is realized.

  The operation of the programmable controller 1 will be described.

  FIG. 2 is a flowchart of a process performed by the programmable controller according to the first embodiment. The CPU 1a1 periodically executes the process shown in FIG.

  In step S100, the state monitoring unit 1a1b1 monitors the voltage, which is a value representing the state of the battery 1a4 that is the monitoring target hardware, using the voltage sensor 1a5.

  In step S102, the state monitoring unit 1a1b1 determines whether or not the voltage that is a value representing the state of the battery 1a4 that is the hardware to be monitored has reached the threshold value “1.2V”.

  If the state monitoring unit 1a1b1 determines that the voltage that is the value representing the state of the battery 1a4 that is the monitoring target hardware has not reached the threshold “1.2V” (No), the process proceeds to step S100.

  If the state monitoring unit 1a1b1 determines that the voltage, which is a value representing the state of the battery 1a4 that is the monitoring target hardware, has reached the threshold value “1.2 V” (Yes), the process proceeds to step S104.

  In step S104, the backup processing unit 1a1b2 reads the data or program from the volatile semiconductor storage unit 1a3 that is the backup target storage unit, writes the data or program in the backup storage unit 1a6a, backs up, and advances the processing to step S100.

  When the backup processing unit 1a1b2 writes the data or program to the backup storage unit 1a6a and backs up, the backup date and time and the cause of the backup "battery voltage drops to the threshold value" are attached to the data or program. It is preferable that data is backed up by writing in the backup storage unit 1a6a.

  The programmable controller 1 according to the first embodiment has the following effects.

  When the battery 1a4 is consumed, deteriorated, or failed and the voltage supplied from the battery 1a4 falls below 1.2V, the volatile semiconductor storage unit 1a3 turns off the power of the programmable controller 1 or supplies power to the programmable controller 1 If the system power supply that supplies power fails, data or programs cannot be retained. That is, when the voltage supplied from the battery 1a4 falls below 1.2V, the data or program in the volatile semiconductor storage unit 1a3 is erased.

  The state monitoring unit 1a1b1 determines whether or not the voltage, which is a value representing the state of the battery 1a4 that is the monitoring target hardware, has reached the threshold “1.2V”.

  When the state monitoring unit 1a1b1 determines that the voltage, which is a value representing the state of the battery 1a4, which is the monitoring target hardware, has reached the threshold value “1.2 V”, the backup processing unit 1a1b2 stores the data or program as the backup target storage unit Are read from the volatile semiconductor storage unit 1a3 and written to the backup storage unit 1a6a.

  Thereby, the programmable controller 1 according to the first embodiment senses the consumption, deterioration, or failure of the battery 1a4 that is the monitoring target hardware, and the data or program in the volatile semiconductor storage unit 1a3 that is the backup target storage unit Before disappears, the data or program in the volatile semiconductor storage unit 1a3, which is the backup target storage unit, can be backed up to the backup storage unit 1a6a.

  Therefore, in the programmable controller 1 according to the first embodiment, data or a program in the volatile semiconductor storage unit 1a3 that is the backup target storage unit is lost due to consumption, deterioration, or failure of the battery 1a4 that is the monitoring target hardware. Can be suppressed.

  Thereby, the user can monitor the hardware state of the programmable controller 1 and suppress the work man-hours for backing up data or programs.

Embodiment 2. FIG.
FIG. 3 is a diagram of a configuration of the programmable controller according to the second embodiment. The programmable controller 10 according to the second embodiment includes a main board 10a instead of the main board 1a as compared with the programmable controller 1 according to the first embodiment shown in FIG.

  The main substrate 10a does not include the volatile semiconductor storage unit 1a3, the battery 1a4, and the voltage sensor 1a5 as compared with the main substrate 1a of the first embodiment. Therefore, in the programmable controller 10, data and programs are loaded into the RAM 1a2.

  FIG. 4 is a diagram of a configuration of the nonvolatile semiconductor memory unit of the programmable controller according to the second embodiment. The nonvolatile semiconductor memory unit 1a10 includes a memory cell group 1a10e that stores data or a program, and a controller 1a10d that controls data writing to the memory cell group 1a10e and data reading from the memory cell group 1a10e.

  The memory cell group 1a10e is exemplified by a flash memory (registered trademark).

  Each memory cell in the memory cell group 1a10e has a charge storage unit. In the case of SLC (Single Level Cell), each memory cell stores 1-bit data depending on the presence or absence of charge in the charge storage unit.

  The injection and extraction of charges to and from the charge storage unit are performed via an insulating film that covers the charge storage unit. The insulating film is consumed, deteriorated, or failed every time the charge passes. Therefore, each memory cell is consumed, deteriorated, or failed every time data is written. That is, the nonvolatile semiconductor memory unit 1a10 has a lifetime with respect to the number of data writing.

  When the non-volatile semiconductor storage unit 1a10 reaches the end of its life, data or program cannot be written, data or program cannot be held, and data or program cannot be read.

  The controller 1a10d uses the memory cell group 1a10e so that writing is not biased to a part of the memory cells, that is, writing is performed equally to all the memory cells. Further, the controller 1a10d counts and holds the number of times of data writing to the memory cell group 1a10e.

  In the second embodiment, the nonvolatile semiconductor storage unit 1a10 corresponds to the backup target storage unit of the present invention.

  In the second embodiment, the nonvolatile semiconductor storage unit 1a10 corresponds to the monitoring target hardware of the present invention.

  The initial number of data writes to the nonvolatile semiconductor memory unit 1a10 is zero. In the nonvolatile semiconductor memory unit 1a10, the insulating film is consumed, deteriorated, or failed every time data is written. Therefore, the data write count of the nonvolatile semiconductor memory unit 1a10 is a value representing the degree of consumption, deterioration, or failure of the nonvolatile semiconductor memory unit 1a10.

  The threshold data 1a10c includes a predetermined threshold “100,000 times” for comparison with the number of times of data writing, which is a value representing the state of the nonvolatile semiconductor memory unit 1a10 that is the monitoring target hardware.

  The operation of the programmable controller 10 will be described.

  The flowchart showing the process of the programmable controller 10 according to the second embodiment is the same as the flowchart showing the process of the programmable controller 1 according to the first embodiment shown in FIG. Therefore, with reference to FIG. 2, the process of the programmable controller 10 concerning Embodiment 2 is demonstrated.

  In step S100, the state monitoring unit 1a1b1 monitors the controller 1a10d in the non-volatile semiconductor storage unit 1a10 by monitoring the number of data writes that is a value representing the state of the non-volatile semiconductor storage unit 1a10 that is the monitoring target hardware. Monitor.

  In step S102, the state monitoring unit 1a1b1 determines whether or not the number of times of data writing, which is a value representing the state of the nonvolatile semiconductor storage unit 1a10 that is the monitoring target hardware, has reached the threshold “100,000 times”.

  If the state monitoring unit 1a1b1 determines that the number of data writes, which is a value representing the state of the nonvolatile semiconductor storage unit 1a10 that is the monitoring target hardware, has not reached the threshold “100,000 times” (No), the process is performed in step S100. Proceed to

  If the state monitoring unit 1a1b1 determines that the number of data writings, which is a value representing the state of the nonvolatile semiconductor storage unit 1a10 that is the monitoring target hardware, has reached the threshold “100,000 times” (Yes), the process proceeds to step S104. Proceed.

  In step S104, the backup processing unit 1a1b2 reads the data or program from the nonvolatile semiconductor storage unit 1a10 that is the backup target storage unit, writes the data or program in the backup storage unit 1a6a, backs up, and advances the processing to step S100.

  When the backup processing unit 1a1b2 writes data or a program to the backup storage unit 1a6a and backs up, the backup date and time and the cause of the backup “the number of times the write has reached the threshold” are attached to the data or program. It is preferable that data is backed up by writing in the backup storage unit 1a6a.

  The programmable controller 10 according to the second embodiment has the following effects.

  In the nonvolatile semiconductor memory unit 1a10 that is the monitoring target hardware, the insulating film is consumed, deteriorated, or failed every time data or a program is written. That is, the nonvolatile semiconductor memory unit 1a10 has a lifetime with respect to the number of data or program writes. When the non-volatile semiconductor storage unit 1a10 reaches the end of its life, data or program cannot be written, data or program cannot be held, and data or program cannot be read.

  The state monitoring unit 1a1b1 determines whether or not the number of times of data writing, which is a value representing the state of the nonvolatile semiconductor storage unit 1a10 that is the monitoring target hardware, has reached the threshold “100,000 times”.

  When the state monitoring unit 1a1b1 determines that the number of times of data writing, which is a value indicating the state of the nonvolatile semiconductor storage unit 1a10 that is the monitoring target hardware, has reached the threshold “100,000 times”, the backup processing unit 1a1b2 The program is read from the non-volatile semiconductor storage unit 1a10 that is a backup target storage unit and written to the backup storage unit 1a6a.

  As a result, the programmable controller 10 according to the second embodiment senses the consumption, deterioration, or failure of the nonvolatile semiconductor storage unit 1a10 that is the monitoring target hardware, and the nonvolatile controller 10a in the nonvolatile semiconductor storage unit 1a10 that is the backup target storage unit Before the data or program is lost, the data or program in the non-volatile semiconductor storage unit 1a10, which is the backup target storage unit, can be backed up to the backup storage unit 1a6a.

  Therefore, in the programmable controller 10 according to the second embodiment, the data or program in the nonvolatile semiconductor storage unit 1a10 that is the backup target storage unit is lost due to the consumption, deterioration, or failure of the nonvolatile semiconductor storage unit 1a10 that is the monitoring target hardware. It can be suppressed from being lost.

  Thereby, it is possible for the user to monitor the hardware state of the programmable controller 10 and suppress the work man-hours for backing up the project data 1a10a.

Embodiment 3 FIG.
FIG. 5 is a diagram illustrating a configuration of a programmable controller according to the third embodiment. When compared with the programmable controller 1 according to the first embodiment, the programmable controller 20 according to the third embodiment includes a main board 20a instead of the main board 1a.

  Compared with main board 1a of the first embodiment, main board 20a does not include voltage sensor 1a5.

  The main board 20a further includes a temperature sensor 1a11 that measures the temperature of the main board 20a as compared with the main board 1a of the first embodiment.

  In Embodiment 3, the volatile semiconductor storage unit 1a3 or the nonvolatile semiconductor storage unit 1a10 corresponds to the backup target storage unit of the present invention.

  In the third embodiment, the main board 20a corresponds to the monitoring target hardware of the present invention.

  The temperature of the main board 20a rises because the temperature of components mounted on the main board 20a rises. Accordingly, when the component mounted on the main board 20a is consumed, deteriorated, or failed, and the temperature of the component rises above the temperature on the part specification, the temperature of the main board 20a rises above the temperature on the product specification. To do. Therefore, the temperature of the main board 20a is a value representing the degree of wear, deterioration, or failure of components mounted on the main board 20a.

  When the temperature of the main board 20a exceeds the temperature in the product specification, each part of the main board 20a or each part on the main board 20a is consumed, deteriorated, or malfunctioned, and the volatile semiconductor storage unit 1a3 or the nonvolatile semiconductor storage unit 1a10. The data or program stored in the memory is lost or cannot be read.

  The threshold data 1a10c includes a predetermined threshold “45 ° C.” for comparison with a temperature that is a value representing the state of the main board 20a that is the monitoring target hardware.

  The temperature sensor 1a11 may be mounted on the main board 20a, or may be mounted on a housing that houses the main board 20a. The temperature of the atmosphere in the housing has a correlation with the temperature of the main board 20a. Therefore, the temperature sensor 1a11 may be mounted on a housing that houses the main board 20a and measure the temperature of the atmosphere in the housing.

  Further, when the temperature sensor 1a11 is mounted on the main board 20a, it may be mounted in the vicinity of the consumable part. The consumable part is exemplified by an electrolytic capacitor. With an electrolytic capacitor, the electrolyte gradually loses with use and the capacitance decreases, so the temperature rises. That is, the temperature of the electrolytic capacitor rises due to wear, deterioration, or failure.

  Mounting the temperature sensor 1a11 in the vicinity of the consumable component means that the temperature sensor 1a11 is mounted in a place where the distance between the temperature sensor 1a11 and the consumable component is shorter than the distance between the temperature sensor 1a11 and other components.

  Further, when the temperature sensor 1a11 is mounted on the main board 20a, it may be mounted in the vicinity of a component whose temperature rises due to wear, deterioration or failure. The communication interface 1a7 is exemplified as a component whose temperature rises due to wear, deterioration, or failure. Since the communication interface 1a7 has analog components that transmit signals over a wired network or a wireless network, the temperature rises due to wear, deterioration, or failure. The analog component is exemplified by an operational amplifier.

  Mounting the temperature sensor 1a11 in the vicinity of a component that increases in temperature due to wear, deterioration, or failure means that the distance between the temperature sensor 1a11 and the component that increases in temperature due to wear, deterioration, or failure is the same as the temperature sensor 1a11 and other components. Mounting in a place that is shorter than the distance between.

  The operation of the programmable controller 20 will be described.

  The flowchart showing the process of the programmable controller 20 according to the third embodiment is the same as the flowchart showing the process of the programmable controller 1 according to the first embodiment shown in FIG. Therefore, with reference to FIG. 2, the process of the programmable controller 20 concerning Embodiment 3 is demonstrated.

  In step S100, the state monitoring unit 1a1b1 monitors the temperature, which is a value representing the state of the main board 20a, which is the monitoring target hardware, using the temperature sensor 1a11.

  In step S102, the state monitoring unit 1a1b1 determines whether or not the temperature that is a value representing the state of the main board 20a that is the monitoring target hardware has reached the threshold “45 ° C.”.

  If the state monitoring unit 1a1b1 determines that the temperature, which is a value representing the state of the main board 20a that is the monitoring target hardware, has not reached the threshold “45 ° C.” (No), the process proceeds to step S100.

  If the state monitoring unit 1a1b1 determines that the temperature, which is a value representing the state of the main board 20a that is the monitoring target hardware, has reached the threshold “45 ° C.” (Yes), the process proceeds to step S104.

  In step S104, the backup processing unit 1a1b2 reads the data or program from the volatile semiconductor storage unit 1a3 that is the backup target storage unit, writes the data or program in the backup storage unit 1a6a, backs up, and advances the processing to step S100. Alternatively, in step S104, the backup processing unit 1a1b2 reads data or a program from the nonvolatile semiconductor storage unit 1a10 that is a backup target storage unit, writes the data or program in the backup storage unit 1a6a, backs up, and advances the processing to step S100.

  When the backup processing unit 1a1b2 writes the data or program to the backup storage unit 1a6a and backs up, the backup date and time and the cause of the backup “temperature reaches a threshold” are attached to the data or program, It is preferable to perform backup by writing to the backup storage unit 1a6a.

  The programmable controller 20 according to the third embodiment has the following effects.

  When the component mounted on the main board 20a that is the monitoring target hardware is consumed, deteriorated, or failed, and the temperature of the component rises above the temperature in the component specifications, the temperature of the main board 20a that is the monitoring target hardware Rises above the product specifications.

  When the temperature of the main board 20a exceeds the temperature in the product specification, each part of the main board 20a or each part on the main board 20a is consumed, deteriorated, or malfunctioned, and the volatile semiconductor storage unit 1a3 or the nonvolatile semiconductor storage unit 1a10. The data or program stored in the memory is lost or cannot be read.

  The state monitoring unit 1a1b1 determines whether or not the temperature, which is a value representing the state of the main board 20a that is the monitoring target hardware, has reached the threshold “45 ° C.”.

  When the state monitoring unit 1a1b1 determines that the temperature, which is a value representing the state of the main board 20a, which is the monitoring target hardware, has reached the threshold “45 ° C.”, the backup processing unit 1a1b2 stores the data or program as the backup target storage unit Are read from the volatile semiconductor storage unit 1a3 and written to the backup storage unit 1a6a. Alternatively, the backup processing unit 1a1b2 reads data or a program from the nonvolatile semiconductor storage unit 1a10 that is a backup target storage unit and writes the data or program to the backup storage unit 1a6a.

  As a result, the programmable controller 20 according to the third embodiment senses the consumption, deterioration, or failure of the components mounted on the main board 20a that is the monitoring target hardware, and the volatile semiconductor memory that is the backup target storage unit. Before the data or program in the unit 1a3 is lost, the data or program in the volatile semiconductor storage unit 1a3, which is the backup target storage unit, can be backed up to the backup storage unit 1a6a. Alternatively, the programmable controller 20 according to the third embodiment senses wear, deterioration, or failure of components mounted on the main board 20a that is monitoring target hardware, and is a non-volatile semiconductor storage unit that is a backup target storage unit Before the data or program in 1a10 is lost, the data or program in the nonvolatile semiconductor storage unit 1a10, which is the backup target storage unit, can be backed up to the backup storage unit 1a6a.

  Therefore, the programmable controller 20 according to the third embodiment has the data in the volatile semiconductor storage unit 1a3 that is the backup target storage unit due to wear, deterioration, or failure of the components mounted on the main board 20a that is the monitoring target hardware. Or it can suppress that a program is lost. Alternatively, the programmable controller 20 according to the third embodiment includes data in the nonvolatile semiconductor storage unit 1a10 that is a backup target storage unit due to wear, deterioration, or failure of components mounted on the main board 20a that is monitoring target hardware. Or it can suppress that a program is lost.

  Thereby, the user can monitor the hardware state of the programmable controller 20, and can suppress the man-hours which back up data or a program.

Embodiment 4 FIG.
FIG. 6 is a diagram illustrating a configuration of a programmable controller according to the fourth embodiment. When compared with the programmable controller 1 according to the first embodiment, the programmable controller 30 according to the fourth embodiment includes a main board 30a instead of the main board 1a.

  Compared with the main substrate 1a of the first embodiment, the main substrate 30a does not include the volatile semiconductor storage unit 1a3, the battery 1a4, and the voltage sensor 1a5. Accordingly, in the programmable controller 30, the data and control program 1a10a1 is loaded into the RAM 1a2.

  The communication interface 1a7 of the main board 30a communicates with the external device 31 via a wired or wireless network N.

  The nonvolatile semiconductor storage unit 1a10 stores a communication parameter 1a10f that represents a physical setting of communication between the communication interface 1a7 and the external device 31.

  Examples of the communication parameter 1a10f include communication speed, frame size, distinction between clock masters and clock slaves, distinction between MDI (Medium Dependent Interface) and MDI-X (Medium Dependent Interface Crossover).

  In the fourth embodiment, the nonvolatile semiconductor storage unit 1a10 corresponds to the backup target storage unit of the present invention.

  In the fourth embodiment, the communication interface 1a7 corresponds to the monitoring target hardware of the present invention.

  Since the communication interface 1a7 includes analog components that transmit signals over a wired network or a wireless network, the communication interface 1a7 is consumed, deteriorated, or failed.

  When the communication interface 1a7 is not consumed, deteriorated, or malfunctioned, the frequency of communication failure between the communication interface 1a7 and the external device 31 is very low. The communication interface 1a7 retries communication when a communication failure with the external device 31 occurs.

  When the communication interface 1a7 is consumed, deteriorated, or malfunctioned, the frequency of communication failure between the communication interface 1a7 and the external device 31 increases. Then, communication failure between the communication interface 1a7 and the external device 31 occurs continuously a plurality of times. Therefore, the number of continuous occurrences of communication failure between the communication interface 1a7 and the external device 31 is a value representing the degree of wear, deterioration, or failure of the communication interface 1a7.

  When the communication interface 1a7 is further consumed, deteriorated, or broken down, communication between the communication interface 1a7 and the external device 31 becomes impossible, and the external device 31 stores the communication parameter 1a10f stored in the nonvolatile semiconductor storage unit 1a10 or The project data 1a10a cannot be read.

  The threshold data 1a10c includes a predetermined threshold “3 times” for comparison with the number of consecutive communication failures that is a value representing the state of the communication interface 1a7 that is the monitoring target hardware.

  The operation of the programmable controller 30 will be described.

  The flowchart showing the process of the programmable controller 30 according to the fourth embodiment is the same as the flowchart showing the process of the programmable controller 1 according to the first embodiment shown in FIG. Therefore, the process of the programmable controller 30 according to the fourth embodiment will be described with reference to FIG.

  In step S100, the state monitoring unit 1a1b1 monitors the communication interface 1a7 by monitoring the communication interface 1a7, which is a value representing the state of the communication interface 1a7 that is the monitoring target hardware.

  In step S102, the state monitoring unit 1a1b1 determines whether or not the number of consecutive communication failures, which is a value representing the state of the communication interface 1a7 that is the monitoring target hardware, has reached the threshold “3 times”.

  If the state monitoring unit 1a1b1 determines that the number of consecutive communication failures, which is a value representing the state of the communication interface 1a7 that is the monitoring target hardware, has not reached the threshold “3 times” (No), the process proceeds to step S100.

  If the state monitoring unit 1a1b1 determines that the number of consecutive communication failures, which is a value representing the state of the communication interface 1a7 that is the monitoring target hardware, has reached the threshold “3 times” (Yes), the process proceeds to step S104.

  In step S104, the backup processing unit 1a1b2 reads data or a program including the communication parameter 1a10f from the nonvolatile semiconductor storage unit 1a10 that is the backup target storage unit, writes the data or program in the backup storage unit 1a6a, and backs up, and the process proceeds to step S100. .

  When the backup processing unit 1a1b2 writes data or a program to the backup storage unit 1a6a for backup, the backup date and time and the cause of the backup “the number of consecutive communication failures reaches the threshold” are attached to the data or program. Thus, it is preferable to write in the backup storage unit 1a6a for backup.

  The programmable controller 30 according to the fourth embodiment has the following effects.

  When the communication interface 1a7, which is the hardware to be monitored, is consumed, deteriorated, or failed, the frequency of communication errors, that is, communication failures between the communication interface 1a7 and the external device 31 increases. Then, communication failure between the communication interface 1a7 and the external device 31 occurs continuously a plurality of times.

  When the communication interface 1a7 is further consumed, deteriorated, or failed, communication between the communication interface 1a7 and the external device 31 becomes impossible, and the external device 31 sets the communication parameter 1a10f stored in the nonvolatile semiconductor storage unit 1a10. The data or program that it contains cannot be read.

  The state monitoring unit 1a1b1 determines whether or not the number of consecutive communication failures, which is a value representing the state of the communication interface 1a7 that is the monitoring target hardware, has reached the threshold “3 times”.

  The backup processing unit 1a1b2 includes the communication parameter 1a10f if the state monitoring unit 1a1b1 determines that the communication continuous failure count, which is a value representing the state of the communication interface 1a7 that is the monitoring target hardware, has reached the threshold “3 times”. Data or a program is read from the non-volatile semiconductor storage unit 1a10 that is a backup target storage unit and written to the backup storage unit 1a6a.

  Thereby, the programmable controller 30 according to the fourth embodiment senses the consumption, deterioration, or failure of the communication interface 1a7 that is the monitoring target hardware, and the communication parameters in the nonvolatile semiconductor storage unit 1a10 that is the backup target storage unit. Data or programs including 1a10f can be backed up in the backup storage unit 1a6a.

  Therefore, the programmable controller 30 according to the fourth embodiment indicates that data or a program including the communication parameter 1a10f in the nonvolatile semiconductor memory unit 1a10 is lost due to consumption, deterioration, or failure of the communication interface 1a7 that is the monitoring target hardware. Can be suppressed.

  Thereby, the user can monitor the hardware state of the programmable controller 30, and can suppress the man-hours which back up data or a program.

  In the fourth embodiment, the monitoring target hardware is the communication interface 1a7. However, even if the monitoring target hardware is the USB interface 1a8 or the bus interface 1a9, the USB communication continuous failure count or the bus communication continuous failure count is monitored. good.

Embodiment 5 FIG.
FIG. 7 is a diagram illustrating a configuration of a control system according to the fifth embodiment. The control system 40 according to the fifth embodiment includes a programmable controller 41 and an external device 50 that communicates with the programmable controller 41.

  Compared with the programmable controller 1 according to the first embodiment shown in FIG. 1, the programmable controller 41 includes a main board 41a instead of the main board 1a.

  The main board 41a further includes the temperature sensor 1a11 described in the third embodiment as compared with the main board 1a of the first embodiment.

  The nonvolatile semiconductor storage unit 1a10 stores the communication parameter 1a10f described in the fourth embodiment.

  The communication interface 1a7 of the main board 41a communicates with the external device 50 via a wired or wireless network N.

  FIG. 8 is a diagram illustrating a hardware configuration of an external device of the control system according to the fifth embodiment. In the fifth embodiment, the external device 50 is a computer. In the computer, a CPU 51, a RAM 52, a ROM (Read Only Memory) 53, a storage unit 54, an input unit 55, a display unit 56, a communication interface 57, and a storage unit 59 which is a removable storage member are inserted. Slot 58. The CPU 51, RAM 52, ROM 53, storage unit 54, input unit 55, display unit 56, communication interface 57, and slot 58 are connected via the bus B.

  The CPU 51 executes programs stored in the ROM 53 and the storage unit 54 while using the RAM 52 as a work area. The program stored in the ROM 53 is exemplified by BIOS (Basic Input / Output System) or UEFI (Unified Extensible Firmware Interface). Examples of the program stored in the storage unit 54 include an operating system program and an engineering tool program. The storage unit 54 is exemplified by an SSD or an HDD (Hard Disk Drive).

  The input unit 55 receives an operation input from the user. The input unit 55 is exemplified by a keyboard or a mouse. The display unit 56 displays characters and images. The display unit 56 is exemplified by a liquid crystal display device. The communication interface 57 communicates with the programmable controller 41.

  FIG. 9 is a functional block diagram of an external device of the control system according to the fifth embodiment. The storage unit 54 stores an engineering tool program 54a. The engineering tool unit 51a is realized by the CPU 51 executing the engineering tool program 54a.

  The engineering tool program 54a includes a project data creation program 54a1 that creates project data 1a10a based on an input from the user and transmits it to the programmable controller 41.

  When the CPU 51 executes the project data creation program 54a1, the project data creation unit 51a1 that creates the project data 1a10a based on the input from the user and transmits it to the programmable controller 41 is realized.

  The engineering tool program 54a includes a backup program creation program 54a2 that creates the backup program 1a10b based on the input from the user and transmits it to the programmable controller 41.

  When the CPU 51 executes the backup program creation program 54a2, the backup program creation unit 51a2 that creates the backup program 1a10b based on the input from the user and transmits it to the programmable controller 41 is realized.

  The engineering tool program 54a includes a threshold data creation program 54a3 that creates threshold data 1a10c based on input from the user and transmits the threshold data 1a10c to the programmable controller 41.

  When the CPU 51 executes the threshold data creation program 54a3, the threshold data creation unit 51a3 that creates the threshold data 1a10c based on the input from the user and transmits it to the programmable controller 41 is realized.

  The threshold data creation program 54a3 corresponds to the necessity of monitoring one or more monitored hardware and one or more thresholds for determining the status of one or more monitored hardware, respectively. It includes an input screen display program 54a3a that displays an input screen for input.

  By executing the input screen display program 54a3a by the CPU 51, one or a plurality of items for determining whether or not one or a plurality of monitoring target hardware needs to be monitored and the state of the one or a plurality of monitoring target hardwares, respectively. An input screen display unit 51a3a for displaying an input screen for inputting the threshold value in association with each other is realized.

  The threshold data creation program 54a3 includes an input reception program 54a3b that receives input to the input screen.

  When the CPU 51 executes the threshold data creation program 54a3, an input receiving unit 51a3b that receives an input on the input screen is realized.

  The threshold data creation program 54a3 has a threshold value that correlates the necessity of monitoring one or more monitoring target hardware and one or more threshold values based on the input received by the input receiving unit 51a3b. A creation program 54a3c for creating data 1a10c is included.

  When the CPU 51 executes the threshold data creation program 54a3, based on the input received by the input receiving unit 51a3b, whether or not one or more monitoring target hardware needs to be monitored, one or more thresholds, The creation unit 51a3c for creating the threshold data 1a10c having the associations is realized.

  The threshold data creation program 54a3 includes a transmission program 54a3d that transmits the threshold data 1a10c created by the creation unit 51a3c to the programmable controller 41.

  When the CPU 51 executes the transmission program 54a3d, the transmission unit 51a3d that transmits the threshold data 1a10c created by the creation unit 51a3c to the programmable controller 41 is realized.

  The operation of the control system 40 will be described.

  FIG. 10 is a flowchart of a process performed by an external device of the control system according to the fifth embodiment.

  In step S200, the input screen display unit 51a3a determines one or more threshold values for determining whether or not one or a plurality of monitoring target hardware needs to be monitored and the state of the one or more monitoring target hardware, respectively. Are displayed on the display unit 56 in association with each other.

  In step S202, the input receiving unit 51a3b receives an input to the input screen.

  FIG. 11 is a diagram illustrating a display surface of the display unit of the external device of the control system according to the fifth embodiment. An input screen 60 is displayed on the display surface 56a of the display unit 56 by the input screen display unit 51a3a. The input screen 60 includes a connection information input unit 61 for inputting information for uniquely specifying the programmable controller 41 to which threshold data 1a10c created from the present time is transmitted, and one or a plurality of monitoring target hardware. And a backup setting input unit 62 for inputting the necessity of monitoring and one or more threshold values in association with each other.

  The connection information input unit 61 includes a manufacturing serial number input field 61a for inputting a manufacturing serial number of the programmable controller 41, an IP address input field 61b for inputting an IPv4 (Internet Protocol version 4) address of the programmable controller 41, and a programmable controller. A model name input field 61c for inputting 41 model names.

  The backup setting input unit 62 includes setting input fields 62a, 62b, 62c, and 62d for inputting the necessity / unnecessity of monitoring of four monitored hardware and the four threshold values in association with each other.

  In the manufacturing serial number input field 61a, “120300 ***”, which is the manufacturing serial number of the programmable controller 41, is input by the user.

  In the IP address input field 61b, “192.168.0.1”, which is the IPv4 address of the programmable controller 41, is input by the user.

  In the model name input field 61c, “R08CPU” which is the model name of the programmable controller 41 is input by the user.

  The setting input column 62a includes a necessity input column 62a1 for inputting necessity of monitoring of the battery 1a4 which is the monitoring target hardware.

  In the necessity input column 62a1, “necessary” indicating that the battery 1a4 as the monitoring target hardware is monitored is input by the user.

  The setting input field 62a includes a threshold value input field 62a2 for inputting a threshold value for determining the state of the battery 1a4 that is the monitoring target hardware.

  In the threshold value input column 62a2, a threshold value “1.2V” of the voltage of the battery 1a4 for determining the state of the battery 1a4 as the monitoring target hardware is input by the user.

  The setting input column 62b has a necessity input column 62b1 for inputting necessity of monitoring of the non-volatile semiconductor storage unit 1a10 which is hardware to be monitored.

  In the necessity input column 62b1, “necessary” indicating that the nonvolatile semiconductor storage unit 1a10 that is the monitoring target hardware is monitored is input by the user.

  The setting input field 62b includes a threshold value input field 62b2 for inputting a threshold value for determining the state of the nonvolatile semiconductor memory unit 1a10 that is the monitoring target hardware.

  In the threshold value input column 62b2, a threshold value “100,000 times” of the number of times of writing to the nonvolatile semiconductor memory unit 1a10 for determining the state of the nonvolatile semiconductor memory unit 1a10 that is the monitoring target hardware is input by the user. Yes.

  The setting input column 62c includes a necessity input column 62c1 for inputting necessity of monitoring of the main board 41a which is the monitoring target hardware.

  In the necessity input column 62c1, “No” indicating that monitoring of the main board 41a as the monitoring target hardware is not performed is input by the user.

  The setting input field 62c includes a threshold value input field 62c2 for inputting a threshold value for determining the state of the main board 41a that is the monitoring target hardware.

  In the threshold value input column 62c2, since the main board 41a that is the monitoring target hardware is not monitored, the threshold value for determining the state of the main board 41a is not input by the user.

  The setting input field 62d has a necessity input field 62d1 for inputting necessity of monitoring of the communication interface 1a7 which is the monitoring target hardware.

  In the necessity input column 62d1, “necessary” indicating that the communication interface 1a7 that is the monitoring target hardware is monitored is input by the user.

  The setting input field 62d has a threshold value input field 62d2 for inputting a threshold value for determining the state of the communication interface 1a7 that is the monitoring target hardware.

  In the threshold value input column 62d2, the threshold value “three times” of the communication continuous failure number of the communication interface 1a7 for determining the state of the communication interface 1a7 that is the monitoring target hardware is input by the user.

  Referring to FIG. 10 again, the creating unit 51a3c determines whether or not one or a plurality of monitoring target hardware needs to be monitored based on the input received by the input receiving unit 51a3b and the one or more monitoring units in step S204. Threshold data 1a10c having threshold values associated with each other is created.

  In step S206, the transmission unit 51a3d transmits the threshold data 1a10c created by the creation unit 51a3c to the programmable controller 41. When the CPU 1a1 of the programmable controller 41 receives the threshold data 1a10c from the external device 50, the CPU 1a1 writes the received threshold data 1a10c into the nonvolatile semiconductor storage unit 1a10.

  The CPU 1a1 of the programmable controller 41 executes the process shown in the flowchart of FIG. 2 described in the first embodiment.

  Based on the threshold data 1a10c received from the external device 50, the state monitoring unit 1a1b1 of the programmable controller 41 monitors a voltage that is a value representing the state of the battery 1a4 that is the monitoring target hardware, and the voltage is the threshold “1. It is determined whether or not “2V” has been reached. When the state monitoring unit 1a1b1 determines that the voltage of the battery 1a4 has reached the threshold value “1.2V”, the backup processing unit 1a1b2 of the programmable controller 41 stores the data or program as the backup target storage unit volatile semiconductor storage unit 1a3. Are backed up and written to the backup storage unit 1a6a for backup.

  When the backup processing unit 1a1b2 writes data or a program to the backup storage unit 1a6a for backup, the backup date and time, the cause of the backup “battery voltage drops to the threshold”, and the serial number of the programmable controller 41 manufactured It is preferable that the number, the IPv4 address, and the model name are attached to the data or program and written in the backup storage unit 1a6a for backup.

  Based on the threshold data 1a10c received from the external device 50, the state monitoring unit 1a1b1 of the programmable controller 41 monitors the number of writes, which is a value representing the state of the nonvolatile semiconductor storage unit 1a10 that is the monitored hardware, and writes It is determined whether or not the number of times has reached the threshold “100,000 times”. When the state monitoring unit 1a1b1 determines that the number of times of writing in the nonvolatile semiconductor storage unit 1a10 has reached the threshold value “100,000 times”, the backup processing unit 1a1b2 of the programmable controller 41 stores the data or program as a backup target storage unit. Is read from the conductive semiconductor storage unit 1a10 and written to the backup storage unit 1a6a.

  When the backup processing unit 1a1b2 writes data or a program to the backup storage unit 1a6a and backs up, the backup date and time, the cause of the backup “the number of writes reaches the threshold”, and the serial number of the programmable controller 41 manufactured It is preferable that the number, the IPv4 address, and the model name are attached to the data or program and written in the backup storage unit 1a6a for backup.

  Based on the threshold data 1a10c received from the external device 50, the state monitoring unit 1a1b1 of the programmable controller 41 does not monitor the temperature that is a value representing the state of the main board 41a that is the hardware to be monitored.

  Based on the threshold data 1a10c received from the external device 50, the state monitoring unit 1a1b1 of the programmable controller 41 monitors the number of continuous communication failures, which is a value representing the state of the communication interface 1a7 that is the monitored hardware, and continues communication. It is determined whether or not the number of failures has reached the threshold value “3 times”. When the status monitoring unit 1a1b1 determines that the number of consecutive communication failures of the communication interface 1a7 has reached the threshold “3 times”, the backup processing unit 1a1b2 of the programmable controller 41 stores the data or program as a non-volatile semiconductor that is a backup target storage unit Read from the storage unit 1a10 or the volatile semiconductor storage unit 1a3 and write to the backup storage unit 1a6a.

  When the backup processing unit 1a1b2 writes data or a program to the backup storage unit 1a6a for backup, the backup date and time, the cause of the backup “the number of consecutive communication failures reaches the threshold”, and the programmable controller 41 It is preferable that the manufacturing serial number, the IPv4 address, and the model name are attached to the data or program and written in the backup storage unit 1a6a for backup.

  The control system 40 according to the fifth embodiment has the following effects.

  The control system 40 associates the necessity of monitoring one or more monitored hardware with one or more thresholds for determining the status of the one or more monitored hardware, respectively. Threshold data 1a10c can be created.

  Thereby, the control system 40 can suppress unnecessary monitoring of hardware and can suppress the processing load of the programmable controller 41. In addition, the control system 40 can suppress unnecessary monitoring of hardware and suppress the use area of the backup storage unit 1a6a.

  In addition, when there are a plurality of hardware to be monitored, the control system 40 determines whether monitoring of the plurality of hardware to be monitored is necessary and a plurality of thresholds for determining the states of the plurality of hardware to be monitored, respectively. Input can be performed intuitively. As a result, the control system 40 can easily input, without omission, the necessity of monitoring a plurality of monitored hardware and a plurality of threshold values for determining the status of each of the monitored hardware. Can be made possible.

  In the fifth embodiment, the external device 50 is a computer, but the external device 50 may be a programmable display (JIS B 3551: 2012, programmable display).

  In the fifth embodiment, the external device 50 transmits the threshold data 1a10c to the programmable controller 41. However, the external device 50 may write the threshold data 1a10c into the removable storage unit 59, and the user may take out the storage unit 59 from the external device 50 and insert it into the slot 1a6 of the programmable controller 41.

  Thereby, even if it is a case where the external apparatus 50 and the programmable controller 41 cannot communicate, the programmable controller 41 can use threshold value data 1a10c.

  In the fifth embodiment, the external device 50 creates the threshold data 1a10c. However, the present invention is not limited to this.

  FIG. 12 is a diagram illustrating a configuration of a programmable controller according to another control system example of the fifth embodiment. When compared with the programmable controller 41, the programmable controller 70 according to another example of the fifth embodiment includes a main board 70a instead of the main board 41a.

  The main board 71a further includes a display unit 1a12 that displays characters and images, and an input unit 1a13 that receives an operation input from the user, as compared with the main board 41a of the fifth embodiment. The display unit 1a12 is exemplified by a liquid crystal display device. The input unit 1a13 is exemplified by a physical button or a touch panel.

  The backup program 1a10b in the nonvolatile semiconductor storage unit 1a10 further includes a threshold data creation program 1a10b3. When the CPU 1a1 executes the threshold data creation program 1a10b3, the threshold data creation unit 1a1b3 is realized.

  The programmable controller 70 can create the threshold data 1a10c even in a factory building that cannot communicate with the external device 50. Moreover, the programmable controller 70 can make the external device 50 unnecessary. Thereby, the programmable controller 70 can suppress cost.

Embodiment 6 FIG.
FIG. 13 is a diagram illustrating a configuration of a control system according to the sixth embodiment. The control system 80 according to the sixth embodiment includes one master programmable controller 81 that operates as a master, and a plurality of slave programmable controllers 82 and 83 that operate as slaves. The master programmable controller 81 and the slave programmable controllers 82 and 83 can communicate via a wired or wireless network N.

  In the sixth embodiment, the number of slave programmable controllers that operate as slaves is two, but the number of slave programmable controllers that operate as slaves may be one or more than two.

  FIG. 14 is a diagram illustrating a configuration of a master programmable controller of the control system according to the sixth embodiment. The master programmable controller 81 of the control system 80 according to the sixth embodiment includes a main board 81a.

  The backup program 1a10b in the nonvolatile semiconductor storage unit 1a10 of the master programmable controller 81 further receives another device backup management program 1a10b4 that receives data or a program from the slave programmable controller 82 or 83, writes it in the backup storage unit 1a6a, and backs it up. Including.

  The CPU 1a1 of the master programmable controller 81 executes the other device backup management program 1a10b4, thereby realizing the other device backup management unit 1a1b4 that receives data or a program from the slave programmable controller 82 or 83, writes it to the backup storage unit 1a6a, and backs it up. Is done.

  FIG. 15 is a diagram illustrating the contents of the backup storage unit of the master programmable controller of the control system according to the sixth embodiment.

  The backup processing unit 1a1b2 of the master programmable controller 81 reads the data or program from the backup target storage unit when the state monitoring unit 1a1b1 determines that the value representing the status of the monitoring target hardware has reached the threshold, and the backup storage unit The device backup data or program 1a6a1 is written in 1a6a for backup.

  When the other device backup management unit 1a1b4 of the master programmable controller 81 receives the data or program from the slave programmable controller 82, it writes the slave backup data or program 1a6a2 in the backup storage unit 1a6a for backup.

  When the other device backup management unit 1a1b4 of the master programmable controller 81 receives the data or program from the slave programmable controller 83, it writes the slave backup data or program 1a6a3 in the backup storage unit 1a6a for backup.

  FIG. 16 is a diagram of a configuration of the slave programmable controller of the control system according to the sixth embodiment. The slave programmable controller 82 of the control system 80 according to the sixth embodiment includes a main board 82a.

  The backup program 1a10b in the nonvolatile semiconductor storage unit 1a10 of the slave programmable controller 82 further includes a backup transmission program 1a10b5 that transmits the data or program backed up to the backup storage unit 1a6a to the master programmable controller 81.

  When the CPU 1a1 of the slave programmable controller 82 executes the backup transmission program 1a10b5, the backup transmission unit 1a1b5 that transmits the data or program backed up to the backup storage unit 1a6a to the master programmable controller 81 is realized.

  Since the configuration of the slave programmable controller 83 is the same as the configuration of the slave programmable controller 82, illustration and description are omitted.

  The operation of the slave programmable controller 82 will be described.

  FIG. 17 is a flowchart illustrating processing of the slave programmable controller of the control system according to the sixth embodiment. The backup transmission unit 1a1b5 of the slave programmable controller 82 executes the process shown in FIG. 17 when the backup processing unit 1a1b2 backs up data or programs to the backup storage unit 1a6a.

  In step S300, the backup transmission unit 1a1b5 of the slave programmable controller 82 reads the data or program backed up by the backup processing unit 1a1b2 from the backup storage unit 1a6a, transmits it to the master programmable controller 81, and ends the process.

  FIG. 18 is a flowchart of the process of the master programmable controller of the control system according to the sixth embodiment.

  The other device backup management unit 1a1b4 of the master programmable controller 81 receives data or a program from the slave programmable controller 82 in step S400.

  In step S402, the other apparatus backup management unit 1a1b4 determines whether the slave backup data or the program 1a6a2 of the transmission source slave programmable controller 82 is already in the backup storage unit 1a6a.

  If the other device backup management unit 1a1b4 determines that the slave backup data or the program 1a6a2 of the slave programmable controller 82 is not in the backup storage unit 1a6a in step S402 (No), the received data or program is transferred to the slave backup data in step S404. Alternatively, the program 1a6a2 is written in the backup storage unit 1a6a for backup.

  If the other device backup management unit 1a1b4 determines that the slave backup data or the program 1a6a2 of the slave programmable controller 82 is already in the backup storage unit 1a6a in step S402 (Yes), the received data or program and the slave backup in step S406 It is determined whether there is a difference between the data or the program 1a6a2.

  If the other device backup management unit 1a1b4 determines that there is no difference between the data or program received in step S406 and the slave backup data or program 1a6a2 (No), the other device backup management unit 1a1b4 ends the processing.

  If the other device backup management unit 1a1b4 determines that there is a difference between the data or program received in step S406 and the slave backup data or program 1a6a2 (Yes), it writes the difference in the backup storage unit 1a6a in step S408. Back up and finish processing. At this time, the other device backup management unit 1a1b4 overwrites only the portion corresponding to the difference in the slave backup data or the program 1a6a2 already in the backup management unit 1a1b4 and already exists in the backup management unit 1a1b4. It is preferable to leave the portion of the slave backup data or program 1a6a2 that does not correspond to the difference without being overwritten.

  The control system 80 according to the sixth embodiment has the following effects.

  The control system 80 can collect backup data or programs of the master programmable controller 81 and the slave programmable controllers 82 and 83 in the master programmable controller 81.

  Therefore, the user only needs to go to the master programmable controller 81 to collect the backup data or programs of the master programmable controller 81 and the slave programmable controllers 82 and 83.

  Thereby, the control system 80 performs the operation | work which a user patrols the installation place of the master programmable controller 81 and the slave programmable controllers 82 and 83 in order to collect | recover the backup data or program of the master programmable controller 81 and the slave programmable controllers 82 and 83. It can suppress, and a user's work man-hour can be suppressed.

  Moreover, since the control system 80 consolidates the backup data or programs of the master programmable controller 81 and the slave programmable controllers 82 and 83 in the master programmable controller 81, the backup data or the master programmable controller 81 and the slave programmable controllers 82 and 83 The maintainability of the program can be improved.

  In addition, since the control system 80 aggregates the backup data or programs of the slave programmable controllers 82 and 83 in the master programmable controller 81, the backup data of the slave programmable controllers 82 and 83 can be obtained even when the slave programmable controller 82 or 83 is damaged. Alternatively, since the program can be collected by the master programmable controller 81, it is possible to prevent the backup data or programs of the slave programmable controllers 82 and 83 from being lost.

Embodiment 7 FIG.
FIG. 19 is a diagram illustrating a configuration of a control system according to the seventh embodiment. The control system 90 according to the seventh embodiment includes an external device 91, one master programmable controller 92 that operates as a master, and a plurality of slave programmable controllers 93 and 94 that operate as slaves. The external device 91, master programmable controller 92, and slave programmable controllers 93 and 94 can communicate via a wired or wireless network N.

  In the seventh embodiment, the number of slave programmable controllers that operate as slaves is two. However, the number of slave programmable controllers that operate as slaves may be one or more.

  In the seventh embodiment, the external device 91 is a computer. Since the hardware configuration of the computer is the same as the hardware configuration of the external device 50 according to the fifth embodiment shown in FIG. 8, illustration and description are omitted.

  FIG. 20 is a diagram of functional blocks of an external device of the control system according to the seventh embodiment. The engineering tool program 54a further includes a restore control program 54a4 as compared with the external device 50 of the fifth embodiment shown in FIG.

  The CPU 51 executes the restore control program 54a4, thereby realizing the restore control unit 51a4.

  The restore control program 54a4 includes a list request program 54a4a that requests the master programmable controller 92 for a list of data or programs backed up in the backup storage unit 1a6a of the master programmable controller 92.

  When the CPU 51 executes the list request program 54a4a, the list request unit 51a4a that requests the master programmable controller 92 for a list of data or programs backed up in the backup storage unit 1a6a of the master programmable controller 92 is realized.

  The restore control program 54a4 includes a list display program 54a4b for displaying a list display screen for displaying a list of data or programs received by the list request unit 51a4a.

  When the CPU 51 executes the list display program 54a4b, a list display unit 51a4b that displays a list display screen for displaying a list of data or programs received by the list request unit 51a4a is realized.

  The restore control program 54a4 includes a restore input acceptance program 54a4c that accepts input of data or a program to be restored and information for uniquely specifying a restore destination programmable controller of the slave programmable controllers 93 or 94 within the list display screen.

  Restoration in which the CPU 51 executes the restore input acceptance program 54a4c to accept input of data or a program to be restored and information for uniquely specifying a restore destination programmable controller in the slave programmable controller 93 or 94 within the list display screen The input receiving unit 51a4c is realized.

  The restore control program 54a4 sends the data or program to be restored and information for uniquely specifying the restore destination programmable controller in the slave programmable controller 93 or 94 to the restore destination programmable controller in the slave programmable controller 93 or 94. A restore request transmission program 54a4d to be transmitted is included.

  When the CPU 51 executes the list display program 54a4d, the data or program to be restored and information for uniquely specifying the restore destination programmable controller in the slave programmable controller 93 or 94 are stored in the slave programmable controller 93 or 94. A restore request transmission unit 51a4d for transmitting to the restore destination programmable controller is realized.

  FIG. 21 is a diagram illustrating a configuration of a master programmable controller of the control system according to the seventh embodiment. The master programmable controller 92 of the control system 90 according to the seventh embodiment includes a main board 92a.

  Compared with the master programmable controller 81 according to the sixth embodiment shown in FIG. 14, the master programmable controller 92 according to the seventh embodiment reads the data or program to be restored from the backup storage unit 1a6a. And a restore management program 1a10b6 to be transmitted to the restore destination programmable controller in the slave programmable controller 93 or 94.

  Restore by which the CPU 1a1 of the master programmable controller 92 executes the restore management program 1a10b6 to read the data or program to be restored from the backup storage unit 1a6a and send it to the restore destination programmable controller in the slave programmable controller 93 or 94 The management unit 1a1b6 is realized.

  FIG. 22 is a diagram illustrating a configuration of a slave programmable controller of the control system according to the seventh embodiment. The slave programmable controller 93 of the control system 90 according to the seventh embodiment includes a main board 93a.

  The slave programmable controller 93 according to the seventh embodiment receives the data or program to be restored from the master programmable controller 92 as compared with the slave programmable controller 82 according to the sixth embodiment shown in FIG. Then, it further includes a restore processing program 1a10b7 for writing and restoring to the backup storage unit 1a6a or the nonvolatile semiconductor storage unit 1a10.

  Restoration in which the CPU 1a1 of the slave programmable controller 93 receives the data or program to be restored from the master programmable controller 92 and writes it to the backup storage unit 1a6a or the non-volatile semiconductor storage unit 1a10 by executing the restore processing program 1a10b7 The processing unit 1a1b7 is realized.

  The operation of the control system 90 will be described.

  FIG. 23 is a sequence diagram illustrating processing of the control system according to the seventh embodiment.

  The list request unit 51a4a of the external device 91 requests the master programmable controller 92 for a list of backup data or programs backed up in the backup storage unit 1a6a of the master programmable controller 92 in step S500.

  In step S510, the restore management unit 1a1b6 of the master programmable controller 92 transmits a list of backup data or programs backed up in the backup storage unit 1a6a to the external device 91.

  In step S502, the list display unit 51a4b of the external device 91 displays a list of backup data or programs received by the list request unit 51a4a on the display surface of the display unit 56.

  FIG. 24 is a diagram illustrating a display surface of the display unit of the external device of the control system according to the seventh embodiment. A list display screen 100 is displayed on the display surface 56b of the display unit 56 by the list display unit 51a4b. The list display screen 100 includes a backup data information display unit 101 that displays backup data or program information backed up in the backup storage unit 1a6a of the master programmable controller 92, and a restore destination slave programmable controller that restores the backup data or program. And a restore destination input unit 102 for inputting information for uniquely identifying the.

  The connection information input unit 61 includes a manufacturing serial number display field 101a for displaying the manufacturing serial number of the backup source slave programmable controller, an IP address display field 101b for displaying the IPv4 address of the backup source slave programmable controller, and a backup A model name display column 101c for displaying the model name of the original slave programmable controller, a date display column 101d for displaying the backup date, a time display column 101e for displaying the backup time, a backup trigger, And a trigger display field 101f that displays the status of the monitored hardware that has become.

  In FIG. 24, a total of five backup data from line 103 to line 107 are displayed in a list.

  The restore destination input unit 102 includes a manufacture serial number input field 102a for inputting a manufacture serial number of a slave programmable controller as a restore destination, and an IP address input field 102b for inputting an IPv4 address of the slave programmable controller as a restore destination.

  Referring to FIG. 23 again, in step S504, the restore input receiving unit 51a4c of the external device 91 inputs the information for uniquely specifying the backup data or program to be restored and the slave programmable controller to be restored to the list display screen 100. Accept within.

  Referring to FIG. 24 again, the manufacturing serial number “140300 ***” is input by the user in the manufacturing serial number input field 102a in the row 103, and the IPv4 address “192” is input in the IP address input field 102b in the row 103. .168.0.52 "has been entered by the user. Therefore, the backup data or program listed in the row 103 is restored to the slave programmable controller having the manufacturing serial number “140300 ***” and the IPv4 address “192.168.0.52”.

  Further, the manufacturing serial number “140300 ***” is input to the manufacturing serial number input field 102 a of the row 105 by the user, and the IPv4 address “192.168.8.0.” Is input to the IP address input field 102 b of the row 105. 52 "has been entered by the user. Therefore, the backup data or program listed in the row 105 is restored to the slave programmable controller having the manufacturing serial number “140300 ***” and the IPv4 address “192.168.0.52”.

  When the information input to the list display screen 100 is completed, the user clicks the execution button 110. When the execution button 110 is clicked by the user, the restore input reception unit 51a4c of the external device 91 ends the reception of information input.

  Referring to FIG. 23 again, in step S506, the restore request transmission unit 51a4d of the external device 91 transmits, to the master programmable controller 92, information that uniquely specifies the backup data or program to be restored and the slave programmable controller to be restored. To do.

  In step S512, the restore management unit 1a1b6 of the master programmable controller 92 reads the backup data or program to be restored from the backup storage unit 1a6a and transmits it to the restore destination slave programmable controller.

  In step S520, the restore processing unit 1a1b7 of the restore destination slave programmable controller writes the received backup data or program to be restored to the nonvolatile semiconductor storage unit 1a10 and the backup storage unit 1a6a to restore.

  The control system 90 according to the seventh embodiment has the following effects.

  The control system 90 displays a list of backup data or programs in the list display screen 100. Thereby, the control system 90 can enable the user to appropriately select the backup data or program to be restored while looking at the list.

  Further, the control system 90 can restore the slave programmable controller simply by operating the external device 91 without the user having to go to the installation location of the master programmable controller 92 or the restore destination slave programmable controller. Can be. Thereby, the control system 90 can suppress a user's work man-hour. When there are a plurality of slave programmable controllers as restore destinations, the control system 90 can suitably suppress the user's work man-hours.

  In the seventh embodiment, the external device 91 is a computer, but the external device 91 may be a programmable display.

  In the seventh embodiment, the external apparatus 91 accepts a restore input, but the present invention is not limited to this. The master programmable controller 92 may include the display unit 1a12 and the input unit 1a13 illustrated in FIG. 12 and execute the restore control program 54a4. Thereby, since the control system 90 can make the external apparatus 91 unnecessary, it can suppress cost. When the master programmable controller 92 includes the display unit 1a12 and the input unit 1a13 and executes the restore control program 54a4, the list request program 54a4a and the restore request transmission program 54a4d are unnecessary.

  The configuration described in the above embodiment shows an example of the contents of the present invention, and can be combined with another known technique, and can be combined with other configurations without departing from the gist of the present invention. It is also possible to omit or change the part.

  1, 10, 20, 30, 41, 70 Programmable controller, 1a1, 51 CPU, 1a1b backup unit, 1a1b1 status monitoring unit, 1a1b2 backup processing unit, 1a1b3, 51a3 threshold data creation unit, 1a1b4 Other device backup management unit, 1a1b5 backup Transmission unit, 1a1b6 restore management unit, 1a1b7 restore processing unit, 1a3 volatile semiconductor storage unit, 1a4 battery, 1a5 voltage sensor, 1a6a backup storage unit, 1a10 nonvolatile semiconductor storage unit, 1a10b backup program, 1a10c threshold data, 1a10f communication parameter 1a11 temperature sensor, 1a12 display unit, 1a13 input unit, 50, 91 external device, 51a3a input screen display unit, 51a3b input reception unit, 5 a3c creation unit, 51a3d transmission unit, 51a4 restore control unit, 51a4a list request unit, 51a4b list display unit, 51a4c restore input reception unit, 51a4d restore request transmission unit, 54 storage unit, 60 input screen, 40, 80, 90 control system , 81, 92 Master programmable controller, 82, 83, 93, 94 Slave programmable controller, 100 list display screen.

Claims (5)

A control system comprising a plurality of Programmer llama logic controllers,
Each of the plurality of programmable controllers is
A backup target storage unit for storing data or programs used in machine control; and
A backup storage unit for storing the data or program as a backup;
A state monitoring unit that monitors a value representing the state of the monitored hardware and determines whether the value has reached a predetermined threshold;
When the state monitoring unit determines that the value has reached the threshold, a backup processing unit that reads the data or program from the backup target storage unit, writes the data or program in the backup storage unit, and backs up,
With
One of the plurality of programmable controllers is:
A backup transmission unit for transmitting the data or program backed up in the backup storage unit to another one of the plurality of programmable controllers;
Another one of the plurality of programmable controllers is:
A control system further comprising: another device backup management unit that receives the data or program from one of the plurality of programmable controllers, writes the data or program in the backup storage unit, and backs up the data or program. The other apparatus backup management unit
When the data or program is received from one of the plurality of programmable controllers, if the one data or program of the plurality of programmable controllers already exists in the backup storage unit, the backup storage unit the difference between the data or program received there the data or program already, characterized in that the backup write to the backup storage unit, the control system according to claim 1. A list requesting unit that requests a list of the data or program backed up in the other one of the plurality of programmable controllers to the other one of the plurality of programmable controllers;
A list display unit for displaying a list display screen for displaying a list of the data or program received by the list request unit;
A restore input accepting unit that accepts input of information that uniquely specifies the data or program to be restored and a programmable controller that is a restore destination of the plurality of programmable controllers in the list display screen;
A restore request transmitter for transmitting the data or program to be restored and information for uniquely specifying a restore-destination programmable controller among the plurality of programmable controllers to another one of the plurality of programmable controllers;
Further comprising an external device having
Another one of the plurality of programmable controllers is:
A restore management unit is further provided that reads the data or program to be restored from the backup storage unit and transmits the data or program to the restore destination programmable controller of the plurality of programmable controllers,
One of the plurality of programmable controllers is:
It further includes a restore processing unit that receives the data or program to be restored from another one of the plurality of programmable controllers, writes the data or program to the backup storage unit or the backup target storage unit, and restores the data or program. The control system according to claim 1 . Another one of the plurality of programmable controllers is:
A list display unit for displaying a list display screen for displaying a list of the data or programs backed up in the other one of the plurality of programmable controllers in the backup storage unit;
A restore input accepting unit that accepts input of information that uniquely specifies the data or program to be restored and a programmable controller that is a restore destination of the plurality of programmable controllers in the list display screen;
A restore management unit is further provided that reads the data or program to be restored from the backup storage unit and transmits the data or program to the restore destination programmable controller of the plurality of programmable controllers,
One of the plurality of programmable controllers is:
It further includes a restore processing unit that receives the data or program to be restored from another one of the plurality of programmable controllers, writes the data or program to the backup storage unit or the backup target storage unit, and restores the data or program. The control system according to claim 1 . A control system to that control method executed with a plurality of programmable controllers,
Each of the plurality of programmable controllers is
A state monitoring step of monitoring a value representing the state of the monitored hardware and determining whether the value has reached a predetermined threshold;
When it is determined in the state monitoring step that the value has reached the threshold value, a backup storage unit that reads out data or a program used in machine control from a backup target storage unit and stores the data or program as a backup Backup processing steps to write to and back up,
Run
One of the plurality of programmable controllers is:
Further executing a backup transmission step of transmitting the data or program backed up to the backup storage unit to another one of the plurality of programmable controllers;
Another one of the plurality of programmable controllers is:
A control method further comprising: performing another device backup management step of receiving the data or program from one of the plurality of programmable controllers and writing the data or program to the backup storage unit for backup.

Images