GEK-118585 OC 6000e Nexus System Manual V1.3
GEK-118585 OC 6000e Nexus System Manual V1.3
GEK-118585 OC 6000e Nexus System Manual V1.3
OC 6000e Nexus
System Manual
GEK-118585
Revision 1.3
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. All license inquiries should be directed to the address below. If further information is
desired, or if particular problems arise that are not covered sufficiently for the purchaser’s
purpose, the matter should be referred to:
GE Energy
Control Solutions
1800 Nelson Road
Longmont, CO 80501
[email protected]
http://www.ge-mcs.com
Phone: + 1 (800) 835-5182 (United State)
+ 1 (970) 461-5201 (International)
(“+” indicates the international access code required when calling from outside the USA)
This document contains proprietary information of General Electric Company, USA and is
furnished to its customer solely to assist that customer in the installation, testing, operation,
and/or maintenance of the equipment described. This document shall not be reproduced in
whole or in part nor shall its contents be disclosed to any third party without the written
approval of GE.
GE provides the following document and the information included therein as is and without
warranty of any kind, express or implied, including but not limited to any implied statutory
warranty of merchantability or fitness for particular purpose.
© 2015 General Electric Company, USA. All rights reserved.
Tip Provides essential information that is not normally defined in regular use
but from an experienced user.
Contents
Chapter 1 OC 6000e Nexus Overview 1
1.1 Overview .............................................................................................................................................. 1
1.1.1 Applications ..................................................................................................................................... 1
1.1.2 Controllers ........................................................................................................................................ 2
1.1.3 I/O Networks ................................................................................................................................... 2
1.1.4 I/O Modules...................................................................................................................................... 2
1.1.5 Related Documents....................................................................................................................... 3
1.1.6 How to Get Help ............................................................................................................................. 4
1.1.7 Acronyms and Abbreviations ..................................................................................................... 4
Chapter 2 System Architecture 5
2.1 Overview .............................................................................................................................................. 5
2.2 System Components ........................................................................................................................ 5
2.2.1 Controller .......................................................................................................................................... 5
2.2.2 I/O Networks ................................................................................................................................... 6
2.2.3 I/O Module........................................................................................................................................ 7
2.2.4 Power sources ................................................................................................................................ 9
2.2.5 Networks ........................................................................................................................................ 11
2.2.6 Cabinets .......................................................................................................................................... 13
2.2.7 Human Machine Interface (HMI) ............................................................................................. 15
2.2.8 Remote I/O ..................................................................................................................................... 16
2.2.9 3rd-party Communication Interface ....................................................................................... 17
2.3 System Features and Specification ........................................................................................... 19
2.3.1 IO Module Specification ............................................................................................................. 19
2.3.2 Communication Control Module Specification ................................................................... 24
2.3.3 HMI summary ............................................................................................................................... 25
2.4 Software............................................................................................................................................. 25
2.4.1 OS ..................................................................................................................................................... 25
2.4.2 Control Platform Software ........................................................................................................ 25
2.4.3 Application Software .................................................................................................................. 25
2.5 Certification and standards ......................................................................................................... 26
Chapter 3 System Planning 27
3.1 Hardware Calculation .................................................................................................................... 27
3.1.1 Controller ........................................................................................................................................ 27
3.1.2 I/O Module...................................................................................................................................... 27
3.1.3 iLink Cable ...................................................................................................................................... 28
3.1.4 Bus & Power Extension Module MCD50 ................................................................................ 28
3.2 Cabinet ............................................................................................................................................... 28
3.2.1 Control/Extension Cabinet Assemblies ................................................................................. 28
3.2.2 Control Cabinet............................................................................................................................. 29
3.2.3 General Cabinet ........................................................................................................................... 29
3.3 HMI....................................................................................................................................................... 29
3.4 Network switch ................................................................................................................................ 30
3.5 Other equipment ............................................................................................................................. 30
3.5.1 Communication Module ............................................................................................................ 30
Chapter 4 Installation and Configuration 31
4.1 System Arrangement ..................................................................................................................... 31
4.2 Signal Segregation .......................................................................................................................... 31
4.3 Cabinet Assembly ........................................................................................................................... 31
4.4 System Network Topology ........................................................................................................... 32
4.5 System Power Distribution ........................................................................................................... 32
4.6 Power Distribution Cabinet .......................................................................................................... 33
4.7 Grounding.......................................................................................................................................... 34
1.1 Overview
The OC 6000e Nexus series is the I/O system extension based on the OC 6000e
integrated control platform. It was designed to serve a wide variety of industrial
process control and protection applications from boiler control and protection,
steam turbine control and protection, to power generation balance of plant (BOP)
equipment. The compatibility design of the OC 6000e platform and the Nexus I/O
series also provides an efficient system upgrading solution for the legacy OC 4000
DCS user.
1.1.1 Applications
The control system consists of three primary components, the Controllers, I/O
Networks, and I/O Modules as shown in the following diagram.
UDH A UDH B
A B
Controllers
iDPU iDPU
I/O Networks
S Link
R Link
T T T
B B B
I/O Modules
T T T
B B B
Note Each pair of redundant controllers can provide max. 4 I/O links. To simplify the diagram, only
one link is shown here.
All types of the Nexus I/O module have the same dimension and installation
mechanism, except the logic protection module MLP/BLP. For discrete output, the
large capacity relay extension module is available for specific applications.
Nexus I/O module provides the following features:
Redundant 24V dc power supplies
Module internal working power and I/O power are isolated with system power
Power management, plug and play and current-limit
High performance 32bit embedded processor
Redundant high-speed serial communication interface
Full isolated circuit design,input/output isolation and protection
Self-diagnostic, working power and inner temperature monitoring and alarm
Removable Euro-style terminal block
Highly compatible mounting size and I/O wiring definition with legacy OC 4000
terminal board
2.1 Overview
This chapter defines the architecture of the OC 6000e Nexus system, including the
system components, communication networks, and remote control/IO station. It
also discusses connectivity between the Nexus system and Third-Party systems.
2.2.1 Controller
The iDPU series controller is applied in the OC 6000e Nexus system. It is an
integrated stand-alone computer that runs the application code for industrial
process control and data communication. The controller mounts directly in a panel.
Real-Time I/O data is transferred to and from the control system over the intelligent
I/O buses (iLink) between the Nexus I/O module and the controller. The Operating
System (OS) is QNX® Neutrino®, a real-time multitasking OS designed for high-speed,
high-reliability industrial applications. The controller is loaded with software specific
to its application, which includes but not limited to third-party communication, boiler
control, boiler protection, steam turbine control, balance of plant products. The
program language is function block based and complies with IEC1131-3 standards
and strengthens in graphic configuration and debugging language. Time
synchronization of the I/O network is implemented through iLink (R or S bus), and the
synch accuracy can reach to ±100us. Data communication between controllers and
other system nodes is implemented through UDH (Unit Data Highway) A and/or B.
In a simplex system, I/O network data includes process inputs/outputs to the I/O
modules.
In a dual system, I/O network data includes:
Process inputs/outputs to the I/O modules
Internal state values and initialization information from the designated
controller
Status and synchronization information from both controllers
Redundant 24V dc
Power Supplies
Redundant UDH
Interfaces
As shown in Fig 1.1-1, integrated I/O networks also include associated I/O bus &
power extension modules, as well as controller iLink extension cables. For a detailed
network connection scheme, please refer to GEK-118586 OC 6000e Nexus
Hardware Manual.
Field signals are interfaced to the control system via the I/O modules terminal blocks.
Each I/O module has several TBs (quantity depends on module type). It is a
removable single-row Euro-style with 16 pins (or different, depends on module type)
for each TB, and each pin can hold one 2.05mm (#12AWG) wire, or two 1.63mm
(#14AWG) wires. TB pitch is 5.08mm (0.2”) with 2000VAC insulation withstands
voltage.
I/O modules are installed in the cabinet in several columns. The DO module and the
associated extension relay board which are used for large capacity DC control
circuit are mounted adjacently, with module above relay board. Front and rear
grounding bars are provided on the bottom of the cabinet and adjacent to the
cabinet entrance of field cables for shield grounding.
Generally, other equipment added in the control cabinet for process monitoring and
control purpose, such as 3rd-party communication interface module, signal isolator,
should be selected using 24V dc power supply and powered by system DC power. In
such cases, system DC power consumption needs to be calculated and checked,
and corresponding fuse(s) need to be installed. Those accessories installed the in
cabinet for the control system safety and reliability, or for some special application,
should not use system DC power, e.g. heat dissipation fan, heater, or moisture
eliminator, In principle, power source from switch F31 of power switch box should be
applied, or use separated power supply per actual requirement.
AC power supply
For system w/ AC power supply, the OC 6000e Nexus control cabinet provides two
redundant AC power inputs, connect to the AC power switch box, to provide filtering
and protection for the input power, as well as auxiliary power outlet. The electrical
circuit scheme is shown as follows:
Two power inputs are switched by dedicated MCB, then filtered and rectified by
power filters, and connected to two 24V dc power supply modules. The power
supply for the cabinet auxiliaries is coming from power input 2 by default, which is
switched by switch F31, for cabinet heat dissipation fan and other device. Maximum
current is 2A.
If special power is required for auxiliaries and can’t use default power supply,
additional power input need to be considered for this purpose.
DC power supply
Each standard OC 6000e Nexus control cabinet has two redundant DC power supply
modules, and each DC module has its dedicated AC input which comes from the AC
power switch box. DC power is provided for all system modules. All OC 6000e Nexus
modules have redundant DC power input, including iDPU controller, I/O module and
communication control module.
Two 24V dc outputs from redundant DC modules connect to power distribution
terminal block (including circuit fuse), then distribute to iDPU controller and MCD50
(I/O bus & power extension module) separately. The DC power for the extension
cabinet also comes from this terminal block.
Looped power supply is applied for I/O modules within one same iLink, which is
derived from the same fuse of the power distribution terminal block. Remove/plug
any module will not affect other module’s power supply.
DC power fuse – glass tube fuse, 20x5mm, 8 Amp for each I/O bus.
Proper fuse must be installed for each DC branch, to avoid affecting other
power circuit when short-circuit/overload occurs, and to prevent
equipment damage and avoid consequent safety risks as well.
2.2.5 Networks
Dual-layer communication networks are applied in the OC 6000e Nexus system. The
system topology is shown below. This is for one unit.
The system backbone network adopts TCP/IP industrial Ethernet and GE standard
EGD communication protocol, forms the control system UDH (Unit Data Highway),
for data communication & sharing between controllers and HMIs (Human Machine
Interface).
Between the controller and I/O modules, there is a GE self-defined intelligent serial
communication bus, namely iLink, for real-time communication between I/O
modules and controller.
Per system extension requirement, all HMI’s functionality can be extended for
advanced application. By re-configuring existing HMI station, or setting dedicated
communication interface unit, a high level system network for plant application can
be formed, namely PDH (Plant Data Highway).
2.2.6 Cabinets
The OC 6000e Nexus system contains the following types of cabinet: control cabinet,
I/O extension cabinet, power supply cabinet, network cabinet, etc.
The control cabinet is the smallest construction unit of the control system.
Normally, an integrated Nexus DCS system is composed by one or several such
control units. Each control cabinet contains dual-redundant (or simplex) iDPU
controllers, dual-redundant (or simplex) iLink buses, I/O modules, power switch
box, dual-redundant (or simplex) DC modules and other system components.
Each control cabinet can hold a maximum of two pairs of redundant I/O buses,
which come from controller’s iLink port #1 and #2.
The I/O extension cabinet is used to extend I/O capacity of the control cabinet.
Compared with the control cabinet, the extension cabinet normally has no
controller, nor power supply assembly. Module’s power supply comes from
associated control cabinet DC output. Remote I/O cabinet is some kind of
special I/O extension cabinet. It has a power supply assembly. Each I/O
extension cabinet can hold maximum two pairs of redundant I/O buses, which
come from controller’s iLink port #3 and #4.
The power supply cabinet is used for whole control system input power
distribution. Normally, the cabinet contains power indication & alarm assembly,
MCBs and power bus system. The whole system’s grounding bar can also be
installed in this cabinet.
The whole control system’s UDH/PDH switches are installed in network cabinet,
as well as all power supplies for these network switches.
All kinds of cabinets apply standard framework design. The cabinet dimension is
800x600x2200mm, IP42 protection. Cabinet mounting size is shown below.
Control cabinet
In consideration of module’s installation characteristics, the inner structure of the
OC 6000e Nexus control cabinet and I/O extension cabinet is separated into two
areas: power & control unit area, and I/O area.
24V dc
module
Power &
Control Unit
Power
Area
switch box
iLink buses
I/O Area
Power Indication
AC Power
& Alarm Assembly
Switchover
Assembly
MCB
24V dc
Module
UDH
Switch
PDH
Switch
Cabinet Input
Power TB
Fig 2.2-10 Standard Power Supply (Network) Cabinet Structure (Front View)
Fig 2.2-11 Nexus Remote IO Network Connection Scheme (Twisted Pair Cable)
MCD50 module should be applied in the central control cabinet for remote IO bus
connection, and connect to redundant iDPU controller via special Y type iLink cable.
Per actual application, proper I/O modules and associated two MCD50 modules are
installed in the remote IO cabinet, the I/O network connection is same as standard
iLink connection. When use remote IO, make sure the bus terminator is installed on
MCD50 C that is shown in above scheme.
Ethernet
N/A
M port
P
U
Serial port N/A N/A N/A N/A
TP Cable
Special interface
3rd-party system
(Profibus-DP)
Fig 2.2-12 Nexus and 3rd-party Device/system Connection
Item Specification
System ambient temperature 0~60ºC
System ambient humidity 10 ~ 95% (non-condensing)
Total points in one system < 64,000 points
Number of controllers Max. 160
Number of HMIs Max. 80
SOE accuracy 1ms
Controller 1.66GHz, 15W
Real-time OS QNX®
Power rating for each cabinet 110-240V~, 50Hz/60Hz, < 480W
Item Specification
Power supply Dual redundant 24V dc (±10%)
Processor High performance 32bit embedded processor
IO network interface Redundant high-speed serial bus, DB-9 male connector
IO network speed 115.2kbps、230.4kbps、460.8kbps、921.6kbps(nominal 1Mbps)
Controller scan rate Vary from IO network baud rate setting, the fastest 40ms
Terminal block Removable Euro-style terminal block, wiring gauge: two 2.5mm2
Size 209mm x 129.5mm x 51mm (High x Width x Depth)*
Installation Screw mounting
Operating temperature 0 ~ 60 ºC (32 ~ 140 ºF)
Storage temperature -40 ~ 85 ºC (-40 ~ 185 ºF)
Operating relative
humidity 5 ~ 95% (non-condensing)
Vibration 10-500Hz, acceleration < 10m/s2
Contaminants withstand PCBA double-side coating; dust particle size > 0.5uis, < 18,000 parts/L
Note Some type of module has different size, e.g. Logic Protection module.
Item Specification
Number of channels 16
Temperature input types Thermocouples (TC) E/J/K/N/R/S/T/B
Resistance Temperature Device (RTD),
Pt10/Pt100/Cu50/Cu100/BA1/Cu10/Cu53, 3-wire
Input span 0~+128mV or 0~+32mV, acquired by module temperature input type
setting
Cold junction Reference junction temperature measured by one / two channels of RTD
compensation input, and compensated in controller by software
A/D resolution 16 bit
Scan time 2 times/second
Accuracy 0.2% of full scale over the full operating temperature range
Interference resistance CMRR ≥ 120dB@250VAC,NMRR ≥ 60dB@50/60Hz
Isolation Channel to channel ≥ 250VAC@50/60Hz
Channel to ground ≥500VAC@50/60Hz
Channel to system ≥1500VAC@50/60Hz
Power consumption Typical 2.1W, Max 2.5W
Heat dissipation Typical 2.1W, Max 2.5W
Item Specification
Number of channels 16
Output type Relay output, dry contact
Max load current Resistive Load - 12A/250VAC; 12A/30VDC
Inductive Load - 7.5A/250VAC; 6A/30VDC
Max response time on 15 ms typical
Max response time off 10 ms typical
Contact material AgNi
Contact life Electrical operations: 200,000 (AC); 100,000 (DC)
Mechanical operations: 30 x 106 (AC); 50 x 106 (DC)
Frame rate Refresh all channels within 1ms;
System dependent scan rate for control purposes
Isolation Channel to channel ≥ 1000VAC@50/60Hz
Channel to ground ≥2500VAC@50/60Hz
Channel to system ≥3000VAC@50/60Hz
Power consumption Typical 1.3W, Max 11W
Typical 1.3W, Max 27W (including heat dissipation of external control
Heat dissipation loop on relay contact)
Item Specification
Number of channels 16
Discrete output capacity Each channel with Max. 100mA@24V dc
Frame rate Refresh all channels within 1ms;
System dependent scan rate for control purposes
Isolation Channel to channel isolation, determined by connected relay board
Channel to ground ≥2500VAC@50/60Hz
Channel to system ≥3000VAC@50/60Hz
Power consumption Typical 1.3W, Max 4W
Heat dissipation Typical 1.3W, Max 4W
Item Specification
Number of channels 1
Frequency range 1-20,000Hz
Input Span 50mVrms~40Vrms
Speed
input Signal type sine wave/triangle wave/square wave, or TTL signal
(Frequency) Speed sensor type Magnetic/eddy current/Hall/photoelectric
Accuracy 0.01%, notice that,
speed range 1~3600rpm, < 0.1rpm
speed range 3600~8000rpm, < 0.5rpm
Number of channels 6
Input Span ±10V, 0(4) - 20mA
AI A/D resolution 16 bit
Accuracy(@25 ºC) 0.1% of full scale range
Temperature drift Max 0.05% of the upper range value over full operating
Item Specification
Number of channels 2
Exciting frequency 1~3kHz
LVDT Signal span 3.5Vrms/7.0Vrms
Sensor type 3-wire, 6-wire
Measurement accuracy 0.25%
Number of channels 2
Input span ±10V, ±5V, 0(4) - 20mA
A/D resolution 16 bit
Accuracy(@25 ºC) 0.1% of full scale range
AI Max 0.05% of the upper range value over full operating
Temperature drift
temperature
Interference resistance CMRR ≥ 120dB@250VAC,NMRR ≥ 60dB@50/60Hz
Channel to channel ≥ 250VAC@50/60Hz
Isolation Channel to ground ≥500VAC@50/60Hz
Channel to system ≥1500VAC@50/60Hz
Number of channels 6
Input type Dry contact, current sink type
Input status indication Each channel has one LED for status indication
DI
Input filter Software filter, 3~50ms, default 24ms
Input wetting voltage 24V dc
Input current <3mA
Number of channels 2
Servo Output capacity -40mA ~ +40mA@120Ω
output Or -10V ~ +10V@20mA with Max. load 500Ω
Output accuracy 0.5%
Item Specification
Number of channels 8
Analog output 0(4)-20mA,0(1)-5V dc(Channel number 07 & 08)
Load capacity (current
output) Max. 1kΩ
Load capacity (voltage
output) Min. 200kΩ
D/A resolution 12 bit
Frame rate Refresh all channels within 1ms;
System dependent scan rate for control purposes
Accuracy 0.2% of full scale over the full operating temperature range
HART Support HART protocol V5/V6/V7
All output channels can be configured as HART enabled individually
HART data update time: 5s@8 channels
Interference resistance CMRR ≥ 120dB@250VAC
Isolation Channel to channel ≥ 250VAC@50/60Hz
Channel to ground ≥500VAC@50/60Hz
Channel to system ≥1500VAC@50/60Hz
Power supply Dual redundant 24V dc (±10%)
Power consumption Typical 1.7W, Max 6.7W
Heat dissipation (250Ω
load) Typical 1.6W, Max 5.9W
2.4 Software
Software is required for all system components (controller, HMI, etc.) normal
operation, including operation software (OS) and OC 6000e platform software, All
software packages should be supplied to end user along with system hardware.
2.4.1 OS
Each iDPU controller (including communication control module) needs one QNX real-
time operating system.
Each HMI computer needs one Windows XP professional operating system.
An MS office package (2010 or later version) is required for each report server or HMI
which needs to configure or communicate with the report server.
To plan specific project hardware, the following steps can be used to roughly
calculate system components. The following calculation only considers basic
requirement and minimum amount of system hardware. Additional hardware
should be included according to customer specific requirements.
3.1.1 Controller
Normally, the controllers are dual-redundancy configured.
Each pair of iDPU controller can support up to 4 redundant iLink buses.
Note TC and RTD type signals can be configured in one MAI51 module, each type of input occupies
one side of module input (8 channels). Module quantity should be calculated accordingly.
Note Pulse input can be calculated together with DI point. Remember one DI module can only
provide 4 PI channels.
MDO53 = (AC or low voltage DC* control circuit DO points) x (1+ channel margin in
percentage) / 16
MDO54 = (DC control circuit DO points) x (1+ channel margin in percentage) / 16
Note 1) For some special modules, the module number should be calculated per its actual
occupied position, e.g. MDO54 - 3, logical protection module - 3.
2) For remote I/O, the bus number is calculated per actual module number.
3.2 Cabinet
OC 6000e Nexus recommends 5 standardized control cabinet/extension cabinet
designs. For each standard design, there will be a cabinet layout drawing and BOM
for reference.
Cabinet assembly defines a standard cabinet structure which includes all cabinet
components and accessories except I/O modules and cabinet framework.
Control cabinet assembly includes iDPU controller, power switch box, DC module,
iLink cable & bus extension module, DC power distribution terminal block, and other
basic installation accessories.
3.3 HMI
OC 6000e Nexus applies peer-to-peer network architecture, all HMI functions can be
realized on any system computer by configuration, which offers n+1 redundancy for
all HMI stations.
For system security and Intellectual Property protection, OC 6000e Nexus use
hardware dongle to protect all HMI applications. Each HMI computer must have
corresponding dongle and software to ensure the legal use of software.
HMI quantity usually is determined per customer operation requirement. In principle,
one control system should have one engineer station and one historian at least.
Operator stations are configured per customer requirement. Other types of stations
should be configured to meet system’s function extension requirements.
On some small DCS projects, some HMI functions can be integrated into one station
to reduce system’s HMI quantity, e.g. engineer station with historian function.
Basic requirements for HMI computer:
Industrial PC or brand computer
CPU:Dual core 2.6GHz or above
RAM: 1GB DDR or above
HDD: no specific requirement, recommend 160GB or above
Si l'équipement est utilisé d'une façon autre que celle indiquée par le
fabricant, la protection fournie par l'équipement peut être compromise.
At least one of system’s two power supplies should come from plant UPS
system.
4.7 Grounding
4.7.1 Cabinet grounding
There are two types of grounding in the OC 6000e Nexus cabinet according to
device voltage class:
Low voltage device grounding, for device with 24V dc power supply
High voltage device grounding, for device with 220V AC power supply
Each OC 6000e Nexus cabinet has one unique grounding point, which is directly
connected to cabinet framework.
High voltage devices are installed on a separated power panel which is insulated
with a cabinet mounting plate. The panel then connects to the cabinet grounding
bar through a grounding cable.
The controller mounting plate, IO module mounting pillars are connected by
grounding cables, and connect to the cabinet grounding bars.
AO (MAO50/MHO50)
DO (MDO53)
4.9 Interface
4.9.1 Information communication
Process data can be shared between the Nexus system & other device/systems via
communication interface.
The standard communication protocol can be used for data communication
between different control platforms.
It is not recommended to transmit real-time control command through
communication interface between different control platforms.
When interfacing with plant MIS/OA system, a firewall is a must. The information
can only be sent out from DCS. Receiving from outside to DCS is not allowed or
supported.
A and B are redundant controllers. Node number 1-80, 101-180 are for dual
redundant controllers, for example, 51 and 151 are a pair of redundant controllers.
Note For management convenience, DCS or DEH/ETS controller can be assigned a fixed ID.