melsec ethernet daserver users guide - たけびしfaweb · pdf fileintroduction - 5 - 1....

MELSEC Ethernet DAServer

Users Guide

Revision 2D

Jan. 2017

Precautions about the Document

(1) Operate the product only after you have thoroughly read the document and understood the contents.

(2) This document describes the details of the product and is not guaranteed to meet your specific objectives.

(3) No part of this document shall be reproduced or reprinted without the prior written permission.

(4) The information in this document is subject to change without notice.

(5) Contents of this document apply to program version 2.0 and later.

Liability Limitations of the Product

Takebishi Corporation makes no warranties concerning the product, unless stated in the warranty guidelines.

Takebishi Corporation disclaims, without limitation, all liability for any loss or damage of any kind, direct or indirect, to

the customers or any third parties caused by the use of this product or by unexpected defects in the product.

About This Software

You may use this software by installing it on one specific computer. If you wish to install the software on another

computer and use it, purchase another copy.

You may not copy the software for any reason other than backup.

Store the CD (media) which contains the software safely.

You may not reverse engineer, decompile, or disassemble the software.

You may not allow any third parties to use the whole or a part of the software by transferring, exchanging, or shifting it

without the prior permission.

The specifications for this software are subject to change without notice.

Copyright

Copyright of the program and online manual contained in the CD belongs to Takebishi Corporation. You may not copy,

transfer, or distribute (including distribution on the network) the contents of the CD to any third parties. You may not

register or record the contents to video tape or other media without the prior permission.

Trademarks

ArchestrA and InTouch are trademarks of Wonderware Corporation.

MELSEC and MELSECNET are trademarks of Mitsubishi Electric Corporation.

Windows and EXCEL are trademarks of Microsoft Corporation.

All other company names, product names, and trademarks belong to their respective owners.

Table of Contents

1. Introduction ............................................................................................................................................................................................5

1.1 Overview ...........................................................................................................................................................................................5

1.2 Features ............................................................................................................................................................................................5

1.3 PLC Communications Protocols ..................................................................................................................................................5

1.4 Application Communications Protocols ......................................................................................................................................6

2. Composition ...........................................................................................................................................................................................7

2.1 System Configuration ....................................................................................................................................................................7

2.2 System Requirements ....................................................................................................................................................................8

2.2.1 Computer System ....................................................................................................................................................................8

2.2.2 PLC System ..............................................................................................................................................................................9

3. Installation .......................................................................................................................................................................................... 10

3.1 Procedure ....................................................................................................................................................................................... 10

3.2 Installed Files ............................................................................................................................................................................... 15

3.3 License Certification .................................................................................................................................................................... 16

3.3.1 Serial Number ....................................................................................................................................................................... 16

3.3.2 Hardware Key ....................................................................................................................................................................... 16

3.3.3 License status and application operation ........................................................................................................................ 16

3.3.4 Using License Manager ....................................................................................................................................................... 17

3.4 Uninstallation ............................................................................................................................................................................... 21

4. Specifications ...................................................................................................................................................................................... 23

4.1 General Specification .................................................................................................................................................................. 23

4.2 Access Name (Tagname)............................................................................................................................................................. 24

4.3 Access Range ................................................................................................................................................................................. 25

4.4 Device Type and Item Name ..................................................................................................................................................... 26

4.5 Expanded Tagname .................................................................................................................................................................... 28

4.5.1 Not Specified .......................................................................................................................................................................... 29

4.5.2 Bit Position Read in Word Device (: 00 ~ : 15) ................................................................................................................. 29

4.5.3 32-bit Signed Integer (: D) ................................................................................................................................................... 29

4.5.4 16-bit BCD (: B) ..................................................................................................................................................................... 29

4.5.5 32-bit BCD (: C) ..................................................................................................................................................................... 29

4.5.6 Floating Point (: R) ............................................................................................................................................................... 29

4.5.7 16-bit Unsigned Integer (: U) .............................................................................................................................................. 29

4.5.8 Character String (: S) ........................................................................................................................................................... 30

4.5.9 Text Decimal (: A) .................................................................................................................................................................. 30

4.5.10 Text Hexadecimal (: H) ...................................................................................................................................................... 30

4.5.11 Batch File Write (.F) ........................................................................................................................................................... 30

4.6 System Tag .................................................................................................................................................................................... 31

4.6.1 Global System Tag ................................................................................................................................................................ 31

4.6.2 Device Specific System Tag................................................................................................................................................. 31

4.6.3 Device Group Specific System Tag .................................................................................................................................... 32

4.6.4 Redundant Device Specific System Tag ........................................................................................................................... 33

5. Configuration ...................................................................................................................................................................................... 34

5.1 Tutorial ........................................................................................................................................................................................... 34

5.2 DAServer Manager Configuration ........................................................................................................................................... 40

5.2.1 Global Parameters................................................................................................................................................................ 40

5.2.2 Adapter Configuraiton ......................................................................................................................................................... 42

5.2.3 PLC Configuration ............................................................................................................................................................... 45

5.2.4 Redundancy Configuration................................................................................................................................................. 49

5.3 DCOM Configuration ................................................................................................................................................................. 51

5.3.1 Overview................................................................................................................................................................................. 51

5.3.2 Procedure ............................................................................................................................................................................... 53

5.3.3 Notes on Windows XP/SP2 ................................................................................................................................................. 59

5.4 Access from InTouch .................................................................................................................................................................... 63

5.5 DDE Access from Microsoft EXCEL ........................................................................................................................................ 64

5.6 DDE Access from Visual Basic 6.0 ........................................................................................................................................... 65

5.7 OPC Access from Visual Basic 6.0 ............................................................................................................................................ 66

6. MELSEC Ethernet Unit Configuration ........................................................................................................................................ 67

6.1 MELSEC-iQ-R Series ................................................................................................................................................................. 67

6.1.1 Unit Parameter ..................................................................................................................................................................... 67

6.1.2 Open Setting .......................................................................................................................................................................... 67

6.2 MELSEC-Q Series....................................................................................................................................................................... 68

6.2.1 Network Parameters -- General ........................................................................................................................................ 68

6.2.2 Network Parameters -- Operations .................................................................................................................................. 69

6.2.3 Network Parameters – Initial Setting .............................................................................................................................. 70

6.2.4 Network Parameters – Open Setting ............................................................................................................................... 70

6.3 MELSEC-QnA/A Series ............................................................................................................................................................. 71

6.3.1 Mode Selection Switch (MODE) ........................................................................................................................................ 71

6.3.2 Communication Configuration Switches (SW1~SW8) ................................................................................................. 71

6.3.3 Network Parameters ........................................................................................................................................................... 72

6.3.4 Initial Processing .................................................................................................................................................................. 73

6.3.5 Port Control Processing ....................................................................................................................................................... 75

6.4 Sample Ladder Program (MELSEC-QnA Series) ................................................................................................................ 77

6.5 Sample Ladder Program (MELSEC-A Series) ...................................................................................................................... 81

7. Troubleshooting .................................................................................................................................................................................. 85

7.1 Version Information..................................................................................................................................................................... 85

7.2 Connectivity with PLC ............................................................................................................................................................... 85

7.3 WindowViewer (InTouch) Communication Status ............................................................................................................... 85

7.4 Attention of TCP/IP communication ........................................................................................................................................ 86

7.5 Error Messages ............................................................................................................................................................................ 87

7.5.1 Application Messages ........................................................................................................................................................... 87

7.5.2 Error Message Causes and Solutions ............................................................................................................................... 89

7.5.3 Frequently Asked Questions .............................................................................................................................................. 91

7.5.4 Winsock Error Codes ........................................................................................................................................................... 94

7.6 Diagnostics Functions ................................................................................................................................................................. 95

7.6.1 LOG Flag ................................................................................................................................................................................ 95

7.6.2 Diagnostics ............................................................................................................................................................................. 97

8. Addendum ......................................................................................................................................................................................... 104

8.1 DDE Test Client (Visual Basic) ............................................................................................................................................... 104

8.2 OPC Sample Program (Visual Basic) .................................................................................................................................... 106

8.3 OPC Test Client .......................................................................................................................................................................... 107

8.4 User Support............................................................................................................................................................................... 108

Introduction

- 5 -

1. Introduction This User’s Guide describes the functions and operation of MELSEC Ethernet DAServer (hereafter referred to as

DAServer).

Media CD of DAServer contains the DAServer software, online manual, and a sample program. The manuals are not

available in hard copy.

1.1 Overview DAServer is a Microsoft Windows application program that acts as a communications protocol server. It allows other

Windows application programs access to data in Mitsubishi PLC MELSEC via Ethernet. It may also be accessed by a

DDE, FastDDE, SuiteLink, or OPC client.

*DAServer is intended for use with Wonderware InTouch (Version 7.11 Patch 02 and later).

1.2 Features DAServer provides the following features:

- The ability to use multiple application communications protocols (OPC/SuiteLink/DDE/FastDDE/NetDDE)

simultaneously.

- The ability to be configured remotely.

- Extensive RAS functions.

- The ability to add tags beforehand and import/export them

- The ability to add new application-level protocols on the fly.

1.3 PLC Communications Protocols DAServer supports Mitsubishi Electric MELSEC-Q Series, QnA Series, and A Series PLCs as well as MELSEC SLMP

Protocol. SLMP Protocol defines the communication protocol of Mitsubishi MELSEC Series PLCs. It allows external

applications to access the internal memory of the PLCs.

Introduction

- 6 -

1.4 Application Communications Protocols MELSEC Ethernet DAServer uses 5 types of protocols (OPC, SuiteLink, DDE, FastDDE, NetDDE) to communicate

with client applications.

OPC

OPC (OLE for Process Control) is a standard interface based upon Microsoft’s OLE/COM technology. This standard

makes possible interoperability between automation/control applications, field systems/devices and business/office

applications.

Traditionally software/application developers had to write custom drivers to exchange data with field devices. But OPC

defines a common interface and provide the reusability of HMI, SCADA and control/custom applications.

OPC uses DCOM (Distributed COM) for remote communications via the network.

SuiteLink

SuiteLink is a TCP/IP based protocol designed by Wonderware. It provides data integrity and high throughput.

It provides the following features:

- Ability to provide client applications with a time stamp and quality indicator on all data values.

- High throughput.

- Microsoft’s standard network transport protocol TCP/IP

DDE

DDE is a protocol which provides applications in the Windows environment with two-way communication: Send/receive

data and instructions to/from each other. With it, client applications send a request, DAServer sends data according to

the request.

FastDDE

FastDDE is a protocol which simplifies and packs Wonderware’s proprientry DDE messages into a single Microsoft

DDE message. It improves efficiency and performance by reducing the total number of DDE transactions required

between a client and a server.

NetDDE

NetDDE is a protocol which extends the standard DDE functionality for communication over networks and enables

communication between applications running on different computers connected via networks or modems.

Composition

- 7 -

2. Composition System configuration of DAServer is provided below.

2.1 System Configuration

- You can access the PLCs on Ethernet from InTouch on a local PC or custom application (VC/VB). You can

access other stations on MELSECNET via the station connected to Ethernet.

- You can access DAServer on another node from the application on a remote PC to get the PLC data.

- You can configure/diagnose DAServer that is running on another node from SMC (System Management

Console) on a remote PC.

Composition

- 8 -

2.2 System Requirements

2.2.1 Computer System

The following hardware and software are required to run DAServer:

Description

Computer PC running Windows

Basic OS*

Windows 10 Version 1607

Windows 8/ Windows 8.1

Windows 7

Windows Vista

Windows Server 2012(R2)

Windows Server 2008(R2)

Memory Min. 1GB

HDD Min. 100MB

Drive CD-ROM drive

LAN Adapter Adapter that runs on Windows

* Performance has been confirmed on Japanese and English OS’. Please test carefully before using the system on

an OS other than Japanese and English OS’.

* There are following limitations for Windows 8/7/Vista/2012/2008.

- Unsupported NetDDE.

- Run execution file directory because service program are not available with DDE.

- Does not use both interface, DDE and OPC at a same time.

Composition

- 9 -

2.2.2 PLC System

DAServer supports the following PLCs.

CPU Units

MELSEC-iQ-R Series R04CPU,R08CPU,R16CPU,R32CPU,R120CPU

