SYSMAC OPC Server V2.6 Operation Manual

Programmable Controller

SYSMAC

SYSMAC OPC Server V2 Operation Manual V2.6

(1/95)

SYSMAC OPC Server V2.6 Operation Manual

Notice: OMRON products are manufactured for use according to proper procedures by a qualified operator and only for the purposes described in this manual. The following conventions are used to indicate and classify precautions in this manual. Always heed the information provided with them. Failure to heed precautions can result in injury to people or damage to property.

DANGER

Indicates an imminently hazardous situation which, if not avoided, will result in death or serious injury.

WARNING

Indicates a potentially hazardous situation which, if not avoided, could result in death or serious injury.

Caution

Indicates a potentially hazardous situation which, if not avoided, may result in minor or moderate injury, or property damage.

(2/95)

SYSMAC OPC Server V2.6 Operation Manual

Safety Precautions Caution

Confirm safety at the destination node before transferring a program to another node or changing contents of the I/O memory area. Doing either of these without confirming safety may result in injury.

Applications Precautions Observe the following precautions when using the SYSMAC OPC Server V2. -

Fail-safe measures must be taken by the customer to ensure safety in the event of incorrect, missing, or abnormal signals caused by broken signal lines, momentary power interruptions, or other causes.

-

Confirm that no adverse effect will occur in the system before attempting any of the following. Not doing so may result in an unexpected operation.

-

-

Changing the operation mode of the PLC.

-

Force-setting/force-resetting any bit in memory.

-

Changing the present value of any word or any set value in memory.

Be sure that all the mounting screws, terminal screws, and cable connector screws are tightened to the torque specified in the relevant manuals. Incorrect tightening torque may result in malfunction.

-

Check the user program for proper execution before actually running it on the Unit. Not checking the program may result in an unexpected operation.

-

The tag setting file for the SYSMAC OPC Server V2 may not be saved in the event of a system failure or power interruptions. Saving the file regularly is recommended.

-

Check whether scaling is performed and whether scaling setting is correct in each tag before scaling.

(3/95)

SYSMAC OPC Server V2.6 Operation Manual

TABLE OF CONTENTS 1.

Overview ............................................................................................................................................ 8 1.1. 1.2. 1.3.

2.

Features of SYSMAC OPC Server V2 ....................................................................................... 8 System Requirements................................................................................................................. 9 Connection Target .................................................................................................................... 10 Setup ................................................................................................................................................ 13

2.1. 2.2. 2.3. 2.4. 3.

Uninstalling old version of SYSMAC OPC Server and FinsGateway................................... 13 Installing ................................................................................................................................... 13 Uninstalling .............................................................................................................................. 23 File Configuration..................................................................................................................... 26 Basic Operations ............................................................................................................................ 27

3.1. Starting ..................................................................................................................................... 27 3.2. Window Contents...................................................................................................................... 28 3.2.1. Configuration of Toolbar ......................................................................................................... 29 3.2.2. Configuration of Popup Menu ................................................................................................. 29 3.3. File Menu .................................................................................................................................. 31 3.4. Edit Menu.................................................................................................................................. 32 3.5. Add Menu .................................................................................................................................. 33 ...................................................................................................................................... 34 ....................................................................................................................................... 36 ........................................................................................................................................... 37 ........................................................................................................................ 40 ................................................................................................................................ 41 Separate sheet 1. Data type to be set to the area and its address range ........................................... 45 Separate sheet 2. ASCII conversion specification............................................................................... 46 Separate sheet 3. Simulation type ....................................................................................................... 47 Separate sheet 4. Scaling specification............................................................................................... 48 3.6. View Menu ................................................................................................................................ 51 3.7. Tool Menu.................................................................................................................................. 51 3.7.1. FINS Communications ............................................................................................................ 55 3.7.2. Device Connection Monitoring ................................................................................................ 55 3.8. Help Menu................................................................................................................................. 56 3.9. Write Tag................................................................................................................................... 57 4.

Starting and Setting of Network.................................................................................................... 57 4.1.

5.

Setting of Network.................................................................................................................... 59 Tag Convert Function..................................................................................................................... 62

5.1. Tag Import Function ................................................................................................................ 62 5.1.1. Import from CSV file(Device,Tag)........................................................................................... 62 5.1.2. Import of CX-Process version1 Monitor Tag File.................................................................... 65 5.1.3. Import of CX-Process version2 or later CSV Tag File ............................................................ 66

(4/95)

SYSMAC OPC Server V2.6 Operation Manual

5.1.4. Import of CX-Programmer V1.x Project .................................................................................. 68 5.1.5. Import of CX-Programmer version2 or later Project ............................................................... 70 5.2. Tag Export Function................................................................................................................. 72 5.2.1. Export to CSV File(Device,Tag).............................................................................................. 72 5.2.2. Export to CSV file for RSView32............................................................................................. 74 6.

Using from OPC Client ................................................................................................................... 76 6.1. Using from OPC Sample Client (Local Connection)............................................................... 77 6.2. Using from OPC Sample Client (Remote Connection) ........................................................... 78 6.3. Using from RSView32 V6.3...................................................................................................... 82 6.3.1. Registration of SYSMAC OPC Server V2 to RSView32......................................................... 83 6.3.2. Registration of a Tag to RSView32......................................................................................... 84

Appendix 1

Response Performance (Reference Value).................................................................. 89

Appendix 2

OPC Implementation Interface ...................................................................................... 90

1. OPC Automation Interface................................................................................................................ 90 2. OPC Custom Interface....................................................................................................................... 91

(5/95)

SYSMAC OPC Server V2.6 Operation Manual

Introduction Thank you for purchasing the SYSMAC OPC Server V2. The SYSMAC OPC Server V2 is a local/remote server that runs on WindowsNT/ 2000/XP, corresponding to OPC Data Access1.0a/2.0. This provides you with an environment to connect the OPC client to OMRON's Programmable Logic Controllers (described as PLC hereafter). This manual explains how to operate the SYSMAC OPC Server V2 in detail. SYSMAC, FINS, and CX-Programmer are trademarks of Omron Corporation. Microsoft, Windows, WindowsNT, Windows2000, WindowsXP and Visual C++ are trademarks of Microsoft Corporation. Other company names and product names are trademarks of each corresponding company.

Intended Audience This manual is intended for the following personnel, who must also have knowledge of electrical systems (an electrical engineer or the equivalent). -

Personnel in charge of installing FA systems.

-

Personnel in charge of designing FA systems.

-

Personnel in charge of managing FA systems and facilities.

General Precautions -

The user must operate the product according to the performance specifications described in the operation manuals.

-

Before using the product under conditions which are not described in the manual or applying the product to nuclear control systems, railroad systems, aviation systems, vehicles, combustion systems, medical equipment, amusement machines, safety equipment, petrochemical plants, and other systems, machines, and equipment that may have a serious influence on lives and property if used improperly, consult your OMRON representative.

-

Make sure that the ratings and performance characteristics of the product are sufficient for the systems, machines, and equipment, and be sure to provide the systems, machines, and equipment with double safety mechanisms.

-

This manual provides information for operating the SYSMAC OPC Server V2. Be sure to read this manual before attempting to use this product and keep this manual close at hand for reference during operation.

(6/95)

SYSMAC OPC Server V2.6 Operation Manual

Safety Precautions Caution

Confirm safety at the destination node before transferring a program to another node or changing contents of the I/O memory area. Doing either of these without confirming safety may result in injury.

Caution

Scaling by OPC Server may result in reading and writing a value different from the case when scaling is not performed and cause unexpected malfunction or a notification error, which may lead to an accident. Check whether scaling is performed and whether scaling setting is correct in each tag before scaling.

Applications Precautions Observe the following precautions when using the SYSMAC OPC Server V2. -

Fail-safe measures must be taken by the customer to ensure safety in the event of incorrect, missing, or abnormal signals caused by broken signal lines, momentary power interruptions, or other causes.

-

-

Confirm that no adverse effect will occur in the system before attempting any of the following. Not doing so may result in an unexpected operation. -

Changing the operation mode of the PLC.

-

Force-setting/force-resetting any bit in memory.

-

Changing the present value of any word or any set value in memory.

Be sure that all the mounting screws, terminal screws, and cable connector screws are tightened to the torque specified in the relevant manuals. Incorrect tightening torque may result in malfunction.

-

Check the user program for proper execution before actually running it on the Unit. Not checking the program may result in an unexpected operation.

-

The tag setting file for the SYSMAC OPC Server V2 may not be saved in the event of a system failure or power interruptions. Saving the file regularly is recommended.

(7/95)

SYSMAC OPC Server V2.6 Operation Manual

1.

Overview 1.1.

Features of SYSMAC OPC Server V2

The SYSMAC OPC Server V2 is a local/remote server that runs on WindowsNT/2000/XP, corresponding to OPC Data Access1.0a/2.0. This provides you with an environment to connect the OPC client to OMRON's Programmable Logic Controllers (described as PLC hereafter). [Features] - Easily connected from various OPC client applications. Using an OLE Automation interface allows to easily connect from Visual Basic5.0 or later / Excel97 or later. - Supports multiple network connections (Host link, Controller Link, and Ethernet etc.). - Provides an Explorer-like interface to create, indicate, and monitor tag data. - Created tag data can be saved and read as a tag setting file (*.sdb). - The IO simulation mode allows to connect and test an OPC client application without connecting an actual device. - Imports Symbols (tags) in the ladder program created by the programming tool for Omron’s PLC (CX-Programmer). Also, exports to a CSV-format file, which can be imported to the RSView32 tag database. - Imports a tag setting file created by the software tool for the Omron’s Loop Control Unit (CX-Process). - For a WORD/DWORD-type tag, BCD conversion can be performed; and for a STRING-type tag, Shift-JIS (Japanese edition) and ASCII (English edition) conversion can be performed. - Directly accesses Omron’s Loop Control Board (LCB) and Loop Control Unit (LCU).

OPC Client (Remote)

OPC Client (Local)

COM1

COM2

Custom i/f

Automation i/f

Import

SYSMAC OPC Server Tag data(*.sdb)

Omron’s PLC/LCB/LCU

Export FinsGateway Event Memory (CIO/DM)

Controller etc.

Link/Ethernet

Omron’s PLC/LCB/LCU

(8/95)

Omron’s software tool CX-Programmer .CX-Process

HMI software RS-View32

SYSMAC OPC Server V2.6 Operation Manual

1.2.

System Requirements

The following hardware and software are required to use the SYSMAC OPC Server V2. Computer: -

IBM PC/AT compatible machine CPU: Intel Pentium / Celeron 400 MHz or faster Main memory: 128 MB or grater Hard disk: 100 MB or more available space

Software: OS: Windows NT 4.0 Workstation + Service Pack 3 or later versions Windows2000 Professional + Service Pack 3 or later versions To connect OPC Server with RS-View, RS-View patch software for Windows2000(Japanese) SP3 is required separately1. - WindowsXP Professional Edition Communications middleware (FinsGateway): - If your OS is WindowsNT: FinsGateway Version 2 + FinsGateway Update 2.14 FinsGateway Version 3.20 or later versions (FinsGateway Version2003 is unsupported.) - If your OS is Windows2000: FinsGateway Version 2 + FinsGateway Update 2.14 FinsGateway Version 3.20 or later versions FinsGateway Version2003 - If your OS is WindowsXP: FinsGateway Version 3.20 or later versions FinsGateway Version2003 -

Note 1. FinsGateway V3 and Version2003 are included in this product, no need to be purchased separately. 2. The administrator authority is required to execute this software. 3. Operations with Windows 9x/Me are not assured. 4. SYSMAC OPC Server does not support the “Fast User Switching” Function(WindowsXP). 5. SYSMAC OPC Server does not support “hibernation”(WindowsXP). 6. When using OPC Server in a remote environment, the settings for Fire Wall (WindowsXP) and DCOM are required.For more information, refer to the support information for Microsoft and OPC Foundation.

1

The patch is provided by Rockwell Automation. (9/95)

SYSMAC OPC Server V2.6 Operation Manual

