This Tech Note outlines configuring the Wonderware Modbus Ethernet DAServer (DASMBTCP) to use TCP Ports other than the default port number TCP 502.

Similar documents
Tech Note 715 Resolving Issues with DAServer Diagnostic Node on the Windows 2008 Operating System

Tech Note 784 Installing and Enabling the WebDAV Extension Module for Wonderware Information Server (WIS)

Introduction. Application Versions. Configuration Details. Tech Note 685 Using FSGateway to Communicate between Two Different Galaxies

Introduction. Application Versions. Utilization Control Buttons and Configuration Options

Tech Note 1010 SQL Server Authentication and ArchestrA Network Account Restrictions When Installing Wonderware Historian

Introduction. Application Versions. How Supply Chain Connector Works. Tech Note 959 Planning for Supply Chain Connector Import Efficiency

Tech Note 892 Configuring Microsoft SQL Server 2008 Express Server Authentication for Use with InTouch Alarm DB Logger

Introduction. Application Versions. Important. Tech Note 987 Configuring AppServer to Store Data in Primary and Partner Historians

Tech Note 1068 Moving Recipe Manager 2014 from a Standalone Configuration to the Domain

Tech Note 680 Configuring ActiveFactory for ArchestrA License Server Communication Across a Firewall

This Tech Note provides step-by-step procedures to install SQL Server 2008 Express on a 32-bit or 64-bit Operating System.

Introduction. Tech Note 941 Resetting a Non-Responsive Intermec CK61 Device. At times your Intermec CK61 handheld computer can become non-responsive.

Tech Note 920 Resolving Disabled ActiveFactory Reporting Website for Wonderware System Platform R2

Tech Note 868 Troubleshooting Wonderware Software Resource Issues with Performance Monitor

Network Setup for AppEngine Redundancy

Tech Note 812 Creating a Custom.NET Control in C# for Use in an Application Server Graphic

Tech Note 716 Viewing, Creating and Modifying Service Dependencies in Windows Server 2003

Introduction. Application Version. Overall Process Tasks. Import the System.Speech.dll

Tech Note 1006 Managing Symbol Script Timeouts When Using WW MES API Pop-up Dialogs

Tech Note 811 InTouch MultiMonitor Support on Windows Vista, Windows 7 and Windows 2008 Server

Tech Note 936 Troubleshooting and Resolving the Web access of Microsoft Reporting Services Reports application failed Issue

Introduction. Application Versions. Installation Overview. Preparation. Ensure IIS is Installed on the Default Drive

Tech Note 754 Solving Historian Client Report Publishing Problems on Windows 2008 O/S

This Tech Note explains resolving a known issue that occurs when the MES Database (MESDB) is moved to a different time zone.

Tech Note 937 Using the Wonderware Installation Wizard for Wonderware Industrial Computers

Tech Note 989 Historizing AppServer Objects to Partner Historians and Retrieving Data Using HistClient Trend

Tech Note 997 Setting up the InBatch 2012 R2 Batch Events Feature on a 2-Node System

Logix arrays are base-0, but UDA Array are base-1, so you will need to remember that there is an offset that will occur.

Tech Note 751 Installing InBatch Report Contents for Wonderware Information Server (WIS)

Tech Note 969 Port Configuration List for System Platform 2012 R2 Multi-Galaxy Environment

Tech Note 988 Wonderware System Platform 2014 AlarmMgr Support for InTouch and AppServer on Windows Vista and Later Operating Systems

Tech Note 962 Automating Object Configuration Tasks in the GRAccess Toolkit: Configuring UDA Array

Tech Note 726 Capturing a Memory Dump File Using the Microsoft Debug Diagnostic Tool (32bit)

Before You Get Started

Introduction. Application Versions. For the Customer Machine. Tech Note 919 Using the ProcDump Utility to Capture a Wonderware Process Dump

Introduction. Application Versions. Device Integration Objects. Tech Note 879 Redundant Device Integration Object Scan Mode Behaviors

Introduction. Tech Note 1051 Solving HTTP 404 Error for aaflexlicwebservice

Tech Note 448 Configuring the SST5136SD PCI Card Using the New SSTDHP I/O Server or the DASDHPlus Server

