technical information stardom technical guide · 2019. 4. 26. · network-based control system...

Technical Information

STARDOM Technical Guide

TI 34P02A03-01E

TI 34P02A03-01E

© Copyright Dec. 2007 (YK) 8th Edition July 31, 2014 (YK)

Part-A Outline

Part-B Autonomous Controller FCN/FCJ

Part-C FCN/FCJ Installation

Part-D NPAS POU Outline

Part-E VDS (Versatile Data Server Software)

Part-F General Specifications (GS) F1. STARDOM Overview

F2. FCN/FCJ

F3. APPF

F4. VDS

A

B

D

E

F Over- view

FCx

APPF

VDS

C

i

All Rights Reserved. Copyright © 2007, Yokogawa Electric Corporation TI 34P02A03-01E July 31, 2014-00

Introduction About this manual

STARDOM control system provides • High reliability • Simple, high-quality engineering • An open system that can be connected easily to other systems • Reassuring support for long-term operation This manual describes in detail the functions of the STARDOM control system.

Contents of this manual The contents of this manual are based on the style of hardware and the specifications of software release at the time of this publication. A function may be limited by the combination of an operating hardware and software. Please check it on the following homepage.

http://STARDOM.jp -> Members Page Yokogawa Plus

Network-based Control System (STARDOM) Compatibility of STARDOM Component

Intended readers of this manual This manual has been prepared for individuals who conduct engineering and estimates regarding STARDOM control system as an estimate guide for the model choice.

< Part-C. FCN/FCJ Installation > C-54

TI 34P02A03-01E July 31, 2014-00

C

5

4

3

2

1

9

8

7

6

RS-232-C Communication Cable The pin assignments of the CPU module is shown below.

● Pin Assignments of FCJ’s Serial Ports Table Connector Pin Assignment (D-sub 9-pin, male) Figure Pin Position (Front View)

Pin No Signal name

Function

1 CD Data channel receiving carrier detection 2 RD Receiving data 3 SD Transmission data 4 ER Data terminal ready 5 SG Signal ground 6 DR Data set ready 7 RS Transmission request 8 CS Transmission enabled 9 - Not used

IMPORTANT

FCJ’s serial ports are D-SUB 9 pins (male). Connectors are fastened using inch screw threads (No.4-40 UNC).

Blank Page

i

TI 34P02A03-01E July 31, 2014-00

Part-E VDS (Versatile Data Server Software)

CONTENTS Part-E .......................................................................................................... i E 1. Features of VDS ............................................................................ E-1

E 1.1 SYSTEM REQUIREMENTS ...................................................................... E-2 E 2. System Specifications ................................................................. E-3

E 2.1 Functional Configuration of VDS ........................................................... E-3 E 2.2 VDS System Configurations ................................................................... E-4 E 2.3 Connectable Controllers and I/O Devices ............................................. E-5 E 2.4 OPC Client/Server Connections ............................................................. E-7

E 3. Functions ...................................................................................... E-8 E 3.1 Software Structure .................................................................................. E-8 E 3.2 I/O Object .................................................................................................. E-9 E 3.3 Data Server ............................................................................................. E-10

E 3.3.1 Control Objects .......................................................................... E-11 E 3.4 HMI Server/HMI Client ........................................................................... E-13

E 3.4.1 HMI Server ................................................................................. E-13 E 3.4.2 HMI Client .................................................................................. E-14 E 3.4.3 Graphic Windows ....................................................................... E-15

E 3.5 .NET Application .................................................................................... E-24 E 3.6 Message Management Functions ........................................................ E-25 E 3.7 Process Management Functions ......................................................... E-26 E 3.8 Security for Operation .......................................................................... E-27

E 4. Application Development Environment ................................... E-28 E 4.1 Object Builder ........................................................................................ E-28 E 4.2 VBA Programs on Data Server ............................................................. E-30 E 4.3 Graphic Designer................................................................................... E-31

E 5. Software Products ...................................................................... E-32 E 5.1 Styles of Software Supply .................................................................... E-32 E 5.2 Optional Packages ................................................................................ E-34

E 5.2.1 Report Package ......................................................................... E-35 E 5.2.2 Trend Package ........................................................................... E-36 E 5.2.3 Test Package .............................................................................. E-37 E 5.2.4 Multi-task Package ..................................................................... E-38 E 5.2.5 Extended Security Package ....................................................... E-40

STARDOM Technical Guide Part-E VDS (Versatile Data Server Software)

TI 34P02A03-01E 8th Edition

ii

TI 34P02A03-01E July 31, 2014-00

E 5.2.6 MELSEC Driver .......................................................................... E-41 E 5.2.7 SYSMAC Driver ......................................................................... E-42 E 5.2.8 OPC Server Driver ..................................................................... E-43 E 5.2.9 DARWIN Driver .......................................................................... E-44 E 5.2.10 OPC Data Link Package for .NET ............................................ E-45

< Part-E VDS (Versatile Data Server Software) > E-1

TI 34P02A03-01E July 31, 2014-00

E

E1. Features of VDS VDS (Versatile Data Server Software), which is operation and monitoring software that runs on a personal computer, adds an advanced architecture to the conventional HMI/SCADA functionality such as data acquisition from various I/O devices and graphical presentation of the acquired data. VDS thus embodies a “network-based control system (NCS)” proposed by Yokogawa as a new system architecture for boosting manufacturing efficiency. • Operation and monitoring of the sites can be performed anytime, from

anywhere with VDS Viewer" (Java application). Only a personal computer with Internet access is needed, without special dedicated software, thus simplifying maintenance of the PC itself.

• VDS can handle various applications by linking up diverse devices and controllers including autonomous controllers, programmable logic controllers of a variety of suppliers, power monitors, and temperature controllers. The OPC client/server connectivity also enables VDS to interlink with business framework systems.

• A wealth of functions simplifies operations such as message management and assures security, and provides an object-oriented engineering environment to minimize programming effort, thus making engineering more efficient.

● Connected Specification Item Specification Remarks

VDSs Up to 4 per control LAN Consult Yokogawa if more VDSs needed. VDS interconnections (data server-to-HMI server connections)

Up to 4 data servers per HMI server

Maximum number of data servers an HMI server can access, including the data server on the same computer

HMI clients Up to 50 per HMI server Maximum number of HMI clients that can access an HMI server, including the HMI client on the same computer

I/O devices and controllers

Up to 32 per database server －

Control objects (tags) Up to 5000 The maximum number of objects can be set to 50, 100, 200, 500, 1000, 2000, or 5000 (depending on the license).

SEE ALSO For more information about the system specifications of VDS, refer to E2., “System Specifications.”

● VDS Software Licenses Model Name Remarks

NT201AJ VDS software media DVD-ROM (English version) NT610FJ VDS basic software license for fulltime Number of objects: 50, 100, 200, 500, 1000, 1500,

2000, 5000 (English version) NT610RJ VDS basic software license for runtime NT620FJ VDS Upgrade kit for full-time

Increased number of objects NT620RJ VDS Upgrade kit for run-time NT625AJ HMI Client additional licenses Add 1 or 5 Clients

SEE ALSO For more information about the VDS software licenses, refer to E5.1, “Styles of Software Supply.”


TI 34P02A03-01E July 31, 2014-00

E

E1.1 SYSTEM REQUIREMENTS The table below shows the system requirements to run VDS and those for an HMI client.

Items Data Server/HMI Server HMI Client(*1) Personal Computer IBM PC/AT compatible

CPU

Windows 7 (32-bit) 1 GHz or higher 32-bit (x86) or 64-bit (x64) processor

Windows 7 (64-bit) 1 GHz or higher 64-bit (x64) processor

RAM 2GB or more