1.3.

Connection Target

The followings show PLCs and networks connectable to the SYSMAC OPC Server V2. - SYSMAC CS1/CJ1 Series SYSMAC CS1 SYSMAC CS1-H SYSMAC CJ1 SYSMAC CJ1-H SYSMAC CJ1M SYSMAC CS1D SYSMAC CS1 board Network Host link (Serial) Toolbus CS/CJ

Model CS1H/G - CPU**(-V1) Model CS1H/G - CPU**H Model CJ1G - CPU** Model CJ1H/G - CPU**H Model CJ1M-CPU** Model CS1D-CPU**H Model CS1PC - PCI01 - DRM Requirement

Computer COM port attached to the computer.

Controller Link

Controller Link Support Board Model 3G8F7-CLK21/12/52 Model 3G8F5-CLK21/11

Ethernet (UDP)

WindowsNT/2000/XP-compatible Ethernet board

Ethernet (TCP/UDP)

WindowsNT/2000/XP-compatible Ethernet board

SYSMAC LINK

SYSMAC LINK Support Board Model 3G8F7-SLK21/11 Model 3G8F5-SLK21/22

(10/95)

PLC the RS232C port attached to the CPU Unit Serial Communication Board Model CS1W-SCB21/SCB41 Serial Communication Unit Model CS1W-SCU21 Model CJ1W-SCU41 Controller Link Unit Model CS1W-CLK21/11/12/52 Model CJ1W-CLK21 Model CS1W-CLK21/12/52-V1 Model CJ1W-CLK21-V1 Ethernet Unit Model CS1W-ETN01/11 Model CJ1W-ETN11 Ethernet Unit Model CS1W-ETN21 Model CJ1W-ETN21 Model CS1D-ETN21D SYSMAC LINK Unit Model CS1W-SLK21/11

SYSMAC OPC Server V2.6 Operation Manual

- LCU/LCB Loop Control Unit Loop Control Board Network Host link (Serial) Toolbus CS/CJ

Controller Link

Ethernet (UDP)

Model CS1W-LC*** Model CS1W-LCB** Requirement Computer COM port attached to the computer.

Controller Link Support Board Model 3G8F7-CLK21/12/52 Model 3G8F5-CLK21/11

WindowsNT/2000/XP-compatible Ethernet board

Ethernet (TCP/UDP)

WindowsNT/2000/XP-compatible Ethernet board

SYSMAC LINK

SYSMAC LINK Support Board Model 3G8F7-SLK21/11 Model 3G8F5-SLK21/22

PLC CPU built-in COM port Serial Communications Board Model CS1W-SCB21/SCB41 Serial Communications Unit Model CS1W-SCU21 Model CJ1W-SCU41 Controller Link Unit Model CS1W-CLK21/11/12/52 Model CJ1W-CLK21 Model CS1W-CLK21/12/52-V1 Model CJ1W-CLK21-V1 Ethernet Unit Model CS1W-ETN01/11 Model CJ1W-ETN11 Ethernet Unit Model CS1W-ETN21 Model CJ1W-ETN21 Model CS1D-ETN21D SYSMAC LINK Unit Model CS1W-SLK21/11

- SYSMAC CV/CVM1 Series SYSMAC CV Model CV2000/1000/500 - CPU**(-V1) SYSMAC CVM1 Model CVM1 - CPU**(-V1) Network Host link (Serial) Toolbus CV

Controller Link

Ethernet SYSMAC LINK

Requirement Computer COM port attached to the computer.

Controller Link Support Board Model 3G8F7-CLK21/12/52 Model 3G8F5-CLK21/11 WindowsNT/2000/XP-compatible Ethernet board SYSMAC LINK Support Board Model 3G8F7-SLK21/11 Model 3G8F5-SLK21/22

(11/95)

PLC the RS232C port attached to the CPU Unit Host link Unit Model CV500–LK201 Controller Link Unit Model CVM1-CLK21/12/52 Ethernet Unit Model CV500-ETN01 SYSMAC LINK Unit Model CV500-SLK21/11

SYSMAC OPC Server V2.6 Operation Manual

- SYSMAC C Series SYSMAC Alpha SYSMAC CQM1H SYSMAC Board Network Host link (Serial) Toolbus C

Controller Link

Ethernet SYSMAC LINK

Model C200HX/HG/HE - CPU**(-Z) Model CQM1H - CPU** Model C200PC – ISA**(-DRM/-SRM) Requirement Computer COM port attached to the computer.

Controller Link Support Board Model 3G8F7-CLK21/12/52 Model 3G8F5-CLK21/11 WindowsNT/2000/XP-compatible Ethernet board SYSMAC LINK Support Board Model 3G8F7-SLK21/11 Model 3G8F5-SLK21/22

PLC the RS232C port attached to the CPU Unit Serial Communication Board Model C200HWCOM02/03/04/05/06(-V1) Model CQM1H-SCB41 Controller Link Unit Model C200HW-CLK21 Model CQM1H-CLK21 PC Card Unit (Ethernet set) Model C200HW-PCS01-V1 SYSMAC LINK Unit Model C200HWSLK23/24/13/14

Note: 1. LCB/LCU are one of CS/CJ-series Special IO Units. Mount LCB/LCU on CS/CJ PLC together with a communications unit. 2. Operations in a combination not described above are not assured. 3. Controller Link can not use multiple series of units simultaneously. 4. Host link can use up to two series of units simultaneously. 5. Toolbus CS/CJ and Ethernet (TCP) are available only with FinsGateway Version2003.

(12/95)

SYSMAC OPC Server V2.6 Operation Manual

2.

Setup 2.1.

Uninstalling old version of SYSMAC OPC Server and FinsGateway

SYSMAC OPC Server V2 runs on FinsGateway V2, V3, or V2003. Uninstall the old version of SYSMAC OPC Server V2 and FinsGateway when they have been installed. Note: If your OS is WindowsXP, SYSMAC OPC Server V2 runs on only FinsGateway V3.20 or later versions or V2003. Uninstall FinsGateway from your computer if it is older than V3.20.

2.2.

Installing

The installing procedure is outlined as follows:

Start installing

No

FinsGateway has been installed

Install FinsGateway V3/2003

Yes

Install SYSMAC OPC Server V2

Install FinsGateway ?

No

Yes Install FinsGateway V3.20 Update or 2003 ETN duplication patch.

Complete

Note 1. To use FinsTCP, ToolbusCS/CJ, or new functions of Controller Link Unit V1, install FinsGateway2003. The major new functions of Controller Link Unit V1 are as follows: 1) Using 62 nodes (wire type) 2) Automatic setting of data link (1 to N Assignment) 2. If FinsGateway2003 is installed, the computer is restarted and then the Ethernet duplication patch is installed. 3. For the installation of FinsGateway Version2003, see the Installation Guidelines for FinsGateway Version2003. The installation guidelines are included in this CD.

(13/95)

SYSMAC OPC Server V2.6 Operation Manual

(1) Installing the SYSMAC OPC Server V2 Step (1) Start “:\SETUP.EXE” to execute the setup wizard.

Step (2) Select whether to install FinsGateway. If FinsGateway has been already installed, select “Do not install FinsGateway” to go to Step 10 (Installing SYSMAC OPC Server V2). To change the FinsGateway version, stop installation, uninstall FinsGateway once, and then restart installation.

Note 1. If FinsGateway is already installed and you want to add or remove a specific network unit, you must stop all FinsGateway related services first. Step (3) Select a FinsGateway version (Windows2000/XP). In the case of WindowsNT, this dialog is not displayed. Go to Step (4).

(14/95)

SYSMAC OPC Server V2.6 Operation Manual

Step (4) Installing the FinsGateway starts. Select “Next >”. FinsGateway V3 is installed in this example.

Step (5) Select an install folder. “C:\Program Files\OMRON\FinsServerNT” is set by default. To change it, press “Browse” to select a desired folder.

(15/95)

SYSMAC OPC Server V2.6 Operation Manual

Step (6) Select a network type to use. Be sure to select at least one type of network.

Step (7) Select a program folder. “FinsGateway” is set by default.

(16/95)

SYSMAC OPC Server V2.6 Operation Manual

Step (8) Installing the selected networks starts.

Note 1. If you quit installing halfway, the OPC server will not work normally. Reinstall it. Step (9) When installing completes, the Complete dialog box will appear. Press “Finish”, and then installing SYSMAC OPC Server V2 starts.

Note 1. After the installation of FinsGateway Version2003, the confirmation dialog to prompt you to restart your computer may be displayed. Either you select "Yes" or "No", the installer start installing SYSMAC OPC Server (Step 10). If you restart your computer after installing SYSMAC OPC Server, both FinsGateway and SYSMAC OPC Server are validated.

(17/95)

SYSMAC OPC Server V2.6 Operation Manual

Step (10) Select “Next>” to install the SYSMAC OPC Server V2.

Step (11) Read the software licensing agreement carefully. If you agree, select “Yes”.

Step (12) Enter your name and your company name. Your license number is shown in the enclosed “Software license agreement” or the CD case.

(18/95)

SYSMAC OPC Server V2.6 Operation Manual

Step (13) Select an install folder. “C:\Program Files\OMRON\SYSMAC OPC Server” is set by default. To change it, press “Browse” to select a desired folder.

Step (14) Select a program folder. “SYSMAC OPC Server V2” is set by default.

Step (15) When installing completes, the Complete dialog box will appear. Press “Finish”.

(19/95)

SYSMAC OPC Server V2.6 Operation Manual

Step (16) Restart your computer.

Note: 1. If FinsGateway2003 is installed, the computer is restarted and then the Ethernet duplication patch is installed.

(20/95)

SYSMAC OPC Server V2.6 Operation Manual

(2) Installing FinsGateway Update 3.20 Step (1) Start “:\FgwUpdate\FgwUpdate320.exe” to execute the setup wizard.

Step (2) Select “Next>” to install the FinsGateway Update 3.20.

Step (3) Confirm the update products. Press “Next>”.

(21/95)

SYSMAC OPC Server V2.6 Operation Manual

Step (4) Confirm a destination folder for the update module. Press “Next>”.

Step (5) When installing completes, the Complete dialog box will appear. Press “Finish”.

(22/95)

SYSMAC OPC Server V2.6 Operation Manual

2.3.

Uninstalling

This section explains how to uninstall the SYSMAC OPC Server V2 as an example of the case of Windows2000. Take the same procedure if your OS is WindowsNT or WindowsXP, but the screen images are different. Step (1) Start “Add/Remove Programs” in the Control Panel. Select “SYSMAC OPC Server V2”, and then press “Change/Remove”.

Step (2) Press “Yes” to uninstall.

Step (3) Confirms whether shared files may be deleted or not. Files in the install folder (“C:\Program Files\OMRON\SYSMAC OPC Server\” by default) for the SYSMAC OPC Server may be deleted.

(23/95)

SYSMAC OPC Server V2.6 Operation Manual

Step (4) Uninstalling has completed. Press “OK”.

Step (5) Next uninstall FinsGateway. Do not uninstall FinsGateway when the application in which FinsGateway is used remains. Start “Add/Remove Programs” in the Control Panel. Select the FinsGateway, and then press “Change/Remove”. In the following figure, the FinsGateway for Ethernet has been selected.

Step (6) Click “Yes” to execute uninstalling.

(24/95)

SYSMAC OPC Server V2.6 Operation Manual

Step (7) Reconfirm uninstalling. Click “Yes”.

Step (8) Confirms whether shared files may be deleted or not. Files in the install folder (“C:\Program Files\OMRON\FinsServerNT\” by default) for the FinsGateway may be deleted.

Step (9) Uninstalling has completed. Press “OK”.

(25/95)

SYSMAC OPC Server V2.6 Operation Manual

Step (10) Repeat the steps (5)-(9) if there are FinsGateway which should be deleted. When uninstalling the last FinsGateway is completed, the following message is displayed. Press “OK” to restart your computer.

