11.07.2015 Views

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

SHOW MORE
SHOW LESS
  • No tags were found...

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

6-26 <strong>ControlLogix</strong> I/O ModulesChecklist for SIL OutputsThe follow<strong>in</strong>g checklist is required for plann<strong>in</strong>g, programm<strong>in</strong>g andstart up of SIL outputs. It may be used as a plann<strong>in</strong>g guide as well asdur<strong>in</strong>g proof test<strong>in</strong>g. If used as a plann<strong>in</strong>g guide, the checklist can besaved as a record of the plan.For programm<strong>in</strong>g or start-up, an <strong>in</strong>dividual requirement checklist mustbe filled <strong>in</strong> for every s<strong>in</strong>gle SIL output channel <strong>in</strong> a system. This is theonly way to make sure that the requirements are fully and clearlyimplemented. This checklist can also be used as documentation onthe connection of external wir<strong>in</strong>g to the application program.Output Check List for <strong>ControlLogix</strong> SystemCompany:Site:Loop def<strong>in</strong>ition:SIL output channels <strong>in</strong> the:No. All Output Module Requirements (apply to both digital and analog output modules) Yes No Comment:1 Have you performed proof tests on the modules?2 Is Exact Match selected as the electronic key<strong>in</strong>g option for all modules?3 Is the RPI value set to an appropriate value for your application?4 Have you set up fault rout<strong>in</strong>es, <strong>in</strong>clud<strong>in</strong>g <strong>com</strong>par<strong>in</strong>g output data with a correspond<strong>in</strong>g <strong>in</strong>put po<strong>in</strong>t?5 If required, have you used external relays <strong>in</strong> your application to disconnect module power if ashort or other fault is detected on the module or isolated output <strong>in</strong> series?6 Is the control of the external relay implemented <strong>in</strong> ladder logic?7 Have you exam<strong>in</strong>ed the Output Data Echo signal <strong>in</strong> application logic?8 Are all outputs configured to deenergize <strong>in</strong> the event of a fault or the controller enter<strong>in</strong>g program mode?9 Do two modules of the same type, used <strong>in</strong> the same application, use identical configurations?10 Does one controller own both modules if two of the same type are used <strong>in</strong> an application?11 Are control, diagnostics and alarm<strong>in</strong>g functions performed <strong>in</strong> sequence <strong>in</strong> application logic?No. Digital Output Module-Only Requirements Yes No Comment1 For the standard output modules, is the Communication Format set to Output Data?2 For standard output modules, have you wired the outputs to a correspond<strong>in</strong>g <strong>in</strong>put to validatethat the output is follow<strong>in</strong>g its <strong>com</strong>manded state?3 For the diagnostic output modules, are all diagnostics enabled on the module?4 For the diagnostic output modules, are enabled diagnostic bits monitored by fault rout<strong>in</strong>es?5 For the diagnostic output modules, is the Communication Format set to FullDiagnostics-Output Data?6 For diagnostic output modules, have you periodically performed a Pulse Test to make surethat the output is capable of change state?7 For diagnostic output modules, is the connection to remote modules a direct connection?No. Analog Output Module-Only Requirements Yes No Comment1 Is the Communication Format set to Float Data?2 Have you calibrated the modules as often as required by your application?3 When wir<strong>in</strong>g the <strong>1756</strong>-OF8 <strong>in</strong> current mode, are loop devices placed properly?4 Have you written application logic to exam<strong>in</strong>e bits for any condition that may cause a faultand appropriate fault rout<strong>in</strong>es to handle the fault condition?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!