Error management: requirements needed

[JakobGartner]

We have developed a first concept for error and warnings management in the EVC.

The concept relies on several components:

• An error bus that collects the errors/ warnings from Operators that wish to transmit error messages
• An error status database in the central data storage
• A log function that outputs the error/warning flow to the outside world

LEA Railergy will contribute at own expense an additional resource for maintaining the related library and most importantly, to issue error codes to all "customers" (=SCADE Operators) and maintaining the related matrix

Before starting implementation, I would like to collect your input on requirements.

At the moment the error table would contain the following information:

Error_ID (unique identifier, centrally managed) Criticality (Safety_Critical, Error, Warning, Information) Operator (informational, the "customer" is responsible for using the code in the correct way) Persistence (how long to be stored in database) Scope (who may listen)

Please let us know if you have any detailed suggestions or requirements or if you can point us to a standard set of error classes which is EVC- relevant.

[ghost]

I take over this issue . A first draft library will be provided next week. We will also provide a central error code database which will be maintained by our new intern.