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
6-8 ControlLogix I/O ModulesGeneral Considerations when using Any ControlLogix DigitalOutput ModuleWiring the two types of digital output modules differs, depending onyour application requirements (these wiring methods are explained indetail in later sections). However, regardless of the type ofControlLogix output module used, there are a number of generalapplication considerations that you must follow when applying thesemodules in a SIL2 application:• Proof Tests - Periodically (for example, once every severalyears) a System Validation test must be performed. Manually, orautomatically, test outputs to make sure that all outputs areoperational and not stuck in the ON or OFF state. Outputs mustbe cycled from ON to OFF or OFF to ON. For additionalinformation on Proof Tests, see page 1-5 and Figure 9.1 onpage 9-5.• Examination of Output Data Echo signal in Applicationlogic: The application logic must examine the Data Echo valueassociated with each output point to make sure that therequested On/Off command from the controller was received bythe module.In the rungs below, a timer begins to increment for anymiscompare between the actual output bit and its associatedData Echo bit. The timer must be preset to accommodate thedelay between setting the output bit in controller memory andreceipt of the Data Echo from the module. If a miscompareexists for longer than that time, a fault is reported.Figure 6.6Application LogicActuatorOutput BitData EchoTimerOutput BitData EchoTimer doneFaultFaultAlarm to OperatorPublication 1756-RM001B-EN-P - October 2003
ControlLogix I/O Modules 6-9The control, diagnostics and alarming functions must beperformed in sequence. For more information on faults, seeChapter 7, Faults in the ControlLogix System.• Use of external Relays to disconnect Module Power ifOutput De-energization is Critical: To make sure outputs willde-energize, users must wire an external relay that can removepower from the output module if a short or other fault isdetected. See Figure 6.7 on page 6-10 for an example method ofwiring an external relay.• Test outputs at specific times to make sure they areoperating properly. The method and frequency of testing isdetermined by the type of module–diagnostic or standard. Formore information on testing diagnostic module outputs, seepage 6-10. For more information on testing standard moduleoutputs, see page 6-11.• For typical emergency shutdown (ESD) applicationsoutputs must be configured to De-energize: Whenconfiguring any ControlLogix output module, each output mustbe configured to de-energize in the event of a fault and in theevent of the controller going into program mode. For exceptionsto the typical ESD applications, see Chapter 1, SIL Policy.• When wiring two digital output modules in series so that onemay break source voltage (as shown in Figure 6.10 onpage 6-12), make sure:– Both modules use identical configuration.– The same controller owns both modules.Publication 1756-RM001B-EN-P - October 2003
- Page 4 and 5: Summary of Changes 2Notes:Publicati
- Page 6 and 7: Preface 2Table Preface.1Section: Ti
- Page 8 and 9: Table of Contents 2ControlLogix Com
- Page 10 and 11: Table of Contents 4Additional Infor
- Page 12 and 13: 1-2 SIL PolicyThe TUV Rheinland has
- Page 14 and 15: 1-4 SIL PolicySIL2 CertificationFig
- Page 16 and 17: 1-6 SIL PolicySIL2-Certified Contro
- Page 18 and 19: 1-8 SIL PolicyHardware Designs andF
- Page 20 and 21: 1-10 SIL PolicyCatalogNumberDescrip
- Page 22 and 23: 1-12 SIL PolicyCatalogNumberDescrip
- Page 24 and 25: 1-14 SIL PolicySIL ComplianceDistri
- Page 26 and 27: 1-16 SIL PolicyProgram Watchdog Tim
- Page 28 and 29: 2-2 The ControlLogix SystemIf an an
- Page 30 and 31: 2-4 The ControlLogix SystemData Ech
- Page 32 and 33: 2-6 The ControlLogix SystemSoftware
- Page 34 and 35: 2-8 The ControlLogix SystemNotes:Pu
- Page 36 and 37: 3-2 ControlLogix System HardwareCon
- Page 38 and 39: 3-4 ControlLogix System HardwareRec
- Page 40 and 41: 3-6 ControlLogix System HardwareNot
- Page 42 and 43: 4-2 ControlLogix ControllerRecommen
- Page 44 and 45: 5-2 ControlLogix Communications Mod
- Page 46 and 47: 5-4 ControlLogix Communications Mod
- Page 48 and 49: 6-2 ControlLogix I/O ModulesFigure
- Page 50 and 51: 6-4 ControlLogix I/O ModulesModule
- Page 52 and 53: 6-6 ControlLogix I/O ModulesWiring
- Page 56 and 57: 6-10 ControlLogix I/O ModulesWiring
- Page 58 and 59: 6-12 ControlLogix I/O ModulesApplic
- Page 60 and 61: 6-14 ControlLogix I/O Modules• Ch
- Page 62 and 63: 6-16 ControlLogix I/O ModulesWiring
- Page 64 and 65: 6-18 ControlLogix I/O ModulesWiring
- Page 66 and 67: 6-20 ControlLogix I/O ModulesUsing
- Page 68 and 69: 6-22 ControlLogix I/O ModulesFigure
- Page 70 and 71: 6-24 ControlLogix I/O ModulesWiring
- Page 72 and 73: 6-26 ControlLogix I/O ModulesCheckl
- Page 74 and 75: 7-2 Faults in the ControlLogix Syst
- Page 76 and 77: 7-4 Faults in the ControlLogix Syst
- Page 78 and 79: 8-2 General Requirements for Applic
- Page 80 and 81: 8-4 General Requirements for Applic
- Page 82 and 83: 8-6 General Requirements for Applic
- Page 84 and 85: 9-2 Technical SIL2 Requirements for
- Page 86 and 87: 9-4 Technical SIL2 Requirements for
- Page 88 and 89: 9-6 Technical SIL2 Requirements for
- Page 90 and 91: 9-8 Technical SIL2 Requirements for
- Page 92 and 93: 10-2 Use and Application of Human t
- Page 94 and 95: 10-4 Use and Application of Human t
- Page 96 and 97: A-2 Response Times in ControlLogixE
- Page 98 and 99: A-4 Response Times in ControlLogixR
- Page 100 and 101: B-2 System Self-Testing and User-Pr
- Page 102 and 103: C-2 Additional Information on Handl
6-8 <strong>ControlLogix</strong> I/O ModulesGeneral Considerations when us<strong>in</strong>g Any <strong>ControlLogix</strong> DigitalOutput ModuleWir<strong>in</strong>g the two types of digital output modules differs, depend<strong>in</strong>g onyour application requirements (these wir<strong>in</strong>g methods are expla<strong>in</strong>ed <strong>in</strong>detail <strong>in</strong> later sections). However, regardless of the type of<strong>ControlLogix</strong> output module used, there are a number of generalapplication considerations that you must follow when apply<strong>in</strong>g thesemodules <strong>in</strong> a <strong>SIL2</strong> application:• Proof Tests - Periodically (for example, once every severalyears) a System Validation test must be performed. Manually, orautomatically, test outputs to make sure that all outputs areoperational and not stuck <strong>in</strong> the ON or OFF state. Outputs mustbe cycled from ON to OFF or OFF to ON. For additional<strong>in</strong>formation on Proof Tests, see page 1-5 and Figure 9.1 onpage 9-5.• Exam<strong>in</strong>ation of Output Data Echo signal <strong>in</strong> Applicationlogic: The application logic must exam<strong>in</strong>e the Data Echo valueassociated with each output po<strong>in</strong>t to make sure that therequested On/Off <strong>com</strong>mand from the controller was received bythe module.In the rungs below, a timer beg<strong>in</strong>s to <strong>in</strong>crement for anymis<strong>com</strong>pare between the actual output bit and its associatedData Echo bit. The timer must be preset to ac<strong>com</strong>modate thedelay between sett<strong>in</strong>g the output bit <strong>in</strong> controller memory andreceipt of the Data Echo from the module. If a mis<strong>com</strong>pareexists for longer than that time, a fault is reported.Figure 6.6Application LogicActuatorOutput BitData EchoTimerOutput BitData EchoTimer doneFaultFaultAlarm to OperatorPublication <strong>1756</strong>-<strong>RM001B</strong>-<strong>EN</strong>-P - October 2003