Hard Disk 20 GB or more free space is required.

Ethernet adapter An Ethernet adapter that is supported by the operating system specified below is required.

DVD-ROM Drive A DVD-ROM drive that is supported by the operating system specified below is required at installation.

USB port Required to install an ID module that is supported by the operating system specified below is required.

－

Printer

A laser printer or color printer for A4-size paper (that is supported by the operating system specified below) is required. An ESC/P code-enabled serial printer is required for alarm printing.

－

Peripheral devices

An MO, digital audio tape, CD-RW, DVD-RW or other removable storage drive supported by the operating system specified below is required for backup.

－

Display(*2) 1024 x 768 pixels or more, 256 colors or more 1024 x 768 pixels or more, True Color

Operating system(*3) Windows 7 Professional SP1 (32-bit/64-bit) (*4)(*5) Runtime Environment Java Runtime Environment 7.0 Update 25 (*6) *1: If the same computer runs the VDS and an HMI client, the system requirements (except display) for a VDS apply.

*2: 800 x 600 pixels display is acceptable for maintenance.

*3: It is required that all VDSs and HMI clients are at the same OS and service pack level in the system.

*4: Aero style, User Account Control (UAC) and Windows Defender of Windows 7 must be disabled.

*5: Smart Screen Filter of Internet Explorer 8.0 must be disabled. When User Account Control (UAC) of Windows 7 is disabled, Protection mode of Internet Explorer 8.0 is disabled together.

*6: It is bundled with VDS Software Media.


TI 34P02A03-01E July 31, 2014-00

E

E2. System Specifications E2.1 Functional Configuration of VDS

In VDS, server functionality such as data acquisition and saving is split from client functionality such as operation and monitoring via graphic windows.

● Data server Acquires data from I/O devices and controllers such as autonomous controllers FCN/FCJ and programmable logic controllers, saves it, and passes it to the HMI server and Visual Basic applications. Data is controlled using tags called control objects. Up to four controllers implementing a data server can exist on each train of the control network, and up to a total of 32 I/O devices and controllers can be connected to each data server. Up to 5,000 control objects can be defined and implemented on each data server.

● HMI server An HMI server delivers, to HMI clients, operation and monitoring window data for data residing in data servers. An HMI client can access any data server, whether it is running on the same computer or a different networking computer on the same control network (can connect to up to four Data Servers).

● HMI client An HMI client accesses an HMI server via VDS Viewer to display operation and monitoring windows. An HMI client can be run either on the same computer with an HMI server or a different networking computer on the same control network. (An HMI server allows concurrent access from up to fifty clients.)

VDS ViewerOperation and

monitoring

Various controllers and I/O devices

Data ServerData Server

HMI ServerHMI Server

HMI ClientHMI Client

Control network (100/10 Mbps)

PC running

Acquiring data from I/O devices and saving itAcquiring data from I/O devices and saving it

Generating and distributing operation and monitoring windows Generating and distributing operation and monitoring windows

• Data servers: Up to 4 • HMI clients: Up to 50

• Connectable I/O devices: Up to 32 • Implementable control objects: Up to 5,000

Presenting operation and monitoring windows Presenting operation and monitoring windows

Network

Up to 4 per control network

Data acquisition and saving

Control

Figure Functional Configuration of VDS


TI 34P02A03-01E July 31, 2014-00

E

E2.2 VDS System Configurations From a small system such as connecting a single controller or I/O device, up to a large system consisting of multiple controllers and I/O devices, VDS can be optimally configured to suit any scale.

● Advantages • HMI clients can access VDS through the Internet and a firewall. • Each HMI client computer need not install VDS software. - Cheaper updating of package software • The HMI server can assess VDS’s data server running on a different PC, so

operation and monitoring of a different system is also possible. • Up to a total of 32(*1) controllers and I/O devices can be connected, and they can

all be of different models. *1: For controllers/devices connected via serial communication, each RS-485/422 train is counted as one.

Control Network(Ethernet)

I/O device/controller

+ HMI client

(VDS Viewer)

Figure Example of Small-scale system

Various I/O devices/controllers, e.g., PLCs and recorders

HMI clients

Control Network (Ethernet)

Information LAN (Ethernet)

Internet

Up to 4 per control LANUp to 4 per control LAN

Up to a total of 32 per VDSUp to a total of 32 per VDS

Up to 50 per VDSUp to 50 per VDS

Autonomous controllers

Serial communication

Temperature controllers and power monitors

Figure Example of Large-scale system


TI 34P02A03-01E July 31, 2014-00

E

E2.3 Connectable Controllers and I/O Devices VDS can link up a variety of controllers and I/O devices to meet a broad range of applications and thus integrate the site information held by those controllers and devices scattered on site.

● Controller and I/O Device Link • Up to a total of 32* controllers and I/O devices from those listed in the table above

can be connected, and they can all be of different models. (* For controllers / devices connected via serial communication, each RS-485/422 train is counted as one.)

• Connections of the FCN/FCJ and FA-M3 controllers require no optional drivers.

SEE ALSO • For optional device connection drivers, refer to E5.2, “Optional Packages.”

• For more information about the VDS standard drivers, refer to E3.2, “I/O Object.”


TI 34P02A03-01E July 31, 2014-00

E

Table Devices that can be connected to VDS Type Supported Models Interface Option Required

Autonomous Controllers

Yokogawa FCN/FCJ Ethernet (can be duplexed) None

PLC Yokogawa FA-M3 series Ethernet, RS-232-C None

Mitsubishi Electric MELSEC series

Serial, Ethernet, MELSECNET II, MELSECNET/10, MELSECNET/H, CC-Link, etc.

MELSEC Driver

OMRON SYSMAC series

Serial, Ethernet, Controller Link, SYSMACLINK, Compo Bus/D, etc. SYSMAC Driver

FL-NET-enabled controllers FL-NET

OPC Server Driver (plus RobotricsWare FA-Server required)

Fuji Electric MICREX-F RS-232-C Hitachi HIDEC-S10/2α Ethernet Sharp JW series Ethernet, RS-232-C Panasonic Electric Works

MEWNET-FP Ethernet, RS-232-C

Keyence KZ-A300, -A500 RS-232-C JTEKT

TOYOPUC Ethernet OPC Server Driver (plus Takebishi

Electric OPC server required) Fuji Electric MICREX-SX Ethernet OPC Server Driver (plus Fuji

Electric OPC server required) Allen-Bradley Logix5550 Ethernet OPC Server Driver (plus Allen-

Bradley RSLinx required)

Programmable Display

Digital GP-77 series Type R, GP2000 series, GP3000 series

Ethernet OPC Server Driver (Digital middleware, “Pro Server” is required)

Power monitor Yokogawa power monitor

PC-Link applicable model RS-485

None

Thermometer Yokogawa

Green series, UTAdvanced series

RS-422/RS-485 None

Data acquisition units

Yokogawa DARWIN Ethernet DARWIN Driver

Recorders Yokogawa DAQSTATION , hybrid recorders

Ethernet DARWIN Driver


TI 34P02A03-01E July 31, 2014-00

E

E2.4 OPC Client/Server Connections VDS can interlink with business framework systems such as the production management system using its OPC server functions as well as act as an OPC client to access data residing in an OPC server.

● Connection from/to OPC clients VDS, with no optional package, supports the following interfaces to allow not merely access to OPC clients from applications running in the same PC as the that running VDS but also access from remote OPC clients as shown in the figure: • OPC Custom Interface An interface adopting the basic functions of the OLE/COM as they are (client

applications are written in C or C++). • OPC Automation Interface An interface stipulated by the OPC DA 2.0 allows for access from Visual Basic

and VBA programs. (Access from Visual Basic is feasible also by the way of the section C4.4.)

