04 - ProSafe-RS Hardware Overview
04 - ProSafe-RS Hardware Overview
Figure 4-1
The hardware needed for above mentioned options will be described in the next paragraphs.
ProSafe-RS System
Application Logic
Control Module
Contol Module
Function Blocks
I/O
Input Variable
Scan
Output Variable
Output
Enable/Disable
Data Status
Data Value SCAN SEQUENCEData Status Data Value
Figure 4-2
The ProSafe-RS system is module based, as shown in Figure 4-3 and Figure 4-4.
§ ProSafe-RS modules are each designed to perform a specific application such as critical
control or I/O handling.
§ The type of module (and number of each) in a system depends on the application. Any two
systems are not necessarily the same.
Figure 4-4
Figure 4-5
In the Figure 4-5, ProSafe-RS modules in a basic SCS are illustrated:
1. The Power Supply Module is connected to a 100 to 120VAc or 220 to 240VAc or 24VDC
main source and supplies insulated +5V and +24V to each installed I/O module through the
back board.
2. The Control Module executes the configured control scheme. It is able to execute any
combination of two control languages and supervise its I/O modules to provide discrete
regulatory control.
3. I/O modules are configurable modules which act as interfaces between control modules and
field signals, offering a analog inputs and discrete input/output capabilities.
a. Analog data of either 4 to 20 mA or 1 to 5 V/ 1 to 10 V is converted to data of 0 to
100% in the CPU process data input processing and stored in the input variables. This
means that the data values stored in the input variables have been normalized to
values between 0 and 100%. All data that requires normalization, such as
measurements from differential pressure transmitters, is automatically processed in
the process data input processing in this way. Subsequent conversion from data in the
range from 0 to 100% to data using engineering units can be performed freely in the
application logic.
b. The input digital signals are converted into the internal data in the safety control unit.
The ProSafe-RS digital input/output modules consist of the following types:
· SDV144: Non-voltage contact input, 16 Channels, Isolated Dry contact 24
VDC
· SDV531: 24V DC output (0.6 A/channel), 16 Channels, Isolated
Figure 4-6
Figure 4-7
1. ESB bus coupler module (Model: SEC401) is installed in the safety control unit for
communicating with the ESB bus interface module (Model: SSB401) installed in the safety node
unit. Generally, the ESB bus coupler modules are dual-redundantly configured.
2. ESB bus interface module (Model: SSB401) is installed in the safety node unit for communicating
with the ESB bus coupler module (Model: SSB401) installed in the safety control unit. Generally,
the ESB bus interface modules are dual-redundantly configured.
If a second (up to 9) Safety Node is required the SSB401 card has 2 connectors on the front (for
continuation of the ESB bus). The last Safety node will be terminated (special SSB front
connector, with only 1 connector).
In Figure 4-8 a schematic overview with the positions of the ESB modules have been illustrated.
The ProSafe-RS can communicate to other Yokogawa System using the Control Bus, also known as
Vnet.
The following options will be described:
1. Communication to other SCS systems.
2. Communication to the SENG and/or other computers equipped with a Vnet PCI card.
3. Communication to DCS CS3000.
CS 3000 HIS
V net
Safety
communication Safety Data to FCS
CS 3000 FCS
Safety Controller
Figure 4-10
If communication between two or more (ProSafe-RS) Safety Control Units is required then the
dedicated Yokogawa Control Bus is used, know as Vnet. Safety communication through Vnet allows
data to be sent and received between SCSs.
In the Figure 4-11 the control bus (Vnet) connections are illustrated between two SCS systems.
Communication over the control bus is Safe only if special function blocks are used within the
application program.
Figure 4-11
The minimum ProSafe-RS configuration includes one SCS and one SENG.
This SENG is Windows based PC with Control BUS Interface card (Vnet card).
Programs such as ProSafe-COM MULCOM and FAST/TOOLS can communicate to Vnet.
In the figure below a Vnet Interface Card is depicted. This card must be installed in (for example) the
SENG.
Figure 4-12
The CS3000 Integration Function of the ProSafe-RS provides a communication interface for
accessing ProSafe-RS SCSs via the Vnet from HISs and FCSs connected to a CS3000 system. This
function allows the SCSs to be operated and monitored from HISs using the same interface (windows)
used when monitoring FCSs. SCS data can also be accessed from FCSs using the same interface (tag
names).
Figure 4-13
Vnet
Ethernet Domain C
Vnet
Safety ENG HIS HIS/ENG SENG
Domain A
ENG
CGW CGW
Repeater
Safety FCS
Controller Safety Safety
Controller Controller
Figure 4-14
Using Vnet bus repeaters and Vnet optical repeaters can expand the Vnet connection within one Vnet
domain. Furthermore, a Vnet domain can be divided into several Vnet domains connected each other
using BCV and CGW. Passing through BCV and CGW enables communication between stations in
different Vnet domains. The system connected through BCV and CGW is a kind of CS 3000
Integration Structure.
A Vnet domain is a collection of stations connected to each other with one line of Vnet.
Limitations
Systems can be extended up to the following numbers.
· Hierarchical domains that can be connected: 16
· Stations that can be connected in a domain: 64
· Hierarchical stations that can be connected: 256
Figure 4-15
Specify a domain number in the range from 1 to 16 and a station number from 1 to 64.
The domain and station number can be set on the backside of the controller. Changing of the Domain
and Station Address must be done offline.
Figure 4-16
The following dip switch tables must be used for setting the addressing.
The Domain number can be set with the following table:
Figure 4-17
Figure 4-18
If the Safety system is extended with a Safety Node, the node setting must be done on the SSB401
card in the Safety Node on the front side (first remove the front cover). Changing of node numbers
must be done Off-line.
Figure 4-19
Figure 4-20
Figure 4-21
MPU memory
MPU memory
MPU memory
Figure 4-22
Figure 4-23
Figure 4-24
Figure 4-25
Figure 4-26