Wonderware Support has discovered a problem with some machines using IIS 7.x: There are some missing Handler Mappings to.net Framework 4.0.

Tech Note 908 Troubleshooting Wonderware Information Server (WIS) Part Eight: ActiveFactory Reports

Introduction. Application Versions. Issues. Symptoms

ICL Application Note No

All Tech Notes and KBCD documents and software are provided "as is" without warranty of any kind. See the Terms of Use for more information.

Tech Note 524 Resolving the "URL cannot be resolved or accessed or does not reference an XML document" Error in Wonderware Information Server

Introduction. Application Versions. Table of Contents. $PingNode Object Template Configuration

Application Versions. Functions List. GetAlarmLogConnStatus( ) Tech Note 506 Alarm DB Logger Status Functions

Introduction. Application Versions. Configuring DASABCIP. Tech Note 600 Using Online OPC Item Browsing in DASABCIP 4.0

Introduction. Application Versions. Real-World Examples and Scenarios

Introduction. Application Versions. Scenario 1: Importing All Dependent Files

All Tech Notes and KBCD documents and software are provided "as is" without warranty of any kind. See the Terms of Use for more information.

Introduction. Supported aatrendcontrol Class Methods and Properties. Tech Note 661 ActiveFactory 9.2 Undocumented.NET Methods and Properties

Wonderware ActiveFactory allows you to publish reports using Microsoft Excel, Word, and Trend to the ActiveFactory Reporting Website (AFRWS).

Introduction. Upgrading from Previous InTouch Versions. Upgrading from InTouch Version 7.11

Tech Note 1004 Accessing InBatch Materials Inside of System Platform using Material Automation Server (Object Hosted to Remote Node)

WWCdi Error 80040E14: Description 'Warning: The join order has been enforced because a local join hint is used'

Introduction. Tech Note 690 How to Hide the Public NameSpace and Tags in ActiveFactory v9.2

Introduction. Application Versions. Back Up the Runtime Database. Tech Note 817 Moving the Historian Runtime Database from One Machine to Another

Tech Note 710 Wonderware MES Operations Capability Object: Configuring Rolling Counter Reset

Tech Note 999 Wonderware Application Server Security Troubleshooting Essentials Part 2: Security Classification & Operational Permissions

This Tech Note shows how to use the URL parameters to control the Historian Client Trend user interface and behaviors in a browser window.

Tech Note 901 Configuring Smart Card Authentication for ArchestrA System Platform 2012

Tech Note 840 Configuring and Using Secured\Verified Write With the SignedWrite() Function

Introduction. HMI Reports Driver Overview. Application Versions. Creating a CSV/Text Data Access Client Driver

Introduction. Application Versions. AppEngine Automatically Fails Over on Reboot of One of the Redundant Pair. Issue. Resolution.

Tech Note 526 Automating Object Configuration Tasks Using GRAccess: Configuring the OPCClient DIObject

Introduction. Application Versions. Examples. Examples. Show/Hide Graphic. Tech Note 815 Using the ShowGraphic() Function with ArchestrA Graphics

All Tech Notes and KBCD documents and software are provided "as is" without warranty of any kind. See the Terms of Use for more information.

Tech Note 640 Troubleshooting Process Graphics Client Live Data Delivery in Wonderware Information Server (WIS)

Introduction. Application Versions. Tech Note 618 Restoring AFWeb Database Configuration to Publish Reports and Trends

Tech Note 905 Troubleshooting Wonderware Information Server (WIS) Part Six: ArchestrA Graphics No Live- Data

Tech Note 1007 Wonderware Application Server Scripting Implementations Part 1: Inserting a DB Row During Each Scan Cycle

Operator actions are initiated in visualization nodes, processed in dedicated server nodes, and propagated to other nodes requiring it.

Introduction. Tech Note 910 Using the MatrikonOPC Sniffer to Trace OPC Communication

Tech Note 1000 Wonderware Application Server Security Troubleshooting Essentials Part 3: Attribute Category

Tech Note 256 Using Network Application Development (NAD) with InTouch