SEE ALSO For more information about the access from Visual Basic programs, refer to E4.4, “Easy Link with VB Applications.”

● Connection from/to OPC servers The optional OPC Server Driver enables data access from/to a third-party OPC server based on the tag names whether that OPC server runs on the same PC as that running VDS or it is a remote OPC server as shown in the figure.

SEE ALSO For more information about the interfaces and methods supported, refer to F4.8, “OPC Server Driver" (GS 34P02G08-01E).

OPC server

PLC/DCSVarious controllers

Data server

Internet

Exaquantum PIsystem

OPC server

I/OObjectト

OPC client

HMI server

VDS Viewer

Autonomous Controllers

EthernetEthernet

PLC/DCSVarious controllers

OPCOPC Server Driver (OPC DA 2.0 Interface)

OPC Custom InterfaceOPC Automation Interface

Figure OPC Client/Server Connections


TI 34P02A03-01E July 31, 2014-00

E

E3. Functions E3.1 Software Structure

From the functions for communicating with I/O devices to those for delivering graphic display data to the VDS Viewer, VDS consists of a simple, hierarchical software structure with clear functional partitioning. • The I/O object performs communication with controllers and I/O devices. • The data server contains and manages data that are to be exchanged

with controllers and I/O devices via the I/O object. • The HMI server delivers graphic windows to VDS Viewer. • .NET application has components practically usable on Visual Studio,

including graphic components and multi-task application development supporting components.

Available helpers for developing application programs include Object Builder, a suite of object-oriented engineering tools, and Graphic Designer, which provides many graphics parts for drawing graphics easily. Standard features include message management that performs integrated management of messages including process alarms, operation logs, and system errors, and process management that performs integrated management of the various programs of the VDS system.

Data serverVBA

HMI server(Web server)

FCN/FCJdriver

I/O object

Messagemanagement

Communication drivers for controllers and I/O devices

Manages data that are to be exchanged with controllers and I/O devices via the I/O object. (Possible function enhancement using VBA)

FA-M3driver

Control objects

VDS Viewer

HMI client

GraphicDesigner

ObjectBuilder

VBA: Visual Basic Applications Edition

Processmanagement

FCN/FCJdriver

.NET application

Acquires data from the Data Server and delivers Web-compatible display data to HMI Clients.

Components usable on Visual Studio 2010 (Alarm Summary, Trend Graph and so on)

Allows operation and monitoring via graphic windows (can also be implemented in the same PC as that running VDS).

Figure Software Structure

TIP VDS has object-oriented control objects (data servers) and I/O objects. These can be used by merely making a setting in the object builder.


TI 34P02A03-01E July 31, 2014-00

E

E3.2 I/O Object The I/O object is a component for linking various controllers and devices such as FCN and FCJ autonomous controllers, programmable logic controllers, and I/O devices. Simply by plugging into the I/O object the proper driver for the I/O device or controller you want to connect, communication with that I/O device or controller will be performed in response to input/output requests from each control object on the data server.

● Specifications of I/O Object Table Specifications of I/O Object

Item Specifications Number of pluggable I/O drivers

Up to 32

Data refresh interval 1 to 3600 seconds Data refresh condition Periodic Acquires data and notifies the plugged-in control object of it at a specified refresh

interval. Upon change Acquires data at a specified refresh interval and notifies the plugged-in control

object of it only when there is a change in data value from the previous time. One-shot Acquires data from the specified controller or I/O device only once in response to

a request and notifies the plugged-in control object of it. Asynchronous Notifies the plugged-in control object of an asynchronous event upon receipt of it.

● Standard I/O Drivers • FCN/FCJ driver (Ethernet) • FA-M3 Ethernet driver (supporting the F3LE11 or F3LE01-5T (Rev.3 or later)

Ethernet interface module) • FA-M3 RS-232-C driver (supporting the F3LC11-1N PC link module, Rev.5 or

later)

SEE ALSO For controllers and I/O devices that can be connected using optional I/O drivers, refer to E2.3, “Connectable Controllers and I/O Devices.”

Data serverVBA

FCN/FCJdriver

FCN/FCJdriver

I/O objectFA-M3driver

FA-M3driver

Can implement up to 32 I/O drivers.

Performs communication with the specified controller or I/O device in response to input/output requests from each control object.

Can implement up to 32 I/O drivers.

Performs communication with the specified controller or I/O device in response to input/output requests from each control object.


FCN/FCJdriver

FCN/FCJdriver

Control objects

HMI client(VDS Viewer)

Figure I/O Object


TI 34P02A03-01E July 31, 2014-00

E

E3.3 Data Server The data server exchanges data with controllers and I/O devices via the I/O object, and performs various processing on the field data thus acquired. Individual data are managed by control objects allotted on the data server. Since VBA (Visual Basic Applications Edition) is implemented in the data server, control object actions and linking actions between multiple objects can be controlled using a VBA program.

● Control Objects Various control objects are provided to handle diverse types of data. Up to 5,000 control objects can be defined on the data server.

● Access to/from External Applications Various data contained in a control object can be used not only for graphic presentations but also by external application programs via the OPC custom interface and OPC automation interface supported as standard. The data can also easily be used by VBA programs.

SEE ALSO • For external applications via the OPC interface, refer to E2.4, “OPC Client/Server Connections.”

• For VBA programs, refer to E4.4, “Easy Link with VB Applications.”

Data serverVBA

FCN/FCJdriver

FCN/FCJdriver


FA-M3driver


FCN/FCJdriver

FCN/FCJdriver

Control objects

HMI Client(VDS Viewer)

Manages field data acquired by control objects that are defined on the data server.

Up to 5,000 control objects can be defined.

Functional enhancement is possible using VBA programs.

Allows access from/to external applications via OPC interfaces.

Figure Data Server


TI 34P02A03-01E July 31, 2014-00

E

E3.3.1 Control Objects

● Device Tag Objects A device tag object reads and writes device data in conjunction with an I/O driver, and possesses basic data processing functions such as scaling, integration, and alarm detection.

Table Device Tag Objects Type Description Remarks DI Digital input 1 bit data input DO Digital output 1 bit data output DR Digital register 1 bit data array input/output up to 256 bits AI Analog input 1-word data input AO Analog output 1-word data output AR Analog register 1-word data array input/output up to 64 words TXT Text Character data input/output up to 128 characters XAI Expanded analog input 2-word data input XAO Expanded analog output 2-word data output XAR Expanded analog register 2-word data array input/output up to 32 words XTX Expanded text Character data input/output up to 4096 characters (*1) (*2) WAI Wide analog input 4-word data input (*3) WAO Wide analog output 4-word data output (*3) WAR Wide analog register 4-word data array input/output (*3)

*1: For XTX (enhanced text) object, the number of blocks is counted as one for each of 128 bytes in terms of capacity.

*2: XTX objects cannot be used in the FCN/FCJ or PLC for an FA-M3 or MELSEC.

*3: These can be used only with FCN/FCJ.

Note: A DR (digital register) object can input and output the values of 256 contiguous bits, but has neither alarm detection nor integration function. An AR (analog register) object can input and output the values of 64 words, but has neither alarm detection nor integration function and scaling cannot be specified for each of those words. (Neither does an XAR object.)

● Application Support Objects These are control parts that support the actions of an application, such as generating timing signals. Using optional Multi-task Package allows the use of control parts to provide multi-tasking functions such as synchronization and data sharing between the data server and a VB program.

Table Application Support Objects Type Description Remarks TMR Timer Start VBA programs at specified time or at specified intervals. EVT Event Start VBA programs from external applications. BUF Buffer Buffer to store arbitrary data. SG Signal exchange Exchange events (signals) betweens processes. (*2) BD Block data Structured data input/output up to 32 Kbytes (*1) (*2) BDA Block data access Access to data by a block data object (*2)

