M01a30 40e 02 PRT18

Reference
System Integration OPC Station
IM 33M01A30-40E
IM 33M01A30-40E
2nd Edition
TocR-1
CENTUM VP
Reference
IM 33M01A30-40E 2nd Edition
CONTENTS
PART-R System Integration OPC Station
R1. Overview of System Integration OPC Station......................................R1-1
R1.1 System Configuration.................................................................................... R1-3
R1.2 Operating Environment.................................................................................. R1-4
R1.2.1 Hardware Requirements.................................................................. R1-5
R1.2.2 Software Requirements................................................................... R1-6
R2. SIOS Functional Details..........................................................................R2-1
R2.1 Process Data Access...................................................................................... R2-3
R2.1.1 SIOS Data Items............................................................................ R2-10
R2.1.2 SIOS Instrument Specific Data Items............................................ R2-15
R2.2 Messages....................................................................................................... R2-17
R2.3 Error Handling............................................................................................... R2-21
R2.4 Online Maintenance...................................................................................... R2-31
R2.4.1 Maintenance of OPC Server Information...................................... R2-32
R2.4.2 Maintenance of Data Item Information.......................................... R2-33
R2.4.3 Changing the Data Cache Size..................................................... R2-34
R2.5 Status Management...................................................................................... R2-35
R3. SIOS Engineering....................................................................................R3-1
R3.1 Setting Security Policies................................................................................ R3-2
R3.2 Creation of New SIOS..................................................................................... R3-6
R3.3 Configuration of OPC Server......................................................................... R3-9
R3.3.1 Automatic Configuration of OPC Server........................................ R3-10
R3.3.2 Manual Configuration of OPC Server............................................ R3-20
R3.4 Definition Files.............................................................................................. R3-22
R3.4.1 SIOS Definition File........................................................................ R3-23
R3.4.2 OPC DA Server Definition File....................................................... R3-25
R3.4.3 OPC A&E Server Definition File ................................................... R3-31
R4. SIOS Operation and Monitoring............................................................R4-1
R5. SIOS Maintenance...................................................................................R5-1
R6. SIOS Communication Performance......................................................R6-1
IM 33M01A30-40E 2nd Edition : Jun.05,2009-00

Blank Page
<R1. Overview of System Integration OPC Station> R1-1
R1. Overview of System Integration OPC

Station
The System Integration OPC Station (hereinafter referred to as “SIOS”) connects to a
control bus (V net or Vnet/IP) just like the HIS or FCS does. When connected to an OPC
server, the SIOS serves as a gateway between the CENTUM VP system and the OPC
server.
HIS can access the data on a PCS (PCS : Process Control System) such as DCS or PLC
connected to the OPC server. Not only the data on PCSs from Yokogawa but also the data
on PCSs from any third-party are accessible via the SIOS. The SIOS also converts alarms
and messages output by the PCS to those readable by the CENTUM VP and sends them to
the HIS.
The SIOS accesses OPC DA servers using the OPC DA 2.0 interface defined by the OPC
Foundation. It also accesses OPC A&E servers based on the OPC A&E 1.0 interface in
order to convert OPC events to CENTUM VP messages and relay them to HISs.
By using an OPC server that supports a desired third-party PCS, data on various systems
can be accessed without having to create special programs.
PC equipped with
HIS
the system generation function
Access process data

Control bus (V net)
Messages (A&E) Engineering
Acquire data items

SIOS (Browse)
FCS
Ethernet
OPC server
Bus unique to PCS
Controller of PCS Controller of PCS Controller of PCS

R010001E.ai
Figure Example of SIOS Connection (Based on a V net control bus)
IM 33M01A30-40E 1st Edition : Mar.23,2008-00

<R1. Overview of System Integration OPC Station> R1-2
n Difference between the SIOS and GSGW

The SIOS is mainly designed to monitor PCSs by integrating them into the CENTUM VP system.
Thus, the SIOS handles more data points than the GSGW. The SIOS also supports A&E, which
means the SIOS can be used to acquire messages into the CENTUM VP system.
On the other hand, the GSGW is mainly designed to connect subsystems. Thus, the GSGW
handles less data points than the SIOS and provides similar control functions available on the
FCS.
Table Comparison of SIOS and GSGW
Function SIOS GSGW

Builder, Builder,
Engineering
general-purpose editor general-purpose editor
Data acquisition Available Available
Data setting Available Available
Message Available Not available
Number of tags 100000 6000
Number of data points 2000000 (*1) 4000
Control function Not available Available
Maximum number of OPC servers DA server 16 units 4 units
that can be connected A&E server 16 units Cannot be connected
R010002E.ai
*1: This is number of data points for SIOS Instrument Tags. For SIOS Tags, the number of data points is the same as the number of
tags (i.e., 100000).

<R1.1 System Configuration> R1-3
R1.1 System Configuration

A system consisting of a SIOS and an OPC server can be designed in one of the following
configurations:
• The SIOS and the OPC server operate independently on different PCs.
• The SIOS and the OPC server coexist and operate on the same PC.
PC equipped with
HIS ENG
Control bus (V net)
SIOS
FCS
Ethernet
OPC server
Bus unique to PCS
Controller of Controller of Controller of

PCS PCS PCS R010101E.ai
Figure Configuration of SIOS/OPC Server System (Separated)
PC equipped with
HIS ENG
Control bus (V net)
SIOS
(The OPC server exists
on the same PC.)
FCS
Ethernet
Bus unique to PCS
Controller of Controller of Controller of

PCS PCS PCS R010102E.ai
Figure Configuration of SIOS/OPC Server System (Coexistent)

<R1.2 Operating Environment> R1-4
R1.2 Operating Environment

This section explains the PC hardware requirements and software requirements to run the
SIOS.

R1.2.1 Hardware Requirements

This section explains the hardware requirements to run the SIOS.
n Hardware
PC: IBM PC/AT compatible
CPU: 1 GHz or more. Operable on a PC with hyper-threading and multiple
CPUs.
Main memory size: For Windows Vista
2 Gbytes or more (Use of an ECC memory is recommended.)
For Windows XP
1 Gbytes or more (Use of an ECC memory is recommended.)
Network: Ethernet card (An Ethernet card is required if a V net bus is used.)
Control bus interface card (VF701 or VI701)
If an OPC server is installed in the same PC, a bus interface card to be
used by the OPC server is required.
Hard disk capacity: 10 Gbytes or more
Peripheral: Use of an uninterruptible power supply (UPS) is recommended.
n PC
For a PC in which to install the SIOS, select one running either of the following operating
systems:
• Windows Server 2003
• Windows Vista Business
• Windows XP Professional
The SIOS is mainly used to perform data acquisition and setting, so it is assumed to operate
continuously. Regular desktop PCs are not suitable for use as a SIOS, since they do not have
cooling fans and power supplies that are designed for continuous operation. On the other hand,
server PCs are designed for continuous operation and have reliable cooling fans and power
supplies. Among server PCs, those equipped with an ECC (Error Checking and Correcting)
memory that provides error detection and correction functions, or a hard disk RAID system, are
recommended for use as SIOS PCs.
If an OPC server runs on the same PC as the SIOS, the PC also needs to satisfy the hardware
requirements for the OPC server.
n Uninterruptible Power Supply (UPS)

When an uninterruptible power supply (hereinafter referred to as “UPS”) is connected to a PC,
the PC continues to operate for a while in the event of a power outage. When the power supply is
cut off, the UPS supplies power from a battery to the PC for the UPS OFF standby time specified
by the user. Upon elapse of the UPS OFF standby time, the UPS outputs a shutdown command
to Windows.
If a UPS is connected and the power supply is restored within the UPS OFF standby time, the
SIOS continues to operate as if nothing has happened. Even if the power outage continues
beyond the UPS OFF standby time, the SIOS can be turned off through the normal shutdown
sequence to protect the data stored in the hard disk. For the above reasons, it is recommended
to connect a UPS to the PC that functions as a SIOS. If a UPS is used, however, the software for
the applicable UPS needs to be installed and set up in the PC.

R1.2.2 Software Requirements

This section explains the software requirements to run the SIOS.
n Operating System
For a PC in which to install the SIOS, select one running either of the following operating
systems:
• Windows Server 2003
• Windows Vista Business
• Windows XP Professional
n Running an OPC Server on the Same PC

To run an OPC server on the same PC as the SIOS, the applicable OPC server software needs
to be installed in the PC. The OPC server needs to conform to either of the following interfaces:
• DA server: OPC DA 2.0 Custom Interface
• A&E server: OPC A&E 1.0 Custom Interface
n SIOS Functions
Install the following package to implement the SIOS functions:
• LBC2100 System Integration OPC Client Package
SEE
ALSO For installation of the package, see the following:
CENTUM VP Installation (IM 33M01A20-40E)
n Running Other Functions on the Same PC

Do not run software other than the SIOS functions and OPC server on the PC on which the SIOS
is run. The SIOS and GSGW cannot be installed and run on the same PC.

<R2. SIOS Functional Details> R2-1
R2. SIOS Functional Details

The SIOS consists of the following functions. This chapter explains each of these
functions:
• Process data access
• Message
• Download
• Status management
• Time synchronization
Process data
access communication
System status
Message communication Download communication
Read Write display communication
V net Time
Control bus driver
Process data access function Message function
Download function
Process data Status
Message processing Offline download
access processing management
Online download
function
Data cache Time

synchronization
fuction
SIOS definition
information
OPC DA client OPC A&E client
Basic SIOS functions
OLE/DCOM
OPC DA server OPC A&E server
R020001E.ai
Figure SIOS Functional Configuration

<R2. SIOS Functional Details> R2-2
n Overview of Each Function

The following gives an overview of each function of the SIOS.
l Process Data Access Function

The process data access function enables HIS or FCS to access the process data in the PCS
through control bus (V net or Vnet/IP). It converts CENTUM VP tag names to OPC item IDs
according to the definition information in the SIOS and then acquires applicable data from OPC
servers.
l Message Function
The message function is used to convert OPC alarms and events generated by A&E servers to
CENTUM VP messages and transfer them to HISs. It also notifies system alarms generated by
the SIOS to HISs.
l Download Function
The download function is used to perform offline and online downloads from builders.
l Status Management Function

The status management function is used to process system status and display communication
from HISs. It also monitors the operating status of the SIOS software itself.
l Time Synchronization Function

When the SIOS is started, the V net time synchronization service will be launched. Using this
service, the SIOS clock synchronizes with the V net time. The accuracy of clock time is the same
as that of the HIS.

<R2.1 Process Data Access> R2-3
R2.1 Process Data Access

The SIOS converts process data access requests received from HISs and FCSs via a
control bus (V net or Vnet/IP) to access requests containing data item names used by
applicable OPC servers, acquires data from the OPC servers or sets data in the OPC
servers, and then returns the results as process data access responses to the HISs and
FCSs via the control bus.
n Accessing Process Data

When the SIOS accesses a given data via an OPC server, it registers the applicable item ID in
the OPC server first. The SIOS contains a mapping table for the combination of CENTUM VP tag
names and Data item names and the corresponding OPC item IDs. When a process data access
request is received from an HIS or FCS via a control bus (V net or Vnet/IP), the SIOS references
this correspondence table to find the OPC item ID corresponding to the specified CENTUM VP
tag name and accesses the OPC server using the OPC item ID found.
The SIOS also has an internal data cache where it registers the OPC item IDs and data that have
been acquired.

n SIOS Tag and SIOS Instrument Tag

The SIOS has SIOS Tags and SIOS Instrument Tags. An SIOS Tag corresponds to an OPC item
ID. Data item name is fixed to “PV.”
An SIOS Instrument Tag is used for accessing multiple data items. A data item corresponds to
an OPC item ID. If the SIOS Instrument Tag is used for accessing the process data, instrument
faceplates of function blocks for another system can be displayed on the HIS. The max. number
of instrument faceplate types displayable on HIS is 120 per one project.
IMPORTANT
Currently, the system accessible using the SIOS Instrument Tags is Yokogawa’s STARDOM only.
Before you start engineering for the SIOS, see the STARDOM Engineering Guide for connecting
to the STARDOM.
SEE
ALSO For connecting to the STARDOM, see the following Engineering Guide:
Engineering Guide of CENTUM/ STARDOM Integration (TI 34P02K41-01E)
The figure below shows examples of accessing process data using an SIOS Tag and using an
SIOS Instrument Tag.
Accessing process data using an SIOS Tag
SIOS tag Data item name OPC item ID
FIC1001SV PV FCJ01 ! FIC1001.SV
Accessing process data using an SIOS Instrument Tag

Data item name
SIOS instrument tag OPC item ID
FIC1001 SV FCJ01 ! FIC1001.SV
PV FCJ01 ! FIC1001.PV
MV FCJ01 ! FIC1001.MV
FIC1001
NPAS_PID
Function Block of Other

PH FCJ01 ! FIC1001.PH System (Example of
Yokogawa STARDOM)
PL FCJ01 ! FIC1001.PL
SIOS instrument type
DA Instrument
Description
File (*1)
*1: The DA instrument description file contains definitions such as the function block type,
data item name and data type for each function block type of the connected system.
This file is provided for each connected system type.
R020109E.ai
Figure Two Data Access Methods of SIOS

n Referencing Data
The SIOS has an internal data cache used for referencing data. Once the SIOS acquires a
data item from an OPC server, the data item is registered in the SIOS’s data cache. The data
item registered in the data cache remains registered in the original OPC server. Every time a
change to the data is notified by the OPC server, the SIOS refreshes the data in the data cache.
Here, access by the SIOS to the process data and refreshing of the data on the OPC side occur
asynchronously.
If the data specified in a process data reference request exists in its data cache, the SIOS returns
the applicable data in the data cache as a response. If the specified data is not registered in its
data cache, the SIOS returns a data status “NRDY,” acquires the corresponding data from the
OPC server, and then registers the data in its data cache. The SIOS continues to return NRDY
until the data is registered in the data cache.
When accessing data that has not been registered in the data cache, for numeric data, it returns
0; while for CHR type data, it returns the default character string (NOT_READY). The user can
change a desired default character string for CHR type data.
(3) Return NRDY
Reference process data

Tag name: FIC1001
Data item name: PV
(1) Look up in the data cache

Data cache
Data item
(2) Look for Tag-Item conversion information Tag name name Data value ODAT/OTIM OQUA OERR
FIC1001 PV 50.0 **** 0 0
Tag-Item conversion
Data information
item
Tag name name
FIC1001 MV OPC item ID
(4) Access the OPC DA server