Note 1. Restart the computer whenever FinsGateway is uninstalled. 2. To uninstall FinsGateway completely, uninstall FinsGateway as usual first and then execute “FinsGateway Remover 3” or “FgwRemover2003”. Execute "\FgwUtils\FgwRemover3.exe" or “\FinsGatway2003\FgwUnits\FgwRemover2003.exe” of the installation CD.

Refer to the

Readme file for details.

2.4.

File Configuration

The SYSMAC OPC Server V2 installer sets up the following program files to the specified folder when installing. File name Contents \bin\LocaleJPN.dll DLL for the Japanese-version resources \bin\LocaleUK.dll DLL for the English-version (U.K.) resources \bin\LocaleUS.dll DLL for the English-version (U.S.) resources \bin\OmronOPCDAAuto.dll DLL for OPC Automation Interface \bin\OpcEventLog.dll DLL for the event log \bin\OpcServer.exe OPC server program \bin\Opccomn_ps.dll DLL for OPC proxy \bin\OPCProxy.dll DLL for proxy \bin\psapi.dll DLL for process administration \bin\OmronOpc.reg Reg file for registration \bin\ OpcClient.exe OPC sample client \bin\SpecialIF.dll DLL for CX-Process \bin\Readme.txt Precautions, etc. \Manual\OmronOpcV26.pdf Online manual \sample\CXT File\test.cxt CXT file sample

(26/95)

SYSMAC OPC Server V2.6 Operation Manual

3.

Basic Operations

This section explains the basic operations of the SYSMAC OPC ServerV2.

3.1.

Starting

The SYSMAC OPC Server V2 starts by selecting “Programs”-”OMRON”-”SYSMAC OPC Server V2”-”SYSMAC OPC Server” of “Start” menu. Starting the SYSMAC OPC Server V2 will show the following window for a few seconds.

Following the above window, the main window of the SYSMAC OPC Server V2 will appear.

When OPC Server starts for the first time, nothing is set in the tag setting file. Next time the OPC Server is started, the tag setting file last used will be read. If the option “Restore Tag file automatically when boot” (See 3.7 Tool Menu) is active and a tag file to be opened is invalid, the tag file (backup file) saved last but one time is opened. In this case, data is saved in the file to be originally opened (invalid file). If the backup file is also invalid or the option “Restore Tag file automatically” is deactivated, SYSMAC OPC Server operates as well as the first startup. Note 1. The program can not be started more than once simultaneously. (27/95)

SYSMAC OPC Server V2.6 Operation Manual

3.2.

Window Contents

The SYSMAC OPC Server V2 has two types of display areas: The device group and the tags.

Device Group Display Area

Tag Display Area

- The device group display area is a window to show the information on a connection destination. A device (

) is to specify a PLC to communicate with. In the example window, two devices

with the names of Device1 and Device2 are registered. A group (

) is to further classify each device. In the example window, a group with the

name of Group is registered. - The tag display area is a window to show the information (the table below) on the tag set by the OPC server. The contents displayed are different between CPU Unit and LCB/LCU. Name Tag Area BIT CH Value Description

CPU Unit Meaning Name of a tag Area type of a tag (DM, CIO, etc.) Bit offset (0-15: Available for bit-type tags only) Area address of a tag (Channel;word address) Value of a tag Description of a tag

Name Tag Block Address Item No. Value Description

LCB/LCU Meaning Name of a tag Block address of a tag (0-999) Item number of a tag (0-999) Value of a tag Description of a tag

(28/95)

SYSMAC OPC Server V2.6 Operation Manual

- The tag icon displayed depends on the data types. Icon Data Type WORD(Signed/Unsigned)/WORD_BCD/ DWORD(Signed/Unsigned)/DWORD_BCD/ FLOAT/STRING/BYTE * The icon is light blue if the tag is a scaling target. BIT

3.2.1.

Configuration of Toolbar

Menus corresponding to each button of the toolbar are as follows: Button

3.2.2.

Corresponding menu

Function

new Device

Add a new device.

new Group

Add a new group.

new Tag

Add a new tag.

Cut

When selecting a tag, cut the tag and copy it to the clipboard. Unavailable when selecting a device or a group.

Copy

Copy a tag or a group to the clipboard. Unavailable when selecting a device.

Paste

Paste the content of the clipboard.

Monitor Connection check

Monitor tag value in the tag display area. Start communications with a device and check the connection (Disabled when the option “Device connection monitoring” is not selected).

Configuration of Popup Menu

Select the device icon and the group icon in the device group display area, and a tag name in the tag display area, and then click the right button. The popup menu will appear.

(29/95)

SYSMAC OPC Server V2.6 Operation Manual

Functions of each menu are as follows: Menu Function Copy Copy a group to the clipboard. Paste Paste the content of the clipboard. Delete Delete a device or a group. (Unavailable while monitoring tags ) New Group Add a new group. New Tag Add a new tag. Properties View/Edit the property of a device or a group.

Functions of each menu are as follows: Menu Function Cut Cut tags and then copy them to the clipboard. (Unavailable while monitoring tags.) Copy Copy tags to the clipboard. Paste Paste the content of the clipboard. Delete Delete tags. (Unavailable while monitoring tags.) Write Tag Write (update) tag values. Properties View/Edit the property of a tag. Note 1 .If a group includes more than 5000 tags, it may take some time to complete pasting the tags.

(30/95)

SYSMAC OPC Server V2.6 Operation Manual

3.3.

File Menu

In the file menu, a tag setting file (*.sdb) used by the SYMAC OPC Server is read/written, and various files are imported/exported. A tag setting file is an original binary file in the SYSMAC OPC Server V2.

Functions of each menu are as follows: Menu Shortcut key New Ctrl+N Open Ctrl+O

Save Save As (Recent File)

Ctrl+S

Import Device Import Tag Import CX-Process Import CX-Programmer CX-Programmer version1 (.cxt) Import CX-Programmer CX-Programmer version2 or later Export Device(D)… Export Tag(T)… Export RSView32(R)... Exit

(31/95)

Function Create a tag setting file. Open a tag setting file. Can not open a file created by the SYSMAC OPC ServerV1.x. You can't open this version's file with the old version of SYSMAC OPC Server. Overwrite the existing tag setting file. Save the tag setting file as another name. Show the names of files recently used if any. Import the device data file (CSV-format) exported by the SYSMAC OPC Server V2. Import the tag data file (CSV-format) exported by the SYSMAC OPC Server V2. Import the tag file set by the CX-Process1 version1 or version2 or later. Import the variable in the .cxt-format file created by the CX-Programmer V1.x. as the tag. Import the variable in the project being edited in the CX-Programmer version2 or later. Export the device information in the original CSV-format file. Export the tag information in the original CSV-format file. Export the device/tag information in the CSV-format file possible to import to the RSView32 tag database. Exit the SYSMAC OPC Server V2.

SYSMAC OPC Server V2.6 Operation Manual

If performing “New” or “Open” or “Exit” with the OPC client connected, the following warning message will appear.

or

3.4.

Edit Menu

In the edit menu, cut, copy, paste, delete, setting network, and showing property for a device, a group, and tags are performed.

Functions of each menu are as follows: Menu

Shortcut key

Function

Cut

Ctrl + X

When tags are selected, cut tags to copy to the clipboard. Unavailable when a device or a group is selected.

Copy

Ctrl + C

Copy tags or a group to the clipboard. Unavailable when device is selected.

Paste

Ctrl + V

Paste the content of the clipboard.

Delete

Del

Delete a device, group, or tags.

Network Setting…

Properties…

Start the Communications Unit with the FinsGateway service manager (SCM). Then set the Communications Unit with the FinsGateway Configuration or the FinsGateway Network Navigator. Refer to 4. Start/Set Network for details. Ctrl + P

Show the property of a device, a group, or a tag. (32/95)

SYSMAC OPC Server V2.6 Operation Manual

Note 1. If a group includes more than 5000 tags, it may take some time to complete pasting the tags. When performing “Cut/Copy” and “Paste”, if the same name already registered exists, the following dialog box will appear.

The functions of each button are as follows: Button Function Yes Overwrite a tag. Yes to All Overwrite a tag with the same name afterwards. No Skip overwriting. Cancel Cancel all tag copyings afterwards. Paste all as different Save all tags having the same name as different names. names A new tag is named “Copy[No]_+ tag name”.

3.5.

Add Menu

In the Add menu, a device, a group, and a tag to communicate are added.

Functions of each menu are as follows: Menu Shortcut key New Device… Ctrl + D New Group… Ctrl + G New Tag… Ctrl + T

Function Add a new device. Add a new group. Add a new tag.

To correct a device, a group, or a tag, right-click on the corresponding item, or alternatively executethe properties of the edit menu.

(33/95)

SYSMAC OPC Server V2.6 Operation Manual

The screen is different between when the device is CPU Unit and when it is LCB/LCU. CPU Unit (CS/CJ series) is selected by default.

Initial screen image (CS/CJ series is selected)

Screen image (LCB/LCU is selected)

(34/95)

SYSMAC OPC Server V2.6 Operation Manual

Setting item Name

Network No. Node No.

Unit No.

Read Unit Frame Length

Simulation IO Note

Outline and limitations for setting ‘.’ (dot), ‘,‘ (comma), or ‘ ‘ (space) can not be used. The total number of the characters for a device name, a group name, and a tag name is 256 bytes. 0 to 127 Network 0 represents a local network. 1 to 253 When referring to an event memory (A data link area on the computer through Controller Link etc.), set the same value as the local node number of the FinsGateway Controller Link Unit etc. 0 to 15 Enter a unit number set by LCU. Activated only when LCU is selected as device. 1. Specify the unit of reading if CPU Unit is selected. 8 to 998 (words) 2. Specify the frame length if LCB/LCU is selected. 16 to 1000 (bytes) Set here with the number of words/bytes for one packet when reading a tag value from a device. See the “Note” below for the max value. Check here to use in the IO simulation mode.

1. If the same device name is registered in the tag setting file, it can not be created again. 2. For Host Link, setting a large read unit tends to cause a receive timeout. To prevent a receive timeout from occurring, set a small read size or a large enough timeout time for FinsGateway. 3. The maximum value which can be set to “READ” Is different according to the network used. Serial(Host link):

128

Ethernet:

998

ControllerLink:

998

SYSMAC LINK:

256

SYSMAC Board:

256

SYSMAC CS1 Board:

500

Toolbus CS/CJ:

500

Toolbus C:

128

Toolbus CV:

269

When use the DWORD type tag, the maximum value of “Read” is ((the maximum value of each network) – 1). When use the STRING type tag, the maximum value of “Read” is ((the maximum of each network) - (maximum value of the size of the STRING type tag)). When use the array type tag, the maximum value of “Read” is ((the maximum of each network) - (maximum value of the size of the array type tag)). 4. The maximum value which can be set to “Frame Length” depends on the network used. Serial(Host link):

540

Ethernet:

1000

ControllerLink:

1000

SYSMAC LINK:

542

Toobus CS/CJ:

1000

5. After determining the device type (pressing the OK button), you cannot change the device between CPU Unit and LCB and LCU. 6. Unit No. is not unit address (value used in CX-Process). Unit address equals to unit number plus 0x10.

(35/95)

SYSMAC OPC Server V2.6 Operation Manual



Setting item Name

Outline and limitations for setting ‘.’ (dot), ‘,‘ (comma), or ‘ ‘ (space) can not be used. The total number of the characters for a device name, a group name, and a tag name is 256 bytes. There is no limit on the number of group layers as long as it does not exceed the maximum number of characters.

Note 1. If the same group name as the one to be created is registered in the device, it can not be created.

(36/95)

SYSMAC OPC Server V2.6 Operation Manual

The screen is different between when the device is CPU Unit and when it is LCB/LCU. 1. CPU Unit

(37/95)

SYSMAC OPC Server V2.6 Operation Manual

Setting item Name

