[go: up one dir, main page]

WO2013075895A1 - Procédé de communication redondante entre un terminal d'utilisateur et un serveur de système de gestion - Google Patents

Procédé de communication redondante entre un terminal d'utilisateur et un serveur de système de gestion Download PDF

Info

Publication number
WO2013075895A1
WO2013075895A1 PCT/EP2012/070840 EP2012070840W WO2013075895A1 WO 2013075895 A1 WO2013075895 A1 WO 2013075895A1 EP 2012070840 W EP2012070840 W EP 2012070840W WO 2013075895 A1 WO2013075895 A1 WO 2013075895A1
Authority
WO
WIPO (PCT)
Prior art keywords
terminal
server
message
control system
communication
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/EP2012/070840
Other languages
German (de)
English (en)
Inventor
Rene Bernhard
Antonius Boller
Michael Kasper
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Siemens AG
Siemens Corp
Original Assignee
Siemens AG
Siemens Corp
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Siemens AG, Siemens Corp filed Critical Siemens AG
Priority to EP12786864.4A priority Critical patent/EP2764665A1/fr
Publication of WO2013075895A1 publication Critical patent/WO2013075895A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

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/418—Total factory control, i.e. centrally controlling a plurality of machines, e.g. direct or distributed numerical control [DNC], flexible manufacturing systems [FMS], integrated manufacturing systems [IMS] or computer integrated manufacturing [CIM]
    • G05B19/4185—Total factory control, i.e. centrally controlling a plurality of machines, e.g. direct or distributed numerical control [DNC], flexible manufacturing systems [FMS], integrated manufacturing systems [IMS] or computer integrated manufacturing [CIM] characterised by the network communication
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/40—Bus networks
    • H04L12/40169—Flexible bus arrangements
    • H04L12/40176—Flexible bus arrangements involving redundancy
    • H04L12/40189—Flexible bus arrangements involving redundancy by using a plurality of bus systems
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
    • H04L67/125—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks involving control of end-device applications over a network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/40—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass for recovering from a failure of a protocol instance or entity, e.g. service redundancy protocols, protocol state redundancy or protocol service redirection
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/40—Bus networks
    • H04L2012/4026—Bus for use in automation systems