MELSEC-Q Series

Q00(U)(J)CPU, Q01(U)CPU, Q02(U/H/PH)CPU, Q03UD(E)CPU

Q04UD(E)HCPU, Q06(P)HCPU, Q06UD(E)HCPU, Q12(P/PR)HCPU

Q25(P/PR)HCPU, Q13UD(E)HCPU, Q26UD(E)HCPU, Q10UD(E)HCPU

Q20UD(E)HCPU, Q50UDEHCPU, Q100UDEHCPU, Q03UDVCPU

Q04UD(P)VCPU, Q06UD(P)VCPU, Q13UD(P)VCPU, Q26UD(P)VCPU

MELSEC-L Series L02/06CPU(-P)

L26CPU-(P)BT

MELSEC-FX Series

FX0(S/N)

FX1(S/N/NC)

FX2(N/2NC/2C)

FX3(S/U/UC/G/GC)

FX5U(C)

MELSEC-QnA Series Q2A(S/SH)CPU(-S1)

Q3ACPU

Q4A(R)CPU

MELSEC-A Series

A1(N)(S/SH)CPU

A2(N/A/U)(S)CPU(-S1)

A3(N/A/U)CPU

A4UCPU

Ethernet Units

MELSEC-iQ-R Series RJ71EN71, CPU Built-in Ethernet Port*1

MELSEC-Q Series QJ71E71-(100/B5/B2), QnUDE(H) CPU Built-in Ethernet Port*1

MELSEC-L Series LJ71QE71, CPU Built-in Ethernet Port

MELSEC-FX Series FX3U-ENET(-L), FX5 CPU Built-in Ethernet Port

MELSEC-QnA Series A(1S)J71QE71(N/N3)(-T/B5/B2)

MELSEC-A Series A(1S)J71E71(N/N3)(-S3)(-T/B5/B2)

CC-Link IE Field

(SLMP protocol)

NZ2GF-ETB

*1 CPU Built-in Ethernet port has several restrictions in comparison with the Ethernet Unit.

- You cannot use the automatic open UDP port (No.5000).

- You cannot use Q4E frame and A1E frame.

- You cannot use block access.

- You cannot access CPU on another station in a multiple CPU system.

- You cannot access CPU on another station via a network (MELSECNET).

- You cannot access Random access buffer.

- You cannot access buffer memory of the intelligent function module.

- In using TCP/IP, Existence Confirmation will be done 9 times for 5 seconds.

Installation

- 10 -

3. Installation

3.1 Procedure

(1) Inserting the DAServer CD in the CD drive launches the installer. Select “Install DAServer.”

There is something that the installation starts without displaying this screen according to the product.

Important

You must have Administrator rights to set up DAServer.

Installation

- 11 -

(2)If your computer doesn’t fill with precondition, the following window may be displayed. Install displayed lists and

press “Next.”

(3) If a FactorySuite product is already installed, the following dialog may be displayed. Click OK.

(4) When the InstalShield Wizard is displayed, press “Next.”

Installation

- 12 -

(5) If you agree with the License Agreement, check “I agree” and press “Next.”

(6) Enter user information and press “Next.”

Important

Please input the serial number that has been described to the product accurately.

If inputting invalid serial number, following dialog will be displayed.

Installation

- 13 -

(7) After input valid serial number, the following dialog will be displayed. Select where you wish to install the system

or components you wish to install as may be necessary.

(8) Preparation for installation is now complete. Press “Install” to start installation.

(9) If no FactorySuite product is installed, the following dialog may be displayed. Click OK.

Installation

- 14 -

(10) If installation is completed correctly, the following dialog will be displayed. Press “Finish.”

Installation

- 15 -

3.2 Installed Files The installer installs the following files:

File Name Destination Coment

MelsecEthernet.exe Install Folder DAServer itself

MelsecEthernet.dll Install Folder DAServer itself

MelsecEthernet.pdf Install Folder Online manual

MelsecEthernet.aaRUL Install Folder DAServerdefinition file

MelsecEthernet.aaCFG Install Folder DAServer configuration file

CFG_TAKEBISHI_LAN.dll Install Folder Dialog library

CFG_TAKEBISHI_E71.dll Install Folder Dialog library

LicMan.exe Install Folder License Manager

Register.bat Install Folder Registry registration file

UnRegister.bat Install Folder Registry unregistration file

DdeSample.xls Install Folder EXCEL sample

OPC Client.exe Install Folder OPC client test tool

DDE Client Sample Install Folder¥Sample¥VbSampleDde¥*.* VB6.0 project

OPC Client Sample Install Folder¥Sample¥VbSampleOpc¥*.* VB6.0 project

MELSEC-Q Sample Install Folder¥GPPW¥QJ71E71 GX-Developer project

MELSEC-QnA Sample Install Folder¥GPPW¥ AJ71QE71 GX-Developer project

MELSEC-A Sample Install Folder¥GPPW¥AJ71E71 GX-Developer project

Wonderware Common components may be installed in addition to the files listed above.

Installation

- 16 -

3.3 License Certification This chapter explains the procedure to install the regular license by using License Manager.

License Certification is the procedure that add the license information to the product and run as regular product.

The licensing agreement of our software product permits the right that is installed in one specific PC and used.

3.3.1 Serial Number

The serial number is a unique number received when the customer buys the license. When installing it, the customer

should accurately input this serial number. The serial number input when installing it can be displayed by using

License Manager.

3.3.2 Hardware Key

There is something that requested the hardware key according to the product type. In this case, it is necessary to install

both the serial number and the hardware key in same PC to execute the application. Please input an accurate serial

number when you install it, and connect the hardware key with a PC.

3.3.3 License status and application operation

The following table shows the status of the license under each situation and the operation of the application.

Operation can be confirmed with the icon of SMC.

SMC Icon License Status Application Operation

Valid License Run without the restriction.

Invalid License Run as demo mode for only one hour.

Stop to communicate after one hour.

Term License

Run for 14 days after installing.

Please install the license code between those.

Stop to communicate after specified period passed.

Temporary License Run as demo mode for 30 days after installing.

Stop to communicate after specified period passed.

Expiration License Stop to communicate beacause specified period passed.

Installation

- 17 -

3.3.4 Using License Manager

Start License Manager

From the Start Menu select “DAServer” -> “License Manager” to start the license certification tool.

If status is displayed as "OK", the license is valid. In this case it is not necessary to operate the following.

Installation of hardware key

If status is displayed as "HASP", it is necessary to install the hardware key.

Install the hardware key in a PC, and restart the license manager.

If status is displayed as "OK", the license is valid. In this case it is not necessary to operate the following.

Installation

- 18 -

Get the license code

If status is displayed as "TERM", it is necessary to get and install the license code within 14 days.

The license code can be got by WEB, Mail, FAX.

WEB

Please input and transmit serial number, computer ID, and necessary information from the user registration page on

our WEB site.

We will inform of the license code with mail.

URL http://www.faweb.net/asp/registration.aspx

Mail

Please transmit serial number, computer ID, and a necessary information (company name, name, phone number, and

mail address) to us after it is described in the subject as "FAWEB:License".

We will inform of the license code with mail.

Mail Address [email protected]

FAX

Please fill in Serial No., computer ID, and necessary information on the user registration form and fax it to us.

We will inform of the license code with FAX.

FAX +81-75-325-2273

Installation

- 19 -

Install License

Select the product in License Manager and right-click on it. From the popup menu select “Install License”.

Input the acquired license code into "License Code", and press OK button.

If the license code is certified, status becomes "OK".

Installation

- 20 -

Transfer License

The license can be transferred from PC to other PC in which the license is installed. The application is developed,

evaluated with the development machine, and it is possible to shift to the destination machine.

1. First, before transferring License, install the product on destination PC.

Confirm the computer ID in the destination PC’s display below.

2. Next, in the source PC’s display below select the product with Status displayed “OK” and right-click on it.

From the popup menu select ”Transfer License”.

3. Input the computer ID of the destination PC into the source PC.

4. Then press “Transfer” button. The license code is displayed corresponding to the destination PC.

Caution: After this operation is done, the license in the source PC becomes invalid.

5. Install the license code above on the destination PC. Then transferring License is completed.

Installation

- 21 -

3.4 Uninstallation To uninstall DAServer, select “MELSEC Ethernet DAServer” from “Add/Remove Programs” on the Control Panel.

Important

Please you must run “Unregister.bat” of Install path as administrator before uninstllation, if the operating system

uses User Accoutn Control (UAC).

Installation

- 22 -

If you select “Change,” the following dialog will be displayed to allow you to modify or repair the contents of installation.

Specifications

- 23 -

4. Specifications This section describes the specifications of DAServer.

4.1 General Specification

Description

Service Activation Yes

Max. Number ofAdapters/Ports 62 adapters

Max. Number of PLCs 62 units/adapter

Supported Protocols DDE, FastDDE, NetDDE, SuiteLink, OPCDA2.05A

Devices That Can Be Accessed All MELSEC devices (see list on next page on)

Tag Alias Yes (defined in “Device Items” of SMC)

DDE DDE Application Name MelsecEthernet

DDE Topic Name Arbitrary

OPC

Program ID Takebishi.MelsecEthernet.1

Class ID 34E27B57-FEDD-4340-0087-140DC2B6142B

OPC Access Path Not supported

OPC Item ID Adapter name, device name, and tagname are delimited

Data Type

VT_BOOL Boolean

VT_I2 16-bit signed integer

VT_UI2 16-bit unsigned integer

VT_I4 32-bit signed integer

VT_R4 32-bit signed real

VT_BSTR Character string

Expansion Format

1-bit boolean

Word device bit position specification

16-bit signed integer

16-bit unsigned integer

32-bit signed integer

16-bit BCD

32-bit BCD

Floating point

Character string

Text-format decimal

Text-format hexadecimal

PLC

Communication

Communication Code Binary (ASCII not supported)

Communication Protocol Q-compatible 4E frame / QnA-compatible 3E frame /

A-compatible 1E frame

Communication Commands Batch Read / Batch Write / Random Write / Block Write

Random Access Buffer Communication

Note

- “Maximum number of adapters” and “maximum number of PLCs” indicate the maximum number

that can be defined on the software.

- The communication protocol "Q Comaptible 4E Frame" of MELSEC-Q Series is valid for Ethernet Unit version,

after upper 5 place of serial number is '07082' and functional version 'D'.

Specifications

- 24 -

4.2 Access Name (Tagname) How to access DAServer depends on the way a client application communicates with it.

OPC

To access an OPC item, the OPC client needs to connect to DAServer, create an OPC group, and register tags. DAServer

supports Public OPC groups, which are shared across multiple clients to improve the performance of the entire system.

In case of OPC communications, Access Name consists of 6 elements: node name, program name, group name, device

group, link name and item name. The following briefly describes the respective elements:

Node Name Computer name on the network

Program ID The name of the program that provide the client application with data element. OPC server has the

name with a unique identifier (ProgID)

DAServer is named “Takebishi.MelsecEthernet.1.”

Group Name The OPC group created from the client application for organizing a collection of items based on the

update rate

Link Name Set of hierarchy node names defined by the DAServer manager

Item Name A name that consists of a PLC device name (such as register, relay, timer, and counter) and an

extension.

For example, if you wish to access data memory (D) 0 of PLC “PLC1”, adapter “PORT1”, of DAServer on the local node,

the Tagname will be “PORT1.PLC1.D0.”

DDE/SuiteLink

In the case of DDE/SuiteLink communications, Access Name consists of 4 elements node name, application name, topic

name and item name. The following briefly describes respective elements:

Node Name Computer name on the network

Application Name The name of the program that provide the client application with data element. DAServer is

named “MelsecEthernet.”

Topic Name Name of the accessed PLC information defined by DAServer manager. The name is used in

all communications with the PLC. You can define multiple topic names for the same PLC to

poll different points at different rates.

Item Name A name that consists of a PLC device name (such as register, relay, timer and counter) and an

extension.

Note

MELSEC device names listed on the following page can be used as item names. You may define an alias of the

device name on the “SystemItems” tab on SMC’s “PLC Configuration” page.

Specifications

- 25 -

4.3 Access Range DAServer is accessed to the PLC by using the SLMP Protocol. The table below shows the range of the maximum