All Tech Notes and KBCD documents and software are provided "as is" without warranty of any kind. See the Terms of Use for more information.

Introduction. Application Versions. OEE Requirements and Calculations. Tech Note 657 Wonderware Performance 3.5 Software: Performance Tips

Tech Note 528 Automating Object Configuration Tasks Using GRAccess: Creating and Configuring Field Attributes

Introduction. InTouch Files. General Files. Security Files. Tech Note 145 FactorySuite and ArchestrA InTouch Application File List

Wonderware Wonderware ArchestrA License Manager Guide

WW TSS-09 Advanced DAServer Troubleshooting

This Tech Note describes the procedure for manually uninstalling ArchestrA System Platform (ASP) 2012 and later products from a computer.

Wonderware DAServer for Omron FINS Ethernet User s Guide

Technical Information Sheet

Wonderware DAServer 1.0 for Mitsubishi Ethernet User s Guide

ArchestrA Log Flag Editor User s Guide Invensys Systems, Inc.

Wonderware DAServer 1.0 for Omron FINS Ethernet User s Guide

TOTAL Online. Setup Guide. Converting from Desktop to Online Edition. moneytree.com Toll free

Introduction. Application Versions. Virtual Machine Defined. Other Definitions. Tech Note 656 Building Wonderware Solution Architectures on VMware

Schneider Electric Software Knowledge & Support Center

Wonderware DAServer for Omron FINS Serial User s Guide

4D v12 Single User Upgrade Installation Manual

Remote ialarm Center. User s Manual

SyncLockStatus Evaluator s Guide Software Pursuits, Inc.

Object Viewer User s Guide

Wonderware. S7SIMATIC DAServer User s Guide. Invensys Systems, Inc. Version 3.0 Last Revision: 2/25/13

The SAS Workspace Servers can run on any platform that is supported by SAS 9.3.

Introduction. Application Versions. Virtual Machine Defined. Other Definitions. Tech Note 656 Building Wonderware Solution Architectures on VMware

file:///media/rhandsome/toshiba/wonderware/do... Wonderware InTouch HMI Version 10.1 Readme

Activant Eagle econnect Setup and User s Guide

Transcription:

Tech Note 912 Using Alternate TCP Port Numbers with Modbus Ethernet DAServer All Tech Notes, Tech Alerts and KBCD documents and software are provided "as is" without warranty of any kind. See the Terms of Use for more information. Topic#: 002725 Created: January 2013 Introduction This Tech Note outlines configuring the Wonderware Modbus Ethernet DAServer (DASMBTCP) to use TCP Ports other than the default port number TCP 502. Application Version DASMBTCP 1.5 SP1 or greater Configuring DASMBTCP Overview In order to demonstrate the capability of configuring alternate TCP ports in all of the possible configurations, we will create multiple device configurations within DASMBTCP via the Wonderware System Management Console (SMC). The first configuration item within the DASMBTCP structure is the TCPIP_Port object. The editor interface will only allow you to have one TCPIP_Port object within the DASMBTCP configuration (Figure 1 below).

FIGuRE 1: ADDING a TCPIP_PORt OBJEct The TCPIP_Port object is not editable, and is set to TCP Port number 502. This is the default TCP Port for all devices, unless there is a device-specific TCP Port number defined. Even if you change this directly in the DASMBTCP XML configuration file, there will be no impact on any devices. You must set a device-specific TCP port if you want the device to use a TCP port other than 502 (Figure 2 below). FIGuRE 2: TCPIP_PORt OBJEct FacEpLatE Configuring the Device In this example we created a TSXQuantum object (Figure 3 below). This configuration also applies to the TSXMomentum and TSXPremium objects. These devices do not have a UI configuration setting to allow for an override of the default TCP port number. You need to do this

manually in the DASMBTCP XML configuration file. A device Group called Topic_100 is created for this device. FIGuRE 3: TSXQuaNtum OBJEct FacEpLatE Next we create the ModbusPLC object (Figure 4 below). Note that the ModbusPLC object has a UI configuration setting to allow overriding the default TCP port number. To set the TCP Port number for this device, you simply type the Port Number in the Port number field. It is not shown, but a device Group called Topic_101 is created for this device.