*1: For BD (block data) object, the number of blocks is counted as one for each of 128 bytes in terms of capacity.

*2: Supplied by Multi-task Package.


TI 34P02A03-01E July 31, 2014-00

E

● PAS POU Objects These are control parts supporting process automation system program organization units (PAS POUs) in FCNs and FCJs. A PAS POU object reads and writes data from/to a PAS POU, and has functions to perform scaling and transfer of alarms occurring in the PAS POU.

Table PAS POU Objects Type name Description FCN/FCJ PAS POU Type PPVI Indication block NPAS_PVI PPID PID controller block NPAS_PID, NPAS_PI_HLD PONOFF ON/OFF controller block NPAS_ONOFF, NPAS_ONOFF_G PMLD Manual loader block NPAS_MLD, NPAS_MLD_PB, NPAS_MLD_BT PRATIO Ratio set block NPAS_RATIO, NPAS_RATIO_RT PAS Auto-selector block NPAS_AS_H, NPAS_AS_M, NPAS_AS_L PBDBUF Data set block NPAS_BDBUF_R, NPAS_BDBUF_T PPROG Program set block NPAS_PG_L30, NPAS_PG_L30_BP PVELLIM Velocity limiter block NPAS_VELLIM, NPAS_VELLIM_PB PSIO Switch instrument NPAS_SI_1, NPAS_SI_2, NPAS_SO_1, NPAS_SO_2,

NPAS_SIO_11, NPAS_SIO_12, NPAS_SIO_21, NPAS_SIO_22

PCALC Calculation block NPAS_LDLAG, NPAS_DLAY, NPAS_AVE_M, NPAS_AVE_C PSW Selector switch block NPAS_SW13, NPAS_SW31, NPAS_SW19, NPAS_SW91 PFOUT Cascade signal distributor

block NPAS_FOUT

PFFSUM Feedforward signal summing block

PAS_FFSUM, PAS_FFSUM_BL

PFUNC Function block NPAS_FUNK_VAR PASTM ASTM correction block PAS_ASTM1, PAS_ASTM2 PCFL Temperature and pressure

correction block NPAS_TP_CFL, NPAS_T_CFL, NPAS_P_CFL

PDFILE General-purpose data file NPAS_DFILE PTMCT Timer/counter NPAS_TM, NPAS_CT PCDATA Structure data NPAS_FFRD_ANLG, NPAS_FFWT_ANLG,

NPAS_FFRD_DINT, NPAS_FFWT_DINT, NPAS_FFRD_STS, NPAS_FFWT_STS

PUT Temperature control instrument block

SD_CDIC_UT, SD_CDIC_UT_HC

PUPM Power monitoring instrument block

SD_CPM_UPM, SD_CPM_UPM01, SD_CPM_UZ_PR

PPD Power demand instrument block

SD_CPM_PDEMAND


TI 34P02A03-01E July 31, 2014-00

E

E3.4 HMI Server/HMI Client E3.4.1 HMI Server

The HMI server delivers the data contained in control objects on the data server and display data for operation and monitoring windows to HMI clients. The HMI server has the following features: • Web server functionality: Delivers Web-compatible display data to

HMI Clients. • Session control: Establishes a session in response to an

authorized logon attempt by an HMI client and maintains and controls it.

• Data access functionality: Accesses a data server. • User authentication: Can restrict the privileges of each user to

read-only depending on the combination of user name entered at logon.


TI 34P02A03-01E July 31, 2014-00

E

E3.4.2 HMI Client Each HMI client uses a VDS Viewer to display operation and monitoring windows. An HMI client can be a personal computer running VDS or any computer on the same network. Each HMI client has the following features: • Graphic window display: Presents user-created operation and

monitoring windows. • Object view: Presents the instrument faceplate for

each control object. • Sound output (*1): Sound can be output upon occurrence of

an alarm. • Tuning window display: Presents windows for tuning various

parameters of each PAS POU object running on an FCN or FCJ.

*1: The message primitive (a graphic part for displaying messages) needs to be displayed at all times. Arbitrary WAV format files can be selected.

Uses the VDS Viewer to display operation and monitoring windows.

Enables remote control and monitoring using a VDS Viewer running on a PC

Audible alarms can be output and stopped.

Data serverVBA

FCN/FCJdriver



FCN/FCJdriver

Control objects

HMI client(VDS Viewer)

Generates operation and monitoring windows and delivers them to HMI clients.

Allows up to 50 HMI clients to concurrently access VDS with optional, additional HMI client licenses purchased. (A VDS basic license includes the license for only the first HMI client.)

Privileges of a user can be restricted to read-only depending on the combination of user name and password entered at logon.

Figure Generation (by HMI server) and display (by an HMI client) of windows for operation

and monitoring


TI 34P02A03-01E July 31, 2014-00

E

E3.4.3 Graphic Windows Various graphics parts (primitives) allow accurate system images to be presented, thus simplifying the operations.

General Specifications • The window size can be set arbitrarily for each window. • The data refresh interval is one second or longer (for only foreground data). • Colors: True colors

● Guideline for Capacity of Each Graphic Window • Data displayed or used in

modification conditions: Up to 200 • Modification conditions: Up to 100 (up to 8 conditions per primitive) • Graphs: Up to 4 • Computational expressions

for modifying data characters or coordinates: Up to 50

• Touch targets: Up to 400 • Graphic generic names: Up to 400 • Generic name sets: Up to 200

Modification Specifications

● Pattern modifications • Modification actions:

Color modification, disappearance, blinking, character modification, highlighting, function disable, bitmap change

• Modification type: Executes every time the specified condition is true or only when the window is opened and the condition is true at that time.

• Modification conditions: Up to eight conditions can be set per primitive.

● Coordinates modifications • Dynamic modification according to the value of the specified data item.

● Touch targets and pushbuttons • Provide access to a URL, monitoring window, logon dialog box, dialog box for

data entry, menu window, data setting, and printing.


TI 34P02A03-01E July 31, 2014-00

E

Graphics Primitives (Parts)

● Basic primitives Pens, straight lines, polylines, arcs, rectangles, fill areas, circles, ellipses, fans, markers, texts

● Control primitives Data character display, rectangle data bars, arrow data bars, circle data bars, line graphs, user-defined line graphs, bar graphs, step graphs, radar charts, X-Y graphs, touch targets, pushbuttons, messages, trend graphs

● Bitmap primitives Bitmaps

● Link parts A link part is a graphic part that represents a group of primitives. Link parts include instrument faceplates, ISA symbols, motors, pipes, pumps, switches, tanks, and valves.

Example of Graphics Primitives (Link Parts)

● Instrument Faceplate

Figure Faceplate of Device Tag

Figure Faceplate of Device Tag (DI, DO, AI, AO)


TI 34P02A03-01E July 31, 2014-00

E

Figure Faceplate of Process Tag

Figure Faceplate of Optional Application Portfolio


TI 34P02A03-01E July 31, 2014-00

E

Figure Faceplate of PAS POU


TI 34P02A03-01E July 31, 2014-00

E

Figure ISA Symbol


TI 34P02A03-01E July 31, 2014-00

E

Figure Motor

Figure Simple Motor

Figure Pipe


TI 34P02A03-01E July 31, 2014-00

E

Figure Simple Pipe


TI 34P02A03-01E July 31, 2014-00

E

Figure Pump

Figure Simple Pump

Figure Switch


TI 34P02A03-01E July 31, 2014-00

E

Figure Tank

Figure Valve

Figure Simple Valve

Figure Other


TI 34P02A03-01E July 31, 2014-00

E

