METHOD FOR OPERATING SAFETY CONTROL AND AUTOMATION NETWORK HAVING SUCH SAFETY CONTROL

• US 20170139388A1
• Filed: 01/30/2017
• Published: 05/18/2017
• Est. Priority Date: 08/08/2014
• Status: Active Grant

• Current Assignee: Beckhoff Automation GmbH
• Original Assignee: Beckhoff Automation GmbH
• Inventors: Schiller, Frank, Sachs, Jens, Bttner, Holger
• Granted Patent: US 10,732,594 B2
• Time in Patent Office: Days
• CPC Class Codes: G05B 19/0425 Safety, monitoring
• CPC Class Codes: G05B 19/054 Input/output
• CPC Class Codes: G05B 2219/14012 Safety integrity level, safety integrated systems, SIL, SIS
• CPC Class Codes: G05B 2219/2231 Master slave
• CPC Class Codes: G05B 2219/24008 Safety integrity level, safety integrated systems SIL SIS
• CPC Class Codes: G05B 2219/25157 Checksum CRC
• CPC Class Codes: G05B 2219/25232 DCS, distributed control system, decentralised control unit
• CPC Class Codes: G05B 2219/33273 DCS distributed, decentralised controlsystem, multiprocessor
• CPC Class Codes: H04L 1/00 Arrangements for detecting or preventing errors in the information received correcting synchronisation H04L7/00

Abstract

A method operates a safety control in an automation network having a master subscriber which carries out the safety control, at least one first slave subscriber which is assigned a first safety integrity level, and at least one second slave subscriber which is assigned a second safety integrity level. The first safety integrity level and the second safety integrity level differ from each other. A first safety code determination method is assigned to the first slave subscriber and a second safety code determination method is assigned to the second slave subscriber. The first safety code determination method and the second safety code determination method differ from each other. The master subscriber and the first slave subscriber use the first safety code determination method for interchanging a safety data block. The master subscriber and the second slave subscriber use the second safety code determination method for interchanging a safety data block.

Claims

1. A method for operating safety control in an automation network having a master subscriber which carries out the safety control, at least one first slave subscriber which is assigned a first safety integrity level, and at least one second slave subscriber which is assigned a second safety integrity level,

the first safety integrity level and the second safety integrity level differing,

a first safety code determination method being assigned to the first slave subscriber and a second safety code determination method being assigned to the second slave subscriber,

the first safety code determination method and the second safety code determination method differing, and

the master subscriber and the first slave subscriber using the first safety code determination method for interchanging a safety data block, and the master subscriber and the second slave subscriber using the second safety code determination method for interchanging a safety data block.

2. The method as claimed in claim 1, the first and second safety code determination methods carrying out a cyclic redundancy check, a first safety code generator polynomial being assigned to the first safety code determination method and a second safety code generator polynomial being assigned to the second safety code determination method,

the master subscriber and the first slave subscriber using the first safety code generator polynomial for the cyclic redundancy check for interchanging a safety data block, and the master subscriber and the second slave subscriber using the second safety code generator polynomial for the cyclic redundancy check for interchanging a safety data block.

3. The method as claimed in claim 2, different residual error probabilities for the occurrence of an error being assigned to the first and second safety integrity levels, and the Hamming distance of the first safety code generator polynomial differing from the Hamming distance of the second safety code generator polynomial.

4. The method as claimed in claim 1, address allocation for the at least first slave subscriber having the first safety integrity level and address allocation for the at least second slave subscriber having the second safety integrity level being carried out independently of one another.

5. A method for operating safety control in an automation network having a master subscriber which carries out the safety control, at least one first slave subscriber which is assigned a first safety integrity level, and at least one second slave subscriber which is assigned a second safety integrity level, the first safety integrity level and the second safety integrity level differing,

the master subscriber, the first slave subscriber and the second slave subscriber being connected to one another via a data transmission path and each having a safety layer and a data link layer,

the safety layer using a safety code determination method to determine, in a transmission mode, a safety code for a safety data block to be transmitted, and the data link layer forming a data packet containing the safety data block and the safety code for transmission on the data transmission path, and

the data link layer extracting a safety data block and an associated safety code from a data packet received via the data transmission path in a reception mode, and the safety layer verifying the safety code for the safety data block using the safety code determination method,

a first safety code determination method being assigned to the first slave subscriber and a second safety code determination method being assigned to the second slave subscriber,

the first safety code determination method and the second safety code determination method differing, and

the master subscriber and the first slave subscriber using the first safety code determination method for interchanging a safety data block, and the master subscriber and the second slave subscriber using the second safety code determination method for interchanging a safety data block.

6. The method as claimed in claim 5, the first and second safety code determination methods carrying out a cyclic redundancy check, a first safety code generator polynomial being assigned to the first safety code determination method and a second safety code generator polynomial being assigned to the second safety code determination method,

the master subscriber and the first slave subscriber using the first safety code generator polynomial for the cyclic redundancy check for interchanging a safety data block, and the master subscriber and the second slave subscriber using the second safety code generator polynomial for the cyclic redundancy check for interchanging a safety data block.

7. The method as claimed in claim 6, different residual error probabilities for the occurrence of an error being assigned to the first and second safety integrity levels, and the Hamming distance of the first safety code generator polynomial differing from the Hamming distance of the second safety code generator polynomial.

8. The method as claimed in claim 5, address allocation for the at least first slave subscriber having the first safety integrity level and address allocation for the at least second slave subscriber having the second safety integrity level being carried out independently of one another.

9. An automation network having a master subscriber which carries out safety control, at least one first slave subscriber which is assigned a first safety integrity level, and at least one second slave subscriber which is assigned a second safety integrity level, the first safety integrity level and the second safety integrity level differing,

the master subscriber, the first slave subscriber and the second slave subscriber being connected to one another via a data transmission path and each having a safety layer and a data link layer,

a first safety code determination method being assigned to the first slave subscriber and a second safety code determination method being assigned to the second slave subscriber,

the first safety code determination method and the second safety code determination method differing, and

the master subscriber and the first slave subscriber using the first safety code determination method for interchanging a safety data block, and the master subscriber and the second slave subscriber using the second safety code determination method for interchanging a safety data block.

10. The automation network as claimed in claim 9, in a transmission mode, the safety layer using a safety code determination method to determine a safety code for a safety data block to be transmitted and the data link layer forming a data packet containing the safety data block and the safety code for transmission on the data transmission path.

11. The automation network as claimed in claim 9, in a reception mode, in the data link layer extracting a safety data block and an associated safety code from a data packet received via the data transmission path and the safety layer verifying the safety code for the safety data block using the safety code determination method.

12. The automation network as claimed in claim 9, the first and second safety code determination methods carrying out a cyclic redundancy check, a first safety code generator polynomial being assigned to the first safety code determination method and a second safety code generator polynomial being assigned to the second safety code determination method,

the master subscriber and the first slave subscriber using the first safety code generator polynomial for the cyclic redundancy check for interchanging a safety data block, and the master subscriber and the second slave subscriber using the second safety code generator polynomial for the cyclic redundancy check for interchanging a safety data block.

13. The automation network as claimed in claim 12, different residual error probabilities for the occurrence of an error being assigned to the first and second safety integrity levels, and the Hamming distance of the first safety code generator polynomial differing from the Hamming distance of the second safety code generator polynomial.

14. The automation network as claimed in claim 9, address allocation for the at least first slave subscriber having the first safety integrity level and address allocation for the at least second slave subscriber having the second safety integrity level being carried out independently of one another.

15. The automation network as claimed in claim 9, the data transmission path being an Ethernet-based field bus.