GE Mark VIeS System Manual
Read Online
Read the GE Mark VIeS System Manual online using the built-in PDF viewer.
Text of the manual
Mark* VIeS Functional Safety Systems
for General Market
Volume II: System Guide for General-purpose Applications
July 2019
Public Information
These instructions do not purport to cover all details or variations in equipment, nor to provide for every possible
contingency to be met during installation, operation, and maintenance. The information is supplied for informational
purposes only, and GE makes no warranty as to the accuracy of the information included herein. Changes, modifications,
and/or improvements to equipment and specifications are made periodically and these changes may or may not be reflected
herein. It is understood that GE may make changes, modifications, or improvements to the equipment referenced herein or to
the document itself at any time. This document is intended for trained personnel familiar with the GE products referenced
herein.
GE may have patents or pending patent applications covering subject matter in this document. The furnishing of this
document does not provide any license whatsoever to any of these patents.
Public Information – This document contains non-sensitive information approved for public disclosure.
GE provides the following document and the information included therein as is and without warranty of any kind,
expressed or implied, including but not limited to any implied statutory warranty of merchantability or fitness for
particular purpose.
For further assistance or technical information, contact the nearest GE Sales or Service Office, or an authorized GE Sales
Representative.
Issued: July 2019
© 2019 General Electric Company.
___________________________________
* Indicates a trademark of General Electric Company and/or its subsidiaries.
All other trademarks are the property of their respective owners.
We would appreciate your feedback about our documentation.
Please send comments or suggestions to [email protected]
Public Information
Mark VIeS Functional Safety Systems for General Market Volume I: System Guide
GEH-6860
Mark VIeS Control General Market Functional Safety Manual
GEH-6861
Mark VIeS Functional Safety System Equipment in Hazardous Locations (HazLoc)
Instruction Guide
GEH-6862
ToolboxST User Guide for Mark VIeS Functional Safety Systems
GEI-100846
Mark VIeS Functional Safety System Release Notes
GEI-100861
Mark VIeS Functional Safety Control Systems Power Distribution Modules (PDM)
Application Guide for General Market
GEI-100862
Mark VIeS Functional Safety Contact Input Module Summary Sheet
GEI-100863
Mark VIeS Functional Safety Relay Contact Output Module Summary Sheet
GEI-100864
Mark VIeS Functional Safety Vibration Input Module Summary Sheet
GEI-100865
Mark VIeS Functional Safety Universal Analog I/O Module Summary Sheet
GEI-100866
Mark VIeS Functional Safety Analog I/O Module Summary Sheet
GEI-100867
Mark VIe and Mark VIeS Functional Safety UCSC Controller Summary Sheet
GEI-100868
Mark VIe Modbus Master Communication Module Summary Sheet
GEI-100869
Mark VIe Industrial Ethernet / IONet Switches Summary Sheet
GEI-100870
Mark VIe Power Distribution Module Summary Sheet
GFK-3006
UCSC/UCEC Installation and Maintenance Requirements (IMR)
GFT-870
Mark VIeS Functional Safety System Technical Specifications
Mark VIeS DoC
EU Declaration of Conformity - Mark VIeS
System Guide
GEH-6855_Vol_II
3
Public Information
Safety Symbol Legend
Warning
Indicates a procedure or condition that, if not strictly observed, could result in
personal injury or death.
Caution
Indicates a procedure or condition that, if not strictly observed, could result in damage
to or destruction of equipment.
Attention
Indicates a procedure or condition that should be strictly followed to improve these
applications.
4
GEH-6855_Vol_II
GEH-6855_Vol_II Mark VIeS Functional Safety Systems Volume II
Public Information
Control System Warnings
Warning
To prevent personal injury or damage to equipment, follow all equipment safety
procedures, Lockout Tagout (LOTO), and site safety procedures as indicated by
Employee Health and Safety (EHS) guidelines.
Warning
This equipment contains a potential hazard of electric shock, burn, or death. Only
personnel who are adequately trained and thoroughly familiar with the equipment
and the instructions should install, operate, or maintain this equipment.
Warning
Isolation of test equipment from the equipment under test presents potential electrical
hazards. If the test equipment cannot be grounded to the equipment under test, the
test equipment’s case must be shielded to prevent contact by personnel.
To minimize hazard of electrical shock or burn, approved grounding practices and
procedures must be strictly followed.
Warning
To prevent personal injury or equipment damage caused by equipment malfunction,
only adequately trained personnel should modify any programmable machine.
Warning
Always ensure that applicable standards and regulations are followed and only
properly certified equipment is used as a critical component of a safety system. Never
assume that the Human-machine Interface (HMI) or the operator will close a safety
critical control loop.
GEH-6855_Vol_II System Guide 5
Public Information
Orderable Part Numbers................................................................................................................. 9
2
Controllers .......................................................................................................................................17
2.1 UCSC Controllers.................................................................................................................................. 17
2.2 Controller Password Protection ................................................................................................................ 37
2.3 Shared IONet........................................................................................................................................ 37
2.4 Black Channel Safety Communication....................................................................................................... 37
2.5 Controller Setup and Download................................................................................................................ 37
2.6 Initial Download to I/O Modules .............................................................................................................. 38
2.7 Controller Diagnostic Alarms................................................................................................................... 40
3
Unmanaged Ethernet Switches ..................................................................................................85
3.1 Available Form Factors........................................................................................................................... 86
3.2 Installation ........................................................................................................................................... 86
3.3 Configuration........................................................................................................................................ 87
3.4 IONet Switch Specifications .................................................................................................................... 87
3.5 Operation............................................................................................................................................. 88
3.6 Third-party Switch Replacement............................................................................................................... 90
4
YAIC Analog I/O Modules .............................................................................................................91
4.1 Mark VIeS YAIC Analog I/O Pack............................................................................................................ 91
4.2 YAIC Specific Alarms ...........................................................................................................................101
4.3 TBAIS1C Analog Input/Output ...............................................................................................................106
4.4 STAIS2A Simplex Analog Input..............................................................................................................113
5
YDIA Discrete Input Modules .................................................................................................... 115
5.1 Mark VIeS YDIA Discrete Input Pack ......................................................................................................115
5.2 Configuration.......................................................................................................................................119
5.3 YDIA Specific Alarms...........................................................................................................................120
5.4 TBCIS#C Contact Input with Group Isolation ............................................................................................121
5.5 STCIS#A Simplex Contact Input .............................................................................................................127
6
YDOA Discrete Output Modules ...............................................................................................131
6.1 Mark VIeS YDOA Discrete Output Pack...................................................................................................131
6.2 YDOA Configuration ............................................................................................................................137
6.3 YDOA Specific Alarms .........................................................................................................................138
6.4 TRLY Discrete Output Terminal Boards....................................................................................................142
6.5 TRLYS1B Relay Output with Coil Sensing................................................................................................143
6.6 TRLYS1D Relay Output with Solenoid Integrity Sensing .............................................................................150
6.7 TRLYS#F Relay Output – TMR Contact Voting .........................................................................................155
6.8 SRLYS2A Simplex Relay Output.............................................................................................................161
7
YUAA Universal I/O Modules.....................................................................................................171
7.1 Mark VIeS YUAA Universal I/O Pack......................................................................................................171
7.2 Specifications ......................................................................................................................................172
7.3 Module Installation and Mounting ...........................................................................................................176
7.4 Operation............................................................................................................................................186
7.5 Analog Inputs (Voltage or mA Current).....................................................................................................188
7.6 Current Outputs....................................................................................................................................189
6
GEH-6855_Vol_II
GEH-6855_Vol_II Mark VIeS Functional Safety Systems Volume II
Public Information
7.7 HART-Enabled mA Inputs and Outputs.....................................................................................................190
7.8 RTD Inputs..........................................................................................................................................191
7.9 Thermocouple Inputs.............................................................................................................................192
7.10 Digital Inputs and Outputs......................................................................................................................194
7.11 Pulse Accumulator................................................................................................................................200
7.12 Configuration.......................................................................................................................................200
7.13 Diagnostics..........................................................................................................................................213
7.14 Replacement........................................................................................................................................214
7.15 YUAA Diagnostic Alarms......................................................................................................................216
7.16 SUAA Universal Analog Terminal Board..................................................................................................225
8
YVIB Vibration Monitor Modules ..............................................................................................227
8.1 Mechanical Vibration Standards ..............................................................................................................227
8.2 Mark VIeS YVIB Vibration Monitor I/O Pack............................................................................................228
8.3 YVIB Functions ...................................................................................................................................234
8.4 YVIB Specific Diagnostic Alarms ...........................................................................................................271
8.5 TVBAVibration Input ...........................................................................................................................276
9
PSCA Modbus Master (Serial Communication) Module.....................................................285
9.1 PSCA Serial Communication I/O Pack .....................................................................................................285
9.2 PSCA Specific Alarms...........................................................................................................................291
9.3 SSCA Simplex Serial Communication Input/Output ....................................................................................293
10
PDM Power Distribution Modules..........................................................................................301
10.1 Power Distribution Overview..................................................................................................................301
10.2 PPDA Power Distribution System Feedback ..............................................................................................306
10.3 PPDA Specific Alarms ..........................................................................................................................319
10.4 JPDD DC Power Distribution..................................................................................................................362
10.5 JPDE DC Battery Power Distribution .......................................................................................................366
10.6 JPDG Core Power Distribution ...............................................................................................................373
10.7 JPDH High Density Power Distribution ....................................................................................................384
10.8 JPDS Core 28 V DC Power Distribution ...................................................................................................388
10.9 JGND Shield Ground ............................................................................................................................395
10.10Phoenix Power Supplies (GE Part Number Series 342A3648) ......................................................................398
11
Common I/O Module Functionality ........................................................................................441
11.1 BPPx Processor....................................................................................................................................441
11.2 I/O Module Common Diagnostic Alarms ..................................................................................................443
12
Maintenance and Replacement ..............................................................................................477
12.1 Maintenance ........................................................................................................................................477
12.2 Replacement........................................................................................................................................478
12.3 Ordering Parts......................................................................................................................................484
GEH-6855_Vol_II System Guide 7
Public Information
GEH-6855_Vol_II Mark VIeS Functional Safety Systems Volume II
Public Information
Orderable Part Numbers
The following tables provide the orderable part numbers for the Mark VIeS Functional Safety System product components,
including I/O packs, modules, Terminal Boards (TB), and daughterboards.
Note For replacement and ordering instructions, refer to the sections Replacement and Ordering Parts.
Attention
The information in this document applies to the Mark VIeS Functional Safety System
general market products; however, your application may not be licensed to access full
system capability and I/O packs as described in this document. For example, the Mark
VIeS Functional Safety System for General Markets only utilizes the following I/O
packs:
••
Analog I/O (YAIC)
••
Universal Analog (YUAA)
••
Vibration Input Monitor (YVIB)
••
Relay Output (YDOA)
••
Discrete Contact Input (YDIA)
••
Power Distribution System Diagnostics (PPDA)
••
Serial Modbus Communication (PSCA)
••
Mark VIeS Safety Controller (UCSCS2x)
••
Mark VIe Controller for Gateway (UCSCH1x)
Orderable Part Numbers
GEH-6855_Vol_II System Guide 9
Public Information
Module Part Numbers
I/O Pack/Part
Number
Associated Base
Assembly/Accessory
Description
Replacement Part within
Module
Notes
IS420YDIAS1B
N/A
Contact Input Safety I/O pack
Board: IS400BPPCS1A
Board: IS200BPDIS1A
IS410STCIS2A
Simplex, 24 pt - 24 V dc Contact
In, 4" S-type TB, with cover and
TB plugs, WROx posts
Board: IS400STCIS2A
Cover: 151X1202YE04PP01BL
52 pt TB: 64G6940-226L
IS410STCIS4A
Simplex, 24 pt - 48 V dc Contact
In, 4" S-type TB, with cover and
TB plugs, WROx posts
Board: IS400STCIS4A
Cover: 151X1202YE04PP01BL
52 pt TB: 64G6940-226L
IS410STCIS6A
Simplex, 24 pt - 125 V dc Contact
In, 4" S-type TB, with cover and
TB plugs, WROx posts
Board: IS400STCIS6A
Cover: 151X1202YE04PP01BL
52 pt TB: 64G6940-226L
UL Pending
IS410TBCIS1C
TMR, 24 pt - 125 V dc Contact In,
4" T-type TB, with cover and TB
blocks
Board: IS400TBCIS1C
Cover: 151X1202YE08PP16BL
24 pt TB (1-24): 173C9123BB
003
24 pt TB (25-48): 173C9123BB
004
UL Pending
IS410TBCIS2C
TMR, 24 pt - 24 V dc Contact In,
4" T-type TB, with cover and TB
blocks
Board: IS400TBCIS2C
Cover: 151X1202YE08PP16BL
24 pt TB (1-24): 173C9123BB
003
24 pt TB (25-48): 173C9123BB
004
IS410TBCIS3C
TMR, 24 pt - 48 V dc Contact In,
4" T-type TB, with cover and TB
blocks
Board: IS400TBCIS3C
Cover: 151X1202YE08PP16BL
24 pt TB (1-24): 173C9123BB
003
24 pt TB (25-48): 173C9123BB
004
10
GEH-6855_Vol_II
GEH-6855_Vol_II Mark VIeS Functional Safety Systems Volume II
Public Information
Module Part Numbers (continued)
I/O Pack/Part
Number
Associated Base
Assembly/Accessory
Description
Replacement Part within
Module
Notes
IS420YDOAS1B
N/A
Contact Output Safety I/O pack
Board: IS400BPPCS1A
Board: IS200BPDOS1
IS410SRLYS2A
Simplex, 12 Form C Contact Out,
7" S-type TB, with cover and TB
plugs
Board: IS400SRLYS2A
Cover: 151X1202YE04PP05BL
48 pt TB: 64G6940-224L
IS410TRLYS1B
Simplex or TMR, 12 pt - Form C
Relay, 1st 6 pts wetted, with cover
and TB blocks
Board: IS400TRLYS1B
Cover: 151X1202YE08PP18BL
24 pt TB (1-24): 173C9123BB
003
24 pt TB (25-48): 173C9123BB
004
3.15 A fuse: 64G5005-011
10 A 2PDT Relay: 64G5600-003
Relay Clip: 65G2101-011
IS410TRLYS1D
Simplex or TMR, 6 pt - Solenoid
Out, ohm monitor, 7" T-type TB,
with cover and TB block
Board: IS400TRLYS1D
Cover: 151X1202YE08PP18BL
24 pt TB: 173C9123BB 003
3.15 A fuse: 64G5005-011
10 A 2PDT Relay: 64G5600-003
Relay Clip: 65G2101-011
IS410TRLYS1F
TMR, 12 pt NO Voted Contacts, 7"
T-type TB, with cover and TB
blocks, WPDF post
Board: IS400TRLYS1F
Cover: 151X1202YE08PP14BL
24 pt TB (1-24): 173C9123BB
003
24 pt TB (25-48): 173C9123BB
004
IS410TRLYS2F
TMR, 12 pt NC Voted Contacts, 7"
T-type TB, with cover and TB
blocks, WPDF post
Board: IS400TRLYS2F
Cover: 151X1202YE08PP14BL
24 pt TB (1-24): 173C9123BB
003
24 pt TB (25-48): 173C9123BB
004
IS420YAICS1B
N/A
Analog In / Out Safety I/O pack
Board: IS400BPPCS1A
Board: IS400BPAIS1A
IS410STAIS2A
Simplex, 10 Analog in / 2 Analog
out, 4" S-type TB, with cover and
TB plugs
Board: IS400STAIS2A
Cover: 151X1202YE04PP01BL
48 pt TB: 64G6940-224L
IS410TBAIS1C
TMR, 10 Analog in / 2 Analog out,
4" S-type TB, with cover and TB
blocks
Board: IS400TBAIS1C
Cover: 151X1202YE08PP16BL
24 pt TB (1-24): 173C9123BB
003
24 pt TB (25-48): 173C9123BB
004
IS420YUAAS1A
N/A
Universal Analog Safety I/O pack
N/A
IS410SUAAS1A
Universal Analog Simplex, 16
Channel Volt/Current/TC/DI/Cntr,
3" S-type TB
52 pt TB: 64G6946-226L
Orderable Part Numbers
GEH-6855_Vol_II System Guide 11
Public Information
Module Part Numbers (continued)
I/O Pack/Part
Number
Associated Base
Assembly/Accessory
Description
Replacement Part within
Module
Notes
IS420YVIBS1B
N/A
Vibration I/O pack
Board: IS400BPPCS1A
Board: IS400BBAAS1A
IS410TVBAS2B
Simplex or TMR, 8 Vib/Prox, 3
Pos, 2 Key/Pos, 7" T-type TB, with
cover and TB blocks
Board: IS400TVBAS2B
Cover: 151X1202YE08PP14BL
24 pt TB (1-24): 173C9123BB
003
24 pt TB (25-48): 173C9123BB
004
IS420PSCAH1B
N/A
Serial Communication / Modbus
Master I/O pack
Board: IS400BPPCS1A
Board: IS400BSCAH3A
IS410SSCAH2A
Simplex, 6 channel Serial Comm
Termination Board , 4" S-type TB,
with cover and TB plugs
Board: IS400SSCAH2A
Cover: 151X1202YE04PP01BL
48 pt TB: 64G6940-224L
Power Distribution Module and Daughterboard Part Numbers
I/O Pack/Part
Number
Associated Base
Assembly/Accessory
Description
Replacement Part within
Module
Notes
IS420PPDAH1B
N/A
JPDG / JPDS Power Supply
Diagnostics I/O pack
Board: IS400BPPCH1A
Board: IS400BPDAH1A
IS410JPDSG1A
28 V Control Power Distribution,
with diagnostics I/O pack, with
cover
Board: IS400JPDSG1A
Cover: 151X1202YE12PP02BL
IS410JPDGH1A
28 V Dual Control and 24 V (or 48
V) Wetting Power Distribution,
with diagnostics, with cover
Board: IS400JPDGH1A
Cover: 151X1202YE12PP02BL
10 A fuse: 64G5002-001
15 A fuse: 64G5003-001
N/A
IS410JPDDG2A
24 or 48 V dc wetting distribution
via 6 switch branches, 5 x 20 mm
fuse holder, with cover
Board: IS400JPDDG2A
Cover: 151X1202YE12PP04BL
Fuse: any 20.0 × 5.0 mm (0.79 ×
0.20 in)
IS410JPDDG3A
24 or 48 V dc wetting distribution
via 6 switch branches, 1.25 x 0.2
5in fuse holder, with cover
Board: IS400JPDDG3A
Cover: 151X1202YE12PP04BL
Fuse: any 31.75 × 6.35 mm (1.25
× 0.25 in)
IS410JPDEG1A
TMR Wetting Power System /
Distribution module (24 or 48 V
dc), with cover
Board: IS400JPDEG1A
Cover: 151X1202YE12PP01BL
7 A fuse: 64G5001-001
15 A fuse: 64G5003-001
IS410JPDHG1A
Control Power Fanout
Distribution, with cover
Board: IS400JPDHG1A
Cover: 151X1202YE12PP03BL
12
GEH-6855_Vol_II
GEH-6855_Vol_II Mark VIeS Functional Safety Systems Volume II
Public Information
Power Distribution Module and Daughterboard Part Numbers (continued)
I/O Pack/Part
Number
Associated Base
Assembly/Accessory
Description
Replacement Part within
Module
Notes
N/A
IS400WROBH1A
Optional daughterboard
IS400SRLYS2A wetting and
fusing, adds hi/lo fusing to 1st 6
relays
3.15 A fuse: 64G5005-011
IS400WROFH1A
Optional daughterboard
IS400SRLYS2A wetting and
fusing, adds form-C COM fuses to
all 12 relays
3.15 A fuse: 64G5005-011
IS400WROGH1A
Optional daughterboard
IS400SRLYS2A wetting and
fusing, adds hi-side fusing to all
12 relays
3.15 A fuse: 64G5005-011
IS400WPDFH1A
Optional daughterboard
IS400TRLYS#F wetting and
fusing, Adds hi/lo fusing and
sensed power to 2 groups of 6
relays
3.15 A fuse: 64G5005-005
UL Pending
IS400WPDFH2A
Optional daughterboard
IS400TRLYS#F wetting and
fusing, Add hi side fusing and
sensed power to 2 groups of 6
relays
3.15 A fuse: 64G5005-005
UL Pending
Mark VIe and Mark VIeS Controllers Part Numbers
I/O Pack/Part
Number
Associated Base
Assembly/Accessory
Description
Replacement Part within
Module
Notes
IS420UCSCS2A
N/A
Mark VIeS Safety Controller
N/A
IS420UCSCH1B
N/A
Mark VIe Gateway Controller
N/A
Orderable Part Numbers
GEH-6855_Vol_II System Guide 13
Public Information
IONet Switch and DIN-rail Mounting Clip Part Numbers
I/O Pack/Part
Number
Associated Base
Assembly/Accessory
Description
Replacement Part
within Module
Notes
IS420ESWAH1A
N/A
IONet Switch - 8 copper, 1 FX
Multimode Fiber (LC-type)
N/A
IS420ESWAH2A
N/A
IONet Switch - 8 copper, 2 FX
Multimode Fiber (LC-type)
N/A
IS420ESWAH3A
N/A
IONet Switch - 8 copper
N/A
IS420ESWAH4A
N/A
IONet Switch - 8 copper, 1 FX
Singlemode Fiber (LC-type)
N/A
IS420ESWAH5A
N/A
IONet Switch - 8 copper, 2 FX
Singlemode Fiber (LC-type)
N/A
IS420ESWBH1A
N/A
IONet Switch -16 copper, 1 FX
Multimode Fiber (LC-type)
N/A
IS420ESWBH2A
N/A
IONet Switch - 16 copper, 2 FX
Multimode Fiber (LC-type)
N/A
IS420ESWBH3A
N/A
IONet Switch - 16 copper
N/A
IS420ESWBH4A
N/A
IONet Switch - 16 copper, 1 FX
Singlemode Fiber (LC-type)
N/A
IS420ESWBH5A
N/A
IONet Switch - 16 copper, 2 FX
Singlemode Fiber (LC-type)
N/A
259B2451BVP1
N/A
Option DIN-rail base for ESWA
and ESWB, long edge of switch
body parallel to DIN-rail
N/A
259B2451BVP2
N/A
Option DIN-rail base for ESWA,
long edge of switch body
perpendiculr to DIN-rail
N/A
259B2451BVP4
N/A
Option DIN-rail base for ESWB,
long edge of switch body
perpendicular to DIN-rail
N/A
14
GEH-6855_Vol_II
GEH-6855_Vol_II Mark VIeS Functional Safety Systems Volume II
Public Information
Mark VIe Power Supplies and OR-ing Module Part Numbers
I/O Pack/Part
Number
Associated Base
Assembly/Accessory
Description
Replacement
Part within
Module
Notes
342A3648P120W24
N/A
120W Power Supply
120/240AC//125/250DC > 24DC
N/A
342A3648P120W24C
N/A
120W Power Supply
120/240AC//125/250DC > 24DC, Coated
N/A
342A3648P120W28
N/A
120W Power Supply
120/240AC//125/250DC > 28DC
N/A
342A3648P120W28C
N/A
120W Power Supply
120/240AC//125/250DC > 28DC, Coated
N/A
342A3648P240W24
N/A
240W Power Supply
120/240AC//125/250DC > 24DC
N/A
342A3648P240W24C
N/A
240W Power Supply
120/240AC//125/250DC > 24DC, Coated
N/A
342A3648P240W28
N/A
240W Power Supply
120/240AC//125/250DC > 28DC
N/A
342A3648P240W28C
N/A
240W Power Supply
120/240AC//125/250DC > 28DC, Coated
N/A
342A3648P240W48
N/A
240W Power Supply
120/240AC//125/250DC > 48DC
N/A
342A3648P480W24
N/A
480W Power Supply
120/240AC//125/250DC > 24DC
N/A
342A3648P480W24C
N/A
480W Power Supply
120/240AC//125/250DC > 24DC, Coated
N/A
342A3648P480W28
N/A
480W Power Supply
120/240AC//125/250DC > 28DC
N/A
342A3648P480W28C
N/A
480W Power Supply
120/240AC//125/250DC> 28DC, Coated
N/A
342A3648P480W48
N/A
480W Power Supply
120/240AC//125/250DC > 48DC
N/A
342A3648P960W24
N/A
960W Power Supply
120/240AC//125/250DC > 24DC
N/A
342A3648P960W28
N/A
960W Power Supply
120/240AC//125/250DC > 28DC
N/A
342A3647P960W48
N/A
960W Power Supply
120/240AC//125/250DC > 48DC
N/A
342A3648PF20A28C
N/A
FET-ORing Module - 28VDC 2X10ADC,
Coated
N/A
342A3648PF40A28C
N/A
FET-ORing Module - 28VDC 2X20ADC,
Coated
N/A
342A3648PF80A28C
N/A
FET-ORing Module - 28VDC 2X40ADC,
Coated
N/A
342A3647PD40A48
N/A
Diode-ORing Module - 48VDC 2x20ADC
N/A
Orderable Part Numbers
GEH-6855_Vol_II System Guide 15
Public Information
GEH-6855_Vol_II Mark VIeS Functional Safety Systems Volume II
Public Information
UCSC controllers are compact, stand-alone controllers that run application-specific control system logic used in a diverse
range of applications, such as wind turbines, gas and steam turbines, and combined-cycle power plants.
The UCSC controller offers the following advantages:
•
Single module
•
No battery
•
No fan
•
No jumper settings required
•
Flash memory can be conveniently updated
•
Can be expanded to include seven additional I/O ports
The UCSC controller mounts in a panel and communicates with I/O modules through on-board I/O network (IONet),
PROFINET, High-speed Serial Link (HSSL), and/or other interfaces.
UCSC Controller Data Name Plate
Note For additional information, refer to the following documents:
• Mark* VIe and Mark VIeS Functional Safety UCSC Controller Summary Sheet (GEI-100867)
• Mark VIeS Functional Safety Systems for General Market Volume I: System Guide (GEH-6855_Vol_I)
• ToolboxST *User Guide for Mark VIeS Functional Safety Systems (GEH-6862)
• Mark VIeS Functional Safety System Release Notes (GEI-100846)
• UCSC/UCEC Installation and Maintenance Requirements (IMR) (GFK-3006)
Controllers
GEH-6855_Vol_II System Guide 17
Public Information
Mark VIe UCSCH1B Controllers
The Mark VIe IS420UCSCH1B quad core controller uses real-time hypervisor technology and QNX® Neutrino, a real-time,
multi-tasking operating system (OS) to run high-speed, high-reliability industrial applications. Embedded Field Agent (EFA)
technology is used to apply Predix™cloud-based applications and/or locally hosted web applications over a secure
connection and deliver real-time data.
The UCSCH1x controller is loaded with software specific to its application. As a turbine or balance of plant (BoP) controller,
it runs the Mark VIe firmware and applications and utilizes IONet interfaces. IONet is a private special-purpose Ethernet that
only supports Mark controls I/O packs and controllers. IEEE 1588 protocol is used through the IONet interfaces to
synchronize the clock of the I/O modules and controllers to within ±100 microseconds. External data is transferred to and
from the control system database in the controller over the IONet interfaces. This includes process inputs/outputs to the I/O
modules. Unlike traditional controllers where I/O is on a backplane, the UCSC controller does not host any application I/O. In
a redundant set, all I/O networks are attached to each controller, providing them with all input data. This hardware and
software architecture guarantees that no single point of application input is lost if a controller is powered down for
maintenance or repair.
The UCSCH1B is available beginning with ControlST* V07.01, and supports Simplex, Dual, and Triple Modular Redundant
(TMR) redundancy.
UCSCH1 Platform Configuration Supported Features
Platform
Embedded PPNG
Embedded EtherCAT
EFA
UCSCH1B
X
X
✓
Mark VIe UCSCH1B Controller
18
GEH-6855_Vol_II
GEH-6855_Vol_II Mark VIeS Functional Safety Systems Volume II
Public Information
Mark VIeS UCSCS2A Controllers
The IS420UCSCS2A dual core controller runs the Mark VIeS Safety control applications used for functional safety loops to
achieve SIL 2 and 3 capabilities. Mark VIeS Safety equipment is used by operators that are knowledgeable in
safety-instrumented system (SIS) applications to reduce risk in critical safety functions. Safety controllers and distributed I/O
modules are specifically programmed for safety control use, and this specific control hardware and software is compliant with
the IEC 61508 certification. The Mark VIeS Safety controller runs on QNX Neutrino, a real-time, multi-tasking operating
system (OS).
The UCSCS2A is available beginning with ControlST V07.02, and supports Simplex, Dual, and TMR redundancy.
Mark VIeS Safety UCSCS2A Controller
Controllers
GEH-6855_Vol_II System Guide 19
Public Information
IS420UCSCH1: quad core, 1.2 GHz AMD G-Series
IS420UCSCS2: dual core, 1.6 GHz AMD G-Series
Memory
IS420UCSCH1: 4 GB DDR3-1333 SDRAM
IS420UCSCS2: 2 GB DDR3-1066 SDRAM
NVSRAM
Supports 3067 nonvolatile program variable, 338 forces, and 64 totalizers
Not supported by the Mark VIeS Safety control
Ports
•
5 Ethernet ports on front panel (Refer to the section Interface Details.)
•
1 Ethernet port on bottom used for connectivity to Predix
•
2 USB ports only used to initially set up UDH network IP address or for restore function
•
1 COM port is 115200 bit/s, 8N1, RJ-45 connector, no Flow-Control, serial redirection of UEFI-setup, and
typically used by GE for troubleshooting in field
•
1 Display Port (disabled after startup)
•
1 microSD (not currently supported)
LEDs
Refer to the section LEDs.
Input Power
Refer to the section Power Requirements.
HMI
ControlST V07.00.00C or later
Programming
Control block language with analog and discrete blocks; Boolean logic represented in relay ladder diagram format.
Supported data types include:
•
Boolean
•
16-bit signed integer
•
16-bit unsigned integer
•
32-bit signed integer
•
32-bit unsigned integer
•
32-bit floating point
•
64-bit long floating point
Dimensions
UCSC: 168 x 150 x 55 mm (6.61 x 5.90 x 2.17 in) (H x D x W)
UCSC with mounting: 204 x 152 x 55 mm (8.03 x 5.99 x 2.17 in) (H x D x W)
Weight
1,327 g (46.8 oz)
Mounting
Refer to the section Mounting Requirements.
Cooling
Convection
Operating temperature
-40 to 70°C (-40 to 158 °F), ambient 25 mm (0.98 in) from any point on UCSC
Storage Temperature
-40 to 85°C (-40 to 185 °F)
Humidity
95% non-condensing
Altitude
Normal Operation: 0 to 1,000 m (0 to 3281 ft) at 101.3 to 89.8 kPa
Extended Operation: 1,000 to 3,000 m (3281 to 9,843 ft) at 89.8 to 69.7 kPa; requires temperature derating up to
3000 m (9,843 ft) = 65°C (149 °F) max
Reliability MTBF at 30°C
(86 °F)
IS420UCSCH1: 414,248 hours
IS420UCSCS2: 417,821 hours
ECCN US Classification
Can be supplied upon request
Certifications
Refer to the section Agency Certifications and Standards.
20
GEH-6855_Vol_II
GEH-6855_Vol_II Mark VIeS Functional Safety Systems Volume II
Public Information
UCSC Mounting and Installation Requirements
2.1.4.1
UCSC Mounting Requirements
The following are requirements for mounting the UCSC controller:
•
Directly mount the UCSC to the mounting base using the two mounting screws.
•
Vertical mount with unobstructed air flow through fins.
•
Leave a minimal 100 mm (3.94 in) air gap above and below the UCSC.
•
Parallel mount UCSC to UCSC requires a minimal 50 mm (1.97 in) spacing to achieve full temperature rating.
•
The operating temperature envelope is 25 mm (0.98 in) from any point on UCSC.
Controllers
GEH-6855_Vol_II System Guide 21
Public Information
UCSC Mounting Requirements to Achieve 70ºC Operating Temperature
22
GEH-6855_Vol_II
GEH-6855_Vol_II Mark VIeS Functional Safety Systems Volume II
Public Information
UCSC Mounting Requirements to Achieve 65ºC Operating Temperature
Controllers
GEH-6855_Vol_II System Guide 23
Public Information
UCSC Controller Mounting Dimensions
24
GEH-6855_Vol_II
GEH-6855_Vol_II Mark VIeS Functional Safety Systems Volume II
Public Information
UCSC Controller Input Power
—
18
30.8
Watts
Voltage
18
24/28
30
V dc
Input Capacitance
—
25
—
uF
Surge Protection
Non-replaceable 4 A 125 V dc rated fuse
Nominal melting: 26 A squared seconds (A2 sec)
Reverse Polarity Protection
Provided
Reversing the + and - input will not damage the UCSC, nor will it power up.
3-pin Power Plug
Item
Description
Pin 1
Ground
Pin 2
Negative
The UCSC case is bonded to power supply negative.
Pin 3
Positive
Wire Sizes
28 to 16 AWG
Screw Torque
0.23 Nm (2 in-Ib)
Part Number
Phoenix Contact MC 1,5/ 3-STF-3,81 - 1827716
Controllers
GEH-6855_Vol_II System Guide 25
Public Information
UCSC Connection Ports (Front View)
Note For further information, refer to the ToolboxST User Guide for Mark VIeS Functional Safety Systems (GEH-6862), the
section System Controller Platforms.
26
GEH-6855_Vol_II
GEH-6855_Vol_II Mark VIeS Functional Safety Systems Volume II
Public Information
UCSC Connection Ports (Bottom View)
Note
† For instructions to set up the controller Internet Protocol (IP) address using the COM port, refer to the ToolboxST
User Guide for Mark VIeS Functional Safety Systems (GEH-6862), the section Configure and Transfer IPAddress to UCSC
Controller.
Controllers
GEH-6855_Vol_II System Guide 27
Public Information
Mark VIe UCSCH1B Ethernet Ports
Ethernet Port
Description
IONet Ethernet Interface
(3 Ports)
UCSCH1B:
T/SL3 is network for TMR (using all three ports).
S/SL2 is network for Dual redundancy (used with R/SL1).
R/SL1 is network for Simplex redundancy.
Twisted pair 10Base-TX/100Base-TX, RJ-45 connector is used.
TCP/IP protocols is used to communicate between controllers and I/O modules.
For TMR and Dual configurations, IONet redundancy is equal to controller redundancy.
For Simplex configurations, both Simplex and TMR IONet redundancy are supported.
ENET 1 Primary Ethernet
Interface to LAN
UDH
Twisted pair 10Base-T/100Base-TX, RJ-45 connector is used.
TCP/IP protocol is used for communication between controller and ToolboxST application.
TCP/IP protocol is used for alarm communication to HMIs.
Modbus TCP Slave and/or OPC UA
EGD protocol is used for application variable communication to HMIs.
ENET 2
UCSCH1B:
Secondary plant network
Twisted pair 10Base-T/100Base-TX, RJ-45 connector is used.
Modbus TCP Slave, OPC UA, and/or EGD
Mark VIeS UCSCS2A Ethernet Ports
Ethernet Port
Description
IONet Ethernet Interface
(3 Ports)
T/SL3 is network for TMR (using all three ports).
S/SL2 is network for Dual redundancy (used with R/SL1).
R/SL1 is network for Simplex redundancy.
Twisted pair 10Base-TX/100Base-TX, RJ-45 connector is used.
TCP/IP protocols is used to communicate between controllers and I/O modules.
For TMR and Dual configurations, IONet redundancy is equal to controller redundancy.
For Simplex configurations, both Simplex and TMR IONet redundancy are supported.
ENET 1 Primary Ethernet
Interface to LAN
UDH
Twisted pair 10Base-T/100Base-TX, RJ-45 connector is used.
TCP/IP protocol is used for communication between controller and the ToolboxST application.
TCP/IP protocol is used for alarm communication to HMIs.
Modbus TCP Slave
EGD protocol is used for application variable communication to HMIs.
ENET 2
Not supported
28
GEH-6855_Vol_II
GEH-6855_Vol_II Mark VIeS Functional Safety Systems Volume II
Public Information
UDH Network Configuration
The UCSC is typically set up for communications on the UDH network using an unencrypted minimum 4 GB flash drive that
is configured with the ToolboxST application. The factory default IP address is 192.168.101.111. The correct UDH IP address
must be properly set up so that the controller can communicate to the site HMIs.
Note The UCSC, as shipped from the factory, does not include the software on the controller to support communication
from the PHY PRES button to the EFA. The user needs to download to the controller at least once (using ToolboxST) to
enable this.
➢➢
To change the UDH network IP address for the UCSC
1.
Verify that the HMI computer running the ToolboxST application has been configured (through Windows OS) with the
correct IP address for the UDH network.
2.
From the ToolboxST Component Editor, verify that the controller Platform is set as UCSCxxx.
3.
From the Component Editor General tab Property Editor Network Adapter 0, configure the appropriate controller IP
address as a relative subnet to the HMI’s UDH IP address from Step 1.
4.
Insert a non-encrypted, USB 2.0 only flash drive with a minimum 4 GB capacity into a USB port of the computer that is
running the ToolboxST application.
5.
From the ToolboxST Component Editor, select Device, Download, and Controller Setup to launch the Controller
Setup Wizard.
6.
Follow the on-screen instructions to load the flash drive. Refer to the ToolboxST User Guide for Mark VIeS Functional
Safety Systems (GEH-6862), the section Configure and Transfer IPAddress to UCSC Controller for further instructions.
➢➢
To set the controller’s network address using the COM port
Attention
Use a UCSC COM port adapter, a standard serial to USB cable, and/or a Cat5e or
better Ethernet cable for this connection.
1.
Connect the UCSC COM port adapter to the Ethernet cable and the other end of the cable to the UCSC COM port.
2.
Connect the UCSC COM port adapter to the serial to USB cable, then to the computer that runs the ToolboxST
application.
3.
From the ToolboxST Component Editor General tab, select Device, Download, and Controller Setup to launch the
Controller Setup Wizard.
4.
Follow the on-screen instructions to transfer the UDH network address to the controller. Refer to the ToolboxST User
Guide for Mark VIeS Functional Safety Systems (GEH-6862), the section Configure and Transfer IPAddress to UCSC
Controller for further instructions.
Controllers
GEH-6855_Vol_II System Guide 29
Public Information
The locations and descriptions of the LED indicators that are located on the front panel of the UCSC controller and the UCEC
module are as follows.
30
GEH-6855_Vol_II
GEH-6855_Vol_II Mark VIeS Functional Safety Systems Volume II
Public Information
The UCSC controller uses internal temperature readings and logic to protect its internal electronics. Internal circuitry
generates a warning at 85°C (185 °F) and shuts down at 95°C (203 °F). The UCSC will reboot once the internal circuitry
detects the temperature has dropped below 75°C (167 °F). Independently, the microprocessor monitors its operating
temperature and generates a warning at 105°C (221 °F) and shuts down at 107°C (225 °F). A power cycle is required to
recover from a microprocessor over-temperature shut down. Both of these warnings drive the OT LED and are annunciated as
diagnostic alarms.
2.1.5.4
UCSC COM Port
Typically used by GE to troubleshoot in the field, the UCSC COM port accepts a UCSC COM port adapter and a standard
serial to USB cable is used to connect to another computer. Use Cat5e or better Ethernet cable for this connection. The COM
port can also be used to set the controller’s UDH network address. For these instructions, refer to the ToolboxST User Guide
for Mark VIeS Functional Safety Systems (GEH-6862), the section Configure and Transfer IPAddress to UCSC Controller.
2.1.6
UCSC Embedded Field Agent (EFA)
The Embedded Field Agent (EFA) provides connectivity to GE Predix* cloud-hosted applications and datastores through a
local Predix machine interface that runs within a Linux virtual machine on the UCSCH1. The EFA has two primary functions:
•
Collecting and transmitting machine data securely
•
A platform for running Predix apps on the Edge directly on the machine
Once a Field Agent is up and running, data is transferred from the plant to the cloud over encrypted channels, preserving its
time stamp, quality, and fidelity. It also provides a rich domain application environment for edge processing, so logic can be
executed at the most appropriate place in the architecture — locally on the machine or in the cloud.
Note For more information, refer to the following documentation:
• Field Agents User Guide (GFK-2993)
• Field Agent Secure Deployment Guide (GFK-3009)
• Field Agents Upgrade Guide (GFK-3017)
Controllers
GEH-6855_Vol_II System Guide 31
Public Information
UCSC Virtual Network
The virtual network is a feature of the hypervisor used in UCSCH1 controllers. The virtual network transfers data between the
virtual machines (VMs) in the UCSCH1 controller like an Ethernet network transfers data between physical machines over a
physical network. The virtual network in the UCSCH1 controller is used to transfer data between the Mark VIe control
running in one VM, and the Embedded Field Agent (EFA) running in another VM. The EFA requires a connection to the
Mark VIe control and a connection to the cloud. However, the Mark VIe control must not have a connection to the cloud, so a
physical managed switch must be used to segment the networks. To resolve this issue, data is passed through the virtual
network so the EFA can connect directly to the cloud and eliminate the need of a managed switch.
The virtual network transfers data through memory shared between the VMs instead of the wires of a physical network. The
Mark VIe control uses a network firewall to prevent all other traffic.
Like a physical network, the virtual network must be configured with an IP address and subnet mask. The VMs in the
UCSCH1 controller must be on the same subnet to function properly. The Mark VIe virtual network is configured using the
ToolboxST application. The default configurations for the Mark VIe control and the EFA provide a working virtual network.
However, changing the configuration in one VM may interrupt communication over the virtual network until a corresponding
change is made to the other VM.
Note To configure virtual network adapters, refer to the ToolboxST User Guide for Mark VIeS Functional Safety Systems
(GEH-6862), the section Virtual Network Adapters. To configure the virtual network in the EFA, refer to the Field Agents
User Guide (GFK-2993).
32
GEH-6855_Vol_II
GEH-6855_Vol_II Mark VIeS Functional Safety Systems Volume II
Public Information
Agency Certifications and Standards
Refer to the UCSC Installation and Maintenance Requirements (IMR) (GFK-3006) for conformance to these standards.
Description
Marking
Comments
North America Safety for
Programmable Controller for use in
Hazardous locations
ISA 12.12.01: 2015, Class I Div. 2 Groups ABCD, UL 60079-0 Ed 6.0 (2013), Class I,
Zone 2 Gas Group ABCD, UL 60079-15 Edition 4.0 (2013), [Ex nA]
CSA C22.2 No. 213-15, CAN/CSA-C22.2 NO. 60079-0:15, Class I, Zone 2,
CAN/CSA-C22.2 NO. 60079-15:12
EMC Directive
European Restriction of Hazardous
Substances (RoHS)
IEC/EN 61131-2: 2007(sections 8-10, Zone B),
IEC/EN 61000-6-2: 2005 Ed 2.0,
IEC/EN 61000-6-4: 2006 Ed 2.0,
CISPR 11:2009 +A1: 2010 / EN 55011: 2009 +A1: 2010,
CISPR 22: 2010 / EN55022: 2010/AC:2011 (Class A),
CISPR 24: 2010 / EN55024: 2010,
IEC/EN 61131-2: 2007 (sections 4 & 6),
IEC 61000-4-18: 2006 / EN 61000-4-18: 2007 (refer to IEC61131-2: 2007 Annex D for
levels)
European Safety for Explosive
Atmosphere, ATEX Directive
Category 3 equipment - [II 3 G], EN 60079-0: 2012 A+11:2013, EN 60079-7: 2015 [Type
of Protection Ex ec]
European Waste & Collection
Compliance with European WEEE Directive 2012/19/EU
China Restriction of Hazardous
Substances
Compliance with “Management Methods for the Restriction of the Use of Hazardous
Substances in Electrical and Electronic Products”.
(Jan 21, 2016) Declaration Table provided with equipment.
Environmental
No Marking
IEC/EN 61131-2: 2007 (sections 5 & 6)
Storage: Dry Heat - IEC 60068-2-2: 1974 test Bb (70°C at 16hrs, unpowered), Cold
Temp - IEC 60068-2-1: 2007 test Ab (-40°C at 16hrs, unpowered
Sinusoidal Vibration: DIN EN 60068-2-6: (Edition 10/08) (test Fc)
Shock: DIN EN 60068-2-27: (Edition 2/10) (test Ea)
Controllers
GEH-6855_Vol_II System Guide 33
Public Information
UCSB to UCSC Power Cable Adapter
121T6659P0001
UCSC COM Port Adapter (RJ-45 to DB9F)
34
GEH-6855_Vol_II
GEH-6855_Vol_II Mark VIeS Functional Safety Systems Volume II
Public Information
UCSC Hardware Replacement
Replacement parts may contain static-sensitive components. Therefore, GE ships replacement parts in anti-static bags. When
handling electronics, make sure to store them in anti-static bags or boxes and use a grounding strap.
Caution
To prevent component damage caused by static electricity, treat all boards with
static-sensitive handling techniques. Wear a wrist grounding strap when handling
boards or components, but only after boards or components have been removed from
potentially energized equipment and are at a normally grounded workstation.
Warning
In addition to information provided here, always follow all wiring and safety codes
that apply to your area or your type of equipment. For example, in the United States,
most areas have adopted the National Electrical Code standard and specify that all
wiring conform to its requirements. In other countries, different codes will apply. For
maximum safety to personnel and property you must follow these codes. Failure to do
so can lead to personal injury or death, property damage or destruction, or both.
➢➢
To replace the UCSC with another UCSC
1.
Loosen the screws holding the power connector in place.
2.
Disconnect the power connector from the controller.
3.
Disconnect all Ethernet cables (note which cable is connected to which port).
4.
Loosen the screws holding the controller in place. The mounting is a keyhole design.
5.
Remove the controller by lifting to align the large portion of the keyhole with the mounting screws and pull forward.
6.
Verify that the hardware revision of the old UCSC is the same or compatible with the new UCSC for its particular
application.
7.
Reinstall the new controller by reversing steps 2 through 4. Do not apply power yet.
8.
Perform the UCSC Restore procedure to initialize the new controller.
9.
If restore was not successful, configure the new controller’s UDH network address.
10. Use the ToolboxST application to Build and Download to the controller as needed. Refer to the ToolboxST User Guide
for Mark VIeS Functional Safety Systems (GEH-6862), the section Download to Controller for instructions.
Controllers
GEH-6855_Vol_II System Guide 35
Public Information
After installing a replacement controller, perform the following procedure to apply the configuration to the UCSC controller
and allow communication between the UCSC and the ToolboxST application. The Physical Presence (PHY PRES) button
located on the front of the controller is used to initiate the procedure.
Note The UCSC, as shipped from the factory, does not include the software on the controller to support communication
from the PHY PRES button to the EFA. The user needs to download to the controller at least once (using ToolboxST) to
enable this.
➢➢
To perform UCSC restore
1.
From the ToolboxST Component Editor Device menu, select Download, then select Controller Setup.
2.
When the Controller Setup Wizard Welcome window displays, click Next.
3.
Select Initialize USB Flash Device, then click Next.
4.
Insert a non-encrypted USB 2.0 (only) flash device with a 4 GB minimum capacity into the HMI computer USB port.
5.
Click Scan and select the listed flash drive.
6.
Select the correct Channel (R, S, or T if using redundant controllers).
7.
Click Write, then click Next.
8.
Complete the controller restore process using the instructions provided on the Controller Setup Wizard window or using
the remaining steps in this procedure.
9.
Remove the USB flash device from the HMI computer.
10. Remove power from the controller.
11. Insert the USB flash device into either USB port of the controller.
12. Press and hold in the PHY PRES button, and apply power to the controller. Continue to hold in the PHY PRES button
until the USB On LED is lit (~ 15 seconds).
13. Release the PHY PRES button and wait for the process to complete. (The USB On LED remains lit to indicate the restore
is in progress. The procedure takes one to two minutes.) When the LED turns off, the restore has completed successfully.
Note If the LED flashes at a 1 Hz rate, a failure has occurred. Retry or remove the USB flash device.
14. Remove the USB flash device from the controller.
15. Cycle power on the controller.
16. From the ToolboxST Controller Setup Wizard window, click Finish.
17. Perform a Download to bring the controller back online and in the controlling state.
36
GEH-6855_Vol_II
GEH-6855_Vol_II Mark VIeS Functional Safety Systems Volume II
Public Information
Controller Password Protection
Beginning with controller firmware V06.00.00C, password protection can be applied as a security measure to restrict access
to the controller. The password has an eight-character limit and other requirements. For the instructions to set password
protection, change the password, and other details, refer to the ToolboxST User Guide for Mark VIeS Functional Safety
Systems (GEH-6862), the section System Password Protection for the component.
2.3
Shared IONet
The Shared IONet function (with ControlST V04.06 or higher) enables the sharing of Mark VIeS Safety inputs with another
basic process Mark VIe controller set, saving the cost of redundant sensors and I/O. Refer to the Mark Controllers Shared
IONet User Guide (GEH-6812) for more information.
2.4
Black Channel Safety Communication
Black Channel is a safety communications approach in which the new safety functionality is built over existing protocol
without impact to existing safety applications. The Black Channel feature provides the transfer of Safety control data between
two Mark VIeS Safety control devices without using the standard UDH network, providing a safer, less congested network. A
matching pair of transmitter and receiver blocks, BLACK_TX and BLACK_RX, are configured for the two Mark VIeS Safety
control devices in the application. The data is passed through Ethernet (similar to UDH EGD), and the BLACK_TX and
BLACK_RX blocks run a data integrity check on each respective side of the Black Channel. For more information on these
blocks, refer to the Mark VIeS Safety Control Block Library (GEI-100691), the chapters Black Channel Transmitter (BLACK_
TX) , Black Channel Receiver (BLACK_RX), and Black Channel Example.
Transmitting Device
Receiving Device
App
App
BLACK _TX
Block
BLACK_TX
Block
Vardef
EGD
EGD
EGD
Exchange
EGD
Exchange
Produced
BlackChannel
Page
Consumed
BlackChannel
Page
Transmit
Block
Data
Receive
Block
Data
Var1
Var2
Var3
Var4
Sequence
Number
Connection
ID
Signature
Var1
Var2
Var3
Var4
Sequence
Number
Connection
ID
Exp
Connection
ID
Signature
EGD
Packet
Example Black Channel Configuration
2.5
Controller Setup and Download
After a controller and associated I/O modules have been added to the system, prepare the controller for use by configuring the
IP address and redundancy information using the ToolboxST application. For further instructions and procedures, refer to the
ToolboxST User Guide for Mark VIeS Functional Safety Systems (GEH-6862), the sections Controller Setup and Build and
Download to Controller.
Controllers
GEH-6855_Vol_II System Guide 37
Public Information
Initial Download to I/O Modules
2.6.1
Update Terminal Boards
Prerequisites
•
Successfully online with the associated controller set
•
All I/O modules have been correctly added to the ToolboxST system
•
Correctly connected IONet cables to all the I/O modules
•
I/O modules are powered on
Complete this procedure to detect the terminal board barcodes.
➢➢
To update terminal boards online
1.
If not already online, then from the Component Editor toolbar click the Go On/Offline icon to go online with the
ToolboxST application.
2.
Have available or create a written record of all installed terminal boards.
3.
Enable the I/O modules for configuration.
a.
From the Component Editor Hardware tab, select all the I/O modules.
b.
From the Property Editor, under Configuration, Required, select True.
4.
From the Tree View, double-click the I/O module icon to display the Modify dialog box.
5.
From the Bar Code text box, click the ellipsis button to display the Select Unassigned Terminal Board dialog box
with the available terminal boards.
6.
From the dialog box, select the correct Bar Code and click OK.
7.
Read the warning message, then click Yes.
8.
Click OK.
9.
Repeat this procedure for the remaining I/O modules.
10. Verify using the written record that all terminal boards have been identified by the ToolboxST application.
2.6.2
Initial Download to I/O Modules
➢➢
To perform an initial download
1.
If using Shared IONet, save and close both Component Editors. From the System Editor Tree View, select the Shared
IONet Group. Right-click and select Download Shared IONet, then complete the wizard. Go to step 4.
2.
From the Component Editor, click Build.
3.
Click Download and complete the wizard using the default settings.
4.
Cycle power to the panel. Wait for all equipment to power on with correct status LEDs.
5.
Click to go online.
6.
Wait and reset any alarms, if needed.
7.
Build and Download again, if needed.
8.
Wait and reset any alarms, if needed.
9.
Select the Component InfoView Status tab.
38
GEH-6855_Vol_II
GEH-6855_Vol_II Mark VIeS Functional Safety Systems Volume II
Public Information
The color of the Status tab indicates overall health and equality status of the controller, including its associated I/O hardware.
A major difference in controller equality means that the configuration in the ToolboxST application is different from the
controller configuration.
•
Green indicates that the ToolboxST configuration and the controller configuration are equal.
•
Orange indicates the presence of inequalities or diagnostic warnings.
•
Red indicates that the configuration in the ToolboxST system, which includes base load, firmware, application code,
and I/O module configuration, is significantly different from the component configuration (a Download will correct
this).
Note Refer to GEH-6855_Vol_I, the chapter Troubleshooting for further assistance. For example, if a particular download
fails, this may be fixed by selecting the pack individually from the download wizard and trying again.
Controllers
GEH-6855_Vol_II System Guide 39
Public Information
Controller Diagnostic Alarms
These diagnostic alarms are common among Mark Controls Platforms. However, some alarms are not applicable to all
controller platforms.
0
Description
Diagnostic Alarm Reset
20
Description
ToolboxST application detects unhealthy link or loss of communication between [ ] and controller.
Possible Cause
•
I/O pack configuration files missing
•
I/O pack restarted or did not complete startup
•
I/O pack configured for dual networks, but only one network is connected
•
Network issue preventing connection to ToolboxST application
•
Power failure to the I/O pack
•
Terminal board Bar Code entered incorrectly in ToolboxST configuration
•
Wrong terminal board is configured in ToolboxST application
•
I/O pack or module plugged into wrong jack on terminal board, or wrong jack number in ToolboxST configuration
•
I/O pack configured in ToolboxST application, but configuration not downloaded to the controller
•
I/O pack in program mode
Solution
•
Verify that the Ethernet cables and network switch are operating correctly.
•
Verify that the I/O pack configuration (such as Type, HW Form, Bar Code, position) matches the actual hardware.
•
Manually restart the I/O pack or module.
•
If ToolboxST communication is working correctly, any additional diagnostics should indicate the cause of the problem.
•
Build and download parameters to the I/O pack or module.
•
Download firmware and parameters to the I/O pack or module.
•
Build and download the configuration to the controller, wait for I/O pack communication status to change, then scan and
download to the I/O pack.
Note This alarm is not reported to the WorkstationST Alarm Viewer. This alarm is generated by the ToolboxST application,
not by the firmware.
40
GEH-6855_Vol_II
GEH-6855_Vol_II Mark VIeS Functional Safety Systems Volume II
Public Information
Note This alarm is obsolete.
Description
Control/Status communication failure between [ ] and controller
Possible Cause
•
Asynchronous Drive Language (ADL) communication unhealthy
•
Terminal board barcode typed incorrectly in the ToolboxST configuration
•
Wrong terminal board is configured in the ToolboxST application
•
I/O pack or module plugged into wrong jack on terminal board, or wrong jack number in ToolboxST configuration
•
I/O pack or module is configured in the ToolboxST application, but configuration is not downloaded to the controller
•
I/O pack or module in program mode
Solution
•
Verify that the I/O pack or module configuration (such as Type, HW Form, Bar Code, position) matches the actual
hardware.
•
Perform a build and download the configuration to the controller, wait for pack communication status to change, then
scan and download to the I/O pack or module.
•
Manually restart the I/O pack or module.
22
Description
ToolboxST application detects a diagnostic status signal (...L3DIAG, ATTN, and/or LINK_OK...) is [ ];
therefore, the status signal is inaccurate, unknown, or indeterminate
Possible Cause
•
I/O status signal quality in warning state
•
Signal quality unhealthy, forced, or being simulated
•
Status information inaccurate
Solution
•
Check status signal health.
•
Remove the force or simulated condition applied to the status signal.
Note This alarm is not reported to the WorkstationST Alarm Viewer. This alarm is generated by the ToolboxST application,
not by the firmware.
Controllers
GEH-6855_Vol_II System Guide 41
Public Information
ToolboxST application detects a major difference in [ ] controller application code
Possible Cause
•
Compressing variables, EGD pages, distributed I/O, or NVRAM
•
Changing frame or background period
•
Changing controller or network redundancy
•
Changing controller platform or NTP client mode
•
Changing controller host name or IP address
•
Changing IONet IP address
•
Adding/removing first/last linking device (PFFA), respectively
•
Removing a WCBM module
•
Changing from multicast to broadcast (or vice-versa) I/O communication
•
Adding the first Shared I/O module or connecting the first Controller to Controller I/O variable
•
Removing the last Modbus Slave point
•
Disabling controller web pages
•
Disabling Wind Compress Data Log
•
Disabling Wind Farm Management System
Solution
Rebuild the controller and download.
Note This alarm is not reported to the WorkstationST Alarm Viewer. This alarm is generated by the ToolboxST application,
not by the firmware.
42
GEH-6855_Vol_II
GEH-6855_Vol_II Mark VIeS Functional Safety Systems Volume II
Public Information
ToolboxST application cannot retrieve diagnostics information from I/O pack [ ]
Possible Cause
•
Cannot get requested information from I/O pack or module
•
Communication program failure
•
I/O pack or module unable to retrieve IP address
•
Terminal board Bar Code entered incorrectly in ToolboxST configuration
•
Wrong terminal board configured in ToolboxST application
•
I/O pack or module plugged into wrong jack on terminal board, or wrong jack number in ToolboxST configuration
•
I/O pack or module configured in ToolboxST application, but configuration not downloaded to controller
•
I/O pack or module in program mode
•
I/O pack or module not able to load firmware
•
Power failure to the I/O pack or module
Solution
•
Verify that the I/O pack configuration (such as Type, HW Form, Bar Code, position) matches the actual hardware.
•
Build and download the configuration to the controller, wait for pack communication status to change, then scan and
download to the I/O pack or module.
•
Manually restart the I/O pack or module.
•
Check network cables for proper connection.
•
Verify that the switch is functioning correctly.
Note This alarm is not reported to the WorkstationST Alarm Viewer. This alarm is generated by the ToolboxST application,
not by the firmware.
Controllers
GEH-6855_Vol_II System Guide 43
Public Information
Note This alarm is obsolete.
Description
Control/Status communication Error: [ ]
Possible Cause
•
Cannot get diagnostic information from I/O pack or module
•
I/O pack or module not able to load firmware
Solution
•
Verify that the I/O pack or module configuration is correct.
•
Rebuild the application and download the firmware and application to the I/O pack or module.
•
Check network cables for proper connection.
•
Verify that the switch is functioning correctly.
259
Description
Application Runtime Error - [ ] Frame overruns occurred
Possible Cause
Overloaded processor sequencer malfunction (one or more frame overruns occurred)
Solution
For a controller, perform the following to increase the frame idle time:
•
Reduce the application or increase the EGD period.
•
Upgrade the controller to one with a faster processor.
•
Replace the controller.
For an I/O module, perform the following:
•
From the ToolboxST application, rebuild the system, then download the application and configuration to the I/O module.
•
Replace the I/O module.
44
GEH-6855_Vol_II
GEH-6855_Vol_II Mark VIeS Functional Safety Systems Volume II
Public Information
Application Runtime Error - [ ] Frame skips occurred
Possible Cause
There is an overloaded processor or a processor malfunction. Frame number skips were detected. The
frame number should incrementally increase during Controlling state.
Solution
For a controller, do the following:
•
Reduce the application or increase the EGD period to reduce the processor load.
•
Upgrade the controller to one with a faster processor.
•
Replace the controller.
For an I/O module, do the following:
•
From the ToolboxST application, rebuild the system, then download the application and configuration to the I/O module.
•
Replace the I/O module.
279
Description
Could not determine platform type from hardware
Possible Cause
•
During commissioning/maintenance: Incorrect firmware version or hardware malfunction (firmware could not recognize
host hardware type)
•
During normal operation: Hardware failure
Solution
•
Verify that all connectors are aligned properly and fully seated.
•
Check the firmware version for compatibility with platform. If correct, replace the controller.
Controllers
GEH-6855_Vol_II System Guide 45
Public Information
Platform hardware does not match configuration
Possible Cause
•
During commissioning/maintenance: Platform type identified in the application configuration does not match actual
hardware
•
During normal operation: Hardware failure
Solution
•
Fix the platform type in the ToolboxST application. From the General tab, select General Properties and Platform.
•
Rebuild and download the application.
•
If problem persists, replace the controller.
282
Description
Firmware Load Error - application independent processes failed to initialize
Possible Cause
Runtime malfunction. An application-independent firmware process could not be started successfully.
Solution
•
Reload firmware and application and restart.
•
If controller is a UCSA, try formatting and reloading the flash memory.
•
If I/O pack has diagnostic: try to re-download the base load.
•
Replace the controller or I/O module.
283
Description
Firmware error - Internal process crashed
Possible Cause
Runtime or hardware malfunction (runtime process failed).
Solution
•
Reload firmware and application and restart.
•
If controller is a UCSA, try formatting and reloading the flash memory.
•
If this does not work, replace the controller.
46
GEH-6855_Vol_II
GEH-6855_Vol_II Mark VIeS Functional Safety Systems Volume II
Public Information
Application Error - application overrunning the frame
Possible Cause
Application cannot start within frame.
Solution
Check application loading and reduce the amount of application code or frequency of execution. Build
application and download to all controllers.
294
Description
Controller CPU overtemperature, Temp [ ] °C, Threshold [ ] °C
Possible Cause
•
Excessive ambient temperature
•
Hardware malfunction
•
Fan loss
Solution
•
Check the fan (if applicable), the ambient temperature, and for the presence of dust.
•
Replace the controller.
300
Description
Application Code Load Failure
Possible Cause
During commissioning/maintenance:
•
Invalid application configuration
During normal operation:
•
Firmware or hardware malfunction
Solution
•
Rebuild and download the application to all controllers.
•
Reload firmware and application.
•
If problem persists, replace the controller.
Controllers
GEH-6855_Vol_II System Guide 47
Public Information
Process Alarm Buffers Full - controller can miss alarm transitions
Possible Cause
•
Multiple alarm variables changing state too quickly to transmit all transitions
•
Excessive alarms in queue (Plant-wide system failures)
Solution
During commissioning/maintenance:
•
Reduce the number of alarms that can change state at the same time (filter alarm variables in the application code).
During normal operation:
•
Eliminate the conditions causing excessive process alarms.
321
Description
Internal Runtime error - Process Alarms not being scanned
Possible Cause
Runtime malfunction: alarms not being scanned. Controller may restart on software watchdog timeout
due to processor overload.
Solution
•
Reload firmware and application, and restart.
•
If problem persists, replace the controller.
322
Description
Configuration Load error - Too many consumed EGD variables for Fault Tolerant EGD
Possible Cause
Number of relevant, consumed UDH EGD variables exceeds fault tolerant EGD limitation of 1400 bytes
of data.
Normal UDH EGD operation not affected; however, in the event of UDH EGD failure, some consumed variables may not be
transmitted to redundant controllers over the IONet (if applicable).
Solution
During commissioning/maintenance:
•
Reduce the amount of relevant, consumed UDH EGD data by removing the appropriate number of variables from EGD
pages.
323
Description
EGD Error - Fault Tolerant EGD activated
Possible Cause
EGD exchange timeout occurred on requesting controller. Redundant processor (if applicable) is unable
to receive UDH EGD inputs and requested that EGD data be transferred over the IONet.
Solution
•
Verify that all redundant controllers on the UDH network are receiving all expected EGD exchanges.
•
Verify that all relevant devices are powered on and producing data on the network.
48
GEH-6855_Vol_II
GEH-6855_Vol_II Mark VIeS Functional Safety Systems Volume II
Public Information
EGD Error - Fault Tolerant EGD data requested
Possible Cause
An EGD exchange timeout occurred on the requesting controller. Redundant processor (if applicable)
unable to receive UDH EGD inputs and has requested that EGD data be transferred over the IONet.
Solution
•
Check UDH network and verify that all redundant controllers are receiving all expected EGD exchanges.
•
Verify that all relevant devices are powered on and producing data on the network.
326
Description
Communication lost from R processor
Possible Cause
•
IONet or hardware malfunction
•
S or T processor in redundant system lost communication with R processor
•
Missing cable from the controller to the Unit Data Highway (UDH) network switch
Solution
•
Go online with the R processor. Verify that the processor is in the Controlling state. If not communicating or in
Controlling state, restart the processor.
•
Check for disconnected IONet cables or malfunctioning switches.
•
Rebuild and download the application.
•
Check for a defective Ethernet cable to network switch.
•
Check for a defective network switch:
−
Place the Ethernet cable into empty port.
−
If the problem persists, replace the network switch.
Controllers
GEH-6855_Vol_II System Guide 49
Public Information
Communication lost from S processor
Possible Cause
•
IONet or hardware malfunction
•
R or T processor in redundant system lost communication with S processor
•
Missing cable from the controller to the Unit Data Highway (UDH) network switch
Solution
•
Go online with the S processor. Verify that the processor is in the Controlling state. If not communicating or in
Controlling state, restart the processor.
•
Check for disconnected IONet cables or malfunctioning switches.
•
Rebuild and download the application.
•
Check for a defective Ethernet cable to network switch.
•
Check for a defective network switch:
−
Place the Ethernet cable into empty port.
−
If the problem persists, replace the network switch.
328
Description
Communication lost from T processor
Possible Cause
•
IONet or hardware malfunction
•
R or S processor in redundant system lost communication with T processor
•
Missing cable from the controller to the Unit Data Highway (UDH) network switch
Solution
•
Go online with the T processor. Verify that the processor is in the Controlling state. If not communicating or in
Controlling state, restart the processor.
•
Check for disconnected IONet cables or malfunctioning switches.
•
Rebuild and download the application.
•
Check for a bad Ethernet cable to network switch.
•
Check for a bad network switch:
−
Place the Ethernet cable into empty port.
−
If the problem persists, replace the network switch.
50
GEH-6855_Vol_II
GEH-6855_Vol_II Mark VIeS Functional Safety Systems Volume II
Public Information
Startup sequence failed - Data initialization timeout R processor
Possible Cause
Controller unable to complete startup data initialization
•
IONet malfunction
•
Controllers have different application revisions
•
One or more controllers powered down
•
Controller overloaded by external command messages
Solution
•
Check for disconnected IONet cables or malfunctioning network switches.
•
Rebuild and download the application.
•
Verify that all controllers are powered on.
•
Disable all other command senders (for example, Modbus masters) until controller is online.
330
Description
Startup sequence failed - Data initialization timeout S processor
Possible Cause
Controller is unable to complete startup data initialization.
•
IONet malfunction
•
Controllers have different application revisions
•
One or more controllers are powered down
•
Controller is overloaded by external command messages.
Solution
•
Check for disconnected IONet cables or malfunctioning network switches.
•
Rebuild and download application.
•
Ensure all controllers are powered up.
•
Disable all other command senders (for example, Modbus masters) until controller is online.
Controllers
GEH-6855_Vol_II System Guide 51
Public Information
Startup sequence failed - Data initialization timeout T processor
Possible Cause
Controller is unable to complete startup data initialization.
•
IONet malfunction
•
Controllers have different application revisions
•
One or more controllers are powered down
•
Controller is overloaded by external command messages
Solution
•
Check for disconnected IONet cables or malfunctioning network switches.
•
Rebuild and download application.
•
Ensure all controllers are powered up.
•
Disable all other command senders (for example, Modbus masters) until controller is online.
332
Description
Overtemperature - Controller rebooted and throttled
Possible Cause
•
Excessive ambient temperature
•
Hardware malfunction
•
Fan loss
Solution
•
Check ambient temperature.
•
Check for dust buildup on the cabinet filters, controller, and power supply.
•
Replace the controller.
•
Check fans.
334
Description
Application Error – [ ] Frame Skips Detected
Possible Cause
•
Hardware or IONet malfunction
•
Frame number skips detected. Frame number should monotonically increase until rollover; alarm occurs following a
single frame number skips in successive frames.
Solution
•
Check IONet (switches, cables).
•
Replace the controller.
52
GEH-6855_Vol_II
GEH-6855_Vol_II Mark VIeS Functional Safety Systems Volume II
Public Information
Memory Verification Failed – Firmware Processes
Possible Cause
A modification has occurred in the code segment for one of the processes. This indicates that a hardware
memory failure has occurred.
Solution
Replace the controller.
336
Description
Controller is Unlocked
Possible Cause
•
Leaving Data Init control state and not locked
•
The controller is unlocked through the ToolboxST application.
Solution
From ToolboxST application, lock the controllers before running safety functions.
337
Description
Output exchange disagreement detected
Possible Cause
IONet malfunction or hardware problem. For at least one output, a difference was detected between the
controller outputs. This alarm remains active until the controllers agree on all outputs. A difference for non-Boolean data
generally indicates a deviation of more than 10% from the median value or no IONet EGD configuration is present. For
median values near zero, the variation exceeds integer 2 or real value 0.2.
Solution
•
For the Mark VIe runtime, use the ToolboxST disagreement display (View | Disagreements) to determine which variables
are in disagreement.
•
In the application, avoid use of global variable 'ControllerID' and avoid the use of sequencing block 'USB_HB'.
•
Check IONet (switches, cables); rebuild and download application to all processors. If the problem persists, replace the
processor module.
347
Description
Running Application does not match the Branded Application
Possible Cause
Application not branded or different from branded version.
Note The purpose of branding is to label a verified safety application, and to ensure that it is running.
Solution
•
Reload the branded application to the controller and I/O packs.
•
Use the ToolboxST application to brand the currently running application.
Controllers
GEH-6855_Vol_II System Guide 53
Public Information
Intermittent Communications on IONet1 – Packet Loss Exceeded [ ]%
Possible Cause
•
Power cycled on I/O producer (controller or I/O module)
•
Faulty Ethernet cable from I/O pack to IONet switch and/or from IONet switch to controller.
•
Faulty IONet switch
•
I/O message corruption
•
Communication errors occurred on more than 5% of data transmissions on IONet1
Solution
•
Check for evidence of I/O pack restart (diagnostic alarms, error logs).
•
Replace Ethernet cable(s).
•
Replace the I/O pack.
•
Move the I/O pack’s Ethernet cable into an empty IONet switch port. If problem persists, replace the IONet switch.
349
Description
Intermittent Communications on IONet2 – Packet Loss Exceeded [ ]%
Possible Cause
•
Power cycled on I/O producer (controller or I/O module)
•
Faulty Ethernet cable from I/O pack to IONet switch and/or from IONet switch to controller.
•
Faulty IONet switch
•
I/O message corruption
•
Communication errors occurred on more than 5% of data transmissions on IONet2
Solution
•
Check for evidence of I/O pack restart (diagnostic alarms, error logs).
•
Replace Ethernet cable(s).
•
Replace the I/O pack.
•
Move the I/O pack’s Ethernet cable into an empty IONet switch port. If problem persists, replace the IONet switch.
350
Description
Intermittent Communications on IONet3 – Packet Loss Exceeded [ ]%
Possible Cause
•
Power cycled on I/O producer (controller or I/O module)
•
Faulty Ethernet cable from I/O pack to IONet switch and/or from IONet switch to controller.
•
Faulty IONet switch
•
I/O message corruption
•
Communication errors occurred on more than 5% of data transmissions on IONet3
Solution
•
Check for evidence of I/O pack restart (diagnostic alarms, error logs).
•
Replace Ethernet cable(s).
•
Replace the I/O pack.
•
Move the I/O pack’s Ethernet cable into an empty IONet switch port. If problem persists, replace the IONet switch.
54
GEH-6855_Vol_II
GEH-6855_Vol_II Mark VIeS Functional Safety Systems Volume II
Public Information
Memory Validation Failed – Blockware Data Structures
Possible Cause
A hardware memory failure because application process data was modified (data should not change after
controller goes online)
Solution
Replace the controller.
353
Description
Memory Validation Failed – Configuration Shared Memory
Possible Cause
A hardware memory failure because system process data was modified (data should not change after
controller goes online)
Solution
Replace the controller.
354
Description
Memory Validation Failed – IONet Data Structures
Possible Cause
There is a hardware memory failure because IONet process data was modified (data should not change
after the controller goes online)
Solution
Replace the controller.
355
Description
State Exchange Voter disagreement detected
Possible Cause
•
State Exchange disagreement found
•
Application sequencing error
•
IONet malfunction or hardware problem
Solution
•
Use the ToolboxST disagreement display (View | Disagreements) to determine which variables are in disagreement.
•
In the application, avoid use of global variable 'ControllerID' and avoid the use of 'USB_HB' block.
•
Check IONet (switches, cables). If problem persists, replace the processor module.
356
Description
NANs detected in CALC or NAN_BREAKER block
Possible Cause
•
NaN (Invalid floating point number) received from I/O interface
•
Hardware problem
Solution
•
Check for external devices that may be sending NaNs to the controller.
•
If conditions persists, replace the controller.
Controllers
GEH-6855_Vol_II System Guide 55
Public Information
Internal Runtime error - Sequencer out-of-order or overrun detected
Possible Cause
There is a possible hardware malfunction. Sequencer critical clients were scheduled out of order or were
overrun. This alarm occurs following three successive frames of sequencer critical client out-of-order detections. After five,
the controller is put into the FAILURE control state.
Solution
Replace the controller.
358
Description
Internal Runtime error - Sequencer client execution underrun
Possible Cause
Possible hardware malfunction. Sequencer critical client underrun detected. Alarm occurs after a
sequencer critical client has been run slower than its nominal rate three times in a row; after five, controller put in FAILURE
control state.
Solution
•
Ignore this alarm if it occurs during a restart of the controller.
•
If the alarm occurs during normal operation, then replace the controller.
359
Description
Internal Runtime error - Sequencer client execution overrun
Possible Cause
Possible hardware malfunction. Sequencer critical client overrun detected. Alarm occurs after a
sequencer critical client has been run faster than its nominal rate three times in a row; after five, controller put in FAILURE
control state.
Solution
•
Ignore alarm if it occurs during a restart of the controller.
•
Replace the controller, if the alarm occurs during normal operation.
360
Description
Internal Runtime error - Sequencer frame period out-of-bounds (±15%)
Possible Cause
Possible hardware malfunction. Frame period greater than ±15% of nominal. Alarm occurs following
frame period out-of-bounds condition occurring three frames in a row; after five, controller put in FAILURE control state.
Solution
•
Ignore alarm if it occurs during a restart of the controller.
•
Replace the controller, if the alarm occurs during normal operation.
56
GEH-6855_Vol_II
GEH-6855_Vol_II Mark VIeS Functional Safety Systems Volume II
Public Information
Internal Runtime error - Sequencer frame state timeout out-of-bounds (±15%)
Possible Cause
Possible hardware malfunction. Sequencer frame state timeout greater than ±15% of nominal. Alarm
occurs following a sequencer frame state timeout being out-of-bounds three frames in row; after five, controller put in
FAILURE control state.
Solution
•
Ignore alarm if it occurs during a restart of the controller.
•
Replace the controller, if the alarm occurs during normal operation.
362
Description
Internal Runtime error - Sequencer frame number skip detected
Possible Cause
Possible hardware or IONet malfunction. Frame number skips detected. Frame number should
monotonically increase until rollover; alarm occurs following three skips in a row, after five, controller put in FAILURE
control state.
Solution
•
Ignore this alarm if it occurs during a restart of the controller.
During normal operation:
•
Check for hardware or network switch malfunction.
•
Check for loose or defective network cables.
•
Replace the controller.
363
Description
Memory Validation failed - Sequencer data structures
Possible Cause
Hardware memory failure. Sequencer process data was modified (data should not change after the
controller is online).
Solution
Replace the controller.
364
Description
Too many state voter disagreements detected
Possible Cause
•
State exchange voter disagreement overflow. System exceeded the limit of 128 simultaneous disagreements at once.
•
Application error
•
Hardware problem or IONet malfunction
Solution
•
Use the ToolboxST disagreement display (View | Disagreements) to determine which variables are in disagreement.
•
In the application, avoid use of global variable 'ControllerID' and avoid the use of 'USB_HB' block.
•
Check IONet (switches, cables).
•
If problem persists, replace the controller.
Controllers
GEH-6855_Vol_II System Guide 57
Public Information
Invalid Calibration Settings
Possible Cause
•
Calibration file not detected
•
Calibration file corrupted
•
Calibration constants invalid
•
Hardware Failure
Solution
Replace the module.
375
Description
Controller has entered Quality Control (QC) Mode
Possible Cause
The device has received a command to enter factory QC mode.
Solution
Reboot the device.
462
Description
Hardware Reconfigured: Reboot by removing and reapplying power
Possible Cause
Flash memory file system corruption.
Solution
•
After reapplying power, Rebuild and download baseload, firmware and application.
•
If the problem persists, replace the controller.
463
Description
Internal runtime error - Could not create the Command and Event Log (CEL) file
Possible Cause
Internal runtime error. Could not create the CEL file.
Solution
•
Rebuild and download baseload, firmware, and application to the controller.
•
If the problem persists, replace the controller.
464
Description
Ethernet Interface [ ] disabled due to excessive traffic
Possible Cause
Network interface has been disabled to protect itself from excessive activity on the network.
Solution
•
Check for network loops.
•
Monitor network activity and remove excessive traffic.
58
GEH-6855_Vol_II
GEH-6855_Vol_II Mark VIeS Functional Safety Systems Volume II
Public Information
Ethernet Interface [ ] disabled due to excessive traffic
Possible Cause
Network interface has been disabled to protect itself from excessive activity on the network
Solution
•
Check for network loops.
•
Monitor network activity and remove excessive traffic.
466
Description
Ethernet Interface [ ] disabled due to excessive traffic
Possible Cause
Network interface has been disabled to protect itself from excessive activity on the network
Solution
•
Check for network loops.
•
Monitor network activity and remove excessive traffic.
467
Description
Ethernet Interface [ ] disabled due to excessive traffic
Possible Cause
Network interface has been disabled to protect itself from excessive activity on the network.
Solution
•
Check for network loops.
•
Monitor network activity and remove excessive traffic.
468
Description
Ethernet Interface [ ] disabled due to excessive traffic
Possible Cause
Network interface has been disabled to protect itself from excessive activity on the network.
Solution
•
Check for network loops.
•
Monitor network activity and remove excessive traffic.
Controllers
GEH-6855_Vol_II System Guide 59
Public Information
UDH EGD fault detected by the R processor
Possible Cause
•
UDH EGD producer is powered down
•
Producer is unhealthy
•
Ethernet connection(s) failure
Solution
•
Ensure all EGD producers are powered on and healthy.
•
Check for a defective Ethernet cable from producer to network switch. Replace the cable(s).
•
Check for a defective network switch by placing the producer's Ethernet cable into an empty port. If the problem persists,
replace the network switch.
•
Replace the processor module.
470
Description
UDH EGD fault detected by the S processor
Possible Cause
•
UDH EGD producer is powered down
•
Producer is unhealthy
•
Ethernet connection(s) failure
Solution
•
Ensure all EGD producers are powered up and healthy.
•
Check for a defective Ethernet cable from producer to network switch. Replace the cable(s).
•
Check for a defective network switch by placing the producer's Ethernet cable into an empty port. If the problem persists,
replace the network switch.
•
Replace the producer processor module.
471
Description
UDH EGD fault detected by the T processor
Possible Cause
•
UDH EGD producer is powered down
•
Producer is unhealthy
•
Ethernet connection(s) failure
Solution
•
Ensure all EGD producers are powered up and healthy.
•
Check for a defective Ethernet cable from producer to network switch. Replace the cable(s).
•
Check for a defective network switch by placing the producer's Ethernet cable into an empty port. If the problem persists,
replace the network switch.
•
Replace the producer processor module.
60
GEH-6855_Vol_II
GEH-6855_Vol_II Mark VIeS Functional Safety Systems Volume II
Public Information
Auto-Reconfiguration server installation is incomplete
Possible Cause
•
A download from the ToolboxST application to an I/O pack and/or the Auto-Reconfiguration server has failed
•
Not all of the I/O packs were selected for download
Solution
Perform a scan and download using the ToolboxST application.
487
Description
Auto-Reconfiguration server failed scanning or downloading an I/O pack
Possible Cause
At least one I/O pack is in an unexpected state that the Auto-Reconfiguration server is unable to handle
Solution
•
Cycle power on the I/O pack.
•
Perform a scan and download using the ToolboxST application.
•
Replace the I/O pack.
488
Description
EGD Error - Could not configure consumed exchanges from one or more Producers
Possible Cause
•
Producer EGD Page(s) configured incorrectly
•
Producer(s) powered down
•
Network connectivity intermittent or severed
•
Internal Firmware failure
Solution
•
Rectify configuration error. Compress all pages and download application to Producer.
•
Ensure each Producer is powered on and in the Controlling state.
•
Refer to the Network Troubleshooting guide for possible solutions.
•
Replace the Consumer and/or Producer hardware.
Controllers
GEH-6855_Vol_II System Guide 61
Public Information
EGD Error - One or more consumed exchanges contain unbound variables
Possible Cause
•
An EGD variable has been removed from a Producer's EGD configuration
•
An EGD variable has been added to a different Producer's EGD Page from its original EGD Page
Solution
•
Add the offending variable to the Producer's EGD configuration, compress the Page and download the application to the
Producer.
•
Remove the reference to the offending variable from the Consumer's application code; build and download application to
the Consumer.
•
Compress the EGD Page in the Producer where the variable has been added; build and download the application to the
Producer.
490
Description
Software watchdog has been disabled
Possible Cause
•
A runtime malfunction has disabled the software watchdog protective function
•
An invalid version of firmware has been downloaded
Solution
•
Reload base load, firmware, and application and restart.
•
If using a UCSA, reformat the flash and reload the firmware.
•
I/O pack or module: re-download the base load.
•
If this does not work, replace the controller or I/O module.
491
Description
Hardware watchdog has been disabled
Possible Cause
•
A runtime malfunction has disabled the hardware watchdog protective function
•
A hardware failure has disabled the hardware watchdog protective function
Solution
•
Reload firmware and restart.
•
If problem persists, replace hardware.
62
GEH-6855_Vol_II
GEH-6855_Vol_II Mark VIeS Functional Safety Systems Volume II
Public Information
CDH EGD fault detected by the R processor
Possible Cause
•
CDH EGD producer is powered down
•
Producer is unhealthy
•
Ethernet connection(s) failure
Solution
•
Ensure all EGD producers are powered up and healthy.
•
Check for a defective Ethernet cable from producer to network switch. Replace the cable(s).
•
Check for a defective network switch by placing the producer's Ethernet cable into an empty port. If the problem persists,
replace the network switch.
•
Replace the producer processor module.
494
Description
CDH EGD fault detected by the S processor
Possible Cause
•
CDH EGD producer is powered down
•
Producer is unhealthy
•
Ethernet connection(s) failure
Solution
•
Ensure all EGD producers are powered up and healthy.
•
Check for a defective Ethernet cable from producer to network switch. Replace the cable(s).
•
Check for a defective network switch by placing the producer's Ethernet cable into an empty port. If the problem persists,
replace the network switch.
•
Replace the producer processor module.
Controllers
GEH-6855_Vol_II System Guide 63
Public Information
CDH EGD fault detected by the T processor
Possible Cause
•
CDH EGD producer is powered down
•
Producer is unhealthy
•
Ethernet connection(s) failure
Solution
•
Ensure all EGD producers are powered up and healthy.
•
Check for a defective Ethernet cable from producer to network switch. Replace the cable(s).
•
Check for a defective network switch by placing the producer's Ethernet cable into an empty port. If the problem persists,
replace the network switch.
•
Replace the producer processor module.
496
Description
Failed to incorporate the user-configured frame state timeouts
Possible Cause
•
Invalid user-configured frame state timeout values
•
Failed to parse the user-configured frame state timeouts file
Solution
•
Timeout values configured by the user must satisfy the condition
Frame Rate > Output Timeout > App Timeout > Input Timeout > 0.
•
Rebuild the application and force an offline download of the application to the controller.
497-498
Description
Fan loss detected for controller fan [ ]
Possible Cause
•
Hardware malfunction
•
Fan power not applied
Solution
•
Check the fan.
•
Verify that the power connector is properly inserted.
•
Replace the fan.
64
GEH-6855_Vol_II
GEH-6855_Vol_II Mark VIeS Functional Safety Systems Volume II
Public Information
Total memory consumption has exceeded [ ] percent
Possible Cause
Memory usage is driven from three functions:
•
The online download procedure temporarily stores the previous and new application configuration in memory.
•
The footprint of the application configuration/code has been enlarged.
•
Memory usage can grow over time if there is a memory leak.
Solution
•
The alarm should return to normal state after download is complete.
•
Reduce the content of the application configuration/code.
•
To address a memory leak, reboot the device to reinitialize baseline memory use. Monitor for reoccurrence and contact
your GE representative.
502
Description
Syspage inconsistency detected
Possible Cause
Memory corruption
Solution
Restart the controller to re-initialize QNX syspage.
503
Description
Communications timeout with Remote System Log Server
Possible Cause
•
Remote Syslog server not in network
•
Remote Syslog server down
•
Incorrect Remote Syslog server IP address in system configuration
•
Network issue (cables/switch) connecting controller to Remote Syslog server
Solution
•
Verify that the Remote Syslog server is in operation.
•
Verify that the correct Remote Syslog server IP address in the system configuration.
•
Check the network connections.
Controllers
GEH-6855_Vol_II System Guide 65
Public Information
Unauthorized executable was detected and terminated
Possible Cause
When in Secure mode, the controller only permits authorized executables. An unauthorized executable
has been detected and dismissed.
Solution
•
Inspect the syslog/error log messages
•
Rebuild and download the baseload, firmware, and application to the controller.
•
Re-install the ControlST application, then rebuild and download the baseload, firmware, and application to the controller.
505
Description
R network shared I/O module inputs unhealthy
Possible Cause
•
I/O module restarting or restarted
•
I/O module application/configuration missing
•
Application/configuration does not match in I/O module and controller
•
Failed Ethernet connection between I/O module and controller
•
Ethernet cable inserted into wrong connector on I/O module
Note When using the Shared IONet feature, this alarm is generated if there is a problem with receiving inputs from any
shared I/O module on the R IONet. Refer to Mark Controllers Shared IONet User Guide (GEH-6812).
Solution
•
Rebuild and download application/parameters to all controllers and I/O modules.
•
Reload firmware and parameters to the affected I/O module.
•
Reload firmware and application to all controllers.
•
If the problem persists, replace the affected I/O module, then replace the controller.
66
GEH-6855_Vol_II
GEH-6855_Vol_II Mark VIeS Functional Safety Systems Volume II
Public Information
S network shared I/O module inputs unhealthy
Possible Cause
•
I/O module restarting or restarted
•
I/O module application/configuration missing
•
Application/configuration does not match in I/O module and controller
•
Failed Ethernet connection between I/O module and controller
•
Ethernet cable inserted into wrong connector on I/O module
Note When using the Shared IONet feature, this alarm is generated if there is a problem with receiving inputs from any
shared I/O module on the S IONet. Refer to Mark Controllers Shared IONet User Guide (GEH-6812).
Solution
•
Rebuild and download application/parameters to all controllers and I/O modules.
•
Reload firmware and parameters to the affected I/O module.
•
Reload firmware and application to all controllers.
•
If the problem persists, replace the affected I/O module, then replace the controller.
507
Description
T network shared I/O module inputs unhealthy
Possible Cause
•
I/O module restarting or restarted
•
I/O module application/configuration missing
•
Application/configuration does not match in I/O module and controller
•
Failed Ethernet connection between I/O module and controller
•
Ethernet cable inserted into wrong connector on I/O module
Note When using the Shared IONet feature, this alarm is generated if there is a problem with receiving inputs from any
shared I/O module on the T IONet. Refer to Mark Controllers Shared IONet User Guide (GEH-6812).
Solution
•
Rebuild and download application/parameters to all controllers and I/O modules.
•
Reload firmware and parameters to the affected I/O module.
•
Reload firmware and application to all controllers.
•
If the problem persists, replace the affected I/O module, then replace the controller.
Controllers
GEH-6855_Vol_II System Guide 67
Public Information
Application mismatch between redundant controllers
Possible Cause
•
One processor installed new application code while the other processor(s) did not
•
Processor was replaced and application code was built with a different version of the ToolboxST application
Solution
•
Rebuild and download the application code to all controllers.
•
Verify that the Application Code checkbox is selected in the download wizard for all controllers prior to downloading.
509
Description
Controller certificate has been revoked
Possible Cause
•
Controller certificate is in the Certificate Revocation List (CRL)
•
Certificate Authority (CA) Administrator revoked the certificate
Solution
•
Transition the controller from Secure to Open state then back to Secure to generate a new certificate and private key.
•
Contact the Certificate Authority (CA) Administrator.
510
Description
Controller certificate will expire within 30 days
Possible Cause
Controller certificate will expire within 30 days
Solution
•
Transition the controller from Secure to Open state then back to Secure to generate a new certificate and private key.
•
Contact the Certificate Authority (CA) Administrator.
68
GEH-6855_Vol_II
GEH-6855_Vol_II Mark VIeS Functional Safety Systems Volume II
Public Information
Controller certificate will expire within seven days
Possible Cause
Controller certificate will expire within seven days
Solution
•
Transition the controller from Secure to Open state then back to Secure to generate a new certificate and private key.
•
Contact the Certificate Authority (CA) Administrator.
512
Description
Controller certificate will expire in one day
Possible Cause
Controller certificate will expire in one day
Solution
•
Transition the controller from Secure to Open state then back to Secure to generate a new certificate and private key.
•
Contact the Certificate Authority (CA) Administrator.
513
Description
Controller certificate has expired; controller is no longer in Secure state
Possible Cause
•
Controller is not in Secure state
•
Controller certificate has expired
Solution
•
Place the controller in the Secure state.
•
Contact the Certificate Authority (CA) Administrator.
Controllers
GEH-6855_Vol_II System Guide 69
Public Information
Controller To Controller (C2C) Inputs Unhealthy on IONet [ ] from ControlSet [ ]
Possible Cause
•
Failed Ethernet connection between controllers
•
Ethernet cable is inserted into the wrong connector on the IONet switch
•
Controller to Controller (C2C) packet production is restarting or not occurring
•
Application or configuration is missing in the controller or does not match in both controllers
Note A control set is a controller in a Shared IONet group. There are 24 Controller to Controller (C2C) diagnostic alarms
assigned for eight control sets. Each control set contains three diagnostics for its IONets.
Solution
•
Check for Ethernet connectivity between the controllers.
•
Rebuild and download the application to all controllers.
•
Reload the firmware and application to all controllers.
•
If the problem persists, replace the affected switch and Ethernet cables, then replace the controller.
538
Description
Certificate Authority (CA) certificate will expire within 30 days
Possible Cause
CA certificate will expire within 30 days
Solution
Contact the CA Administrator.
539
Description
Certificate Authority (CA) certificate will expire within seven days
Possible Cause
CA certificate will expire within seven days
Solution
Contact the CA Administrator.
540
Description
Certificate Authority (CA) certificate will expire within one day
Possible Cause
CA certificate will expire within one day
Solution
Contact the CA Administrator.
70
GEH-6855_Vol_II
GEH-6855_Vol_II Mark VIeS Functional Safety Systems Volume II
Public Information
Certificate Authority (CA) certificate has expired; controller is no longer in Secure state
Possible Cause
CA certificate has expired
Solution
Contact the CA Administrator.
542
Description
Certificate Revocation List (CRL) has expired
Possible Cause
CRL has expired
Solution
1.
Contact the CA Administrator and request/confirm the renewal of the CRL.
2.
After the CRL is renewed, from the Mark VIe Device menu select View | Diagnostics | Controller Advanced Diagnostics.
3.
Expand the Commands tree, expand the Diagnostics tree, and double-click Get CRL for controller from CA
Server.
4.
Confirm the reply, CRL received successfully, which indicates that the Mark VIe to CA Server connection is healthy.
5.
Close the Advanced Diagnostics Commands window.
543
Description
Total memory consumption has exceeded [ ] percent
Possible Cause
•
Memory leak
•
Application code is too large
Solution
•
Decrease memory usage.
•
Restart the controller.
544
Description
Communications error with Certificate Authority Server
Possible Cause
•
Certificate Authority (CA) server not in network or not in operation (server is down)
•
Incorrect CA server IP address in system configuration
•
Network issue (cables/switch) connecting controller to CA server
Solution
•
Verify that the CA server is in operation.
•
Verify that the CA server IP address is correct in the system configuration.
•
Check the network connections.
Controllers
GEH-6855_Vol_II System Guide 71
Public Information
Active PFFA diagnostics detected
Possible Cause
At least one configured PFFA module contains an active diagnostic. Since each controller within a
control set monitors the diagnostic conditions of PFFA modules and connected Fieldbus devices, PFFA diagnostics may differ
between the individual controllers.
Solution
•
If there are active PFFA diagnostics in the WorkstationST Alarm Viewer, correct those issues.
•
If there are no active PFFA diagnostics in the Alarm Viewer, go online specifically to the controller with this 545
diagnostic using the ToolboxST application. From the Component Editor Hardware tab, select the PFFA with active
diagnostics, and correct the identified issues.
546
Description
This component is or has been in factory test mode.
Possible Cause
The controller or I/O pack has received the command to enter factory test mode.
Solution
Reboot the I/O pack or controller.
547
Description
Default user password detected
Possible Cause
The controller password is the default value.
Solution
From the ToolboxST application, set the password.
Note It is the user’s responsibility to change the default password to a unique password. If you do not know the default
password, contact the nearest GE Sales or Service Office, or an authorized GE Sales Representative.
To change the controller password, refer to the ToolboxST User Guide for Mark VIeS Functional Safety Systems (GEH-6862),
the section Controller Password Change.
72
GEH-6855_Vol_II
GEH-6855_Vol_II Mark VIeS Functional Safety Systems Volume II
Public Information
Inputs unhealthy on IO Module [ ], R pack IONet [ ] - Message Timeout
Possible Cause
•
I/O pack restarting or restarted
•
I/O pack application/configuration is missing
•
Application/configuration does not match in the I/O pack and controller
•
Failed Ethernet connection between I/O pack and controller
•
Ethernet cable inserted into wrong connector on I/O pack
Solution
•
Reset all diagnostic alarms.
•
Rebuild and download application to all controllers and I/O packs.
•
Reload firmware and application.
•
Verify that Ethernet cable on I/O pack matches the ToolboxST configuration.
•
Check for faulty Ethernet cable from pack to network switch and/or from switch to controller. Replace cable(s) if
necessary.
•
Replace the I/O pack.
•
Defective network switch, place I/O pack's Ethernet cable into empty port. If problem persists, replace network switch.
Controllers
GEH-6855_Vol_II System Guide 73
Public Information
Inputs unhealthy on IO Module [ ], S pack IONet [ ] - Message Timeout
Possible Cause
•
I/O pack restarting or restarted
•
I/O pack application/configuration is missing
•
Application/configuration does not match in the I/O pack and controller
•
Failed Ethernet connection between I/O pack and controller
•
Ethernet cable inserted into wrong connector on I/O pack
Solution
•
Reset all diagnostic alarms.
•
Rebuild and download application to all controllers and I/O packs.
•
Reload firmware and application.
•
Verify that Ethernet cable on I/O pack matches the ToolboxST configuration.
•
Check for faulty Ethernet cable from I/O pack to network switch and/or from switch to controller. Replace cable(s) if
necessary.
•
Replace the I/O pack.
•
Defective network switch, place I/O pack's Ethernet cable into empty port. If problem persists, replace network switch.
1000-2024
Description
Inputs unhealthy on IO Module [ ], T pack IONet [ ] - Message Timeout
Possible Cause
•
Pack restarting or restarted
•
I/O pack application/configuration is missing
•
Application/configuration does not match in the I/O pack and controller
•
Failed Ethernet connection between I/O pack and controller
•
Ethernet cable inserted into wrong connector on I/O pack
Solution
•
Reset all diagnostic alarms.
•
Rebuild and download application to all controllers and I/O packs.
•
Reload firmware and application.
•
Verify that Ethernet cable on I/O pack matches the ToolboxST configuration.
•
Check for faulty Ethernet cable from I/O pack to network switch and/or from switch to controller. Replace cable(s) if
necessary.
•
Replace the I/O pack.
•
Defective network switch, place I/O pack's Ethernet cable into empty port. If problem persists, replace network switch.
74
GEH-6855_Vol_II
GEH-6855_Vol_II Mark VIeS Functional Safety Systems Volume II
Public Information
Inputs unhealthy on IO Module [ ], IONet [ ] - Message Timeout
Possible Cause
•
I/O pack restarting or restarted
•
I/O pack application/configuration is missing
•
Application/configuration does not match in the I/O pack and controller
•
Failed Ethernet connection between I/O pack and controller
•
Ethernet cable inserted into wrong connector on I/O pack
Solution
•
Reset all diagnostic alarms.
•
Rebuild and download application to all controllers and I/O packs.
•
Reload firmware and application.
•
Verify that Ethernet cable on I/O pack matches the ToolboxST configuration.
•
Check for faulty Ethernet cable from I/O pack to network switch and/or from switch to controller. Replace cable(s) if
necessary.
•
Replace the I/O pack.
•
Defective network switch, place I/O pack's Ethernet cable into empty port. If problem persists, replace network switch.
1000-2024
Description
Inputs unhealthy on IO Module [ ], R pack IONet [ ] - Message Length not valid
Possible Cause
Application/configuration does not match in the I/O pack and controller.
Solution
•
Rebuild and download application/parameters to all controllers and I/O packs.
•
Reload firmware and parameters to the affected I/O pack.
•
Reload firmware and application to all controllers.
•
If problem persists, replace affected I/O pack, then replace controller.
1000-2024
Description
Inputs unhealthy on IO Module [ ], S pack IONet [ ] - Message Length not valid
Possible Cause
Application/configuration does not match in the I/O pack and controller.
Solution
•
Rebuild and download application/parameters to all controllers and I/O packs.
•
Reload firmware and parameters to the affected I/O pack.
•
Reload firmware and application to all controllers.
•
If problem persists, replace affected I/O pack, then replace controller.
Controllers
GEH-6855_Vol_II System Guide 75
Public Information
Inputs unhealthy on IO Module [ ], T pack IONet [ ] - Message Length not valid
Possible Cause
Application/configuration does not match in the I/O pack and controller.
Solution
•
Rebuild and download application/parameters to all controllers and I/O packs.
•
Reload firmware and parameters to the affected I/O pack.
•
Reload firmware and application to all controllers.
•
If problem persists, replace affected I/O pack, then replace controller.
1000-2024
Description
Inputs unhealthy on IO Module [ ], IONet [ ] - Message Length not valid
Possible Cause
Application/configuration does not match in the I/O pack and controller.
Solution
•
Rebuild and download application/parameters to all controllers and I/O packs.
•
Reload firmware and parameters to the affected I/O pack.
•
Reload firmware and application to all controllers.
•
If problem persists, replace affected I/O pack, then replace controller.
1000-2024
Description
Inputs unhealthy on IO Module [ ], R Pack IONet [ ] - Major Signature Mismatch
Possible Cause
Application/configuration does not match in the I/O pack and controller.
Solution
•
Rebuild and download application/parameters to all controllers and I/O packs.
•
Reload firmware and parameters to the affected I/O pack.
•
Reload firmware and application to all controllers.
•
If problem persists, replace affected I/O pack, then replace controller.
76
GEH-6855_Vol_II
GEH-6855_Vol_II Mark VIeS Functional Safety Systems Volume II
Public Information
Inputs unhealthy on IO Module [ ], S Pack IONet [ ] - Major Signature Mismatch
Possible Cause
Application/configuration does not match in the I/O pack and controller.
Solution
•
Rebuild and download application/parameters to all controllers and I/O packs.
•
Reload firmware and parameters to the affected I/O pack.
•
Reload firmware and application to all controllers.
•
If problem persists, replace affected I/O pack, then replace controller.
1000-2024
Description
Inputs unhealthy on IO Module [ ], T Pack IONet [ ] - Major Signature Mismatch
Possible Cause
Application/configuration does not match in the I/O pack and controller.
Solution
•
Rebuild and download application/parameters to all controllers and I/O packs.
•
Reload firmware and parameters to the affected I/O pack.
•
Reload firmware and application to all controllers.
•
If problem persists, replace affected I/O pack, then replace controller.
1000-2024
Description
Inputs unhealthy on IO Module [ ] IONet [ ] - Major Signature Mismatch
Possible Cause
Application/configuration does not match in the I/O pack and controller.
Solution
•
Rebuild and download application/parameters to all controllers and I/O packs.
•
Reload firmware and parameters to the affected I/O pack.
•
Reload firmware and application to all controllers.
•
If problem persists, replace affected I/O pack, then replace controller.
Controllers
GEH-6855_Vol_II System Guide 77
Public Information
Inputs unhealthy on IO Module [ ], R Pack IONet [ ] - Minor Signature Mismatch
Possible Cause
Application/configuration does not match in the I/O pack and controller.
Solution
•
Rebuild and download application/parameters to all controllers and I/O packs.
•
Reload firmware and parameters to the affected I/O pack.
•
Reload firmware and application to all controllers.
•
If problem persists, replace affected I/O pack, then replace controller.
1000-2024
Description
Inputs unhealthy on IO Module [ ], S Pack IONet [ ] - Minor Signature Mismatch
Possible Cause
Application/configuration does not match in the I/O pack and controller.
Solution
•
Rebuild and download application/parameters to all controllers and I/O packs.
•
Reload firmware and parameters to the affected I/O pack.
•
Reload firmware and application to all controllers.
•
If problem persists, replace affected I/O pack, then replace controller.
1000-2024
Description
Inputs unhealthy on IO Module [ ], T Pack IONet [ ] - Minor Signature Mismatch
Possible Cause
Application/configuration does not match in the I/O pack and controller.
Solution
•
Rebuild and download application/parameters to all controllers and I/O packs.
•
Reload firmware and parameters to the affected I/O pack.
•
Reload firmware and application to all controllers.
•
If problem persists, replace affected I/O pack, then replace controller.
78
GEH-6855_Vol_II
GEH-6855_Vol_II Mark VIeS Functional Safety Systems Volume II
Public Information
Inputs unhealthy on IO Module [ ] IONet [ ] - Minor Signature Mismatch
Possible Cause
Application/configuration does not match in the I/O pack and controller.
Solution
•
Rebuild and download application/parameters to all controllers and I/O packs.
•
Reload firmware and parameters to the affected I/O pack.
•
Reload firmware and application to all controllers.
•
If problem persists, replace affected I/O pack, then replace controller.
1000-2024
Description
Inputs unhealthy on IO Module [ ], R Pack IONet [ ] - Timestamp Mismatch
Possible Cause
Application/configuration does not match in the I/O pack and controller.
Solution
•
Rebuild and download application/parameters to all controllers and I/O packs.
•
Reload firmware and parameters to the affected I/O pack.
•
Reload firmware and application to all controllers.
•
If problem persists, replace affected I/O pack, then replace controller.
1000-2024
Description
Inputs unhealthy on IO Module [ ], S Pack IONet [ ] - Timestamp Mismatch
Possible Cause
Application/configuration does not match in the I/O pack and controller.
Solution
•
Rebuild and download application/parameters to all controllers and I/O packs.
•
Reload firmware and parameters to the affected I/O pack.
•
Reload firmware and application to all controllers.
•
If problem persists, replace affected I/O pack, then replace controller.
Controllers
GEH-6855_Vol_II System Guide 79
Public Information
Inputs unhealthy on IO Module [ ], T Pack IONet [ ] - Timestamp Mismatch
Possible Cause
Application/configuration does not match in the I/O pack and controller.
Solution
•
Rebuild and download application/parameters to all controllers and I/O packs.
•
Reload firmware and parameters to the affected I/O pack.
•
Reload firmware and application to all controllers.
•
If problem persists, Immediate Attention Required: Fieldbus I/O Module [ ] Not Detected on IoNet [ ]ts, replace affected
I/O pack, then replace controller.
1000-2024
Description
Inputs unhealthy on IO Module [ ] IONet [ ] - Timestamp Mismatch
Possible Cause
Application/configuration does not match in the I/O pack and controller.
Solution
•
Rebuild and download application/parameters to all controllers and I/O packs.
•
Reload firmware and parameters to the affected I/O pack.
•
Reload firmware and application to all controllers.
•
If problem persists, replace affected I/O pack, then replace controller.
1000-2024
Description
Inputs unhealthy on IO Module [ ] IONet [ ] - Message Timeout
Possible Cause
Application/configuration does not match in the I/O pack and controller.
Solution
•
Rebuild and download application/parameters to all controllers and I/O packs.
•
Reload firmware and parameters to the affected I/O pack.
•
Reload firmware and application to all controllers.
•
If problem persists, replace affected I/O pack, then replace controller.
80
GEH-6855_Vol_II
GEH-6855_Vol_II Mark VIeS Functional Safety Systems Volume II
Public Information
Immediate Attention Required: Fieldbus I/O Module [ ] Not Detected on IoNet [ ]
Possible Cause
Note: If this diagnostic is active, the module needs to be replaced immediately. If it is simplex, the
devices under this PFFA have lost communication. If it is redundant and not replaced, and a controller on the remaining
module's IONet goes down, then control is lost for all devices under the PFFA modules.
•
PFFA module did not complete Start
•
PFFA module configuration files missing
•
PFFA module restarted
•
PFFA module configured for Hot Backup, but only one network is connected
•
Serial connection between PFFA modules is broken
•
Network issue
Solution
•
If the Control/Status communication is working correctly, any additional diagnostics should indicate the cause of the
problem.
•
Build and download parameters to the PFFA module and controller.
•
Verify Serial cable is attached correctly.
•
Verify that the Ethernet cables and network switch are operating correctly.
•
Manually restart the PFFA module.
2400
Description
EtherCAT scan bus error
Possible Cause
•
EtherCAT device(s) is unplugged or without power
•
An Ethernet cable is disconnected or damaged
•
Redundancy mode is not set correctly
•
Redundant Ring is broken
Solution
•
Ensure all devices are connected and powered.
•
Verify all Ethernet LINK lights are lit.
•
Verify redundant configuration is correct.
2401
Description
EtherCAT All Ethernet links disconnected
Possible Cause
•
Ethernet LINK between Mark VIe controller and EtherCAT network is lost
•
EtherCAT device(s) are unplugged or without power
Solution
•
Reconnect Ethernet cables.
•
Verify all Ethernet LINK lights are lit.
•
Verify all EtherCAT devices are powered.
Controllers
GEH-6855_Vol_II System Guide 81
Public Information
EtherCAT linebreak detected between devices [ ] and [ ]
Possible Cause
•
An Ethernet cable is disconnected or damaged
•
EtherCAT device(s) is unplugged or without power
Solution
•
Reconnect Ethernet cables.
•
Verify all Ethernet LINK lights are lit.
•
Verify all EtherCAT devices are powered.
2404
Description
EtherCAT limit for lost frames has been exceeded
Possible Cause
•
A device or network component is corrupting the EtherCAT frame
•
An Ethernet cable is damaged
Solution
Use Controller Advanced Diagnostic tool to determine where network issues are located in the device topology.
2405
Description
EtherCAT device disconnected
Possible Cause
•
EtherCAT device(s) is unplugged or without power
•
An Ethernet cable is disconnected or damaged
Solution
•
Ensure all devices are connected and powered.
•
Verify all Ethernet LINK lights are lit.
2406
Description
EtherCAT device in unexpected state
Possible Cause
EtherCAT device(s) have invalid configuration or have experienced a watchdog event.
Solution
Check the EtherCAT device configuration in the ENI file and EtherCAT Configuration Tool.
2407
Description
EtherCAT Master in unexpected state
Possible Cause
Bus does not match ENI file.
Solution
Download a new ENI file or plug in all devices.
82
GEH-6855_Vol_II
GEH-6855_Vol_II Mark VIeS Functional Safety Systems Volume II
Public Information
EtherCAT ENI file does not match bus configuration
Possible Cause
ENI File imported in ToolboxST does not match the discovered network.
Solution
•
Verify ENI file matches the network connected to the Mark VIe controller.
•
Verify EtherCAT network is connected and intact.
2409
Description
EtherCAT redundant Ethernet links crossed
Possible Cause
Main and Redundant Ethernet links are swapped on the controller.
Solution
Switch the EtherCAT Network connections on the controller.
2410
Description
EtherCAT configuration is not supported
Possible Cause
•
The ENI file contains unsupported commands or features
•
The ENI file contains commands that are unsupported in redundancy
Solution
•
Remove unsupported commands or disable unsupported features.
•
In redundant operation, replace LRW commands with LRD / LWR.
Controllers
GEH-6855_Vol_II System Guide 83
Public Information
GEH-6855_Vol_II Mark VIeS Functional Safety Systems Volume II
Public Information
Unmanaged Ethernet Switches
GE’s product line of industrial unmanaged Ethernet 10/100 switches, ESWA and ESW, are specifically designed to meet the
needs of real-time industrial control solutions. To meet the requirements for speed and functionality, the following features are
provided:
•
802.3, 802.3u, and 802.3x compatibility
•
10/100 base copper with auto negotiation
•
Full/half duplex auto-negotiation
•
100 Mbps FX uplink port
•
HP-MDIX auto sensing
•
LEDs for Link Presence, Activity and Duplex, and Speed per port (each LED has two colors)
•
LED for Power
•
Minimum 256 KB buffer with 4K media access control (MAC) addresses
Unmanaged Ethernet Switches
GEH-6855_Vol_II System Guide 85
Public Information
Available Form Factors
The ESWx switch is available in the following form factors:
Part #
Description
IS420ESWAH1A
8 ports 10/100BASE-TX + 1 port 100BASE-FX LC-type connection
IS420ESWAH2A
8 ports 10/100BASE-TX + 2 ports 100BASE-FX LC-type connection
IS420ESWAH3A
8 ports 10/100BASE-TX
IS420ESWAH4A
8 ports 10/100BASE-TX + 1 port 100BASE-LX10 LC-type connection
IS420ESWAH5A
8 ports 10/100BASE-TX + 2 ports 100BASE-LX10 LC-type connection
IS420ESWBH1A
16 ports 10/100BASE-TX + 1 port 100BASE-FX LC-type connection
IS420ESWBH2A
16 ports 10/100BASE-TX + 2 ports 100BASE-FX LC-type connection
IS420ESWBH3A
16 ports 10/100BASE-TX
IS420ESWBH4A
16 ports 10/100BASE-TX + 1 port 100BASE-LX10 LC-type connection
IS420ESWBH5A
16 ports 10/100BASE-TX + 2 ports 100BASE-LX10 LC-type connection
3.2
Installation
For new installations, mount the switch or switches onto the control system panel(s) using a DIN-rail. Connect the copper
and/or fiber cables in accordance with system requirements and redundancy. Connect the 28 V dc power from the power
distribution board to the switch.
Note For system requirements, redundancy, and other related information, refer to the Mark VIe Industrial Ethernet / IONet
Switches Summary Sheet (GEI-100869) and the Mark VIeS Functional Safety Systems for General Market Volume I: System
Guide (GEH-6855_Vol_I), the chapter Ethernet Networks.
GE has qualified the following DIN-rail clips for use with the ESWx switches.
Clip Part #
Switch Usage
Mounting Orientation
259B2451BVP1
ESWA (8-port) or
ESWB (16-port)
Long edge of switch body parallel to rail
259B2451BVP2
ESWA (8-port)
Long edge of switch body perpendicular to rail
259B2451BVP4
ESWB (16-port)
Long edge of switch body perpendicular to rail
86
GEH-6855_Vol_II
GEH-6855_Vol_II Mark VIeS Functional Safety Systems Volume II
Public Information
The RJ-45 connectors support multiple insertions and removals with an estimated service life expectancy of 200
insertion/removal cycles. Connector components are exposed to torsion forces across any axis of the connector and tension
forces that are static from cable weight and cable dressing. Dynamic stresses are imposed on the connectors from transients in
assembled system transport to the plant site and operation in a high vibration power production environment. Connector
design anticipated static forces of three pounds force (89.9 Newton) per connection while complying with the other dynamic
operating load requirements.
Connector
Description
28 V dc power
Phoenix® contact part number MC 1.5/S-STF-3.81
Copper
RJ-45 ports for Cat 5e UTP
Fiber
LC-type †
Single Mode Fiber (SMF) requires the additional IR SFP single-mode transducer, GE part # 65G2100–008.
† A port adapter is used if needing to interface an existing SC fiber termination to the LC fiber port.
GE part # 336A5026P01 SC to LC adapter is required for multi-mode fiber (most common).
GE part # 336A5026P02 SC to LC adapter is required for single-mode fiber.
3.4
IONet Switch Specifications
Item
Description
Mounting
DIN-rail mounted with separately purchased mounting clip. DIN-rail mounting meets
vibration and shock specifications.
Dimensions (width x depth x height)
ESWA: 138 x 86 x 56 mm (5.45 x 3.40 x 2.20 in)
ESWB: 188 x 86 x 56 mm (7.40 x 3.40 x 2.20 in)
Incoming power connection
Supports two redundant Diode-OR module power supply inputs of 18 to 36 V dc
Cooling
Convection cooled when mounted vertically or horizontally
Coating
Resistant to corrosion with provisions made for grounding per IEC 60721-3-3 Class
3C2
Ambient rating for enclosure design
IS420ESWAHxA and IS420ESWBHxA are rated for -40 to 70°C (-40 to 158 °F)
Refer to the Mark VIeS Functional Safety Systems for General Market Volume I:
System Guide (GEH-6855_Vol_I), the chapter Technical Regulations, Standards,
and Environments for more details.
Absolute Maximum Current
IS420ESWAHxA: < 0.5 A
IS420ESWBHxA: < 1.0 A
Shipping vibration, shock
The switch can survive 72 hours at 0.3 G rms between frequencies of 4 to 16 Hz.
Three shocks of 15G, 2-millisecond impulse each repeated for all three axes as
mounted on panel base.
Operating vibration
Can survive 1.0 G Horizontal, 0.5 G vertical at 15 to 120 Hz
Unmanaged Ethernet Switches
GEH-6855_Vol_II System Guide 87
Public Information
The performance of a level 1 Ethernet switch is mainly centered on the ability to buffer packets. When a level 1 switch has a
continuous stream of incoming broadcast or multicast packets, the switch must in turn send those packets out upon complete
reception. A single incoming stream should require enough space to buffer one packet or at the most one packet per port.
When the switch has multiple incoming streams, it is only able to relieve one of the incoming streams and must buffer the rest
for later transmission.
3.5.1
Conformance Criteria
The packet traffic can be synchronized by IEEE 1588 timing and triggered to initiate within a 1-microsecond packet start
window. The switch’s capability and conformance is tested to meet the following four criteria:
•
Initiation of the required Multicast packet load on one port, without IEEE 802.3x flow control negotiated
•
Initiation of the required Multicast packet load on one port, with IEEE 802.3x flow control negotiated
•
Initiation of the required Multicast packet load distributed across all ports, packet count per port must average required
per number of switch ports with no IEEE 802.3x flow control
•
Initiation of the required packet Multicast load distributed across all ports, packet count per port must average 200 per
number of switch ports with IEEE 802.3x flow control negotiated on half the ports
3.5.2
Flow Control (Pause)
The switch supports flow control between switches. It uses IEEE defined pause packets to receive and honor pause packets.
The switch only sends the pause packets if it needs flow control on a port.
3.5.3
Reliability and Performance
Because high reliability is critical to any controls solutions business, the switch exceeds 4 million hours Mean Time Between
Failures (MTBF) at 35°C (95 °F) ambient temperature, ground fixed controlled environment. The switch also meets the
following performance criteria:
Performance Criteria
Feature
Description
Switch latency
Switch packet latency does not exceed required application limits.
Switch architecture
The switch supports store and forward architecture, providing high data confidence.
Inrush current
The switch provides soft start capability that limits inrush current to less than 200% of the
normal operating current.
88
GEH-6855_Vol_II
GEH-6855_Vol_II Mark VIeS Functional Safety Systems Volume II
Public Information
The following figure defines the LED functions on the ESWx switch.
Power is solid green when internal
power supply is up and regulating
For each of the 16 ports (and SPF ports),
the Activity LED functions as follows:
•
flashes green for activity at full duplex
•
flashes yellow for activity at half duplex
For each of the 16 ports (and SPF ports),
the Link LED functions as follows:
•
Solid green with 100 MB link
•
Solid yellow with 10 MB link
•
Not lit if no link
Attention
In certain conditions, an input voltage sag, known as a brownout, may cause the GE
IS420ESWBH#_ (ESWB) I/O Network (IONet) switch to incorrectly reboot and fail to
re-establish communication with the system. If the ESWB switch experiences a
brownout condition that reduces the input 28 V line below the minimum operating
voltage but not completely to 0 V, when the input voltage returns to above the
minimum operating voltage, the switch may not correctly reboot. If this occurs, the
ESWB LEDs will either remain on solid, flash in sync, or scroll from one side to the
other, and the switch will not re-establish communication. If the site experiences a
brownout, after the voltage returns and the IONet loses communication, observe the
LEDs on the front of the switch. If they are solid, flashing in sync, or scrolling, cycle
power to manually reboot the switch.
Unmanaged Ethernet Switches
GEH-6855_Vol_II System Guide 89
Public Information
Third-party Switch Replacement
When the ESWA or ESWB is used to replace a different unmanaged switch, it uses the existing mounting brackets, which can
either be panel or DIN-rail mounts. There are seven screw holes used on the existing switch to support panel mounting. The
following drawing displays the pattern and dimensions for these holes.
Holes to Support Panel Mounting
90
GEH-6855_Vol_II
GEH-6855_Vol_II Mark VIeS Functional Safety Systems Volume II
Public Information
YAIC Analog I/O Modules
4.1
Mark VIeS YAIC Analog I/O Pack
The Analog I/O pack (IS420YAICS1B) provides the electrical interface between one
or two I/O Ethernet networks and an analog I/O terminal board. The YAIC contains a
common processor board and an acquisition board specific to the analog input
function. The I/O pack is capable of handling up to 10 analog inputs, the first eight of
which can be configured as ±5 Vor ±10 V inputs, or 4-20 mA current loop inputs. The
last two inputs can be configured as ±1 mA or 4-20 mA current inputs.
The load terminal resistors for current loop inputs are located on the terminal board
and voltage is sensed across these resistors by the YAIC. The I/O pack also includes
support for two 0-20 mA current loop outputs. The I/O pack receives or sends data
through dual RJ-45 Ethernet connectors to the controller and has a three-pin connector
to power it on. Output is through a DC-37 pin connector that connects directly with the
associated terminal board connector. Visual diagnostics are provided through indicator
LEDs.
TBAI Analog Input
Terminal Board
YAIC
Analog I/O Pack
Analog Inputs (10)
Processor board
BPAI board
One I/O pack for
Simplex (connect
to JR1)
Dual is not
available
Single or dual
Ethernet cables
ENET1
ENET2
External 28 V
dc power supply
ENET1
ENET2
28 V dc
Three I /O
packs for TMR
Analog Outputs (2)
ENET1
ENET2
28 V dc
YAIC Analog I/O Modules
GEH-6855_Vol_II System Guide 91
Public Information
The YAIC I/O pack contains an internal processor board.
YAIC Version Compatibility
I/O Pack
Processor Board Compatible (Supported) Firmware
ControlST Software Suite Versions
YAICS1B
BPPC
V05.01 and later
Supported in V06.01 and later versions
Attention
YAICS1A and YAICS1B I/O pack versions cannot be mixed on the same T-type
terminal board.
All three YAIC I/O packs in a TMR set must be the same hardware form.
To upgrade or replace the YAIC, refer to the following replacement procedures for specific instructions:
•
Replace Mark VIeS Safety I/O Pack with Same Hardware Form
•
Replace Mark VIeS Safety I/O Pack with Upgraded Hardware Form
The YAIC I/O pack is compatible with the TBAISIC and STAIS2A terminal boards.
YAIC Terminal Board Compatibility
Terminal Board
Description
I/O Pack Redundancy
Simplex
Dual
TMR
TBAIS1C
TMR Analog input/output terminal board
Yes
No
Yes
STAIS2A
Simplex Analog input/output terminal board
Yes
No
No
I/O pack redundancy refers to the number of I/O packs used in a signal path, as follows:
•
Simplex uses one I/O pack.
•
TMR uses three I/O packs.
92
GEH-6855_Vol_II
GEH-6855_Vol_II Mark VIeS Functional Safety Systems Volume II
Public Information
To install a new YAIC I/O module into an existing Mark VIeS panel
1.
Securely mount the desired terminal board.
2.
Directly plug one YAIC I/O pack for simplex or three YAIC I/O packs for TMR into the terminal board connectors.
3.
Mechanically secure the packs using the threaded studs adjacent to the Ethernet ports. The studs slide into a mounting
bracket specific to the terminal board type. The bracket location should be adjusted such that there is no right-angle force
applied to the DC-37 connector between the pack and the terminal board. The adjustment should only be required once in
the life of the product.
4.
Plug in one or two Ethernet cables depending on the system configuration. The pack will operate over either port. If dual
connections are used, the standard practice is to connect ENET1 to the network associated with the R controller. These
choices are also defined in the ToolboxST configuration.
5.
Apply power to the pack by plugging in the connector on the side of the pack. It is not necessary to insert this connector
with the power removed from the cable as the I/O pack has inherent soft-start capability that controls current inrush on
power application.
6.
Configure the I/O pack as necessary using the ToolboxST application.
4.1.2.1
Connectors
The I/O pack contains the following connectors:
•
A DC-37 pin connector on the underside of the YAIC connects directly to the discrete input terminal board. The
connector contains the 24 input signals, ID signal, relay coil power, and feedback multiplex command.
•
An RJ-45 Ethernet connector named ENET1 on the side of the pack is the primary system interface.
•
A second RJ-45 Ethernet connector named ENET2 on the side of the I/O pack is the redundant or secondary system
interface.
•
A 3-pin power connector on the side of the pack is for 28 V dc power for the pack and terminal board.
YAIC Analog I/O Modules
GEH-6855_Vol_II System Guide 93
Public Information
Analog Input Hardware
The YAIC accepts input voltage signals from the terminal board for all 10 input channels. The analog input section consists of
an analog multiplexer block, several gain and scaling selections, and a 16-bit analog-to-digital converter (ADC).
Inputs 1–8 can be individually configured as ±5 Vor ±10 V, or 4–20 mA scale signals, depending on the input configuration.
Inputs 9–10 can only be configured for ±1 mA or 4-20 mA. The terminal board provides a 250 Ωburden resistor when
configured for current inputs yielding a 5 V signal at 20 mA. These analog input signals are first passed through a passive,
low pass filter network with a pole at 75.15 Hz. Voltage signal feedbacks from the analog output circuits and calibration
voltages are also sensed by the YAIC analog input section.
94
GEH-6855_Vol_II
GEH-6855_Vol_II Mark VIeS Functional Safety Systems Volume II
Public Information
Analog Output Hardware
The YAIC includes two 0-20 mA analog outputs capable of 18 V compliance running simplex or TMR. A 14-bit
digital-to-analog converter (DAC) commands a current reference to the current regulator loop in the YAIC that senses current
both in the YAIC pack and on the terminal board. In TMR mode, the three current regulators in each YAIC share the
commanded current loads among themselves. Analog output status feedbacks for each output include:
•
Current reference voltage
•
Individual current (output current sourced from within the YAIC)
•
Total current (as sensed from the terminal board, summed current in TMR mode)
Each analog output circuit also includes a normally open mechanical relay to enable or disable operation of the output. The
relay is used to remove a failed output from a TMR system allowing the remaining two YAICs to create the correct output
without interference from the failed circuit. When the suicide relay is de-activated, the output opens through the relay,
open-circuiting the analog output from the customer load that is connected to the terminal board. The mechanical relay has a
second normally open contact that is used as a status to indicate position of the relay to the control and includes visual
indication with an LED.
YAIC Analog I/O Modules
GEH-6855_Vol_II System Guide 95
Public Information
Number of Channels
12 channels per terminal board (10 AI, 2 AO)
AI Types Supported
Inputs 1 to 8: ±5 V dc, ±10 V dc, or 4–20 mA
Inputs 9 to 10: 4–20 mA or ±1 mA
Input Converter Resolution
16-bit ADC
I/O Scan Time
Supported Controller I/O Scan rates: 10 ms, 40 ms, 80 ms, 160 ms
Input Accuracy
0.1% of full scale over the full operating temperature range.
Noise Suppression on Inputs
The 10 circuits have hardware filter with single pole down break at 500 rad/s. A software filter,
using a two pole low pass filter, is configurable for: 0.75 Hz, 1.5 Hz, 3 Hz, 6 Hz, 12 Hz
Common Mode Rejection
AC CMR 60 dB at 60 Hz, with up to ±5 V common mode voltage.
DC CMR 80 dB with -5 to +7 peak V common mode voltage
Common Mode Voltage Range
±5 V (±2 V CMR for the ±10 V inputs)
Output Converter
14-bit D/A converter with 0.5% accuracy
Output Load
800 Ωmax for 0-20 mA output
Output Accuracy
±0.5% of full measurement range
Power Consumption
5.3 watts typical, 6.2 watts worst case
Compressor Stall Detection
Not supported
Size
8.26 cm high x 4.19 cm wide x 12.1 cm deep (3.25 in x 1.65 in x 4.78 in)
Ambient Rating for Enclosure Design
-40 to 70°C (-40 to 158 °F)
Technology
Surface mount
Note
For further details, refer to the Mark VIeS Functional Safety Analog I/O Module Summary Sheet (GEI-100866).
96
GEH-6855_Vol_II
GEH-6855_Vol_II Mark VIeS Functional Safety Systems Volume II
Public Information
The YAIC performs the following self-diagnostic tests:
•
A power-up self-test that includes checks of RAM, flash memory, Ethernet ports, and most of the processor board
hardware
•
Continuous monitoring of the internal power supplies for correct operation
•
A check of the electronic ID information from the terminal board, acquisition board, and processor board to confirm that
the hardware set matches, followed by a check that the application code loaded from flash memory is correct for the
hardware set
•
Each analog input has hardware limit checking based on configurable high and low levels for 4-20 mA inputs and preset
(non-configurable) levels for ± 5 V, ± 10 V, and ± 1 mA inputs. If the limit is exceeded, then the I/O pack raises an alarm
and marks the input as unhealthy. A logic signal (L3DIAG_pack) is set, which refers to the entire board.
•
Each input has configurable system limit checking with high and low levels, latching, and non-latching selection options.
These limits can be used in the programming of the controller to generate process alarms. This controller logic requires
using a RSTSYS pin on a SYS_OUTPUTS block to reset the out of limits status when the latch is enabled. System limit
checking can be configured as Enable/Disable at point level, and are only functional only when system limits are enabled
at module level (Parameters tab).
•
The analog input hardware includes precision reference voltages in each scan. Measured values are compared against
expected values and are used to confirm health of the analog to digital converter circuits.
•
Analog output current is sensed on the terminal board using a small burden resistor. The I/O pack conditions this signal
and compares it to the commanded current to confirm health of the digital to analog converter circuits.
•
The analog output suicide relay is continuously monitored for agreement between commanded state and feedback
indication.
Details of the individual diagnostics are available from the ToolboxST application. The diagnostic signals can be individually
latched and then reset with the RSTDIAG signal if they go healthy.
4.1.5.1
Status LEDs
Relay Application LEDs
LED
Label
Description
Yellow
ENA1
Indicates the closure of the relay controlling output 1
Yellow
ENA2
Indicate the closure of the relay controlling output 2
YAIC Analog I/O Modules
GEH-6855_Vol_II System Guide 97
Public Information
Enable or temporarily disable all system limit checks.
Setting this parameter to Disable will cause a diagnostic
alarm to occur.
Enable, Disable
Min_ MA_Input
Select minimum current for healthy 4-20 mA input
0 to 22.5 mA
Max_ MA_Input
Select maximum current for healthy 4-20 mA input
0 to 22.5 mA
4.1.6.2
Inputs
Input
Description
Choices
AnalogInput01
through
AnalogInput10
First of 10 Analog Inputs – board point. Point edit
(Input REAL)
InputType
Current or voltage input type
Unused or 4-20 mA (for all Analog Inputs)
±5 V or ±10 V (for AnalogInput01 to 08 only)
±1 mA (for AnalogInput09 and 10 only)
Low_Input
Value of input current (mA) or voltage (V) at low end of input scale
-10 to 20
Low_Value
Value of input in engineering units at Low_Input
-3.4082 e + 038 to 3.4028 e + 038
High_Input
Value of input current (mA) or voltage (V) at high end of input scale
-10 to 20
High_Value
Value of input in engineering units at High_Input
-3.4082 e + 038 to 3.4028 e + 038
InputFilter
Bandwidth of input signal filter
Unused, 0.75hz, 1.5hz, 3hz, 6hz, 12hz
TMR_DiffLimit
Difference limit for voted inputs in % of High_Value - Low_Value
0 to 200
SysLim1Enabl
Enable System Limit 1 fault check
Enable, Disable
SysLim1Latch
System Limit 1 fault latch - if set, requires a Reset System Limits
(RSTSYS) on SYS_OUTPUTS block to clear
Latch, NotLatch
SysLim1Type
System Limit 1 Check Type
>= or <=
SysLim1
System Limit 1 in engineering units
-3.4082 e + 038 to 3.4028 e + 038
SysLim2Enabl
Enable System Limit 1 fault check
Enable, Disable
SysLim2Latch
System Limit 2 fault latch - if set, requires a Reset System Limits
(RSTSYS) on SYS_OUTPUTS block to clear
Latch, NotLatch
SysLim2Type
System Limit 2 Check Type
>= or <=
SysLimit2
System Limit 2 in Engineering Units
-3.4082 e + 038 to 3.4028 e + 038
DiagHighEnab
Enables the generation of a high limit diagnostic alarm when the
value of the 4-20 mA input is greater than the value of parameter
Max_MA_Input
Enable, Disable
DiagLowEnab
Enables the generation of a low limit diagnostic alarm when the
value of the 4-20 mA input is less than the value of parameter Min_
MA_Input
Enable, Disable
TMR_DiffLimt
Diag limit, TMR input vote difference, in percent of (High_Value -
Low_Value)
0 to 200 %
98
GEH-6855_Vol_II
GEH-6855_Vol_II Mark VIeS Functional Safety Systems Volume II
Public Information
First of two analog outputs - board point, Point edit
Output REAL
Output_MA
Output current, mA selection.
Unused, 0-20 mA
OutputState
State of the outputs when offline. When the YAIC loses
communication with the controller, this parameter determines
how it drives the outputs:
PwrDownMode - Open the output relay and drive outputs to
zero current
HoldLastVal - Hold the last value received from the controller
Output_Value - Go to the configured output value set by the
parameter Output_Value
PwrDownMode
HoldLastVal
Output_Value
Output_Value
Pre-determined value for the outputs
-3.4082 e + 038 to 3.4028 e + 038
Low_MA
Output mA at low value
0 to 200 mA
Low_Value
Output in Engineering Units at Low_MA
-3.4082 e + 038 to 3.4028 e + 038
High_MA
Output mA at high value
0 to 200 mA
High_Value
Output value in Engineering Units at High_MA
-3.4082 e + 038 to 3.4028 e + 038
TMR_Suicide
Enables suicide for faulty output current, TMR only
Enable, Disable
TMR_SuicLimit
Suicide threshold (Load sharing margin) for TMR operation, in
mA
0 to 200 mA
D/A_ErrLimit
Difference between D/A reference and feedback, in % for
suicide, TMR only
0 to 200 %
Dither_Ampl
Dither % current of Scaled Output mA
0 to 10
Dither_Freq
Dither rate in Hertz
Unused, 12.5hz, 25hz, 33.33hz, 50hz, 100hz
YAIC Analog I/O Modules
GEH-6855_Vol_II System Guide 99
Public Information
I/O Link OK indication
Input
BOOL
ATTN_YAIC
Module Diagnostic
Input
BOOL
IOPackTmpr
I/O Pack Temperature (deg F)
Input
REAL
PS18V_YAIC
I/O 18V Power Supply Indication
Input
BOOL
PS28V_YAIC
I/O 28V Power Supply Indication
Input
BOOL
SysLimit1_1
System Limit 1
Input
BOOL
↓
↓
Input
BOOL
SysLimit1_10
System Limit 1
Input
BOOL
SysLimit2_1
System Limit 2
Input
BOOL
↓
↓
Input
BOOL
SysLimit2_10
System Limit 2
Input
BOOL
OutSuicide1
Status of Suicide Relay for Output 1
Input
BOOL
OutSuicide2
Status of Suicide Relay for Output 2
Input
BOOL
Out1MA
Feedback, Total Output Current, mA
Input
REAL
Out2MA
Feedback, Total Output Current, mA
Input
REAL
100
GEH-6855_Vol_II
GEH-6855_Vol_II Mark VIeS Functional Safety Systems Volume II
Public Information