Outline and limitations for setting ‘.’ (dot), ‘,‘ (comma), or ‘ ‘ (space) can not be used. The total number of the characters for a device name, a group name, and a tag name is 256 bytes. Description The maximum number of characters is 256 bytes. Location Areas that can be specified vary depending on a device type. (Refer to Separate sheet 1.) Access right Specify ReadOnly or Writable. CH Area address(Channel, word address) Values that can be set vary depending on an area/device type. (Refer to Separate sheet 1.) Bit position 0 to 15 Effective only if the data type is BOOL. CH(2 Addr) When 2-address setting is selected, specify the words for write.(for LCU) Set 2 address setting Check here if you want to set separate addresses for read and write. (for (Write) LCB/LCU) Data Type Select from BOOL / WORD / WORD_BCD / DWORD / DWORD_BCD / FLOAT / STRING, varying depending on an area/device type. (Refer to Separate sheet 1.) - STRING type is for a character array of word length. - FLOAT type is for single floating point number (32 bits) conforming to IEEE. Signed If checked here, data can be monitored with a sign. Effective only for WORD or DWORD type. WORD_BCD/DWORD_BCD type will be handled as unsigned. ASCII Effective only for STRING type. If not checked here, tags are regarded as Unicode strings when Read/Write. else, OPC Server converts Unicode strings to ASCII strings when Read/Write (Refer to Separate sheet 3 for details.) Data Size Data size can be set to a maximum of 256. - For STRING type tag, if the device is specified as simulation, the size is handled as a maximum of 5. - Can not be set for BOOL-type data. LCB/LCU Properties Displays the LCB/LCU Properties screen. Simulation signal Specify the data change method for simulation (Refer to Separate sheet 3. Simulation type for details.) Previous Displays the properties for the previous tag in the same group (device) as the present tag. If the presently displayed tag is the first tag in the group (device), this button is deactivated. Next Displays the properties for the next tag in the same group (device) as the present tag. If the presently displayed tag is the last tag in the group (device), this button is deactivated. Apply Saves the change contents. Pressing this button does not close the dialog. This button is validated when properties are changed. New Tag Creates a new tag. The same properties as the present tag are displayed. Label Enables to set labels to True/False of a BOOL tag respectively. * These values are attributes used in RS-View and not particularly used in OPC Server. Perform scaling Check this box when scaling with OPC Server. (See Separate sheet 4. Scaling specification for details of scaling.) Scaling upper limit Specifies an integer (See Separate sheet 4. Scaling specification for details). Scaling lower limit

Specifies an integer (See Separate sheet 4. Scaling specification for details).

Scaled upper source

Specifies an integer (See Separate sheet 4. Scaling specification for details).

(38/95)

SYSMAC OPC Server V2.6 Operation Manual

Scaled lower source

Specifies an integer (See Separate sheet 4. Scaling specification for details).

Decimal Point

Shows a decimal point. Fixed to 0 in manual setting.

Conversion Scale

Specifies the scaling conversion method. “Linear” is selected as default. (See Separate sheet 4. Scaling specification for details). Shows scale value (See Separate sheet 4. Scaling specification for details).

Offset

Shows offset (See Separate sheet 4. Scaling specification for details).

Data upper limit

Specifies an integer (See Separate sheet 4. Scaling specification for details).

Data lower limit

Specifies an integer (See Separate sheet 4. Scaling specification for details).

Unit

Shows a string up to 20 bytes that is entered by the user.

Display scaling Displays the Scaling formula screen. formula (See Separate sheet 4. Scaling specification for detailed formula.) Scaling data setting Specifies the way to set scaling data. Select either of the followings: 1. Calculate from the set value of LCB/LCU Properties 2. Manual (Changes in LCB/LCU Properties are not reflected) “Calculate from the set value of LCB/LCU Properties” is selected as default. (See Separate sheet 4. Scaling specification for details.) Note 1. When reading/writing, the area size and the data size are not checked. If the area address (word) + the size exceeds the PLC area, reading/writing will fail. If such a tag exists, correctly set tags may be affected. 2. If the data size is more than one, data of the size exceeding the read unit may be read. If you want always to read data of the read unit or less, set one to the data size. 3. For the SYSMAC C Series/SYSMAC CV/CVM1 Series PLCs, when writing to a BOOL-type tag, once read word data, change the bit, and then overwrite it. Be careful in actual operations as synchronism of the word data is not assured. 4. If the total number of characters for a device name, a group name, and a tag name exceeds 256 bytes, proper operations are not assured. 5. If the same tag name as the one to be created is registered in the group, it can not be created.

(39/95)

SYSMAC OPC Server V2.6 Operation Manual

Pressing “LCB/LCU Properties” button in the dialog box of tag’s property will show the following dialog box, enabling to display and to set the property for LCB/LCU.

Setting item Alarm tag Scaling upper limit Scaling lower limit Decimal Point Unit Data upper limit Data lower limit FP No. Block address. ITEM No. Scaled upper source Scaled lower source

Outline and Limitations for setting Enter a value from 0 to 8. Enter an integer. Enter an integer. Enter a value from 0 to 9. Enter up to eight characters Enter an integer. Enter an integer. Enter a value from 0 to 999. Enter a value from 0 to 999. Enter a value from 0 to 999. Enter a value from -32000 to 32000. Enter a value from -32000 to 32000. Enter 0 when no offset corresponds. Do not use data Specifies which one is used for the max value of data after upper/lower limits scaling; data upper/lower limits, or scaling upper/lower limits. If this check box is; ON: Scaling upper/lower limits OFF: Data upper/lower limits The default is OFF. * This feature is valid only when the scaling expansion setting under the Tools - Options menu is ON. For the details of the property for LUC, refer to the following manual. SYSMAC CS1 Series: CX-Process Tool Operation Manual [Cat. No. .W372-E1]

(40/95)

SYSMAC OPC Server V2.6 Operation Manual

1) Linear

2) Second root

(41/95)

SYSMAC OPC Server V2.6 Operation Manual

2. LCB/LCU

(42/95)

SYSMAC OPC Server V2.6 Operation Manual

Setting item Name

Scaling upper limit

Outline and limitations for setting ‘.’ (dot), ‘,‘ (comma), or ‘ ‘ (space) can not be used. The total number of the characters for a device name, a group name, and a tag name is 256 bytes. The maximum number of characters is 256 bytes. Specify ReadOnly or Writable. 0 to 999 Specify a block address. 0 to 999 Specify an item number. Select from BOOL/BYTE/WORD. If checked here, data can be monitored with a sign. Effective only for WORD type. Fixed to one size. Displays the LCB/LCU Properties screen. (See ). Specify the data change method for simulation (Refer to Separate sheet 3. Simulation type for details.) Displays the properties for the previous tag in the same group (device) as the present tag. If the presently displayed tag is the first tag in the group (device), this button is deactivated. Displays the properties for the next tag in the same group (device) as the present tag. If the presently displayed tag is the last tag in the group (device), this button is deactivated. Saves the change contents. Pressing this button does not close the dialog. This button is validated when properties are changed. Creates a new tag. The same properties as the present tag are displayed. Enables to set labels to True/False of a BOOL tag respectively. * These values are attributes used in RS-View and not particularly used in OPC Server. Check this box when scaling with OPC Server. (See Separate sheet 4. Scaling specification for details of scaling.) Specifies an integer (See Separate sheet 4. Scaling specification for details).

Scaling lower limit

Specifies an integer (See Separate sheet 4. Scaling specification for details).

Scaled upper source

Specifies an integer (See Separate sheet 4. Scaling specification for details).

Scaled lower source

Specifies an integer (See Separate sheet 4. Scaling specification for details).

Decimal Point

Shows a decimal point. Fixed to 0 in manual setting.

Conversion Scale

Specifies the scaling conversion method. “Linear” is selected as default. (See Separate sheet 4. Scaling specification for details). Shows scale value (See Separate sheet 4. Scaling specification for details).

Offset

Shows offset (See Separate sheet 4. Scaling specification for details).

Data upper limit

Specifies an integer (See Separate sheet 4. Scaling specification for details).

Data lower limit

Specifies an integer (See Separate sheet 4. Scaling specification for details).

Unit

Shows a string up to 20 bytes that is entered by the user.

Description Access right Block Address Item No. Data Type Signed Data Size LCB/LCU Properties Simulation signal Previous

Next

Apply New Tag Label

Perform scaling

Display scaling Displays the Scaling formula screen (See ). formula (See Separate sheet 4. Scaling specification for detailed formula.) Scaling data setting Specifies the way to set scaling data. Select either of the followings:

(43/95)

SYSMAC OPC Server V2.6 Operation Manual

1. Calculate from the set value of LCB/LCU Properties 2. Manual (Changes in LCB/LCU Properties are not reflected) “Calculate from the set value of LCB/LCU Properties” is selected as default. (See Separate sheet 4. Scaling specification for details.) Note 1. When reading/writing, the area size and the data size are not checked. If the area address (word) + the size exceeds the PLC area, reading/writing will fail. If such a tag exists, correctly set tags may be affected. 2. If the total number of characters for a device name, a group name, and a tag name exceeds 256 bytes, proper operations are not assured. 3. If the same tag name as the one to be created is registered in the group, it can not be created.

(44/95)

SYSMAC OPC Server V2.6 Operation Manual

Separate sheet 1. Data type to be set to the area and its address range For SYSMAC CS1/CJ1 Series Area Explanation CIO CIO PV HR HR PV AR AR PV WR WR PV DM DM PV EM EM PV EM0 to EMC EM0-EMC PV TIM_Value TIM PV CNT_Value CNT PV TIM_Flag TIM flag CNT_Flag CNT flag

Available type Address range of area BOOL / WORD / WORD_BCD / 0 to 6143 DWORD / DWORD_BCD / 0 to 511 FLOAT / STRING 0 to 959 0 to 511 0 to 32767 0 to 32767 0 to 32767 WORD / DWORD 0 to 4095 WORD / DWORD 0 to 4095 BOOL 0 to 4095 BOOL 0 to 4095

For SYSMAC CV/CVM1 Series Area Explanation CIO CIO PV AR AR PV G G PV DM DM PV EM EM PV EM0 to EM7 EM0-EM7 PV TIM_Value TIM PV CNT_Value CNT PV TIM_Flag TIM flag CNT_Flag CNT flag

Available type Address range of area BOOL / WORD / WORD_BCD / 0 to 2555 DWORD / DWORD_BCD / 0 to 511 FLOAT / STRING 0 to 255 0 to 24575 0 to 32765 0 to 32765 WORD / DWORD 0 to 1023 WORD / DWORD 0 to 1023 BOOL 0 to 1023 BOOL 0 to 1023

For SYSMAC C Series Area Explanation Available types Address range of area CIO CIO PV BOOL / WORD / WORD_BCD / 0 to 511 DWORD / DWORD_BCD / 0 to 99 HR HR PV FLOAT / STRING AR AR PV 0 to 27 LR LR PV 0 to 63 DM DM PV 0 to 6655 EM EM PV 0 to 6143 EM0 to EMF EM0-EMF PV 0 to 6143 TIM_Value TIM PV WORD / DWORD 0 to 511 CNT_Value CNT PV WORD / DWORD 0 to 511 TIM_Flag TIM flag BOOL 0 to 511 CNT_Flag CNT flag BOOL 0 to 511 For the details of areas and address ranges, refer to the PLCs’ manuals.

(45/95)

SYSMAC OPC Server V2.6 Operation Manual

Separate sheet 2. ASCII conversion specification

