ABB Triguard SC300E Safety Manual

Also see for Triguard SC300E: User manual

Contents

ABB Triguard SC300E Safety Manual Manual pdf 21 page image

Issue 5 - September 2006 Page 21 of 65Bit Reference Description0 History Entry in history table - errors logged relating toprocessors and communications1 Data/Voting 2oo3 voting error – voting discrepanciesencountered and logged by the processors duringI/O scanning2 LFD latent fault detection of failed on or failed off signalpaths – monitor and fault bits set depending onfault type and location3 Monitor Initialisation error – bits are set in the fault ormonitor registers4 INIT System initialisation error – modules referenced inthe table of operations are missing. Either a singleslot module or both modules missing in a dual slothot repair partnership.5 MPP A Processor A failure – out of synchronisation6 MPP B Processor B failure – out of synchronisation7 MPP C Processor C failure – out of synchronisation8 MPP A power Processor A loss of power – fuse or PSU9 MPP B power Processor B loss of power – fuse or PSU10 MPP C power Processor C loss of power – fuse or PSU11 MPP lowBatteryMemory battery - low charge on one or more of theprocessor’s batteries12 Off-line module Single slot repair - module off-line – should be on-line.13 Digital Output Fault on any digital output module(s)14 Multiple fault Multiple faults on a module15 ReservedTable 1 FALT Error Flags (RTTS 8.30 versions 001 – 003)The error flags should be used to give primary indication to the operator/maintainer that a faultexists within the system. In addition to the error flags the chassis system power supply faultcontacts should also be wired to at least one digital input channel and used for system powersupply fault reporting. On the majority of systems other external fault indications would be wiredto digital input channels to provide maintenance alerts (eg cabinet temperature, field powersupply failure, loop fuse failure etc).3.5.6.1 Bits 0 - HistoryEntries in the system History table – the errors in the history table are those related to theprocessors and communications areas.3.5.6.2 Bit 1 - Data/VoteData (vote) entries – these errors are due to voting discrepancies encountered during the I/Oscanning. This bit is set by the main processors detecting errors and not the I/O modules andtherefore does not result directly in any other monitor/fault bits being set in the exception tables.3.5.6.3 Bit 2 - LFDLFD entries – these errors are due to latent fault testing of the I/O modules. LFD testing is doneon each I/O module in turn on a 20 second rotating basis. Since genuine LFD errors aredetected by the I/O module they will result in the I/O module health lamp being turned off andother bits in the monitor/fault flags being set eg if system channel A has a fault then the monitorflag bit 1000h would be set. It should be noted that LFD testing is not carried out on an outputmodule that is detected as not being healthy. However, LFD continues on input modules after