access of the SLMP Protocol at reading and writing time.

Accessing Station Max. Read Points Max. Write Points

Max Random

Write Points

Discrete Word Discrete Word Discrete Word

MELSEC-iQ-R Series Ethernet 15360 960 7168 960 94 80

MELSEC-iQ-R Series Other Network

MELSEC-Q Series Ethernet 15360 960 7168 960 188 160

MELSEC-Q Series Other Network

MELSEC-QnA Series Ethernet 7680 480 3584 480 94 80

MELSEC-QnA Series Other Network

MELSEC-A/FX Series Ethernet 2048 256 256 256 80 40

MELSEC-A/FX Series Other Network 512 32 160 64 20 10

Note

- "Ethernet" means accessing station of DAServer.

"Other Network" is effective When it accesses station on other network through Ethernet accessing station.

- "Max. Read Points" in the table is applied to usual polling process.

- "Max. Write Points" in the table is applied at the time of writing to the expanded tag.

When accessing expanded tag, it becomes only an access wording, and each bit is not accessed.

Important

As for the range of the access, in PLC Configuration Screen of DAServer, the maximum value of Ethernet Station is

set by default. Please set an appropriate value referring to the above table when you access other station via

another network.

Specifications

- 26 -

4.4 Device Type and Item Name See below for a list of PLC device types that can be specified as item names and the corresponding item names.

Bit Device

Item

Name Device Type Type Note

X Input relay Hex

Y Output relay Hex

DX Direct input relay Hex Not A Series

DY Direct output relay Hex Not A Series

B Link relay Hex

M Internal relay Dec

L Latch relay Dec Not A Series (accessed as internal relay M)

S Step relay Dec Not A Series (accessed as internal relay M)

F Annunciator Dec

V Edge relay Dec Not A Series

TS Tmer contact Dec

TC Timer coil Dec

SS Multiple timer contact Dec Not A Series

SC Multiple timer coil Dec Not A Series

CS Counter contact Dec

CC Counter coil Dec

SM Special relay Dec Not A Series (ACCESSED AS M9000’S)

SB Special link relay Hex Not A Series

Word Device

Item

Name Device Type Type Note

D Data register Dec

W Link register Hex

R File register Dec

ZR Expanded file register (serial number) Dec Not A Series

ER Expanded file register (block number

specified)

Dec Example: Accessing address 10,000 of block No. 10->

ER10:10000

BM Ethernet unit

Random access buffer

Hex Example: BM1FFF -> Specifying the buffer memory

address as the device number

T(TN) Timer current value Dec “Txxx” or “TNxxx”

C(CN) Counter current value Dec “Cxxx” or “CNxxx”

SN Multiple timer current value Dec Not A Series

SD Special register Dec Not A Series

SW Special link register Hex Not A Series (accessed as D9000’s)

Z Index register Dec Not A Series

Specifications

- 27 -

Note

-Device range depends on your CPU.

-When using AnUCPU, only the AnACPU device range can be accessed due to the Ethernet unit restriction.

-When using A Series, DX, DY, V, S, SS, SC, ZR, SB, SW, SM, SD, and Z are not accessible.

-When accessing ‘BM’, automatic open UDP port (5000) can not use.

-iQ-RCPU can not be used Random access buffer “BM”.

-MELSEC Ethernet connection, can not use long timer “LT”, Long integration timer ”LST”, Long counter “LC”,

Long index register “LZ”, the unit refresh register “RD”.

Specifications

- 28 -

4.5 Expanded Tagname See below for specifying an expanded tagname. A separator must separate the tagname and expanded character

string.

Expansion Description Note

None Word device : 16-bit signed integer

Bit device: boolean

: 00~: 15 Bit position read in word device: boolean Cannot write/no bit device specification

: D 32-bit signed integer

: B 16-bit BCD

: C 32-bit BCD

: R floating point

: U 16-bit unsigned integer

: Sxxx character string where “xxx” is the number of access points (numeric

value between 1 and 1023)