E3.5 .NET Application The various components (graphic components, multi-task application development supporting components and so on) are practically usable on Visual Studio 2013/2010. Using these components, VDS can implement .NET application development and operation on Visual Studio 2013/2010. Use these components to make application on Visual Stadio.

VDS

OPC data link (*2)

< Data server >

Graphic (VDS Viewer)

HMI server

Graphic DesignerVisual Studio (*1)

< I/O object >

*1: Studio 2013/2010 is not supplied with VDS. Purchase is required separately.*2: "OPC Data Link Package for .Net" option is required separately in order to use

the OPC data link function.

.NET application

Figure .NET application

● Components A list of Components (ActiveX Control) is shown below.

Table List of controls can be run with VDS R7.10 or later Control Name Description Required Licenses

AlarmFsX2 Alarm summary display (VDS Basic) MsgHistX Historical messages display (VDS Basic) TreX2 Realtime/historical trend display Trend Package YfsSignal Signal transmission and reception between tasks Multi-task Package YfsBDAObj High-speed access to block data Multi-task Package YfsClock Timer specified by the interval or time (VDS Basic) YfsIsamMt Import, export and restoration of an ISAM file (VDS Basic) RunAsDialog User change dialog at the time of using the security (VDS Basic) (*1) SecurityLog Notification of a new record addition to a security

recorder file (VDS Basic)

PDemand Power demand graph display (VDS Basic) (OPC Data Link f or .NET) (*2)

*1: Extended Security Package License is required to use the RunAs dialog password management function including a change notice, a term notification of audit, the notice of expiration, and password change operation with RunAs Dialog Control.

*2: When assigning an object without programming, use the OPC data link function. (Assignment by programming is also possible)


TI 34P02A03-01E July 31, 2014-00

E

E3.6 Message Management Functions Message management functions, which are crucial in equipment and process operation and monitoring, are featured as standard. VDS’s message management performs integrated management of messages including errors, alarms, user operation logs, and process operation records occurring in the system programs, controllers and I/O devices, and user VB applications, and notifies them to operators in various ways.

Note: Alarms indicate messages that require a user to perform an acknowledgment action.

● Message Handling • Displays messages in the alarm summary (message primitive) • Saves messages to a message log file (and displays the contents in the message

primitive and Message Viewer) • Saves messages to a text file • Opens a dialog box displaying a message upon occurrence • Activates a voice output upon occurrence • Prints messages using a serial printer • Notifies a user application of occurrence

Note: At an HMI client, only the actions of a message primitive work. (The voice output and message printing functions for the messages currently shown in the message primitive are featured as part of the primitive’s standard functions.)

Messagelog file

Serialprinter

Voice output

Messageprimitive

Userapplications

System messages: Error and event messages output from VDS system programs

Process messages: Messages of events detected by a control object, such as operation logs

Process alarms: Alarms detected by a control object, such as high-limit and rate-of-change alarms

System alarms: Alarms notifying changes in statuses of FCN and FCJ autonomous controllers

User messages: Messages of general information generated by a VB application, such as operation logs

User alarms: Alarms generated by a VB application

MessageViewer

Dialogbox

Textfile

Message ManagementMessage Management

(Historical)

Messageprimitive

(Alarm summary) Figure Message Management Functions


TI 34P02A03-01E July 31, 2014-00

E

E3.7 Process Management Functions Process management performs integrated management of the various programs of the VDS system, including VDS system programs and VB application programs, and allows system startup and shutdown to be performed automatically.

● Process Management Overview • Administers the VDS operation mode and controls mode transitions • Controls system startup and shutdown actions • Starts user applications as specified • Issues an advance notice for a shutdown of the data server to user applications • Records the start and stop events of each program in the Windows event log

● VDS Operation Modes The table below shows the VDS operation modes.

Table VDS Operation Modes Mode Outline Description

Operation mode A mode for normal operations and debugging.

VDS automatically runs the system programs and registered VB applications.

Development mode

A mode for development such as configuring the data server.

VDS runs only the basic system programs such as message management.

Shutdown mode A mode for backup operations or the like.

All programs including message management are stopped.

Process Control ServerProcess Control Server

Basic system processes

Basic system processes

System option

processes

System option

processesUser

processesUser

processes

Startup file

-Mode Change Tool-Object Builder

-Mode Change Tool-Object Builder

Startup End Shutdown

Mode switch requestShutdown request

Windows event log

Figure Process Management Functions


TI 34P02A03-01E July 31, 2014-00

E

E3.8 Security for Operation VDS assures security against unauthorized access via a HMI Client by means of user name plus password authentication. The users can be divided into up to eight groups (one of which must be the group of users having administrative privileges to be allowed for all operations) and the ranges of permissible operations can be set differently for each group to prevent problems such as operation mistakes and ensure the system security. (A restriction cannot apply to monitoring [data viewing], however.)

● Restricts operations on VDS The ranges of permissible operations can be predefined for each user group: • Access to control objects via the HMI server, VB application or tuning windows for

FCN/FCJ controllers • Alterations to archived long-term data files of historical data acquired • Running of system programs (builders, tools, etc.) • Access to tuning panel • Switching of VDS mode between development and runtime • Changes to security log definitions • Alarm acknowledgment • Deleting messages in the message history file, changing the number of stored

messages • Stopping the sound of the HMI server from the HMI client

Table Example of Operational Restriction Settings for Each User Group User Group

A B C Tag Group1 Tag Group2 ─ Tag Group3 ─ ─ System programs starting ─ ─ VDS mode switching ─ ─ ─

● Security Logs The log of actions by each user during runtime can be saved to a CSV format file for every day for recording. (Whether to record actions can be specified for each subject of operations.)

● 21 CFR Part11 Security functions enables you to build systems which comply with FDA (U. S. Food and Drug Administration), 21 CFR Part 11 – rules concerning electronic record-keeping and electronic signatures that are acceptable as equivalent to paper records.


TI 34P02A03-01E July 31, 2014-00

E

E4. Application Development Environment Object-oriented engineering tools for all engineering tasks, from defining I/O device connections and data acquisition specifications up to creation of graphic windows, make application development much more efficient.

E4.1 Object Builder Object Builder is used for plugging I/O drivers into the I/O object and defining control objects on the data server.

Data serverVBA

FCN/FCJdriver

FCN/FCJdriver

I/O object

FA-M3driver

FA-M3driver

Control objects

VDS Viewer

ObjectBuilder

GraphicDesigner


FCN/FCJdriver

FCN/FCJdriver

Figure Application Development Environment (Object Builder)

● Plugging in I/O Drivers Simply select a proper driver for each controller or I/O device to be connected and make the basic communication settings such as an IP address. There’s no need to write a communication program.

Figure Example of Plugging in I/O Driver


TI 34P02A03-01E July 31, 2014-00

E

● Defining Control Objects Define control objects suitable for the types of data residing in the individual I/O devices and controllers. A device tag object used for communication with a programmable logic controller or the like can be defined by setting values in a table of the settings such as the tag name, device address inside the communication target, scaling factor, whether to enable integration, and alarm processing specifications. For an FCN or FCJ controller, the necessary control objects will be defined upon importing the PAS POUs used to build the control application and their parameter settings into Object Builder.

Figure Example of Control Object


TI 34P02A03-01E July 31, 2014-00

E

E4.2 VBA Programs on Data Server To allow the functions of the individual control objects to be enhanced, the data server implements Visual Basic Applications Edition. Use a VBA program in conjunction with multiple control objects to embody a block of user-specific functions and group them for reuse.

● Reuse of Engineering Know-how Using VBA programs, which can run on the data server, will materialize a block of functions you specifically want and will reuse it. An example of such reusable parts is a part that will perform specified calculations based on various acquired data immediately when a predefined digital input signal turns on, and outputs the calculation result via an analog output object.