FIGuRE 4: MODBusPLC OBJEct FacEpLatE Next we create the ModbusBridge object with ModbusPLCRS object (Figures 5 and 6 below). Note that the ModbusBridge object does not have a UI configuration setting to allow us to override the default TCP port number. You need to do this manually in the DASMBTCP XML configuration file. It is not shown, but a device Group called Topic_102 is created for this device. Since the TCP Port setting applies to the ModbusBridge object that contains the IP address, this example configuration also applies when using the Compact984, ModiconMicro, and TSXMomentumRS sub-objects under the ModbusBridge. This also means that each bridge can have a different TCP port configured.

FIGuRE 5: MODBusBRIDGE OBJEct FacEpLatE FIGuRE 6: MODBusPLCRS OBJEct FacEpLatE Now that we have a few devices configured, we can activate DASMBTCP and use WWClient to attempt to read from the devices (Figure 7 below).

FIGuRE 7: REaDING FROm EacH TOpIc If we run NETSTAT from a Command Prompt, we can see the three connections being attempted, all using TCP port 502 (Figure 8 below). Note that we did not have actual devices to connect to with these IP addresses, so the connection state does not show as Established in the screen capture. FIGuRE 8: NETSTAT REsuLts UsING DEfauLt TCP PORts Modifying TCP Port Settings Modifying the TCP Port settings requires completing the following tasks.

Configuration Information and Tools The DASMBTCP configuration file is in XML format and is stored in two possible locations (v2.0 and later). These may be hidden folders on your system, so you will first need to enable the option to show hidden file and folders. Configuration file locations Server 2003 and Windows XP: C:\Documents and Settings\All Users\Application Data\Wonderware\DAServer\DASMBTCP\DASMBTCP.aaCFG Server 2008, Windows 7, Windows Vista and newer: C:\Program Data\Wonderware\DAServer\DASMBTCP\DASMBTCP.aaCFG The easiest and safest way to work directly with the configuration file is to use an XML Editor like Microsoft XML Notepad 2007. Be sure that DASMBTCP is deactivated and the SMC is closed while you are modifying the configuration file. Override Device TCP Port Configuration 1. Open the configuration file with XML Notepad and navigate to the device object you want to modify. In this step, we will modify the TSXQuantum object (under the DeviceNode folder), but the steps are the same for all devices where the Port Number is not available with the SMC user interface (Figure 9 below).

FIGuRE 9: UNmODIfIED TSXQuaNtum CONfIGuRatION VIEwED IN XML NOtEpaD 2. Right-click on the IP Address item and click Insert (Figure 10 below).

FIGuRE 10: INsERtING A NEw XML ELEmENt 1. Name the new element PortNumber and type the value to the desired TCP Port number. In this case, we set it to 505 (Figure 11 below).

FIGuRE 11: SEttING TSXQuaNtum OBJEct's TCP PORt to 505 I also set the ModbusBridge object to TCP Port 506 using these same steps. Setting the port Number is done within the DeviceNode section of the configuration file that correlates to the ModbusBridge object's configuration. 3. Close XML Notepad and open the SMC. 4. Change the ModbusPLC object's TCP Port number to 510 using the User Interface and save the changes (Figure 12 below). FIGuRE 12: SEttING MODBusPLC OBJEct s TCP PORt to 510 5. Activate DASMBTCP, and attempt to read from the devices again using WWClient. Then run NETSTAT from a command prompt. You can now see that each device is using the ports that we specified (Figure 13 below).

FIGuRE 13: NETSTAT REsuLts UsING SpEcIfIED TCP PORts D. Scott Tech Notes are published occasionally by Wonderware Technical Support. Publisher: Invensys Systems, Inc., 26561 Rancho Parkway South, Lake Forest, CA 92630. There is also technical information on our software products at Wonderware Technical Support. For technical support questions, send an e-mail to wwsupport@invensys.com. Back to top 2013 Invensys Systems, Inc. All rights reserved. No part of the material protected by this copyright may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying, recording, broadcasting, or by anyinformation storage and retrieval system, without permission in writing from Invensys Systems, Inc. Terms of Use.