www.4shared.com/folder/nYes8heM/STANDARDDOCS.

html

http://www.4shared.com/folder/f0K-a3Jx/1_online.html

Director, Applied Technology, Emerson Process Management, Singapore

Hardwiring MOV would require a lot of cable and system I/O cards. Therefore digital communications is used instead.
To fully take advantage of the MOV capability you would need 22 wires (11 pairs) and 16 system I/O channels to
make use of all the signals:
* Open/stop/close control = 3 DO and 4 wires
* Desired valve position control = 1 AO and 2 wires
* Emergency shut down = 1 DO and 2 wires
* Valve position status (limit switches) = 2 DI and 3 wires
* Percentage open = 1 AI and 2 wires
* Available for control = 1 DI and 1 wires
* Local/remote switch = 1 DI and 1 wires
* Motor running open direction = 1 DI and 1 wires
* Motor running closed direction = 1 DI and 1 wires
* Torque switch tripped = 1 DI and 1 wires
* Percentage torque = 1 AI and 2 wires
* Motor thermostat tripped = 1 DI and 1 wires
* Battery condition low = 1 DI and 1 wires
TOTAL = 16 I/O and 22 wires
Multiply this by the number of MOV and it translates into large numbers of I/O and cables
You could eliminate some of these signals, but your plant operations and maintenance would not fully benefit from the
capabilities of the MOV. Partial device functionality, partial plant benefits. Using digital technology plants get the full
advantage of their MOV

Moreover, digital communication enables remote configuration and centralized diagnostics of the MOV which cannot
be done using hardwired signals. That is, digital communication means less wiring and more functionalit

@Ahmad: No. You can set the fieldbus macrocycle as fast as the scan time of traditional I/O cards. That is, if you set
the DI/DO card scan time to 1000 ms and the fieldbus macrocycle to 1000 ms they will be equally fast. You can set
the fieldbus macrocycle to 150 ms or faster depending on the system. However, considering that MOV normally take
a long time to open, 1000 ms is sufficient
Considering cost and time behoof, most of the End Users preferred to use the digital fieldbus (serial link, fault tolerant
network) for MOV (2 wire SMART type actuator) monitoring and control purpose, for applications which involves large
numbers of MOV located adjacent to each other in unit process area, tankform area ,...etc.
Communication between Master Control System (MCS) (i.e. dedicated system for MOV control) and field actuator
(i.e. microprocessor based field control unit) shall be via 2 wire cable loop ( field/ communication cable) of digital
fieldbus, preferably using protocol such as MODBUS, Fieldbus, Profibus, DeviceNet or Proprietary by electrical
actuator manufacturer.
MCS shall be a microprocessor based 2 wire SMART type control system and perform the tasks of bus master, data
collector, data concentrator, operator interface , protocol converter and be a slave to a host system. Generally host
system such as Distributed Control System , PLC or computer shall be serial interfaced with MCS via redundant data
ports using either MODBUS RTU or MODBUS TCP/ IP protocol.
MCS shall be installed in the control room with an independent cabinet. All signals from the MCS to the field units
shall be suitable for transmission over a 2 wire twisted pair cable with overall screen and shall use a current loop
serial data communication. This cable shall be connected from the MCS to each field unit in turn and then back to the
MCS.
The MCS shall be configured fully redundant to provide full fail safe protection. The two control unit will operate in
HOT STANDBY mode installed in single panel with control automatically transferred from primary to standby in the
event of a failure , without affecting the communication with field units. Removal and on line replacement of
communication card shall be possible, without affecting the communication.
Loss of power to anyone device on the field cable shall not cause loss of communication with the remaining devices
connected to the communication cable.
Selection of 2 wire loop protocol is mainly depends on single loop distance limitation w.r.t. numbers of field control
unit (i.e. actuators connected in loop ) and scan time (i.e. time response).
Single loop distance limitation for MODBUS /fieldbus 2 wire loop is 1200 metres without repeaters in generally.
Numbers of field control unit and scan time loop varies with manufactures. For longer distance loop, repeater and
other required accessories cost is considerable. Hence same needs to be reviewed on case to case basis.

@Shahram: by using FOUNDATION fieldbus you eliminated the need for an itnermediate "master control system"
(gateway). All DCS today support FOUNDATION fieldbus natively today so you network MOV direct to the DCS. This
is the ultimate and simplest way to network MOV available. No Modbus register data mapping required. Every I/O
signal, every piece of diagnostics, and all configuration settings available without mapping a single register

IBM Power 770 server

Reliable, secure systems for your critical information

Product details
Browse & buy
Accessories

Overview
Features & benefits

Specifications
Performance data

Configuration
Options

Per building block

System maximum

Processors

16 x 3.8 GHz POWER7+