PV OPC item ID • Register an item
FIC1002 MV OPC item ID • Read data
PV OPC item ID
(5) Register data in the data cache
OPC DA server
Data refresh
R020102E.ai
Figure Data Reference

n Setting Data
After receiving a data setting request from an HIS or FCS, the SIOS executes a write processing
to the applicable OPC server. At this time, the SIOS also registers the data in its data cache. If the
corresponding data item name does not exit in the data cache, the SIOS establishes a session
with the OPC server, registers the data item name in the data cache, and then writes the data.
In the case of a write request, the SIOS returns a response without waiting for completion of the
requested data write on the OPC server.
n Appending the LongLife Attributes

The LongLife attributes are automatically appended to the following data among all the data
registered in the data cache. The LongLife attributes are appended so that the data that is
continuously referenced will not be deleted from the data cache at the wrong timing as a result of
data cache garbage collection.
• Trend acquisition data
• Inter-station communication data
n Data Cache Garbage Collection

The data cache garbage collection function includes LRU control and screening.
l LRU (Least Recently Used) Control

If the number of data registered in its data cache exceeds the data cache size, the SIOS deletes
from the data cache the data that has not been referenced for the longest time. This algorithm
is referred to as LRU (Least Recently Used) Control. In other words, data that are frequently
referenced by HISs have higher chances of remaining in the data cache. The data item deleted
from the SIOS’s data cache is also deleted from the OPC server. The data cache size of the
SIOS can be changed by online maintenance.

l Screening
In addition to implementing data cache control based on the LRU logic, the SIOS periodically
screens its data cache. In this screening, the SIOS deletes those data items remaining in its data
cache even though they have not been referenced for a long time. The purpose of this screening
is to prevent the data cache from continuing to store data that are no longer referenced, thereby
adding to the workloads on the OPC servers.
Specifically, a timer is provided for each group that has been registered in the OPC server, and
the data items in the group that has not been accessed after elapse of the timer are deleted from
the SIOS’s data cache and also from the OPC servers.
Specify whether or not to execute screening in the SIOS definition file. Screening is not specified
in the default settings. Specify the set time in the OPC DA server definition file. The default setting
is 120 seconds. Each timer needs to be set to an integer multiple of the screening period (10
sec).
Note that on the data having the LongLife attribute, screening is always valid. The data having
the LongLife attribute are deleted after 12 minutes if they are not referenced during that period.
SEE
ALSO • For more information about the SIOS definition file, see the following:
R3.4.1, “SIOS Definition File”
• For more information about the OPC DA server definition file, see the following:
R3.4.2, “OPC DA Server Definition File”
The operation of data cache screening is shown below. Screening is carried out at 10-second
periods. As shown in the figure, the time until data is deleted from the data cache varies between
the result of (set time - screening period) and the set time.
Access from an HIS
(Timeout = 3 Ts)
Register in
the cache
0 (Default) 0 (Reset)
Timer count changes 0 Ts 1 Ts 1 Ts 2 Ts 3 Ts
Screening
period (Ts)
Set Time – Screening period
Set Time
Delete from the data cache

R020104E.ai
Figure Screening

n Data Type Conversion

If a process data access request is received from an HIS or FCS, the SIOS performs data type
conversion between the CENTUM VP system and the applicable OPC server.
l CENTUM VP Data Types

The table below lists the data types used by the CENTUM VP system.
Table CENTUM VP Data Types
Data type Name
I16 Signed 16-bit integer
U16 Unsigned 16-bit integer
I32 Signed 32-bit integer
U32 Unsigned 32-bit integer
F32 32-bit single-precision floating-point data
F64 64-bit double-precision floating-point data
CHR Character string data
R020105E.ai
l OPC Server Data Types

Data returned by OPC servers are VARIANT type data. The VARIANT data types are defined in
the table below. The SIOS cannot handle VT_CY among the data types listed in the table, nor
can it handle vendor-specific data types not listed in the table.
Table OPC Server Data Types
Data type Name Number of bytes
VT_I1 Signed 8-bit integer 1
VT_UI1 Unsigned 8-bit integer 1
VT_R4 32-bit single-precision floating-point data 4
VT_R8 64-bit double-precision floating-point data 8
VT_CY 8-character currency data string (4-digit fixed-point data) 8
VT_DATE The day/time of the year 8
Character string
VT_BSTR UNICODE and NULL characters are appended at the end of Variable length
a VT_UI4 character string.
VT_BOOL Same with VT_I1. 0: FALSE, -1: TRUE 1
R020106E.ai

l Data Type Conversion Rules
When acquiring data in response to a process data access request, the SIOS converts the
data returned from the OPC server to the applicable CENTUM VP data type according to the
conversion table. In this data type conversion, all data other than CHR type data are converted to
the data with data status.
When setting data, set it in the CENTUM VP data type corresponding to the applicable OPC data
type. If the specified data type violates the conversion rules, the setting request generates an
individual data error.
Table Data Type Conversion Rules
CENTUM VP
data type I16 U16 I32 U32 F32 F64 CHR
OPC data type
VT_I1 Yes
VT_UI1 Yes
VT_I2 Yes
VT_UI2 Yes
VT_I4 Yes
VT_UI4 Yes
VT_R4 Yes
VT_R8 Yes
VT_BOOL Yes (*1) Yes Yes
VT_DATE Yes (*2)
VT_BSTR Yes (*3)
R020107E.ai
Yes: The SIOS performs data type conversion between the CENTUM VP system and the OPC server.
Blank: The SIOS does not perform data type conversion between the CENTUM VP system and the OPC server.
*1: In a data conversion from VT_BOOL to I16, the data is converted, as shown below:
VT_BOOL --> 16:
0 (FALSE) --> 0, -1 (TRUE) --> 1
I16 --> VT_BOOL:
0 --> 0 (FALSE), 1 --> -1 (TRUE)
*2: When data is read, the local time is returned in the following format:
PV = “yyyy/mm/dd”
PV2 = “hh:mm:ss.nnn”
(yyyy: Year, mm: Month, dd: Day, hh: Hours, mm: Minutes, ss: Seconds, nnn: Milliseconds)
When setting data, specify “yyyy/mm/dd” in PV (item name) and “hh:mm:ss.nnn” in PV2. The SIOS combines these two
character strings and sets “yyyy/mm/dd hh:mm:ss.nnn.” The combined character string is converted to a format appropriate for
the locale setting of the SIOS.
*3: If data containing more than 16 characters is read from an OPC server, the SIOS returns the first 16 characters by cutting off the
17th and subsequent characters. If the read data contains less than 16 characters, the blank digit or digits are filled with a NULL.
When setting data containing less than 16 characters, fill the blank digit or digits with a NULL.

R2.1.1 SIOS Data Items

The SIOS stores the following information for the purpose of controlling the SIOS
instrument tag and SIOS tag.
• Tag management information
• Data status
• Data item qualifier
n Tag Management Information

The SIOS stores the following data as the tag management information. Among these data
items, the representative data items of the SIOS instrument will be reflected in ODAT, OTIM,
OQUA and OERR. When the value of the representative data item is updated, ODAT, OTIM,
OQUA and OERR are also updated.
The representative data item is set to PV in the default settings. It can be changed in the DA
instrument description file.
Table Tag Management Information
Data Item Data Type Explanation
ODAT CHR Time stamp: Most recent data update date
OTIM CHR Time stamp: Most recent data update time
OQUA U32 Quality flag that indicates the data quality
SH F32 Scale high limit of the measured data
SL F32 Scale low limit of the measured data
MSH F32 Scale high limit of the output data
MSL F32 Scale low limit of the output data
OPMK I16 Operation mark
BTYP CHR Instrument type
OERR U32 Error code
R020110E.ai
l Time Stamp
Together with data, the SIOS stores in its data cache the time at which the data was read.
Time stamps can be acquired via a command specifying ODAT or OTIM as the data item name.
A command specifying ODAT returns the date field of the time stamp, while one specifying OTIM
returns the time field of the time stamp. To handle time stamp data, the clock of the CENTUM VP
system and that of each connected OPC server need to be synchronized. Time stamps are converted
to a format appropriate for the locale setting of the SIOS.

l Quality Flag
Data quality is indicated by a Quality flag consisting of eight bits. The SIOS stores Quality flags
of data in its data cache. Quality flags can be read via a command specifying OQUA as the item
name. Quality flags are also mapped in the data statuses.
SEE
ALSO For data status mapping, see the following:
“n Data Status”
The Quality flag structure and meaning of each bit value are explained below.
Quality flag structure
QQSSSSLL
QQ: Quality bit
SSSS: Substatus bit
LL: Limit bit
Table Quality Flag Structure and Meanings of Values
QQ Quality value Meaning
00 00SSSSLL BAD
01 01SSSSLL Uncertain
10 10SSSSLL –
11 11SSSSLL GOOD
R020103E.ai
l SH and SL Data
The SH and SL data stored in the SIOS’s data cache are those predefined on an ENG. If the
request from an HIS or FCS specifies an SH or SL, the SIOS does not access OPC servers, but
directly returns the applicable SH or SL data stored in its data cache.
l MSH and MSL Data

The MSH and MSL data stored in the SIOS’s data cache are those predefined on an ENG. If the
request from an HIS or FCS specifies an MSH or MSL, the SIOS does not access OPC servers,
but directly returns the applicable MSH or MSL data in its data cache.
l SSH and SSL Data

The SSH and SSL data stored in the SIOS’s data cache are those predefined on an ENG. If the
request from an HIS or FCS specifies an SSH or SSL, the SIOS does not access OPC servers,
but directly returns the applicable SSH or SSL data in its data cache.
l Operation Mark
The data item OPMK is set when an operation mark is assigned to a faceplate in the HIS. Even if
there is no data item corresponding to OPMK on the connected system, an operation mark can
be assigned in the HIS.

l Instrument Type
When a faceplate is displayed on the HIS, the value of Instrument Type BTYP is shown as the
Instrument Type of the connected system. The Instrument Type of the connected system is
changeable in the DA instrument description file.
l Error
If data access to an OPC server generates an error, the SIOS sets the returned error code in its
data cache. These error codes can be read via a command specifying OERR as the data item
name. The stored error code is cleared once data access to the applicable item is established
successfully. The value in this field is used as an error message on the requesting HIS.

n Data Status
The table below lists the data statuses returned from the SIOS and causes of respective
statuses. Each Quality flag returned from an OPC server and the status of communication with
the OPC server are mapped in the data status, as shown below.
Table Mapping to Data Status
Data status Data value OPC Cause

Quality flag
• Communication error between the SIOS and the OPC server
BAD 0x80000000 BAD • The OPC server is down.
• OPC client error
QST 0x40000000 Uncertain
• The OPC server is not connected.
NRDY 0x00001000
• The data does not exist in the data cache.
NORMAL 0x00000000 GOOD
R020108E.ai
l Data Corresponding to Data Status BAD or QST

• If the data status is BAD, the previous data is returned in the case of both numeric value
data and CHR type data.
• If the data status is QST, the data notified by the OPC server is returned in the case of both
numeric value data and CHR type data.
l Conditions in Which an Error Data Status Occurs

The data status changes according to the Quality flag. If one of the following conditions occurs,
however, the SIOS changes the data status:
• Abnormal operation of the OPC client
The SIOS internally monitors the operation of the OPC client. If an abnormal operation of
the OPC client is detected, the SIOS returns BAD to all data reference requests.
• Unable to access the OPC server
If the SIOS is unable to access the corresponding OPC server after receiving a process
data reference request, it sets BAD as the data status of the requested data item in the
applicable OPC server. BAD is cancelled after the SIOS has successfully accessed the
OPC server and acquired the data from the OPC server. In this case, the SIOS sets the data
status according to the content of the Quality flag received from the OPC server.
• The OPC server is down
If the OPC server has shut down or stopped due to an error, the SIOS changes the data
status of the applicable data in its data cache to BAD.
• Response error from the OPC server
If an error is returned from the OPC server, the SIOS changes the data status of the
applicable data in its data cache to BAD.
The OPC server returns an error in the following conditions:
• The SIOS specified an invalid OPC item ID or access path.
• The OPC item ID has been deleted from the OPC server.

l Acquiring a Data Status
The data statuses can be acquired by adding #PV after the data item name of the SIOS tag when
calling it on HIS.
l Validity Check of Process Data

Validity of acquired data can be checked from the data status or Quality flag of the data.
• Data statuses can be referenced via a command specifying “#PV” as the data item name.
• Error codes generated between the SIOS and each OPC server can be referenced via a
command specifying “OERR” as the data item name.
• Quality flags of OPC data can be referenced via a command specifying “OQUA” as the data
item name.
n Data Item Qualifiers

The data item qualifier is used to check the status of the tag mark displayed on the faceplate or
the data setup. There are two types of data item qualifiers; for data reference and for data setup.
Table Data Item Qualifiers Used for Data Reference
Qualifier Data Type Explanation
A data item referenced as a character string such as MODE, BSTS or ALRM is
@ U32
returned as a 32-bit integer.
Only the status of the data that includes the data status is returned as a 32-bit
# U32
integer.
% F32 A value (0 to 100%) before the scale conversion is returned.
All alarm data is returned at once. “!” can be used only for the data item name
of ALRM.
! ALRM The alarm data that is returned includes the alarm name, alarm status, alarm
suppression on/off, and alarm flashing on/off.
“!” is used for HIS faceplate display.
? U32 Information of error regarding the data item with “?” appended is returned.
R020111E.ai
Table Data Item Qualifier Used for Data Setup

Qualifier Data Type Explanation
The specified data status is set up. The data statuses that can be set are either
& CHR CAL or NCL. The calibration status of the function block of the connected
system can be set or canceled.
R020112E.ai

R2.1.2 SIOS Instrument Specific Data Items