Definitions

  • the present invention relates to a method for redundant communication between a user terminal and a control system server for an automation system, wherein the automation system comprises a control device for the automatic control of a plant or a device, and the control system server for project planning, for engineering , is set up and designed to operate and / or to monitor the control device.
  • the automation system comprises a control device for the automatic control of a plant or a device
  • the control system server for project planning, for engineering is set up and designed to operate and / or to monitor the control device.
  • Access to the server system exists and in this way, for example, data collected by the server system from the controller are displayed.
  • Such a method is designed and set up for redundant communication between a user terminal and a control system server for an automation system.
  • the automation system comprises a control device for automatically controlling a system or a device.
  • the control system server for configuring, for engineering, for operating and / or monitoring of the control device is set up and designed.
  • the user terminal comprises a first and a second terminal interface for communication with the control system server via at least one communication network.
  • the control system server likewise comprises a first and a second server interface for communication with the user terminal via the at least one communication network.
  • the named method is designed such that a first terminal message with terminal user data for projecting, engineering, operating and / or monitoring the control device is sent to the control system server via the first terminal interface and a second terminal message with the same terminal payload as the first terminal message via the second terminal interface to the control system server is sent.
  • the control system server After receiving a new terminal message, the control system server checks whether it has already received a terminal message with the same user data as in the newly received terminal message. If he has already received a terminal message with the same payload, the host server discards the new terminal message. If he has not yet received a terminal message with the same user data, the control system server stores the newly received terminal message and processes it further below.
  • the control system server Due to the fact that the user terminal twice sends a message with the same user data via various of its interfaces and in general then also various communication paths to the control system server, the latter receives the necessary user data information, even if one of the messages is lost, for example due to a defective cable, a defective device or similar. As a result of the fact that the control system server checks for every incoming message whether it has already received the same user data, it is then avoided that corresponding messages are processed twice. and so unwanted reactions in the control system server could be caused.
  • said method increases the reliability in an automation system, in particular against failures in the field of communication between a terminal and a corresponding control system.
  • the communication between the user terminal and the control system server can take place, for example, via a TCT / IP protocol, an Ethernet protocol, an industrial Ethernet protocol or also an Internet protocol.
  • the user terminal can be embodied, for example, as a PC, a special operator terminal, an operator station, a monitoring station or also an operator control and monitoring station, or also as a similar station or a similar terminal for displaying and inputting information for and by a user.
  • the control system server can, for. B. as a server or computer system with an installed or provided thereon process control system, for example, as a process control system for automatic system or device control.
  • the control system server can also be designed as a server of an operator control and monitoring system or include such. In this case, such a control and monitoring system can be designed and set up for monitoring and controlling, for example, a system or device controlled via a corresponding automatic control system.
  • control system server can also be designed and set up as a server of a configuration system for configuring an automatic system or device controller or include such.
  • a control system server in particular the so-called and / or procedural level of the overall automation system associated or assigned.
  • An automation system may include, for example, one or more control units, for example so-called programmable logic controllers (so-called “PLC” or “PLC”) or even modular programmable logic controllers.
  • PLC programmable logic controllers
  • Such control units can, for example, be designed and set up to control one or more installations or devices.
  • the controlled systems or devices can be attributed to the automation system.
  • such controls may be associated, for example, a control level of the automation system.
  • the plants or devices to be controlled or controlled may belong to a so-called field level of the automation system.
  • the control system server and / or the user terminal can also be assigned to the automation system, in particular if this is designed as an overall system. However, these can also be regarded as independent of the automation system.
  • control system server and / or the control device can furthermore be designed and set up such that by means of the control system server via the control device also an operation and / or monitoring of the one by the
  • Control device controlled system and / or device is possible or carried out.
  • the at least one communication network for communication between the user terminal and the control system server can comprise, for example, one, two or even more communication networks.
  • each of these communication networks can be designed and set up, for example, as so-called LAN, WLAN, as Internet, as Ethernet, as industrial Ethernet or a comparable network or comprise such a network.
  • the at least one communication network can have exactly two comparable, identical or identically designed or redundant communication networks. The communication between the first terminal interface and the first server interface via a first of the two communication networks, while the communication between the second terminal interface and the second server interface via the other of the communication networks takes place.
  • the at least one communication network can also be designed as a ring network, with the first and second interfaces of the user terminal and the control system server respectively being designed as so-called ring ports for integrating the user terminal or the control system server into the ring network are and / or are interconnected as well.
  • the at least one communication network can consist of exactly one such communication ring network.
  • the terminal messages can be generated, for example, in such a way that, after provision of the user data to be transmitted with regard to configuring, engineering, operating and / or monitoring the control device or a system or a device connected thereto, the first terminal Message with this user data and the second terminal message is created with the same user data.
  • the two terminal messages may continue to have an identifier, by means of which a receiver can recognize when receiving one of these messages that a duplicate message with the same user data has been sent for this purpose.
  • Such an identifier can for example give an immediate indication of the message sent in parallel, for example by comprising a unique identifier of this parallel message.
  • such an identifier can also only signal in general that a parallel with the same user data was sent to this message to the same recipient.
  • the second terminal message may be generated by duplicating, copying or doubling the first terminal message so that first and second terminal messages are identical.
  • the terminal messages can each have an identifier that generally signals to a recipient of the message that a duplicate was sent for this message.
  • first and second terminal messages can also be identical except for a reference identifier to the respective other message and / or a unique message identification identifier.
  • control system server can be designed and set up such that it checks for each incoming message whether it has already received another terminal message with the same user data.
  • control system server can also be embodied and set up such that, in the case of a newly received terminal message, it checks, for example by means of an identifier within the message, whether an ever duplicate has been sent, and then only checks whether it already has a terminal message was received with the same user data including the other above procedure, if such an identifier is present.
  • the check as to whether a terminal message has already been received with the same user data can be carried out by the control system server, for example, by comparing the user data of a newly received terminal message with the user data of previously received, stored messages. Furthermore, the check can also take place, for example, on the basis of specific user data or an identifier assigned to a particular terminal message, which in particular has a unique identifier for specific user data or also a specific terminal identifier. Message can be. Such an identifier or signature, for example, as a kind of counter, the z. B. may be performed within the transmitter, or even be obtained from the user data or the entire terminal message signature.
  • the first and second terminal messages may have the same identifier, so that the control system server can relatively easily recognize, by comparing a newly obtained identifier with stored identifiers, whether it has already received a message with the same user data.
  • control system server determines that it has already received the duplicate sent by the user terminal for a newly received terminal message, it discards the newly received message.
  • the newly received terminal message is stored and processed further within the control system server or for further processing by the control system server to another unit further mediated.
  • the storage can take place at least among other things within a specially set up for the above-mentioned duplicate check database.
  • this database for example, for each incoming terminal message for which a duplicate has not yet been registered, and for which a duplicate check should or must be made, the information required for the duplicate check is stored. This may in particular include an identifier for the sender, the receiver, a message identifier, in particular a unique message identifier and / or the payload of the message. In particular, in such a database at most one identifier for the receiver, one identifier for the transmitter, and one unique identifier for the transmitted terminal message or a unique identifier stored for the related message pair itself.
  • control system server checks after receiving the new terminal message at the first server interface whether it has already received a terminal message with the same user data at the second server interface and vice versa. The newly received terminal message is discarded if it already has a terminal message with it
  • the newly received terminal message is stored and further processed by the control system server if the control system server has not yet received a terminal message with the same user data at the other of the server interfaces.
  • the storage of the new terminal message may include, for example, storing in a special database, which for the described duplicate check of the
  • Terminal messages is used.
  • an identifier for the server interface to which the respective terminal message was received can also be stored.
  • At least one communication network can be designed and set up in such a way that a message sent, for example, via the first terminal interface is passed on so that it can be received at the first server interface, but not at the second server interface , or vice versa.
  • a message sent, for example, via the first terminal interface is passed on so that it can be received at the first server interface, but not at the second server interface , or vice versa.
  • an increased reliability can be achieved by the other communication path may continue to be functional in case of disturbances in one of the mentioned communication paths and thus reach the corresponding user data more secure the desired recipient.
  • the first and second terminal message each comprise a redundancy identifier
  • the control system server is designed and set up in such a way that it complies with the test, discard or storage method and method mentioned in the present description Execution of a received terminal message only if the received terminal message comprises the redundancy identifier.
  • Such a redundancy identifier can be, for example, a general identifier for a duplicate having the same user data for a received terminal message.
  • the redundancy identifier can also include an identifier that includes a direct reference to the parallel transmitted terminal message with the same user data, for example, a reference to a unique message identifier or message identification number of the parallel-dispatched terminal message.
  • the guidance system server may first check if the received new terminal message has a redundancy identifier. If this is not the case, the newly received terminal message is immediately forwarded to the further processing in the control system server, it also being possible for it to be stored. If the received terminal message has a redundancy identifier, the control system server checks, for example according to the present description, whether a corresponding duplicate of the terminal message already exists and then undertakes, for example, the further steps listed in the present description.
  • the described method can furthermore be designed in such a way that the contents of the first and second terminal messages are identical.
  • the second terminal message can be generated by copying the first terminal message.
  • a reference identifier can be added to the respective other message.
  • the generation of the first and second terminal message for example, according to or also based on the so-called HSR and / or PRP standard, eg according to IEC 62439-3, be carried out or trained.
  • the duplicate check explained in the present description and further processing of such double-dispatched terminal messages in accordance with the aforementioned HSR and / or PRP standard, for example according to IEC 62439-3 or based thereon, may be designed and set up.
  • the presently illustrated method may be configured such that the control system server in the context of processing a received and stored first or second terminal message, a message for data request, for engineering, for engineering, for operating
  • control system server via the user terminal by means of the control system server, monitoring or management of a control device or a system connected to the control device or a device connected to the control device can take place.
  • the communication is usually the case in such a communication Connection between the user terminal and the control system server is a weak point, since more often longer distances have to be overcome and under certain circumstances also be resorted to communication networks (eg a public network, LAN or WAN or Internet) to which in the context of creating a corresponding automation system or an automated overall system little or no impact exists.
  • the control system server is often located more in the vicinity of the system or control device than in the area of a user terminal.
  • the mentioned weak point in the communication between the user terminal and the control system server can be made more fail-safe, so that a more reliable monitoring and a more reliable management of a corresponding automation system, a control device or installation or a device is achieved can be.
  • a method also solves the above object in which the roles of the user terminal and the host server are interchanged in the communication method as described above. That is, in such a method, the guidance system server would enter the role of the user terminal as a message sender, as described above, sending server messages instead of terminal messages. The user terminal then enters the role of the control system server as a receiver as described above.
  • both the control system server as the sender, the user terminal as the receiver and the server messages instead of the terminal message can be designed and set up correspondingly on the basis of the above description.
  • Particularly advantageous is a method in which both the communication from the user terminal to the control system server via first and second terminal messages according to the present description takes place, as well as the communication from the control system server to the user terminal via first and second server Messages according to the present description is performed. In this way, all communication between the user terminal and the control system server can be made more resilient in both directions.
  • the communication between the user terminal and the control system server can take place both in one direction and the other via an internet protocol, in particular via a web and / or http protocol or web and / or http protocol.
  • Message include.
  • such http protocol messages or web messages or also internet messages within a data packet can be transmitted, for example, as user data or the user data of such a data packet can be corresponding web and / or http protocol or also internet messages include.
  • a transmission between the user terminal and the control system server can be made more fail-safe with conventional and widely used transmission protocols and methods, for example including the use of web servers.
  • a communication system with a user terminal and a control system server for redundant communication between the user terminal and the control system server, wherein the user terminal and / or the control system server for carrying out a method are designed and set up according to the present description.
  • the user terminal and / or the control system server can continue to be designed and set up in accordance with the present description.
  • the at least one communication network for communication between the user terminal and the control system server may further comprise, for example, a first and a second communication network, the first communication network for communication between the first terminal interface and the first server interface and the second communication network is designed and set up for communication between the second terminal interface and the second server interface. It can further be provided that the first and second communication network have no direct connection. However, for example, further devices may have both an interface with the first and one with the second communication network. Furthermore, the at least one communication network can also comprise further communication networks. The at least one communication network can also consist exactly only of the first and second communication networks.
  • the reliability can be further increased between the user terminal and the control system server, since in this way separate communication paths are created and in the event of malfunctions in one of the communication paths, a functioning communication is still possible or at least via the second of the communication paths. can be.
  • the at least one communication network for communication between the control system server and the user terminal can be designed as a ring network, or comprise a ring network, wherein the control system server and the user terminal each because they are integrated via their first and second interfaces in the ring network.
  • a ring network arise two independent communication paths between the first server interface and the first terminal interface and the second server interface and the second terminal interface, so that the above-mentioned advantages in terms of reliability even in the case described here Possibility of designing the at least one communication network as ring network present.
  • the present object is also achieved by a control system server for a communication network according to the present description for communication with a user terminal, wherein the control system server for carrying out a method for receiving, checking, storing and / or processing of
  • Terminal messages may be formed according to the present description.
  • the control system server can also be designed and set up for sending the first and second server messages according to the present description.
  • the control system server can be designed both for receiving and processing terminal messages according to the present description and for sending the first and second server messages according to the present description.
  • control system server can be designed and set up for communication with the user terminal in accordance with an HSR and / or PRP standard, in particular according to IEC 62439-3.
  • the sending of the first and second server messages can, for example, also take place via an Internet protocol or comprise corresponding Internet messages or http messages or Web messages.
  • control system server can have a modular structure and comprise a server base device and a server communication module.
  • the processing of the terminal messages can then be carried out, for example, in the server base unit.
  • Server base unit and the server communication module can be designed as two structurally separate devices, which are connected for example via a cable connection or wireless communication connection.
  • the server communication module can be designed and set up for communication in accordance with the HSR and / or PRP standard, in particular according to IEC 62439-3 or the like.
  • the server communication module can, for example, perform the duplicate check on received terminal messages and their correct forwarding to the server basic unit and / or generate and send corresponding first and second server messages from messages or data packets originating from the server base unit.
  • such an older device can be integrated as a server base device by adding a server communication module in a fail-safe communication according to the present description.
  • the present object is also achieved by a user terminal for a communication network according to the present description for communicating with a control system server according to the present description, wherein the user terminal for carrying out a method for receiving, checking, storing and / or Processing server messages according to the present description and / or for sending the first and second terminal messages according to the present description is designed and set up.
  • the user terminal can be designed and set up, for example, for communication in accordance with the HSR and / or PRP standard, in particular according to IEC 62439-3 or the like.
  • the sending of the first and second terminal messages may, for example, take place via an internet protocol or include corresponding internet, http or web messages.
  • the user terminal may also have a modular design and comprise a terminal basic device and a terminal communication module. In this case, for example, receiving, checking and / or storing the server messages and / or the
  • Sending the first and second terminal messages by the server communication module A presentation of information relating to the server messages, for example based on user data transmitted therewith, can be performed by the terminal base unit. Furthermore, the input of information for the creation of terminal messages to be transmitted user data in the terminal base unit can also be done.
  • the duplicate check takes place when receiving messages together with corresponding data storage in the terminal communication module, whereby this then only forwards the already "isolated" messages to the terminal base unit.
  • the base unit sends user data to the terminal communication module or also
  • the generation of the first and second terminal messages and the corresponding sending of these messages can then take place via the terminal communication module.
  • FIG. 1 shows an exemplary automation system with redundant communication
  • 2 shows the exemplary automation system from FIG. 1 with a further configuration possibility of the redundant communication system.
  • FIG. 1 shows an automation system 100 with a memory-programmable controller (PLC) 400 for controlling a field device 500.
  • PLC memory-programmable controller
  • the communication between the PLC 400 and the field device 500 takes place via a first fieldbus network 450, which has a first fieldbus interface 422 of the PLC 400 a first field device interface 512 of the field device 500 connects.
  • a second communication connection via a second fieldbus network 452 between a second field bus interface 424 of the PLC 400 to a second field device interface 514 of the field device.
  • the automation system further comprises a control system server 300 for configuring and operating and monitoring the PLC 400 with the field device 500 via operator terminals 210, 220.
  • the communication between the control system server 300 and the PLC 400 is designed to be redundant. It takes place on the one hand via a first control network 350, for the transmission of information between a first control network port 322 of the control system server 300 and a first control network interface 412 of the PLC 400.
  • the communication between the control system server 300 and the PLC 400 can in parallel also via a second control network 452 to the transmission Data between a second control network port 324 of the control system server 300 and a second control network interface 414 of the PLC 400 done.
  • the automation system 100 For operating, setting up, monitoring, evaluating or similar activities of the control system server, or of the project planning and the operator control and monitoring system thereon, the automation system 100 has the two operating terminals 210, 220, which are referred to as PCs 210 , 220 are formed. On the operator terminals, information on the configuration, management or operation and monitoring of the PLC 400 with the field device 500 can be viewed, changed or set by the control system server 300.
  • the operator terminals 210, 220 may, for example, also be located at locations that are spatially substantially separated from the rest of the automation system 100, and may permit remote control or remote monitoring of the rest of the automation system 100.
  • the communication between the control system server 300 and the terminals 210, 220 is in turn designed to be redundant.
  • a first communication path via a first terminal network 250 between a first terminal network interface 312 of the control system server 300 and respectively first terminal interfaces 212, 222 of the operator terminals 210, 220.
  • a second parallel communication path between the control system server 300 and the operator terminals 210, 220 takes place via a second terminal network 252 between a second terminal network interface 314 of the control system server 300 and in each case second terminal interfaces 214, 224 of the user terminals 210, 220.
  • both the first terminal network 250 and the second terminal network 252 may comprise public communication networks or Internet parts in order to be able to bridge a relatively large spatial distance of user terminals 210, 220 and control system server 300.
  • the control system server To transmit information from the control system server 300 to the operator terminals 210, 220, the control system server generates a corresponding server message, provides it with, for example, the address of the operator terminal 210 shown on the left in FIG. 1 and an identifier that Duplicate transfer method is used.
  • the terminal server 300 adds a unique identifier to the message, which distinguishes it, at least in the normal daily routine, from further messages of the control system server. On the one hand, the control system server 300 then sends these
  • control system server 300 duplicates this message and sends this duplicate via its second terminal network interface 314 into the second terminal network 252.
  • the first server message first reaches the terminal interface 212 of the left user terminal 210. Based on the duplicate method identifier contained in the message, the user terminal 210 recognizes that The transmission of this message was a duplicate procedure used. The user terminal 210 then performs a duplicate check by checking to see if it finds a message with the same unique identification number in a duplicate database established in the user terminal 210.
  • the duplicated message Since the duplicated message has not yet arrived at the left operator terminal 210 due to the mentioned different run times, no such data record will be present in the duplicate check database of the left terminal 210. Therefore, a new, for the first arrived server message characteristic record is now created in the duplicate audit database, which includes at least the unique identifier of the received server message.
  • the message will then be displayed within the left ter- minals 210 further processed and evaluated, for example, the user data, for example, display corresponding data from the control system server 300 with respect to the controlled system on a screen of the terminal 210.
  • the duplicated server message will arrive at the second terminal interface 214 of the left terminal 210 via the second terminal network 252. Based on the duplicate check identifier within the duplicated server message, the terminal 210 recognizes that the received message is part of a duplicate message dispatch. It then checks in its duplicate check database whether there already exists a data record with the unique message identification code of the received second server message. In the example described here, this is the case since, as described, the parallel server message has already arrived and been recorded in the terminal 210. The left terminal 210 then discards the second, duplicated server message and makes no further action therewith. If appropriate, the data record associated with this message pair can then also be deleted in the duplicate check database of the left-hand terminal 210.
  • the return channel that is to say the transmission of information from the left-hand terminal 210 to the control system server 300
  • the operator terminal 210 duplicates a message to be sent via the two terminal interfaces 212, 214, and the corresponding duplicate check as described above, after receiving the messages via the terminal network interfaces 312, 314 of the control system server 300 in the control system server 300 are performed accordingly.
  • the communication can continue via the still functioning terminal. Network 250, 252, take place.
  • the duplicate check regularly results in such fault cases that no duplicates are yet present, since the communication via the respective other communication network is not working properly.
  • An advantage of this method is in particular that in addition to increasing the reliability of the communication network, no switching over or switching to undisturbed, alternative or secure communication paths is necessary, as with other redundancy communication method
  • a communication can be maintained without time delay in the method described here.
  • the redundant communication in the control networks 350, 352 between the control system server 300 and PLC 400 can be carried out using one of the common and known redundancy methods or also a method according to the present description. This also applies to the redundant communication via the fieldbus networks 450, 452 between the PLC 400 and the field device 500.
  • FIG. 2 shows a further embodiment of the redundant communication networks in the automation system 100. Instead of the two redundant terminal networks 250, 252, a ring terminal network is used 260 which connects the user terminals 210, 220 and the control system server 300 in a communication ring. Furthermore, the control networks 350, 352 are in
  • Fig. 2 replaced by a ring control network 360.
  • the redundant fieldbus networks 450, 452 in FIG. 1 are also replaced in FIG. 2 by a fieldbus ring network 460.
  • the communication between the terminals 210, 220 and the control system server 300 as well as between the control system server 300 and PLC 400 and the PLC 400 and field devices 500 continue to be carried out as described in relation to FIG. 1.

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Automation & Control Theory (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Quality & Reliability (AREA)
  • Manufacturing & Machinery (AREA)
  • General Engineering & Computer Science (AREA)
  • Health & Medical Sciences (AREA)
  • Computing Systems (AREA)
  • General Health & Medical Sciences (AREA)
  • Medical Informatics (AREA)
  • Computer Security & Cryptography (AREA)
  • Safety Devices In Control Systems (AREA)

Abstract

La présente invention concerne un procédé de communication redondante entre un terminal d'utilisateur (210, 220) et un serveur de système de gestion (300) destiné à un système d'automatisation (100). Le système d'automatisation (100) comprend un dispositif de commande (400) servant à commander automatiquement une installation ou un appareil (500) et le serveur de système de gestion (300) est conçu et agencé pour projeter, réaliser, utiliser et/ou surveiller le dispositif de commande (400). Il est prévu en outre que le terminal d'utilisateur (210, 220) comporte une première (212, 222) et une deuxième interface de terminal (214, 224) pour communiquer avec le serveur de système de gestion (300) par le biais d'au moins un réseau de communication (250, 252, 260), que le serveur de système de gestion (300) comporte une première (312) et une deuxième interface de serveur (314) pour communiquer avec le terminal d'utilisateur (210, 220) par le biais du ou des réseaux de communication (250, 252, 260), et qu'un premier message de terminal contenant des données de terminal utiles pour projeter, réaliser, utiliser et/ou surveiller le dispositif de commande (300) est envoyé par le biais de la première interface de terminal (212, 222) au serveur de système de gestion (300) et un deuxième message de terminal contenant les données de terminal utiles est envoyé par le biais de la deuxième interface de terminal (214, 224) au serveur de système de gestion (300). Après avoir reçu un nouveau message de terminal, le serveur de système de gestion (300) contrôle s'il a déjà reçu un message de terminal contenant les mêmes données utiles et rejette le nouveau message de terminal lorsqu'il a déjà reçu et mémorisé un message de terminal contenant les mêmes données utiles, ou bien il mémorise le nouveau message et en poursuit le traitement lorsqu'il n'a pas encore reçu de message de terminal contenant les mêmes données utiles.
PCT/EP2012/070840 2011-11-21 2012-10-22 Procédé de communication redondante entre un terminal d'utilisateur et un serveur de système de gestion Ceased WO2013075895A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
EP12786864.4A EP2764665A1 (fr) 2011-11-21 2012-10-22 Procédé de communication redondante entre un terminal d'utilisateur et un serveur de système de gestion

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
DE102011086726.0A DE102011086726B4 (de) 2011-11-21 2011-11-21 Verfahren zur redundanten Kommunikation zwischen einem Nutzer-Terminal und einem Leitsystem-Server
DE102011086726.0 2011-11-21

Publications (1)

Publication Number Publication Date
WO2013075895A1 true WO2013075895A1 (fr) 2013-05-30

Family

ID=47178591

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/EP2012/070840 Ceased WO2013075895A1 (fr) 2011-11-21 2012-10-22 Procédé de communication redondante entre un terminal d'utilisateur et un serveur de système de gestion

Country Status (3)

Country Link
EP (1) EP2764665A1 (fr)
DE (1) DE102011086726B4 (fr)
WO (1) WO2013075895A1 (fr)

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3104242A1 (fr) * 2015-06-12 2016-12-14 Siemens Aktiengesellschaft Systeme de commande et procede pour la évaluation de la communication dans un processus technique
DE102020130622B4 (de) 2020-11-19 2024-05-23 Vega Grieshaber Kg Messgerät zur Prozessautomatisierung im industriellen Umfeld
EP4295201A1 (fr) 2021-02-18 2023-12-27 Sew-Eurodrive GmbH & Co. KG Dispositif de commande pour un système d'automatisation, système d'automatisation et procédé pour faire fonctionner un dispositif de commande
DE102021001792B3 (de) 2021-04-07 2022-05-25 Sew-Eurodrive Gmbh & Co Kg Automatisierungssystem und Verfahren zum Betrieb eines Automatisierungssystems

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6151625A (en) * 1997-09-10 2000-11-21 Schneider Automation Inc. Internet web interface including programmable logic controller for controlling output devices based on status of input devices
US20050119863A1 (en) 2003-08-07 2005-06-02 Buikema John T. Manufacturing monitoring system and methods for determining efficiency
US20060069946A1 (en) * 2004-09-16 2006-03-30 Krajewski John J Iii Runtime failure management of redundantly deployed hosts of a supervisory process control data acquisition facility
EP2148473A1 (fr) * 2008-07-22 2010-01-27 ABB Research Ltd Noeuds de commutation pour réseaux à forte disponibilité

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4780869A (en) * 1987-05-20 1988-10-25 Allen-Bradley Company, Inc. Local area network redundancy system
JPH10200552A (ja) * 1997-01-16 1998-07-31 Yamatake Honeywell Co Ltd イーサネット通信を用いた冗長方法
FR2832006B1 (fr) * 2001-11-05 2004-08-06 Airbus France Procede de mise en oeuvre d'un reseau de communication redondant de type ethernet full-duplex commute
EP1657888A1 (fr) * 2004-11-16 2006-05-17 Abb Research Ltd. Réception de trames redondantes et non redondantes

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6151625A (en) * 1997-09-10 2000-11-21 Schneider Automation Inc. Internet web interface including programmable logic controller for controlling output devices based on status of input devices
US20050119863A1 (en) 2003-08-07 2005-06-02 Buikema John T. Manufacturing monitoring system and methods for determining efficiency
US20060069946A1 (en) * 2004-09-16 2006-03-30 Krajewski John J Iii Runtime failure management of redundantly deployed hosts of a supervisory process control data acquisition facility
EP2148473A1 (fr) * 2008-07-22 2010-01-27 ABB Research Ltd Noeuds de commutation pour réseaux à forte disponibilité

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
KIRRMANN H ET AL: "HSR: Zero recovery time and low-cost redundancy for Industrial Ethernet (High availability seamless redundancy, IEC 62439-3)", EMERGING TECHNOLOGIES&FACTORY AUTOMATION, 2009. ETFA 2009. IEEE CONFERENCE ON, IEEE, PISCATAWAY, NJ, USA, 22 September 2009 (2009-09-22), pages 1 - 4, XP031575609, ISBN: 978-1-4244-2727-7 *

Also Published As

Publication number Publication date
DE102011086726A1 (de) 2013-05-23
DE102011086726B4 (de) 2014-04-03
EP2764665A1 (fr) 2014-08-13

Similar Documents

Publication Publication Date Title
EP2838220B1 (fr) Procédé de transmission redondante de messages dans un réseau de communication industriel et appareil de communication
EP2940926B1 (fr) Procédé de configuration d'un appareil de communication au sein d'un système d'automatisation industriel et unité de répartition pour un serveur de configuration d'un réseau de communication industriel
EP2924928B1 (fr) Composant de réseau récepteur destiné à fonctionner dans un réseau de communication et procédé de fonctionnement d'un réseau de communication
EP3295645B1 (fr) Procédé et système de transmission sans effet rétroactif de données entre réseaux
EP2688249A1 (fr) Procédé de transmission de nouvelles dans un réseau de communication industriel pouvant fonctionner de manière redondante et appareil de communication pour un réseau de communication industriel pouvant fonctionner de manière redondante
EP3155763A1 (fr) Transmission redondante de télégrammes de données dans des réseaux de communication présentant une topologie en anneau
EP1738236A1 (fr) Reseau d'automatisation a composantes reseau produisant des messages d'etat
EP2913727B1 (fr) Procédé de transmission de messages via un système bus de fond de panier d'un automate industriel modulaire
EP3787237B1 (fr) Procédé de transmission de données dans un réseau de communication à fonctionnement redondant et appareil de communication par couplage
DE102011086726B4 (de) Verfahren zur redundanten Kommunikation zwischen einem Nutzer-Terminal und einem Leitsystem-Server
EP3414632A1 (fr) Procédé et dispositif pour contrôler un traitement et une transmission de données dans une chaîne de sécurité d'un système de sécurité
WO2005053221A2 (fr) Reseau, notamment reseau pa profibus, a proprietes de redondance, element de ramification pour appareil d'abonne dans un reseau de ce type, gestionnaire de redondance pour un reseau de ce type et procede pour faire fonctionner un reseau de ce type
DE10305415B4 (de) Verfahren und Vorrichtung zum medienredundanten Betreiben eines Endgeräts in einem Netzwerk
EP3343303B1 (fr) Système de radiocommunication pour un système d'automatisation industrielle et son procédé de fonctionnement
DE102013211406A1 (de) Kommunikationsgerät zur Verbindung eines Feldgeräts eines industriellen Automatisierungssystems mit einer ausfallgesicherten Steuerungseinheit und industrielles Automatisierungssystem
WO2001031407A2 (fr) Systeme et procede destines a empecher l'acces non autorise a un module, notamment dans des systemes automatises
WO2004030275A1 (fr) Systeme de communication entre des dispositifs utilisateurs et unite de diagnostic
EP3699705A1 (fr) Procédé de surveillance d'un réseau de communication industriel, système de sécurité, réseau de communication industriel, programme informatique et support lisible par ordinateur
EP2854345B1 (fr) Procédé et appareil de communication couplé pour la transmission de messages dans un réseau de communication industriel à fonctionnement redondant
DE10207527A1 (de) Lokales Netzwerk, insbesondere Ethernet-Netzwerk, mit Redundanzeigenschaften sowie Koppelgerät für ein derartiges Netzwerk
DE19743758C1 (de) Responsives System zur digitalen Signalverarbeitung sowie Verfahren zum konsistenten Betrieb eines responsiven Systems
DE102017208836A1 (de) Statussignalausgabe
EP3607437B1 (fr) Procédé de configuration d'au moins un dispositif d'un véhicule ferroviaire dans un réseau, programme informatique et support d'enregistrement lisible par ordinateur
EP3157187B1 (fr) Procédé temporisé de transport périodique en temps réel et tolérant aux pannes de données dans un système informatique réparti
DE102018221417B4 (de) Fahrzeug mit einem Netzwerkverteiler zum Melden einer Störung in einem Kommunikationsnetzwerk

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 12786864

Country of ref document: EP

Kind code of ref document: A1

REEP Request for entry into the european phase

Ref document number: 2012786864

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 2012786864

Country of ref document: EP

NENP Non-entry into the national phase

Ref country code: DE