In the OPC specification, STRING tags are regarded as Unicode strings when Read/Write. When data type is STRING and the option of ASCII conversion is activated, SYSMAC OPC Server V2 automatically converts Unicode strings to ASCII strings when Read/Write. The conversion rules are described below. Definition of data size Regardless of whether ASCII conversion is taken place or not, the data size of a STRING tag indicates the number of letters. Channels of the data size are allocated to the internal memory of PLC. Read processing From the start address of a STRING tag, word data of the data size is read. The letters of the data size are converted from ASCII to Unicode. If converted successfully, the Unicode string is sent to OPC Client. If conversion fails, NULL string (‘\0’) of the data size is sent. e.g. A STRING tag of the start address DM0 and the data size 3: (1) If ASCII string ”abcdef” is set to the area from DM0 to DM2, the Unicode string sent to OPC Client becomes three letters ”abc”. Write processing A Unicode string sent from OPC Client is converted to ASCII of the data size. If converted successfully, the ASCII string is written to the STRING tag from the start address. If the write area is bigger than the write data, the remaining area is filled with NULL code (‘\0’). If conversion fails, NULL code (‘\0’) of the write data size is written. Note: 1. If the converted ASCII string is less than the words of the data size, NULL code (‘\0’) is added to the remaining words. 2.The write size never exceeds the data size of the STRING tag. e.g. A STRING tag of the start address DM0 and the data size 3: (1) If the string ”abcd” is written, the ASCII string “abc” (three bytes) and three bytes of NULL code are written to the area from DM0 to DM2 (6 bytes in total).

(46/95)

SYSMAC OPC Server V2.6 Operation Manual

Separate sheet 3. Simulation type

Data type BOOL WORD WORD_BCD DWORD DWORD_BCD BYTE FLOAT STRING2

2

Sine curve Increment Random Constant ON / OFF in a ON / OFF in a ON / OFF at No change 6-sec cycle 6-sec cycle random 0 to 100 in a Increment at Repeat 0 to 100 2-min. cycle every scan at random

-1 to 1 in a 2-min. cycle Combined characters of any one character from ‘a’ – ‘z’ and random numeric value

Up to five characters regardless of data size specification. (47/95)

SYSMAC OPC Server V2.6 Operation Manual

Separate sheet 4. Scaling specification There are two scaling methods; one is Linear and the other is Second root. Scaling setting is available for all data types excluding BOOL and STRING. For array data, scaling will be performed to each element. Scaling formula The formula to obtain scaling value is as follows: 1) Linear Scaling value = Scale x Raw data (untouched value in the memory) + Offset Scale = (Scaling upper limit – Scaling lower limit) / (Scaling upper source – Scaling lower source) / 10**(Decimal Point) Offset = {Scaling lower limit – (Scaling upper limit – Scaling lower limit) / (Scaling upper source – Scaling lower source) * Scaling lower source} / 10**(Decimal Point) 2) Second root Scaling value = Scale x sqrt (Raw data) + Offset Scale = (Scaling upper limit – Scaling lower limit) / (sqrt (Scaling upper source) – sqrt (Scaling lower source)) / (10**z) Offset = [Scaling lower limit – {(Scaling upper limit – Scaling lower limit) / (sqrt (Scaling upper source) – sqrt (Scaling lower source))} * sqrt (Scaling lower source)] / (10**z)

Scaling data setting There are following two ways to set scaling data: 1) Calculate from the set value of LCB/LCU Properties Setting the value of LCB/LCU Properties enables scaling setting. If you want to use the scaling setting of a tag imported from CX-Process as it is, select this option. 2) Manual Each value is set regardless of the value of LCB/LCU Properties. Note: In either cases, if the scaling parameter is obtained by the IOPCItemProperties() method, OPC Client returns not the value shown in LCB/LCU Properties but the value shown in Tag Properties. Setting the max/min values of data after scaling The max/min values of data after scaling (=high high limit/low low limit) are determined as follows: 1) Manual (48/95)

SYSMAC OPC Server V2.6 Operation Manual

High high limit/Low low limit = Data upper/lower limits determined in the Tag Properties dialog 2) Auto 2-1) Expansion setting of scaling3 is OFF High high limit/Low low limit = Values obtained by reflecting decimal point into the data upper/lower limits which are determined in the LCB/LCU Properties dialog 2-2) Expansion setting of scaling is ON 2-2-1) “Do not use data upper/lower limits” is OFF High high limit/Low low limit = Values obtained by reflecting decimal point into the data upper/lower limits determined in the LCB/LCU Properties dialog 2-2-2) “Do not use data upper/lower limits” is ON High high limit/Low low limit = Values obtained by reflecting decimal point into the scaling upper/lower limits determined in the LCB/LCU Properties dialog Note on using RS-View If tag information is exported to a csv file for RS-View, the maximum/minimum values are determined as follows: 1) For a scaling-target tag, follow the way mentioned in the above “Setting the max/min values of data after scaling”. 2) For a non scaling-target tag, follow the way mentioned in the above “2) Auto”. In addition, the data is fixed as follows for a scaling-target tag: Scale=1, Offset=0, Data type=F.4 Note on using CX-Process Tool (Ver.3.2 or later) When the option “Force scaling data range to 0-100% “ is specified from CX-Process Tool and RS-View Tag is output, High high limit/Low low limits of an exported tag will be the upper/lower limits of a scaling. In such cases monitoring by RS-View will cause a scaling value to exceed the upper/lower values and the quality flag of the tag will be not GOOD (Refer to the “Note on tag values”.) In order to avoid this, High high/Low low limits need to be within the upper/lower limits of the data range by setting OFF to the extension setting of scaling. (Refer to the “Setting the max/min values of data after scaling”.) Note on tag values • If scaling is set, Canonical Data Type will be VT_R8; therefore, when this tag value is read out from OPC Client, the real value is returned. • “Canonical Data Type” is not “Data type” in the Tag Properties dialog. “Data type” is the type of data when OPC Server accesses a device (For a non scaling-target tag, “Data type” is the same as Canonical Data Type.) • If AddItems() is called from OPC Client with Request Data Type set to VT_EMPTY, set Canonical

3 4

Select [Tools] – [Options] from the menu to set this option. Fix the data as mentioned to perform scaling in OPC Server. (49/95)

SYSMAC OPC Server V2.6 Operation Manual

•

• • •

•

Data Type (=R8) to Request Data Type for a scaling-target tag. If Write Tag is requested to a scaling-target tag, apply the data type after changed to raw data when writing into a device. Therefore, an integer tag is rounded at a decimal point (Same applies to a FLOAT tag exceeding VT_R4). If Write Tag is requested to a scaling-target BCD tag and raw data is not BCD, writing is impossible (Quality flag=BAD). When importing a tag from CX-Process and if it is a scaling-target tag, set Canonical Data Type to VT_R8. When a scaling value exceeds the maximum or minimum value, the quality flag of the tag is as follows:5 Uncertaion(0x40) + Last Known(0x14) + Limit High(0x02) Uncertaion(0x40) + Last Known(0x14) + Limit Low(0x01) When scaling setting is activated, the OPC-DA2.0-compliant dead band becomes available from OPC Client. Using the dead band enables to specify the variation width of the value that issues data change notification.6 Caution: 1. Check whether scaling is performed and whether scaling setting is correct in each tag before scaling.

5 6

See “OPC Data Access Custom Interface Specification 2.05 Dec 17, 2001” for details. See “OPC Data Access Custom Interface Specification 2.05 Dec 17, 2001” for details. (50/95)

SYSMAC OPC Server V2.6 Operation Manual

3.6.

View Menu

In the View menu, Monitor or View status is selected.

Menu Monitor Monitor Option Connection Check

Shortcut key

Status Bar

Function Monitor tag values in the tag display area. Set monitoring refresh cycle. Start communications with a device and check the connection (Disabled when the option "Device connection monitoring" is not selected). Switch the status bar display.



Setting item Monitor Rate

Outline and restrictions for setting Set monitoring refresh cycle. Initial value is 1000. A cycle between 300 and 10000 can be set.

In a case where each communications unit and the CPU Unit of FinsGateway are in a halt status, the device will be shown as Bad.

3.7.

Tool Menu

The “Option” of the Tool menu is prepared for maintenance. Do not change the setting usually.

(51/95)

SYSMAC OPC Server V2.6 Operation Manual



(52/95)

SYSMAC OPC Server V2.6 Operation Manual

Setting item DA2.0 Custom I/F Log

Outline and Limitations for setting When OPC DA Custom I/F is called, it enables to log the date and time of calling, method name, parameters, and execution result. The log file is named DA20IF.log and saved under the installation folder \bin. One file can contain logs up to the number specified in “Max Record Count”. If the number of logs exceeds the specified max count, the contents of the log file are cleared (saved as a backup log file with a different name) and new logs are saved from the head of the file. The backup log files are saved up to the number specified in “Max Backup Count”. The value from 1 to 9999 can be set to “MAX Record Count”. The value from 0 to 99 can be set to “MAX Backup Count”. The default values of “MAX Record Count” and ”MAX Backup Count” are 100 and 4 respectively.

FINS Communication Communication Watch Time FINS communication (See 3.7.1.)

Shows the timeout value (msec) of FinsGateway communications. The value from 10 to 9900 can be set. The default value is 3000. Communication Watch Time: The timeout value (msec) of FinsGateway communications. The default value is 3000. Retries in timeout: The number of times for retry at the timeout of FINS communications. The set value can be 0 to 10. The default value is 3. Number of Fins ports: The number of the available FINS ports for OPC Server. The set value can be 1 to 8. The default value is 8. The set value of “Number of Fins ports” becomes active after all devices are once deleted by taking procedures such as: 1) Restart OPC Server. 2) Select [File]-[New] from the menu. In addition, the value cannot be set during communications (including monitoring).

The waiting time until timeout occurs: Communication watch time x (Retries in timeout + 1) Device connection Sets an interval (minute) for monitoring device connection status monitoring (See 0.) (minimum value). Automatic setting: The value obtained by the equation, the number of devices x 10 min., is set. Manual setting: A given monitoring interval can be set. At first communications: Checks the connection status just for the first communications with the device. The default is “Not monitor”. The set monitoring interval can be a number from 1 through 71582. Start and Exit (1)Defines whether automatically end OPC Server when disconnecting all clients. (2)Defines whether automatically restore the tag file or not when it is invalid at startup of OPC Server. Scaling Specifies expansion setting of scaling. (See Separate sheet 4. Setting this option to ON enables to set the option “Do not use data Scaling specification) upper/lower limits”.

(53/95)

SYSMAC OPC Server V2.6 Operation Manual

Note 1. At the shutdown of OS, the system is terminated forcibly regardless of the setting of “Start and Exit”. 2. Call back such as data change notification or asynchronous processing request is out of the scope of DA2.0 Custom I/F Log. 3. When DA2.0 Custom I/F Log is enabled, the performance of OPC Server is considerably degraded. Use this function only when necessary.

(54/95)

SYSMAC OPC Server V2.6 Operation Manual

3.7.1.

FINS Communications

OPC Server enables parallel communication processing for the number of FINS ports. Up to 16 FINS ports are available in total of the FinsGateway units and the FinsGateway applications installed in one computer. Set the number of FINS ports according to your environment. When a large volume of data is handled on FINS communications, timeout may occur regardless of communication watch time. In this case, the number of times for retry can be specified and the FINS communication message can be resent. Checks when timeout occurs 1. Check that the PLC and OPC Server are physically connected. 2. Check the communication status by monitoring or FINS Communications Test (utility of FinsGateway). 3. Modify the set values of “Retries in timeout” and “Communication Watch Time” . (1) If too many tag points are handled (about more than 5000 points), change the set value of “Retries in timeout”. (2) If data change is frequently sent, change the set value of “Communication Watch Time”. 3.7.2.

Device Connection Monitoring

When the option “Device connection monitoring” is activated the connection status of devices (logical devices set on OPC Server) is detected, and after that, communication processing for disconnected devices is disabled. It improves the response performance between OPC Server and connected devices. OPC Server communicates with the devices every monitoring interval to check the connection status (See 3.6). If receives Read/Write processing for the tags of disconnected devices, OPC Server handles it as a communications error, without performing FINS communications. If, for instance, receives the SyncIO::Read() request from OPC Client, OPC Server returns a quality flag as BAD to the target items. Caution 1. Device connection monitoring is not executed to devices unused (the devices to which OPC Client has not executed Addltems()) and also not monitored. 2. Even if OPC Client requests Read/Write for a specific device, OPC Server does not communicate with the device if it is a disconnected device. 3. To update connection status immediately, select [View] - [Connection check] from the menu.

(55/95)

SYSMAC OPC Server V2.6 Operation Manual

3.8.

Help Menu

