Coupling of safe fieldbus systems

• US 20060229737A1
• Filed: 03/03/2006
• Published: 10/12/2006
• Est. Priority Date: 03/07/2005
• Status: Active Grant

• Current Assignee: Phoenix Contact GmbH & Company KG
• Original Assignee: Phoenix Contact GmbH & Company KG
• Inventors: Esch, Rainer, Landwehr, Heinz-Carsten
• Granted Patent: US 7,809,449 B2
• Time in Patent Office: Days
• US Class Current: 700/1
• CPC Class Codes: G05B 2219/25205 Encrypt communication
• CPC Class Codes: H04L 12/462 LAN interconnection over a bridge based backbone
• CPC Class Codes: H04L 12/66 Arrangements for connecting between networks having differing types of switching systems, e.g. gateways
• CPC Class Codes: H04L 2012/40208 characterized by the use of a particular bus standard
• CPC Class Codes: H04L 41/0806 for initial configuration or provisioning, e.g. plug-and-play

Abstract

Generally, a means for coupling widely differing fieldbus or network systems to their own respective safety mechanisms is provided, in such a way as to ensure the transmission of safety data between at least two bus/network systems with different safety mechanisms. A method and an apparatus are provided for coupling at least two (field)bus/network systems to respectively different safety mechanisms, in particular respective proprietary safety mechanisms, with safety data which is to be transmitted between the different system-based safety mechanisms being processed additionally using a safe data structure which is defined but is system-independent.

Claims

1. A method for coupling at least two (field)bus/network systems each having different proprietary safety mechanisms, wherein safety data to be transmitted between the different system-based safety mechanisms is processed additionally using a defined system-independent safe data structure.

2. The method of claim 1, wherein safety data which is to be transmitted between the systems is converted from a system-dependent safe data structure (321, 322, 366), which is in the form of one or more channels, before being transmitted using the defined, but system-independent, safe data structure.

3. The method of claim 1, wherein, safety data to be transmitted between the systems is converted to a multiple-channel or single-channel system-dependent safe data structure (321, 322, 366) after being transmitted using the safe data structure which is defined but is system-independent.

4. The method of claim 1, wherein, in each case one data structure which is to be converted from one safe data structure to another safe data structure is evaluated (10, 20, 301, 302, 311, 312) on a safety basis, and a data protocol (20), which is in the form of one or more channels after evaluation, is converted (10, 20, 301, 302, 311, 312) to the corresponding other safe data structure.

5. The method of claim 1, wherein, the safety data which is processed additionally using a defined system-independent safe data structure (215) is transmitted within a unit, which is involved with a process to be controlled, of one of the systems to be coupled, to be precise between a safety-related device, which processes safety data that is relevant for this process, of the unit and at least one (field)bus/network connection of the unit.

6. The method of claim 1, further comprising, a set of input/output data, which is in the form of one or more channels, of the process to be controlled is converted to the safe data structure which is defined but is system-independent, or is obtained from the safe data structure which is defined but is system-independent by evaluation of that safe data structure which is defined but is system-independent.

7. The method of claim 1, wherein, the system-independent safe data structure is protected for single-channel transmission.

8. The method of claim 1, wherein, the data structure is protected using safety mechanisms in accordance with IEC 61508 and SIL 3.

9. The method of claim 1, wherein, the transmission is carried out using non-safe components (200, 201, 202).

10. An apparatus for coupling at least two (field)bus/network systems which each have different proprietary safety mechanisms, for conversion between safety data and a system-dependent safe data structure, comprising at least one first and one second safety-based data processing module (10) for processing safety data to be transmitted between the different system-based safety mechanisms using a defined system-independent safe data structure

11. The apparatus of claim 10, wherein, each of the data processing modules (10) is coupled to a system-based safety mechanism (30, 301, 302, 311, 312), in which case at least the at least one first data processing module is designed to convert safety data which is to be transmitted and is in the form of one or more channels to the defined system-independent safe data structure, and at least the at least one second data processing module is designed for safety-based evaluation of the system-independent safe data structure in order to produce safety data in the form of one or more channels.

12. The apparatus of claim 10 or 11, wherein, the data processing modules (10) are integrated in a unit, which is involved with a process to be controlled, of one of the systems to be coupled, with at least one of the at least two data processing modules being integrated in a safety-related device which processes safety data that is relevant for this process, and at least one other of the at least two data processing modules being integrated with a (field)bus/network connection in the unit.

13. The apparatus of claim 12, furthermore comprising at least one data processing module, which is integrated in the safety-related device, for conversion of a set, which is in the form of one or more channels, of safety data which comprises input/output data for the process to be controlled to the defined system-independent safe data structure, or for safety-based evaluation of the defined system-independent safe data structure, for single-channel or multiple-channel production of a set of safety data comprising input/output data.

14. The apparatus of claim 12, wherein, the unit is a modular unit.

15. The of claim 12, wherein, the unit is a bus subscriber unit or a bus control unit.

16. The apparatus of claim 12, wherein, the unit is in the form of a unit with a gateway functionality.

17. The apparatus of claim 10, wherein, the data processing modules (10) are designed to process a data structure which is protected on a system-independent basis for single-channel transmission between in each case at least two data processing modules.

18. The apparatus of claim 17, further comprising at least one non-safe coupling component (200, 201, 202) in the transmission path for the single-channel transmission between respective data processing modules.

19. The of claim 10, wherein, one data processing module comprises at least two redundant, interacting module units (10), with the module units being coupled on the output side to a non-safe coupling component (200, 201, 202) for transferring a data structure, which is jointly protected on a system-independent basis, to this coupling component, and/or are coupled on the input side with a non-safe coupling component (200, 201, 202) for safety-based reading of a data structure, which is protected on a system-independent basis, from this coupling component thereto.

20. The apparatus of claim 19, wherein a non-safe coupling component comprises at least one microprocessor, serial bus and/or coupling memory (200, 201, 202), in particular in the form of a DPM.

21. The apparatus of claim 10, wherein the data processing modules (10) comprise hardware and/or software.

22. A computer-readable medium with information stored in it which, when executed implement the steps of:

coupling at least two (field)bus/network systems each having different proprietary safety mechanisms, wherein safety data to be transmitted between the different system-based safety mechanisms is processed additionally using a defined system-independent safe data structure.