1747-6.22, Backup Scanner User Manual

More documents

Recommendations

Info

4-56 Operating Your SLC 500 Backup System Publication 1747-6.22 Primary Program Each data block that can be transferred from the primary to secondary SLC 5/0x is identified by its address in the M0/M1 files. The application program must transfer each block using the following procedure. A MOV instruction is used to get the Data Transfer Status Word (DTSW) and to see if the block can be transferred from the SLC 5/0x to the 1747-BSN (if the data block status bit is clear). When this bit is clear, the new data block must be copied to this corresponding M0 address. Then the data block control bit in the Data Transfer Control Word (DTCW) must be set to advise the 1747-BSN that this new data block is ready to transfer to the secondary system. This bit must be held set until the corresponding bit in the DTSW is set by the 1747-BSN. The bit must then be cleared. Secondary Program For each block that can be received by the secondary SLC 5/0x, its application program must do the following procedure. A MOV instruction is used to get the Data Transfer Status Word (DTSW) and to see if new data for the block is ready for reading in the secondary 1747-BSN module. When this bit is set, the new data block must be copied from the 1747-BSN M1 file. Then its corresponding bit in the Data Transfer Handshake Word (DTHW) must be set to advise the 1747-BSN that the data block was already received. This bit must be held set until the corresponding bit in DTSW is cleared by the 1747-BSN module. The bit must then be cleared. Backup System Theory of Operation A redundant system using the 1747-BSN can be initially defined as an “Asynchronized Data Transfer” system. While the Input Image Table is automatically acquired from the RIO link by the secondary system, the Data Table is transferred by an application program written by the user. It is recommended that you minimize the amount of data to be transferred from the primary to the secondary processor because the program logic generates the same outputs based on the same inputs. All timer and counter values must be transferred at least once because the primary and backup processors may have started at different times and are not synchronized. Therefore, timer and counter data may be different in the two processors. For example, after a faulted processor is repaired and reinstalled as a backup, the timer and counter accumulated values, as well as the control words, in the two processors are different. The number of data table words to be transferred from a primary to a secondary processor is dependent on the user program and/or user architecture.
Startup Sequencing Operating Your SLC 500 Backup System 4-57 When the system is powered up for the first time, the following sequence must be followed: 1. Disconnect both the primary and secondary SLC 5/0x from DH+ or DH485 2. Download programs containing the desired DH+ or DH485 node address to each processor. Leave both SLC 5/0x in program mode, and power down both systems. 3. Apply power to the system that is intended to be primary; 4. Apply power to the system that is intended to be secondary; 5. Change the primary SLC processor to Run mode; 6. Change the secondary SLC processor to Run mode. Power-up Sequencing To determine the primary and secondary systems, use the following powerup sequence: Processor Mode Change Sequencing 1. Apply power to the system that is intended to be primary; 2. After the primary SLC 5/0x has been powered-up and is operating correctly, apply power to the system that is intended to be secondary. If both systems are powered-up at the same time, they use a “talkand-listen algorithm” to determine which system is going to be primary and which is going to be secondary. The RIO and DH+ relays remain open until only one of the systems assumes primary status. This ensures that only one of the SLC 5/0x processors takes control over the RIO and DH+ links. The 1747-BSN does not control the operating mode of the SLC 5/0x in either the primary or the backup systems. If a processor mode change is required, it should be done primarily in the secondary system. After that, if required, the processor mode change should also be done in the primary processor. If the primary operating mode is changed from Run mode to Program mode, the secondary system takes control. ATTENTION: Use the processor mode change key to change the primary operating mode. Unexpected ! operation or system shutdown could occur if you use a programming terminal to change the primary operating mode from Remote Run to Remote Program. Publication 1747-6.22
Page 1 and 2:
Backup Scanner 1747-BSN User Manual
Page 3 and 4: Overview Table of Contents Preface
Page 5 and 6: Scanner Configuration and Programmi
Page 7 and 8: Switchover Considerations Programmi
Page 9 and 10: Glossary Index Table of Contents xi
Page 11 and 12: Who Should Use This Manual How to U
Page 13 and 14: Conventions Used in This Manual The
Page 15 and 16: Overview This chapter contains the
Page 17 and 18: Local I/O Remote I/O Processor I/O
Page 19 and 20: SLC and Scanner Asynchronous Operat
Page 21 and 22: RIO Logical Rack 0 RIO Logical Rack
Page 23 and 24: Physical and Logical RIO Link Speci
Page 25 and 26: Overview 1-27 Complementary I/O: Pl
Page 27 and 28: Overview 1-29 Complementary I/O: Pl
Page 29 and 30: Slot Pair I O I O I O I O 0 1 2 3 4
Page 31 and 32: Hardware Features Overview 1-33 Not
Page 33 and 34: Module Address Switch Overview 1-35
Page 35 and 36: A Typical SLC 500 Backup Configurat
Page 37 and 38: Overview 1-39 Data table values are
Page 39 and 40: Required Tools and Equipment Chapte
Page 41 and 42: 5. Configure the system. Quick Star
Page 43 and 44: Configuration Selection Installatio
Page 45 and 46: Backup Scanner Installation Install
Page 47 and 48: Installation and Wiring 3-49 Termin
Page 49 and 50: Chapter 4 Operating Your SLC 500 Ba
Page 51 and 52: (1) Operating Your SLC 500 Backup S
Page 53: Operating Your SLC 500 Backup Syste
Page 57 and 58: Understanding Remote Input and Outp
Page 61 and 62: Rules for Configuring the Scanner G
Page 63 and 64: Logical Rack 0 Logical Rack 1 Logic
Page 65 and 66: Considerations When Configuring Rem
Page 69 and 70: Output Reset Control Device Inhibit
Page 71 and 72: M0 File - RIO Device Reset Control
Page 75 and 76: M1 Status File Description General
Page 77 and 78: Logical Device Starting Address Sta
Page 79 and 80: Logical Device Fault Status M1 (Sta
Page 83 and 84: Primary Logical Device Address, Wor
Page 85 and 86: SLC/Scanner Configuration Scanner C
Page 87 and 88: Chapter 6 Module Control and Status
Page 89 and 90: Module Control and Status Word 6-91
Page 91 and 92: Transferring Data over the High-Spe
Page 93 and 94: Data Transfer Status Word Module Co
Page 95 and 96: Program File 2 0000 0001 0002 Modul
Page 97 and 98: Program File 4 0000 0001 0002 0003
Page 99 and 100: Module Status Counters Module Contr
Page 101 and 102: RIO Block Transfer Theory of Operat
Page 103 and 104: SLC Processor ➀ RIO Block Transfe
Page 105 and 106:
RIO Block Transfer General Function
Page 107 and 108:
Example 2 # 2 # 4 # 1 # 2 # 3 # 4 #
Page 109 and 110:
M0 File BT Control Buffer Layout BT
Page 111 and 112:
Error Code Description RIO Block Tr
Page 113 and 114:
RIO Block Transfer 7-115 Your SLC c
Page 115 and 116:
Control EN TO Status Flag EW ST ER
Page 117 and 118:
Control Flag EN TO Status Flag EW S
Page 119 and 120:
Bit Number Octal 17 10 7 Bit Number
Page 121 and 122:
Block Transfer Read Control Logic E
Page 123 and 124:
RIO Block Transfer 7-125 Rung 2:3 W
Page 125 and 126:
RIO Block Transfer 7-127 Rung 2:1 C
Page 127 and 128:
Directional Continuous Block Transf
Page 129 and 130:
Page 131 and 132:
Directional Repeating Block Transfe
Page 133 and 134:
Rung 2:5 Block transfer reads will
Page 135 and 136:
Page 137 and 138:
Bidirectional Continuous Block Tran
Page 139 and 140:
RIO Block Transfer 7-141 When a BTR
Page 141 and 142:
RIO Block Transfer 7-143 Rung 2:9 T
Page 143 and 144:
RIO Block Transfer 7-145 Rung 2:1 C
Page 145 and 146:
Page 147 and 148:
RIO Block Transfer 7-149 Rung 2:10
Page 149 and 150:
RIO Block Transfer 7-151 Rung 2:2 U
Page 151 and 152:
Page 153 and 154:
RIO Block Transfer 7-155 Rung 2:11
Page 155 and 156:
Switchover Considerations Chapter 8
Page 157 and 158:
Switchover Considerations 8-159 Div
Page 159 and 160:
Switchover Considerations 8-161 Dur
Page 161 and 162:
Switchover Considerations 8-163 The
Page 163 and 164:
Programming Techniques Chapter 9 Ch
Page 165 and 166:
Program File 3 0000 0001 0002 0003
Page 167 and 168:
0009 0010 0011 0012 Programming Tec
Page 169 and 170:
0017 Programming Techniques 9-171 T
Page 171 and 172:
0005 0006 0007 0008 0009 0010 0011
Page 173 and 174:
0021 0022 0023 0024 0025 0026 0027
Page 175 and 176:
Programming Techniques 9-177 Data T
Page 177 and 178:
Programming Techniques 9-179 3. For
Page 179 and 180:
Programming Techniques 9-181 The ha
Page 181 and 182:
Programming Techniques 9-183 Howeve
Page 183 and 184:
Backup Scanner Operating Specificat
Page 185 and 186:
Calculating Throughput Specificatio
Page 187 and 188:
Specifications A-189 You need to ca
Page 189 and 190:
Determining T btx All Baud Rates 57
Page 191 and 192:
Specifications A-193 3. Calculate t
Page 193 and 194:
Backup Scanner Output Delay Time (T
Page 195 and 196:
M0-M1 Files and G Files Appendix B
Page 197 and 198:
Monitoring Bit Addresses M0-M1 File
Page 199 and 200:
Access Time M0-M1 Files and G Files
Page 201 and 202:
S:4/8 causes the #M1:4.3 file to up
Page 203 and 204:
M0-M1 Files and G Files B-205 G Fil
Page 205 and 206:
M0-M1 Files and G Files B-207 With
Page 207 and 208:
RIO Configuration Worksheet Appendi
Page 209 and 210:
Glossary The following terms are us
Page 211 and 212:
Glossary 213 Module Status Word (MS
Page 213 and 214:
Numerics 1/2-slot addressing, 1-13,
Page 215 and 216:
minimizing the scan time, B-6 speci
Page 217 and 218:
Index I-ccxix Publication 1747-6.22
Page 219:
Publication 1747-6.22 — October 1
show all

1747-6.22, Backup Scanner User Manual

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

Delete template?

Save as template?