Version information on the SYSMAC OPC Server V2 can be displayed by “About Sysmac OPC Server” on the help menu.



(56/95)

SYSMAC OPC Server V2.6 Operation Manual

3.9.

Write Tag

Selecting the “Write Tag” menu option from the context menu of a tag in Tag Display Area or double-clicking the “Value” column in that area will display the “Write Tag” dialog.

If the selected tag is a BOOL-type tag, the “On/Off” radio buttons can be selected, the edit box of the Data field is deactivated, and the present value of the tag is displayed as default. Enter a value in the Data field and click the OK button, and then the entered value is written to the tag. Note 1. The writable tags are listed below.

It is impossible to write data to the tags that do not satisfy

the following requirements. • Must be readable and writable. • Must be one of the following data types: WORD/WORD_BCD/DWORD/DWORD_BCD/FLOAT/BYTE/BOOL. • Must be connected to PLC or in the Simulation mode. 2. See 3.5 Separate sheet 4. Scaling specification for a scaling-target tag.

4.

Starting and Setting of Network Selecting “Edit” - “Network Setting” will start the FinsGateway Service Control Manager(SCM). Start the Communication unit (service) of a network to be used with the service manager.

Click

button at the right upper part of the FinsGateway Service Control Manager to start the

FinsGateway Configuration( or FinsGateway Network Navigator).

(57/95)

SYSMAC OPC Server V2.6 Operation Manual

Set for a network to be used by the FinsGateway Configuration .

Note 1. If a Read/Write request is received from a client while changing the communications unit of

FinsGateway setting, it will not be correctly processed. 2. Refer to the Help file of the FinsGateway setting program (the FinsGateway Configuration) for details of FinsGateway.

(58/95)

SYSMAC OPC Server V2.6 Operation Manual

4.1.

Setting of Network This section explains the setting of the network and the FinsGateway as an example of the Host link. Refer to the Help file of the FinsGateway setting program(the FinsGateway Configuration) for details of the setting and the setting of other networks. Example:Setting of the Host link. -

First, start the communication unit (service) necessary for the communication. Select “Services” with a “Basic” tab in a left window of "FinsGateway Settings" selected. Select “SerialUNIT” in a right window, and push “Start” button. Select “CPU_UNIT”, and push “Start” button if the “Status” is “Stopped”. By setting the “Startup” as “Auto”; the selected communication unit of FinsGateway is automatically started from a next start of computer.

-

Next, select the “Network” with the “Basic” tab in a left window . Select "Local Network x(COMx serial unit)" in a right window, and push "Properties" button.

(59/95)

SYSMAC OPC Server V2.6 Operation Manual

-

Set the communication by "COMx Serial Unit Properties". Refer to the Help file of "FinsGateway settings” program for details.

(1)Network tab Set the Fins source address. Network number: Set the network number of the local node. Local node number: Set the node number of the local node. Communication unit number: Set the unit number of the local node. (2)Communication Unit tab Com port: Select the com port set in Line tab Baud rate: Specify the baud rate. (9600 bps in default) Stop bits: Specify the stop bits length. (2 in default) No. of retries: Specify the retry count. (0 in default) Data length: Specify the data bits length. (7 bits in default) Parity: Specify the parity.(Even parity in default) Timeout: Set the timeout time. (5,000 msec in default) (3)Node tab Specify the Fins destination address (Node No., protocol, model name, unit No.) and the data size for each node. (4)Lines tab Select the COM port to be used. Note 1. For serial communications, setting for the network on the PLC is not required.

(60/95)

SYSMAC OPC Server V2.6 Operation Manual

Example:Setting of Network for CX-Simulator -

When the destination is the CX-Simulator, the “Network setting” is unnecessary. According to the guide in the dialog of the following the CX-Simulator, just specifying the network number and the node number in the property of the device allows to connect.

Note 1. If the CX-Simulator is connected to a network, do not execute starting/stopping and setting of the communications unit by the FinsGateway Service Manager or the FinsGateway Settings program.

(61/95)

SYSMAC OPC Server V2.6 Operation Manual

5.

Tag Convert Function This section explains the tag convert function of the SYSMAC OPC Server V2.

5.1.

Tag Import Function

5.1.1.

Import from CSV file(Device,Tag)

The SYSMAC OPC Server V2 can import the device and tag information file that exported to original CSV format by the export function. [Device] [Convert procedure]

The convert procedure is as follows:

(1) Select “File”-”Import”-”Device” menu to show the following dialog box.

(2) Push “…” button, specify the folder and the file, and push “OK”.

(3) .If the following dialogs are displayed, importing is a success.

(62/95)

SYSMAC OPC Server V2.6 Operation Manual

Note 1. An overlap of device names causes to show a message to encourage overwriting. Pressing OK will overwrite the existing device information. 2. If a device to be imported has the same name as a device existing in OPC Server, the data of the imported device is overwritten to the existing device. If, however, the device attribute is different from the existing device, another device is created with a name of “attribute + serial number + device name”. For example, if a CPU device of the same name as a LCU access device named “PLC1” existing in OPC Server is imported, the device named “CPU1_PLC1” is generated.

[Tag] [Convert procedure]

The convert procedure is as follows:

(1) Select “File”-”Import”-”Tag” menu to show the following dialog box.

(2) Push “…” button, specify the folder and the file, and push “OK”.

(3) .If the following dialogs are displayed, importing is a success.

Note 1. An overlap of tag names causes to show a message to encourage overwriting. Pressing OK will overwrite the existing tag information

(63/95)

SYSMAC OPC Server V2.6 Operation Manual

2. If a device to be imported has the same name as a device existing in OPC Server, the data of the imported device is overwritten to the existing device. If, however, the device attribute is different from the existing device, another device is created with a name of “attribute + serial number + device name”. For example, if a CPU device of the same name as a LCU access device named “PLC1” existing in OPC Server is imported, the device named “CPU1_PLC1” is generated.

(64/95)

SYSMAC OPC Server V2.6 Operation Manual

5.1.2.

Import of CX-Process version1 Monitor Tag File

The SYSMAC OPC Server V2 can import monitor tag file information file created by the CX-Process V1.x to the tag setting file. [Convert procedure]

The convert procedure is as follows:

(1) Select “File”-”Import”-”CX-Process…” menu to show the dialog box for importing CX-Process tag.

(2) Select “CX-Process version1” at the “File” , then specify a target folder of the import tag. Specify a folder of the CX-Process Monitor DB. (3) Specify a Device Name. (4) Specify a Start CH for allocation. - Specify a start address of the DM for the node terminal when the CX-Process Tool has generated a monitor tag. - This value can be set in the system common block of the CX-Process Tool, which initial setting value is 16020. (5) Select whether or not to generate the representative tag as a group. - Generate the representative tag as a group: The representative tag is generated as a group and the ITEM tag is generated in the group. - Not generate the representative tag as a group: The tag name will be a combination of the representative tag and the ITEM connected with a '_'. (6) Selecting “OK” in the import dialog box will add the tag to the tag configuration file (*.sdb) currently opened. Note

1. '/’s and ' 's (spaces) are deleted from the tag name. 2. An overlap of tag names causes to show a message to encourage overwriting. Pressing OK will overwrite the existing tag information. 3. If a device to be imported has the same name as a device existing in OPC Server, the data (65/95)

SYSMAC OPC Server V2.6 Operation Manual

of the imported device is overwritten to the existing device. If, however, the device attribute is different from the existing device, another device is created with a name of “attribute + serial number + device name”. For example, if a CPU device of the same name as a LCU access device named “PLC1” existing in OPC Server is imported, the device named “CPU1_PLC1” is generated. 5.1.3.

Import of CX-Process version2 or later CSV Tag File

The SYSMAC OPC Server V2 can import CSV tag file information to the tag setting information created by the CX-Process version2 or later. [Convert procedure]

The convert procedure is as follows:

(1) Selecting “File”-”Import”-”CX-Process…” menu will show the dialog box of the CX-Process tag import.

(2) Select “CX-Process version2 or later” (CSV format) in the file type selection to specify the import target file. Specify CSV tag file. (3) Select whether or not to generate the representative tag as a group. - Generate the representative tag as a group: The representative tag is generated as a group and the ITEM tag is created in the group. - Not generate the representative tag as a group: A tag name will be a combination of the representative tag and the ITEM connected with a '_'. (4) Selecting OK in the import dialog box will add the tag to a tag configuration file (*.sdb) currently opened. Note

1. '/'s and ' 's (spaces) are deleted from the tag name. 2. An overlap of tag names will cause to show a message to encourage overwriting. Pressing OK will overwrite existing tag information. 3. The following lines will be ignored in the CX-Process version2or later file.

(66/95)

SYSMAC OPC Server V2.6 Operation Manual

٠A line with incorrect fields ٠A blank line ٠A line including incorrect values (ex.: Incorrect attribute of tag data) ٠A tag name same as an existing scaling-target tag (scaling set by manual) in OPC Server 4. If a device to be imported has the same name as a device existing in OPC Server, the data of the imported device is overwritten to the existing device. If, however, the device attribute is different from the existing device, another device is created with a name of “attribute + serial number + device name”. For example, if a CPU device of the same name as a LCU access device named “PLC1” existing in OPC Server is imported, the device named “CPU1_PLC1” is generated.

(67/95)

SYSMAC OPC Server V2.6 Operation Manual

5.1.4.

Import of CX-Programmer V1.x Project

The SYSMAC OPC Server V2 can import Symbols (tag) information from a ladder program (.cxt file) created by the CX-Programmer1.x to a tag setting file. The convert specifications of the variable (tag) are as follows: CX-Programmer SYSMAC OPC Server V2 PLC Device Name Convert to a device. (Inherit FINS address and model information) Global Symbols Convert to a tag included in the device. Program Name Convert to a group included in the device. Local Symbols Convert to a tag included in the group. Ex.: The symbol “MyTag” is imported as tag “MyTag” of the group “Main” in the device “MyPLC”.

As an option, a layer structure with separators is supported. This function enables variables registered in the ladder program (.cxt file) created by the CX-Programmer V1.x to be divided into a group and a tag with separators specified by the user. (Layer structure conversion) (Ex.) If “Symbol: S1_D0” is registered in the ladder project and the variable is imported with “Separator: ‘_’” specified, the group name S1 will be created and the tag name D0 will be created in it. The conversion specifications of data type are as follows: Data type of CX-Programmer (Blank) INT DINT LINT UINT UDINT ULINT UINT_BCD UDINT_BCD ULINT_BCD REAL CHANNEL NUMBER

Data type of OPC server BOOL WORD DWORD DWORD WORD DWORD DWORD WORD DWORD DWORD FLOAT WORD (Excepted)

(68/95)

Data size --1 1 2 1 1 2 1 1 2 1 1 ---

Sign --Signed Signed Signed Unsigned Unsigned Unsigned Unsigned Unsigned Unsigned --Unsigned ---

SYSMAC OPC Server V2.6 Operation Manual

[Convert procedure]

The convert procedure is as follows:

(1) Selecting “File”-”Import”-”CX-Programmer”-”CX-Programmer 1.x(.CXT)…” menu will show the dialog box of “Import Tag.”

