Академический Документы
Профессиональный Документы
Культура Документы
Features
• TMR fault tolerant (3-3-2-0) operation
• Dedicated hardware and software test regimes which provide very fast fault recognition and
response times
• Automatic fault handling without nuisance alarming
• Hot replacement, self-configuration.
• Interfaces to Trusted TMR Expander Bus
• Front panel indicators that show module health data transmission status
• Certified to SIL 3 IEC 61508 Edition 1
PREFACE
In no event will Rockwell Automation be responsible or liable for indirect or consequential damages
resulting from the use or application of this equipment. The examples given in this manual are
included solely for illustrative purposes. Because of the many variables and requirements related to
any particular installation, Rockwell Automation does not assume responsibility or reliability for
actual use based on the examples and diagrams.
No patent liability is assumed by Rockwell Automation, with respect to use of information, circuits,
equipment, or software described in this manual.
All trademarks are acknowledged.
DISCLAIMER
It is not intended that the information in this publication covers every possible detail about the
construction, operation, or maintenance of a control system installation. You should also refer to
your own local (or supplied) system safety manual, installation and operator/maintenance manuals.
This document is based on information available at the time of its publication. The document
contents are subject to change from time to time. The latest versions of the manuals are available at
the Rockwell Automation Literature Library under "Product Information" information "Critical
Process Control & Safety Systems".
TRUSTED RELEASE
For the latest information about this product review the Product Notifications and Technical Notes
issued by technical support. Product Notifications and product support are available at the Rockwell
Automation Support Center at
http://rockwellautomation.custhelp.com
At the Search Knowledgebase tab select the option "By Product" then scroll down and select the
Trusted product.
Some of the Answer ID’s in the Knowledge Base require a TechConnect Support Contract. For more
information about TechConnect Support Contract Access Level and Features please click on the
following link:
https://rockwellautomation.custhelp.com/app/answers/detail/a_id/50871
This will get you to the login page where you must enter your login details.
IMPORTANT A login is required to access the link. If you do not have an account then you can create one
using the "Sign Up" link at the top right of the web page.
DOCUMENTATION FEEDBACK
Your comments help us to write better user documentation. If you discover an error, or have a
suggestion on how to make this publication better, send your comment to our technical support
group at http://rockwellautomation.custhelp.com
SCOPE
This manual specifies the maintenance requirements and describes the procedures to assist
troubleshooting and maintenance of a Trusted system.
This manual is for plant maintenance personnel who are experienced in the operation and
maintenance of electronic equipment and are trained to work with safety systems.
SYMBOLS
In this manual we will use these notices to tell you about safety considerations.
This symbol identifies items which must be thought about and put in place when
designing and assembling a Trusted controller for use in a Safety Instrumented
Function (SIF). It appears extensively in the Trusted Safety Manual.
IMPORTANT Identifies information that is critical for successful application and understanding of
the product.
TIP Tips give helpful information about using or setting up the equipment.
Do not connect or disconnect equipment while the circuit is live or unless the area is
known to be free of ignitable concentrations or equivalent
Ne pas connecter ou déconnecter l’équipement alors qu’il est sous tension, sauf si
l’environnement est exempt de concentrations inflammables ou équivalente
MAINTENANCE
Maintenance must be carried out only by qualified personnel. Failure to follow these
instructions may result in personal injury.
CAUTION:
The module PCBs contains static sensitive components. Static handling precautions
must be observed. DO NOT touch exposed connector pins or attempt to dismantle a
module.
ISSUE RECORD
Table of Contents
1. Description ............................................................................................................ 3
2. Installation ............................................................................................................ 5
3. Application ............................................................................................................ 9
4. Operation ............................................................................................................ 41
6. Specifications....................................................................................................... 45
1. Description
1.1. Overview
The SC300E Bridge enables connection between a Triguard SC300E I/O sub system and the Trusted
TMR Processor. Three SC300E Bridge modules replace the three MPP modules in a Triguard primary
chassis.
The Bridge module has a fast serial ("Hotlink") interface that transfers command and response
packets between the two product families via the Trusted Expander Bus. The module uses a Field
Programmable Gate Array (FPGA) for decoding instructions from the Trusted TMR processor,
accessing the specified Triguard I/O module and returning any data requested.
Command data received by the three Bridge modules and responses to the Trusted TMR Processor
are synchronized in accordance with the Lock Step operational characteristics of the Trusted
Expander Bus. For this reason, the three bridge modules share their data and arrange their response
packets in the same order for simultaneous transmission. The clock signal received from the
Expander Bus is used to ensure that data from all three Bridge modules is transmitted on the same
clock edge.
The Trusted TMR processor stores and executes the application program, scans and updates the
Triguard I/O modules and detects system faults. Each of the three slices of the TMR Processor
executes the application program independently, but in lock-step synchronization with the other
two.
All Triguard I/O modules are supported. Triguard Serial Communication modules are not supported.
All communications to workstations and Distributed Control System (DCS) are enabled through the
Trusted Communications Interfaces.
Expansion Bus (TC-322-02 Cable) Inter Module
(TC-325-02 Board) Link
(C) Bridge Module (C)
FCR A
Trusted™
Expander hotlink
Interface receiver FPGA
Module
hotlink
transmitter
Trusted™ to Triguard
Triguard
I/O Modules
Main Chassis Main Chassis
Figure 1 Block Diagram showing interface between Trusted system and Triguard I/O
1.4. Function
When an I/O access is to be performed, the Trusted TMR Processor issues a command packet to an
Expander Interface module. The Expander Interface decodes the chassis address and transmits the
packet through the Expander bus to receivers in the 8161 Bridge modules.
For short distances of a few metres, a twisted-pair copper cable is used, whilst on longer runs the
copper cable is connected to three T8312 fibre optic units at each end of three pairs (Tx and Rx) of
fibre optic cable. The Bridge modules, receiving the command signals, decode the packet.
The Bridge modules then implement the read or write access on the SC300E I/O module selected
and return a response packet via the Expander Bus. The packet will contain both data and diagnostic
information.
2. Installation
2.1. Module
Each of the three Bridge modules replaces one of the Triguard Massively Parallel Processors (MPP).
Figure 2 shows the module. The replacement must be carried out with the system offline.
The modules consist of a single Printed Circuit Board (PCB) assembly.
Figure 4 shows the interface cable connector card (top left) fitted to three unused connectors on the
rear of the Triguard controller chassis which is connected to the Trusted Expander Interface adapter
via the TC-322-02 interface cable (braided cable on left).
Connectors J1-3 on the TC-325-02 card plug into the three 26-way headers on the Triguard
backplane. The expander cable, TC-322-02, from the Trusted Expander Interface plugs into 12-way
socket J4.
Note that the chassis Unit ID jumpers will need setting before fitting the interface cable connector
card (see Section 2.3).
Figure 5 shows a four socket version of the T8312 Expander Interface Adapter with a TC-301-01
cable attached, which connects to a Trusted expander chassis. The Expander Interface Adapter has
four or seven connections available to individual Trusted Expander chassis or to the Triguard
controller chassis using the TC-322-02 Interface Cable Assembly.
Unit ID jumpers 0,1,2,3 represent the binary address bits 1, 2, 4 & 8 respectively. A removed jumper
signals a binary digit ‘1’. The address is set to between 2 and 8. On the first Triguard chassis
(containing the SC300E Bridge Modules), remove jumper 1 to represent Trusted address '2' (as
shown in the picture). The jumpers on all three sets must be set to the same address. Leave the
jumpers as they were on the other Triguard chassis. It is usual to attach the chassis with address 2 to
the first Expander Interface Adapter socket, for both Trusted chassis and Triguard chassis. This
makes the software configuration easier.
3. Application
All Triguard I/O modules are configured using the IEC 61131 application Toolset provided with
Trusted. This configuration requires entries in the System Configuration (System.INI) for the chassis
and modules and their hardware operational parameters, and also in the workbench I/O connection
table, for software settings and data connection.
The Triguard chassis are attached to the Expander Interface as if they were Trusted expander
chassis, but the various chassis options for Triguard and CS300 are provided on the ‘Insert New
Chassis’ dialog. Right-click on the grey background of the configurator window to insert a new
chassis.
The first chassis to be created is an 8161. This includes the bridge modules in place of the Triguard
processors. Choose type Triguard 8161 and select a logical chassis number. This chassis number will
define the switch configuration described in section 2.3.
The chassis should then be allocated to the Trusted Expander Interface module. Left-click on the left
or right end of the Triguard 8161 chassis to open the Chassis Connection dialog. Select the slot
number of the left-hand Expander Interface module.
On closing this dialog, the Triguard 8161 chassis should have a blue flash symbol on the left. The
right hand side shows the chassis address as:
< Trusted expander Interface slot> - <Expander socket number> - <Triguard chassis number>
Left-click on the left or right end of the 8161 chassis to open the Chassis Connection dialog again.
The ‘Jumper Config’ button now demonstrates how to set the Triguard backplane jumpers.
This chassis then links into the extension chassis MBB and MRB04XM. MBB is a local extension
chassis linked to the main chassis by ribbon cables. MRB04XM is also a local chassis but it provides
remote connection via fiber optic cables to slave chassis MRB04XS.
To add an MBB or MRB04XM chassis, right click again on the background and select the chassis type.
The jumper settings on these chassis should not be changed from their old configuration in the
Triguard system. Select the 8161 chassis to which the new chassis should be connected (Parent 8161
Chassis Number; the list will only show the chassis that exist already), and enter the chassis number
as configured on the address jumpers on the chassis (Triguard Chassis Number). Closing this window
and left-clicking on the chassis ends will show the Jumper Config button, which will confirm the
switch settings that have been selected. For the MRB04XM chassis, the two DIP switch settings are
also displayed.
The chassis will now show its address on the right end as:
< Trusted expander Interface slot> - <Expander socket number> - <Triguard chassis number>
For output modules, select the output action on failure (Fallback Mode); either to set all outputs to
zero/de-energized or to remain at their last state.
For all modules, select the action on slice failure, either to shut down when only one slice is working
(3-2-0) or to continue running on one slice (3-2-1).
To enable hot-repair (on-line replacement), check ‘Hot Repair Partner’. This will enable replacement
with the module in the slot to the right of this module. There is no need to check the box in the
right-hand module.
To allow the system to run with a module absent, check ‘Simulate’.
Ensure that the options selected are as configured in the original application.
This definition provides module status for a Logical Triguard 8161 primary chassis expansion
interface module.
The logical module accounts for the 3 physical modules FCR-A, FCR-B and FCR-C.
OEM PARAMETERS
PHYSICAL MODULE
This definition provides module status for a logical Triguard MBB local chassis expansion module.
The logical module accounts for the 3 physical modules FCR-A, FCR-B and FCR-C.
OEM PARAMETERS:
PHYSICAL MODULE:
Note:
The status of MBB FCR's can only be determined by the discrepancy status of accesses performed to I/O
modules within the chassis of the MBB. If no such modules exist or if no MBB FCR’s are fitted then no faults
can be reported.
OEM PARAMETERS
SLOT 1-10
PHYSICAL MODULE:
RACK 1: (AI)
32 INTEGER inputs
RACK 2: (DIAG)
3 INTEGER inputs
Word 1 Health status bits, 0=healthy 1=fault
bit 0-2 Microcontroller watchdog (bit 0=A, bit 1=B, bit2=C)
bit 3-5 MP watchdog (bit 0=A, bit 1=B, bit2=C)
bit 6-8 Microcontroller slice health (bit 0=A, bit 1=B, bit2=C)
bit 9-11 Combined slice health (bit 0=A, bit 1=B, bit2=C)
bit 12 Power Fail
bit 13-15 not used
Word 2 Diagnostic bits
bit 0 Slice A
=1 slice is not responding or there is an error
=0 slice is responding
bit 1 Slice B
=1 slice is not responding or there is an error
=0 slice is responding
bit 2 Slice C
=1 slice is not responding or there is an error
=0 slice is responding
bit 3 Module offline or missing
=1 offline or missing
=0 online
bit 4 Single slot hot repair
=1 in progress
=0 not in progress
bit 5 Discrepancy errors
=1 faults detected
=0 no faults detected
OEM PARAMETERS
PHYSICAL MODULE:
RACK 1: (AI)
32 INTEGER inputs
RACK 2: (DIAG)
3 INTEGER inputs
Word 1 Health status bits, 0=healthy 1=fault
bit 0-2 Microcontroller watchdog (bit 0=A, bit 1=B, bit2=C)
bit 3-5 MP watchdog (bit 0=A, bit 1=B, bit2=C)
bit 6-8 Microcontroller slice health (bit 0=A, bit 1=B, bit2=C)
bit 9-11 Combined slice health (bit 0=A, bit 1=B, bit2=C)
bit 12 Power Fail
bit 13-15 not used
Word 2 Diagnostic bits
bit 0 Slice A
OEM PARAMETERS
PHYSICAL MODULE:
RACK 1: (AI)
32 INTEGER inputs
RACK 2: (DIAG)
3 INTEGER inputs
Word 1 Health status bits, 0=healthy 1=fault
bit 0-2 Microcontroller watchdog (bit 0=A, bit 1=B, bit2=C)
bit 3-5 MP watchdog (bit 0=A, bit 1=B, bit2=C)
bit 6-8 Microcontroller slice health (bit 0=A, bit 1=B, bit2=C)
bit 9-11 Combined slice health (bit 0=A, bit 1=B, bit2=C)
bit 12 Power Fail
bit 13-15 not used
Word 2 Diagnostic bits
bit 0 Slice A
=1 slice is not responding or there is an error
=0 slice is responding
bit 1 Slice B
=1 slice is not responding or there is an error
=0 slice is responding
bit 2 Slice C
=1 slice is not responding or there is an error
=0 slice is responding
bit 3 Module offline or missing
=1 offline or missing
=0 online
bit 4 Single slot hot repair
=1 in progress
=0 not in progress
bit 5 Discrepancy errors
=1 faults detected
=0 no faults detected
bit 6 LFD faults
=1 faults detected
=0 no faults detected
Word 3 Slot number of active module
RACK 3: (FAULTS)
4 INTEGER inputs
Word 1 Discrepancy errors, channels 1-16 (bit 0 = channel 1)
Word 2 Discrepancy errors, channels 17-32 (bit 0 = channel 17)
Word 3 LFD errors, channels 1-16 (bit 0 = channel 1)
Word 4 LFD errors, channels 17-32 (bit 0 = channel 17)
OEM PARAMETERS
PHYSICAL MODULE:
RACK 1: (AI)
32 INTEGER inputs
RACK 2: (DIAG)
3 INTEGER inputs
Word 1 Health status bits, 0=healthy 1=fault
bit 0-2 Microcontroller watchdog (bit 0=A, bit 1=B, bit2=C)
bit 3-5 MP watchdog (bit 0=A, bit 1=B, bit2=C)
bit 6-8 Microcontroller slice health (bit 0=A, bit 1=B, bit2=C)
bit 9-11 Combined slice health (bit 0=A, bit 1=B, bit2=C)
OEM PARAMETERS
PHYSICAL MODULE:
RACK 1: (AO)
4 INTEGER outputs
RACK 2: (DIAG)
4 INTEGER inputs
Word 1 Health status bits, 0=healthy 1=fault
bit 0-2 Microcontroller watchdog (bit 0=A, bit 1=B, bit2=C)
bit 3-5 MP watchdog (bit 0=A, bit 1=B, bit2=C)
bit 6-8 Microcontroller slice health (bit 0=A, bit 1=B, bit2=C)
bit 9-11 Combined slice health (bit 0=A, bit 1=B, bit2=C)
bit 12 Power Fail
bit 13-15 not used
Word 2 Diagnostic bits
bit 0 Slice A
=1 slice is not responding or there is an error
=0 slice is responding
bit 1 Slice B
=1 slice is not responding or there is an error
=0 slice is responding
bit 2 Slice C
=1 slice is not responding or there is an error
=0 slice is responding
bit 3 Module offline or missing
=1 offline or missing
=0 online
bit 4 Single slot hot repair
=1 in progress
=0 not in progress
bit 5 Discrepancy errors
=1 faults detected
=0 no faults detected
bit 6 LFD faults
=1 faults detected
=0 no faults detected
Word 3 Slot number of active module
Word 4 Fault flags, 0=healthy 1=fault
bit 0-2 Logic supply power fail fault (ABC, bit0=A, bit2=C)
bit 3-5 Reserved
bit 6 Field power fail fault
bit 7 Output discrepancy error
bit 8-15 Reserved
RACK 3: (FAULTS)
1 INTEGER input
Word 1 LFD errors, channels 1-4 (bit 0 = channel 1)
OEM PARAMETERS
PHYSICAL MODULE:
RACK 1: (DI)
32 BOOLEAN inputs
RACK 2: (DIAG)
3 INTEGER inputs
Word 1 Health status bits, 0=healthy 1=fault
bit 0-2 Microcontroller watchdog (bit 0=A, bit 1=B, bit2=C)
bit 3-5 MP watchdog (bit 0=A, bit 1=B, bit2=C)
bit 6-8 Microcontroller slice health (bit 0=A, bit 1=B, bit2=C)
bit 9-11 Combined slice health (bit 0=A, bit 1=B, bit2=C)
bit 12 Power Fail
bit 13-15 not used
Word 2 Diagnostic bits
bit 0 Slice A
=1 slice is not responding or there is an error
=0 slice is responding
bit 1 Slice B
=1 slice is not responding or there is an error
=0 slice is responding
bit 2 Slice C
=1 slice is not responding or there is an error
=0 slice is responding
bit 3 Module offline or missing
=1 offline or missing
=0 online
bit 4 Single slot hot repair
=1 in progress
=0 not in progress
bit 5 Discrepancy errors
=1 faults detected
=0 no faults detected
bit 6 LFD faults
=1 faults detected
=0 no faults detected
Word 3 Slot number of active module
RACK 3: (FAULTS)
4 INTEGER inputs
Word 1 Discrepancy errors, channels 1-16 (bit 0 = channel 1)
Word 2 Discrepancy errors, channels 17-32 (bit 0 = channel 17)
Word 3 LFD errors, channels 1-16 (bit 0 = channel 1)
Word 4 LFD errors, channels 17-32 (bit 0 = channel 17)
OEM PARAMETERS
PHYSICAL MODULE:
RACK 1: (DI)
32 BOOLEAN inputs
RACK 2: (DIAG)
3 INTEGER inputs
Word 1 Health status bits, 0=healthy 1=fault
bit 0-2 Microcontroller watchdog (bit 0=A, bit 1=B, bit2=C)
bit 3-5 MP watchdog (bit 0=A, bit 1=B, bit2=C)
bit 6-8 Microcontroller slice health (bit 0=A, bit 1=B, bit2=C)
bit 9-11 Combined slice health (bit 0=A, bit 1=B, bit2=C)
bit 12 Power Fail
bit 13-15 not used
Word 2 Diagnostic bits
bit 0 Slice A
=1 slice is not responding or there is an error
=0 slice is responding
bit 1 Slice B
=1 slice is not responding or there is an error
=0 slice is responding
bit 2 Slice C
=1 slice is not responding or there is an error
=0 slice is responding
bit 3 Module offline or missing
=1 offline or missing
=0 online
bit 4 Single slot hot repair
=1 in progress
=0 not in progress
bit 5 Discrepancy errors
=1 faults detected
=0 no faults detected
bit 6 LFD faults
=1 faults detected
=0 no faults detected
Word 3 Slot number of active module
RACK 3: (FAULTS)
4 INTEGER inputs
Word 1 Discrepancy errors, channels 1-16 (bit 0 = channel 1)
Word 2 Discrepancy errors, channels 17-32 (bit 0 = channel 17)
Word 3 LFD errors, channels 1-16 (bit 0 = channel 1)
Word 4 LFD errors, channels 17-32 (bit 0 = channel 17)
OEM PARAMETERS
PHYSICAL MODULE:
RACK 1: (DI)
32 BOOLEAN inputs
RACK 2: (DIAG)
3 INTEGER inputs
Word 1 Health status bits, 0=healthy 1=fault
bit 0-2 Microcontroller watchdog (bit 0=A, bit 1=B, bit2=C)
bit 3-5 MP watchdog (bit 0=A, bit 1=B, bit2=C)
bit 6-8 Microcontroller slice health (bit 0=A, bit 1=B, bit2=C)
bit 9-11 Combined slice health (bit 0=A, bit 1=B, bit2=C)
bit 12 Power Fail
bit 13-15 not used
Word 2 Diagnostic bits
bit 0 Slice A
=1 slice is not responding or there is an error
=0 slice is responding
bit 1 Slice B
=1 slice is not responding or there is an error
=0 slice is responding
bit 2 Slice C
=1 slice is not responding or there is an error
=0 slice is responding
bit 3 Module offline or missing
=1 offline or missing
=0 online
bit 4 Single slot hot repair
=1 in progress
=0 not in progress
bit 5 Discrepancy errors
=1 faults detected
=0 no faults detected
bit 6 LFD faults
=1 faults detected
=0 no faults detected
Word 3 Slot number of active module
RACK 3: (FAULTS)
4 INTEGER inputs
Word 1 Discrepancy errors, channels 1-16 (bit 0 = channel 1)
Word 2 Discrepancy errors, channels 17-32 (bit 0 = channel 17)
Word 3 LFD errors, channels 1-16 (bit 0 = channel 1)
Word 4 LFD errors, channels 17-32 (bit 0 = channel 17)
OEM PARAMETERS
PHYSICAL MODULE:
RACK 1: (DI)
64 BOOLEAN inputs
RACK 2: (DIAG)
3 INTEGER inputs
Word 1 Health status bits, 0=healthy 1=fault
bit 0-2 Microcontroller watchdog (bit 0=A, bit 1=B, bit2=C)
bit 3-5 MP watchdog (bit 0=A, bit 1=B, bit2=C)
bit 6-8 Microcontroller slice health (bit 0=A, bit 1=B, bit2=C)
bit 9-11 Combined slice health (bit 0=A, bit 1=B, bit2=C)
bit 12 Power Fail
bit 13-15 not used
Word 2 Diagnostic bits
bit 0 Slice A
=1 slice is not responding or there is an error
=0 slice is responding
bit 1 Slice B
=1 slice is not responding or there is an error
=0 slice is responding
bit 2 Slice C
=1 slice is not responding or there is an error
=0 slice is responding
bit 3 Module offline or missing
=1 offline or missing
=0 online
bit 4 Single slot hot repair
=1 in progress
=0 not in progress
bit 5 Discrepancy errors
=1 faults detected
=0 no faults detected
bit 6 LFD faults
=1 faults detected
=0 no faults detected
Word 3 Slot number of active module
RACK 3: (FAULTS)
8 INTEGER inputs
Word 1 Discrepancy errors, channels 1-16 (bit 0 = channel 1)
Word 2 Discrepancy errors, channels 17-32 (bit 0 = channel 17)
Word 3 Discrepancy errors, channels 33-48 (bit 0 = channel 33)
Word 4 Discrepancy errors, channels 49-64 (bit 0 = channel 49)
Word 5 LFD errors, channels 1-16 (bit 0 = channel 1)
Word 6 LFD errors, channels 17-32 (bit 0 = channel 17)
Word 7 LFD errors, channels 33-48 (bit 0 = channel 33)
Word 8 LFD errors, channels 49-64 (bit 0 = channel 49)
OEM PARAMETERS
PHYSICAL MODULE:
RACK 1: (DO)
16 BOOLEAN outputs
RACK 2: (DIAG)
4 INTEGER inputs
Word 1 Health status bits, 0=healthy 1=fault
bit 0-2 Microcontroller watchdog (bit 0=A, bit 1=B, bit2=C)
bit 3-5 MP watchdog (bit 0=A, bit 1=B, bit2=C)
bit 6-8 Microcontroller slice health (bit 0=A, bit 1=B, bit2=C)
bit 9-11 Combined slice health (bit 0=A, bit 1=B, bit2=C)
bit 12 Power Fail
bit 13-15 not used
Word 2 Diagnostic bits
bit 0 Slice A
=1 slice is not responding or there is an error
=0 slice is responding
bit 1 Slice B
=1 slice is not responding or there is an error
=0 slice is responding
bit 2 Slice C
=1 slice is not responding or there is an error
=0 slice is responding
bit 3 Module offline or missing
=1 offline or missing
=0 online
bit 4 Single slot hot repair
=1 in progress
=0 not in progress
bit 5 Discrepancy errors
=1 faults detected
=0 no faults detected
bit 6 LFD faults
=1 faults detected
=0 no faults detected
Word 3 Slot number of active module
Word 4 Fault flags, 0=healthy 1=fault
bit 0-2 Logic supply power fail fault (ABC, bit0=A, bit2=C)
bit 3-5 Field supply power fail fault (ABC)
bit 6 Bias supply 1 power fail fault
bit 7 Bias supply 2 power fail fault
bit 8 Logic supply power fail fault
bit 9-10 Reserved
bit 11-13 Drive supply power fail fault (ABC)
bit 14 Field supply power fail fault
bit 15 Over temperature fault
RACK 3: (FAULTS)
1 INTEGER inputs
Word 1 LFD errors, channels 1-16 (bit 0 = channel 1)
OEM PARAMETERS
PHYSICAL MODULE:
RACK 1: (DO)
16 BOOLEAN outputs
RACK 2: (DIAG)
4 INTEGER inputs
Word 1 Health status bits, 0=healthy 1=fault
bit 0-2 Microcontroller watchdog (bit 0=A, bit 1=B, bit2=C)
bit 3-5 MP watchdog (bit 0=A, bit 1=B, bit2=C)
bit 6-8 Microcontroller slice health (bit 0=A, bit 1=B, bit2=C)
bit 9-11 Combined slice health (bit 0=A, bit 1=B, bit2=C)
bit 12 Power Fail
bit 13-15 not used
Word 2 Diagnostic bits
bit 0 Slice A
=1 slice is not responding or there is an error
=0 slice is responding
bit 1 Slice B
=1 slice is not responding or there is an error
=0 slice is responding
bit 2 Slice C
=1 slice is not responding or there is an error
=0 slice is responding
bit 3 Module offline or missing
=1 offline or missing
=0 online
bit 4 Single slot hot repair
=1 in progress
=0 not in progress
bit 5 Discrepancy errors
=1 faults detected
=0 no faults detected
bit 6 LFD faults
=1 faults detected
=0 no faults detected
Word 3 Slot number of active module
Word 4 Fault flags, 0=healthy 1=fault
bit 0-2 Logic supply power fail fault (ABC, bit0=A, bit2=C)
bit 3-5 Field supply power fail fault (ABC)
bit 6 Bias supply 1 power fail fault
bit 7 Bias supply 2 power fail fault
bit 8 Logic supply power fail fault
bit 9-10 Reserved
bit 11-13 Drive supply power fail fault (ABC)
bit 14 Field supply power fail fault
bit 15 Over temperature fault
RACK 3: (FAULTS)
1 INTEGER inputs
Word 1 LFD errors, channels 1-16 (bit 0 = channel 1)
OEM PARAMETERS
PHYSICAL MODULE:
RACK 1: (DO)
32 BOOLEAN outputs
RACK 2: (DIAG)
4 INTEGER inputs
Word 1 Health status bits, 0=healthy 1=fault
bit 0-2 Microcontroller watchdog (bit 0=A, bit 1=B, bit2=C)
bit 3-5 MP watchdog (bit 0=A, bit 1=B, bit2=C)
bit 6-8 Microcontroller slice health (bit 0=A, bit 1=B, bit2=C)
bit 9-11 Combined slice health (bit 0=A, bit 1=B, bit2=C)
bit 12 Power Fail
bit 13-15 not used
Word 2 Diagnostic bits
bit 0 Slice A
=1 slice is not responding or there is an error
=0 slice is responding
bit 1 Slice B
=1 slice is not responding or there is an error
=0 slice is responding
bit 2 Slice C
=1 slice is not responding or there is an error
=0 slice is responding
bit 3 Module offline or missing
=1 offline or missing
=0 online
bit 4 Single slot hot repair
=1 in progress
=0 not in progress
bit 5 Discrepancy errors
=1 faults detected
=0 no faults detected
bit 6 LFD faults
=1 faults detected
=0 no faults detected
Word 3 Slot number of active module
Word 4 Fault flags, 0=healthy 1=fault
bit 0-2 Logic supply power fail fault (ABC, bit0=A, bit2=C)
bit 3-5 Field supply power fail fault (ABC)
bit 6 Bias supply 1 power fail fault
bit 7 Bias supply 2 power fail fault
OEM PARAMETERS
PHYSICAL MODULE:
RACK 1: (PI)
4 INTEGER inputs
RACK 2: (AO)
4 INTEGER outputs
RACK 3: (DIAG)
4 INTEGER inputs
Word 1 Health status bits, 0=healthy 1=fault
bit 0-2 Microcontroller watchdog (bit 0=A, bit 1=B, bit2=C)
bit 3-5 MP watchdog (bit 0=A, bit 1=B, bit2=C)
bit 6-8 Microcontroller slice health (bit 0=A, bit 1=B, bit2=C)
bit 9-11 Combined slice health (bit 0=A, bit 1=B, bit2=C)
bit 12 Power Fail
bit 13-15 not used
Word 2 Diagnostic bits
bit 0 Slice A
=1 slice is not responding or there is an error
=0 slice is responding
bit 1 Slice B
=1 slice is not responding or there is an error
=0 slice is responding
bit 2 Slice C
=1 slice is not responding or there is an error
=0 slice is responding
bit 3 Module offline or missing
=1 offline or missing
=0 online
bit 4 Single slot hot repair
=1 in progress
=0 not in progress
bit 5 Discrepancy errors
=1 faults detected
=0 no faults detected
bit 6 LFD faults
=1 faults detected
=0 no faults detected
Word 3 Slot number of active module
Word 4 Fault flags, 0=healthy 1=fault
bit 0-2 Logic supply power fail fault (ABC, bit0=A, bit2=C)
bit 3-5 Reserved
bit 6 Field power fail fault
bit 7 Output discrepancy error
bit 8-15 Reserved
RACK 4: (FAULTS)
3 INTEGER inputs
Word 1 Discrepancy errors
bits 0-3 PI channels 1-4 (bit 0 = channel 1)
This definition provides module status for a logical Triguard MRB01XS remote slave chassis
expansion module.
The logical module accounts for the 3 physical modules FCR-A, FCR-B and FCR-C.
OEM PARAMETERS:
PHYSICAL MODULE:
Note 1:
The status of MRB01XS FCR's can only be determined by the discrepancy status of accesses performed to I/O
modules within the chassis of the MRB01XS. If no such modules exist or if no MRB01XS FCR's are fitted then no
faults can be reported.
This definition provides module status for a logical Triguard MRB04XM remote master chassis
expansion interface module.
The logical module accounts for the 3 physical modules FCR-A, FCR-B and FCR-C.
OEM PARAMETERS:
PHYSICAL MODULE:
4. Operation
The Trusted TMR Processor provides fault monitoring, self-test and diagnostics functions.
Fault Detection within a Trusted / SC300E system can be categorized into four regions:
• User Application
Using current Trusted methods for detection of faults, the TMR Processor can monitor for failures up
to the Expander section. The TMR Processor is also able to separate Bridge hardware faults from
SC300E I/O module faults. The Triguard I/O modules carry out on-board diagnostic tests which are
relayed back to the TMR Processor via the Bridge module.
The user application can also be programmed to read error flags in the I/O module fault registers to
annunciate the detection of module faults. Second faults that leave the system unable to confirm
healthy operation will result in the TMR Processor stopping all communication with the 8161 bridge
modules, ensuring that critical outputs go to a safe state when the internal watchdogs time out.
6. Specifications