Matrikon OPC Server for Modbus Devices User's Manual
Matrikon OPC Server for Modbus Devices Matrikon OPC Server for Modbus Devices - User's Manual For additional information on this manual, this OPC server, or Matrikon, please contact: Address: Matrikon 1800, 10405 Jasper Avenue Edmonton, Alberta, Canada T5J 3N4 Phone:
780-448-1010
Fax:
780-448-9191
Web:
http://www.matrikon.com
Sales:
[email protected] Support:
[email protected] CONFIDENTIAL The information contained herein is confidential and proprietary to Matrikon. It may not be disclosed or transferred, directly or indirectly, to any third party without the explicit written permission of Matrikon. All rights reserved. No part of this document may be reproduced, stored in a retrieval system, translated, or transmitted in any form or by any means, electronic, mechanical, photocopying, recording, or otherwise, without prior written permission of Matrikon. © Copyright 2001 Matrikon Inc.
Page 2 of 69
Matrikon OPC Server for Modbus Devices
TABLE OF CONTENTS 1.
Introduction .......................................................................................................................................................................................................................5 1.1
OPC Overview ...............................................................................................................................................................................................................5
1.2 2.
OPC Server Overview.........................................................................................................................................................................................6 Getting Started..................................................................................................................................................................................................................8
2.1
Installation .............................................................................................................................................................................................................8 2.1.1
Standard OPC Proxy/Stubs ......................................................................................................................................................................8
2.1.2
Standard OPC Server Browser...............................................................................................................................................................9
2.1.3
Matrikon OPC Common Components ................................................................................................................................................9
2.1.4
Matrikon OPC Explorer................................................................................................................................................................................9
2.1.5
Matrikon OPC Automation Component.............................................................................................................................................9
2.1.6
Installation Options...................................................................................................................................................................................10
2.2
Licensing................................................................................................................................................................................................................10
2.3
Command-Line....................................................................................................................................................................................................13
3.
Configuration ..................................................................................................................................................................................................................14 3.1
Starting Up ............................................................................................................................................................................................................14
3.2
Server Configuration ......................................................................................................................................................................................16
3.3
Alias Configuration..........................................................................................................................................................................................18
3.4
Save the Configuration.................................................................................................................................................................................34
3.5
DCOM Configuration.......................................................................................................................................................................................35
3.6
Statistics...............................................................................................................................................................................................................35
3.7
Options ...................................................................................................................................................................................................................35
3.7.1
General.............................................................................................................................................................................................................36
3.7.2
Logging.............................................................................................................................................................................................................36
3.7.3
Advanced ........................................................................................................................................................................................................38
3.8 4.
Shutting Down....................................................................................................................................................................................................38
Matrikon OPC Explorer...............................................................................................................................................................................................39 4.1
View Available OPC Servers .......................................................................................................................................................................39
4.2
Connect to an OPC Server............................................................................................................................................................................39
4.3
Add OPC Groups.................................................................................................................................................................................................40
4.4
Add OPC Items ....................................................................................................................................................................................................40
4.4.1
Item ID ...............................................................................................................................................................................................................41
4.4.2
Access Path....................................................................................................................................................................................................41
4.4.3
Browse the Server Address Space ...................................................................................................................................................41
4.4.4
Requested Data Type............................................................................................................................................................................... 42
4.4.5
Active State.................................................................................................................................................................................................... 42
4.4.6
Validate the OPC Items ........................................................................................................................................................................... 42
4.5
Read Real-time Values ................................................................................................................................................................................. 42
4.5.1
Update Rate ................................................................................................................................................................................................... 42
4.5.2
Active State.................................................................................................................................................................................................... 42
4.5.3
Data Display .................................................................................................................................................................................................. 42
4.5.4
I/O Method......................................................................................................................................................................................................43
4.5.5
Time Bias ........................................................................................................................................................................................................43
Page 3 of 69
Matrikon OPC Server for Modbus Devices 4.5.6
Dead-band...................................................................................................................................................................................................... 44
4.5.7
Advise Log....................................................................................................................................................................................................... 44
4.6
Write Control Values...................................................................................................................................................................................... 44
4.7
Options ...................................................................................................................................................................................................................45 4.7.1
General.............................................................................................................................................................................................................45
4.7.2
Data Transfer................................................................................................................................................................................................45
4.7.3
Data Display ..................................................................................................................................................................................................45
4.7.4
COM ....................................................................................................................................................................................................................45
4.8
Save the Session ..............................................................................................................................................................................................45
5.
Matrikon OPC Automation Component ............................................................................................................................................................46
6.
Troubleshooting ............................................................................................................................................................................................................47
Appendix A - Distributed COM (DCOM) ..........................................................................................................................................................................49 A.1 DCOM Configuration Utility....................................................................................................................................................................................55 A.2 Default Properties......................................................................................................................................................................................................55 A.3 Security Permissions...............................................................................................................................................................................................56 A.4 Server Identity..............................................................................................................................................................................................................58 A.5 Default Protocols........................................................................................................................................................................................................58 A.6 Remote Program ID ...................................................................................................................................................................................................59 Appendix B - OPC Compliance...........................................................................................................................................................................................60 B.1 OPC Server Object .......................................................................................................................................................................................................60 B.2 OPC Group Object........................................................................................................................................................................................................60 B.3 Server Registration....................................................................................................................................................................................................61 Appendix C - OPC Quality Flags .........................................................................................................................................................................................62 Appendix D - VARIANT Data Types....................................................................................................................................................................................64 Appendix E - OPC I/O Methods............................................................................................................................................................................................65 E.1 Synchronous Versus Asynchronous I/O ........................................................................................................................................................65 E.2 Device Versus Cache Reads.................................................................................................................................................................................65 E.3 OPC DA 2.0 versus 1.0a Asynchronous I/O ....................................................................................................................................................66 Appendix F - Alias Configuration ......................................................................................................................................................................................67 F.1 Scaling Expressions....................................................................................................................................................................................................67 F.2 Configuration CSV Format......................................................................................................................................................................................68
Page 4 of 69
Matrikon OPC Server for Modbus Devices
1. INTRODUCTION The Matrikon OPC Server for Modbus PLCs is an OPC compliant server that enables data interchange between OPC clients and Modbus PLCs. The server provides read and write access to all basic PLC register types. As well, the server supports Concept style floating point analog registers. The following communication methods are currently supported: The Matrikon OPC Server for Modbus PLCs is an OPC compliant server that enables data interchange between OPC clients and Modbus compliant PLCs. Each read/write with the PLC is optimized to maximize throughput. This server includes support for: •
Modbus (using RS-232 Serial)
•
Modbus Plus using an SA-85 card
•
Modbus Ethernet (TCP/IP) using the Modicon NOE module
•
Modbus Master and Modbus Slave configurations
•
Modbus ASCII and Modbus RTU (binary) protocols
•
Terminal Server
•
Read and write access to all PLC register types
•
Concept style floating point analog registers
2. SYSTEM REQUIREMENTS This Matrikon OPC Server has the following minimum system requirements: •
Intel Pentium II 200MHz Processor
•
64 MB RAM
•
25 MB hard drive space
•
Microsoft Windows 98 or Microsoft Windows NT 4.0 Service Pack 5 (or higher) Page 5 of 69
Matrikon OPC Server for Modbus Devices The server has the following additional requirements: •
For Ethernet communication with Modbus devices: Windows-compatible Ethernet network card
•
For serial communication with Modbus devices: At least one free COM port (RS-232, RS485, etc)
•
For Modbus+ communication with Modbus devices: •
Schneider Automation SA85 card
•
Schneider Automation 32-bit NETLIB driver (catalog number SW-LNET-NT)
2.1 OPC OVERVIEW OLE for Process Control (OPC) was designed to bridge Windows based applications and process control hardware and software applications. It is an open standard that permits a consistent method of accessing field data from plant floor devices. This method remains the same regardless of the type and source of data. OPC servers provide a method for many different software packages to access data from a process control device, such as a PLC or DCS. Traditionally, any time a package needed access data from a device, a custom interface, or driver, had to be written. The purpose of OPC is to define a common interface that is written once and then reused by any business, SCADA, HMI, or custom software packages. Client Application
Client Application
Client Application
OPC Interface OPC Server
OPC Server
OPC Server
Device A
Device B
Device C
Once an OPC server is written for a particular device, it can be reused by any application that is able to act as an OPC client. OPC servers use Microsoft’s OLE technology (also known as the Component Object Model, or COM) to communicate with clients. COM technology permits a standard for real-time information exchange between software applications and process hardware to be defined.
2.2 OPC SERVER OVERVIEW This OPC server follows the requirements of the OPC specification to provide data access to an OPC client. This server implements OPC Data Access (DA) version 1.0a and 2.0 of the OPC custom interface.
Page 6 of 69
Matrikon OPC Server for Modbus Devices Also, the server is optimized for high performance and uses multithreaded technology to provide efficient response to client requests. This approach allows multiple clients to connect to and effectively use the resources of a server. This Matrikon OPC server requires very little configuration after installation. It manages its communication automatically, providing optimal device polling with no additional configuration required by the user. This provides a flexible and powerful method to access data that is still simple to manage. This OPC server (as all of Matrikon’s OPC servers) is guaranteed to be 100% compliant with the OPC DA 1.0a and 2.0 specification. In addition, since our applications are sold world wide, either by vendors or directly by Matrikon, we have developed a comprehensive set of standards and tools to ensure that our interfaces are: • Easy to use • Robust • Reliable • Efficient • Complete with error checking and recovery procedures The focus of Matrikon is to develop strong long-term relationships with our clients. To that extent we make it a priority to become familiar with both the business and technical requirements of all our clients. This enables us to provide innovative services and solutions to enhance the technology direction selected by our clients within the framework in place today. At Matrikon we aim to provide solutions to meet your requirements.
Page 7 of 69
Matrikon OPC Server for Modbus Devices
3. GETTING STARTED This section guides you through the process of setting up a Matrikon OPC Server for real-time data access. Please follow the instructions carefully to avoid problems.
3.1 INSTALLATION The installation program for a Matrikon OPC Server comes on either CD-ROM or 3½” floppy disks. Insert the media in the drive and choose Add/Remove Programs from the Control Panel. Click Install and follow the instructions from the Installation Wizard. The installation program copies all necessary files to the target computer, registers the various software components, and creates short-cut icons in the Start menu. 3.1.1
MATRIKON OPC SERVER FOR MODBUS DEVICES
In addition to the standard Matrikon OPC Server files, the Matrikon OPC Server for Modbus Devices installs the following files. These files are installed by default in the MATRIKON\OPC\MODBUS directory under the Program Files folder. Filename
Description
OPCMODBUS.EXE
Matrikon OPC Server for Modbus Devices Executable
PSTCFGMODICONLIB.OCX
Configuration Panels ActiveX Component
The version-independent program ID for the server is "Matrikon.OPC.Modbus". The versionspecific program ID for this version of the server is "Matrikon.OPC.Modbus.1". The Matrikon OPC Server for Modbus Devices uses a software key for licensing. Contact Matrikon at
[email protected] to obtain the registration code for this server. 3.1.2
STANDARD OPC PROXY/STUBS
In compliance with OPC standards, Matrikon OPC Servers install and register the official OPC proxy/stub DLL’s in the Windows NT SYSTEM32 directory. These files contain version information so that they avoid overwriting newer files with outdated ones. Filename
Description
OPCPROXY.DLL
OPC Data Access 2.0 and 1.0a Interfaces Marshalling Library
OPCCOMN_PS.DLL
OPC Common 1.0 Interfaces Marshalling Library
OPC_AEPS.DLL
OPC Alarms and Events 1.0 Interfaces Marshalling Library
Note
Vendors were originally required to supply their own version of the OPC proxy/stub. Unfortunately, this proved to cause conflicts between various versions of the DLL’s when products from different vendors were installed on the same machine. To solve this problem, the OPC Foundation created official DLLs and they now require that all vendors install these instead. However, older OPC server installation programs may still install the old DLLs, preventing new servers from functioning properly. If this Page 8 of 69
Matrikon OPC Server for Modbus Devices occurs, simply run a newer installation again to ensure that the official DLLs are installed.
3.1.3
STANDARD OPC SERVER BROWSER
In compliance with OPC standards, Matrikon OPC Servers install and register the official OPC Server Browser in the Windows NT SYSTEM32 directory. This file contains version information to avoid overwriting a newer file with an outdated one. The installation program also ensures that the ActiveX Interface Marshalling Library is on the target machine so that the server functions properly. Filename
Description
ACTXPRXY.DLL
ActiveX Interface Marshalling Library
OPCENUM.EXE
OPC Server Browser
3.1.4
MATRIKON OPC COMMON COMPONENTS
Matrikon OPC Servers require the following files to function properly. These files are installed by default in the MATRIKON\OPC\COMMON directory under the Program Files folder (except for EXPREVAL.DLL, which is installed in the SYSTEM32 directory). Filename
Description
PSTCFG.EXE
Matrikon OPC Server Configuration Client
PSTCFGPS.DLL
Matrikon OPC Server Configuration Marshalling Library
OEM_Matrikon_OPC.DLL
Matrikon OPC OEM Badge Library
EXPREVAL.DLL
Expression Evaluation Library (for aliases)
3.1.5
MATRIKON OPC EXPLORER
Matrikon OPC Explorer is a general-purpose OPC client that is useful for testing the capabilities of any OPC server. The file is installed by default in the MATRIKON\OPC\COMMON directory under the Program Files folder. A shortcut icon for the program is added to the Start menu (in the common group). Filename
Description
OPCEXPLORER.EXE
Matrikon OPC Explorer (General-purpose OPC Client)
3.1.6
MATRIKON OPC AUTOMATION COMPONENT
The Matrikon OPC Automation Component enables developers to access OPC data from client applications developed using Automation tools such as Visual Basic, VBA, and VB Script. This component is installed by default in the MATRIKON\OPC\COMMON directory under Program Files. Filename
Description Page 9 of 69
Matrikon OPC Server for Modbus Devices OPCDAAUTO.DLL 3.1.7
Matrikon OPC Automation Component
INSTALLATION OPTIONS
Just before the installation program finishes, it offers two additional options. One option specifies whether the server should be installed as an NT service instead of a local executable. The other option provides a means to restore the older “ProcessX.OPC.Device” program ID to retain compatibility for clients that were coded to use earlier versions of the server.
3.2 LICENSING Most Matrikon OPC Servers require some form of license criteria to be met in order to function fully. Licensing for a particular server can use either a hardware key or a software key. Without an authorized license, most servers will run in ‘demo’ mode for a period of two hours or seven days, depending on the specific OPC server. 3.2.1
HARDWARE KEY LICENSING
For servers requiring hardware licensing, a HASP hardware key coded to the particular server can be purchased. This key must be securely fastened to the parallel port of the computer on which the server is installed. It does not interfere with hardware keys from other vendors, nor does it affect other normal parallel port applications, such as printing. If a server uses hardware licensing, then the installation program will install a device driver for HASP keys on the target system. When the server starts up, it will display a message box if it does not detect the correct key. It will then function for a demonstration period of two hours before “timing out”. At this point all device communication will cease. 3.2.2
SOFTWARE KEY LICENSING
Matrikon currently uses two different methods of software key licensing. The table below shows which OPC servers use each method OPC Server
Licensing
Allen Bradley DDE Modbus
10-digit licensing
Moore APACS Simatic TI5 Triconex Trident V2
Request/Authorization licensing
Page 10 of 69
Matrikon OPC Server for Modbus Devices 3.2.2.1 10-DIGIT LICENSING For servers using this software authorization method, a special ten-digit number is supplied when the server is purchased. This number must be entered in the Software Registration screen, available from the About box for the server (see the section on configuration for instructions on how to access the About box). The About box will include the words “UNREGISTERED COPY” if the number is missing or incorrect.
Page 11 of 69
Matrikon OPC Server for Modbus Devices 3.2.2.2 REQUEST/AUTHORIZATION LICENSING For servers using this software authorization method, a software license key is generated that is specific to the machine on which it is installed. The key is based upon a ‘request’ file that is generated during the installation process. You must send this request file to Matrikon for processing, and we return to you an ‘authorization’ file that is used to license the server. The following steps highlight this process. If you are installing an evaluation version only, refer to ‘When Evaluating” Steps’ section below: When Purchasing… 1. The installation program prompts you for contact information, plus a transaction number that you were provided by Matrikon after the purchase of the OPC server. 2. Based on the information provided by you, the installation program generates the license request file AuthorizeRequest.MTK in the folder where the OPC server is installed. 3. The installation program optionally allows you to create a temporary 7-day license that allows you to run the server in full function mode immediately, until the authorization file can be processed by Matrikon. If you do not select this option during installation, you can enable the 7-day authorization at a later time using the supplied Authorize.exe application. Refer to Step 6 for more information. 4. After installation, email AuthorizeRequest.MTK to
[email protected] or call our support desk and provide us with the details from this file. 5. Matrikon issues you the license authorization file Authorize.MTK by email, which you copy into the directory where the OPC server is installed. If you do not have email access, Matrikon can send you physical media or make the file available via FTP access. 6. Once you have the authorization file, run the supplied license authorization program Authorize.exe, which is located in the OPC server installation directory. The program will locate and read Authorize.MTK in the current directory, and license your server for operation. IMPORTANT: As noted in Step 3, if your run Authorize.exe before you have received and copied Authorize.MTK into the install directory, you will be allowed a one-time option to license the server for a 7 day period on the computer. When you later process Authorize.MTK, the 7 day license option is ‘renewed’ if it was used previously. This provides you with the ability to get your server running again in cases where a reinstallation is required, and the original authorization file has been lost or corrupted. 7. Make a backup copy of Authorize.MTK. NOTE: The preceding process is NOT required if you have a site license for your OPC server. In this case, the server will run immediately without any need for license authorization.
Page 12 of 69
Matrikon OPC Server for Modbus Devices 3.2.2.2.1 RE-INSTALLATION In cases where you need to re-install the OPC server on the same computer, follow these steps: 1. If you have not yet done so, make a backup copy of Authorize.MTK from the existing installation directory. See Step 6 if you do not have a backup copy of Authorize.MTK. 2. Uninstall the previous version, if possible. 3. Reinstall the software. 4. Copy the backed up version of Authorize.MTK into the new installation directory 5. Run Authorize.exe again and the server will licensed. 6. If you do not have a copy of Authorize.MTK available, and you need the server to be functional immediately, simply run Authorize.exe and select the temporary 7-day license option. Then contact Matrikon during regular business hours for another copy of Authorize.MTK. In cases where you need to re-install the OPC server on a different computer, follow the steps for an original installation, as noted previously in section 3.2.2.2.
3.3 COMMAND-LINE The installation program registers the Matrikon OPC Server to run as either a local executable or an NT service (based on user choices) and creates a shortcut in the Start menu. Use this shortcut to invoke the configuration utility, which will in turn start up the server. For reference purposes, the command-line parameters for the OPC server executable are as follows. Parameter
Description
/REGSERVER –REGSERVER
Registers the OPC server to run as a local executable (uninstalling the NT service if necessary).
/SERVICE –SERVICE
Registers the OPC server to run as an NT service. By default the service is set to run as the System account as an interactive process.
/UNREGSERVER –UNREGSERVER
Removes all registry entries for the OPC server (uninstalling the NT service if necessary).
(no parameters)
Starts up a copy of the OPC server as a local executable. It is preferable to start the server up from the configuration utility or another OPC client instead of from the command line.
Page 13 of 69
Matrikon OPC Server for Modbus Devices
4. CONFIGURATION Matrikon OPC Servers require a very small amount of configuration to function properly. This section describes how to create a configuration for your OPC Server using the supplied PSTCFG utility application. It begins with a generic discussion of using PSTCFG, and is followed by specific details on configuring devices supported by this OPC Server.
4.1 STARTING UP Choose the appropriate shortcut for the OPC server from the Start menu to invoke the PSTCFG configuration utility. By default, the shortcut has the name “Matrikon OPC Server for Device” and appears in “Matrikon OPC/Device” under the common section of the Programs folder. If the OPC server is not currently running, then it will launch when the configuration utility is started. If the server runs as a local executable, the splash screen is displayed and then a small red X appears in the Tool Tray at the right-hand side of the Task Bar. Right-click on the X to display the following menu.
Click “Show Control Panel” to display the control panel for the server. Double clicking on the X accomplishes this as well. The control panel displays general statistics for the server, such as the
number of clients currently connected. The control panel always stays on top of every other window on the desktop so that it can be used to monitor the server at all times. Double-click on the title bar to make the control panel “window shaded”. Click the X in the top right-hand corner to hide the control panel. Click “configure” from the control panel or the pop-up menu to display the main configuration window for the server. If the server runs as an NT service, the splash screen is not displayed, nor does the X appear in the Tool Tray. Instead, the main configuration window is displayed immediately. Click “about” from the control panel, pop-up menu, or Help menu in the main configuration window to display the About Box for the server. The About Box contains the server name and version number as well as other information about the software and Matrikon. It may also contain a link to a software registration screen for servers that use software licensing. The shortcut to the configuration utility has the following syntax for command-line options. Page 14 of 69
Matrikon OPC Server for Modbus Devices PSTCFG.EXE PSTCFGMatrikon.OPC.Device.# Matrikon.OPC
Note
The second parameter specifies which OPC server is to be configured. A mechanism in the utility prevents more than one copy of itself from connecting to the same OPC server.
The main configuration window displays a tree-view of objects configured in the server. Select an object to display its current configuration, which appears on the right-hand side of the window.
If the server runs as a local executable, it will remain running even after the main configuration window is closed, even if no clients are connected. Displaying the control panel or main configuration window for the server will “lock” it so that it will not shut down while configuration is being performed. If the server runs as an NT service, it will remain running so long as there are clients connected to it. Closing the main configuration window will shut down the configuration utility, but will not interfere with the normal operation of the server. Page 15 of 69
Matrikon OPC Server for Modbus Devices
4.2 SERVER CONFIGURATION Select “Server Configuration” in the tree view and choose Define New… from the Edit menu. The Insert New Object dialog box appears. Choose the desired type of object from the list and click OK. Different objects may be available depending on which object is currently selected in the tree view.
Note
Once an object is selected, its configuration panel appears. Each type of configurable object has its own configuration panel allowing users to enter object-specific information. Change the configuration settings as desired and press OK to create the object.
Three fields are common to all types of object: Name, Description, and Enabled. The Name field specifies a unique name for the object. It is used later as part of any item ID’s that refer to data Page 16 of 69
Matrikon OPC Server for Modbus Devices items under this object. Object names are automatically converted to title case for display purposes. The Description field can contain up to 63 characters of text for reference purposes. The Enabled checkbox specifies whether or not communication should be enabled for an object. Normally it should be checked. It may be useful to disable certain objects, especially if the devices that they refer to are disconnected or malfunctioning, in order to improve the performance of communication with the other objects. Real-time values are not available from disabled objects. Once an object is created, select it in the tree view and change the settings in its configuration panel to alter its configuration. Click Apply to accept the changes, or Cancel to discard them. To remove an object, select it in the tree view and choose Delete from the Edit menu.
It may be useful to change the default settings for a new object to avoid repetitive work. Choose Defaults from the View menu in order to alter the default settings for available object types. Simply edit the settings in the various configuration panels and choose OK. The next time an object of a particular type is created, it will use these default settings for initial values.
Page 17 of 69
Matrikon OPC Server for Modbus Devices The upcoming section contains further information on the specific types of objects available for this OPC server, and how to configure them.
4.3 MODBUS ETHERNET DEVICE
Field
Description
Modbus Address
Specify the Modbus slave address number for the device. Valid addresses are 1 to 247.
ASCII Mode
Select to use the ASCII protocol instead of the RTU binary protocol.
Confirm Connection
Select to read register 0:00001 when connecting to confirm communication.
Host Name TCP/IP Address
Specify either the host name (from HOSTS file or DNS provider) or the IP address for the device.
Port Number
Specify the TCP/IP port number for the device. This is usually 502 for Modbus.
Timeout
Specify the time limit, in milliseconds, to wait for a response from the Page 18 of 69
Matrikon OPC Server for Modbus Devices device. Retries
Specify the additional number of times to re-send a message after failing to receive a response.
Delay
Specify the time, in seconds, to wait after a communication failure before attempting to re-establish a connection to the device.
Max Registers and Coil blocks per Transmission
The maximum number of Analog (register type 3 or 4) data points and Digital blocks (16 coils per block, type 0 or 1) that will be read from or written to in one Modbus data transmission.
Page 19 of 69
Matrikon OPC Server for Modbus Devices
4.4 MTL 8000 SERIAL DEVICE This object enables communication with an 8000-series device (serial communication) from Measurement Technology Limited. This device is a special case and uses its own variation of the Modbus protocol. Field
Description
Modbus Address
Specify the Modbus slave address number for the device. Valid addresses are 1 to 247.
Port
Computer COM port that you are connecting with.
ASCII/RTU
Select to use either the ASCII protocol or the RTU binary protocol
Timeout
Specify the time limit, in milliseconds, to wait for a response from the device.
Retries
Specify the additional number of times to re-send a message after failing to receive a response.
Delay
Specify the time, in seconds, to wait after a communication failure before attempting to re-establish a connection to the device.
Page 20 of 69
Matrikon OPC Server for Modbus Devices
4.5 MODBUS+
4.5.1
SA85 CARD
Field
Description
Card Number
Specify the SA85 card number (0, 1, 2, or 3).
Modbus+ Address
Specify the local Modbus+ address for the SA85 card.
Page 21 of 69
Matrikon OPC Server for Modbus Devices 4.5.2
MODBUS+ DEVICE
Field
Description
Modbus+ Routing
Specify the Modbus+ routing path for the device, excluding the local Modbus+ address. Select the checkboxes to expand the size of the routing path. The last number should indicate the address for the device at the end of the route.
Timeout
Specify the time limit, in milliseconds, to wait for a response from the device.
Retries
Specify the additional number of times to re-send a message after failing to receive a response.
Delay
Specify the time, in seconds, to wait after a communication failure before attempting to re-establish a connection to the device.
Page 22 of 69
Matrikon OPC Server for Modbus Devices
4.6 MODBUS SERIAL
4.6.1
SERIAL PORT
Field
Description
Port
Specify the serial COMM port.
Baud Rate
Regular serial communications baud rate
Data Bits
Regular serial communications data bits
Parity
Regular serial communications parity
Stop Bits
Regular serial communications stop bits
Timeout
Specify the time limit, in milliseconds, to wait for a response from a device.
Retries
Specify the additional number of times to re-send a message after failing to receive a response.
Delay
Specify the time, in seconds, to wait after a communication failure before attempting to re-establish a connection to a device.
Page 23 of 69
Matrikon OPC Server for Modbus Devices 4.6.2
SERIAL PORT (ADVANCED)
Field
Description
DSR Flow Control
Set data set ready flow control on or off
DSR Sensitivity
Set data ser ready sensitivity on or off
CTS Flow Control
Set clear to send flow control on or off
XON/XOFF Flow Control
Set XON/OFF flow control on or off
RTS Control
Disable or enable request to send
DTR Control
Disable or enable data terminal ready
RTS Rise Delay
Request to send rise delay
RTS Drop Delay
Request to send drop delay
Page 24 of 69
Matrikon OPC Server for Modbus Devices
4.6.3 4.6.4
MODBUS SERIAL DEVICE
Field
Description
Modbus Address
Specify the Modbus slave address number for the device. Valid addresses are 1 to 247. If Address is set to 0, writing to this PLC will cause a Modbus broadcast message to go out to all PLCs on the communications port, writing to all devices simultaneously.
ASCII Mode
Select to use the ASCII protocol instead of the RTU binary protocol.
Confirm Connection
Select to read register 0:00001 when connecting to confirm communication.
Retries
Specify the additional number of times to re-send a message after failing to receive a response.
Delay
Specify the time, in seconds, to wait after a communication failure before attempting to re-establish a connection to the device.
Max Registers and Coil blocks per Transmission
The maximum number of Analog (register type 3 or 4) data points and Digital blocks (16 coils per block, type 0 or 1) that will be read from or written to in one Modbus data transmission. Page 25 of 69
Matrikon OPC Server for Modbus Devices
Page 26 of 69
Matrikon OPC Server for Modbus Devices
4.7 MODBUS UDP
4.7.1
UDP PORT
Field
Description
Host Name TCP/IP Address
Host name or TCP/IP address of device to connect to.
Port Number
Port number of device to connect to.
Timeout
Specify the time limit, in milliseconds, to wait for a response from a device.
Retries
Specify the additional number of times to re-send a message after failing to receive a response.
Delay
Specify the time, in seconds, to wait after a communication failure before attempting to reestablish a connection to a device.
Page 27 of 69
Matrikon OPC Server for Modbus Devices
4.7.2
MODBUS UDP DEVICE
Field
Description
Modbus Address
Specify the Modbus slave address number for the device. Valid addresses are 1 to 247.
ASCII Mode
Select to use the ASCII protocol instead of the RTU binary protocol.
Confirm Connection
Select to read register 0:00001 when connecting to confirm communication.
Max Registers and Coil blocks per Transmission
The maximum number of Analog (register type 3 or 4) data points and Digital blocks (16 coils per block, type 0 or 1) that will be read from or written to in one Modbus data transmission.
Page 28 of 69
Matrikon OPC Server for Modbus Devices
Page 29 of 69
Matrikon OPC Server for Modbus Devices
4.7.3
MODBUS TCP/IP TERMINAL SERVER TCP/IP CONNECTION
Field
Description
Hostname or IP address
Choose one of these to specify the network location of the Terminal Server.
Port Number
Specify the TCP/IP port that the terminal server allows programs to connect to.
Port
Computer COM port that you are connecting with.
Reply Timeout
Specify the time limit, in milliseconds, to wait for a response from the device.
Page 30 of 69
Matrikon OPC Server for Modbus Devices
4.7.4
MODBUS TCP/IP TERMINAL SERVER PLC
Field
Description
Modbus address
The Modbus address of the PLC you are connecting to. Valid addresses are 1 to 247. If Address is set to 0, writing to this PLC will cause a Modbus broadcast message to go out to all PLCs on the communications port, writing to all devices simultaneously.
Retries
The number of times to retry a failed or garbled command before failing
Reconnect Delay
If disconnected from the RTU, how long to wait until a reconnection attempt is made.
Max Registers and Coil Blocks per Transmission
The maximum number of registers or coils read in bulk. Setting this to 0 will allow the program to choose the largest optimal number for TCP/IP terminal servers.
Page 31 of 69
Matrikon OPC Server for Modbus Devices
4.8 ALIAS CONFIGURATION Matrikon OPC Servers provide the ability to create user-defined aliases that can be used in place of regular OPC items. This is particularly useful when the item path for a given server is very complex or difficult to remember (i.e. "DEV0.98.76.5.4321=AI.CV"). Servers can also be configured so that client applications have access to configured aliases only, rather than every available item. You can also use Aliases to create ‘holding registers’ by leaving the Item Path value blank. In this case, the alias acts as a generic Read/Write variable for all clients connecting to the OPC server. When using the Alias in this matter, you must explicitly define the data type when you create the alias point, rather than using 'Default' data type, OR, define the data type when writing/read values from the Alias via an OPC client, rather than using the Default data type. To create an alias, select "Alias Configuration" in the tree view, choose Insert Alias Group from the Edit menu, and enter a name for the group. It is usually better to create aliases in groups rather than directly under the root. Select the newly created group and choose "Insert New Alias" from the Edit menu.
In the "Insert New Alias" dialog box, enter a name for the alias and the item path (item ID) for the OPC item that it references. Click the ellipsis button to browse for available item ID's on the server. Click Save to save the alias, or click "Save & Create New" to configure another one. Select the “Default to new” checkbox to make the “Save & Create New” button the default control when you press Enter, rather than Save. Double-click an existing alias or press Enter while it is selected to change its settings.
Page 32 of 69
Matrikon OPC Server for Modbus Devices
Additional options available when creating an alias are as follows. The Data Type drop-down box allows the user to specify a "canonical" data type for the alias. The OPC item value is coerced to this data type prior to being sent to the client. The Read-only checkbox prevents client applications from writing to this item. The Update Rate and "Poll when inactive" fields work together to ensure that data for the item is always received at a particular rate even if it is not being read by the client. Certain standard scaling formulas may also be applied to the alias. Click the button marked "Scaling >>" to display the scaling portion of the dialog box. Click the tab corresponding to the desired type of scaling and fill in the parameters as needed. Click "