(2) Select a conversion source file (*.cxt). (3) Specify whether to use the separator. (4) Selecting “OK” will add the tag to a tag setting file (*.sdb) currently opened. (5) If errors occur, the following dialog box will appear, and the log file (“\bin \cxp_import.log" ) will be created.

Note 1. The project file of the CX-Programmer must be saved in the .cxt format in advance. 2. A group without a tag is not converted. 3. The data type PV_TIM and PV_CNT is the WORD type or the DWORD type on the SYSMAC OPC Server V2. Change to the WORD type or the DWORD type when PV_TIM and PV_CNT are converted into the WORD_BCD type or the DWORD_BCD type by the tag importing function. 4. The system-defined tags of CX-Programmer (such as P_0_02S) are not imported. 5. If a group includes more than 5000 tags, it may take some time to complete importing the tags. (69/95)

SYSMAC OPC Server V2.6 Operation Manual

6. If a device to be imported has the same name as a device existing in OPC Server, the data of the imported device is overwritten to the existing device. If, however, the device attribute is different from the existing device, another device is created with a name of “attribute + serial number + device name”. For example, if a CPU device of the same name as a LCU access device named “PLC1” existing in OPC Server is imported, the device named “CPU1_PLC1” is generated. 5.1.5.

Import of CX-Programmer version2 or later Project

The SYSMAC OPC Server V2 can import Symbols(tag) information included in the ladder project being edited in the CX-Programmer version2 or later to a tag setting file. The conversion specifications are as same as those of the CX-Programmer V1.x. The conversion specifications of data type are as follows: Data type of CX-Programmer BOOL INT DINT LINT UINT UDINT ULINT UINT_BCD UDINT_BCD ULINT_BCD REAL CHANNEL NUMBER [Convert procedure]

Data type of OPC server BOOL WORD DWORD DWORD WORD DWORD DWORD WORD DWORD DWORD FLOAT WORD (Excepted)

Data size --1 1 2 1 1 2 1 1 2 1 1 ---

Sign --Signed Signed Signed Unsigned Unsigned Unsigned Unsigned Unsigned Unsigned --Unsigned ---

The convert procedure is as follows:

(1) Start the CX-Programmer version2 or later, and then open the ladder project. (2) Selecting “File”-”Import”-”CX-Programmer version2 or later” menu will add a tag to the tag setting file (*.sdb) currently open. (3) If errors occur, the following dialog box will appear, and the log file (“\bin\cxp_import.log " ) will be created.

Note 1 The project file of the CX-Programmer must be saved in the .cxt format in advance. 2 A group without a tag is not converted. 3 The data type PV_TIM and PV_CNT is the WORD type or the DWORD type on the SYSMAC OPC Server V2. Change to the WORD type or the DWORD type when PV_TIM and PV_CNT are converted into the WORD_BCD type or the DWORD_BCD type by the tag importing function.

(70/95)

SYSMAC OPC Server V2.6 Operation Manual

4 5 6

The system-defined tags of CX-Programmer (such as P_0_02S) are not imported. If a group includes more than 5000 tags, it may take some time to complete importing the tags. If a device to be imported has the same name as a device existing in OPC Server, the data of the imported device is overwritten to the existing device. If, however, the device attribute is different from the existing device, another device is created with a name of “attribute + serial number + device name”. For example, if a CPU device of the same name as a LCU access device named “PLC1” existing in OPC Server is imported, the device named “CPU1_PLC1” is generated.

(71/95)

SYSMAC OPC Server V2.6 Operation Manual

5.2.

Tag Export Function

5.2.1.

Export to CSV File(Device,Tag)

The SYSMAC OPC Server V2 can export device and tag information in an original CSV-format file. [Convert procedure]

The convert procedure is shown below.

Specify an output target file (*.csv) in the following window. (1) “File”-”Export”-”Device...” will show the dialog box of “Open”.

(2) Specify an output target file (*.csv). (3) Pressing “OK” will output device information in CSV format.

(72/95)

SYSMAC OPC Server V2.6 Operation Manual

(1) “File”-”Export”-”Tag” menu will show the dialog box of “Export Tag”. (2) Specify an output target file (*.csv). (3) Specify the number of group hierarchy. (4) Pressing “OK” will output the tag information file in CSV format.

The data array specification in a CSV file is output in the second line of a CSV file.

(73/95)

SYSMAC OPC Server V2.6 Operation Manual

5.2.2.

Export to CSV file for RSView32

The SYSMAC OPC Server V2 can export tag information in CSV format that allows to import to the tag database of RSView32. The exported tag data can be imported to the tag database of the RSView32 project using "RSView32 Data Import & Export Wizard" attached to the RSView32. The conversion specifications of the tag are as follows: SYSMAC OPC Server V2 RSView32 Device Folder Group Folder Tag Tag The conversion specifications of data type are as follows: Data type of OPC server (VARIANT type) BOOL STRING Signed WORD Unsigned WORD WORD_BCD Signed DWORD Unsigned DWORD DWORD_BCD FLOAT BYTE

(VT_BOOL) (VT_BSTR) (VT_I2) (VT_UI2) (VT_UI2) (VT_I4) (VT_UI4) (VT_UI4) (VT_R4) (VT_UI1)

Data type of RSView32 Type Native Type Digital Boolean String String 7 Analog Integer Analog Unsigned int Analog Unsigned int Analog Long Analog Float Analog Float Analog Float Analog Byte

It is also possible to output the integer data (Signed WORD, Unsigned WORD, WORD_BCD, Signed DWORD/BYTE) of the SYSMAC OPC Server V2 as a real type (default of the RSView32). For the specifications of the CSV format that allows to import to the tag database of RSView32, refer to the online help of the RSView32.

7

Analog type means Signed WORD, WORD, Signed DWORD, DWORD, or float. (74/95)

SYSMAC OPC Server V2.6 Operation Manual

[Conversion procedure] The conversion procedure is shown below. (1) “File”-”Export”-”RSView” menu will show the convert window.

(2) Specify the name of an export destination file. (3) Specify the group hierarchy. When “Specify the group hierarchy” is not specified, all the tags are exported. The tag in the group exceeding the group hierarchy is not exported. (4) Specify a policy of data conversion when the data to be exported is an array. (5) Specify a node name . Specify a node name set to the SYSMAC OPC Sever in the project of the RSView32 (6) Check “Convert Integer to Real“ when you convert the integer data of the OPC Server into the default type of RSView32 (the real type). (7) Select a type of a file to be exported. Tag: Export Tag only. Tag + Min/Max + Unit: Export Tag and Attached info.(properties for LCU) [Attached info.] Scaling upper/lower limit Decimal position Unit Data upper/lower limit (Converted with scaling info.) Scaled upper/lower source (Converted with scaling info.) (8) Pressing OK button will execute exporting. Note 1. If a file name or a node name is not specified, pressing OK will execute nothing. 2. Even if an export target tag does not exist, no special message will appear. (75/95)

SYSMAC OPC Server V2.6 Operation Manual

6.

Using from OPC Client

This section explains how to use the OPC-compatible client application (described as OPC client, hereafter) using the OPC sample client attached to the product and the RSView32 V6.3J as an example. The specifications the SYSYMAC OPC Server discloses to an OPC-compatible client are as follows: Item Explanation Specifications ProgID Program ID OMRON.OPC or OMRON.OPC.2 The server name to identify the OPC Server ItemID Item ID Device name + [Group name] + Tag name The name to identify a tag set [ ] can be omitted. to the OPC Server Note 1. Use a ‘.’(dot) to separate device name, group name, and tag name 2. The length of ItemID is limited to 256 bytes (excluding a ‘.’ as a separator.) 3. There is no limit in the number of group layers (can be omitted.) 4. A ‘,’ (comma), a ‘.’ (dot), and a ‘ ‘ (space) can not be used as a device name, a group name, and a tag name.

(76/95)

SYSMAC OPC Server V2.6 Operation Manual

6.1.

Using from OPC Sample Client (Local Connection)

This section describes the case where the OPC sample client operates on the computer where the SYSMAC OPC Server V2 does. In this case, the SYSMAC OPC Server V2 operates as a local server. (1) Start the OPC sample client (“\bin\OpcClient.exe”) attached to the product.

(2) Pressing OPC Server Browser (“…”button) will show the dialog box of the Server Browser. Select “OMRON.OPC.2” as the ProgID, and then press “OK”.

(3) Pressing the “Connect” button will connect to the SYSMAC OPC Server V2. You can see that the connection of the OPC server and the client has been established in the Status field.

(77/95)

SYSMAC OPC Server V2.6 Operation Manual

6.2.

Using from OPC Sample Client (Remote Connection)

This section describes how to run the OPC sample client on a computer in the remote network different from the one where the SYSMAC OPC Server V2 runs. In this case, the SYSMAC OPC Server V2 runs as a remote server. Settings for the server computer and the client computer are as follows: Server :Computer name OMRON01 Client :Computer name OMRON02 Assuming that both are Window NT4.0/Windows2000 computers belonging to the same Workgroup or Domain, logged in as the same user (with privileged mode) name and password. [Setting on the server computer] In order to enable remote connection, changing the DCOM settings of the SYSMAC OPC Server V2 on the server computer is required. A setting example is shown here. (1) After installing the SYSMAC OPC Server V2, set for DCOM. Execute “Start”-”Run…” menu, and then type in “Dcomcnfg”. The following dialog box will appear.

(78/95)

SYSMAC OPC Server V2.6 Operation Manual

(2) Select ”OMRON SYSMAC OPC Sever” in the Applications tab, and then press “Properties”. The following dialog box will appear. Select “Use custom lunch permissions” in the Security tab. Add “everyone” with “Edit” - “Add” button, and then press “Apply” button.

(79/95)

SYSMAC OPC Server V2.6 Operation Manual

(3) Next, select “The interactive user” in the Identity tab, and then press “Apply” button. If “The launching user” is selected, the OPC Server window is not displayed when the connection is established from OPC Client; however it does not mean any problem and the connection is established correctly (operates according to the specification for OPC DA2.0).

The setting of DCOM is completed.

(80/95)

SYSMAC OPC Server V2.6 Operation Manual

[Setting on the client computer] (1) Copy the following files attached to the product to an arbitrary folder on the client computer. 1. OPC sample client “\bin\OpcClient.exe” 2. Reg file for OPC Server registration “\bin\OmronOpc.reg” (2) “Start”-”Run” to select and to execute the Reg file (“OmronOpc.reg”) for OPC Server registration. Only if DLL for OPC proxy is not set on the client computer, execute the procedures (3) to (5) below. (3) Copy the following file attached to the product to the system folder (a folder including “Regsrv32.exe”) on the client computer. - DLL for OPC proxy (“< Installer Dir >\bin\opccomn_ps.dll” and “< Installer Dir >\bin \OpcProxy.dll”) (4) “Start”-”Run” to select “Regsrv32.exe” in the system folder, and then set “opccomn_ps.dll” as an argument to execute. (5) Similarly, set “OpcProxy.dll” as an argument to execute.

(6) Start the OPC sample client. Execute OPC Server search (“…”button). When the dialog box of Server Browser appears, select “OMRON.OPC.2”. Next, check “Remote Server”, input the computer name “OMRON01,” and then press “OK”.

Pressing “Connec” button will connect to the SYSMAC OPC Server V2, allowing to confirm the connection of the OPC server and the client.

(81/95)

SYSMAC OPC Server V2.6 Operation Manual

6.3.

Using from RSView32 V6.3

This section describes how to use a tag registered in the SYSMAC OPC Server V2 by the RSView32 V6.3 development version . The content is configured as follows: 1) Registration of the SYSMAC OPC ServerV2 to RSView32 2) Registration of tag to RSView32 2-1) Registration in the dialog box of the tag database 2-2) Batch registration of SYSMAC OPC Server V2 tag by the import function. Here, it is assumed that RSView32 V6.3 development version and the SYSMAC OPC Server V2 are installed on the same computer in advance, and two tags are set as follows: Tag1: ItemID is “Device.Group.Tag1”. Tag2: ItemID is “Device.Group.Tag2”.

Also, it is assumed that a new project (”MyTest1”) has been created by the RSView32 V6.3 development version.

(82/95)

SYSMAC OPC Server V2.6 Operation Manual

6.3.1.

Registration of SYSMAC OPC Server V2 to RSView32

1) Click the node icon in the tree view shown on the “Edit Mode” tab in the RSView32 project window to show the node dialog box.

2) Set the node for the SYSMAC OPC Server V2 as follows: - Select “OPC Server” as “Data Source”. - Input “OmronOpc” as “Name” here, which can be set arbitrarily. - Input “OMRON.OPC” as “Server Name”. Note 1. Pressing “…”button on the right side of the input area will show the dialog box of OPC Server Browser. In here shown is a list of OPC servers registered to the computer, from where a server name (ProgID) can be obtained.

