1756-RM001B-EN-P, Using ControlLogix in SIL2 ... - Tuv-fs.com

1756-RM001B-EN-P, Using ControlLogix in SIL2 ... - Tuv-fs.com 1756-RM001B-EN-P, Using ControlLogix in SIL2 ... - Tuv-fs.com

11.07.2015 Views

8-2 General Requirements for Application SoftwareSIL2 ProgrammingSafety Concept of the ControlLogix systemThe safety concept of SIL2 assumes, that:• the programming system (PS) hardware and firmware workscorrectly (that is, programming system errors can be detected).• the user applies the logic correctly, that is, user programmingerrors can be detected.For the initial start-up of a safety-related ControlLogix system, theentire system must be checked by a complete functional test. After amodification of the application program, the modified program orlogic must be checked.For more information on how users should handle changes to theirapplication program, see the Changing Your Application Programsection on page 9-6.General Guidelines forApplication SoftwareDevelopmentThe application software for the intended SIL2 systems is intended tobe developed by the system integrator and/or user. The developermust follow good design practices including the use of:• Functional specifications• Flow charts• Timing diagrams• Sequence charts• Program review• Program validationAll logic should be reviewed and tested. To facilitate reviews andreduce unintended responses, developers should limit the set ofinstructions to basic Boolean/ladder logic (such as examine On/Off,Timers, Counters, etc.) whenever possible. This set should includeinstructions that can be used to accommodate analog variables, suchas:• Limit tests• Comparisons• Math instructionsSee Appendix B, System Self-Testing andUser-Programmed Responses, for details.Publication 1756-RM001B-EN-P - October 2003

General Requirements for Application Software 8-3Users must verify the downloading of the application program and itsproper operation. A typical validation technique is to upload thedownloaded program file and perform a compare of that file againstwhat is stored in the programming terminal. The upload compare canbe accomplished after an interval by saving the first one andcomparing it to the second or subsequent uploads. This approachcould also be performed through different paths (that is, overControlNet and via the serial port).Safety logic and non safety-related logic should be separate.Check the Created Application ProgramTo check the created application program for adherence to thespecific function, you must generate a suitable set of test casescovering the specification. The set of test cases is filed as the testspecification.A suitable test set must also be generated for the numeric evaluationof formulas. Equivalent range tests are acceptable. These are testswithin the defined value ranges, at the limits, or in impermissiblevalue ranges. The test cases must be selected to prove the correctnessof the calculation. The necessary number of test cases depends on theformula used and must comprise critical value pairs.However, active simulation with sources cannot be omitted as this isthe only means of detecting correct wiring of the sensors andactuators to the system. Furthermore, this is the only means of testingthe system configuration. Users should verify the correct programmedfunctions by forcing I/O or by manual manipulation of sensors andactuators.Possibilities of Program IdentificationThe application program is clearly identified by one of the following:• Name• Date• Revision• Any other user identification informationPublication 1756-RM001B-EN-P - October 2003

8-2 General Requirements for Application Software<strong>SIL2</strong> Programm<strong>in</strong>gSafety Concept of the <strong>ControlLogix</strong> systemThe safety concept of <strong>SIL2</strong> assumes, that:• the programm<strong>in</strong>g system (PS) hardware and firmware workscorrectly (that is, programm<strong>in</strong>g system errors can be detected).• the user applies the logic correctly, that is, user programm<strong>in</strong>gerrors can be detected.For the <strong>in</strong>itial start-up of a safety-related <strong>ControlLogix</strong> system, theentire system must be checked by a <strong>com</strong>plete functional test. After amodification of the application program, the modified program orlogic must be checked.For more <strong>in</strong>formation on how users should handle changes to theirapplication program, see the Chang<strong>in</strong>g Your Application Programsection on page 9-6.General Guidel<strong>in</strong>es forApplication SoftwareDevelopmentThe application software for the <strong>in</strong>tended <strong>SIL2</strong> systems is <strong>in</strong>tended tobe developed by the system <strong>in</strong>tegrator and/or user. The developermust follow good design practices <strong>in</strong>clud<strong>in</strong>g the use of:• Functional specifications• Flow charts• Tim<strong>in</strong>g diagrams• Sequence charts• Program review• Program validationAll logic should be reviewed and tested. To facilitate reviews andreduce un<strong>in</strong>tended responses, developers should limit the set of<strong>in</strong>structions to basic Boolean/ladder logic (such as exam<strong>in</strong>e On/Off,Timers, Counters, etc.) whenever possible. This set should <strong>in</strong>clude<strong>in</strong>structions that can be used to ac<strong>com</strong>modate analog variables, suchas:• Limit tests• Comparisons• Math <strong>in</strong>structionsSee Appendix B, System Self-Test<strong>in</strong>g andUser-Programmed Responses, for details.Publication <strong>1756</strong>-<strong>RM001B</strong>-<strong>EN</strong>-P - October 2003

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!