: Axxx text Dec where “xxx” is the number of access points (numeric


: Hxxx text Hex where “xxx” is the number of access points (numeric


: Fxxx File Batch Write “xxx” is the number of access points (numeric value

between 1 and 1023)

*Access points must be below the “Access Range” defined in Device Configuration.

Note

A colon “:” or a dot “.” may be used as a separator. When using InTouch, a dot has a special meaning as a tag

variable name. In that case, register the tag variable name and item name separately.

(Example) tag variable name “D100_D” -> item name “D100.D”

Specifications

- 29 -

4.5.1 Not Specified

When the tagname is not expanded (tagname + device number only), word device will be a 16-bit signed integer type,

and the bit device will be a Boolean. For data register number 1000, it will be “D1000,” and link relay number 1FF

will be “B1FF.”

4.5.2 Bit Position Read in Word Device (: 00 ~ : 15)

By specify a separator and a number after the tagname (word device), you can read bits in a word device. A bit device is

not expanded. This tag is only for read, not for write.

For example, “D99: 0” indicates 0th bit of D99, and “D100: 15” indicates the 15th bit of D100.

4.5.3 32-bit Signed Integer (: D)

By specify “: D” after the tagname, you can read/write the register value as a 32-bit signed integer.

For example, “D100: D” will access D100 and D101 as double word.

4.5.4 16-bit BCD (: B)

By specify “: B” after the tagname, you can read the register value after a BCD to BIN conversion, and write the value

after a BIN to BCD conversion.

For example, specifying “D100: B” when reading, 1234 (Hex) stored in D100 is converted into “1234 (Dec).” Specifying

“D100: B” when writing, 5678(Dec) is converted into 5678 (Hex).

4.5.5 32-bit BCD (: C)

By specify “: C” after the tagname, you can read the register value as a 32-bit BCD value after a BCD to BIN conversion,

and write the value after a BIN to BCD conversion.

For example, specifying “D100: C” when reading, 1234 (Hex) stored in D100 is converted into 1234 (Dec).

Specifying “D100: C” when writing, 5678 (Dec) is converted into 5678 (Hex).

4.5.6 Floating Point (: R)

By specify “: R” after the tagname, you can read/write the register value as a 32-bit real data.

For example, Specifying “D10: R”, “0x42F6CCCD” stored in D10 and D11 is read “123.4” as floating point data.

4.5.7 16-bit Unsigned Integer (: U)

By specify “: U” after the tagname, you can read/write the register value as an unsigned integer.

For example, specifying “D1: U”, “-5536” stored in D1 is read as “60000.”

Specifications

- 30 -

4.5.8 Character String (: S)

By specify “: Sxxx” ( xxx is the number of accessed register points: 1 ~ 1023) after the tagname, you can read/write the

register value as a character string. When "Register R/W Points" of the PLC Configuration screen doesn't come up to

"1023", the point set by "Register R/W Points" becomes the maximum value. To access a character string tag with

InTouch, use an I/O Message type tag.

For example, specify “D100: S5” to handle the data in D100~D104 as character string. When you create an I/O Message

type tag with the tagname “DS” and item name “D1: S5” using InTouch and execute “DS = ABCDEFGHIJ”, the result

is “D1=0x4241, D2=0x4443, D3=0x4645, D4=0x4847, D5=0x4A49”.

4.5.9 Text Decimal (: A)

By specify “: Axxx” (xxx is the number of accessed register points: 1 ~ 1023) after the tagname, you can read/write the

register value as text decimal. When "Register R/W Points" of the PLC Configuration screen doesn't come up to "1023",

the point set by "Register R/W Points" becomes the maximum value. When poking, the maximum size of value is 2047

bytes. To access a character string tag with InTouch, use an I/O Message type tag.

For example, specify “D100: A3” to handle D100~D102 as text decimal. When “D1=1234, D2=100, D3=1” is in PLC and

you create an I/O Message tag with a tagname “D1A” and item name “D1:A3” using InTouch and access it, "1234,100,1"

will be stored in “D1A.” This data is a 16-bit signed integer. If anything other numbers than (0~9) is included in the

write character string, the subsequent values are ignored.

4.5.10 Text Hexadecimal (: H)

By specify “: Hxxx” ( xxx is the number of accessed register points: 1 ~ 511) after the tagname, you can read/write the

register value as text hexadecimal. When "Register R/W Points" of the PLC Configuration screen doesn't come up to

"511", the point set by "Register R/W Points" becomes the maximum value. To access a character string tag with

InTouch, use an I/O Message type tag.

For example, specify “D100:H3” to handle D100~D102 as text hexadecimal. When “D1=0x1234, D2=0x567, D3=0x1”

is in PLC and you create an I/O Message tag with a tagname “DH” and item name “D1: H3” using InTouch and access

it, "123405670001" will be stored in “DH.” If anything other numbers than (0~9, A~F) is included in the write

character string, the character is handled as “0.”

4.5.11 Batch File Write (.F)

By specify ": Fxxx" ( xxx is the number of accessed register points: 1 ~ 1023*16) after the tagname, you can write the

value in CSV file in batch to PLC. You create text file as CSV format and write the path to the tag when excuting

POKE command. When "Register R/W Points" of the PLC Configuration screen doesn't come up to "1023", the point

set by multiply "Register R/W Points" by 16 becomes the maximum value. This type is write-only and the reading

value always space character. To access the tag with InTouch, use an I/O Message type tag.

For example, specify "D1: F64" to handle D1 ~ D64 as CSV file. When poking values of tag1 ~ tag64 in batch, you

create an I/O Message tag with a tagname "D1FILE" and item name "D1: F64" using InTouch and execute following

script.

FileWriteFields("C:¥TEST.CSV", 0, "tag1", 64);

D1FILE = "C:¥TEST.CSV";

You should use the value as the range of 16 bit register.

Specifications

- 31 -

4.6 System Tag System tag is a special tag whose information is set by the server.. Tagname starts with “$SYS$.”

4.6.1 Global System Tag

Item Type Attribute Description

$SYS$Licensed BOOL Read

Stores the information of whether appropriate DAServer license

exists. (TRUE when yes, FALSE when no)

4.6.2 Device Specific System Tag

Item type Attribute Description

$SYS$Status BOOL Read

Indicates the status of communication with the PLC.

(TRUE when good, FALSE when bad)

For a DDE or SuiteLink client, the status is for each hierarchy

level. For an OPC client, the status is for all hierarchy levels.

* At the root of each hierarchy, the status is always GOOD

(TRUE).

* This does not indicate if an error has occurred in each item.

$SYS$ErrorCode DWORD Read

Stores a detailed error code (“0” when good, “non-0” when there

is an error).

$SYS$ErrorText STRING Read Stores an error character string.

$SYS$StoreSettings WORD Read/Write

If the client changes the update interval in SYS$UpdateInterval

and writes a “1” to this system tag, the new update rate is saved

in the configuration file. If the file is saved correctly, this system

tag is cleared to “0.” If the client changes the update interval in

$SYS$UpdateInterval but does not write a “1” to

$SYS$StoreSettings, DAServer will have the same update

interval as before until it is restarted.

When read, this tag is always 0.

Specifications

- 32 -

4.6.3 Device Group Specific System Tag


$SYS$UpdateInterval DWORD Read/Write

Stores the current update interval in milliseconds. When you

Specify a 0, none of the tags in this topic will be updated.

Valid range is 0~2147483647.

$SYS$MaxInterval DWORD Read Stores the maximum value of the update interval.

$SYS$WriteComplete WORD Read/Write

Stores the write status. This system tag will be “0” when

there is a write request, and “1” when all the write processes

are done (completed/failed).

$SYS$ReadComplete WORD Read/Write

Stores the read status. This system tag will be “1” when all

active tags are read at least once. It will be “0” if at least one

tag is added. If the read operation of the tag is successful, it

will be “1,” and “-1” if it fails. Writing a “0” to this tag resets

the read status of all items. When all the read processes are

completed, it will be “1” or “-1.”

$SYS$ItemCount DWORD Read Stores the number of added tags.

$SYS$ActiveItemCount DWORD Read Stores the number of active tags.

$SYS$ErrorCount DWORD Read

Stores the number of tags that have had an error (quality flag

is anything other than GOOD).

$SYS$PollNow BOOL Read/Write

Writing “1” to this system tag rereads all tags. Use this

system tag to update all tags at once separate from the update

interval. This operation is valid even when the update

interval is set to “0.”

Specifications

- 33 -

4.6.4 Redundant Device Specific System Tag


$SYS$ForceFailover BOOL Read/Write

By set to ‘1’, DAServer should force this device to switch

to secondary device.

$SYS$ActiveDevice STRING Read

DAServer stores active device name such as

“New_Adapter_000.New_PLC_000.”

$SYS$StandbyDevice STRING Read

DAServer stores standby device name such as

“New_Adapter_001.New_PLC_000.”

$SYS$PrimaryDeviceStatus BOOL Read

DAServer stores communication status for primary

device. It contains the value of $SYS$Status.

$SYS$SecondaryDeviceStatus BOOL Read

DAServer stores communication status for standby

device. It contains the value of $SYS$Status.

$SYS$FailoverTime STRING Read DAServer stores GMT time when failover was occurred.

$SYS$FailoverReason STRING Read

This system item will show the reason for the failover.

The value text indicate to "ForceFailover" or the value of

the system item $SYS$ErrorText

Configuration

- 34 -

5. Configuration You must configure the DAServer Manager (hereafter referred to as DAServer manager) on the System Management

Console (hereafter referred to as SMC) to use DAServer. Launch SMC from “Windows Start Menu” ->”Programs”

->”Wonderware” ->”System Management Console.” Configure the hardware and software, such as device hierarchy

and simulation modes, before you start DAServer.

5.1 Tutorial This section describes the steps to use DAServer quickly. Detailed description of each step will be provided later.

1. Installation/configuration of Ethernet adapter

Install the Ethernet adapter and open the “Local Area Connection Properties” page from the Control Panel.

Configuration

- 35 -

Open the TCP/IP properties page and configure the IP address, host name, etc.

2. Installing the product

Run Setup.exe on the CD and install MELSEC Ethernet DAServer.

Important

You must have Administrator rights to install MELSEC Ethernet DAServer.

Configuration

- 36 -

3. Starting up SMC

From the Start menu, select ”Programs” -> ”Wonderware” ->”System Management Console” to start SMC.

Expand the DAServer manager tree in SMC and select “Takebishi.MelsecEthernet.1” (it should be under DAServer

Manager if it is installed correctly).

- DAServer exists under the Local node as “Takebishi.MelsecEthernet.1.”

- See the DAS Control Client documentation for general information about working in this snap-in environment.

Configure DAServer. Before proceeding, determine the hierarchical structure of the network/PLC environment.

4. Global Parameters

Select “Configuration” to display the Global Parameters View in the right pane. Configure the default update interval,

write process type, etc. here.

Note

The default Poke Mode settings for the DAServer is "Optimization Mode." When write operation is repeated

continuously, only the last value will actually be written. For more details, see the DAServre manager document.

Important

Grayed-out global parameters indicate the functions that are not supported.

Configuration

- 37 -

5. Adapter Configuration

Right mouse click on “Configuration” and select “Add Adapter Object” from the pop-up menu.

A default hierarchy tree called “New_Adapter_000” will be created. Its configuration menu will be displayed on the

right. Configure the IP address, port number, etc. here.

Configuration

- 38 -

6. PLC Configuration

Right mouse click on “New_Adapter_000” and select “Add PLC Object” from the pop-up menu.

- A default hierarchy tree called “New_PLC_000” will be created.

- Its configuration menu will be displayed on the right. Configure the network number, CPU number, etc. here.

7. Configuring Topic Name

You can create a group on each hierarchy.

Open the “Device Groups” tab, right mouse click and select “Add” from the pop-up menu.

Note

If you have two SMCs running and open another configuration page from another instance, the second instance will

be locked until the first instance is closed (it will not be saved).

Configuration

- 39 -

8. Activate DAServer

Before accessing from the client application, right mouse click on “Takebishi.MelsecEthernet.1” from the DAServer

manager and execute “Activate Server” to start DAServer.

Note

When using OPC, DAServer automatically starts when you connect from the client.

9. Auto Service

To run DAServer as a Windows service program, right mouse click on “Takebishi.MelsecEthernet.1” and select

“Configure As Service” -> ”Auto Service.”

Configuration

- 40 -

5.2 DAServer Manager Configuration

5.2.1 Global Parameters

Click “Configuration” under “Takebishi.MelsecEthernet.1” to display the Global Parameters View.

Configurable Fields

Item Default Value Description

Device Group Update Interval 500 ms

Define the polling interval of the <Default> device group.

When accessing using OPC, it will be processed as the

<Default> group. UpdateInterval of OPC will be the

interval between events.

Slow Poll Interval 10000 ms Define the slow poll interval when a communication error

has occurred.

Transaction to Subscription Ratio 1

Define the maximum number of messages that can be

processed simultaneously when multiple polling messages

exist.

Transaction Message Timeout 60000 ms Define the message transaction timeout.

Server Protocol Timer 50 ms Define the process interval within the server.

Diagnostic Backlog Size 20 Define the backlog size of the diagnostic transaction display.

Maximum Queued Transactions 75 Define the maximum number of outstanding transactions in

each of the three transaction queues (read, write, refresh.)

Maximum Queued Updates 1 Define the number of outstanding subscription updates for

an individual item.

DDE/SuiteLink Timer Tick 50 ms Define the time between processing DDE/SL client requests.

Configuration

- 41 -


Poke Mode Optimization

Mode

Define the process that takes place when there are multiple

write requests to one item at the same time:

ControlMode: Writes all requests.

TransitionMode: Writes only the first, second, and last

requests.

OptimizationMode: Writes only the last value.

Case Sensitive OFF Determine the case (upper or lower) of group and item

names.

Device Group Cache OFF A different group can share the cache as long as it has the

same item ID (for future expansion).

Simulation Mode OFF Select the operation in simulation mode.

System Items ON Select whether or not system tags can be used.

Unique Device Groups ON Authorize the use of the same topic name.

*Grayed-out fields indicate unavailable functions.

Configuration

- 42 -

5.2.2 Adapter Configuraiton

This section describes how to configure the adapter.

New Adapter Configuration

See below for how to create a new adapter configuration:

1. Click on “Takebishi.MelsecEthernet.1.”

2. Right mouse click on “Configuration” and select ”Add Adapter Object” from the pop-up menu.

3. A default adapter called “New_Adapter_000” is created. You can select an arbitrary adapter name.

4. You may define multiple adapter configurations when you wish to communicate with multiple PLCs.

Configuration

- 43 -

Configurable Fields

Configure the Ethernet communication on the Adapter Configuration page.

Field Default Value Description

Protocol UDP/IP Select the protocol used to communicate with the PLC (TCP/IP or UDP/IP).

Adapter IP Address 0.0.0.0 (* 1)

IP address of the PC LAN adapter in decimal value. Specify “0.0.0.0” when

using one LAN adapter or DHCP system. Specify a unique value when

using multiple LAN adapters or specifying an explicit IP address.

Adapter Port No. 0 (* 2)

PC port number in decimal value. Regularly, “0” is specified. When you

specify your own port number using UDP/IP or or use TCP/IP full passive,

specify this field within the range 1024 ~ 65535.

PLC IP Address 192.168.0.1 Enter the IP address of the connected PLC in decimal value.

PLC Port No. 5000 (* 3)

Enter the port number of the connected PLC in decimal value. Specify the

port number defined by a parameter or ladder program. Valid range is 0 ~

65535. When you use automatic open UDP port with Q/QnA Series, you

may communicate with “5000”. But when accessing random access buffer,

‘BM’, automatic open UDP port (5000) can not use.

Configuration

- 44 -


Reply Timeout 3000 ms

Define the reply timeout after the request message is sent. When Reply

Timeout expires, a timeout error occurs. Valid range is 50 ~ 60000.

Simulation Mode OFF Select whether or not to run DAServer in simulation mode without

connecting to the PLC.

Simulation Type Random

Random :Tag value is changed every time. Write data is ignored.

Fixed Value :Tag value is always 0. Write data is ignored.

Shared Memory :Tag value is fixed. Write data is reflected.

Use Redundant

Communication OFF

Please turn on the check box and set the parameter on standby Ethernet

when you use redundant communication.

* 1 When you specify “0.0.0.0,” it will use the IP address of the LAN adapter that is found first.

* 2 When you specify “0,” OS automatically assigns a port that is not used.

* 3 When using Q/QnA Series, you may use “automatic open UDP port (default: 5000).” When you wish to use

an arbitrary port, modify buffer memory address 20 (14H) or configure the port using the network parameter

of GX-Developer.

Redundancy Communication

When "Use Redundant Communication" is checked, redundant communication becomes effective. The

communication route dynamically changes into the subsystem (parameter in the right of the screen) when the trouble

occurs in the main system (left parameter in communication tools of the screen) so that there is no response from PLC

even if prescribed times is retried. Similarly, it changes into the main system when communication error occurs in the

subsystem.

* When the communication route changes, the communication is continued by the route.

(Never automatically return to the main system side)

Primary System Standby System Primary System Standby System

Configuration

- 45 -

5.2.3 PLC Configuration

This section describes how to configure the PLC you wish to access (hereafter referred to as PLC configuration).

New PLC Configuration

Right mouse click on any adapter and select “Add PLC Object” from the pop-up menu.

1. A default PLC called “New_PLC_000” is created. You can select an arbitrary PLC name.

2. Define multiple devices if you wish to access other stations via the connected PLC.

Configuration

- 46 -

Configurable Fields

Configure the CPU type, multiple CPU system, redundant CPU System and MELSECNET.


PLC Type Q Series PLC type you wish to access (iQ-R / Q / L / FX / A )

Use 4E Protocol OFF

When using MELSEC-Q series, The protocol, "Use 4E Frame" is available.

It is able to control the slippage of message by network trouble, so this

protocol includes sequence number in send/receive message

CPU No

Multiple CPU NONE

CPU number when multiple CPU system is used.

CPU No

Redundant CPU NONE

Accessing CPU when redundant CPU system is used.

Unit Station No. 0

Specify the station number of the unit station you wish to access in a decimal

value when you wish to access a different station that is multidrop connected

to Q Series Serial Communication Link Unit via Ethernet connection

station. Valid range is 0 ~ 31.

MNET Network No. 0 (* 1)

Specify the network number of the last network system you go through in a

decimal value when you wish to access another station on MELSECNET via

Ethernet connection station. Valid range is 0 ~ 255.

MNET PC No. 255 (* 1)

Specify the station number on the last network system you go through in a

decimal value when you wish to access another station on MELSECNET via

Ethernet connection station. Valid range is 0 ~ 255.

Configuration

- 47 -


MNET CPU

Monitoring Timer 10

Specify the timeout(sec) of response from CPU of own or other network by

Ethernet unit which received request from DAServer.

Specify the timeout between 0 and 60.

Coil R/W Size 15360

Specify the maximum number of points of regular read and expanded write

on a bit item.

Register R/W Size 960

Specify the maximum number of points of regular read and expanded write

on a word item.

Coil Write Size 188 Specify the maximum number of points of regular write on a bit item.

Register Write Size 160 Specify the maximum number of points of regular write on a word item.

*1 When you specify the network number and PC number, the communication will be a transient communication

between MELSECNET cyclic transmission. It may affect the response speed.

Note

- Please refer to Chapter 4.3 "Access Range" for details of the access point.

- The communication protocol "Q Comaptible 4E Frame" of MELSEC-Q Series is valid for Ethernet Unit version,

after upper 5 place of serial number is '07082' and functional version 'D'.

Configuring Topic Name

Open the “Device Groups” tab and configure the topic name used for DDE/SuiteLink communication.

Right mouse click on the view to display a pop-up menu. Select “Add” to create a new topic and select an arbitrary

name and update interval.


Name --- Define the topic name used for DDE/ SuiteLink communication.

Update Interval 1000 ms Define the update interval for DDE/ SuiteLink communication.

Configuration

- 48 -

Configuring Tag Name

Open the “Device Items” tab and add the tagname (alias of the actual device).

Right mouse click on the view to display a pop-up menu. Select “Add” to create a new tag and select an arbitrary name

and reference address.


Name --- Define the tagname.

Item Reference --- Define the real device name.

Tag Import/Export

You may import and export tags from the pop-up menu. You can export the tag information as a CSV file, edit it on

Excel, for example, and import it back to save some trouble.

Configuration

- 49 -

5.2.4 Redundancy Configuration

This section describes how to configure the redundancy switching target PLC dynamically.

New Redundancy Configuration

Create some Adapter/PLC configurations

1. Right mouse click on any adapter and select “Add REDUNDANT_DEVICE Object” from the pop-up menu.

2. A default configuration called “New_REDUNDANT_DEVICE_000” is created. You can select an arbitrary name.

Configuration

- 50 -

Configurable Fields


Primary Device ---- Pop-up “Device Browser” and select a hierarchy as primary device.

Secondary Device ---- Pop-up “Device Browser” and select a hierarchy as secondary device.

Ping Item ----

A Ping item must be specified and be a valid tag in both the primary and

secondary controllers to determine the connection status for $SYS$Status.

The Ping item can be a static item in the device such as a firmware version

or processor type. If the Ping item is invalid or does not exist in the controller,

the failover operation may not work correctly as the value of $SYS$Status

may continue to stay as FALSE in the standby device.

Configuring Topic Name

Configure topic name and tag name as same as aboved operations.

Configuration

- 51 -

5.3 DCOM Configuration This section describes how to configure DCOM to connect from a remote computer using OPC. The examples provided

in this section are typical configuration examples. Please modify each setting based on your system security needs.

Note

Please refer to related documents on OS for more details on DCOM.

5.3.1 Overview

Client user must be authenticated on the machine on which the OPC server is running in order to enable DCOM

connection. Authentication of the client machine user is normally done by configuring one user account and one

password on both machines running in a work group. From the user account on the client machine, you log on to the

local PC, remote log on to the server machine, and run the OPC server. The following description provides an example

of configuration on the OPC server machine, unless otherwise indicated.

See below for a configuration example of using DCOM:

Machine Field Simple Secure

Server

Authentication Level None Connect

Start Access Right Everyone Arbitrary user name

Access Right Everyone Arbitrary user name

Identity Interactive User Interactive user/Launching user

Client Pre-defined Authentication Level None None

* “Simple” configuration is for when security is not emphasized.

To use DCOM in a Windows XP workgroup environment, start “Local Security Policy” from Administrative Tools and

set “Network Access: Sharing and security model for local accounts” to “Classic.” This step is not required when you

wish to use DCOM in the domain environment.

Configuration

- 52 -

Important

You can not connect via DCOM if checking the “Windows firewall” in property window of “Local Area Connection” on

Windows Server 2003 / Windows XP. So you should not check this option button.

When Windows XP/SP2 is used, DCOM can be connected by making the firewall effective by setting security.

Please see 5.3.3 "Notes on Windows XP/SP2" for details of the setting.

Configuration

- 53 -

5.3.2 Procedure

Start DCOM Configuration Utility

From the Start menu, select “Run” and enter “DCOMCNFG.EXE” to launch the DCOM configuration utility.

Note

You must log on with Administrator rights to configure DCOM.

Configuration

- 54 -

Default Properties

Combined utilities start on Windows XP. Navigate through “Component Services” -> “Computer” -> “My Computer.”

Right mouse click on “My Computer,” open the Properties page from the pop-up menu, and select the “Default

Properties” tab. On Windows 2000, start DCOMCNFG and select the “Default Properties” tab.

* Check the “Enable Distributed COM on this Computer” check box.

* Set “Default Authentication Level” to “Connect.”

* Set “Default Impersonation Level” to “Identify.”

Important

On the client machine, set “Default Authentication Level” to “None.”

Configuration

- 55 -

DAServer-specific Properties (General)

Right mouse click on ”34E27B57-FEDD-4340-0087-140DC2B6142B” from the “Applications” tab for Windows 2000 and

“DCOM Config” under “My Computer” for Windows XP, and select Properties from the pop-up menu.

* Set the “Authentication Level” to “None.”

Configuration

- 56 -

DAServer-specific Properties (Location)

Select the “Location” tab.

*Check “Run application on this computer.”

Configuration

- 57 -

DAServer-specific Properties (Security)

On Windows XP, the following page opens. Select “Customize” in each field and press “Edit.” On Windows 2000,

select “Use Custom Access Permissions” and press “Edit.”

*Add “Everyone” and “SYSTEM” to “launch permissions,” “access permissions,” and “configuration permissions.”

Configuration

- 58 -

DAServer-specific Properties (ID/Identity)

Select the “ID” tab on Windows XP and “Identity” tab on Windows 2000 and specify the user account that runs the

application.

Select “This User” and specify a user that has Administrator rights. Or select “System Account” to run it as a service

program. When launching DAServer as a service, it becomes a “System Account,” and you cannot specify it as an

“Interactive User” or “Launching User.”

Configuration

- 59 -

5.3.3 Notes on Windows XP/SP2

"Windows firewall" becomes effective if service pack 2 is applied to Windows XP, and neither the DCOM connection

through LAN nor the browsing of the server list that uses the OPCENUM function can be done in the setting of default.

Because the white paper goes out of OPC Foundation, notes when service pack 2 is applied to Windows XP will

recommend often reading.

Please select "Advanced" tab on the property screen of the local area connection, and push "Settings" button.

In Windows XP/SP2, the Windows firewall is effectively set by default. It explains the method of connecting DCOM

with DAServer with the firewall made effective since it the next pages.

Configuration

- 60 -

Exceptions

The application to pass the firewall can be specified in "Exceptions" tab. And push "Add Programs" button and add

"MelsecEthernet.exe". Moreover, to browse the installed server list from another node with the OPCENUM function,

add "OpcEnum.exe".

In addition, port "135" of "TCP" used with DCOM pushing "Add Port" button is added.

Configuration

- 61 -

COM Security

Because the COM security is strengthened when Windows XP/SP2 is applied, the change in the DCOM setting is

needed.

"DCOMCNFG.EXE" is started from the command line or "Component Service" is opened from the management tool of

control panel, and "COM security" tab is selected.

The dialog opens when "Edit limits" button of "Access permit" is pushed. "ANONYMOUS LOGON" is selected to access

OPCEnum.exe remotely, and "Remote Access" is set to "Allow".

Configuration

- 62 -

The dialog opens when "Edit limits" button of "Access permit of starting and making actively" is pushed.

"Everyone" is selected, and "Remote Launch" and "Remote Activation" are set to "Allow".

Configuration

- 63 -

5.4 Access from InTouch This section describes how to access DAServer from Wonderware InTouch.

The following dialog opens when you select “Access Name” from the “System” menu of InTouch.

* Enter “MelsecEthernet” as “Application Name.”

* Enter the name set to “Device Groups” from the DAServer manager as “Topic Name”.

* Select “DDE” or “SuiteLink” for the protocol.

When DAServer has not been activated or the topic name does not exist, the following message may be displayed when

you launch InTouch Viewer.

This dailog will be not shown by set "Start local servers" in configuration dailog of InTouch WindowViewer to OFF.

Configuration

- 64 -

5.5 DDE Access from Microsoft EXCEL Enter “=application name|topic name!item name” in the cell in order to access DAServer from an EXCEL sheet. See

below for an example of accessing the topic name “PLC1” data register “D0”:

Use the EXCEL macro and DDE POKE command to describe as follows:

Chn = DDEInitiate("MelsecEthernet", "topic name")

DDEPoke Chn, "item name", Data_Reference

DDETerminate (Chn)

Note

- Chn indicates the return value of the INITIATE command.

- Data_Reference uses the ID of the cell written to with POKE.

- Use the TERMINATE command when done to close the channel.

- Delay the TERMINATE command by 10 minutes in order to ensure POKE is executed.

- For other access methods, refer to the sample program included with the product.

Configuration

- 65 -

5.6 DDE Access from Visual Basic 6.0 Paste text box control and label control to a form and configure DDE properties. Set LinkMode to “Automatic” to read

the value to the TEXT property.

Property Name Description Sample Setting

LinkTopic DDE application name + "|” + topic name MelsecEthernet|PLC1

LinkItem DDE item name D0

LinkMode DDE communication mode (0: none, 1: automatic link,

2: manual link)

1

Sample Code to Read Values from the PLC

Sample Code to Write Values to the PLC

Configuration

- 66 -

5.7 OPC Access from Visual Basic 6.0 Details of OPC access are clearly defined. Main steps are as follows:

1. Get OPC server list

2. Connect to OPC server

3. Generate Group Object (configure update interval)

4. Add tags

5. Read/write values

6. Disconnect

Details of OPC programming will not be covered in this document. For more details, please refer to the sample

program for OPC access that will be set up in “Install Folder¥Sample¥VbSampleOpc” when you install the product.

Important

An application developed using Visual Basic cannot explicitly specify Outprocess. It calls DAServer as

InProcServer. Therefore, you cannot use OPC connection when you connect from multiple OPC clients or use

DDE/SuiteLink connection on InTouch. Please use DDE connection in that case.

MELSEC Ethernet Unit Configuration

- 67 -

6. MELSEC Ethernet Unit Configuration This section describes the configuration on the PLC side. For details of each function, please refer to the PLC manual.

6.1 MELSEC-iQ-R Series Please use software “GX Works3” to make communication setting for the iQ-R Series.

6.1.1 Unit Parameter

Please set the IP address and the Subnet mask pattern etc.

For communication with DeviceXPlorer, set “Enable online change”and“Binary code” in Communication data code.

Important

In order to perform the setting of the port of RJ71EN71, must be added RJ71EN71 unit to “Module configuration” in

GX Works3.

6.1.2 Open Setting

For communication with DeviceXPlorer, please set the port where you can select the “Ethernet Device (General)” -

“SLMP connected Module" from “Unit List” of External Device configuration.

Important

When using the TCP protocol, it is recommended that you perform the survival checked using the KeepAlive

function.


- 68 -

6.2 MELSEC-Q Series MELSEC-Q Series Ethernet Unit does not have a hardware switch. Use software configuration (GX Developer).

6.2.1 Network Parameters -- General

Open GX Developer’s “Network Param” page, specify “Ethernet” for “Network Type,” and enter the network number,

group number, and station number.


- 69 -

6.2.2 Network Parameters -- Operations

Configure the basic operations of the Ethernet Unit here.

Set “Communication Data Code” to “Binary code,” and “Initial Timing” to “Always wait for OPEN.” Check “Enable

Write at RUN time,” and enter the IP address of the PLC in decimal value. When using TCP/IP, you should select

“KeepAlive” in “TCP Existing Confirmation Setting”.

Note

- If you do not check “Enable Write at RUN time,” you cannot write to the PLC from DAServer.

- “TCP Existing Control” is displayed with GX Developer after version 8.05F .

- KeepAlive function is valid for Ethernet Unit version, after upper 5 place of serial number is ‘05051’.


- 70 -

6.2.3 Network Parameters – Initial Setting

When using TCP/IP, configure the existence confirmation parameters appropriately. When the existence confirmation

parameters are not configured appropriately, re-establishing connection after a network error may be difficult or

impossible.

In the above example, existence confirmation is done three times every 5 seconds starting 10 seconds after the

communication stops.

6.2.4 Network Parameters – Open Setting

Configure the ports you wish to open. Configuration of this page is not required when you wish to use automatic open

UDP port (default 5000) only.

In the above example, port 1 is defined as TCP/IP, and port 2 as UDP/IP.

Important

-For open setting, “Fixed Buffer Communication Procedure” must be set to “Procedure Exists.”

-”Local Port Number” and “Destination Port Number” must be entered in hexadecimal.

-When using UDP, broadcast becomes available by setting the “Destination IP Address” to ”255.255.255.255” and

“Destination Port Number” to ”FFFF.”


- 71 -

6.3 MELSEC-QnA/A Series MELSEC-QnA/A Series Ethernet Unit requires configuration of the hardware switch and initialization program.

6.3.1 Mode Selection Switch (MODE)

Set the Mode Selection Switch (rotary switch “MODE”) to online “0.”

6.3.2 Communication Configuration Switches (SW1~SW8)

Contect

SW1(SW1)

SW2(SW2)

SW3(----)

SW4(----)

SW5(----)

SW6(----)

SW7(SW3)

SW8(SW4)

Process way for TCP

time out error.

Set data code (for divide

from other node)

N/A

Description

OFF

ON

Close when time out error happens

Default

No close when time out error happens

Select communication handling on TCP time out error happens

OFF

ON

Binary

Ascii

Select data code for communication to other node

N/A

Set CPU Communication

timing (allow or not to

write in when CPU is

running)

OFF

ON

Not allow

Allow

Select to allow writing in from other node when PLC is running

Set initial timing

(Initial process timing)OFF

ON

Quick start (Start immediately)

Normal start (Start with 20 seconds late)

Select Initial process timing

OFF

OFF

OFF

OFF

OFF

OFF

OFF

OFF

* Switch numbers in parentheses indicate switch numbers for discontinued A1SJ71E71-B2/B5-S3.

* Use data code setting (SW2) in binary code (OFF).

* Use CPU communication timing (SW7) with “allow writing from other node when PLC is running” (ON).

* Units without a DIP switch on the front panel (such as A1SJ71E71N-T) have the DIP switch on the board.

* For more details, please refer to the Ethernet Unit manual.


- 72 -

6.3.3 Network Parameters

You can configure the IP address for QnA Series from the “Network Parameters” page of GX-Developer. When you use

Automatic port (default 5000), you can configure the communication without a program. Describe the initial process

and port control process in a ladder program when you wish to use anything other than automatic open UDP port

(default 5000).


- 73 -

6.3.4 Initial Processing

You need the initial processing program in order to use QnA Series/A Series Ethernet Unit. The initial processing

program handles IP address configuration and initialization request, for example. Generally, it handles a series of

processes from setting the IP address of the PLC to buffer memory and turning on the initial request flag (Yxxx) to

when initial complete flag (Xxxx) turns on.

Ethernet Unit I/O Signal

X0 Con. 1

Fixed buffer send receive completed normally Y0 Con.1 Send request/receive complete confirmation

X1 Fixed buffer send receive error detected Y1 Con.2 Send request/receive complete confirmation

X2 Con. 2



X4 Con. 3



X6 Con. 4



X8 Con. 5

Fixed buffer send receive completed normally Y8 Connection 1 open request

X9 Fixed buffer send receive error detected Y9 Connection 2 open request

XA Con. 6

Fixed buffer send receive completed normally YA Connection 3 open request

XB Fixed buffer send receive error detected YB Connection 4 open request

XC Con. 7

Fixed buffer send receive completed normally YC Connection 5 open request

XD Fixed buffer send receive error detected YD Connection 6 open request

XE Con. 8

Fixed buffer send receive completed normally YE Connection 7 open request

XF Fixed buffer send receive error detected YF Connection 8 open request

X10 Connection 1 open completed normally Y10 (EEPROM read request)

X11 Connection 2 open completed normally Y11 (EEPROM write request)

X12 Connection 3 open completed normally Y12 ―――





X17 Connection 8 open completed normally Y17 COM.ERR off request

X18 Open error detected Y18 ―――

X19 Initial completed normally Y19 Initial request

X1A Initial error detected Y1A ―――

X1B ――― Y1B ―――

X1C COM.ERR on Y1C (Buffer memory channel switch)

X1D (EEPROM read completed) Y1D ―――

X1E (EEPROM write completed) Y1E ―――

X1F Watchdog timer error detected Y1F ―――

* Functions between parentheses indicate functions of either MELSEC-QnA Series or MELSEC-A Series.

* Refer to each PLC’s manual for more details on each item.


- 74 -

Ethernet Unit Buffer Memory Details

Item A Series QnA Series

Address Default Address Default

Local Ethernet Unit IP Address 0-1 0 0-1 0xC00001FE

Special Function Configuration 2 0 4 256

Timer Setting Time Unit 3 2000 --- ---

System Area 4-6 --- 2-3 ---

System Area --- --- 5-A ---

Target Unit Existence Confirmation Start Interval Timer Value 7 300 11 1200

Target Unit Existence Confirmation Interval Timer Value 8 5 12 20

Target Unit Existence Confirmation Number of Resends 9 3 13 3

TCP ULP Timeout Value A 15 B 60

TCP Zero Window Timeout Value B 5 C 20

TCP Resend Timer Value C 5 D 20

TCP Complete Timer Value D 10 E 40

IP Build Timer Value E 3 F 10

Response Monitoring Timer F 15 10 60

Automatic Open UDP Port Number --- --- 14 5000

System Area --- --- 15-1D ---

TCP Maximum Segment Split Send Configuration --- --- 1E 0x8000

* Buffer memory address is a hexadecimal value.

* Default value of buffer memory is a decimal value. Values with “0x” indicate hexadecimal values.

* Refer to each PLC’s manual for more details on each item.


- 75 -

6.3.5 Port Control Processing

You need a program that controls specific ports in order to use QnA Series/A Series Ethernet Unit. Generally, the

program configures the protocol (TCP/IP or UDP/IP) and port number and handles the port open/close processes. It

can communicate simultaneously with a maximum of 8 other nodes.

PLC Buffer Memory Details

Item A Series QnA Series

Address Default Address Default

Application

Configuration Area

Connection No.1 10 ０ 20 0

Connection No.2 11 0 21 0







Communication

Address

Configuration Area

Con.No.1

Local Port # 18 0 28 0

Other IP Address 19-1A 0 29-2A 0

Other Port # 1B 0 2B 0

Other ARP Functions 1C-1E 0xFFFFFFFF 2C-2E 0xFFFFFFFF

Con.No.2

Local Port # 1F- 0 2F 0

Other IP Address 20-21 0 30-31 0

Other Port # 22 0 32 0

Other ARPFunctions 23-25 0xFFFFFFFF 33-35 0xFFFFFFFF

Con.No.3




Other ARPFunctions 2A-2C 0xFFFFFFFF 3A-3C 0xFFFFFFFF

Con.No.4

Local Port # 2D 0 3D 0

Other IP Address 2E-2F 0 3E-3F 0



-

-

-

-

-

-

Con.No.8





Communication Instruction During STOP Area 1F0 0 67 0

* Buffer memory address is a hexadecimal value.

* Default value of buffer memory is a decimal value. Values with “0x” indicate hexadecimal values.


- 76 -

Application Configuration Area

Configure the communication protocol, execution of existence confirmation, etc. for each port in this area. Application

configuration area (1 word) has the following structure:

b15 b14 b13 b12 b11 b10 b9 b8 b7 b6 b5 b4 b3 b2 b1 b0

[6] 0 [5] [4] [3] 0 [2] [1]

[1] Fixed Buffer Application Configuration (bit 0)

This is the parameter used for the fixed buffer communication function of the PLC. Set this to “0”.

[2] Existence Confirmation Configuration (bit 1)

Set whether the Ethernet checks the other node if communication with the other node whose connection open process

has been completed does not occur for a specific period of time. Generally, this bit is set to “1” for TCP/IP

communication to execute existence confirmation and not for UDP/IP communication.

[3] Paring Open Configuration (bit 7)

This is the parameter used for the fixed buffer communication function of the PLC. Set this to “0”.

[4] Communication Protocol Configuration (bit 8)

Configure the communication protocol for each port. Set this to “0” for TCP/IP communication and “1” for UDP/IP

communication.

[5] Fixed Buffer Communication Configuration (bit 9)

Select “with procedure” or “without procedure” for the fixed buffer communication function of the PLC. Set it to “0

(with procedure)” when using DAServer. If you set it to “1 (without procedure),” DAServer cannot talk to the PLC.

[6] Open Method (bits 14-15)

Set them to “11 (full passive)” to communicate by specifying the other port and “10 (unpassive)” to communicate without

specifying the other port when using TCP/IP communication. Set them to “00” when using UDP/IP.

For example, if you wish to execute Existence Confirmation using TCP/IP unpassive communication, the application

configuration area will be “0x8002.” It will be “0x100” when using UDP/IP communication.

Communication Address Configuration Area

Set the port number that the PLC opens in “local port #,” IP address of the other PC in “other IP address,” and PC port

# of the PC you wish to communicate with in “other port #.” Set “other IP address” and “other port #” to “0” when using

TCP/IP unpassive communication. When using UDP/IP communication, you may specify the other PC’s IP address

and port # and enable a 1:1 communication as well as broadcast communication. In that case, set the IP Address to

“255.255.255.255” and port # to “0xFFFF.” Leave “Other ARP Functions” as default when using DAServer.

Communication Instruction During STOP Area

Set the bit that corresponds to the connection to “1” if you wish to continue the communication with DAserver even

when the CPU of the PLC is stopped.

b15 b14 b13 b12 b11 b10 b9 b8 b7 b6 b5 b4 b3 b2 b1 b0

- - - - - - - - [8] [7] [6] [5] [4] [3] [2] [1]

[1] ~[8]: Communication instruction during STOP for connections No. 1 through No. 8.


- 77 -

6.4 Sample Ladder Program (MELSEC-QnA Series) You need initial processing and port processing programs to use Ethernet with QnA Series. See below for a sample

program of when the Ethernet unit is installed in slot 0. For error processing of the Ethernet unit, refer to the manual

of the PLC.

Sample Program Overview

Item Protocol Local Port Other IP Address Other Port

Connection 1 UDP/IP 1025 255.255.255.255 0xFFFF

Connection 2 TCP/IP Unpassive 1026 N/A N/A

Connection 3 TCP/IP Full Passive 1027 192.168.0.1 1027

IP Address 192.168.0.2

Existence Confirmation Sends ICMP packets three times every 2 seconds after 14 seconds.

Unit Address Ethernet unit is installed in I/O address 0.

H/W Switch Setting SW1-OFF/ SW2-OFF/ SW3-OFF/ SW4-OFF/ SW5-OFF/ SW6-OFF/ SW7-ON/ SW8-OFF

Initial Processing Program

1. Set the local IP Address to “192.168.0.2.”

2. Set Existence Confirmation Start Interval timer to 14 seconds (7×2 seconds).

3. Set Existence Confirmation Interval Timer to 2 seconds (1×2 seconds).

4. Set Communication Instruction during STOP to “enabled” (0xFFFF) for all connections.

5. Turn on Initial Request signal (Y19).

6. After Initial Complete signal (X19) turns on, set the TCP/IP port to wait OPEN (M10/M20).

1

2

3

4

5

6


- 78 -

UDP/IP Open Processing

1. Set Connection 1 protocol to UDP/IP (0x100).

2. Set Local Port # of Connection 1 to “1025”.

3. Set Other IP Address to “0xFFFFFFFF” in order to enable broadcast communication.

4. Set Other Port # to “0xFFFF” in order to enable broadcast communication.

5. Turn ON Port OPEN Request (Y8).

Note

-UDP/IP does not require connection processing. Y8 reset circuit is not required. Port remains open.

-If you do not specify the other PC, set Other IP Address to “0xFFFFFFFF” and Other Port # to ”0xFFFF” in order to

enable broadcast communication.

1

2

4

5

3


- 79 -

TCP/IP Unpassive Open Processing

1. Set Connection 2 protocol to TCP/IP unpassive (0x8002).

2. Set “1026” to the local port of Connection 2.

3. Turn on Open Request (Y9) by default (this enables access from DAServer).

4. When Open Complete signal (X11) turns off, turn Open Request off once and repeat step [3] again after 0.5 seconds.

Note

Configure Existence Confirmation properly when using TCP/IP.

In order to return to wait OPEN state after the session is disconnected, make sure you wait a sufficient amount of

time before attempting again.

1

2

4

3


- 80 -

TCP/IP Full Passive Open Processing

1. Set Connection 3 protocol to TCP/IP full passive (0xC002).


3. Set “192.168.0.1” to Other IP of Connection 3.

4. Set “1027” to Other Port of Connection 3.



Note

Configure Existence Confirmation properly when using TCP/IP.

In order to return to wait OPEN state after the session is disconnected, make sure you wait a sufficient amount of

time before attempting.

When using TCP/IP full passive communication, the port used by Windows will be locked after the session is closed.

You may not be able to establish connection again for some time as a result.

1

2

3

4

5

6


- 81 -

6.5 Sample Ladder Program (MELSEC-A Series) See below for a sample program of when the Ethernet unit is installed in slot 0 of the A Series. For error processing of

the Ethernet unit, refer to the manual of the PLC.

Note

The only difference between MELSEC-A Series and MELSEC-QnA Series is the buffer memory address.

Sample Program Overview

Item Protocol Local Port Other IP Address Other Port

Connection 1 UDP/IP 1025 255.255.255.255 0xFFFF

Connection 2 TCP/IP Unpassive 1026 N/A N/A

Connection 3 TCP/IP Full Passive 1027 192.168.0.1 1027

IP Address 192.168.0.3

Existence Confirmation Sends ICMP packets three times every 2 seconds after 14 seconds.

Unit Address Ethernet unit is installed in I/O address 0.

H/W Switch Setting SW1-OFF/ SW2-OFF/ SW3-OFF/ SW4-OFF/ SW5-OFF/ SW6-OFF/ SW7-ON/ SW8-OFF

Initial Processing Program

1. Set the local IP Address to “192.168.0.3.”

2. Set Existence Confirmation Start Interval timer to 14 seconds (7×2 seconds).

3. Set Existence Confirmation Interval Timer to 2 seconds (1×2 seconds).

4. Set Communication Instruction during STOP to “enabled” (0xFFFF) for all connections.

5. Turn on Initial Request signal (Y19).

6. After Initial Complete signal (X19) turns on, set the TCP/IP port to wait OPEN (M10/M20).

1

2

3

4

5

6


- 82 -

UDP/IP Open Processing

1. Set Connection 1 protocol to UDP/IP (0x100).

2. Set Local Port # of Connection 1 to “1025”.

3. Set Other IP Address to “0xFFFFFFFF” in order to enable broadcast communication.

4. Set Other Port # to “0xFFFF” in order to enable broadcast communication.

5. Turn ON Port OPEN Request (Y8).

Note

-UDP/IP does not require connection processing. Y8 reset circuit is not required. Port remains open.

-If you do not specify the other PC, set Other IP Address to “0xFFFFFFFF” and Other Port # to ”0xFFFF” in order to

enable broadcast communication.

1

2

4

5

3


- 83 -

TCP/IP Unpassive Open Processing

1. Set Connection 2 protocol to TCP/IP unpassive (0x8002).




Note

-Configure Existence Confirmation properly when using TCP/IP.

-In order to return to wait OPEN state after the session is disconnected, make sure you wait a sufficient amount of

time before attempting again.

1

2

4

3


- 84 -

TCP/IP Full Passive Open Processing

1. Set Connection 3 protocol to TCP/IP full passive (0xC002).


3. Set “192.168.0.1” to Other IP of Connection 3.

4. Set “1027” to Other Port of Connection 3.



Note

-Configure Existence Confirmation properly when using TCP/IP.

-In order to return to wait OPEN state after the session is disconnected, make sure you wait a sufficient amount

of time before attempting.

-When using TCP/IP full passive communication, the port used by Windows will be locked after the session is closed.

You may not be able to establish connection again for some time as a result.

1

2

3

4

5

6

Troubleshooting

- 85 -

7. Troubleshooting This chapter describes troubleshooting of DAServer.

7.1 Version Information Version information of DAServer is output to SMC’s LogViewer at startup. You may also check the version

information as follows:

1. Find MelsecEthernet.dll under Install Folder from Explorer.

2. Right mouse click on the file name and select Properties.

3. Click on the Version tab in the dialog box.

4. DAServer version is displayed.

7.2 Connectivity with PLC The system tag, $SYS$Status, can be used to monitor the status of communications with the PLC. This item is set to 0

when communication with the PLC fails and to 1 when communication is successful.

Note

For DDE/SuiteLink clients, only one $SYS$Status exists per topic. For OPC clients, $SYS$Status can be accessed at

all hierarchy levels. $SYS$Status at the root level of the whole hierarchy tree is always “1.”

Enter the following DDE reference formula in the appropriate place in your client:

=MelsecEthernet|PLC1!$SYS$Status

MelsecEthernet: name of the DAServer application

PLC1: topic name defined by the DAServer manager

$SYS$Status: item name (system tag) that monitors the status of connectivity with the PLC

Note

If it cannot establish connectivity with the PLC, DAServer will retry the operation three times and goes into slow

polling mode.

7.3 WindowViewer (InTouch) Communication Status The InTouch WindowViewer supports a built-in topic name called IOStatus (formerly “DDEStatus” with InTouch7.x)

that can be used to monitor the status of I/O communication. For example, IOStatus is set to “0” when this I/O

communication is normal and to “1” when an error occurs.

The status of communications between the PLC and InTouch can be read into Excel by entering the following DDE

reference formula in a cell on a spreadsheet:

=View|DDEStatus!PLC1 or

=View|IOStatus!PLC1

View: InTouch application name

DDEStatus/IOStatus: topic name in which the status of communications between DAServer and InTouch is stored

PLC1: access name defined as the access destination in InTouch

*This is an example of when the access name to topic name “I/O Status” is defined as “PLC1” and Item Name (Boolean)

is defined as “PLC1” also.

Troubleshooting

- 86 -

7.4 Attention of TCP/IP communication When communication error, collision or cutting cable happened on TCP/IP, DAServer wait for the reply message for

configured time. After this time, it will be timeour error occured.DAServer will add to wait for number of times. On

communication is failed, DAServer close active connection and try to communicate again. At this time, MELSEC

should be LISN status. In case of configured ethernet parameter by ladder program, you should make re-connection

work. Also you must configure the 'Destination existence'.

(Sample configuration of ‘Destination existence’ on MELSEC network parameter)

The 'Destination existence' checks host computer via PING command when stopped communication. If not found,

MELSEC close the active port and wait new connection.

# In sample picture, MELSEC will start to check for each 5 seconds after 10 seconds on communication stopped.

# Default value of MELSEC-Q series is configured for each 10 seconds after 10 minutes on communication stopped.

This means that the communication can not return for 10 minutes.

# Recommend to use the Existing Procedure by KeepAlive function in MELSEC-Q Series. The function by PING sends

ICMP packet to the IP address, but by KeepAlive, it sends ACK packet to taraget port.

This means previous trouble depend on timing is not occured. For how to configure, please see Chapter 6.1 MELSEC-Q

Series Ethernet settings. The KeepAlive function is available for Ethernet unit which upper 5 digit of serial number is

after 05051 and functionally version ‘B’.

Troubleshooting

- 87 -

7.5 Error Messages

7.5.1 Application Messages

See below for a list of messages DAServer sends to SMC:

Message Starting MelsecEthernet DAServer Ver1.00.00 Build on Mar. 07, 2004

Description Displays the version information and other information when DAServer starts up.

Message Ethernet Information : Protocol=UDPIP Host=0.0.0.0(0) PLC= 192.168.0.1(5000)

Timeout=3000 Retry=3 Simulated=0

Description Displays the communication parameter information when the PLC is connected.

Message [PORT1]Target Information : CPUType=3 NetNo=0 PCNo=255 UnitIO=3FF UnitST=0

Description Displays the PLC setting when the PLC is connected.

Message [PORT1]Connection Success

Description Connection to the PLC was successful.

Message [PORT1]Connection Close

Description Connection to the PLC has been closed.

Message [PORT1]Connect Error (Winsock=10061)

Description

Connection to the PLC was unsuccessful. PORT indicates the port name, and Winsock indicates

the error code of Windows Sockets.

Message [PORT1]Response Timeout

Description Sent a request message to the PLC but it timed out.

Message Response Error(Code=4031h)

Description

Sent a request message to the PLC but received a response that includes an error code. CODE

indicates the error code returned from the PLC (refer to the manual of the PLC for more details

on error codes).

Message [PORT1]Send Error (Winsock=10054)

Description

Send message failed. PORT indicates the port name, and Winsock indicates the error code of

Windows Sockets.

Troubleshooting

- 88 -

Message [PORT1]Receive Error (Winsock=10054)

Description

Receive message failed. PORT indicates the port name, and Winsock indicates the error code of

Windows Sockets.

Message Board has data at command send time: (Size=1024)

Description

Cleared the receive queue because data remained in the queue at send time. Size indicates the

data size.

Message Over size message received(8193 bytes)

Description Received message is over size. Value between parentheses indicates the size of the message.

Message Invalid access range (TAG=D0.A500, MAX: 480<500)

Description

Access point is out of the access range. Value between parentheses indicates the maximum

access points < specified points.

Message Invalid bit item number (TAG=M1.A1). it must be a multiple of 16

Description Expanded bit item number must be a multiple of 16.

Message Invalid tagname(DD0)

Description Tagname string is invalid.

Message Invalid device number(D3FF)

Description Device number string is invalid. DeviceName between parentheses indicates the tagname.

Message Invalid block number string(ERF: 3)

Description Block number string is invalid. Name between parentheses indicates the tagname.

Message Invalid expanded string(D0.F)

Description Expanded string is invalid. Name between parentheses indicates the tagname.

Message Invalid format(Point=1025, Bit=0, Str=D0.A1025)

Description

Maximum number of points for access all exceeds 1024. Or specification of bit location is invalid.

Point indicates the access points, Bit indicates the bit location, and Str indicates the tagname.

Message Invalid poke operation to 'bit in word item'

Description You cannot write to “bit in word item” (expanded format: 0~:15).

Troubleshooting

- 89 -

7.5.2 Error Message Causes and Solutions

See below for a list of error messages and their possible causes and solutions.


Cause/Solution

During TCP/IP communication, connection is still open on the PLC or port is not specified on the

PLC (not in LISN state). Reset the PLC or configure the appropriate program/parameter.


Cause/Solution

Accessed an IP address that does not exist when TCP/IP communication is used. Check the

network devices such as HUB or configure the correct IP address.

Message Response Error (Code=FFFFFFFFh)

Cause/Solution

This may occur when the Ethernet unit data code is set to “ASCII code” communication. Set it

to “binary code” communication. This may also occur when the actual PLC type is different

from the configured PLC type.

Message Response Error (Code=4031h)

Cause/Solution

Specified a device name outside the PLC parameter range when using MELSEC-Q/QnA Series.

This error occurs when you specify “D30000” and “X2000” with default device setting, for

example. Enter the appropriate device name.

Message Response Error(Code=C051h)

Cause/Solution

Read or write address is outside the permitted range. This error occurs when you specify

MELSEC-QnA Series as MELSEC-Q Series and access “D0.A500,” for example. Select an

appropriate PLC type.


Cause/Solution

This occurs when you attempt to write to MELSEC-A Series when write when it is write

protected. Turn write permit on (communication status configuration switch 7 of the Ethernet

unit of the A Series).


Cause/Solution

Accessed an inappropriate MELSEC-A Series device. This occurs when you attempt to access

L2000 within the latch range, for example. Access latch relay/step relay as internal relay

M2000.

Troubleshooting

- 90 -


Cause/Solution

Accessed a device name outside the PLC parameter range repeatedly when using MELSEC-A

Series. This occurs when you specify “D6143” and “D6144” with default device setting, for

example. Specify an appropriate device name.


Cause/Solution

Accessed a device name outside the PLC parameter range repeatedly when using MELSEC-A

Series. Also, A Series Ethernet unit can only access the device range for MELSEC-AnA.

Therefore, this occurs when you specify “D6144” and “B1000” with default device setting, for

example. Specify an appropriate device name.

Message Response Error (Code=E1A0h)

Cause/Solution

You may have specified an unavailable port during a random access buffer communication. For

example, UDP automatic open port “5000” cannot be used for random access buffer

communication.

Message Response Error (Code=E151h)

Cause/Solution

You may have specified an unavailable port during a random access buffer communication.

Valid buffer memory address is 0~0x17FF.

Message [PORT1]Receive Error (Winsock=10054)

Cause/Solution

This may occur when the PLC disconnects the connection. For example, this may occur when

the power to PLC is turned off.

Message [PORT1]Response Timeout

Cause/Solution

Generally, this occurs when the cable is disconnected or the power to HUB is turned off. This

also occurs when the PLC has not opened the corresponding port for UDP/IP communication.

Check the network devices or specify an appropriate port number.

Troubleshooting

- 91 -

7.5.3 Frequently Asked Questions

See below for a list of frequently asked questions and corresponding answers.

Question I am developing a system using Q Series but cannot communicate at all. Ethernet parameters

seem to be fine.

Response

If the network parameter/open setting of GX Developer is set to “No Procedure,” DAServer

cannot access to it. Set it to “With Procedure.”

Question After some TCP/IP communication, I could no longer connect to the PLC unless I reset it.

Response

This error occurs frequently when a cable is unexpectedly disconnected. TCP connection

remains on the PLC. Change the protocol to UDP/IP, implement the heartbeat function, or set

the existence confirmation parameter of the PLC appropriately. With A Series, this may occur

when the ladder program for port open/close is inappropriate.

Question Does it support DHCP?

Response

It automatically recognizes the DHCP syste when only one adapter is used and the local IP

address is set to “0.0.0.0.”

Question Can you use port 5000 of MELSEC-Q Series without configuring the network parameters?

Response

Port 5000 is provided as a default “automatic open UDP port.” There is no need to configure the

network parameters.

Question Can you use multiple LAN adapters?

Response

If you allocate static IP addresses, you may enter the IP address for each adapter to recognize

them.

Question I can PING a PLC but cannot communicate with it.

Response

IP address is configured correctly, but the PLC has not set the port to wait open. Please take not

that port number of DAServer is in a decimal value, but the PLC (GX Developer) sets it in

hexadecimal.

Question Attempting a word access to a bit device (M100.H16, etc.) results in an error.

Response

For a successful word access (ASCII, HEX, etc.) to a bit device (M/B/X, etc.), the start device

number must be a multiple of 16. For example, you can access “M32.H3,” but accessing

“M30.A10” will cause an error.

Question I would like to back up DAServer. Where is the configuration file?

Response Back up “MelsecEthernet.aaCFG” which is in installed directory.

Troubleshooting

- 92 -

Question I got a wrong device number error. How can you tell which tag is causing the error?

Response

You can check the list of added tags from SMC’s diagnostics screen. Check the tags that are in

red.

Question Accessing “W1000” with A Series Ethernet Unit AJ71E71N results in an error.

Response

A Series Ethernet Unit can only access the device range of AnACPU. It cannot access beyond

B/W1000 and D6144.

Question Can you access the internal device of other stations on MELSECNET via the stations connected

to the Ethernet?

Response

Since transient transmission is supported, you can access any station on MELSECNET simply

by specifying the station number. However, since transient transmission interrupts the regular

cyclic transmission of MELSECNET, response will be slower. Refer to MELSECNET Reference

Manual for more details.

Question Is there a limit to the number of PLCs you can access?

Response

You can define as many as you want, as long as it is within the resource range. However, the

more destinations there are, the slower the communication rate.

Question Can you run DAServer as a Windows service program?

Response

You can configure the service startup from SMC’s DAServer manager. With a service program,

the program is already running even before you log in.

Question Does it support MELSEC multiple CPU system?

Response When you use multiple Q Series CPUs, you can use the Ethernet unit to access any of them.

Question How can you tell from the client if DAServer is communicating correctly?

Response

System Tag “$SYS$Status” is set to “1” during the communication and “0” when the

communication stops. You can monitor this tag to see if a communication error has occurred.

Question Can you import/export tags?

Response

You can import/export tags from the “Device Item” tab on the PLC Configuration screen of SMC’s

DAService manager.

Question When you access from InTouch by DDE, what will the application name be?

Response

Specify “MelsecEthernet” as the application name.

Prog. ID to connect by OPC will be “Takebishi.MelsecEthernet.1.”

Troubleshooting

- 93 -

Question I get an error when I connect from multiple OPC clients.

Response

DAServer runs as InProcServer by default when CoCreateInstance is called. When you connect

from multiple clients, it must be executed as OutProcServer. Configure service startup or

activate DAServer before you connect the clients. You can avoid this error by specifying

CLSCTX_LOCAL_SERVER as the third argument.

If you specify CLSCTX_ALL, DAServer will run as InProcServer, so you can only connect from

one client. In this case, you cannot activate DAServer from SMC ahead of time.

Troubleshooting

- 94 -

7.5.4 Winsock Error Codes

See below for a list of Window Sockets error codes. Refer to MSDN for more details.

Code Title Description

10035 WSAEWOULDBLOCK Nonblocking socket. Cannot complete connection.

10036 WSAEINPROGRESS Blocking operation is currently executing.

10038 WSAENOTSOCK Socket operation on nonsocket.

10039 WSAEDESTADDRREQ Destination address required.

10040 WSAEMSGSIZE Message too long.

10048 WSAEADDRINUSE Address already in use.

*This may occur when the local port is not set to “0.”

10049 WSAEADDRNOTAVAIL Cannot assign requested address.

*This may occur when the cable is disconnected.

10050 WSAENETDOWN Network is down. This error may be reported at any time if the Windows

Sockets implementation detects an underlying failure.

10051 WSAENETUNREACH Network is unreachable.

10052 WSAENETRESET Network dropped connection on reset.

10053 WSAECONNABORTED Software caused connection abort.

10054 WSAECONNRESET Connection reset by peer.

*This may occur when the PLC is reset or power is turned off.

10055 WSAENOBUFS No buffer space available.

10056 WSAEISCONN Socket is already connected.

10057 WSAENOTCONN Socket is not connected.

10058 WSAESHUTDOWN Cannot send after socket shutdown.

10060 WSAETIMEDOUT Connection timed out.

*This may occur when the Ethernet line or PLC program is inappropriate.

10061 WSAECONNREFUSED

Connection refused.

*This may occur when the connection remains on the PLC.

*Clear this error by restting the PLC CPU or turning open request signal off.

Troubleshooting

- 95 -

7.6 Diagnostics Functions You may use DAServer’s diagnostics functions to investigate communication problems and display diagnostics

messages. Refer to the DAServer Manager manual for more details on diagnostics.

7.6.1 LOG Flag

DAServer outputs information such as error messages to SMC’s LogViewer. LogViewer logs only the messages that

were specified by the LOG flag. In order to log communication errors and other information, check “DASTrace” of the

LOG flag.

Select “Log Flags” from the “Operation” menu while the LogViewer is displayed in order to configure the LOG flags.

Select “MelsecEthernet” from the tree view and set each flag displayed on the right pane. Other than the flags that

are checked by default, three flags described on the next page can be configured.

Troubleshooting

- 96 -

The following three LOG flags can be configured on DAServer.

LOG Flag Description

DASTrace Logs DAServer’s general information.

DASReceive Logs messages that DAServer received from the PLC.

DASSend Logs messages that DAServer sent to the PLC.

Note

It is recommended that DASTrace be always ON. Turn on DASReceive and DASSend only during errors, for

leaving them on regularly increases the data size.

When you turn on DASReceive/DASSend, the following messages will be dumped.

Troubleshooting

- 97 -

7.6.2 Diagnostics

When DAServer starts up, the following six diagnostics groups are displayed: Client Groups,” “Structure,”

“Transactions,” “Statistics,” “Message,” and “Device Groups.” Use these groups to diagnose registeration information

of DAServer tags and OPC access status, etc.

Troubleshooting

- 98 -

Client Groups

Client Groups diagnoses the client groups accessed from outside. You can monitor the number of items, number of

active tags, number of errors, group status, etc. on this screen.

You can also monitor information on each added tag, such as item name, value, quality flag, and timestamp. Device

with an error (such as device that is out of range) is displayed in red.

Troubleshooting

- 99 -

Structure

DAServer’s name space has several levels. You can check the hierarchy structure on the Structure screen. You can

also monitor the number of registered items, errors, and R/W attributes of each level.

On each level, a list of added tags is displayed. You can monitor the value, timestamp, quality, and number of

messages.

Troubleshooting

- 100 -

Transaction

You can monitor the transaction information on the Transaction screen. In the sample provided below, the

transactions occurred in the order of write request, read request, refresh request, and write request.

You can also see that the first transaction wrote a “1” in “TAG1.”

Troubleshooting

- 101 -

Statistics

DAServer’s general data is displayed on the Statistics screen. There is no subtree. You can check the server status,

DAS engine version, start time, current time, number of client groups, and errors from this screen.

Troubleshooting

- 102 -

Messages

Information on each message is displayed on the Messages screen. In the sample provided below, there are 5 items

registered to the first message, 1 item to the second, and an error occurred on the third message.

Item name, quality information, message ID, location, and other information registered to each message is displayed.

Troubleshooting

- 103 -

Device Groups

You can see the information on each device group, such as the update interval, quality flag, and message ID on the

Device Groups screen.

You can check such information as value, timestamp, quality flag, and message ID on this screen.

Addendum

- 104 -

8. Addendum

8.1 DDE Test Client (Visual Basic) The product includes a sample client program (Visual Basic) for DDE communication. Use it to check the

communication with DAServer or as a sample program.

Operation

Define DDE Topic Name on the DAServer manager.

1. Start “Takebishi.MelsecEthernet.1” on the DAServer manager.

2. Select AppName (application name) and TopicName (topic name) and press “Connect.” Select “MelsecEthernet” for

the application name, and enter the topic name defined on the DAServer manager.

3. Enter the tagname (device name) in Item Name and press “Request” to read the value. If you press “Auto Read,” it

reads the value regularly.

4. Enter a value in Data and press “Poke” to write the value to the PLC.

5. Select the device type if you wish to use ASCII and double word, for example, select the device number in Number,

access points in Points, and access type in Type to enable regular read, automatic read, and write.

6. Press “DisConnect” to disconnect from the server.

Addendum

- 105 -

Simultaneous access to multiple DAServers, topics, and items

Press “EXPAND” to display the expanded screen. You can access multiple servers and topics simultaneously on this

screen.

The operation is the same as the previous page.

1. Press “Connect/DisConnect” to connect or disconnect.

2. “Request” to read,” “AutoRead” to enable automatic read.

3. “Poke” to write.

Addendum

- 106 -

8.2 OPC Sample Program (Visual Basic) The product includes a sample client program (Visual Basic) for OPC communication. Use it to check the

communicationwith DAServer or as a sample program.

Operation

List of OPC servers that are installed on the PC are displayed. Select “Takebishi. MelsecEthernet.1” and press

“Connect” to display the tree structure on the right pane. Navigate through to the desired level (display of

“DeviceGroupName,” “Port Name” + “PLC Name”) by double-clicking.

1. Enter the tagname you wish to access (in the sample provided above, D0, D1…) and press “Add Group.”

2. Press “Auto READ” for automatic read, “Sync READ” for synchronous read, and “ASyncREAD” for asynchronous

read.

3. You can enter a value in Value next to the checked tagname and press “Sync WRITE” for synchronous write and

“Async WRITE” for asynchronous write.

4. Change the update rate of automatic read by entering a different update rate in “Update Rate” and pressing

“Change.”

5. Press “DisConnect” to disconnect from the server.

Addendum

- 107 -

8.3 OPC Test Client The product includes a sample client program for OPC communication. Use it to check the communication with

DAServer from the OPC custom interface. The source code of this client is not provided.

Select Server Screen

Add Item Screen

Operation

Click “Connect” on the server and select “Takebishi.MelsecEthernet.1” from the OPC server list. Select “Add Item” to

browse the information defined on DAServer. Select a hierarchy structure and add a tag. You can monitor the tags

on the screen and right mouse click to write and select other operations.

Addendum

- 108 -

8.4 User Support User support service is provided to registered users. Please contact User Support for any questions on DAServer

configuration and operation.

When you contact User Support, please have the following information ready:

- Product name, serial number (listed on the CD/user registration form)

- PLC CPU type, communication unit model

- Client software type (InTouch/ArchestrA), Version/SP

Note

Please note that we may not be able to answer non-DAServer questions, such as hardware and device driver

configuration, sample program (sequence program, Visual Basic, EXCEL) codes and programming.

TAKEBISHI Corporation

User Support

29 Mamedacho Nishikyogoku Ukyoku Kyoto 615-8501, Japan

Phone: +81-75-325-2261 FAX +81-75-325-2273

Business Hours: 9:00 ~ 12:00 / 13:00 ~ 17:00 (Japanese Local Time Zone)

E-mail: [email protected]

Product Information: http://www.faweb.net/

mailto:[email protected]

10088-2D Jan.2017

MELSEC Ethernet DAServer

Users Guide

melsec ethernet daserver users guide - たけびしfaweb · pdf fileintroduction - 5 - 1....

Documents