The SIOS instruments have the following specific data items.
• Block mode
• Alarm status
• Block status
• Data status
n Block Modes
In the data item MODE reference, a block mode name is returned as a character string,
consisting of up to eight single-byte characters. If you are referencing the data upon appending
the data item qualifier “@,” a 32-bit integer will be returned. The block modes and the
corresponding values are shown in the table below.
Note that the following block modes and the bit positions are reserved by the system. If using a
user-defined block mode, use another bit position.
Table Block Modes
Block Mode Value Name
O/S 0x80000000 Out of service
IMAN 0x08000000 Initialization Manual
TRK 0x04000000 Tracking
MAN 0x00800000 Manual
AUT 0x00400000 Automatic
CAS 0x00200000 Cascade
PRD 0x00100000 Primary Direct
RCAS 0x00080000 Remote Cascade
ROUT 0x00040000 Remote Output
R020113E.ai
n Alarm Statuses
In the data item ALRM reference, an alarm status name is returned as a character string,
consisting of up to eight single-byte characters. If you are referencing the data upon appending
the data item qualifier “@,” a 32-bit integer will be returned. If you are referencing the data upon
appending “!,” an ALRM type will be returned. The alarm statuses and the corresponding values
are shown in the table below.
Note that the following alarm statuses and the bit positions are reserved by the system. If using a
user-defined alarm status, use another bit position after defining it with the User-defined Status
Character String Builder.
Table Alarm Statuses
Alarm Status Value Name
AFLS 0x80000000 Alarm flashing status
AOF 0x40000000 Alarm inhibition
AF 0x20000000 Alarm detection
NR 0x00800000 Normal
R020114E.ai

n Block Statuses
In the data item BSTS reference, a block status name is returned as a character string, consisting
of up to eight single-byte characters. If you are referencing the data upon appending the data
item qualifier “@,” a 32-bit integer will be returned.
n Data Statuses
The CENTUM VP system includes data items with data statuses. The data statuses are 32-
bit integer data and are defined as shown in the table below. By referencing the data upon
appending the data item qualifier “#,” you can reference only the data with the data status.
Table Data Statuses
Data Status Value Name
BAD 0x80000000 Bad Value
QST 0x40000000 Questionable Value
NCOM 0x20000000 No Communication
NFP 0x10000000 Not From Process
PTPF 0x08000000 Path To Process Failed
CLP+ 0x04000000 Clamp High
CLP- 0x02000000 Clamp Low
CND 0x01000000 Conditional
CAL 0x00800000 Calibration
NEFV 0x00400000 Not Efective
O/S 0x00200000 Out of Service
MNT 0x00100000 Maintenance
IOP+ 0x00008000 Input Open High
IOP- 0x00004000 Input Open Low
OOP 0x00002000 Output Open
NRDY 0x00001000 PI/O Not Ready
PFAL 0x00000800 PI/O Power Failure
LPFL 0x00000400 PI/O Long Power Failure
MINT 0x00000080 Master Initialize
SINT 0x00000040 Slave Initialize
SVPB 0x00000020 SV Pushback
R020115E.ai

<R2.2 Messages> R2-17
R2.2 Messages
Various events (Simple, Condition, Tracking) notified from OPC A&E servers and system
alarms output from the SIOS are broadcast to a control bus (V net or Vnet/IP) as CENTUM VP
messages.
Messages are classified into the following two types:
• Events detected by the SIOS
Messages relating to operations of the SIOS itself, such as startup and shutdown of
the SIOS. These messages are notified to HISs as system alarms.
• Events notified from OPC A&E servers
Events notified from OPC A&E servers. These messages are displayed on the
message monitor window.
Event types and categories of messages to be received can be selected for each OPC
A&E server.
The engineering function acquires event category character strings and assigned
event category values from OPC A&E servers. The category values that should be
received are selected from among these category values and downloaded offline to
the SIOS in advance.
HIS
System alarm Message monitor

view window
Historical
SIOS
Arbitrary character string messages

System alarms
Source (event source)
Time (event generation time)
Message (message character string)
Simple
Condition
Tracking
OPC A&E server
R020201E.ai
Figure Message Flow

n Notification of Events Detected by the SIOS

Events detected by the SIOS are notified to HISs as system alarms.
Table SIOS System Alarms
Message
Alarm name Explanation
number
0353 SIOS start The SIOS was started.
0355 SIOS start error An error occurred while the SIOS was starting.
0356 SIOS online download successful
0357 SIOS online download error An error occurred during online download.
0360 SIOS OPC communication normal Communication with the OPC server returned to a normal state.
0361 SIOS OPC communication error An error occurred during communication with the OPC server.
0363 SIOS task error An irrecoverable error occurred in the task.
0365 SIOS task warning An error occurred in the task.
0367 SIOS station failed The station failed.
0796 UPS diagnosis error The UPS detected an error.
0797 UPS power shut-off The power supply to the UPS has dropped.
0798 Power restored to normal The power supply to the SIOS has been restored.
R020202E.ai
SEE
ALSO • For more information about SIOS system alarm messages, see the following:
Operating Messages (IM 33M05D20-40E)
• Message numbers 0796, 0797 and 0798 are output when the UPS is set up. For more information about
the UPS setup, see the following:
CENTUM VP Installation (IM 33M01A20-40E)

n Event Notifications from OPC A&E Servers

All event notifications from OPC A&E servers are sent to HISs as arbitrary character string
messages in the sequence message format (device number 9) regardless of the event type or
category.
The types of information notified in these character strings are explained below. These
information are notified as common attributes among other OPC event attributes. Vendor
definition information is sometimes appended to OPC event attributes, but the vendor definition
information is not notified.
l Transmitted Information
The information transmitted to HISs includes source information, generation time and message
character string.
• Source information
The source that generated the event, as well as the applicable server program name and
data item name.
• Generation time
The time based on the clock of the source. The SIOS does not change the time information.
• Message character string
A message is limited to 128 characters. Messages containing more than 128 characters are
cut off after the 128th character.
Table OPC Event Attributes (Common Attributes)
Attribute Explanation Transmission to HIS
Source Event source Yes
Time Event generation time Yes
Type Event type (Simple, Tracking, Condition) No
EventCategory Event category (vendor definition) No
Severity Severity No
Message Message character string relating to an event Yes
R020203E.ai
Yes: Notified to HISs

No: Not notified to HISs
n A&E Message Filter

A message filter can be set for each OPC A&E server to receive only the specified messages
from each server. Message filters need to be downloaded from the engineering function in
advance. The following two filter items can be set.
• Event type (Simple, Condition, Tracking)
• Event category
If an OPC A&E server does not support message filtering, messages of all event types and
categories from that server will be transmitted.

n Message Display
Events notified from OPC A&E servers are displayed on the message monitor window in the
format shown below, as arbitrary character string messages (print messages) of message
number 1303. To display events notified from OPC A&E servers on the message monitor window,
the display setting of the message monitor window needs to be adjusted on the HIS side.
Specifically, select the Display Sequence Messages check box in the registration dialog box of
the message monitor window.
The message monitor window also provides the filter dialog box that allows you to filter the
messages to be displayed as arbitrary character strings.
Display format:
OPC A&E server identifier character stringΔOPC A&E server aliasΔEvent source character
stringΔEvent message character string
(Note) Δ: Space
• OPC A&E server identifier character string (Fixed to 8 characters):

Identifier of the OPC A&E server in which the event generated. OPCSAExx (xx: 01 to 16)
• OPC A&E server alias (Variable length):
Alias of the OPC A&E server, having a variable length of up to 16 characters
• Event source character string (Variable length):
Information regarding the event source. An OPC event attribute.
• Event message character string (Variable length):
Message character string relating to the event. An OPC event attribute. A message consists
of a maximum of 128 characters including spaces. The portion exceeding the first 128
characters is deleted.
n Message Flow Control

To prevent broadcast messages from negatively impacting the communication loads of the
control bus, the number of messages sent from the SIOS is limited by the following rates:
• 2 broadcast frames per second
• Maximum 2036 bytes per broadcast frame

<R2.3 Error Handling> R2-21
R2.3 Error Handling

This section explains how the SIOS handles errors in the event of system malfunctions
and notifies these errors to HISs.
n Operations upon Occurrence of Malfunction

The following explains how the SIOS operates in the event of system malfunction and upon
recovery to a normal state.
l OPC Client Down

The SIOS periodically checks the operation of the OPC client. If unable to check the OPC client
operation for a period longer than the diagnostic monitoring time (default: 30 seconds), the SIOS
outputs a system alarm and changes the data status in its data cache to BAD. To correct this
condition and restore a normal state, the SIOS needs to be restarted.
l Communication Error between the OPC Client and an OPC Server

The following explains what happens when a communication error occurs between the SIOS and
an OPC server.
• The SIOS (OPC client) periodically diagnoses its communication with the PC running each
OPC server. If unable to check its communication with any PC for a period exceeding the
“OPC server response monitoring time” specified by the user, the SIOS terminates the
session with the OPC server. The SIOS outputs a system alarm and changes to BAD the
data status of every data item in its data cache corresponding to the applicable OPC server.
• The SIOS (OPC client) reestablishes a session with the OPC server at the “retry period”
specified by the user. After successfully connecting to the OPC server, the SIOS notifies
recovery to a normal state to the applicable HIS via a system alarm. The SIOS registers in
the OPC server the data items corresponding to the applicable OPC server that are stored
in the data cache of the SIOS, and resumes relay operation.
l Shutdown and Restart of the OPC Server

When an OPC server received an external shutdown request, the OPC server notifies the SIOS
(OPC client) that it will shut down.
• OPC DA server
After receiving the shutdown notification, the SIOS disconnects from the OPC DA server
and outputs a system alarm. It also changes to BAD the data status of every data item in
its data cache corresponding to the applicable OPC DA server. The SIOS (OPC DA client)
reestablishes a session with the OPC DA server at the “retry period” specified by the user.
After successfully connecting to the OPC DA server, the SIOS notifies recovery to a normal
state to the applicable HIS via a system alarm. The SIOS registers in the OPC DA server the
data items corresponding to the applicable server that are stored in the data cache of the
SIOS, and resumes relay operation.
• OPC A&E server
After receiving the shutdown notification, the SIOS disconnects from the OPC A&E server
and outputs a system alarm. The SIOS (OPC A&E client) reestablishes a session with the
OPC A&E server at the “retry period” specified by the user. After successfully connecting to
the OPC A&E server, the SIOS notifies recovery to a normal state to the applicable HIS via a
system alarm. The SIOS resets the Event Filter and resumes relay operation.

l Error between an OPC DA Server and a Device (Third-party PCS, Etc.)
If an error response is received from a connected device or when an error occurs in its
communication with a device, the OPC DA server sets the cause of the error in a Quality flag and
notifies the SIOS (OPC client) of the data change. The SIOS maps the cause specified in the
Quality flag in the data status.
l Failed Data Item Registration

If a data item defined in the CENTUM VP system is not registered in the OPC DA server, a
registration request involving that data item will fail. In this case, the requesting HIS can check
the generated error via a command specifying “Tag name.OERR.” The applicable data status
changes to BAD. A retry is attempted when an access is made again from the host.
n Communication Status Monitoring by System Tag Name

Assigning system tag names allows for monitoring of the connection status between the SIOS
and each OPC server. A system tag name can be defined for each server connected to the SIOS,
in order to indicate the status of connection between the server and the SIOS. System tag names
are defined in the SIOS definition file. If an OPC server is accessed using a defined system tag
name, the connection status between the SIOS and the applicable OPC server can be monitored
from an HIS.
l Defining a System Tag Name

Set the following items for each OPC server.
Table Definition of System Tag Name
Item Setting Remarks
Default tag names
• DA server: ddssDAnn
Set a tag name using up to 16 characters • A&E server: ddssAEnn
Tag name (*1) according to the naming rules for dd: Domain number
CENTUM VP tag names. ss: Station number
nn: OPC server number (01 to 16)
Data item name PV Fixed to PV
Data type CHR type Fixed to character string
R020301E.ai
*1: Defined system tag names cannot be assigned to OPC data item IDs as CENTUM VP tag names.
l Response Data
One of the character strings specified in the table below is returned in accordance with the status
of connection between the SIOS and the applicable OPC server.
Table Response Character Strings
Character string Meaning Remarks
The SIOS and OPC server
ONLINE
are connected properly.
The SIOS and OPC server The connection was terminated since the applicable data
OFFLINE
are disconnected. on the OPC server is not stored in the SIOS's data cache.
An error occurred in the YYYY: Category error code (0xEF00 to 0xEFFF)
0xYYYY-ZZZZZZZZ
session with the OPC server. ZZZZZZZZ: Detailed error code
R020302E.ai

n Error Notification
Errors are classified into the following three types:
• Errors that generate in the SIOS
Load error
• Errors that generate between the SIOS and an OPC server
OPC server down
OPC communication error
• Errors that generate between an OPC server and a device
Device down
Errors along the communication path
Respective errors are notified to HISs via the following methods:
• System alarm
• System alarm, system tag, data status
• Quality flag, data status, A&E message
System alarm
SIOS
System alarm
System tag
Data status
OPC server
Quality flag
Data status
A&E message
Device (third-party PCS, etc.)
R020303E.ai
Figure Error Notification

n Error Codes
The SIOS displays errors in the following format:
Category error code (16 bits) + Detailed error code (32 bits)
These error codes are notified to HISs as error codes in system alarms and also as character
strings indicating system tag names.
l Category Error Codes

A list of category error codes is shown below.
Table Category Error Codes (1/2)
Detailed
Category Value Meaning
error code
0xEF01 Invalid SUB-ID
0xEF02 Invalid code
Request 0xEF03 Invalid function
parameter error
0xEF04 Invalid number of request parameters (over 62)
0xEF05
Codes reserved for request parameters
to 0xEF0F
0xEF10 Yes SIOS system information read error
0xEF11 Yes SIOS definition file read error
0xEF12 Yes SIOS definition file check error
0xEF13 Yes OPC DA server definition file read error
0xEF14 Yes OPC DA server definition file check error
0xEF15 Yes OPC A&E server definition file read error
0xEF16 Yes OPC A&E server definition file check error
Definition
information error 0xEF17 Yes Online download difference file read error
0xEF18 Yes Offline download difference file read error
0xEF19 Yes SIOS system information check error
0xEF1A Yes Duplication error
0xEF1B No definition file
0xEF1C Yes BCV.I file read error
0xEF1D
Codes reserved for definition information errors
to 0xEF1F
0xEF20 Process data access failed
0xEF21 Yes Process data access diagnosis error
0xEF22 Message management function failed
0xEF23 Yes Message management diagnosis error
0xEF24 DA client failed
0xEF25 Yes DA client diagnosis error
0xEF26 A&E client failed
Internal error 0xEF27 Yes A&E client diagnosis error
0xEF28 Yes Internal error of the SIOS management service
0xEF29 Yes Internal error of the process data access function
0xEF2A Yes Internal error of the message management function
0xEF2B Yes Internal error of the DA client
0xEF2C Yes Internal error of the A&E client
0xEF2D
Codes reserved for internal errors
to 0xEF2F
R020304E.ai

