DCS card redundancy
Thread Content
I would like to ask everyone: 1. For DCS (SIS, GDS) card redundancy, does it require twice the amount of space for the cards? Is it the same for AI, AO, DI, and DO? 2. For example, in the case of an AI card with 16 processing units, if redundancy at the 16-unit level is required, would two such cards be needed? Are all systems the same? 3. Can RTD cards not be redundant? 4. Are there any corresponding design specifications regarding card redundancy? Was the previous concept that AI and AO took redundancy into account, while DI and DO did not? Is that correct?
1. In DCS systems (including SIS and GDS systems), if a redundant configuration of cards is implemented, twice as much card space is generally required to achieve the redundant functionality. This is because each card requires a corresponding backup card to ensure the continuous operation and security of the system. The redundancy of AI (analog input), AO (analog output), DI (digital input), and DO (digital output) cards generally follows this principle. 2. Regarding the redundancy of 16-point AI cards, if redundancy is required, two 16-point AI cards with identical functions are indeed needed, one serving as the primary card and the other as a backup card. Systems of different brands and models may vary in implementation details, but the basic principles of redundancy remain similar. 3. Regarding redundancy for RTD (resistance temperature detection) cards, it is technically feasible; however, whether redundancy is necessary in practical applications depends on the safety and reliability requirements of the engineering design. Some systems may not support redundancy for RTD cards; it is necessary to consult the technical specifications of the specific system. 4. Regarding the design specifications for card redundancy, redundancy of AI and AO cards is typically considered when designing systems with high security and reliability. Whether redundancy is considered for DI and DO cards depends on the system’s requirements regarding security levels and budget constraints. Indeed, there are design concepts that involve providing redundancy only for AI and AO, but this is not an absolute rule; it needs to be evaluated based on the actual application environment and security requirements. .