MELSEC Serial DAServer Users Guide - たけびしFAWEB · MELSEC Serial DAServer Users Guide ......
89
MELSEC Serial DAServer Users Guide Revision 2D Jan. 2017
Transcript of MELSEC Serial DAServer Users Guide - たけびしFAWEB · MELSEC Serial DAServer Users Guide ......
MELSEC Serial 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
(1) Takebishi Corporation makes no warranties concerning the product, unless stated in the warranty guidelines.
(2) 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
(1) 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.
(2) You may not copy the software for any reason other than backup.
(3) Store the CD (media) which contains the software safely.
(4) You may not reverse engineer, decompile, or disassemble the software.
(5) 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.
(6) 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
(1) ArchestrA and InTouch are trademarks of Wonderware Corporation.
(2) MELSEC and MELSECNET are trademarks of Mitsubishi Electric Corporation.
(3) Windows and EXCEL are trademarks of Microsoft Corporation.
(4) 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 .................................................................................................................................................................... 27
4.5.1 Not Specified .......................................................................................................................................................................... 28
4.5.2 Bit Position Read in Word Device (: 00 ~ : 15) ................................................................................................................. 28
4.5.3 32-bit Signed Integer (: D) ................................................................................................................................................... 28
4.5.4 16-bit BCD (: B) ..................................................................................................................................................................... 28
4.5.5 32-bit BCD (: C) ..................................................................................................................................................................... 28
4.5.6 Floating Point (: R) ............................................................................................................................................................... 28
4.5.7 16-bit Unsigned Integer (: U) .............................................................................................................................................. 28
4.5.8 Character String (: S) ........................................................................................................................................................... 29
4.5.9 Text Decimal (: A) .................................................................................................................................................................. 29
4.5.10 Text Hexadecimal (: H) ...................................................................................................................................................... 29
4.5.11 Batch File Write (.F) ........................................................................................................................................................... 29
4.6 System Tag .................................................................................................................................................................................... 30
4.6.1 Global System Tag ................................................................................................................................................................ 30
4.6.2 Device Specific System Tag................................................................................................................................................. 30
4.6.3 Device Group Specific System Tag .................................................................................................................................... 31
4.6.4 Redundant Device Specific System Tag ........................................................................................................................... 32
5. Configuration ...................................................................................................................................................................................... 33
5.1 Tutorial ........................................................................................................................................................................................... 33
5.2 DAServer Manager Configuration ........................................................................................................................................... 38
5.2.1 Global Parameters................................................................................................................................................................ 38
5.2.2 Adapter Configuraiton ......................................................................................................................................................... 40
5.2.3 PLC Configuration ............................................................................................................................................................... 42
5.2.4 Redundancy Configuration................................................................................................................................................. 46
5.3 DCOM Configuration ................................................................................................................................................................. 48
5.3.1 Overview................................................................................................................................................................................. 48
5.3.2 Procedure ............................................................................................................................................................................... 50
5.3.3 Notes on Windows XP/SP2 ................................................................................................................................................. 56
5.4 Access from InTouch .................................................................................................................................................................... 60
5.5 DDE Access from Microsoft EXCEL ........................................................................................................................................ 61
5.6 DDE Access from Visual Basic 6.0 ........................................................................................................................................... 62
5.7 OPC Access from Visual Basic 6.0 ............................................................................................................................................ 63
6. MELSEC Serial Communication Unit Configuration ............................................................................................................... 64
6.1 MELSEC-Q / L Series ................................................................................................................................................................. 64
6.1.1 I/O Assignment...................................................................................................................................................................... 64
6.1.2 I/O Communication Setting................................................................................................................................................ 64
6.2 MELSEC-QnA/A ......................................................................................................................................................................... 66
6.2.1 Mode Switch .......................................................................................................................................................................... 66
6.2.2 Station Number .................................................................................................................................................................... 66
6.2.3 Communication Switch (MELSEC- QnA) ....................................................................................................................... 66
6.2.4 Communication Switch (MELSEC- A)............................................................................................................................. 67
6.3 Pin Assign (9PIN and 25PIN Interface Diagram)................................................................................................................. 68
7. Troubleshooting .................................................................................................................................................................................. 69
7.1 Version Information..................................................................................................................................................................... 69
7.2 Connectivity with PLC ............................................................................................................................................................... 69
7.3 WindowViewer (InTouch) Communication Status ............................................................................................................... 69
7.4 Error Messages ............................................................................................................................................................................ 70
7.4.1 Application Messages ........................................................................................................................................................... 70
7.4.2 Error Message Causes and Solutions ............................................................................................................................... 72
7.4.3 Frequently Asked Questions .............................................................................................................................................. 73
7.5 Diagnostics Functions ................................................................................................................................................................. 75
7.5.1 LOG Flag ................................................................................................................................................................................ 75
7.5.2 Diagnostics ............................................................................................................................................................................. 77
8. Addendum ........................................................................................................................................................................................... 84
8.1 DDE Test Client (Visual Basic) ................................................................................................................................................. 84
8.2 OPC Sample Program (Visual Basic) ...................................................................................................................................... 86
8.3 OPC Test Client ............................................................................................................................................................................ 87
8.4 User Support................................................................................................................................................................................. 88
Introduction
- 5 -
1. Introduction This User’s Guide describes the functions and operation of MELSEC Serial 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 serial. 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 Serial 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
DAServer
Wonderware InTouch Microsoft VisualStudio
LOCAL PC REMOTE PC
Wonderware InTouch
Ethernet
MELSECNET
MELSEC-Q/QnA/A
Serial Line
- You can access the PLCs through Serial line from InTouch on a local PC or custom application (VC/VB). You
can access other stations on MELSECNET.
- 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-Q Series Q00(J)CPU, Q01CPU, Q02(H / PH)CPU,Q06(P)HCPU, Q12(P / PR)HCPU
Q25(P / PR)HCPU,Q172 / Q173CPU
Q02UCPU, Q03UD(E)CPU,Q04UD(E)HCPU, Q06UD(E)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(S)CPU-(P) , L26CPU-(BT)(PBT), L06CPU-(P)
MELSEC-QnA Series Q2A(S)(H)CPU(-S1), Q3ACPU, Q4A(R)CPU
MELSEC-A Series A0J2HCPU, A1(N/S/FX)(J)(H)CPU, A2(U/A)(N/S/C)( J)(H)CPU(-S1),
A3(U/A/N)CPU, A4UCPU
MELSEC-FX Series FX0NCPU,FX1(S)(N)(NC)CPU
FX2N(C)CPU,FX3(S)(G)(U)(GC)(UC)CPU
FX5U( C) CPU
Serial Units
MELSEC-Q Series QJ71C24(-R2/R4)
MELSEC-L Series LJ21C24(-R2)
MELSEC-QnA Series A(1S)J71QC24(N)(-R2/R4)
MELSEC-A Series A(1S)J71(U)C24(-R2/R4), A1CPUC24-R2, A2CCPUC24
MELSEC-FX Series FX0N-232ADP / 485ADP
FX1N-232BD / 485BD
FX2N(C)-232ADP / 485ADP
FX2N-232BD / 485BD
FX3U-232ADP(-MB) / 485ADP(-MB)
FX3U-232BD / 485BD
FX3G-232BD / 485BD
FX5U-232ADP / 485ADP
FX5U-232BD / 485BD
*The units listed above are existing PLC units. The system runs on some discontinued models.
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
MelsecSerial.exe Install Folder DAServer itself
MelsecSerial.dll Install Folder DAServer itself
MelsecSerial.pdf Install Folder Online manual
MelsecSerial.aaRUL Install Folder DAServerdefinition file
MelsecSerial.aaCFG Install Folder DAServer configuration file
CFG_TAKEBISHI_COM.dll Install Folder Dialog library
CFG_TAKEBISHI_C24.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
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
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 Serial 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 MelsecSerial
DDE Topic Name Arbitrary
OPC
Program ID Takebishi.MelsecSerial.1
Class ID B300E737-AFFA-4B8A-008B-66B7F34DB4BA
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 QnA-compatible 4C frame / A-compatible 1C frame
Communication Commands Batch Read / Batch Write / Random Write
Note
“Maximum number of adapters” and “maximum number of PLCs” indicate the maximum number that can be
defined on the software.
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.MelsecSerial.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 “MelsecSerial.”
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-Q Series 15360 960 7168 960 188 160
MELSEC-QnA Series 7680 480 3584 480 94 80
MELSEC-A/FX Series 256 64 160 64 20 10
Note
- "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.
- The maximum range of MELSEC-Q Serial Communication Unit is limited at 480 points.
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 Not FX Series
Y Output relay Hex Not FX Series
DX Direct input relay Hex Not A/FX Series
DY Direct output relay Hex Not A/FXSeries
B Link relay Hex
M Internal relay Dec
L Latch relay Dec Not A/FX Series (accessed as internal relay M)
S Step relay Dec Not A/FX Series (accessed as internal relay M)
F Annunciator Dec
V Edge relay Dec Not A/FX Series
TS Timer contact Dec
TC Timer coil Dec
SS Multiple timer contact Dec Not A/FX Series
SC Multiple timer coil Dec Not A/FX Series
CS Counter contact Dec
CC Counter coil Dec
SM Special relay Dec Not A/FX Series (ACCESSED AS M9000’S)
SB Special link relay Hex Not A/FX 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/FX Series
ER Expanded file register (block number
specified)
Dec Example: Accessing address 10,000 of block No. 10->
ER10:10000
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/FX Series
SD Special register Dec Not A/FX Series
SW Special link register Hex Not A/FX Series (accessed as D9000’s)
Z Index register Dec Not A/FX Series
BM Buffer memory Dec Not A/FX Series
Note
-Device range depends on your CPU.
-When using A Series, DX, DY, V, S, SS, SC, ZR, SB, SW, SM, SD, and Z are not accessible.
-FX series is not supported X and Y.
-Access range of Buffer memory (BM) is 0 ~ 8967.
Important
BM is not supported random poke function. Use “textDec” or “textHex” format for many poke action.
Specifications
- 27 -
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
value between 1 and 1023)
: Hxxx text Hex where “xxx” is the number of access points (numeric
value between 1 and 511)
: 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
- 28 -
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
- 29 -
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
"1024", 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 "1024",
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) 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
"Register R/W Points" 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
- 30 -
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
- 31 -
4.6.3 Device Group Specific System Tag
Item Type Attribute Description
$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
- 32 -
4.6.4 Redundant Device Specific System Tag
Item Type Attribute Description
$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
- 33 -
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. Installing the product
Run Setup.exe on the CD and install MELSEC Serial DAServer.
Important
You must have Administrator rights to install MELSEC Serial DAServer.
2. 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.MelsecSerial.1” (it should be under DAServer
Manager if it is installed correctly).
- DAServer exists under the Local node as “Takebishi.MelsecSerial.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.
Configuration
- 34 -
3. 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
- 35 -
4. 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 COM port number, parity, etc. here.
Configuration
- 36 -
5. 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, station address, etc. here.
6. 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
- 37 -
7. Activate DAServer
Before accessing from the client application, right mouse click on “Takebishi.MelsecSerial.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.
8. Auto Service
To run DAServer as a Windows service program, right mouse click on “Takebishi.MelsecSerial.1” and select
“Configure As Service” -> ”Auto Service.”
Configuration
- 38 -
5.2 DAServer Manager Configuration
5.2.1 Global Parameters
Click “Configuration” under “Takebishi.MelsecSerial.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
- 39 -
Item Default Value Description
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
- 40 -
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.MelsecSerial.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
- 41 -
Configurable Fields
Configure the Serial communication on the Adapter Configuration page.
Field Default Value Description
Com Port 1 Define COM port number communicating to PLC.
Baud Rate 19200 Define the baud rate.
Data Bit 8 Define the data bit.
Stop Bit 1 Define the stop bit.
Parity NONE Define the parity.
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.
Configuration
- 42 -
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
1. Right mouse click on any adapter and select “Add PLC Object” from the pop-up menu.
2. A default PLC called “New_PLC_000” is created. You can select an arbitrary PLC name.
3. Define multiple devices if you wish to access other stations via the connected PLC.
Configuration
- 43 -
Configurable Fields
Configure the CPU type, multiple CPU system, redundant CPU System and MELSECNET.
Item Default Value Description
PLC Type Q Series PLC type you wish to access (Q Series/QnA Series/A Series/FX Series)
MELSECNET
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
Serial connection station. Valid range is 0 ~ 255.
MELSECNET
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
Serial connection station. Valid range is 0 ~ 255.
CPU No
Multiple CPU NONE
CPU number when multiple CPU system is used.
Unit I/O No 1023
For the multi-drop link unit, the Unit I/O Number should be set to a value
between 0 and 511. When using multiple CPU system, choose the target
CPU unit by CheckBox or type the number at decimal. If not using multiple
CPU system, you must set to '1023'.
Unit ST No. 0
For the multidrop link unit, the Unit Station Number should be set to a
value between 0 and 31. For other types, the value should be set as 0.
Station No. 0
Each Serial Communication unit has a station address number which was
set by the user. Set the station number here (range 0-31).
Configuration
- 44 -
Item Default Value Description
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.
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.
Item Default Value Description
Name --- Define the topic name used for DDE/ SuiteLink communication.
Update Interval 1000 ms Define the update interval for DDE/ SuiteLink communication.
Configuration
- 45 -
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.
Item Default Value Description
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
- 46 -
5.2.4 Redundancy Configuration
This section describes how to configure the redundancy switching target PLC dynamically.
New Redundancy Configuration
1. Create some Adapter/PLC configurations
2. Right mouse click on any adapter and select “Add REDUNDANT_DEVICE Object” from the pop-up menu.
3. A default configuration called “New_REDUNDANT_DEVICE_000” is created. You can select an arbitrary name.
Configuration
- 47 -
Configurable Fields
Item Default Value Description
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
- 48 -
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
- 49 -
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
- 50 -
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
- 51 -
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
- 52 -
DAServer-specific Properties (General)
Right mouse click on ” B300E737-AFFA-4B8A-008B-66B7F34DB4BA” 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
- 53 -
DAServer-specific Properties (Location)
Select the “Location” tab.
*Check “Run application on this computer.”
Configuration
- 54 -
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
- 55 -
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
- 56 -
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
- 57 -
Exceptions
The application to pass the firewall can be specified in "Exceptions" tab. And push "Add Programs" button and add
"MelsecSerial.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
- 58 -
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
- 59 -
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
- 60 -
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 “MelsecSerial” 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
- 61 -
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("MelsecSerial", "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
- 62 -
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 MelsecSerial|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
- 63 -
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 Serial Communication Unit Configuration
- 64 -
6. MELSEC Serial Communication 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-Q / L Series MELSEC-Q/L Series Serial Communication Unit does not have a hardware switch.
Use software configuration tools (GX Works2).
6.1.1 I/O Assignment
Configure the serial communication unit as 32 points intelligent unit.
In the case of it is in first slot, "StartXY" will be "0."
6.1.2 I/O Communication Setting
(Sample: 19200bps, 8, 1, Parity:None, SumCheck, Station:0)
After setting "I/O assignment", you will configure the software switch for each intelligent unit.
For serial communication unit, the content of each switch is following as.
Switch1: CH1 Communication Rate Setting (Upper 8bytes) + CH1 Transmission Setting (Lower 8bytes)
Switch2: CH1 Communication Protocol Setting
Switch3: CH2 Communication Rate Setting (Upper 8bytes) + CH1 Transmission Setting (Lower 8bytes)
Switch4: CH2 Communication Protocol Setting
Switch5: Station Number Setting
Refer to MELSEC manual for each configuration detail.
MELSEC Serial Communication Unit Configuration
- 65 -
Communication Rate Setting (Switch1)
Bit Description OFF(0) ON(1) Remarks Example
b0 Operation Setting Independent Link Set to OFF on CH1 0
b1 Data Bit 7 8 1
b2 Parity Bit None Yes 0
b3 Even/Odd Parity Odd Even 0
b4 Stop Bit 1 2 0
b5 Sum Check None Yes 1
b6 Write during RUN Prohibited Allowed 1
b7 Setting Modifications Prohibited Allowed 1
2
E
Set Data Bit to “8” so DAServer communicate with binary code.
Transmission Setting (Switch1)
Baud Rate (bps) Value Baud Rate (bps) Value Example
300 00H 14400 06H
600 01H 19200 07H
1200 02H 28800 08H
2400 03H 38400 09H
4800 04H 57600 0AH
9600 05H 115200 0BH �
07 : 19200bps
Communication Protocol Setting (Switch2)
Value Description Remarks Example
0H GX Developer Connection Auto Communication Parameters
1H Format 1
2H Format 2
3H Format 3
4H Format 4
5H Format 5 Q Compatible Frame (BINARY)
6H Non Procedure Protocol
7H Bidirectional Protocol
8H For Linked Operation Setting
9H - DH Setting Prohibited
EH ROM/RAM/Switch Test
FH Individual Station Loopback Test
A Compatible Frame (ASCII)
�
5 : Binary
Station Number Setting
Set the station number within the range of "0" to "31" when connecting with multidrop link.
It should be “0” on 1:1 communication.
MELSEC Serial Communication Unit Configuration
- 66 -
6.2 MELSEC-QnA/A
6.2.1 Mode Switch
In order for the DAServer Software to communicate properly with the MELSEC-A/Q, the correct mode must be set. The
MELSEC-A series, uses protocol form 1. Refer to the chart below and choose the mode that corresponds to your
particular system configuration.
The MELSEC-QnA uses protocol form 5 (binary mode). The mode setting switch for the MELSEC-QnA should be at (5).
C o n n e t io n T y p e M O D E S e tt in g S w itc h
R S 2 3 2 C (1 :1 ) 1
R S 2 3 2 C -R S 4 2 2 /4 8 5 (1 :n ) A
R S 4 2 2 /4 8 5 5
M E L S E C -Q n A R S 2 3 2 C /4 2 2 /4 8 5 5
M E L S E C -A
6.2.2 Station Number
Set the station number on the PLC to a unique value in the range 0-31. This number will be used by the DAServer
Software as the Station Number in the Topic Definition when you configure the DAServer Software for communication
with the PLC.
6.2.3 Communication Switch (MELSEC- QnA)
S w itc h N o . IT E M
S W 0 1
S W 0 2
S W 0 9
S W 1 0
S W 1 1
S W 0 3
S W 0 4
S W 0 5
S W 0 6
S W 0 7
O p e r a t io n
D a ta B it
T r a n s m is s io n s p e e d
- - - -
P a r ity c h e c k
S to p B it
S U M C h e c k
W r ite D u r in g R U N
C h a n g e M o d e
O D D /E V E N P a r ity
S W 0 8
S W P o s it io n
O F F O N
9 6 0 0 1 9 2 0 0 2 8 8 0 0 1 1 5 K
O N
O F F
O N O F F
O N
O N
O F F
O F F
O N
O N O N
O F F
In d e p e n d e n t L in k e d
7 b it s 8 b it s
D is a b le d E n a b le d
O D D E V E N
1 b it 2 b it s
D is a b le d E n a b le d
D is a b le d E n a b le d
D is a b le d E n a b le d
O N
S W 0 1
S W 0 2
S W 0 3
S W 0 4
S W 0 5
S W 0 6
S W 0 7
S W 0 8
S W 0 9
S W 1 0
S W 1 1
S W 1 2 S W 1 2 O F F O F F O NO N
Set the Sum Check (SW06) to ON. Set the other switches to correspond to your hardware configuration.
Transmission Baud Rate(BPS) Setting
MELSEC Serial Communication Unit Configuration
- 67 -
6.2.4 Communication Switch (MELSEC- A)
S w itc h N o . IT E M
S W 1 1 (-- - - )
S W 1 2 (S W 0 8 )
S W 1 3 (S W 0 5 )
S W 1 4 (S W 0 6 )
S W 1 5 (S W 0 7 )
S W 1 6 (S W 0 9 )
S W 1 7 (S W 1 0 )
S W 1 8 (S W 1 1 )
S W 2 1 (S W 1 2 )
S W 2 2 (S W 0 4 )
M a in C h a n n e l
D a ta B it
T r a n s m is s io n s p e e d
- - - -
P a r ity c h e c k
S to p B it
S U M C h e c k
W r ite D u r in g R U N
M u ilt i d r o p /C o m p u te r L in k
O D D /E V E N P a r ity
M a s te r /L o c a l
S W 2 3 (-- - - )
S W 2 4 (-- - - )
S W P o s it io n
O F F O N
2 4 0 0 4 8 0 0 9 6 0 0 1 9 2 0 0
O F F
O N
O N O F F
O N
O N
O F F
O N
O F F
O F F O N
O N
R S 2 3 2 C R S 4 2 2 /4 8 5
7 b it s 8 b it s
D is a b le d E n a b le d
O D D E V E N
1 b it 2 b it s
D is a b le d E n a b le d
D is a b le d E n a b le d
M u lt iD r o p L in k C o m p u te r L in k
L o c a l M a s te r
O N
S W 1 1
S W 1 2
S W 1 3
S W 1 4
S W 1 5
S W 1 6
S W 1 7
S W 1 8
S W 2 1
S W 2 2
S W 2 3
S W 2 4
Set SW21 and set the SW23 to ON. You can establish connection with another PC with the DAServer Software using
these settings, also.
MELSEC Serial Communication Unit Configuration
- 68 -
6.3 Pin Assign (9PIN and 25PIN Interface Diagram)
< 9PIN (AnS/AnUS/QnAS/Q) >
CD
RD
SD
DTR
GND
DSR
RS
CS
1
2
3
4
5
6
7
8
Pin No.Signal
CD
RD
SD
DTR
GND
DSR
RS
CS
1
2
3
4
5
6
7
8
Pin No. Signal
PC PLC
< 25PIN (AnN/AnA/AnU/ QnA) >
CD
RD
SD
DTR
GND
DSR
RS
CS
1
2
3
4
5
6
7
8
FG
SD
RD
RS
CS
DSR
SG
CD
1
2
3
4
5
6
7
8
DTR20
Pin No.Signal Pin No. Signal
PC PLC
Note
It is possible to use the RS232C cross cable, but with MELSEC-A series serial communication unit, you must make
program that configured 'CD Terminal Check' to 1 (non-checked).
CD Terminal Check
UNIT Buffer Address 0 1 Default
MELSEC-A 10BH Check Non-Checked Check
MELSEC-QnA 97H(137H) Check Non-Checked Non-Checked
MELSEC-Q 97H(137H) Check Non-Checked Non-Checked
- The value in parentheses means the address of CH2.
- Be careful on MELSEC-A because CD Terminal Check is valid on default.
Troubleshooting
- 69 -
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 MelsecSerial.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:
=MelsecSerial|PLC1!$SYS$Status
MelsecSerial: 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. If timeout error occurs, DAServer immediately 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
- 70 -
7.4 Error Messages
7.4.1 Application Messages
See below for a list of messages DAServer sends to SMC:
Message Starting MelsecSerial DAServer Ver1.00.00 Build on Mar. 07, 2004
Description Displays the version information and other information when DAServer starts up.
Message Serial Information : COM=1 BaudRate=19200 Data=8 Stop=1 Parity=NONE Timeout=3000
Retry=3 Simulated=0
Description Displays the communication parameter information when the PLC is connected.
Message [PORT1]Target Information : CPUType=4 NetNo=0 PCNo=255 UnitIO=3FF UnitST=0 ST=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]Response Timeout
Description Sent a request message to the PLC but it timed out.
Message [PORT1]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 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.
Troubleshooting
- 71 -
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
- 72 -
7.4.2 Error Message Causes and Solutions
See below for a list of error messages and their possible causes and solutions.
Message [PORT1]Connect Error (ret=5)
Cause/Solution Specified COM port is already used by other application.
Message [PORT1]Connect Error (ret=2)
Cause/Solution Specified COM port does not exist. Check to valid COM port by using Device Manager.
Message [PORT1]Response Timeout
Cause/Solution
Generally, this occurs when the cable is disconnected or the power to PLC is turned off or invalid
configuration.
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=15h)
Cause/Solution
This occurs when poking to MELSEC-A without write permittion.
Set the switch "Write During RUN" (SW04 or SW22) of Serial Communication Unit to "Permit".
Message Response Error(Code=7167h)
Cause/Solution
This occurs when poking to MELSEC-Q/QnA without write permittion.
Set the software switch "Write During RUN" of Serial Communication Unit to "Permit".
Message Response Error(Code=7h)
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.
Message Response Error (Code=6h)
Cause/Solution
This occurs when accessing the device out of configured range to MELSEC-A.
For example, when you will access to 'D8192' on AnUCPU.
Troubleshooting
- 73 -
7.4.3 Frequently Asked Questions
See below for a list of frequently asked questions and corresponding answers.
Question Can not poke though I can read from PLC
Response
Check the configuration, "Write During RUN" of Serial Communication Unit is set to "Permit".
Also, check to not over written the value by PLC program.
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 “MelsecSerial.aaCFG” which is in installed directory.
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 Can I access the internal device of other stations on MELSECNET?
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 Maximum 62 PLCs.
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 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.
Troubleshooting
- 74 -
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 “MelsecSerial” as the application name.
Prog. ID to connect by OPC will be “Takebishi.MelsecSerial.1.”
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
- 75 -
7.5 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.5.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 “MelsecSerial” 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
- 76 -
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
- 77 -
7.5.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
- 78 -
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
- 79 -
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
- 80 -
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
- 81 -
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
- 82 -
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
- 83 -
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
- 84 -
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
1. Define DDE Topic Name on the DAServer manager.
2. Start “Takebishi.MelsecSerial.1” on the DAServer manager.
3. Select AppName (application name) and TopicName (topic name) and press “Connect.” Select “MelsecSerial” for the
application name, and enter the topic name defined on the DAServer manager.
4. 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.
5. Enter a value in Data and press “Poke” to write the value to the PLC.
6. 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.
7. Press “DisConnect” to disconnect from the server.
Addendum
- 85 -
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
- 86 -
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
1. List of OPC servers that are installed on the PC are displayed. Select “Takebishi. MelsecSerial.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.
2. Enter the tagname you wish to access (in the sample provided above, D0, D1…) and press “Add Group.”
3. Press “Auto READ” for automatic read, “Sync READ” for synchronous read, and “ASyncREAD” for asynchronous
read.
4. 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.
5. Change the update rate of automatic read by entering a different update rate in “Update Rate” and pressing
“Change.”
6. Press “DisConnect” to disconnect from the server.
Addendum
- 87 -
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.MelsecSerial.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
- 88 -
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/
10088-2D Jan.2017
MELSEC Serial DAServer
Users Guide