Table Category Error Codes (2/2)
Detailed
Category Value Meaning
error code
0xEF30 Yes OPC server connection error
0xEF31 Yes OPC server disconnection error
0xEF32 Yes Group addition error
0xEF33 Yes Group deletion error
0xEF34 Yes Group attribute change error
0xEF35 Yes Item registration error
OPC
0xEF36 Yes Item deletion error
communication
error 0xEF37 Yes Item write error
0xEF38 OPC server shut down
0xEF39 Yes Error in communicating with an OPC server PC
0xEF3A Yes A&E filter setting error
0xEF3B Yes Item read error
0xEF3C
Codes reserved for OPC communication errors
to 0xEF3F
0xEF40 Yes The specified CENTUM VP tag name does not exist
0xEF41 The specified CENTUM VP data item does not exist
0xEF42 Yes Data type conversion error
Conversion error 0xEF43 The data type does not match the load file
0xEF44 CHR type data with BAD data status
0xEF45 Changing the data cache size during online download
0xEF46
Codes reserved for conversion errors
to 0xEF4F
0xEF50 Yes Socket error
0xEF51 Yes Load communication error
Load
0xEF52 Yes Online download error in the process data access function
communication
error 0xEF53 Yes Online download error in the A&E client
0xEF56
Codes reserved for load communication errors
to 0xEF5F
0xEF70 The SIOS received a shutdown request from an ENG
0xEF71 The PC was shut down or management service was closed
Station startup/ 0xEF72 Station startup failed
shutdown error 0xEF73 Recovery from online download error failed
0xEF74
Codes reserved for station startup/shutdown errors
to 0xEF7F
R020305E.ai

l Detailed Error Codes
The list below shows the detailed error codes appended to the category error codes for definition
information errors, conversion errors and load communication errors. The error codes returned
from Windows are appended to other category error codes.
• Detailed error codes for definition information errors
31 30 29 28 27 24 23 16 15 0
0 0 1 0 Type SvrNo Code
R020306E.ai
Figure Bit Structure of Definition Information Error Code
Bits 31 and 30: Severity code

Fixed to 0.
Bit 29: Customer code flag
This flag is used to prevent conflict with the error codes defined by the system (win 32).
Fixed to 1.
Bit 28: Reserved bit
Fixed to 0.
Bits 27 to 24: Type of the error file
These bits are valid only when the category code indicates a definition file error
(0xEF10 to 1A).
They are fixed to 0 for all other errors.
1: SIOS definition file
2: OPC DA server definition file
3: OPC A&E server definition file
4: Duplication check error
5: SIOS environment constant
Bits 23 to 16: OPC server number corresponding to the error file
These bits are fixed to 0 for errors not dependent upon OPC servers.
Bits 15 to 0: Code indicating the specific error
The codes indicated by bits 15 to 0 are listed below.
Table Error Codes Indicted by Bits 15 to 0 (1/3)
Error code Error
0x0001 Invalid redundancy enable action
0x0002 Invalid IP address of the other party
0x0003 Monitoring interval error in status monitoring communication
0x0004 Monitoring interval error in load equalization communication
0x0005 Monitoring interval error in process diagnosis communication
0x000A Invalid default character string for CHR type data
0x000B Invalid data cache screening specification
0x000C Range error for the number of data cache entries
0x000D Invalid OPC server number
0x000E Invalid OPC server alias
0x000F Duplicated OPC server alias
0x0010 Invalid OPC server execution host name
0x0011 Invalid OPC server program ID
0x0012 Range error for OPC server response monitoring time
R020307E.ai

Error code Error
0x0013 Retry period range error
0x0014 Invalid status system tag
0x0015 Group number range error
0x0016 Duplicated group number
0x0017 Invalid group name
0x0018 Duplicated group name
0x0019 Range error for data cache timeout value
0x001A Dead band range error
0x001B Range error for data refresh period
0x001C Invalid tag name
0x001D Duplicated tag name
0x001E Invalid number of OPC data conversion definitions
0x001F Invalid tag comment
0x0020 Invalid item ID
0x0021 Duplicated item ID
0x0022 Invalid access path
0x0023 Invalid data type
0x0024 Invalid CENTUM VP data item
0x0025 Invalid upper limit
0x0026 Invalid lower limit
0x0027 Invalid function restriction level
0x0028 Invalid host equipment name
0x0029 Invalid tag mark
0x002A Invalid double authentications
0x002B Invalid upper window name
0x002C Invalid help number
0x002D Invalid engineering unit symbol
0x002E Invalid switch position label
0x002F Invalid number of scale divisions
0x0030 Invalid scale reverse display
0x0031 Invalid label format
0x0032 Invalid event type mask pattern
0x0033 Invalid event category ID
0x0034 Duplicated event type mask pattern
0x0035 OPC DA server definitions contain no OPC group definition
0x0036 OPC group definitions contain no OPC data conversion definition
0x0037 OPC DA server definitions contain OPC A&E filter definition
0x0038 OPC A&E server definitions contain OPC group definition
0x0039 Invalid OPC DA server identifier
R020308E.ai

Error code Error
0x003A Redundancy is enabled, but the SIOS is not supported or there is no hardware
0x003B Range error in data cache screening specification
0x003C Range error in message flow control
0x003D Minimum time range error in OPC server response monitoring
0x003E Minimum retry period range error in OPC server response monitoring
0x003F Minimum data refresh period range error
0x0040 Minimum monitoring interval range error in status monitoring communication
0x0041 Retry interval range error in status monitoring communication
0x0042 Minimum monitoring interval range error in load equalization communication
0x0043 Retry interval range error in load equalization communication
0x0044 Minimum monitoring interval range error in process diagnosis communication
0x0045 Retry interval range error in process-to-process communication
0x0046 Retry interval range error in socket communication
0x0047 WDT reset timer range error
0x0048 Retry period range error in ProcDA communication
0x0049 Maximum length range error for server alias
0x004A Maximum length range error for group name
0x004B Maximum length range error for item ID
0x004C Maximum length range error for access path
0x004D Upper limit overflow
0x004E Lower limit overflow
R020309E.ai

• Data type conversion errors
Listed below are the detailed error codes appended to errors that generate when HIS-
specified data is converted to OPC data in a data setting operation from a HIS (errors of
category error code 0xEF42).
Table Detailed Error Codes (Data Type Conversion)
Detailed error code Data type Explanation
0x20000002 VT_I2 Signed 16-bit integer
0x20000004 VT_R4 32-bit single-precision floating-point data
0x20000005 VT_R8 64-bit double-precision floating-point data
0x20000006 VT_CY 8-character currency data string
0x20000007 VT_DATE The day/time of the year
0x20000008 VT_BSTR Character string
0x2000000B VT_BOOL Boolean TRUE/FALSE
0x20000011 VT_UI1 Unsigned 8-bit integer
R020310E.ai
• Detailed error codes for load communication errors

Listed below are the detailed error codes appended to errors whose category error code is
load communication error.
Table Detailed Error Codes (Load Communication Errors)
Detailed error code Error Explanation
Command sequence Packets were received in a sequence different from
0x20000001
error the specification.
A packet of a size different from the specification
0x20000002 Packet size error
was received.
A packet for which an abort flag is set to 1 was
0x20000003 Abort error
received.
The load was stopped
0x20000004 Stop error
(switching occurred during the load).
The packet sequence in the file transfer request is
0x20000005 Invalid packet number
invalid.
The XOR value in the file transfer request packet does
0x20000006 Inconsistent XOR
not match the XOR calculated from file fragments.
R020311E.ai

n Enable/Disable setting error codes

If data cannot be accessed due to some error between the SIOS and the OPC server or between
the OPC server and a PCS, “BAD” is set to the data status of the requested data.
You can enable or disable setting error codes. This can be done with the element <VframeError>
in the SIOS Definition File. The default is ‘enable.’ When setting error codes is enabled, causes of
the error are set to the item OERR.
If you use the SIOS Instrument Tag and want to identify the cause of the error, enable the error
code setting in the SIOS definition file. The SIOS will set the error code to the data item, OERR,
for each “BAD” data, and “****” is shown for all the “BAD” data in the instrument faceplate on
the HIS indicating an error code for each is set. To identify the “****”, enter its data item with a
question mark “?” added and read.
For example, if an error is raised when you try to register a data item of the SIOS Instrument Tag,
you can identify the cause of the error as follows:
Open the Tuning view for the SIOS Instrument Tag on the HIS. All the “BAD” data are shown
with “****”. To request the error code, enter the data item with a question mark “?” , send a Read
command, and the error code will be sent back. Check the error code with the error code table.
And you will know that the wrong OPC Item ID for the data item is the cause of the error.

<R2.4 Online Maintenance> R2-31
R2.4 Online Maintenance

The SIOS permits online maintenance of the following information:
• OPC server information
• Data item information
Group definition information, data item definition information
• Data cache size (SIOS definition)

R2.4.1 Maintenance of OPC Server Information

This section explains how the SIOS operates during online maintenance of OPC server
information.
n Maintaining Information on an OPC DA Server

When maintaining information on an OPC DA server, the SIOS terminates the session with the
OPC DA server and loads new definition information.
Until the series of operations are completed, the SIOS returns a data status NRDY to all data
reference requests from HISs targeting the data items on the applicable OPC DA server. At this
time, the SIOS returns the specified default character string(NOT_READY) for CHR type data
requests, and 0 for numeric value data requests. Data setting requests will generate an individual
data error.
n Maintaining Information on an OPC A&E Server

When maintaining information on an OPC A&E server, the SIOS terminates the session with the
OPC A&E server. Thereafter, the SIOS reestablishes a session with the server based on new
definitions and applies an A&E alarm filter.
Until the series of operations are completed, the SIOS does not relay the events notified from the
A&E server whose definitions have been changed.

R2.4.2 Maintenance of Data Item Information

Data item information includes group definition information and data item definition
information. These information are created for each OPC DA server.
If data item information was added, deleted or changed, the SIOS operates differently
during the maintenance session according to the action performed on data item
information.
n Added a Group
If a group was added, the applicable group information is added and item conversion information
is replaced. The data registered in the SIOS’s data cache is not changed.
n Deleted a Group
If a group was deleted, the applicable group information is deleted and item conversion
information is replaced. The item information belonging to the applicable group is deleted from
the SIOS’s data cache. Accesses to the items belonging to other groups are not affected.
n Modified a Group
If group information was modified, the applicable group information and item conversion
information are replaced. The SIOS deletes the modified group from the OPC DA server and
deletes from its data cache the item information belonging to the applicable group. Until the
series of operations are completed, the SIOS returns a data status NRDY to all data reference
requests from HISs targeting the data items belonging to the applicable group. At this time, the
SIOS returns the specified default character string(NOT_READY) for CHR type data requests,
and 0 for numeric value data requests. Data setting requests will generate an individual data
error. Accesses to the items belonging to other groups are not affected.
n Added a Data Item

If a data item was added, the item conversion information is replaced. Data accesses from HISs
are not affected.
n Deleted a Data Item

If a data item was deleted, the item conversion information is replaced. The SIOS deletes the
applicable data item information from its data cache, and also deletes the data item registered in
the OPC DA server. Accesses to other data items are not affected.
n Modified a Data Item

If a data item name was changed or other item definition information was modified, the item
conversion information is replaced. The SIOS deletes the applicable data item information from
its data cache, and also deletes the data item registered in the OPC DA server. Until the series of
operations are completed, the SIOS returns a data status NRDY to all data reference requests
from HISs targeting the applicable data item. At this time, the SIOS returns the specified default
character string(NOT_READY) for CHR type data requests, and 0 for numeric value data
requests. Data setting requests will generate an individual data error. Accesses to other data
items are not affected.

R2.4.3 Changing the Data Cache Size

This section explains how the SIOS operates after its data cache size has been changed.
n Changing the Data Cache Size

Changing the data cache size of the SIOS will cause the SIOS definitions to be replaced. The
SIOS deletes from each OPC DA server the data items stored in its data cache, terminates the
sessions with all OPC DA servers, and then clears the data cache. Until the series of operations
are completed, the SIOS returns a data status NRDY to all data reference requests. At this
time, the SIOS returns the specified default character string (NOT_READY) for CHR type data
requests, and 0 for numeric value data requests. Data setting requests will generate an individual
data error. Receiving operation for messages from A&E servers is not affected.

<R2.5 Status Management> R2-35
R2.5 Status Management

The status management function of the SIOS monitors the operating status of the SIOS
itself and resets the WDT (Watch Dog Timer) if necessary.
HIS
System status display view
System monitor
communication
SIOS
Status management
function
Software diagnosis
Task operating status
CPU load data
SIOS tasks
R020501E.ai
Figure Configuration of Status Management Function
n System Monitor Communication Processing

The SIOS sends to each HIS the information needed to display the system status display view on
the HIS.
SEE
ALSO For the items displayed on the status display window, see the following:
“n SIOS Station Status Display View” in R4, “SIOS Operation and Monitoring”
n Software Diagnosis
The SIOS diagnoses the operating statuses of the following three functions internally:
• Process data access processing
• Message function
• OPC client (DA, A&E)
The diagnosis task of the SIOS periodically polls information regarding each function. If a
response is not received within a specified time (response monitoring time), the SIOS determines
that the processing of the applicable function has stopped. The response monitoring time can be
set freely.

Blank Page
<R3. SIOS Engineering> R3-1
R3. SIOS Engineering

The engineering works for SIOS consist of setting security policies, creation of the new
SIOS and configuration of the OPC server for communication of SIOS.
IMPORTANT
For connecting to the STARDOM, see the STARDOM Engineering Guide before you start
engineering for the SIOS.
SEE
ALSO For connecting to the STARDOM, see the following Engineering Guide:
Engineering Guide of CENTUM/ STARDOM Integration (TI 34P02K41-01E)

<R3.1 Setting Security Policies> R3-2
R3.1 Setting Security Policies

In the PC of SIOS, the local security policies need to be configured. In the PC of OPC
server, the local security policies, user account, and DCOM needs to be configured.
n Local Security Settings