- Select “Local” as “Server type”. - Setting of “Access path” is not required as the communications path is uniquely determined.

(83/95)

SYSMAC OPC Server V2.6 Operation Manual

3) Pressing “Accept” button will register a node for the SYSMAC OPC Server V2 to RSView32. The node name is “OmronOpc”.

6.3.2.

Registration of a Tag to RSView32

[Registering in the Dialog Box of Tag Database] 1) Click the tag database icon in the tree view shown on the “Edit Mode” tab in the RSView32 project window to show the dialog box of the tag database.

(84/95)

SYSMAC OPC Server V2.6 Operation Manual

2) Add a tag set in the SYSMAC OPC Server V2 as follows: - Input “Tag2” here as “Tag:Name”, which can be arbitrarily set. Note 1. ‘A’ – ‘Z’, ‘a’ – ‘z’, ‘-‘ (dash), ‘_’ (underscore), and ‘0’ – ‘9’ can be used as “Tag:Name”. The length is limited to 40 bytes (including separators (”\”) between a tag name and a folder name). - Select “Tag:Type”. “Analog” is selected in this example. - Select “Device as “Data Source:Type”. - Select “OmronOpc,” which was registered previously, as “Data source:Node name”. - Input ItemID of the tag registered to the SYSMAC OPC Server V2 as “Data source: Address”. Input “Device.Group.Tag2” here. Restriction 1. There is no limit on the type of characters usable as “Data source:Address” (which is user-dependent part). However, the maximum length is 60 bytes. If the ItemID of the tag registered to the SYSMAC OPC Server V2 exceeds 60 bytes, it will not be set correctly. Note 1. Pressing “…”button on the right side of the input area will show the dialog box of OPC Address Browser. In here shown is a list of tags registered to the SYSMAC OPC Server V2. Selecting a tag allows to obtain the ItemID to “Data source: Address”.

2. Selecting an unsigned WORD/DWORD-type tag will not allow to obtain the ItemID to Data: Address. 3) Press the “Accept”button to register a tag of the SYSMAC OPC Server V2 (“Device.Group.Tag2” in this example) as a tag of the RSView32 (“Tag2” in this example).

(85/95)

SYSMAC OPC Server V2.6 Operation Manual

[Batch Registration of a Tag of SYSMAC OPC Server V2] The tag information for the SYSMAC OPC Server V2: “Device name, group name , tag name” are converted to “Folder name immediately under the root, folder name, tag name,” respectively. For example, a tag of the SYSMAC OPC Server V2 (ItemID: “Device.Group.Tag”) is converted to a tag on the RSView32 tag database (“Device\Group\Tag”). Therefore, be careful of the followings. 1. In RSView32, only ‘A’-‘Z’, ‘a’-‘z’, ‘-‘,(dash), ‘_’ (underscore), and ‘0’-‘9’ can be used as a folder name and tag name. Therefore, a device name, a group name, and a tag name set in the SYSMAC OPC Server V2 must also conform to the specifications of the RSView32. 2. In RSView32, the maximum length of a tag is 40 bytes (including a separater (”\”) between a folder name and a tag name). Therefore, the maximum length of ItemID set in the SYSMAC OPC Server V2 must also conform to the RSView32 specifications. 1) Select “File”-”Export”-”RSView” for the SYSMAC OPC Server V2, and then export the tag data in the CSV-format file, which can be imported to the RSView32 tag database. In the example below, specify ”To_RSView32.csv” as an export target file and ”OmronOpc” for the SYSMAC OPC Server V2 as a node name, which was previously set.

(86/95)

SYSMAC OPC Server V2.6 Operation Manual

2) Start “Database Import&Export Wizard” attached to RSView32. Select “Import RSView CSV file” as “Import/Export Type”, and then press “Next>“ button.

3) Check “Tag” only in “Import Files”. Set “To_RSView32.csv”, a CSV-format file exported in the SYSMAC OPC Server V2, and then press “Next>“ button.

4) After the next window appears, press “…”button, set “MyTest1,” a project name of the RSView32 newly created this time, as the import/export destination project, and then press “Next>“ button.

(87/95)

SYSMAC OPC Server V2.6 Operation Manual

5) Pressing “Finish” button completes import.

6) Referring to the dialog box of the tag database, you will find that “Device” group and in it “Group” group have been newly created, and that into them the tags of Tag1 and Tag 2 have been imported.

(88/95)

SYSMAC OPC Server V2.6 Operation Manual

Appendix 1

Response Performance (Reference Value)

See the followings for the response performance of SYSMAC OPC Server. Measurement Environment 1) CPU Pentium III 650MHz 2) Memory 128M 3) OS Windows2000 SP3 4) PLC CJ1G CPU43H (Program Mode) 5) Network Type Ethernet 6) OPC Server Settings Reading unit: 998 Without log output Tags are all set on DM of one and the same device.

Response Performance (Unit: msec) method No. of tags

1 10 100 1000 5000 10000

SyncIO::Read () CACHE

SyncIO::Read() Device

SyncIO:Write()

0.20

25.86

15.27

0.34

23.82

63.18

1.10

38.11

588.20

10.75

116.99

5,850.88

63.00

907.40

31,449.40

182.40

2,918.80

80,042.40

Note 1. The above values are just reference values and not assured as response performance.

(89/95)

SYSMAC OPC Server V2.6 Operation Manual

Appendix 2

OPC Implementation Interface

This appendix describes the implementation situation of the OPC interface.

1. OPC Automation Interface The name of the automation wrapper DLL presented by the SYSMAC OPC Server V2 is as follows: OmronOPCDAAuto.dll The interface is compatible with the automation wrapper presented by the OPC Foundation. For details, refer to “OPC Data Access Automation Interface Standard Version 2.02 February 4, 1999.”8

8

Can be downloaded from the home page of OPC-F (http://www.opcfoundation.org/). (90/95)

SYSMAC OPC Server V2.6 Operation Manual

2. OPC Custom Interface The SYSMAC OPC Server V2 supports the interface essential to OPC-DA1.0a and 2.0, and the optional browse interface. For the details of the interfaces, refer to ”OPC Data Access Custom Interface Standard Version 2.0 October 14, 1998.9” The followings describe a list of the custom interfaces supported by the SYSMAC OPC Server V2. (1) Custom Interface Name

Outline

Imple

V110

V211

Optional I/F

Standard interface

ment

9

IOPCServer

Main of OPC server

IOPCCommon

Administrate information on OPC server

NA

IOPCItemProperties

Refer to the item properties

NA

IOPCGroupStateMgt

Administrate the overall group situation

IOPCSyncIO IOPCAsyncIO IOPCAsyncIO2

Synchronous read/write from OPC client to OPC server Asynchronous read/write from OPC client to Asynchronous read/write from OPC client to

NA

OPC server

IEnumOPCItemAttributes

Search for the item and attributes of the group.

IconnectionPointContainer

Administrate a callback connection.

IOPCItemMgt

Administrate items within the group.

IOPCServerPublicGroups

Administrate a public group.

IOPCBrowseServer AddressSpace

Browse item IDs available in OPC server.

IpersistFile

NA

OPC server (old)

Save information on OPC server configuration to a file and load it from a file.

IOPCPublicGroupStateMgt

Administrate the overall public group situation

IdataObject

Asynchronous read / write / cancel / Data change notice (old)

NA

NA NA

Can be downloaded from the home page of OPC-F (http://www.opcfoundation.org/).

10

V1 means OPC Data Access Custom Interface Standard Version 1.0.

11

V2 means OPC Data Access Custom Interface Standard Version 2.0.

(91/95)

NA

SYSMAC OPC Server V2.6 Operation Manual

(2) Custom Interface (Client) Name

Outline

Imple

V1

V2

ment

IOPCShutdown

OPC server end notice

NA

IOPCDataCallback

Asynchronous read / write / cancel / Data change notice

NA

IadviceSink

Data change notice

(3) Support methods The followings describe a list of methods for interfaces to be supported. IOPCServer Interface Member

Explanation

AddGroup

Add a group to OPC server.

GetErrorString

Return an error string corresponding to error codes of OPC server.

GetGroupByName

Return a pointer for a private group created by the same OPC client.

GetStatus

Obtain the current status of OPC server.

RemoveGroup

Delete a group of OPC server.

CreateGroupEnumerator

Create various group enumerators provided by OPC server.

IOPCCommonInterface Member

Explanation

SetLocaleID

Set Locale.

GetLocaleID

Obtain the current Locale.

QueryAvailableLocaleIDs

Obtain a list of Locales possible to set.

GetErrorString

Obtain an error string in the current Locale.

SetClientName

Register a client name to the server.

IOPCItemPropertiesInterface Member

Explanation

QueryAvailableProperties

Refer to the list of item characteristics that can be referred to.

GetItemProperties

Obtain the data for a specified item.

LookupItemIDs

Obtain a list of obtainable data for a specified item.

(92/95)

NA

SYSMAC OPC Server V2.6 Operation Manual

IOPCGroupStateMgtInterface Member

Explanation

GetState

Obtain the current status of a group.

SetState

Set the property of a group.

SetName

Change the name of a private group, where the name is unique. A public group can not be changed.

CloneGroup

Create a copy of a group.

IOPCSyncIOInterface Member

Explanation

Read

Read the data value, the quality flag, and the time stamp for an item in the group.

Write

Write data to an item in the group.

IOPCAsyncIOInterface Member

Explanation

Read

Read an item in the group.

Write

Write to an item in the group.

Cancel

Request the OPC server to cancel an unfinished transaction.

Refresh

Call back an active item in the group.

IOPCAsyncIO2Interface Member

Explanation

Read

Read an item in the group.

Write

Write to an item in the group.

Cancel2

Request the OPC server to cancel an unfinished transaction.

Refresh2

Call back an active item in the group.

SetEnable

Set the change notice status (Effective/Ineffective) in the group.

GetEnable

Check the change notice status (Effective/Ineffective) in the group.

IEnumOPCItemAttributesInterface Member

Explanation

Next

Obtain an item from the group.

Skip

Skip an item.

Reset

Reset to the top item of the enumerator.

Clone

Create a copy of the current status of the enumerator.

(93/95)

SYSMAC OPC Server V2.6 Operation Manual

IConnectionPointContainerInterface Member

Explanation

EnumConnectionPoints

Obtain a list of Connection Points supported among the clients.

FindConnectionPoint

Search for a specified Connection Point supported among the clients.

IOPCItemMgtInterface Member

Explanation

AddItems

Add an item to the group.

ValidateItems

Check if an item is effective or not. Return information on the item.

RemoveItems

Delete an item from the group.

SetActiveState

Set Active/Inactive to the item in the group.

SetClientHandles

Change the client handle of an item in the group.

SetDatatypes

Change the request data type of an item in the group.

CreateEnumerator

Create an enumerator of items in the group.

IOPCDataObjectInterface Member

Explanation

Dadvice

Create a connection between a group and a client.

Dunadvice

End a connection between a group and a client.

IOPCBrowseServerAddressSpace Interface (Optional) Member

Explanation

QueryOrganization

Check if the system structure is flat or hierarchical.

ChangeBrowsePosition

Move Up or Down within the layer space.

BrowseOPCItemIDs

Return the list (IenumString) of an item ID (The position for browsing is set with ChangeBrowsePosition.)

GetItemID

Obtain an item ID within the layer space.

BrowseAccessPaths

Browse the access paths (AccessPaths) of an item ID.

NA

(*) In OMRON’s PCs and network configuration, a device is accessed in only one path, and thus BrowseAccessPaths method relayed to AccessPaths is not supported. IOPCShutdown Interface (on the Client) Member ShutdownRequest

Explanation Notify of OPC server end

IOPCDataCallback Interface (on the Client) Member OnReadComplete

Explanation Notify of read complete.

OnWriteComplete

Notify of write complete.

OnCancelComplete

Notify of cancel complete.

OnDataChange

Notify of data change.

(94/95)

SYSMAC OPC Server V2.6 Operation Manual

IAdviceSink Interface (on the Client) Member OnDataChange

Explanation Notify of data change.

(95/95)