Create a block of specific functions with multiple control objects and a VBA program.

Create a block of specific functions with multiple control objects and a VBA program.

ReuseReuse

EquipmentA-1

EquipmentA-1

EquipmentA-2

EquipmentA-2

EquipmentA-3

EquipmentA-3

Equipment AEquipment A

Group them and define as a software part. Group them and define as a software part.

AIAI

DIDI

AOAO

DODO

AIAI

DIDI

AOAO

DODOVBAVBA

Figure Example of Reuse Creating a Block of Specific Functions


TI 34P02A03-01E July 31, 2014-00

E

E4.3 Graphic Designer Graphic windows running on a Web browser can be created by simply pasting supplied graphic parts (primitives) and specifying their actions in Graphic Designer.

● Creating Graphic Windows A graphic window can be easily created using primitives supplied by Graphic Designer as described in Section E3.4.3, “Graphic Windows.” After drawing static graphics, open the property sheet of each pasted primitive and set dynamic functions such as the modification conditions and pushbutton function.

Data serverVBA

FCN/FCJdriver

FCN/FCJdriver

I/O object

FA-M3driver

FA-M3driver

Control objects

VDS Viewer

ObjectBuilder

GraphicDesigner


FCN/FCJdriver

FCN/FCJdriver

Figure Application Development Environment (Graphic Designer)

Figure Example of Graphic Designer


TI 34P02A03-01E July 31, 2014-00

E

E5. Software Products E5.1 Styles of Software Supply

VDS software products largely consist of a software medium containing various programs and licenses to enable the individual programs to run.

Software Medium (DVD-ROM) The software medium contains the basic and all optional software programs for VDS, and the respective electronic documents. Programs should be installed in the personal computer on which they are to be run.

● Software Medium (DVD-ROM) Description

Model NT201AJ VDS software media Suffix Codes

-P Programs (including electronic documents) C DVD-ROM 1 Always 1 1 Always 1 E English version

Note: The basic VDS software, each type of optional software, and electronic documents are included.

Software Licenses A software license needed to run each of the programs contained in the software medium is supplied in paper form, called an order ID sheet, containing the order ID and password. Access the specified Web site of Yokogawa and enter the order ID and password. Then, the respective license IDs for the supplied software titles will be downloaded.

SEE ALSO For more information about the STARDOM software license, refer to B7.1, “License.”

A VDS basic software license is available in two versions. • Full-time version: The full-time version has both development and runtime environments; • Runtime version: The runtime version offers only the runtime environment. Either version includes a license for one HMI client (Web browser) to access VDS, and is further available in eight types depending on the number of definable control objects. Upgrade kits for increasing the number of definable objects and additional HMI client licenses for adding HMI clients that can concurrently access VDS are also available.


TI 34P02A03-01E July 31, 2014-00

E

● Basic Software License Description

Model NT610FJ VDS basic software license for full-time NT610RJ VDS basic software license for run-time

Suffix Codes

-L License U ID module for USB 00 50 objects 01 100 objects 02 200 objects 05 500 objects 10 1000 objects 15 1500 objects 20 2000 objects 50 5000 objects E English version

● Upgrade Kit Description

Model NT620FJ VDS Upgrade kit for full-time NT620RJ VDS Upgrade kit for run-time

Suffix Codes

-L License W Issued at Web 01 50 to 100 objects 02 100 to 200 objects 05 200 to 500 objects 10 500 to 1000 objects 15 1000 to 1500 objects 20 1500 to 2000 objects 50 2000 to 5000 objects A Standard

● HMI Client Additional Licenses Description

Model NT625AJ HMI Client additional licenses Suffix Codes

-L License W Issued at Web 01 Add 1 Client 05 Add 5 Clients A Standard


TI 34P02A03-01E July 31, 2014-00

E

E5.2 Optional Packages Extensive optional packages are available for VDS to address various needs. Table Lists of Option Package with VDS

Option Package Specifications Description

Report Package GS 34P02H01-01E See section F4.2 Trend Package GS 34P02H02-01E See section F4.3 Test Package GS 34P02M01-01E See section F4.5 Multi-task Package GS 34P02H04-01E See section F4.4 Extended Security Package GS 34P02H07-01E See section F4.11 MELSEC Driver GS 34P02G01-01E See section F4.6 SYSMAC Driver GS 34P02G06-01E See section F4.7 OPC Server Driver GS 34P02G08-01E See section F4.8 DARWIN Driver GS 34P02H05-01E See section F4.9 OPC Data Link Package for.NET GS 34P02H51-01E See section F4.10

SEE ALSO For more information about the General Specifications, refer to Part-F “General Specifications.”


TI 34P02A03-01E July 31, 2014-00

E

E5.2.1 Report Package The report package has the following features. • Allows various settings such as the report type, data to be acquired,

and summarization specifications to be made easily using a builder program.

• Enables the creation of many types of reports such as daily, monthly, lot(*1), and simplified batch(*2) reports.

• Enables effortless development of print formats in Microsoft Excel. • Allows report data to be recorded to an RDB such as SQL Server.

*1: A lot report records the values of specified data items at specified intervals over a specified period (may be used for a shift report).

*2: Simplified batch report records the times when each batch has started and ended, and snapshot values of specified data items at each batch end or the differences in values at each batch end from the start, over a specified period.

Table Major Specifications of Report Package Report types Daily, monthly, daily/monthly, lot, and simplified batch reports Acquisition blocks

Up to 32 blocks for the 5 types of reports above; up to 4 blocks for a total of lot and simplified batch reports

Acquisition data Up to 32 items per acquisition block Acquisition interval

For a daily or lot report, select from 1, 2, 5, 10, 30, and 60 minutes. For a monthly report, select from 30, 60, and 120 minutes.

Recording interval

For a daily or lot report, select from 5, 10, 20, 30, 60, and 120 minutes. For a monthly report, fixed to 1 day.

Record storage period

10 years for an Excel file 1 year for daily and monthly reports in internal database 1 month for lot and simplified batch reports in internal database

System requirements

Excel (Windows 7): Microsoft Excel 2013/2013 SP1 32-bit version Microsoft Excel 2010 SP2 32-bit version

Drawing

Approval

Fresh Water Treatment Daily Report Date

Sea Water Fresh Water DP Chemical Elec. Power PH TemperatureM3PM M3PM PSI GMPM KWH PH C

1:00 AM 97.26 88.51 37.25 4.57 35.98 7.5 19.82:00 AM 94.23 85.75 37.12 4.56 35.38 7.5 19.83:00 AM 89.46 81.41 37.13 4.43 35.71 7.5 19.54:00 AM 85.98 78.24 37.21 4.52 34.34 7.5 19.45:00 AM 89.99 81.89 37.22 4.61 34.78 7.5 19.46:00 AM 102.56 93.33 37.88 4.99 36.12 7.5 19.37:00 AM 120.34 109.51 38.11 5.22 39.99 7.5 19.48:00 AM 125.45 114.16 38.01 5.31 45.34 7.4 19.89:00 AM 97.26 88.51 37.98 5.21 47.34 7.4 20.1

10:00 AM 97.26 88.51 37.25 4.57 42.33 7.4 20.111:00 AM 97.26 88.51 37.25 4.57 35.98 7.4 20.212:00 PM 97.26 88.51 37.25 4.57 35.98 7.5 20.21:00 PM 97.26 88.51 37.25 4.57 35.98 7.5 20.32:00 PM 97.26 88.51 37.25 4.57 35.98 7.5 20.33:00 PM 97.26 88.51 37.25 4.57 35.98 7.5 20.44:00 PM 97.26 88.51 37.25 4.57 35.98 7.5 20.45:00 PM 97.26 88.51 37.25 4.57 35.98 7.5 20.36:00 PM 97.26 88.51 37.25 4.57 35.98 7.5 20.37:00 PM 97.26 88.51 37.25 4.57 35.98 7.5 20.28:00 PM 97.26 88.51 37.25 4.57 35.98 7.5 20.19:00 PM 97.26 88.51 37.25 4.57 35.98 7.5 19.9

