Error condition processing in an automation system

• US 20030061007A1
• Filed: 10/08/2001
• Published: 03/27/2003
• Est. Priority Date: 09/07/2001
• Status: Abandoned Application

• Current Assignee: Siemens AG
• Original Assignee: Siemens AG
• Inventors: Sigl, Klaus
• Application Number:
  US09/972,679
• Publication Number:
  US 20030061007A1
• Time in Patent Office: Days
• US Class Current: 702/185
• CPC Class Codes: G05B 19/4184 characterised by fault tolerance, reliability of production system
• CPC Class Codes: G05B 2219/24053 Diagnostic of controlled machine
• CPC Class Codes: G05B 2219/24056 Portable, detachable module to input test signals, read test results
• CPC Class Codes: Y02P 90/02 Total factory control, e.g. smart factories, flexible manufacturing systems [FMS] or integrated manufacturing systems [IMS]

Abstract

A method and system for analyzing fault conditions in an automation system. An error controller (10) connects to one or more machines or machine elements (12) in an automation system. Signals from the machine (12) are input to one or more inputs (14) of the error controller (10). Internal logic to the error controller (10) uses the inputs to identify possible error conditions, which are then transmitted to a central controller (16) via error controller outputs (18) of the error controller (10). A display monitor (20) provides a user interface for error analysis and configuration of the error controller (10). A PC (22) is provided for configuration of the error controller (10) by running suitable application software for the configuration thereof. When an error condition arises, corresponding error messages are extracted from a database and presented to a user via the display (20).

Claims

1. A method of monitoring an automation system, comprising

identifying functional blocks making up the system;

identifying potential error conditions associated with each of said functional blocks;

defining possible causes for each of said potential error conditions wherein a plurality of possible causes is defined for at least one of said error conditions; and

developing corresponding error messages for the possible causes.

2. The method of claim 1, wherein said possible causes are defined in the step of defining based upon external conditions that impact a functional block.

3. The method of claim 2, wherein said possible causes are defined in the step of defining by reviewing plant documentation associated with said functional blocks.

4. The method of claim 2, wherein each of a plurality of possible causes for an error condition is associated with a weighting factor defining the likelihood of an error condition having been caused by said possible cause.

5. The method of claim 1, wherein said error messages are associated with said potential error conditions that are stored in a database.