WO2003001749A1 - Systeme de reseau securise et esclave securise - Google Patents
Systeme de reseau securise et esclave securise Download PDFInfo
- Publication number
- WO2003001749A1 WO2003001749A1 PCT/JP2002/006242 JP0206242W WO03001749A1 WO 2003001749 A1 WO2003001749 A1 WO 2003001749A1 JP 0206242 W JP0206242 W JP 0206242W WO 03001749 A1 WO03001749 A1 WO 03001749A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- safety
- information
- slave
- safety information
- network
- Prior art date
Links
- 238000012544 monitoring process Methods 0.000 claims abstract description 18
- 230000005540 biological transmission Effects 0.000 claims description 74
- 230000004044 response Effects 0.000 claims description 50
- 230000006854 communication Effects 0.000 claims description 47
- 238000004891 communication Methods 0.000 claims description 46
- 238000012545 processing Methods 0.000 abstract description 21
- 230000006870 function Effects 0.000 description 37
- 101100408464 Caenorhabditis elegans plc-1 gene Proteins 0.000 description 23
- 238000000034 method Methods 0.000 description 22
- 238000004092 self-diagnosis Methods 0.000 description 12
- 230000002159 abnormal effect Effects 0.000 description 9
- 238000010586 diagram Methods 0.000 description 8
- 230000005856 abnormality Effects 0.000 description 7
- 238000012423 maintenance Methods 0.000 description 4
- 238000001514 detection method Methods 0.000 description 3
- 231100001261 hazardous Toxicity 0.000 description 2
- 101000911772 Homo sapiens Hsc70-interacting protein Proteins 0.000 description 1
- 101000710013 Homo sapiens Reversion-inducing cysteine-rich protein with Kazal motifs Proteins 0.000 description 1
- 230000002411 adverse Effects 0.000 description 1
- 230000001174 ascending effect Effects 0.000 description 1
- 238000007796 conventional method Methods 0.000 description 1
- 230000006378 damage Effects 0.000 description 1
- 230000003111 delayed effect Effects 0.000 description 1
- 238000003745 diagnosis Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 238000007689 inspection Methods 0.000 description 1
- 230000010354 integration Effects 0.000 description 1
- 238000011835 investigation Methods 0.000 description 1
- 230000001788 irregular Effects 0.000 description 1
- 238000012806 monitoring device Methods 0.000 description 1
Classifications
-
- G—PHYSICS
- G05—CONTROLLING; REGULATING
- G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
- G05B19/00—Programme-control systems
- G05B19/02—Programme-control systems electric
- G05B19/04—Programme control other than numerical control, i.e. in sequence controllers or logic controllers
- G05B19/05—Programmable logic controllers, e.g. simulating logic interconnections of signals according to ladder diagrams or function charts
-
- G—PHYSICS
- G05—CONTROLLING; REGULATING
- G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
- G05B2219/00—Program-control systems
- G05B2219/10—Plc systems
- G05B2219/14—Plc safety
- G05B2219/14012—Safety integrity level, safety integrated systems, SIL, SIS
-
- G—PHYSICS
- G05—CONTROLLING; REGULATING
- G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
- G05B2219/00—Program-control systems
- G05B2219/20—Pc systems
- G05B2219/24—Pc safety
- G05B2219/24137—Non volatile memory to store program on power loss
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10—TECHNICAL SUBJECTS COVERED BY FORMER USPC
- Y10S—TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10S707/00—Data processing: database and file management or data structures
- Y10S707/99931—Database or file accessing
- Y10S707/99932—Access augmentation or optimizing
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10—TECHNICAL SUBJECTS COVERED BY FORMER USPC
- Y10S—TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10S707/00—Data processing: database and file management or data structures
- Y10S707/99941—Database schema or data structure
- Y10S707/99944—Object-oriented database structure
- Y10S707/99945—Object-oriented database structure processing
Definitions
- the present invention relates to a safety network system and a safety slave.
- a programmable controller (PLC) used in factory automation (FA) is a ladder language that inputs FF and FF information from input devices such as switches and sensors. Performs logical operations according to a sequence program (also referred to as a user program) written in, for example, and outputs ⁇ N0FF information signals to output devices such as relays, valves, and actuators according to the calculated results. Control is executed.
- PLC programmable controller
- FA factory automation
- connection form between the PLC and the input device and the output device may be directly connected to the PLC or may be connected via a network.
- a network system connected by such a network is constructed, transmission and reception of the above 0N / 0FF information is performed via the network.
- information is normally transmitted in a master slave system in which the PLC side is the master and the device side is the slave.
- a fail-safe system has recently been introduced for PLC control.
- the safety function is a function to confirm that it is safe and to output.
- the safety system is activated when the emergency stop switch is pressed or when the network system is in danger, such as when a sensor such as a light curtain detects the entry of a person (part of the body).
- the fail-safe is activated to bring the system to a safe side and stop operation.
- the safety function described above only outputs when it is stored as safe. It is a system that powers and moves a machine. Therefore, if safety cannot be confirmed, the machine stops.
- non-safety information for monitoring the slave or devices connected to the slave, such as the status of the slave, the energization time, and the number of operations, other than the above safety information.
- supplementary information for monitoring the slave or devices connected to the slave, such as the status of the slave, the energization time, and the number of operations, other than the above safety information.
- any of the above-mentioned methods affects traffic, and affects communication performance of safety information.
- safety information cannot be communicated, so sending safety information is delayed accordingly.
- An object of the present invention is to provide a safety network system and a safety slave that can efficiently collect non-safety information while minimizing the influence on network traffic. .
- the safety slave according to the present invention is a safety slave that can be connected to a safety network.
- Non-safety information storage means for storing information, and when the non-safety information stored in the non-safety information storage means satisfies certain conditions, a non-safety information that satisfies at least the condition toward the safety controller is satisfied. It has a function of transmitting safety information. Then, the transmission of the non-safety information may be performed after the end of the safety response of another safety slave in one communication cycle based on the request.
- a safety slave that can be connected to the safety network and that specifies whether or not the vehicle is in a safety state in response to a request from the safety controller transmitted via the safety network.
- a non-safety information storage function for storing non-safety information about the safety slave, a storage means for storing conditions for transmitting the non-safety information, Monitoring means for determining whether or not the non-safety information stored in the information satisfies the condition, and determining means for determining a transmission timing based on a monitoring result of the monitoring means may be provided.
- a safety network system according to the present invention is a network system constructed by connecting a safety controller and the safety slave according to claim 1 via a safety network. The information of the device output from the controller is transmitted to the controller. It is preferable that one communication cycle managed by the safety controller has a reception period of non-safety information after receiving a safety response from each of the safety slaves.
- the safety information includes at least information on whether or not the state of the safety slave and / or the safety device connected thereto is a safety state.
- non-safety information is various types of information that do not include the above-mentioned safety information, and includes, for example, relay life, investigation results, energizing time, number of operations, and type information.
- the “energization time” and the “number of operations” are obtained, for example, by counting and counting with a timer and a counter, respectively, and the obtained current value is transmitted as non-safety information.
- “Relay life” is life prediction.
- the life of the relay as non-safety information here is not the information that the safe operation cannot be performed due to the end of the service life (in this case, it is treated as safety information), and the relay operates safely, but maintenance (replacement, adjustment) This is predictive information that the time for maintenance is approaching.
- “Survey result” is information that indicates, for example, statistical prediction or detection. In other words, it is not the result of the self-diagnosis of the safety on the slave side. This self-diagnosis result is sent as safety information.
- non-safety information it operates safely, but it is (1) It is nearing the end of its service life, (2) it is used in a bad environment, (3) temperature, vibration state, supply voltage, and overuse state. There is information such as whether or not. By knowing such information, maintenance (replacement, adjustment, etc.) can be performed as soon as possible, and it will be impossible to operate after the end of its service life, thereby preventing the effects of abnormalities from increasing. Furthermore, the result of self-diagnosis is also a type of non-safety information.
- the “safety function” is a so-called file safe function, which is a system that outputs on condition that it is safe and moves the machine. Therefore, if it becomes unsafe, the output is stopped. Therefore, when an error occurs in the control of the controller or the like, or when a communication error occurs, the control is stopped, and the stop of the controller can maintain a safe state for the output handling device and the control device.
- cases where this control stop is necessary include: when the controller's CPU and other processing units are duplicated to detect a mismatch between the two; when a network error occurs for any reason; If the stop switch is pressed, In some cases, a hazardous state occurs, for example, when a person (part of the body) enters a hazardous area by a multi-optical axis photoelectric sensor such as a curtain.
- the safety function ensures that the mechanical system to be controlled is operated in a safe state, or in addition to the operation, is stopped in a safe state, or the file system is activated by the file safe. The operation of the mechanical system can be forcibly stopped in a safe state.
- the safety device may be connected to the safety slave, or the safety device itself may be the safety slave, and may transmit and receive data to and from the safety controller.
- the safety device itself is also a safety slave is the light
- Multi-optical axis photoelectric sensor Multi-optical axis photoelectric sensor.
- the function of detecting that a person has entered a dangerous area is a safety device (input device), and the function of communicating the detection result signal to the master via a network is a safety slave.
- the non-safety information about a safety slave is a concept that includes the non-safety information of the safety device connected to the safety slave, and may be only the non-safety information of the safety device.
- the safety slave that has collected and stored the non-safety information determines whether or not it is time to transmit the non-safety information, and when the transmission timing is reached, the non-safety information is transmitted to the safety controller. Send to.
- non-safety information does not need to be sent very often, but there is a demand that when a certain set value is reached, it is necessary to know for maintenance and life expectancy. Then, only the safety slave that is actually collecting the non-safety information can know whether or not the set value has been reached.
- non-safety information can be transmitted at an appropriate timing by transferring the decision on whether or not to transmit, which has been conventionally made on the safety controller side, to the safety slave side.
- all received non-safety information is meaningful and information can be collected efficiently.
- non-safety information is sent based on a request from the safety controller, unnecessary or less useful non-safety information may be sent, which may adversely affect traffic.
- transmission is performed when a required preset transmission timing is reached, so that the influence on network traffic is suppressed as much as possible.
- the force s required to secure time for transmission of the non-safety information in each communication cycle usually when the transmission timing does not reach frequently, The time for transmitting non-all information set in one communication cycle is sufficient if, for example, one or a small number of safety slaves can transmit data. Be shortened.
- the safety slave transmits safety information and non-safety information in accordance with a request from the safety controller power?
- the present invention is rather limited to this, transmission partner is optional.
- a safety slave that can be connected to the safety network and that specifies whether or not it is in a safety state in response to a request from another node sent through the safety network.
- a non-safety information storage function for storing non-safety information about the safety slave, and the non-safety information stored in the non-safety information storage means satisfying a certain condition. When the condition is satisfied, a function of transmitting non-safety information satisfying at least the condition to the other node can be provided.
- the other nodes are nodes connected to the safety network such as a configurator (configuration tool), a monitoring device, and other slaves.
- each of the above-mentioned inventions transmits safety information and non-safety information based on an external trigger called a request from a transmission partner.
- an external trigger called a request from a transmission partner.
- the present invention is not limited to this, and the internal trigger is not limited to this. Includes those that voluntarily transmit safety information or non-safety information based on
- a safety slave that can be connected to a safety network and that transmits safety information that specifies whether or not the vehicle is in a safe state when a transmission condition is satisfied.
- Non-safety information storage means for storing safety information, and when the non-safety information stored in the non-safety information storage means satisfies a certain condition, is directed to another node connected to the safety network.
- FIG. 1 is a diagram illustrating a problem of the conventional example.
- FIG. 2 is a diagram showing an embodiment of the safety network system according to the present invention.
- FIG. 3 is a timing chart showing a communication procedure between the safety PLC and the safety slave.
- FIG. 4 is a flowchart illustrating the function of the safety PLC (master).
- FIG. 5 is a diagram showing a preferred embodiment of the safety slave according to the present invention.
- FIG. 6 is a diagram showing a data structure of the non-safety information storage unit.
- Figure 7 is a flow chart showing the functions of the safety slave MPU (collecting and storing non-safety information).
- FIG. 8 is a diagram illustrating a data structure of the non-secure information transmission control unit.
- Figure 9 is a flowchart showing the function (transmission control) of the MPU of the safety slave.
- FIG. 10 is a diagram illustrating the operation of transmitting safety information and non-safety information.
- FIG. 11 is a diagram illustrating the operation of transmitting safety information and non-safety information.
- FIG. 12 is a diagram illustrating the operation of transmitting safety information and non-safety information.
- FIG. 13 is a flowchart showing a function (transmission control) of the MPU of the safety slave for executing the processing shown in FIG. BEST MODE FOR CARRYING OUT THE INVENTION
- FIG. 2 shows an example of a secure network system to which the present invention is applied.
- a safety PLC 1 master
- a safety slaves 2 are connected via a safety network 3.
- Information is sent and received between the safety PLC 1 and the safety slave 2 in a master-slave manner.
- each safety slave 2 has a safety door switch, a safety limit switch, an emergency stop switch, and various other types.
- Safety devices 4 such as input devices and output devices are connected.
- the safety PLC 1 is configured by connecting a plurality of units such as a CPU unit, a master unit (communication unit), and a 10 unit. In this case, the master unit is connected to the safety network 3.
- the monitoring tool 5 collects and manages information about the safety slave 2 and, eventually, the safety device 4 connected thereto via the safety PLC 1 as described later.
- This safety function is a function that confirms safety and performs output (control). Then, in the event of a danger, the file safe is activated and the system goes to the safe side to stop operation.
- the safety system is activated when the emergency stop switch is pressed or when the network system is in danger, such as when a sensor such as a light curtain detects the entry of a person (part of the body).
- the file safety is activated, the system is on the safe side, and the operation stops. In other words, it is a system that outputs only when it is stored as safe by the above-mentioned safety function, and moves the machine. Therefore, if safety cannot be confirmed, the machine will stop.
- the safety PLC 1 also has a built-in communication function, and sends and receives information to and from the safety slave 2 in a master-slave manner. Basically, as before, the safety PLC 1 issues requests sequentially to each safety slave 2 via the safety network 3 and the safety slave 2 that receives the request issues a safety response as a safety response. It returns information.
- a request is issued from the safety PLC 1 to each safety slave 2 by simultaneous broadcast.
- a safety response to the request is received from all the safety slaves 2, instead of immediately proceeding to the next communication cycle, a reception standby state for a certain period is set.
- This period takes enough time to receive a transmission frame from at least one safety slave 2. That is, this fixed period is set as a period for transmitting and receiving non-security information.
- the decision whether to transmit the non-safety information is made by the safety slave 2 side, and the safety slave 2 that decides to transmit the non-safety information receives the non- Sends non-safety information to safety PLC 1 when in standby state.
- non-safety information does not have to be sent as often, but there are times when it is desirable to send it in certain situations.
- the safety PLC 1 does not know the status of the safety slave 2, so the timing at which the above-mentioned non-safety information is necessarily sent is not always required.
- the request is not always issued at the time. Therefore, it is necessary to issue requests to all safety slaves relatively frequently in order to obtain non-safety information at the right time.
- a specific processing function in the MPU of the safety PLC 1 for executing the above-described processing is to implement a flowchart shown in FIG.
- the reception timeout is a timeout when the time set as one communication cycle time elapses after the transmission request is made. Specifically, it is the time obtained by adding the time for receiving the non-safety information from at least one safety slave to the time for receiving the safety responses from all the safety slaves 2.
- step 5 determines whether or not the response is a safety response. Then, in the case of a safety response, it is further determined whether or not the content of the safety response (the received safety information) is safe (ST6). If the result of the determination is abnormal (dangerous), the process proceeds to step 9, the file safe is activated, the communication process is stopped, and the output cutoff process is executed (ST7, ST8). If the received content is safe, return to step 3 and wait for the next reception. On the other hand, if No in the branch determination in step 5, that is, if non-secure information is received, the process proceeds to step 8 and a predetermined non-secure information reception process is performed.
- the received non-safety information is stored in the memory or output display on the monitor. After that, return to step 3 and wait for the next reception. Then, when the reception time expires (Yes in the branch determination of step 3), the processing of the current communication cycle ends, and the processing shifts to the processing of the next communication cycle (ST7). Thereafter, the above processing is repeatedly executed. 'Note that the notation in the flow chart is omitted. Actually, it is determined whether or not responses have been received from all the safety slaves 2 connected to the safety network 3 when the reception timeout has occurred. I do. Of course, in order to make such a determination, a process of storing the number of the safety slave that has received the safety response is performed.
- step 9 the communication stop processing in step 9 is performed.
- communication stop processing can be performed instead of stopping immediately if communication cannot be performed continuously N times.
- the safety slave 2 has a function to return a safety response according to the request from the safety PLC 1, a function to collect and store non-safety information, and a function to store the stored non-safety information to the safety PLC 1 at a predetermined timing. It has a function of transmitting to the user.
- the specific internal structure for realizing such a function is as shown in FIG.
- a network interface 21 that connects to the safety network 3 and sends and receives data to and from the safety PLC 1 (master), and a safety device connected to the safety slave 2 (not shown) Reads the program stored in the system ROM 24 and the safety device interface 22 for sending and receiving data to and from the system, and executes predetermined processing using the memory area of the system RAM 25 as appropriate.
- MPU 23 is provided. The MPU 23 receives the safety information (safety danger) acquired from the safety device via the safety device interface 22 according to the request from the mass communication received via the network interface 21 and sends the information to the network interface. Performs processing to return to safety PLC 1 via Pace 21 and safety network 3.
- the safety slave 2 itself can be a safety device. It is not a device interface 22 but a safety device section for detecting the presence or absence of safety.
- the safety slave 2 since the above-described respective configurations and operation principles of the safety slave 2 are the same as those of the conventional one, detailed description thereof will be omitted.
- the MPU 23 has a function for monitoring the operation status of the safety device 4 (powering time, ONZOFF count, etc.), and stores device information such as the operation status obtained by operating the monitoring function in the non-safety information storage unit 26. Is also executed. Then, the non-safety information (device information) stored in the non-safety information storage unit 26 is transmitted to the safety PLC 1 according to a rule described later.
- the data structure of the non-safety information storage unit 26 is, for example, as shown in FIG.
- inputs 1, 2, 3, ... are the numbers of the contacts (terminal blocks) of safety slave 2.
- the model type, the name of the manufacturer, the model, and the life setting are registered in advance.
- necessary information is sent to safety slave 2 via safety network 3, and tools connected directly to safety slave 2
- the MPU 23 of the safety slave 2 obtains the information via the network interface 21 and registers it in the non-safety information storage unit 26 in association with the contact number.
- the life setting is, for example, an energizing time, a number of operations, and a value obtained from a value of the energization time and a predetermined arithmetic expression.
- the safety device 4 has reached its replacement time.
- the MPU 23 collects and records the status, number of operations, energization time, and notification flag during the actual system operation. Where the state is that safety device 4 is operating
- the operation count is the information indicating the ONZOFF count of the contact of the safety device 4.
- the energization time indicates that the safety device 4 was energized. This is the integration time. Furthermore, the life result stores whether or not the life has expired (normal). Further, it is preferable that a display unit is provided in the safety slave 2 so that the device information stored in the non-safety information storage unit 26 can be displayed.
- MPU 23 Perform self-diagnosis and safety input monitoring (ST 11). That is, the self-diagnosis is to check whether an abnormality has occurred in the connected safety device 4, and this processing itself is conventionally known.
- the safety input monitoring is for monitoring the input from the connected safety device 4. Then, when there is an abnormality or an input, information on which safety device 4 is also specified.
- step 11 it is determined whether or not the result of the self-diagnosis and the safety input monitoring in step 11 indicates that the abnormality detection or the safety input is OFF (not safe or dangerous) (ST 12). Then, when an abnormality or the like is detected, abnormality processing is performed (ST13). In other words, the abnormal state and the like are stored in the self-diagnosis result and the ON / OFF information column for the corresponding contact number in the safety information storage unit (not shown). The result of the diagnosis is transmitted as a safety response in response to the request for safety information from the safety PLC 1.
- the energizing time is updated (ST 14).
- the time from the previous update process to the present is measured by a timer (the safety device 4 is stopped (no power is supplied) and stopped without timing).
- a value obtained by adding the measured energization time from the update process to the current time to the energization time is set as a new energization time, and the energization time is stored in the non-safety information storage unit 26.
- step 15 it is determined whether or not the input state of the safety device 4 has changed from OFF (previous) to ON (current) (ST15). That is, in the case of the previous OFF, the ON / OFF information column of the non-safety information storage unit 26 is set to 0FF after the processing of step 13. Therefore, if the ONZO FF information of the corresponding contact number is OFF, this branch judgment is Yes. Therefore, the process proceeds to step 16, and the operation count is incremented by 1 (ST16). The operation count is registered in the column of the number of operations in the non-safety information storage unit 26, and the state column of the non-safety information storage unit 26 is turned ON. As a result, once the operating force increment is incremented, the state turns ON.
- step 15 If the branch judgment of step 15 is executed in the next cycle (if the safety input does not turn OFF in the middle), N It becomes o, and the operation count is not performed. Also, since the ON state has already been registered, there is no problem even if the ON state is not written again. Thereafter, the state of the safety device 4 is changed by repeatedly executing the above processing. Can be collected and stored.
- the timer and counter of the energization time and the number of operations may be carried out with the safety slave 2 having the timer / counter, or the energization time and the energization time may be measured on the side of the safety device 4 following the safety slave 2.
- the safety device 4 may always store the information, and the safety slave 2 may read the stored information stored in the safety device 4 at a predetermined timing.
- a non-secure information transmission control unit 27 that determines the timing of transmitting the non-secure information stored in the non-secure information storage unit 26 is provided.
- the non-safety information transmission control unit 27 is a memory that stores a threshold value of the transmission timing for notifying the non-safety information.
- the data structure of the non-safety information transmission control unit 27 stores one or more transmission timings in the energization time, the relay ONZOFF frequency, and the communication retry frequency. .
- the energization time it means that the current value is notified to the safety PLC (master) 1 when the energization time exceeds 200 h, 400 h, 600 h, and 800 h.
- the current value must be notified to the safety PLC 1 when the number of times exceeds 3 0 0, 5 0 0 0, 8 0 0 0, 1 0 0 0 0 0 Means Furthermore, in the case of the number of retries, when the communication cycle is 500, 100, 150, or 2000 times, the number of retries is notified to the safety PLC 1 at that time. means.
- a delimiter value such as 50,000 and 800 as shown in the figure may be used, or a ratio may be determined. For example, if 800.000 (time or time) is the life setting, like the door switch of input 1 in Fig. 6, one third of 266.67 times or 80% of 64% It may be set to 0 times. In other words, it is only necessary to obtain information that indicates the end of the service life (during the course of consumption) as long as it can be regarded as safe operation.
- the notification of network information clarifies points for improving the network environment and optimizes response time (safety stop time for safety-compatible systems). Can be achieved. In other words, different Always ⁇ If there is a safety device that frequently fails, it can be predicted that there is a problem, and the system can be changed by changing the device used. The above-mentioned energization time and the number of relay ON / OFF operations can be obtained by accessing the non-safety information storage unit 26. In addition, since information on the communication cycle and the number of retries is stored and held by the chip that controls and executes communication, it is possible to determine whether or not it has come to the transmission timing by collecting such information. .
- the MPU 23 accesses the non-secure information transmission control unit 27 to obtain the transmission timing of each non-secure information, At the same time, the non-safety information storage unit 26 is accessed to determine whether or not there is a transmission timing. Then, when the non-safety information at the transmission timing is detected, the corresponding information is transmitted.
- the non-safety information to be transmitted is not limited to the above-mentioned information.
- the self-diagnosis result may be transmitted as the non-safety information.
- the self-diagnosis error factor information of the device with built-in light curtain function includes interlock wiring error, external relay monitor error, interference light error, control output error, and sensor destruction.
- the control algorithm for transmitting the safety information and the non-security information in the MPU 23 is as shown in the flowchart of FIG. That is, after the power is turned on, it waits for a request sent from the safety PLC (master) (ST21, ST22), and upon receiving the request, makes a safety response (ST23). That is, the safety status (safety Z error) is notified.
- the safety slave 2 side takes the initiative in actively transmitting the non-safety information.
- the non-safety information is transmitted by monitoring the data flowing on the secure network 3 after receiving the above request and confirming that the transmission frame is no longer transmitted.
- the transmission and reception of data on the secure network 3 by the network interface 21 and the communication protocol in the present embodiment use a CAN (Controller Area Network). That is, as is well known, in CAN, priority is managed in the data link layer, data on the communication line is ORed by one yard, and data "1" and data "0" overlap. On the line, data “0” appears.
- each safety slave 2 sends a transmission frame (safety information) that it intends to send, monitors the data on the line, and matches the data flowing on the line with the data sent by itself. Judge whether or not to send, if it does not match, judge that there is no authority to send this time, and stop sending data after that o
- CAN Controller Area Network
- the transmission frame is normally arranged in the order of header information, transmission destination / source address, and data to be transmitted. Therefore, the transmission address, that is, the node number of each safety slave 2 must be transmitted in ascending order. Can be. Therefore, as shown in Fig. 3, in response to a request by simultaneous broadcast from the safety PLC 1, the safety slave 2 returns a safety response in the order of 1-2-3.
- safety slave (1) is indicated by S1
- safety slave (2) is indicated by S2
- safety slave (3) is indicated by S3. That is, in the Nth communication cycle, only the safety response is executed and the process ends.
- the safety PLC (master) 1 issues the next request, and in response, each safety slave responds in turn with a safety response. .
- a certain safety slave 2 comes at the transmission timing of the non-safety information (the predetermined non-safety information is set).
- the non-safety information is transmitted.
- the only non-safety information sent at this time is the non-safety information that exceeds the setting. As a result, the amount of data to be transmitted is suppressed, and transmission can be performed in a short time. Of course, information other than the non-safety information exceeding the threshold may be sent together.
- the request issued from the safety PLC 1 to each safety slave is performed by simultaneous broadcast, but the present invention is not limited to this.
- the present invention can be similarly applied to a configuration in which requests are issued to the safety slaves 2 in order, such as 1-2-3, and the safety slaves 2 receiving the requests sequentially return the safety requests. Even in this case, as shown in the figure, if there is a non-safety slave that has exceeded the set threshold value and has sent the non-safety information, the non-safety information is transmitted. No non-security information is sent to
- the non-secure information transmission control unit 27 and the non-secure information storage unit 26 are described separately, but may be stored as one table. Further, in the above-described embodiment, the non-safety information transmission control unit 27 is a memory that stores a threshold value as a criterion for determining whether or not transmission timing has been reached, and the MPU 23 determines the actual determination. The non-safety information transmission control unit 27 may monitor the non-safety information storage unit 26 and may apply a trigger to the MPU 23 when the transmission timing comes.
- a period for transmitting non-safety information is provided after a period for transmitting a safety response for transmitting safety information in one communication cycle, but the present invention is not limited to this.
- non-safety information transmission timing non-safety information is transmitted.
- the non-safety information is transmitted on condition that the safety slave is in a safe state.
- the transmission of non-secure information means that the safety of the safety slave is guaranteed. Therefore, if the safety slave is in the safe state, the safety PLC Can confirm that the safety slave is in the safe state directly by receiving the safety information (safety) or indirectly by receiving the non-safety information.
- non-safety information can be reported from the slave (safety slave) to the master (safety controller) without affecting the traffic on the safety network.
- the safety PLC side frame force received? Since safe and information of whether the non-safety information is not known, for example, may them distinguishing flag added to the transmission frame.
- the slave described in the above embodiment sends and receives I / O information to and from the master unit, and sends and receives I / O information related to a controller (PLC) via the master unit.
- PLC controller
- An example of controlling the system was shown, and the master-slave method, in which a desired slave returns a response to a request from the master, between the master unit and the slave was described.
- the slave in the present invention is not limited to the one that performs master-slave communication. In other words, although it is called a slave, any communication method can be used. In that respect, it can be said that it includes a concept that is strictly different from the generally defined slave.
- the slave in the present invention has an arbitrary communication protocol for transmitting and receiving safety information and non-safety information as long as it has a function of transmitting and receiving I0 information necessary for control to and from the controller. It is.
- the destination of the safety information and non-safety information to be transmitted in the present invention is not limited to the master unit or the controller, but may be a monitor device connected to a network, a configuration tool, another slave device, or another device. And other devices other than the own node, that is, other nodes.
- the communication method can also be appropriately selected according to the transmission partner.
- the trigger for transmission is not limited to the one that is performed in response to an external request (for example, a request from a monitor device or a configuration tool) as in the request from the master described above. Transmission may be based on an internal trigger (such as an internal timer or an event that occurs when certain conditions are met).
- the “internal trigger” is based on the result of execution of a predetermined process of the slave itself, and is generated inside the slave.
- the following are examples of internal triggers. That is, when an abnormal condition occurs or when it is determined whether the status information of the input / output device obtained by the slave has reached or exceeded the threshold value, the determination result is generated. Some use the judgment result as a trigger signal.
- a clock is provided in the slave and a trigger signal is periodically generated by the clock every time a predetermined time elapses, or a trigger signal is generated at a predetermined time.
- the safety slave determines when to transmit information, and the conditions for transmitting non-safety information when transmitting the information are satisfied. There are things that fire in some cases.
- the timing for transmitting the former information may be determined, for example, when a result is obtained for a predetermined time by an internal timer or when a condition event occurs.
- the latter, the internal trigger as the notification condition of the non-safety information includes a case where the value collected as the non-safety information exceeds a threshold value and a case where it is necessary to notify the result of the self-diagnosis result.
- an internal timer may be provided as a condition for notifying the non-safety information, and a trigger for notifying the non-safety information may be generated when a predetermined period longer than a normal transmission interval has elapsed.
- the safety slave stops transmission if another safety slave is already transmitting, and if it tries to transmit simultaneously and collides on the network,
- the safety slave with the higher priority continues communication as it is.
- information can be sequentially transmitted from each safety slave in a predetermined order in one communication cycle. By appropriately setting the transmission timer, the information can be smoothly and repeatedly transmitted in that order.
- each safety slave does not respond to the request from the master, but, for example, as shown in Fig. 12, each safety slave has an appropriate timing. It can be configured to send safety information and, if necessary, to send non-safety information.
- the transmission destination is As such, it can be a master, or it can be a configuration tool or other device.
- the flowchart shown in FIG. 13 may be executed. That is, after the power is turned on, the transmission condition is reached, that is, the internal trigger for information transmission is generated (ST31, ST32). Then, when an internal trigger for information transmission occurs, the current safety state (safety / abnormal) is transmitted as safety information to a predetermined partner (ST33). Next, it is determined whether or not it is time to send the non-safety information (ST34). That is, whether the predetermined information and the number of communications stored in the non-safety information storage unit 26 have reached the set value stored in the non-safety information transmission control unit 27, Determine if there is a result.
- the process returns to step 31 without transmitting non-safety information in this communication cycle, and waits for the next internal trigger to be generated. Thereafter, by repeatedly performing the above processing, the safety slave voluntarily issues safety information at an appropriate timing, and when the timing of transmitting the non-safety information has been reached, the safety slave is mainly responsible for the safety slave. Actively send non-safety information.
- the transmission of the non-safety information is performed by monitoring the data flowing on the safety network 3 after transmitting the safety information and transmitting after confirming that the transmission frame is no longer transmitted.
- the transmission condition of the non-secure information comes, it is possible to transmit only the non-secure information without sending the safety information on condition that the safety slave is in the safe state.
- the safety PLC or the like directly or indirectly receives the non-safety information by receiving the safety information (safety). Can be confirmed.
- the safety information danger / abnormal
- Response time does not need to be extended.
- the device information storage means is provided in the slave and the information of the device connected to the slave is stored and held, the stored information about each device connected to the slave is stored in the controller via the network. Yaru can be collected.
- the safety slave that is collecting the non-safety information transmits the non-safety information at a desired timing, the safety controller and other devices can efficiently collect the non-safety information.
Landscapes
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Engineering & Computer Science (AREA)
- Automation & Control Theory (AREA)
- Programmable Controllers (AREA)
- Small-Scale Networks (AREA)
- Selective Calling Equipment (AREA)
Description
Claims
Priority Applications (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2003508023A JP3748078B2 (ja) | 2001-06-22 | 2002-06-21 | 安全ネットワークシステム及び安全スレーブ |
CN028124987A CN1518816B (zh) | 2001-06-22 | 2002-06-21 | 安全网络系统及安全从动装置 |
EP02738779A EP1404061B1 (en) | 2001-06-22 | 2002-06-21 | Safety network system and safety slave |
US10/481,503 US7472106B2 (en) | 2001-06-22 | 2002-06-21 | Safety network system and safety slave |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2001-190418 | 2001-06-22 | ||
JP2001190418 | 2001-06-22 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2003001749A1 true WO2003001749A1 (fr) | 2003-01-03 |
Family
ID=19029189
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/JP2002/006242 WO2003001749A1 (fr) | 2001-06-22 | 2002-06-21 | Systeme de reseau securise et esclave securise |
Country Status (5)
Country | Link |
---|---|
US (1) | US7472106B2 (ja) |
EP (1) | EP1404061B1 (ja) |
JP (1) | JP3748078B2 (ja) |
CN (1) | CN1518816B (ja) |
WO (1) | WO2003001749A1 (ja) |
Cited By (10)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2004234655A (ja) * | 2003-01-28 | 2004-08-19 | Fisher Rosemount Syst Inc | プロセス制御システムおよび安全システムを備えるプロセスプラントにおける統合型診断 |
JPWO2003001306A1 (ja) * | 2001-06-22 | 2004-10-14 | オムロン株式会社 | 安全ネットワークシステム及び安全スレーブ並びに安全コントローラ |
EP1493960A2 (en) * | 2003-06-30 | 2005-01-05 | Keyence Corporation | Safety relay system |
JP2006059356A (ja) * | 2004-08-17 | 2006-03-02 | Phoenix Contact Gmbh & Co Kg | 安全性関連処理のバス結合のための方法と装置 |
JP2006301886A (ja) * | 2005-04-19 | 2006-11-02 | Omron Corp | プログラマブル・コントローラ |
JP2011516997A (ja) * | 2008-04-17 | 2011-05-26 | ベックホフ オートメーション ゲーエムベーハー | セーフティコントロールを作動させる作動方法、および、そのようなセーフティコントロールを備えたオートメーションネットワーク |
JP4827964B2 (ja) * | 2006-03-22 | 2011-11-30 | フェニックス コンタクト ゲーエムベーハー ウント コムパニー カーゲー | 安全通信構成部品の取付け場所を検証するための方法ならびに制御およびデータ伝送システム |
US8521002B2 (en) | 2004-04-16 | 2013-08-27 | Panasonic Corporation | Recording medium, reproduction device, program and method |
JP2016019162A (ja) * | 2014-07-09 | 2016-02-01 | 株式会社デンソー | 通信装置 |
JP2021082028A (ja) * | 2019-11-19 | 2021-05-27 | 株式会社キーエンス | 安全コントローラおよび履歴表示装置 |
Families Citing this family (26)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
DE60235232D1 (de) * | 2001-05-31 | 2010-03-18 | Omron Tateisi Electronics Co | Sicherheitsnetzwerksystem und sicherheits-slaves und sicherheitssteuerung und kommunikationsverfahren und informationssammelverfahren und überwachungsverfahren in einem sicherheitsnetzwerksystem |
US7430451B2 (en) * | 2001-05-31 | 2008-09-30 | Omron Corporation | Safety unit, controller system, connection method of controllers, control method of the controller system and monitor method of the controller system |
US7369902B2 (en) * | 2001-05-31 | 2008-05-06 | Omron Corporation | Slave units and network system as well as slave unit processing method and device information collecting method |
WO2003001307A1 (fr) * | 2001-06-22 | 2003-01-03 | Omron Corporation | Systeme de reseau de securite, esclave de securite, et procede de communication |
WO2003001749A1 (fr) | 2001-06-22 | 2003-01-03 | Omron Corporation | Systeme de reseau securise et esclave securise |
JP3988559B2 (ja) * | 2002-07-18 | 2007-10-10 | オムロン株式会社 | 通信システム、通信装置及び通信制御方法 |
DE102004018857A1 (de) * | 2004-04-19 | 2005-11-10 | Elektro Beckhoff Gmbh Unternehmensbereich Industrie Elektronik | Sicherheitssteuerung |
US8055814B2 (en) * | 2005-03-18 | 2011-11-08 | Rockwell Automation Technologies, Inc. | Universal safety I/O module |
JP3978617B2 (ja) * | 2005-04-19 | 2007-09-19 | オムロン株式会社 | 安全ユニットの入力装置 |
DE102006048172A1 (de) * | 2006-10-10 | 2008-04-17 | Robert Bosch Gmbh | Elektronisches System |
KR100921772B1 (ko) * | 2007-11-21 | 2009-10-15 | 한국전자통신연구원 | 안전 메시지를 전달하는 방법 및 수신하는 방법 |
JP5348499B2 (ja) * | 2009-03-12 | 2013-11-20 | オムロン株式会社 | I/oユニット並びに産業用コントローラ |
DE102009042368B4 (de) * | 2009-09-23 | 2023-08-17 | Phoenix Contact Gmbh & Co. Kg | Steuerungssystem zum Steuern von sicherheitskritischen Prozessen |
EP2375636A1 (de) * | 2010-03-29 | 2011-10-12 | Sick Ag | Vorrichtung und Verfahren zum Konfigurieren eines Bussystems |
US9459619B2 (en) * | 2011-06-29 | 2016-10-04 | Mega Fluid Systems, Inc. | Continuous equipment operation in an automated control environment |
WO2013052894A1 (en) * | 2011-10-05 | 2013-04-11 | Opteon Corporation | Methods, apparatus, and systems for monitoring and/or controlling dynamic environments |
DE102012110999A1 (de) * | 2011-12-21 | 2013-06-27 | Endress + Hauser Wetzer Gmbh + Co Kg | Verfahren zum Betreiben einer Anzeigeeinheit zur Anzeige von Prozessdaten |
JP6015178B2 (ja) * | 2012-07-11 | 2016-10-26 | オムロン株式会社 | 安全システム |
KR101472896B1 (ko) * | 2013-12-13 | 2014-12-16 | 현대자동차주식회사 | 차량 내 통신 네트워크에서의 보안 강화 방법 및 그 장치 |
US9618909B2 (en) | 2013-12-20 | 2017-04-11 | Thales Canada Inc | Safety assurance of multiple redundant systems |
DE102014103135B3 (de) * | 2014-03-10 | 2015-03-19 | Phoenix Contact Gmbh & Co. Kg | System zur sicheren Steuerung von Maschinen, Anlagen oder dergleichen |
JP6772887B2 (ja) * | 2017-02-21 | 2020-10-21 | オムロン株式会社 | サーボシステム |
JP6460137B2 (ja) * | 2017-03-06 | 2019-01-30 | オムロン株式会社 | 制御装置、制御方法、およびプログラム |
DE102017109886A1 (de) * | 2017-05-09 | 2018-11-15 | Abb Ag | Steuerungssystem zum Steuern von sicherheitskritischen und nichtsicherheitskritischen Prozessen mit Master-Slave-Funktionalität |
DE102019200907A1 (de) * | 2019-01-24 | 2020-07-30 | Robert Bosch Gmbh | Teilnehmerstation für ein Bussystem und Verfahren zur Datenübertragung in einem Bussystem |
US11774127B2 (en) | 2021-06-15 | 2023-10-03 | Honeywell International Inc. | Building system controller with multiple equipment failsafe modes |
Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JPH03116395A (ja) * | 1989-09-29 | 1991-05-17 | Csk Corp | 自動販売機データ収集システム |
JPH0445697A (ja) * | 1990-06-13 | 1992-02-14 | Nec Corp | ポーリング方式 |
JPH08211792A (ja) * | 1995-02-03 | 1996-08-20 | Mita Ind Co Ltd | 画像形成装置の管理システム |
Family Cites Families (75)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US3803974A (en) * | 1972-11-03 | 1974-04-16 | Wahl W Corp | Fire control system |
US4625308A (en) * | 1982-11-30 | 1986-11-25 | American Satellite Company | All digital IDMA dynamic channel allocated satellite communications system and method |
JPS6062482A (ja) | 1983-09-02 | 1985-04-10 | フアナツク株式会社 | ロボットの安全速度制御装置 |
US4715031A (en) * | 1985-09-23 | 1987-12-22 | Ford Motor Company | Vehicular data transfer communication system |
US4750171A (en) * | 1986-07-11 | 1988-06-07 | Tadiran Electronics Industries Ltd. | Data switching system and method |
US4918585A (en) * | 1988-01-11 | 1990-04-17 | Spectra Physics, Inc. | Maintenance reminder system for a pump |
FR2654220B1 (fr) * | 1989-11-03 | 1992-02-21 | Inst Francais Du Petrole | Systeme modulaire d'acquisition et de transmission de donnees sismiques a plusieurs niveaux de multiplexage. |
US5282127A (en) * | 1989-11-20 | 1994-01-25 | Sanyo Electric Co., Ltd. | Centralized control system for terminal device |
DE3938735A1 (de) * | 1989-11-23 | 1991-05-29 | Standard Elektrik Lorenz Ag | Einrichtung und verfahren zur ueberwachung einer navigationsanlage |
WO1991011766A2 (en) * | 1990-01-30 | 1991-08-08 | Johnson Service Company | Networked facilities management system |
US5218680A (en) * | 1990-03-15 | 1993-06-08 | International Business Machines Corporation | Data link controller with autonomous in tandem pipeline circuit elements relative to network channels for transferring multitasking data in cyclically recurrent time slots |
US5140316A (en) * | 1990-03-22 | 1992-08-18 | Masco Industries, Inc. | Control apparatus for powered vehicle door systems |
US5059953A (en) * | 1990-04-10 | 1991-10-22 | Pacific Scientific Company | Infrared overheat and fire detection system |
US5631724A (en) * | 1990-04-10 | 1997-05-20 | Sanyo Electric Co., Ltd | Centralized control system for terminal device |
US5157780A (en) * | 1990-06-12 | 1992-10-20 | Advanced Micro Devices, Inc. | Master-slave checking system |
US5519607A (en) * | 1991-03-12 | 1996-05-21 | Research Enterprises, Inc. | Automated health benefit processing system |
JPH0537980A (ja) | 1991-07-29 | 1993-02-12 | Mitsubishi Electric Corp | プラント監視装置 |
GB2267984A (en) | 1992-06-16 | 1993-12-22 | Thorn Emi Electronics Ltd | Multiplexing bus interface. |
US5434872A (en) * | 1992-07-28 | 1995-07-18 | 3Com Corporation | Apparatus for automatic initiation of data transmission |
JPH06169192A (ja) * | 1992-11-30 | 1994-06-14 | Sony Corp | 保守管理機能付き組立装置 |
US5400018A (en) * | 1992-12-22 | 1995-03-21 | Caterpillar Inc. | Method of relaying information relating to the status of a vehicle |
JPH06324719A (ja) | 1993-05-14 | 1994-11-25 | Omron Corp | プログラマブルコントローラ |
JPH07282090A (ja) | 1994-04-14 | 1995-10-27 | Toshiba Corp | データ収集方式 |
US6524230B1 (en) * | 1994-07-22 | 2003-02-25 | Ranpak Corp. | Packing material product and method and apparatus for making, monitoring and controlling the same |
US5572195A (en) * | 1994-08-01 | 1996-11-05 | Precision Tracking Fm, Inc. | Sensory and control system for local area networks |
US5845253A (en) * | 1994-08-24 | 1998-12-01 | Rensimer Enterprises, Ltd. | System and method for recording patient-history data about on-going physician care procedures |
US5841654A (en) * | 1995-10-16 | 1998-11-24 | Smar Research Corporation | Windows based network configuration and control method for a digital control system |
JP3282470B2 (ja) | 1995-11-08 | 2002-05-13 | 三菱電機株式会社 | パソコンを用いた数値制御装置及びその制御方法 |
US5995916A (en) * | 1996-04-12 | 1999-11-30 | Fisher-Rosemount Systems, Inc. | Process control system for monitoring and displaying diagnostic information of multiple distributed devices |
DE19620137C2 (de) * | 1996-05-07 | 2000-08-24 | Daimler Chrysler Ag | Protokoll für sicherheitskritische Anwendungen |
US5786996A (en) * | 1996-06-28 | 1998-07-28 | Eaton Corporation | Appliance control circuit comprising dual microprocessors for enhanced control operation and agency safety redundancy and software application method thereof |
US6098109A (en) * | 1996-12-30 | 2000-08-01 | Compaq Computer Corporation | Programmable arbitration system for determining priority of the ports of a network switch |
US5907689A (en) * | 1996-12-31 | 1999-05-25 | Compaq Computer Corporation | Master-target based arbitration priority |
US6111888A (en) * | 1997-05-27 | 2000-08-29 | Micro Motion, Inc. | Deterministic serial bus communication system |
JP3485444B2 (ja) | 1997-07-09 | 2004-01-13 | 新キャタピラー三菱株式会社 | 移動式作業機械管理システム及び管理方法並びに同管理システムのための移動式作業機械,ユーザ装置及び親装置 |
US6574234B1 (en) * | 1997-09-05 | 2003-06-03 | Amx Corporation | Method and apparatus for controlling network devices |
DE19742716C5 (de) | 1997-09-26 | 2005-12-01 | Phoenix Contact Gmbh & Co. Kg | Steuer- und Datenübertragungsanlage und Verfahren zum Übertragen von sicherheitsbezogenen Daten |
USH1882H (en) * | 1997-09-26 | 2000-10-03 | Asthana; Sarvesh | System and method for transferring data to redundant components |
US6507804B1 (en) * | 1997-10-14 | 2003-01-14 | Bently Nevada Corporation | Apparatus and method for compressing measurement data corelative to machine status |
US6026348A (en) * | 1997-10-14 | 2000-02-15 | Bently Nevada Corporation | Apparatus and method for compressing measurement data correlative to machine status |
US6473811B1 (en) * | 1998-03-13 | 2002-10-29 | Canon Kabushiki Kaisha | Method and apparatus for displaying a connection status of a device based on connection information |
US6285966B1 (en) | 1998-06-25 | 2001-09-04 | Fisher Controls International, Inc. | Function block apparatus for viewing data in a process control system |
US6640268B1 (en) * | 1998-08-28 | 2003-10-28 | Intel Corporation | Dynamic polling mechanism for wireless devices |
DE19905841A1 (de) * | 1999-02-12 | 2000-08-24 | Kuka Roboter Gmbh | Vorrichtung zum Verarbeiten sicherheitsrelevanter Daten |
US6633782B1 (en) | 1999-02-22 | 2003-10-14 | Fisher-Rosemount Systems, Inc. | Diagnostic expert in a process control system |
JP3663617B2 (ja) | 1999-03-12 | 2005-06-22 | オムロン株式会社 | Plc用ツール装置、並びに、プログラム記録媒体 |
JP3794459B2 (ja) | 1999-03-17 | 2006-07-05 | オムロン株式会社 | データ伝送システム並びに通信ユニット及び機器 |
US6762684B1 (en) * | 1999-04-19 | 2004-07-13 | Accutrak Systems, Inc. | Monitoring system |
DE19921846A1 (de) | 1999-05-11 | 2000-11-23 | Bosch Gmbh Robert | Diagnosetestvorrichtung mit portablem Prüfgerät für Kraftfahrzeuge |
DE19925693B4 (de) * | 1999-06-04 | 2007-05-16 | Phoenix Contact Gmbh & Co | Schaltungsanordnung zur gesicherten Datenübertragung in einem ringförmigen Bussystem |
DE19928517C2 (de) * | 1999-06-22 | 2001-09-06 | Pilz Gmbh & Co | Steuerungssystem zum Steuern von sicherheitskritischen Prozessen |
DE50014879D1 (de) * | 1999-08-13 | 2008-02-07 | Fraunhofer Ges Forschung | Haus-kommunikationssystem, transportplattform für ein haus-kommunikationssystem und intelligentes netzabschlussgerät für ein haus-kommunikationssystem |
DE19939567B4 (de) * | 1999-08-20 | 2007-07-19 | Pilz Gmbh & Co. Kg | Vorrichtung zum Steuern von sicherheitskritischen Prozessen |
JP4176252B2 (ja) | 1999-09-14 | 2008-11-05 | 株式会社イシダ | 商品処理装置のメンテナンスシステム |
JP2001084014A (ja) | 1999-09-16 | 2001-03-30 | Nippon Signal Co Ltd:The | 生産設備制御システム |
US6915263B1 (en) * | 1999-10-20 | 2005-07-05 | Sony Corporation | Digital audio decoder having error concealment using a dynamic recovery delay and frame repeating and also having fast audio muting capabilities |
US6353867B1 (en) * | 2000-01-14 | 2002-03-05 | Insilicon Corporation | Virtual component on-chip interface |
US6733446B2 (en) * | 2000-01-21 | 2004-05-11 | Medtronic Minimed, Inc. | Ambulatory medical apparatus and method using a telemetry system with predefined reception listening periods |
JP3501762B2 (ja) * | 2000-02-14 | 2004-03-02 | キヤノン株式会社 | 情報処理装置及び方法 |
JP3827928B2 (ja) | 2000-08-25 | 2006-09-27 | Ntn株式会社 | 機械部品の監視システム |
JP2002073121A (ja) | 2000-08-24 | 2002-03-12 | Fuji Electric Co Ltd | ネットワーク制御システム、その通信モジュール、及びリモート制御方法 |
KR100626675B1 (ko) * | 2000-12-21 | 2006-09-22 | 삼성전자주식회사 | 무선 통신기기 및 그 제어방법 |
US6795871B2 (en) * | 2000-12-22 | 2004-09-21 | General Electric Company | Appliance sensor and man machine interface bus |
GB2371449A (en) * | 2001-01-22 | 2002-07-24 | Nokia Mobile Phones Ltd | Synchronizing a new device to a synchronized network of devices |
WO2002077871A1 (en) * | 2001-02-26 | 2002-10-03 | Walter Reed Army Institute Of Research | Browser for an accident and incident registry |
US6477335B1 (en) * | 2001-05-11 | 2002-11-05 | Troy Group, Inc. | Toner cartridge identification system for a printer |
US7369902B2 (en) * | 2001-05-31 | 2008-05-06 | Omron Corporation | Slave units and network system as well as slave unit processing method and device information collecting method |
DE60235232D1 (de) * | 2001-05-31 | 2010-03-18 | Omron Tateisi Electronics Co | Sicherheitsnetzwerksystem und sicherheits-slaves und sicherheitssteuerung und kommunikationsverfahren und informationssammelverfahren und überwachungsverfahren in einem sicherheitsnetzwerksystem |
US7430451B2 (en) * | 2001-05-31 | 2008-09-30 | Omron Corporation | Safety unit, controller system, connection method of controllers, control method of the controller system and monitor method of the controller system |
JP4280003B2 (ja) * | 2001-05-31 | 2009-06-17 | 株式会社日立製作所 | 遠隔保守方法および産業用機器 |
WO2003001307A1 (fr) * | 2001-06-22 | 2003-01-03 | Omron Corporation | Systeme de reseau de securite, esclave de securite, et procede de communication |
WO2003001749A1 (fr) | 2001-06-22 | 2003-01-03 | Omron Corporation | Systeme de reseau securise et esclave securise |
WO2003001306A1 (fr) * | 2001-06-22 | 2003-01-03 | Omron Corporation | Systeme de reseau securise, esclave securise et controleur securise |
JP2003037545A (ja) * | 2001-07-23 | 2003-02-07 | Nec Corp | 近距離無線機能付き移動局及びその消費電力低減方法 |
JP3988559B2 (ja) * | 2002-07-18 | 2007-10-10 | オムロン株式会社 | 通信システム、通信装置及び通信制御方法 |
-
2002
- 2002-06-21 WO PCT/JP2002/006242 patent/WO2003001749A1/ja active Application Filing
- 2002-06-21 EP EP02738779A patent/EP1404061B1/en not_active Expired - Lifetime
- 2002-06-21 JP JP2003508023A patent/JP3748078B2/ja not_active Expired - Lifetime
- 2002-06-21 US US10/481,503 patent/US7472106B2/en not_active Expired - Lifetime
- 2002-06-21 CN CN028124987A patent/CN1518816B/zh not_active Expired - Lifetime
Patent Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JPH03116395A (ja) * | 1989-09-29 | 1991-05-17 | Csk Corp | 自動販売機データ収集システム |
JPH0445697A (ja) * | 1990-06-13 | 1992-02-14 | Nec Corp | ポーリング方式 |
JPH08211792A (ja) * | 1995-02-03 | 1996-08-20 | Mita Ind Co Ltd | 画像形成装置の管理システム |
Non-Patent Citations (1)
Title |
---|
See also references of EP1404061A4 * |
Cited By (15)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JPWO2003001306A1 (ja) * | 2001-06-22 | 2004-10-14 | オムロン株式会社 | 安全ネットワークシステム及び安全スレーブ並びに安全コントローラ |
JP2004234655A (ja) * | 2003-01-28 | 2004-08-19 | Fisher Rosemount Syst Inc | プロセス制御システムおよび安全システムを備えるプロセスプラントにおける統合型診断 |
EP1493960A2 (en) * | 2003-06-30 | 2005-01-05 | Keyence Corporation | Safety relay system |
EP1493960A3 (en) * | 2003-06-30 | 2009-12-16 | Keyence Corporation | Safety relay system |
US8521002B2 (en) | 2004-04-16 | 2013-08-27 | Panasonic Corporation | Recording medium, reproduction device, program and method |
JP2006059356A (ja) * | 2004-08-17 | 2006-03-02 | Phoenix Contact Gmbh & Co Kg | 安全性関連処理のバス結合のための方法と装置 |
US8576707B2 (en) | 2004-08-17 | 2013-11-05 | Phoenix Contact Gmbh & Co. Kg | Method and apparatus for bus coupling of safety-relevant processes |
JP2011054195A (ja) * | 2004-08-17 | 2011-03-17 | Phoenix Contact Gmbh & Co Kg | 安全性関連処理のバス結合のための方法と装置 |
JP4544422B2 (ja) * | 2005-04-19 | 2010-09-15 | オムロン株式会社 | プログラマブル・コントローラ |
JP2006301886A (ja) * | 2005-04-19 | 2006-11-02 | Omron Corp | プログラマブル・コントローラ |
JP4827964B2 (ja) * | 2006-03-22 | 2011-11-30 | フェニックス コンタクト ゲーエムベーハー ウント コムパニー カーゲー | 安全通信構成部品の取付け場所を検証するための方法ならびに制御およびデータ伝送システム |
JP2011516997A (ja) * | 2008-04-17 | 2011-05-26 | ベックホフ オートメーション ゲーエムベーハー | セーフティコントロールを作動させる作動方法、および、そのようなセーフティコントロールを備えたオートメーションネットワーク |
JP2016019162A (ja) * | 2014-07-09 | 2016-02-01 | 株式会社デンソー | 通信装置 |
JP2021082028A (ja) * | 2019-11-19 | 2021-05-27 | 株式会社キーエンス | 安全コントローラおよび履歴表示装置 |
JP7449679B2 (ja) | 2019-11-19 | 2024-03-14 | 株式会社キーエンス | 安全コントローラおよび履歴表示装置 |
Also Published As
Publication number | Publication date |
---|---|
EP1404061A1 (en) | 2004-03-31 |
EP1404061A4 (en) | 2009-03-25 |
JPWO2003001749A1 (ja) | 2004-10-14 |
CN1518816A (zh) | 2004-08-04 |
US20040210620A1 (en) | 2004-10-21 |
JP3748078B2 (ja) | 2006-02-22 |
EP1404061B1 (en) | 2011-08-10 |
CN1518816B (zh) | 2010-04-28 |
US7472106B2 (en) | 2008-12-30 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2003001749A1 (fr) | Systeme de reseau securise et esclave securise | |
JP3925495B2 (ja) | スレーブ及びネットワークシステム並びにスレーブの処理方法及び機器情報収集方法 | |
JP3912378B2 (ja) | 安全ネットワークシステム及び安全スレーブ並びに安全コントローラ | |
US7162311B2 (en) | Safety network system, safety slaves unit, safety controller and communication method and information collecting method and monitoring method for the safety network system | |
JP4338354B2 (ja) | スレーブ | |
JP4569832B2 (ja) | ネットワーク電源モニタシステム | |
US11079826B2 (en) | Control apparatus, control method, and program | |
JPWO2003001307A1 (ja) | 安全ネットワークシステム及び安全スレーブ並びに通信方法 | |
JP3882783B2 (ja) | プログラマブルコントローラ及びcpuユニット並びに通信ユニット及び通信ユニットの制御方法 | |
CN107918590B (zh) | 运算装置以及控制装置 | |
JP4941365B2 (ja) | 産業用コントローラ | |
JP2016095770A (ja) | コントローラ、およびこれを用いた冗長化制御システム | |
JP2004206212A (ja) | 運用監視システム | |
JP4788597B2 (ja) | プログラマブルコントローラ二重化システム | |
JPH0729986U (ja) | 監視制御装置 | |
JP3836671B2 (ja) | ネットワーク二重化装置および方法 | |
JP5042064B2 (ja) | 防犯システム | |
JP2019134350A (ja) | 管理システム | |
JP2014187587A (ja) | 通信部を有する装置 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AK | Designated states |
Kind code of ref document: A1 Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BY BZ CA CH CN CO CR CU CZ DE DK DM DZ EC EE ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NO NZ OM PH PL PT RO RU SD SE SG SI SK SL TJ TM TN TR TT TZ UA UG US UZ VN YU ZA ZM ZW |
|
AL | Designated countries for regional patents |
Kind code of ref document: A1 Designated state(s): GH GM KE LS MW MZ SD SL SZ TZ UG ZM ZW AM AZ BY KG KZ MD RU TJ TM AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE TR BF BJ CF CG CI CM GA GN GQ GW ML MR NE SN TD TG |
|
121 | Ep: the epo has been informed by wipo that ep was designated in this application | ||
WWE | Wipo information: entry into national phase |
Ref document number: 2003508023 Country of ref document: JP |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2002738779 Country of ref document: EP |
|
WWE | Wipo information: entry into national phase |
Ref document number: 028124987 Country of ref document: CN |
|
WWP | Wipo information: published in national office |
Ref document number: 2002738779 Country of ref document: EP |
|
REG | Reference to national code |
Ref country code: DE Ref legal event code: 8642 |
|
WWE | Wipo information: entry into national phase |
Ref document number: 10481503 Country of ref document: US |
|
ENP | Entry into the national phase |
Ref document number: 2004124952 Country of ref document: RU Kind code of ref document: A |