10:00 PM 97.26 88.51 37.25 4.57 35.98 7.4 19.911:00 PM 97.26 88.51 37.25 4.57 35.98 7.5 19.812:00 AM 97.26 88.51 37.25 4.57 35.98 7.5 19.7

21-Feb-2002

Figure Example of Daily Report


TI 34P02A03-01E July 31, 2014-00

E

E5.2.2 Trend Package The trend package has the following features. • Allows continuous data acquisition in which data is acquired at all

times, as well as batch acquisition in which data acquisition begins and ends in response to external commands.

• Saves acquired data for every day to a file if long-term archive is specified, and allows such archived long-term data to be retrieved into a trend graph.

• Allows historical data thus acquired to be accessed from applications such as VB programs.

• Enables archived long-term data to be exported to a CSV file.

Major Specifications of Trend Package

● Historical Data Acquisition Objects whose data are to be acquired

Up to 1024 tags (= 32 blocks x 4 groups x 8 tags)

Acquisition interval A submultiple of 86,400 from 1 to 86,400 in seconds. (However, an interval of 10 seconds or less can only be set for up to 16 blocks.)

Acquisition period 60 to 86,400 seconds. (If long-term archive is specified, the acquired data is saved to a file every day or every specified number of days.)

Simultaneity of data Assured within each historical data block.

● Trend Graph Display Number of pens 8 per primitive Scroll Possible along both of the time and data axes. Expansion/reduction Time axis: The number of data values to be displayed at one time can be

specified from 2 to 10800. Data axis: Can be expanded and reduced arbitrary from 300% to 10%.

Paste a trend display primitive onto a graphic window to display a trend graph.

Data server

Historical data acquisition

Acquired data can be automatically assigned to trend pens.

Archived long-term

data

Historical data access

8 objects per acquisition

group

Definable acquisition

blocks: Up to 32

Acquisition groups:4 groups per block

Visual BasicAcquired data is accessible for VB.

Figure Image of Trend Package Function


TI 34P02A03-01E July 31, 2014-00

E

E5.2.3 Test Package The test package has the following features. Note: The test package provides Trace Manager with the ability to start and stop this object tracing functionality for

FCN/FCJ.

● Simulation • Needs no I/O devices, calibrators, and test switches for debugging. • Needs no debugging program. • Allows the users to build applications while checking the operation.

● Device Monitor • Enables the users to view and change the values and statuses held in connected

PLCs during debugging.

TIP Device Monitor is applicable to the following PLCs.

• FA-M3

• MELSEC A and Q Series

• SYSMAC Series controllers

SEE ALSO For the supported CPU and communication module models of the PLCs, refer to F4.5, “Test Package” (GS 34P02M01-01E).

● Object Trace • Records changes in data with timed traces to a CSV format file and thus enables

applications that depends on execution timings to be analyzed without need of developing a dedicated program.

AI1.Cv = 370

Data server

HMI server

AIAI

Simulated input data Simulated input data

DIDI TXTTXT

A value can be input via a dialog box. A value can be input via a dialog box.

In addition to the provided standard patterns, arbitrary patterns can be defined by users.

In addition to the provided standard patterns, arbitrary patterns can be defined by users.

I/O object

DI1

DI2

AI1

Pattern inputs

One-shot input

Figure Image of Simulation Function


TI 34P02A03-01E July 31, 2014-00

E

E5.2.4 Multi-task Package When creating a Visual Basic program, it may often require events to be notified bilaterally with VDS (between tasks) and data to be shared with VDS. Multi-task Package provides components (objects) that effortlessly materialize these functions.

● Event Notification Events can be notified between VDS and VB programs. The receiver need not check the event occurrences periodically and quick response is obtained. • Data of up to 1 Kbyte can be transmitted with each event notification. • Notifications can be made bidirectionally with VB programs running in another

computer over the network.

Visual Basic

u Bilateral notifications of event occurrences with Visual Basic programs

Communications signal objects

Data server

HMI server

I/O object

A maximum of 1 KB data can be transmitted together!

Visual Basic

Figure Image of Event Notification Function


TI 34P02A03-01E July 31, 2014-00

E

● Data Sharing Data can be shared between VDS and user programs. • A block data object running in the data server can hold different types of data

such as characters and numbers in a total of up to 32 Kbytes. • A block data object functions as a buffer for collectively exchanging data between

the data server and an I/O device(*1). • Multiple VB programs can access the same data at all times. • Using multiple block data objects and dividing and assigning the data you want to

share to those objects, will allow each task to access but the necessary block or blocks.

• Access can be made by referring to the variable name, which makes programs easier to read and understand.

• Data can be shared with VB programs running in another computer via the network.

*1: The volume of data which are collectively exchangeable depends on I/O devices. It is possible to collectively exchange up to 2 Kbytes of data between the data server and an autonomous controller FCN/FCJ.

Visual Basic

Data server

HMI server

I/O object

Each block data object can hold a maximum of 32 KB data!

u Exchange of array data at a time with Visual Basic programs

Block data object

Block data access object s

Visual Basic

Figure Image of Data Sharing Function


TI 34P02A03-01E July 31, 2014-00

E

E5.2.5 Extended Security Package Extended Security Package augments the VDS standard security in terms of the added work file protection and enhanced user password security.

● Work File Protection Attempts to falsify any of the files created by VDS during operation, namely the message text files, long-term archive files (created when using Trend Package), and logging report files, including write access and deletion, moving, and copying of those files, can be prevented.

Table Work File Protection Function File type Read Write List Delete Move Copy Create

Standard

Security log files ─ ─ ─ ─ ─ ─ Message text files Long-term archive files Logging report files

Extended

Message text files When not using the folder Protected

─ Long-term archive files ─

Logging report files ─ Message text files When using

the folder Protected (*1)

─ ─ ─ ─ ─ Long-term archive files ─ ─ ─ ─ ─

Logging report files ─ ─ ─ ─ ─

: Permitted

─: Prohibited

*1: The folder Protected, located in the Data folder of the VDS installation folder, has strengthened security. Specifying that files be created under the folder Protected allows you to prohibit them from being deleted and moved, as well other tasks being performed on them.

Note: If a user account for working on a computer running VDS belongs to an ASTMAC Manager group, the user is assigned full control of file access privileges and can perform any task. An ASTMAC Manager group has special privileges. The range of tasks that can be performed by this group cannot be changed and tasks on all items to be operated are permitted.

● Password Management Function The passwords for VDS user accounts can be modified during operation. In response to any user attempt to log on to VDS, password administration displays a dialog box prompting the user to change the password if it is the first-time logon for the user, or if the validity of the password is about to expire or has already expired.


TI 34P02A03-01E July 31, 2014-00

E

E5.2.6 MELSEC Driver MELSEC Driver offers two types of connection:

● EZSocket Connection EZSocket connection uses the incorporated EZSocket middleware. The differences in protocol between different models or different network styles usually require a specific I/O driver for each connection. EZSocket absorbs those differences and allows VDS to perform access in accordance with a fixed protocol.

Table EZSocket Connection Supported models MELSEC-A Series, QnA Series, Q Series, FX Series, L Series. Connection interface Serial, Ethernet, MELSECNET II, MELSECNET/10, CC-Link, etc. via EZSocket Functions Reading and writing of sequence elements (also referred to as devices)