The local security policies need to be configured in both the PC of SIOS and the PC of OPC
server. However, for the PC of OPC server, this is required only if the operating environment is
Windows Vista, Windows XP, or Windows Server 2003.
1. Logon the PC using an account with the Computer administrator privilege. And then, choose
[Control Panel] – [Administrative Tools] – [Local Security Policy] from the [Start] menu of
Windows, so as to open the Local Security Settings window.
Local Security Settings
File Action View Help
Security Settings Policy Security Setting

Account Policies Network access : Do not allow anonymous enumeration... Disabled
Local Policies Network access : Do not allow storage of credentials or... Disabled
Audit Policy Network access : Let Everyone permissions apply to an... Disabled
User Rights Assignmen Network access : Named Pipes that can be accessed an... COMNAP, COMNODE, SQL\Q
Security Options Network access : Remotely accessible registry paths System\CurrentControlSet\Con
Public Key Policies Network access : Shares that can be accessed anonym... COMCFG, DFS$
Software Restriction Policie Network access : Sharing and security model for local a... Classic - local users authentica
IP Security Policies on Loc Network security : Do not store LAN Manager hash valu... Disabled
Network security : Force logoff when logon hours expire Disabled
Network security : LAN Manager authentication level Send LM & NTLM responses
Network security : LDAP client signing requirements Negotiate signing
Network security : Minimum session security for NTLM S... No minimum
Network security : Minimum session security for NTLM S... No minimum
Recovery console : Alllow automatic administrative logon Disabled
R030101E.ai
Figure Local Security Settings Window
2. Choose [Local Policies] – [Security Options]. And then click [Network access: Sharing and
security model for local accounts] from the list so as to open the dialog box for setting its
property.
Network access: Sharing and security model for local accounts... ?
Local Security Setting

Network access: Sharing and security model for local accounts
Classic - local users authenticate as themselves
OK Cancel Apply
R030102E.ai
Figure Property Sheet of Network access: Sharing and security model for local accounts
3. On the property sheet of Network access: Sharing and security model for local accounts,
select [Classic- local users authenticate as themselves].

n Creating User Account

When an OPC client of SIOS is connecting to the OPC server, the account name of “CTM_
PROCESS” will be used.
Therefore, the user account of “CTM_PROCESS” needs to be created in the PC of OPC server.
When createing the user account of “CTM_PROCESS”, the tool in the media of CENTUM VP
software should be used.
The path of tool is :
<DVD-ROM Drive> : \CENTUM\SECURITY\CreateCTMProcess.exe

n Configuring DCOM for OPC server
IMPORTANT
Regarding the settings on the OPC server side, follow the instructions in the manual of each OPC
server.
If a DCOM setup method is not described in the applicable OPC server manual, use the following
setup example as a reference.
l Start Component Services

Logon the PC using an account with the Computer administrator privilege. And then, choose
[Control Panel] – [Administrative Tools] – [Component Services] from the [Start] menu of
Windows, so as to open the Component Services window.
Component Services
File Action View Window Help
Console Root My Computer 4 object(s)

Component Services COM+ Applications
Computers DCOM Config
Distributed Transaction Coordinator
My Computer
Running Processes
COM+ Applications
DCOM Config
Distributed Transaction
Running Processes
Event Viewer (Local)
Services (Local)
R030103E.ai
Figure Component Services Window
SEE
ALSO For more information about how to use the component services, refer to Windows Help.

l Default Properties of the PC
The default properties need to set to the PC of the OPC server.
1. On the Component Services window, choose [Console Root] – [Component Services]
– [Computers] – [My Computer].
2. Open the My Computer properties.
3. On [Default Properties] tab, do the followings:

• Check [Enable Distributed COM on this computer].
• Choose [None] for [Default Authentication Level].
• Choose [Identify] for [Default Impersonation Level].
l DCOM Configuration of OPC Server

For configuring DCOM of OPC server, do the following:
1. On the Component Services window, choose [Console Root] – [Component Services]
– [Computers] – [My Computer] – [DCOM Config].
2. Choose OPC server from the displayed list. And then, open its properties.
3. In [General] tab, choose [Default] for [Authentication Level].
4. Do the following on [Security] tab:

• For [Launch and Activation Permissions] choose [CTM_PROCESS].
• For [Access Permissions] choose [CTM_PROCESS].

<R3.2 Creation of New SIOS> R3-6
R3.2 Creation of New SIOS

A new SIOS can be created in a CENTUM VP project on CENTUM VP System View. The
detailed procedure for creating the new SIOS is as follows.
n Create New SIOS

On System View, Choose [Create New] – [BCV...] from [Files] menu. Then [Create new BCV]
dialog box will be displayed. For new SIOS station, [Type] and [Network] tabs are available for
configuration.
Create new BCV
Type Network
Type
Station type (Parentheses indicate a lower bus)
SIOS System Integration OPC Station
Station Address
Domain Number 1
Station Number 60
Component Number
Number
Station Comment SIOS0160
Alias of Station
Station Status Display
Upper Equipment Name
OK Cancel
R030201E.ai
Figure Create New BCV Dialog Box (Type Tab)
The settings on these tabs will be explained below.
n Settings on Type Tab

The settings on Type tab will be explained.
l Station Type
▼ Station Type
Station type of the newly created station needs to be specified. Here [SIOS System Integration
OPC Station] should be selected.
l Station Address
▼ Domain Number, Station Number
Station address of the newly created station needs to be specified. A station address consists of
domain number and station number. The domain number of the SIOS connected control bus (V
net or Vnet/IP) should be specified. The station number needs to be specified within the range of
1 to 64. The station address cannot be modified once the setting is applied.

l Component Number
▼ Component Number
Component number of the newly created station may be specified. This setting is omissible.
l Station Comment
▼ Station Comment
Station comment of the newly created station may be specified. Up to 24 single-byte characters
or 12 double-byte characters can be used. This setting is omissible.
l Alias of Station
▼ Alias of Station
Station comment of the newly created station may be specified.
When this setting is set to a station, the station will be identified on HIS by the alias instead of the
station name. Up to 8 alphanumeric characters can be used for setting the alias of station. The
alias of station can be omitted.
l Station Status Display

▼ Station Status Display
When this setting is set to a station, the station status display view will be identified on the HIS by
the character string of this setting instead of the station name. Up to 16 alphanumeric characters
can be used for this setting. On HIS system status overview view, double-clicking the SIOS icon
can open the station status display view named with this setting. The setting of station status
display can be omitted.
l Upper Equipment Name

The equipment name of higher hierarchy of this station may be specified. The names of
hierarchical equipment should be defined on Plant Hierarchy builder of the project. The upper
equipment name can be omitted.

n Settings on Network Tab

▼ Ethernet TCP/IP Settings
The settings on Network tab will be explained.
Create new BCV
Type Network
Vnet/IP
Ethernet TCP/IP Settings
Host Name E0160
IP Address 172.17.1.60
Subnet Mask 255.255.0.0
OK Cancel
R030202E.ai
Figure Create New BCV Dialog Box (Network Tab)
l Hostname
The hostname is automatically determined according to the bus type, domain number and station
number. In general, this automatically determined hostname should be used.
Eddss
E : Identifier indicating that the bus type is Ethernet(fixed)
dd : Domain number specified when the SIOS is created.
ss : station number specified when the SIOS is created.
l IP Address
The IP address is used for physically identifying the connected SIOS on Ethernet.
The IP address is automatically determined according to the domain number and station number.
In general, this automatically determined IP address should be used.
172.17.dd.ss : Ethernet IP address
172 : System Fixed
17 : Identifier indicating that the bus type is Ethernet(fixed)
dd : Domain number specified when the SIOS is created.
ss : station number specified when the SIOS is created.
l Subnet Mask
The subnet mask is set to 255.255.0.0 as default. In general, this default subnet mask should be
used.

<R3.3 Configuration of OPC Server> R3-9
R3.3 Configuration of OPC Server

The server for communication of SIOS needs to be configured. The configuration of the
OPS server includes two types of configurations, i.e., automatic configuration and manual
configuration.

R3.3.1 Automatic Configuration of OPC Server

The OPC server can be automatically configured on SIOS Engineering Window. The
communication between SIOS and the OPC server is also configured on the SIOS
Engineering Window. User can either browse the OPC server information so as to
automatically configure the server or to import an automatic configuration file that was
exported in another environment.
n Automatic Configuration by Browsing Servers

1. On the tree view of System View, choose the folder of SIOS station, and then [Configuration]
folder. And then double click [BCV-OPC] so as to display the Connected System Type
Select Dialog Box.
Connected System Type Select Dialog Box
Connected System Type

(none)
STARDOM
OK Cancel
R030311E.ai
Figure Connected System Type Select Dialog Box
2. Select the connected system on Connected System Type Select dialog box. Select [none] if
connecting through the SIOS tag.
IMPORTANT
The Connected System Type Select dialog box is displayed only during the first engineering
process immediately after the SIOS is created. This dialog box is not displayed in the subsequent
SIOS engineering processes. To change the connected system type, delete the SIOS from
System View and create the SIOS again.

3. Click [OK] button on Connected System Type Select dialog box so as to display the SIOS
Engineering Window.
In [Connected System Type] field of the SIOS Engineering Window, the connected system
type selected on Connected System Type Select dialog box is displayed.
SIOS Engineering BCVO0160
Connected System Type STARDOM Update System Files
Predefined DA Server Predefined A&E Server
Open Open
Add Add
Delete Delete
Load Load
Load Process Progress Print Save
Open SIOS OPC Browse

Load All Close
Definition View...
R030301E.ai
Figure SIOS Engineering Window
Tip
If the engineering work is performed to the SIOS for the first time, the pane of Predefined DA Server and the pane
of Predefined A&E Server will be empty.
4. If a connected system type is selected (if the type is other than [none]), click [Upgrade
System Files] button on the SIOS Engineering Window.
The files required to connect the system selected on Connected System Type Select dialog
box to the SIOS will be updated.

5. Click [OPC Browse View...] button on the SIOS Engineering Window so as to open the OPC
Browse List dialog box.
OPC Browse List Dialog Box
OPC Browse File
Open
Delete
Import...
Automatic
OPC Browse... Close
Generation...
R030302E.ai
Figure OPC Browse List Dialog Box
TIP
Operations such as gathering information from the OPC server and displaying the gathered information are
commonly called “OPS Browse.”
6. Click [OPC Browse...] button on the OPC Browse List dialog box so as to open OPC Browse
Execute dialog box.
OPC Browse Execute Dialog Box
Specify OPC Server Definition, and Browse
OPC Server Definition
Specify Host Name and Program ID, and Browse
Server kind DA Server A&E Server
Host Name Or IP Address HIS0164 Refer
Program ID Yokogawa.CSHIS_OPC
DA Instrument SRDAInst.csv Refer
OPC Browse Making Name BrowseDA001
Process Print Save

Starts OPC Browse Process. Host Name=HIS0164 Program ID=Yoko
Start Cancel Close
R030303E.ai
Figure OPC Browse Execute Dialog Box

7. To browse the existing OPC server configuration, the radio button of [Specify OPC
Definition, and Browse] on OPC Browse Execute dialog box needs to be checked. And then
choose an OPC server configuration from the list box.
If it is the first time engineering, OPC Browse the radio button of [Specify Host Name and
Program ID, and Browse] on OPC Browse Execute dialog box needs to be checked. And
then entering the following settings:
• Server Kind
Choose either DA server or A&E server.
• Host Name or IP Address
Enter the hostname (computer name) or IP address of the target OPC server for browsing.
• Program ID
Enter the program ID of the OPC server. After entering the host name or the IP address
of the OPC server for browsing, when cursor moves to the program ID column, a list of
program IDs obtained from the browsed OPC server will be created. If the list of program
IDs cannot be obtained from the browsed OPC server, a list of program IDs will be created
based on the local PC registries. A program ID can be selected from the list.
• DA Instrument Description File
When using the SIOS instrument data access, specify the DA instrument description file
that corresponds to the connected system. When you click the [Refer] button, a list of
DA instrument description files for the connected system that is specified on the SIOS
Engineering Window will be displayed.
• OPC Browse Making Name
Enter the file for holding the browsed OPC configuration. The predefined default file name
corresponds to the OPC server will be displayed. However, the default file name can be
changed.
8. Click [Start] button on OPC Browse Execute dialog box. Then the OPC server information
will be browsed for gathering, and an OPC Browse file will be created.
9. When browsing, the progress messages will be displayed in the Process area of the OPC
Browse Execute dialog box. When clicking [Print] button, the displayed messages can be
printed from a printer. When clicking [Save] button on the OPC Browse Execute dialog
box, the displayed messages can be saved into a file. These two buttons need to be used
accordingly.

10. On the OPC Browse List dialog box, the name of OPC browse file will be added. And then
click [Automatic Generation] button on the OPC Browse List dialog box so as to open the
Automatic Generation dialog box.
Automatic Generation Dialog Box
Automatic Generation Source Automatic Generation Target

BrowseDA001 Make New OPC Server
DA Server Automatic Generation Rule AE Server Automatic Generation Rule
Rule of when the automatic generation destination file is saved

Update All
Not updated if the same tag is found
Only Browse information is updated if the same tag is found
CENTUM Tag Generation Rule

Automatic Generation from Leading Several Characters of Item ID
The number of specified characters from head
Delimiter Field number
Automatic Generation from Specified

Character String
Automatic Assignment
Specify Each Tag
Save DA Server Automatic Generation Rule
Process Print Save
Start Cancel Close
R030304E.ai
Figure Automatic Generation Dialog Box (DA Server Automatic Generation Rule Tab)

Automatic Generation Dialog Box
Automatic Generation Source Automatic Generation Target

BrowseAE001 Make New OPC Server
DA Server Automatic Generation Rule AE Server Automatic Generation Rule
Event Type
Select All
Select SIMPLE TRACKING CONDITION
Save A&E Server Automatic Generation Rule
Process Print Save
Start Cancel Close
R030305E.ai
Figure Automatic Generation Dialog Box (AE Server Automatic Generation Rule Tab)

