ICS Triplex T8311 Trusted TMR Expander Interface
|Catalog||Trusted TMR System|
|Description||ICS Triplex T8311 Trusted TMR Expander Interface|
|Origin||United States (US)|
Requirements for the Trusted TMR system
The Trusted TMR System requires at least a controller assembly and a power system, and possibly an expander system as well. The controller assembly has a T8100 Trusted Controller Chassis to house the essential modules: • One T8111 or T8110 Trusted TMR Processor.
• One T8311 Trusted Expander Interface modules to provide the interface between the controller chassis and the CS300 chassis. • One T8151B Trusted Communication Interface for the Ethernet interface to the engineering workstation and, if present, other Trusted systems or third-party equipment. (A T8151C conformal coated version can also be used). • One T8153 Trusted Communications Interface Adapter, to allow the physical connections to the T8151B Trusted Communication Interface. The T8100 Trusted Controller Chassis must be installed in a rack with doors and side panels, and the doors must be kept closed during usual operation. This lets the 8162 Bridge Module achieve compliance with its EMC specifications with no degradation in performance. The front door can have a window so that the LEDs are visible. The CS300 equipment must be inside the cabinet and earthed correctly (see Physical Installation Design on page 77). A complete list of all Trusted items needed for the migration is given in Table C2.
System architecture features The three 8162 CS300 Bridge Modules enable the connection between the Trusted TMR System and the legacy CS300 I/O, as shown in this figure:
The system communications must use approved cabling and accessories. In particular: • The Trusted TMR System carries a T8312 Expander Interface Adaptor and the CS300 rack carries a TC-324-02 PCB. • There is one TC-322-02 cable assembly. This carries the data between the two items of equipment using a triple, bidirectional communication link. • Cable assemblies are available up to 15 m long, and the system will support a cable up to 50 m long. The migrated system will support the pre-existing configuration of the CS300 I/O modules. Communications that existed from the legacy CS300 system to workstations, printers, and distributed control systems must be provided through the T8151 Communications Interface module
Method: Step 1 - If performing this test on a live system, it will be necessary to disconnect the final element associated with the channel under test, this is to help prevent a spurious action occurring due to the Proof test. If not, proceed to Step 2. Step 2 – Disconnect the switched output to final element, but with the 120V AC supply remaining connected and energized, verify that the output being tested reports a STATE value of 3 (No Load). Energize the output channel and verify that the channel STATE remains at STATE 3 (No Load), if the output, when energized reports either a STATE 4 (Output Energized) or a STATE 5 (Field Short Circuit) then the output channel likely has a failed varistor, so the FTA will need to be replaced. Step 4 – De-energize the output, then reconnect the final element field connection and verify that the output is reporting a STATE 2 (Output Deenergized). This test applies to the expansion modules (T8310, T8311, T8314), cabling, and fiber connections associated with the communication path between the Trusted Main Chassis and each Trusted or Triguard Expansion Chassis. The purpose of the test is to verify the integrity of the communications path between the Trusted Main Chassis and each Expansion Chassis in order to assert that the risk of dangerous residual error or spurious trip due to loss of communication remains at or below the published levels. The method described here is the recommended method to verify that the bit error rate associated with the communication path to each Expansion Chassis is below the level that could significantly impact the dangerous residual error rate or risk of spurious trip due to loss of communication. It is assumed that this methodology will be incorporated into a Proof Test procedure that includes other elements of Proof Testing and general proof test requirements as defined in IEC61511.