Absorbs the difference between drivers

VDS

driverdriverdriverdriver

Figure Image of EZSocket Middleware

● Asynchronous Connection Asynchronous connection allows event notifications from MELSEC controllers in addition to periodic data acquisition. Event reception is not performed as a continuous task, so this type of connection helps develop applications of a high throughput.

Table Asynchronous Connection Supported models MELSEC-A Series, QnA Series, Q Series (except QnU) (*1) Connection interface Ethernet (*2), RS-232-C Functions Reading and writing of sequence elements (also referred to as devices), and

reception of asynchronous data

*1: Only the devices covered by the A series can be accessed. Devices Ms and Ds between 9000 to 9999 cannot be accessed.

*2: Operates within the A compatible 1E frame.


TI 34P02A03-01E July 31, 2014-00

E

E5.2.7 SYSMAC Driver SYSMAC Driver implements the OMRON FinsGateway middleware.

● FinsGateway Usually, the differences in protocol between different models or different network styles require a specific I/O driver for each connection. FinsGateway absorbs those differences and allows VDS to perform access in accordance with a fixed protocol. (Fins is an acronym of factory interface network service.) Fins: Factory Interface Network Service

Table FinsGateway Communication interface Interfaces supported by FinsGateway including serial interface,

Ethernet, Controller Link, and SYSMACLINK Types of access to device memory Access to contiguous bits or access to contiguous words Asynchronous data reception Possible only from the FinsGateway CPU unit (*1)

*1: A virtual CPU unit exists in FinsGateway and is called FinsGateway CPU unit. FinsGateway CPU unit contains variable areas for CIOs and DMs, to which SYSMAC Series controllers on the network can perform reading and writing access.

FinsGateway

Ethernet SYSMACLinkSerial Controller

Link

VDS Absorbs the difference between drivers

Figure Image of FinsGateway


TI 34P02A03-01E July 31, 2014-00

E

E5.2.8 OPC Server Driver This optional OPC server driver is used to connect third-party OPC servers to the VDS. Table Major Specifications of OPC Server Driver Interface OPC DA2.0 Asynchronous data reception

Not available

• Either an OPC server running in the same computer with VDS or an OPC server running in a different computer can be connected.

SEE ALSO For the interfaces and methods that need to be implemented in the connected server, refer to F4.8, “OPC Server Driver” (GS 34P02G08-01E).

Other suppliers’ PLCs

Data serverVBA

HMI server

I/O objectOPC

ServerDriver

OPCServerDriver

Control objects

OPCserver

Tag-based data exchange with OPC servers

Figure Example of Connected OPC Server Driver


TI 34P02A03-01E July 31, 2014-00

E

E5.2.9 DARWIN Driver DARWIN Driver enables Yokogawa DARWIN Series data acquisition units and DAQSTATION networking paper-free recorders to be connected. • Connecting DARWIN units actualizes multipoint direct analog-input

logger system at low cost. • Connecting DAQSTATIONs enables data fetched into the DAQSTATIONs

to be used in VDS for reports and display in graphic windows. No extra wiring is required to connect those recorded signals to VDS.

Table Major Specifications of DARWIN Driver Supported models DARWIN Series DA100 and DR230/240 (style 8 or later)

DAQSTATION DX1000, DX2000, DX1000N, DX100, DX200, DX100P, DX200P, CX1000 and CX2000 (*1)

Communication interface Ethernet TCP/IP Functions - Reading snapshot values (measured values and calculated values) with

real number conversion based on the floating point - Reading and writing relay statuses (for Model DA100 only) - Controlling (staring, stopping, and resetting) the calculations

*1: In the communication with CX1000 or CX2000, the VDS system can only read the measurement channel #1 to #20 and PV/SP/OUT channel #101 to #118 and #201 to #248.

Ethernet

．．．．．．．．．．．．

DA100DX100

DAQSTATIONDARWIN

Figure Example of Connected DARWIN and DAQSTATION


TI 34P02A03-01E July 31, 2014-00

E

E5.2.10 OPC Data Link Package for .NET OPC Data Link Package for .NET is an optional package for linking various control properties in Microsoft Visual Studio (hereinafter referred to as Visual Studio) — Visual Basic or C# to control object properties on VDS data server without using a program. This package consists of OPC Data Link Components and OPC Data Link Definition Addin.

Figure Overview

Function Specifications

● OPC Data Link Functions Table OPC Data Link Functions

Item Specifications Interface OPC DA2.0a (*1) Data read Notification of data changes from OPC server Data write Asynchronous write (*2) Number of OPC servers connected 1/component Remote server connection Available

*1: Can also be connected to the VDS data server and the OPC server of the FCN/FCJ.

*2: Asynchronous data write is performed by calling up methods from the OPC data link components.


TI 34P02A03-01E July 31, 2014-00

E

● Modify Functions Distributing a data based on conversion type to each control.

Table Modify Functions Function Description

None No conversion Numeral to Color Converts numeric values to color codes Numeral to Text Converts numeric values to character-string data

Numeral to Boolean Converts numeric values to results having one of two values compared with specified values

Text to Color Converts character-string data to color codes Text to Numeral Converts character-string data to numeric values Text to Text Converts character-string data to other character-string data

Text to Boolean Converts character-string data to results having one of two values compared with specified character-string data

Boolean to Color Converts Boolean values to color codes Boolean to Numeral Converts Boolean values to numeric values Boolean to Text Converts Boolean values to character-string data Invert Boolean Inverts Boolean values Scale Conversion Converts scale factor of numeric value Numeral to Alarm color Checks (HH, HI, NR, LO, LL) alarms and converts them to specified color codes Numeral to Alarm text Checks (HH, HI, NR, LO, LL) alarms and converts them to text

● OPC Data Link Define Functions Data links are defined by OPC Data Link Definition Addin. This Addin is a Visual Studio addin that allows data acquisition from the OPC server, function modification and data distribution to a control without using a program. Data link designations can be intuitively defined by selecting browsed OPC data and controls. The defined information is stored in an XML file referenced by the OPC data link component.

i

TI 34P02A03-01E July 31, 2014-00

Revision Information Document name : STARDOM Technical Guide Document No. : TI 34P02A03-01E Dec. 2007/First Edition

• New publication

Sep. 2008/Second Edition • Support for VDS/ASTMAC R6.01

• Supoprt for FCN/FCJ R2.01

• Error corrections

Oct. 2009/Third Edition • Supoprt for FCN-RTU

• Supoprt for NFBU050 for FCN use

• Support for VDS/ASTMAC R6.20



Aug. 2010/Fourth Edition • Support for VDS/ASTMAC R6.30

• Support MELSEC L Series Ethernet


• Abolish Control Loop Definition Funtion


Jun. 2011/Fifth Edition • Support for VDS/ASTMAC R7.01


• Supoprt for Windows 7

• Addition of VDS Viewer

• Addition of Communication Cables


Aug. 2012/Sixth Edition • Support for VDS/ASTMAC R7.10


• Addition of communication modules (NFLC121, NFLP121)


Jun. 2013/Seventh Edition • Support for VDS R7.20



ii

TI 34P02A03-01E July 31, 2014-00

July 2014/Eighth Edition • Support for VDS R7.30


• Support for Windows 7 SP1 (64-bit)

• Windows XP was deleted.

• Update of compliant standards.

For Questions and More Information

If you have any questions, you can send an E-mail to the following address.

E-mail:[email protected]

Written by: Yokogawa Electric Corporation

Published by: Yokogawa Electric Corporation

2-9-32 Nakacho, Musashino-shi, Tokyo 180-8750, Japan

technical information stardom technical guide · 2019. 4. 26. · network-based control system...

Documents