11. Automatic Generation dialog box consists of two tabs, [DA Server Automatic Generation
Rule] tab and [AE Server Automatic Generation Rule] tab. After choosing the tab for the
selected server, the following options need to be defined for automatic generation.
Table DA Server Automatic Generation Rule (1/2)
Items Descriptions
Automatic Generation Source Displays a list of OPC Browse Making Names
Creates new OPC server and displays the file name of the
Automatic Generation Target
configured OPC DA server.
If identical tag is found, choose one of the following rules:
• Update all (default)
Deletes all the existing data and accept the newly browsed data
and update the host name and program ID.
• Not update if the same tag is found
When identical CENTUM VP tag is found after automatic generation,
Rule of when the automatic
the existing CENTUM VP tag has higher precedence.
generation destination file is
The unique CENTUM VP tags will be appended.
saved
• Only Browse information is updated if the same tag is found
After automatic generation, if identical CENTUM VP tags are found,
the previous data specific to the function blocks will be held and
only the browsing information will be updated.
The data with browsing information and the data specific to the
function blocks generated from those data will be updated.
Choose one of the following rules for automatically generating
CENTUM VP tags:
• Automatic Generation from Leading Several Characters of Item ID
The number of specified characters from head (default):
Enter a number between 1 and 16 as the length of the string
prefixed to the item ID.
Delimiter:
Enter an alphanumeric or single byte symbol. By default, no
delimiter is used.
A delimiter can also be selected from the spin box. The options
in the spin box are [ ], [!], [.] and [:].
CENTUM Tag Generation Rule Field number:
When delimiter is specified, the filed number needs to be
specified using a number between 1 and 99.
• Automatic Generation from Specified Character String
Up to 16 characters can be used as the specified string.
• Automatic Assignment
The tags automatically generated by the system will be assigned.
• Specify Each Tag
During automatic generation, a dialog box of each item ID for
defining CENTUM VP tag name will be displayed for each tag.
User needs to define a CENTUM VP tag name on this dialog box
for each tag.
After clicking the button of [Save DA Server Automatic Generation
Rule], the setting on the DA Server Automatic Generation Rule tab
Save DA Server Automatic
will be saved.
Generation Rule
The saved settings will be displayed when the automatic
generation dialog box is opened next time.
R030306E.ai

Table DA Server Automatic Generation Rule (2/2)
Items Descriptions
After clicking [Print] button, the contents displayed in the Process
Print Button
area will be sent to printer to printout.
After clicking [Save] button, the contents displayed in the Process
Save Button
area will be saved to a file.
After clicking [Start] button, the automatic generation for the OPC
Start Button
server will be started according to the defined rule.
After clicking [Cancel] button, the automatic generation for the
Cancel Button
OPC server will be canceled.
After clicking [Close] button, the automatic generation dialog box
Close Button
will be closed.
R030307E.ai
Table AE Server Automatic Generation Rule

Items Descriptions
Automatic Generation Source Displays a list of OPC Browse Making Names
Creates new OPC server and displays the file name of the
Automatic Generation Target
configured OPC DA server.
Choose event types for automatic generation.
[Select All], all types of events will be used.
Event Type
[Select], select from the following types:
SIMPLE, TRACKING and CONDITION
After clicking the button of [Save A&E Server Automatic Generation
Rule], the setting on the AE Server Automatic Generation Rule tab
Save A&E Server Automatic
will be saved.
Generation Rule
The saved settings will be displayed when the automatic
generation dialog box is opened next time.
After clicking [Print] button, the contents displayed in the Process
Print Button
area will be sent to printer to printout.
After clicking [Save] button, the contents displayed in the Process
Save Button
area will be saved to a file.
After clicking [Start] button, the automatic generation for the OPC
Start Button
server will be started according to the defined rule.
After clicking [Cancel] button, the automatic generation for the
Cancel Button
OPC server will be canceled.
After clicking [Close] button, the automatic generation dialog box
Close Button will be closed.
R030308E.ai
12. On the Automatic Generation dialog box, click [Start] button. Then the data of OPC server
will be automatically generated. The automatically generated data for OPC server will be
saved into files. The file names of the automatically generated data will be displayed SIOS
Engineering window in the pane for DA server or A&E server accordingly.
13. Click [Load All Servers] button on SIOS Engineering window, the contents of OPC servers
will be downloaded to SIOS.
14. After downloading, the progress messages will be displayed in the Load Process Progress
area of the SIOS Engineering window. When clicking [Print] button on the SIOS Engineering
window, the displayed messages can be printed from a printer. When clicking [Save] button
on the SIOS Engineering window, the displayed messages can be saved into a file. These
two buttons need to be used accordingly.

n Automatic Configuration by Importing Files

Automatic configuration for the SIOS and communicated OPC server can also be performed
using the CSV files exported from other environment.
folder. And then double click [BCV-OPC] so as to display the SIOS Engineering Window.
2. Click [OPC Browse View...] button on the SIOS Engineering Window so as to open the OPC
Browse List dialog box.
3. Click [Import...] button on the OPC Browse List dialog box so as to open Browse Import
dialog box.
Browse Import Dialog Box
OPC Browse
Use Default Browse Name
Make CSV File Column Allocation

Effective
Column Number
Item ID
Item Description
Access Path
Item Canonical Data Type
High EU
Low EU
EU Unit
Contact Close Label
Contact Open Label
Loaded from File
Import Close
R030309E.ai
Figure Browse Import Dialog Box
4. Enter a name to OPC Browse blank. The default name can be used by checking the option
of [Use Default Browse Name].
To change the alignment of the columns of the imported file, check the option of [Make CSV
File Column Allocation Effective]. Then the boxes for aligning columns will be available.
Using these combo boxes, the data items can be aligned to the specified columns.

5. Click [Import] on Browse Import dialog box. Then an Open dialog box will be displayed.
Open
Look in: TEMP
a. OPCSDA01.csv
a. OPCSDA02.csv
a. OPCSDA03.csv
a. OPCSDA04.csv
File name: OPCSDA01.csv Open
Files of type: *.csv Cancel
R030310E.ai
Figure Open Dialog Box
6. On the Open dialog box, choose the file for importing and then click [Open] button. Then the
file will be imported.
7. The Browse names specified on the Browse Import dialog box are displayed in the list area
of OPC Browse List dialog box.
Click [Automatic Generation...] button on the OPC Browse List dialog box so as to display
Automatic Generation dialog box.
8. The Automatic Generation dialog box consists of two tabs, DA Server Automatic Generation
Rule tab and AE Server Automatic Generation Rule tab. Choose a tab for automatically
generating the OPC server and enter the required settings accordingly.
9. Click [Start] button on the Automatic Generation dialog box. The OPC server data will be
saved in an automatically generated file. The name of the automatically generated file will
be displayed in the pane of Predefined DA Server or the pane of Predefined A&E Server on
the SIOS Engineering window.
10. On SIOS Engineering window, click [Load All Servers] button. The configuration of the OPC
server will be downloaded to SIOS.

R3.3.2 Manual Configuration of OPC Server

The OPC server can be manually configured by modifying the OPC server definition files
on SIOS Engineering Window. On the SIOS Engineering Window, user can modify the
existing OPC server definition file and the SIOS definition file.
n Modify SIOS Definition File

The SIOS engineering information can be changed by editing the default SIOS Definition File.
Each SIOS has a definition file.
2. Click [Open SIOS Definition] button on SIOS Engineering window so as to open the SIOS
Definition file.
3. Edit the SIOS definition file.
SEE
ALSO For more information about the OPC server definition file, see the following:
R3.4.1, “SIOS Definition File”
4. Save the edited SIOS definition file into a CSV file.

5. Click [Load All Servers] button on the SIOS Engineering window, the edited contents will be
downloaded to the SIOS.
n Manually Configuring the New OPC Server

How to manually configure the newly created OPC server will be explained below. On the
SIOS Engineering Window, user can open the default OPC server definition file, edit it and then
download it to the SIOS. The detailed procedure is as follows:
folder. And then double click [BCV-OPC] so as to display the SIOS Engineering window.
2. Click [Add] button on the SIOS Engineering Window so as to open the default OPC server
definition file.
3. Edit the OPC server definition file.
SEE
• R3.4.2, “OPC DA Server Definition File”
• R3.4.3, “OPC A&E Server Definition File”
4. Save the edited OPC server definition file into a CSV file.
5. Click [Load] on SIOS Engineering window so as to download the OPC server definition file
to SIOS.

n Modify OPC Server Definition File

How to modify the server definition file will be explained below.
Open the OPC definition file on SIOS Engineering window. And then edit the file and download
the edited file to SIOS. The procedure is as follows:
2. On SIOS Engineering window, choose a definition file of DA server or definition file of A&E
server from either windowpane.
3. Click [Open] button on SIOS Engineering window so as to open the OPC server definition
file.
4. Edit the OPC server definition file.
SEE
• R3.4.2, “OPC DA Server Definition File”
• R3.4.3, “OPC A&E Server Definition File”
5. Save the edited OPC server definition file into a CSV file.
6. Click [Load] on SIOS Engineering window so as to download the OPC server definition file
to SIOS.

<R3.4 Definition Files> R3-22
R3.4 Definition Files

The files essential for SIOS engineering are the following three types of definition files:
• SIOS Definition File
• OPC DA Server Definition File
• OPC A&E Server Definition File

R3.4.1 SIOS Definition File

An SIOS definition file contains the settings of software diagnostic interval, default
character string of character data, cached data screening, number of cached data and so
on so forth. A sample SIOS definition file is shown as follows:
#=======================================
# SIOS Definition File
#=======================================
#
# SIOS Definition Element Configuration
#<BCVOTable>
# <FileHeader> File Information(Unchangeable) </FileHeader>
# <BcvOpcElement> SIOS Definition Information </BcvOpcElement>
#</BCVOTable>
#
# Element Specification
#<BCVOTable>
# <FileHeader>
# <FileId>,BCVOPCDEF,</FileId>
# <Revision>,Revision No.,</Revision>
# <Locale>,[JP|US|EU],Time Difference,</Locale>
# <Create>,Created Time Local Time(Notation depends on Locale),</Create>
# <Update>,Update Time Local Time(Notation depends on Locale),Local Time(U32),</Update>
# <FileSeq>,File Sequence No.,Terminal Mark('E' means end of files),</FileSeq>
# </FileHeader>
# <BcvOpcElement>
# <GenTime>,Local Time(Notation depends on Locale),Local Time(U32),</GenTime>
#
# The following shows the items that can change the definition.
#
# <Cpuinfo>,Redundancy(0:No/1:Yes),Other Party IP Address,Subnet Mask,Status Monitoring Communication
Interval(1-60 seconds: default 10),Load Equalization Communication Interval(1-60 seconds: default 30)</Cpuinfo>
# <DigInterval>,Software Diagnostic Interval (1-60 seconds: default 10),</DigInterval>
# <Letter>,Character type data default character string,</Letter>
# <CacheScr>,Specify Cache Screening (0: No Screening/1: Screening default 0),</CasheScr>
# <DtCache>,Number of data cache entries(100 - 30000: default 3000 100 unit),</DtCache>
# <VframeError>,"Specify setting a communication error code in an error of OPC Item Access(0: do not set an
error code/1: set an error code, default 1)",</VframeError>
# </BcvOpcElement>
#</BCVOTable>
#
#
# Change Definition Information.
<BCVOTable>
<FileHeader>
<FileId>,BCVOPCDEF,</FileId>
<Revision>,,</Revision>
<Locale>,,,</Locale>
<Create>,,</Create>
<Update>,,,</Update>
<FileSeq>,,,</FileSeq>
</FileHeader>
<BcvOpcElement>
<GenTime>,,,</GenTime>
# Definition Items
<Cpuinfo>,0,,,10,30,</Cpuinfo>
<DigInterval>,10,</DigInterval>
<Letter>,NOT_READY,</Letter>
<CacheScr>,0,</CacheScr>
<DtCache>,3000,</DtCache>
<VframeError>,1,</VframeError>
</BcvOpcElement>
</BCVOTable>
R030401E.ai
Figure A Sample SIOS Definition File

n Elements of SIOS Definition File

The elements between <BcvOpcElement> and </BcvOpcElement> in the SIOS definition file
define the operations of the SIOS.
l <Cpuinfo>
The meaning of each <Cpuinfo> element is as follows.
• Redundancy (fixed to 0 since it is not used)
• Other Party ID address (not used)
• Subnet Mask (not used)
• Status Monitoring Communication Interval (fixed to 10 seconds since it is not used)
• Specify the interval of re-transmission between 1 and 60 seconds in the case of equalize
communication errors at the time of off-line or online download. The default setting is 30
seconds.
l <DigInterval>: Software Diagnostic Interval

Specify the software diagnostic interval between 1 and 60 seconds. The default setting is 10
seconds.
l <Letter>: Character Type Data Default Character String

Specify a character string to be returned when the character type data does not exist in the data
cache. The default setting is “NOT_READY.”
l <CacheScr>: Specify Cache Screening

Specify whether or not to use the cache screening by selecting 0 or 1. The default setting is 0.
• 0: Use screening
• 1: Do not use screening
l <DtCache>: Number of Data Cache Entries

Specify the number of data items registered in the data cache between 100 and 30000. The
default setting is 3000. Specify the number in increments of 100.
l <VframeError>: Specify Individual Error

Specify by selecting 0 or 1 the process when the data status of the reference data is BAD during
a process data access communication. The default setting is 1.
• 0: An error code will not be set even if the data status is BAD.
• 1: An error code will be set for each data item whose data status is BAD.
When an instrument faceplate is displayed in the HIS, “****” will appear for the data whose
status is BAD.

R3.4.2 OPC DA Server Definition File