processor cores or
12 x 4.2 GHz POWER7+
processor cores

64 x 3.8 GHz POWER7+

processor cores or
48 x 4.2 GHz POWER7+
processor cores

Sockets

Four

Sixteen

Level 2 (L2) cache

256 KB L2 cache per

core

256 KB L2 cache per

core

Level 3 (L3) cache

10 MB L3 cache per
core (eDRAM)

10 MB L3 cache per core

(eDRAM)

Enterprise Memory

Up to 1 TB of 1066 MHz
DDR3
Active Memory

Up to 4 TB of 1066 MHz
DDR3
Active Memory

Configuration
Options

Per building block

System maximum

Expansion

Expansion

Integrated SAS bays for Up to six SFF SAS drive

Solid State Drives
bays
(SSD) or
Hard Disk Drives (HDD)

Up to 24 SFF SAS drive

bays

Integrated media bays

One slimline for SATA

DVD-RAM

Four slimline for SATA

DVD-RAMs

Integrated PCI adapter

slots

Six PCIe Gen2 slots

24 PCIe Gen2 slots

Integrated
multifunction card

Up to one per enclosure: Up to four per system:

Dual 10 Gb + Dual 1

Dual 10 Gb + Dual 1

Gb

Gb

Integrated SAS
controllers

Two SAS DASD/SSD

controllers
One SATA media
controller

Eight SAS DASD/SSD

controllers
Four SATA media
controllers

Other integrated ports

Three USB; two HMC;

two SPCN

Nine USB; four HMC;

four SPCN

GX slots (12X)

Two

Eight

Expansion features (optional operating system dependencies)

I/O expansion

Up to 4 PCIe 12X I/O

drawers
Up to 8 PCI-X DDR 12X
I/O drawers

High-bandwidth PCI
adapters

6 Gigabit SAS
8 Gigabit Fibre Channel

Up to 16 PCIe 12X I/O

drawers
Up to 32 PCI-X DDR 12X
I/O drawers

Expansion features (optional operating system dependencies)

10 Gigabit Ethernet
10 Gigabit Fibre Channel over Ethernet
40 Gigabit QDR
Other PCI adapters
supported

SAS, Fibre Channel, Ethernet, SCSI, WAN/Async,

USB, Crypto, iSCSI

PowerVM virtualization technologies

POWER Hypervisor

LPAR, Dynamic LPAR; Virtual LAN

(Memory to memory interpartition
communication)

PowerVM Standard Edition

(optional)

Micropartitioning with up to 20
micropartitions per processor; Multiple
Shared Processor Pools; Virtual I/O Server;
Shared Dedicated Capacity

PowerVM Enterprise Edition

(optional)

PowerVM Standard Edition plus Live

Partition Mobility (LPM)1 and Active
Memory Sharing (AMS)2

RAS features

Processor Instruction Retry

Alternate Processor Recovery
Selective dynamic firmware updates
Chipkill memory
Memory DRAM sparing
ECC L2 cache, L3 cache
Redundant service processors with automatic
failover3
Redundant system clocks with dynamic failover3
Hot-swappable disk bays
Hot-plug/blind-swap PCI slots
Hot-add I/O drawers
Hot-plug power supplies and cooling fans
Dynamic Processor deallocation
Dynamic deallocation of logical partitions and PCI
bus slots
Extended error handling on PCI slots

Redundant power supplies and cooling fans

Active Memory Mirroring (optional)
Capacity on Demand
features (optional)

Processor and/or Memory CUoD

Elastic Processor and/or Memory CoD
Trial Processor and/or Memory CoD
Utility CoD
Power Enterprise Pools4

Operating systems

AIX, IBM i and Linux for Power5

Power requirements

Operating voltage: 200 V ac to 240 V ac

Power consumption: 1,925 watts maximum per
enclosure

System dimensions

Power 770 rack drawer building block:

6.9 in. H (4U) 19.0 in. W 34.0 in. D (174 mm
483 mm 863 mm)
Weight 155 lbs (70.3 kg)6

Warranty (limited)

Nine hours per day, Monday through Friday

(excluding holidays), next business day for one year
at no additional cost; onsite for selected
components; CRU (customer replaceable unit) for
all other units (varies by country). Warranty service
upgrades and maintenance are available.

Live Partition Mobility is not supported on IBM i 6.1

Active Memory Sharing requires AIX 5.3-12 SP5, IBM i 6.1 or later, SUSE Linux
Enterprise Server 10 SP4 for Power or later, or Red Hat Enterprise Linux 6.1 or
later.
3
Requires two or more building blocks (nodes)
4
General availability, April 25, 2014
5
See Facts and Features for specific supported operating system levels
6
Weight will vary when disks, adapters and peripherals are installed
1