An OPC DA server definition file contains the settings of OPC server number, OPC server
response time-out, communication retry period, system status tag name, data caching
time-out, data updating period, CENTUM VP tag name, tag comment, item IDs and so on
so forth. A sample OPC DA server definition file is shown as follows:
#=======================================
# OPC DA Server Definition File
#=======================================
#
# OPC DA Server Definition Element Configuration
#<BCVOTable>
# <FileHeader> File Information(Unchangeable)</FileHeader>
# <OpcSvrInfo> OPC Server Information </OpcSvrInfo>
# <Attribute>
# #DA Instrument Description File
# </Attribute>
# <OpcGrpInfo>
# <OpcGrp> Group Definition</OpcGrp>
# #Number of Groups
# </OpcGrpInfo>
# <DispGrpInfo>
# <DispGrp>
# Definition of CENTUM TAG
# </DispGrp>
# #Number of CENTUM TAG
# </DispGrpInfo>
#</BCVOTable>
#
#<BCVOTable>
# <FileHeader>
# <FileId>,BCVOPCDAD,</FileId>
# </FileHeader>
# <OpcSvrInfo>
# <TypeId>,DA,</TypeId>
# <OpcSvrNo>,OPC Server Number(1-16),</OpcSvrNo>
# <OpcAlias>,Server Alias Name(16 characters at max),</OpcAlias>
# <OpcInfo>,OPC Server Execution Host Name,OPC Server Program ID,</OpcInfo>
# <OpcResTm>,OPC Server Response Time-out(4-60 seconds: default 30),</OpcResTm>
# <RtyPrd>,Retry Period(1-300 seconds: default 10),</RtyPrd>
# <SysTag>,Status System Tag(16 characters at max:default:ddssDAnn),</SysTag>
# <Cmnt>,Arbitrary Comment,</Cmnt>
# </OpcSvrInfo>
# <Attribute>
# <DaInstFile>,DA Instrument Description Filename,</DaInstFile>
# </Attribute>
# <OpcGrpInfo>
# <OpcGrp>
# <OpcGrpNo>,Group Number(01-99),Group Name(16 characters at max),Change Time(Notation depends on
Locale),</OpcGrpNo>
# <CacheTout>,Cache Time-out Value(30-3600 seconds: default 120 10 unit),</CacheTout>
# <GrpPrm>Deadband(0-100%: default 0),Data Update Period(1-3600000msec: default500),<GrpPrm>
# </OpcGrp>
R030402E.ai
Figure A Sample OPC DA Server Definition File (1/2)

# Another Group starts.

# <OpcGrp>
# <OpcGrpNo>,Group Number,Group Name,Change Time,</OpcGrpNo>
# <CacheTout>,Cache Time-out Value,</CacheTout>
# <GrpPrm>,Deadband,Data Update Period,</GrpPrm>
# </OpcGrp>
# #Continues for Number of Tags
# </OpcGrpInfo>
# <DispGrpInfo>
# <DispGrp>
# CENTUM Tag Definition
# </DispGrp>
# #Continues for Number of CENTUM tags
# </DispGrpInfo>
#</BCVOTable>
#
# Describe Definition Information as follows:
<BCVOTable>
<FileHeader>
<FileId>,BCVOPCDAD,</FileId>
<Revision>,R4.01.00,</Revision>
<Create>,,</Create>
<FileSeq>,0,E,</FileSeq>
</FileHeader>
<OpcSvrInfo>
<TypeId>,DA,</TypeId>
<OpcSvrNo>,1,</OpcSvrNo>
<OpcAlias>,OPCSDA01,</OpcAlias>
<OpcInfo>,,,</OpcInfo>
<OpcResTm>,30,</OpcResTm>
<RtyPrd>,10,</RtyPrd>
<SysTag>,ddssDAnn,</SysTag>
<Cmnt>,,</Cmnt>
</OpcSvrInfo>
<OpcGrpInfo>
# <OpcGrp>
# <OpcGrpNo>,,,,</OpcGrpNo>
# <CacheTout>,120,</CacheTout>
# <GrpPrm>,0,500,</GrpPrm>
# </OpcGrp>
# If there is another group, add <OpcGrp> - </OpcGrp>.
</OpcGrpInfo>
<DispGrpInfo>
# <DispGrp>
# <GrpAttr>,Tag Group ID,CENTUM Tag Name,Tag Comment,Instrument Type,CENTUM Instrument Block Type,
Upper Limit of PV, Lower Limit of PV,Upper Limit of MV, Lower Limit of MV,Upper Limit of Ratio, Lower Limit of
Ratio, Decimal Point for PV,Decimal Point for MV,Decimal Point for SUM,Decimal Point for RATIO,Alarm Priority
Level,Security Level,Upper Name,RAW Data Display,SUM Display,Reverse-Scale Display,Tag Mark,Double
Authentication,CAS Mark,Upper Level Window,Help Number,Scale Division,EU Symbol of PV,EU Symbol of MV,
Switch Position Label,Label Format,Operation Mark,</GrpAttr>
# <Item>,Data Item Item ID,Access Path,CENTUM Data Item Name,OPC Group Name,</Item>
# #Continues for Number of Items
# </DispGrp>
# If another CENTUM Tags exist, append <GrpAttr> - </GrpAttr>.
</DispGrpInfo>
</BCVOTable>
R030403E.ai
Figure A Sample OPC DA Server Definition File (2/2)

n Elements of OPC DA Server Definition File

The elements between <OpcSvrInfo> and </OpcSvrInfo> in the OPC DA server definition file
define the OPC DA server information.
l <OpcSvrNo>: OPC Server Number

Specify the OPC DA server number between 01 and 16.
l <OpcAlias>: Server Alias Name

Specify the OPC DA server alias name using up to 16 single-byte characters. This is set to
“OPCSDA” + “OPC server number” in the default settings.
l <OpcInfo>: OPC Server Information

This data includes the OPC server execution host and the OPC DA server program ID.
• Host name: Specify the host name of OPC DA server execution PC. It is not necessary (can
be left blank) if the server coexists with the SIOS.
• Program ID: Specify the OPC DA server program ID.
l <OpcResTm>: OPC Server Response Time-out

Specify the response time-out of the OPC DA server between 4 and 60 seconds. The default
setting is 30 seconds. If no response to a request from the OPC client is made within this time
period, it will be determined that there is no response from the OPC DA server.
l <RtyPrd>: Retry Period

Specify the period (in seconds) between 1 and 300 seconds to retry connecting to the OPC DA
server when it is determined that there is no response from the OPC DA server. The default
setting is 10 seconds.
l <SysTag>: Status System Tag

This is a system tag name used to monitor the communication status between the SIOS and the
OPC DA server. It is specified based on the CENTUM VP tag naming conventions, using up to 16
single-byte characters. The system tag name cannot be assigned to the OPC data item ID.
The default system tag name is as follows.
In the case of the OPC DA server: ddssDAnn
dd: Domain number
ss: Station number
nn: OPC DA server number (01 to 16)
l <OpcGrpInfo> to </OpcGrpInfo>
This section is used to specify the OPC group definition.
l <OpcGrp> to </OpcGrp>
This section is used to specify the definition of one OPC group.

l <OpcGrpNo>: OPC Group
• Group Number: Specify a number for each OPC group without duplicating any number.
• Group Name: Specify the OPC group name.
• Change Time: Not used
l <CacheTout>: Cache Time-out Value

Specify the timer setting of the data cache screening process between 30 and 3600 seconds.
Specify the timer setting in increments of 10 seconds. If the data items that belong to this group
are not referenced by the HIS within this timer setting period, they will be deleted from the data
cache. The actual timing of deletion varies between the (timer setting - 10 seconds) and the timer
setting. The default setting is 120 seconds.
l <GrpPrm>: Group Parameters

Specify the deadband and the update period.
• Deadband: Specify the deadband in percentage (%).
If none is specified (if left blank), the deadband will not be applied.
• Data Update Period: Specify the data update period in msec.
The default setting is 500 msec.
l <DispGrpInfo> to </DispGrpInfo>
This section is used to describe the information of data items that are arranged into blocks.
l <DispGrp> to </DispGrp>: Display Group

This section is used to describe the information when the multiple data items are handled as one
function block.
l <GrpAttr>: Group Attributes

This section is used to describe the information regarding the SIOS instrument. The group
attributes are reflected in the HIS tag list. If the SIOS instrument data is changed, the
corresponding values of the items within the group attributes will also be changed. The meaning
of each element between <GrpAttr> and </GrpAttr> is shown in the tables below.
Table Elements between <GrpAttr> and </GrpAttr> (1/2)
Element Explanation
The character string after deleting the data item name of an OPC item ID
Tag Group ID
acquired by executing Browse.
This is automatically generated or the tag name that was specified in the editor
CENTUM tag name
will be set.
The item comment selected through browsing will be set. If it exceeds 24 bytes,
Tag comment
the excess will be deleted and a warning message will appear.
Instrument type The instrument type selected through browsing will be set.
CENTUM instrument block type CENTUM instrument block type corresponding to Instrument type is set.
The SH value selected through browsing will be set. If an SH value cannot be
Upper limit of PV (SH)
acquired, 100 or 100.0 will be set for analog, and 0 for BOOL.
The SL value selected through browsing will be set. If an SL value cannot be
Lower limit of PV (SL)
R030404E.ai

Table Elements between <GrpAttr> and </GrpAttr> (2/2)
Element Explanation
The MSH value selected through browsing will be set. If a MSH value cannot
Upper limit of MV (MSH)
be acquired, 100 or 100.0 will be set for analog, and 0 for BOOL.
The MSL value selected through browsing will be set. If a MSL value cannot be
Lower limit of MV (MSL)
Upper limit of Ratio (RH) The RH value selected through browsing will be set.
Lower limit of Ratio (RL) The RL value selected through browsing will be set.
This will be set to AUTO with automatic generation.
Decimal point for PV (DP) If set to AUTO, the decimal point position is determined from SH/SL when the
tag list is generated.
Decimal point for MV (MV_DP) If set to AUTO, the decimal point position is determined from MSH/MSL when
the tag list is generated.
Decimal point for SUM (TP) If set to AUTO, this will be the same as the decimal point position of the
measured value (DP).
If set to AUTO, this will be the same as the decimal point position of the
Decimal point for Ratio (RP)
measured value (DP).
Alarm priority level This will be set to 2 (medium-priority alarm) with automatic generation.
Security level This will be set to 4 with automatic generation.
This will be left blank with automatic generation, meaning a host
Upper equipment name
station (SIOS).
Raw data display This will be set to NO (none) with automatic generation.
SUM display This will be set to NO (none) with automatic generation.
Reverse-scale display This will be set to 0 (none) with automatic generation.
Tag mark This will be set to 2 (general) with automatic generation.
Double authentication This will be set to NO (none) with automatic generation.
CAS mark This will be set to NO (none) with automatic generation.
Upper level window This will be left blank with automatic generation.
Help number This will be set to HW0000 with automatic generation.
This will be set to the engineering unit symbol selected through browsing for
EU symbol of PV analog data. If there is no engineering unit symbol, this will be set to % by
default.
This will be set to the engineering unit symbol selected through browsing for
EU symbol of MV analog data. If there is no engineering unit symbol, this will be set to % by
default.
This will be set to the label that was edited based on the switch position label
Switch position label
value selected through browsing.
With automatic generation:
Scale-division This will be set to AUTO (determine automatically) for analog data.
This will be left blank for non-analog data.
Label format This will be set to 0 (normal position) with automatic generation.
Operation mark This will be set to 0 with automatic generation.
R030405E.ai

l <Item>: Item Definition
The item definition is provided for all items. The meaning of each element between <Item> and
</Item> is as follows.
Table Elements between <Item> and </Item>
Element Explanation
OPC item ID The valid item ID selected through browsing will be set as is.
Access path The access path selected through browsing will be set as is.
This will be set to the CENTUM data item name that corresponds to the OPC
CENTUM data item name
item ID acquired through browsing.
Specify the OPC group name specified in <OpcGrpNo>.
OPC group name
The OPC item here will be updated based on the data update period for this group.
R030406.ai
n Saving Subdivided Files

The OPC DA server definition file that was automatically generated will be subdivided into
multiple files each time the number of lines in one file reaches 50000 and then saved. The
subdivided files will be named as follows.
• First file
File name generated by the system (Example: OPCSDA01)
• Subsequent files
“-n” (n = 1, 2, 3, ...) will be added to the name of the first file (Example: OPCSDA01-1).
The file structure is indicated in the element <FileSeq>, file number, END mark</FileSeq> within
the OPC DA server definition file.
• File number
This is a sequential number for the files. It will be 0 for the first file, and then sequential
numbers, such as 1, 2 and 3, will be assigned in order for all subsequent files.
• END mark
“E” will be added for the last file if the first file was subdivided and saved.

R3.4.3 OPC A&E Server Definition File

An OPC A&E server definition file contains the settings of OPC server number, OPC
server response time-out, communication retry period, system status tag name, data
caching time-out, data updating period, event filter masking patterns, category IDs and so
on so forth. A sample OPC A&E server definition file is shown as follows:
#=======================================
# OPC A&E Server Definition File
#=======================================
#
# OPC A&E Server Definition Element Configuration
#<BCVOTable>
# <FileHeader> File Information (Unchangeable) </FileHeader>
# <OpcSvrInfo> OPC Server Information </OpcSvrInfo>
# <AEFlt>
# <Event>
# </EvtType> Event Filter Mask Pattern </EvtType>
# <EvtCat> Category Information </EvtCat>
# </Event>
# <Event>
# Up to 7 Filter Definitions of Each Event Mask Pattern
# </Event>
# </AEFlt>
#</BCVOTable>
#
#
#<BCVOTable>
# <FileHeader>
# <FileId>,BCVOPCAED,</FileId>
# </FileHeader>
# <OpcSvrInfo>
# <TypeId>,AE,</TypeId>
# <OpcSvrNo>,OPC Server Number(10-16),</OpcSvrNo>
# <OpcAlias>,Server Alias Name(16 characters at max),</OpcAlias>
# <OpcInfo>,OPC Server Execution Host Name,OPC Server Program ID,</OpcInfo>
# <OpcResTm>,OPC Server Response Time-out(4-60 seconds: default 30),</OpcResTm>
# <RtyPrd>,Retry Period(1-300 seconds: default 10),</RtyPrd>
# <SysTag>,Status System Tag(16 characters at max:default:ddssAEnn),</SysTag>
# <Cmnt>,Arbitrary Comment,</Cmnt>
# </OpcSvrInfo>
# <AEFlt>
# <Event>
# <EvtType>,Event Filter Mask Pattern 1,</EvtType>
# <EvtCat>,Category ID,Description,</EvtCat>
# Number of Category ID
# <EvtType>,Event Filter Mask Pattern 2,</EvtType>
# Number of Category ID
# </Event>
# </AEFlt>
#</BCVOTable>
R030407E.ai
Figure A Sample OPC A&E Server Definition File (1/2)

#
# Describe Definition Information as follows:
<BCVOTable>
<FileHeader>
<FileId>,BCVOPCAED,</FileId>
<Revision>,R4.01.00,</Revision>
<Create>,,</Create>
<FileSeq>,0,E,</FileSeq>
</FileHeader>
<OpcSvrInfo>
<TypeId>,AE,</TypeId>
<OpcSvrNo>,1,</OpcSvrNo>
<OpcAlias>,OPCSAE01,</OpcAlias>
<OpcInfo>,,,</OpcInfo>
<OpcResTm>,30,</OpcResTm>
<RtyPrd>,10,</RtyPrd>
<SysTag>,ddssAEnn,</SysTag>
<Cmnt>,,</Cmnt>
</OpcSvrInfo>
<AEFlt>
# <Event>
# <EvtType>,Event Filter Mask Pattern,</EvtType>
# </Event>
</AEFlt>
</BCVOTable>
R030408E.ai
Figure A Sample OPC A&E Server Definition File (2/2)

<R4. SIOS Operation and Monitoring> R4-1
R4. SIOS Operation and Monitoring

This chapter explains the operation and monitoring function for operating and monitoring
the SIOS from a HIS.
n Number of SIOSs That Can Be Operated and Monitored

“N00xx” in the model name of the basic operation and monitoring function, such as LHS1100/
N00xx or LHM1101/N00xx, indicates the number of control stations that can be operated and
monitored by the function. SIOSs are not counted as control stations that can be operated and
monitored by the operation and monitoring function.
n Data Display
Data accessed via the SIOS can be displayed on the following windows:
• Graphic view (Graphic Attribute)
• Graphic view (Overview Attribute)
• Graphic view (Control Group Attribute)
• Trend view (*1)
• Tuning view
• Faceplate
*1: 1-second trend cannot be displayed.
n A&E Message Displa sage monitor window. Messages are displayed under message
number 1303.
SEE
ALSO For the message display format, see the following:
“n Message Display” in R2.2, “Messages”

n System Status List Display View

SIOS icons are displayed on the system status list display view. The SIOS icon displayed on the
system status list display view is shown below.
R040001E.ai
Figure SIOS Icon Displayed on System Status List Display View
n SIOS Station Status Display View

The following information is displayed on the SIOS Station Status Display view:
• Station name
• Station comment
• Station No
• Type: SIOS
• Revision
• Generation date and time
• CPU usage (CPU load data in Windows)
• Communication load status (Number of data processed per unit time)
• Control status (RUN/STOP)
A display example of the SIOS Station Status Display view is shown below.
.SF BCVO0160 Station Status Display
MYPJT Domain : 01 V net1 V net2

SIOS0160
SIOS
Station No : 60
Type : SIOS
Revision : R4.01.00
Generation :
08/03/23 PM 01 : 12
CPU Load Ave : 10%

Cur : 20%
Comm Load Ave : 300 data/sec
Cur : 500 data/sec
Control Status : RUN
Ready
R040002E.ai
Figure Display Example of SIOS Station Status Display View

n Cautions when Using Process Report and Reports

The HIS process report view collects and displays the data when the view is opened or when
the search is executed again. When the SIOS receives a request from the HIS to reference data
not registered in the data cache, it returns the data status “NRDY” to the HIS until the data is
acquired from the OPC DA server. As a result, the SIOS instrument data may not be displayed in
the process report view.
If a search is executed in the process report view targeting “all tags,” the process data access will
occur for all SIOS data. At this time, the data registered in the SIOS data cache will be replaced,
and the data items that are accessed relatively frequently may be deleted from the data cache.
However, the data appended with the LongLife attributes will not be deleted from the data cache.
Even if the SIOS data is referenced in a report, the same thing happens as in the process report
view.

Blank Page
<R5. SIOS Maintenance> R5-1
R5. SIOS Maintenance

This chapter explains the maintenance of the SIOS.
n Statistic Collector
Starting the statistic collector will open the SIOS Statistic Collector window. The following
statistical information stored in the SIOS can be referenced on the SIOS Statistic Collector
window. The statistical information can also be output to a file from this window:
• Control bus (V net or Vnet/IP) load information:
Number of data/frames processed per unit time
• OPC server load information:
Number of data changes notified and number of setting requests received per unit time
• Cache information:
Number of cache errors generated per unit time
l Starting the Statistic Collector

From the [Start] menu of Windows, point to [All Programs], point to [YOKOGAWA CENTUM],
and then select [SIOS Statistic Collector]. The statistic collector is started and the SIOS Statistic
Collector window opens.
l SIOS Statistic Collector Window

The SIOS Statistic Collector window can be used to reference statistical information and output
the information to a file.
SIOS Statistic collector
Dump Save Clear Exit
Message
------------ ---------------------- ---------------- -------- --

Type SubType OPCServerName Latest M
------------ ---------------------- ---------------- -------- --
VnetLoad Processed Data Count 0 54
VnetLoad DataAccess Send Frame 0 2
VnetLoad DataAccess Receive Frame 0 2
VnetLoad MsgMng Send Frame 0 1
VnetLoad MsgMng Receiv Frame 0 0
CacheInfo Miss 0 52
OPCServerLoad Change OPCSDA01 0 1
OPCServerLoad Set OPCSDA01 0 0
OPCServerLoad Change 0 0
OPCServerLoad Set 0 0
R050001E.ai
Figure SIOS Statistic Collector Window

<R5. SIOS Maintenance> R5-2
The following explains each button on the SIOS Statistic Collector window.
• Dump button
Clicking the [Dump] button will acquire the statistical information stored in the SIOS. The
acquired statistical information is displayed in the Message area of the SIOS Statistic
Collector window.
• Save button
Clicking the [Save] button will output to a file the statistical information acquired via the
[Dump] button. The output destination file can be specified in the file selection dialog box.
• Clear button
Clicking the [Clear] button will clear the messages displayed in the Message area of the
SIOS Statistic Collector window. To display the messages again, click the [Dump] button.
• Exit button
Clicking the [Exit] button will close the SIOS Statistic Collector window.
• Message area
The statistical information acquired via the [Dump] button as well as error messages are
displayed in this area.
l Data Cache Size Tuning

The SIOS has a data cache of up to 30000 data items (default: 3000 data). For the data deleted
from the cache, the OPC items will also be deleted from the OPC DA server.
If there are many process data access requests for data not registered in the data cache, it
requires more time than usual for the data to be displayed by the HIS, since it takes a long time to
register the OPC items to the OPC DA server or to register the data to the data cache.
You can check the number of caching errors per unit time in the SIOS Statistic Collector window,
and it is thus possible to adjust the data cache size to a desired value. To change the data cache
size, change the data cache size defined in the SIOS definition file. Online maintenance is
allowed to change the data cache size.
SEE
ALSO • For more information about changing the data cache size, see the following:
R2.4.3, “Changing the Data Cache Size”
• For more information about changing the SIOS definition file, see the following:
“n Modify SIOS Definition File” in R3.3.2, “Manual Configuration of OPC Server”

<R6. SIOS Communication Performance> R6-1
R6. SIOS Communication Performance

This chapter explains the communication performance of the SIOS.
n Response Time
The response time refers to the time after a data write request is output from a HIS until the
request is reflected in the window on the HIS. The response time is calculated as a sum of
processing times t1 to t5.
HIS
Reference Reference
Write request Write response response
request
SIOS
Process data access
Refresh the data cache

Write request Notify the data change
OPC client
OPC server
Write request
Write response
Device
t1 t2 t3 t4 t5
R060001E.ai
Figure Components of Response Time

The following explains processing times t1 to t5.
l t1
An internal delay time of the SIOS, corresponding to the time after a write request is received
from the HIS until the OPC client outputs a write request.
l t2
An internal delay time of the SIOS, corresponding to the time after the OPC client receives a write
request from the process data access function until it outputs a write request to the OPC server.
Although the specific time varies depending on the OPC client configuration used by the SIOS,
t2 is generally in a range of 0 to 100 milliseconds if the OPC client is assumed to retrieve data
setting requests from the process data access function at 100-millisecond periods.
l t3
The time after the OPC server receives a write request from the OPC client until the device
completes write processing in response to a write request output to the device by the OPC
server.
Although the specific setting varies depending on the OPC server and device, devices generally
process requests at their own scan period, and thus the write operation of each device also
depends on the scan period of the device.
l t4
The time after the OPC server outputs a data change notification to the SIOS upon completion of
write processing by the device until the data cache of the SIOS is refreshed.
The OPC server reads all registered data items asynchronously with the write processing by the
device. Since devices generally process data reference requests at their own scan period, the
time needed to read data from a device depends on the scan period of the device. Accordingly,
the communication between the SIOS and device continues as long as there is a data item to be
read.
l t5
The time after the data cache of the SIOS is refreshed until the HIS reads the data. HISs refresh
data at 1-second periods. Thus, t5 is normally in a range of 0 to 1 second.

n Estimation of Response Time

The time after a data write request is output by a HIS until the request is reflected in the HIS’s
window (response time) is estimated. The preconditions used in estimating the response time are
as follows:
• The device processes data read/write requests at its scan period. The scan period of the
device is set to 100 milliseconds.
• The OPC server has a scan period of 1 second, meaning that all data items are read within
1 second.
• Communication processing time, internal processing delays in the respective devices and
user-defined data conversion processing time are ignored.
• Each processing time is calculated as an average.
Table Estimation of Response Time
Average processing Explanation
time (msec)
t1 0 Internal delays of the SIOS are ignored.
If the OPC client processes data write requests at 100-msec
t2 50
intervals, the average wait time is calculated as 50 msec.
If the scan period of the device is 100 msec, the average wait
t3 50
time is calculated as 50 msec.
If the scan period of the OPC server is 1 second, the average
t4 500
wait time is calculated as 500 msec.
t5 Since the HIS refreshes data every second, the average wait
500
time is calculated as 500 msec.
Total 1100
R060002E.ai
n Operation under High Load

If the number of data accesses received via the SIOS increases, the data refresh rate on the HIS
sometimes slows. The number of data processed by the SIOS per unit time can be checked from
the communication load status on the status display window.
If the data refresh rate on the HIS has slowed, perform the following measures:
• Reduce the number of windows displayed on the HIS
• Reduce the number of data assigned to the graphic view, etc.

Blank Page
Ind-1
CENTUM VP
Reference
IM 33M01A30-40E 2nd Edition
INDEX
A S
Automatic Configuration of OPC Server........... R3-10 Setting Security Policies..................................... R3-2
SIOS Communication Performance................... R6-1
C SIOS Data Items............................................... R2-10
Changing the Data Cache Size........................ R2-34 SIOS Definition File........................................... R3-23
Configuration of OPC Server.............................. R3-9 SIOS Engineering............................................... R3-1
Creation of New SIOS......................................... R3-6 SIOS Functional Details...................................... R2-1
SIOS Instrument Specific Data Items............... R2-15
D SIOS Maintenance.............................................. R5-1
Definition Files................................................... R3-22 SIOS Operation and Monitoring......................... R4-1
SIOS Tag and SIOS Instrument Tag................... R2-4
E Software Requirements...................................... R1-6
Status Management.......................................... R2-35
Error Handling................................................... R2-21
System Configuration......................................... R1-3
H
Hardware Requirements..................................... R1-5
M
Maintenance of Data Item Information............. R2-33
Maintenance of OPC Server Information......... R2-32
Manual Configuration of OPC Server............... R3-20
Messages.......................................................... R2-17
O
Online Maintenance.......................................... R2-31
OPC A&E Server Definition File........................ R3-31
OPC DA Server Definition File.......................... R3-25
Operating Environment....................................... R1-4
Overview of System Integration OPC Station.... R1-1
P
Process Data Access.......................................... R2-3

Blank Page
Rev-1
Revision Information
l Title : CENTUM VP Reference System Integration OPC Station
l Manual No. : IM 33M01A30-40E
Jun. 2009/2nd Edition/R4.01.60 or later*

* : Denotes the release number of the software corresponding to the contents of this user's manual. The
revised contents are valid until the next edition is issued.
R1.2.1 Descriptions regarding the OS in the PC of SIOS are modified
R1.2.2 Descriptions regarding the OS in the PC of SIOS are modified
Mar. 2008/1st Edition/R4.01 or later

Newly published.
n For Questions and More Information

If you have any questions, you can send an E-mail to the following address.
E-mail: support-CENTUM@csv.yokogawa.co.jp
n If you want more information about Yokogawa products, you can visit Yokogawa’s
homepage at the following web site.
Homepage: http://www.yokogawa.com/
n Written by Process Automation Product Marketing Dept.
Industrial Automation Systems Business Div.
Yokogawa Electric Corporation
n Published by Yokogawa Electric Corporation
2-9-32 Nakacho, Musashino-shi, Tokyo 180-8750, JAPAN
n Printed by KOHOKU PUBLISHING & PRINTING INC.

Blank Page

M01a30 40e 02 PRT18

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

M01a30 40e 02 PRT18

Uploaded by

Copyright:

Available Formats

Reference

System Integration OPC Station

IM 33M01A30-40E 2nd Edition : Jun.05,2009-00

R1. Overview of System Integration OPC

Access process data

Messages (A&E) Engineering

Acquire data items

Bus unique to PCS

Controller of PCS Controller of PCS Controller of PCS

Figure Example of SIOS Connection (Based on a V net control bus)

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

n Difference between the SIOS and GSGW

Function SIOS GSGW

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

R1.1 System Configuration

Control bus (V net)

Bus unique to PCS

Controller of Controller of Controller of

Figure Configuration of SIOS/OPC Server System (Separated)

Control bus (V net)

Bus unique to PCS

Controller of Controller of Controller of

Figure Configuration of SIOS/OPC Server System (Coexistent)

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

R1.2 Operating Environment

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

R1.2.1 Hardware Requirements

n Uninterruptible Power Supply (UPS)

IM 33M01A30-40E 2nd Edition : Jun.05,2009-00

R1.2.2 Software Requirements

n Running an OPC Server on the Same PC

n Running Other Functions on the Same PC

IM 33M01A30-40E 2nd Edition : Jun.05,2009-00

R2. SIOS Functional Details

Control bus driver

Process data access function Message function

Data cache Time

Basic SIOS functions

OPC DA server OPC A&E server

Figure SIOS Functional Configuration

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

n Overview of Each Function

l Process Data Access Function

l Status Management Function

l Time Synchronization Function

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

R2.1 Process Data Access

n Accessing Process Data

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

n SIOS Tag and SIOS Instrument Tag

Accessing process data using an SIOS Instrument Tag

Function Block of Other

Figure Two Data Access Methods of SIOS

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

Reference process data

(1) Look up in the data cache

(4) Access the OPC DA server

Figure Data Reference

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

n Appending the LongLife Attributes

n Data Cache Garbage Collection

l LRU (Least Recently Used) Control