Scribd
Upload
52 views

Tech Note 912 - Using Alternate TCP Port Numbers With Modbus Ethernet DAServer

This document discusses configuring the Wonderware Modbus Ethernet DAServer (DASMBTCP) to use TCP ports other than the default port 502. It describes how to manually edit the DASMBTCP XML configuration file to set alternate port numbers for specific devices, as some devices do not allow setting the port number through the user interface. Testing confirms that connections then occur on the custom ports instead of 502.

Uploaded by

profilemail8
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
52 views

Tech Note 912 - Using Alternate TCP Port Numbers With Modbus Ethernet DAServer

This document discusses configuring the Wonderware Modbus Ethernet DAServer (DASMBTCP) to use TCP ports other than the default port 502. It describes how to manually edit the DASMBTCP XML configuration file to set alternate port numbers for specific devices, as some devices do not allow setting the port number through the user interface. Testing confirms that connections then occur on the custom ports instead of 502.

Uploaded by

profilemail8
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 11

Using Alternate TCP Port Numbers with Modbus Ethernet DAServer

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).

file:///C|/inetpub/wwwroot/t002725/t002725.htm[1/22/2013 1:29:53 PM]


Using Alternate TCP Port Numbers with Modbus Ethernet DAServer

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
file:///C|/inetpub/wwwroot/t002725/t002725.htm[1/22/2013 1:29:53 PM]
Using Alternate TCP Port Numbers with Modbus Ethernet DAServer
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.

file:///C|/inetpub/wwwroot/t002725/t002725.htm[1/22/2013 1:29:53 PM]


Using Alternate TCP Port Numbers with Modbus Ethernet DAServer

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.

file:///C|/inetpub/wwwroot/t002725/t002725.htm[1/22/2013 1:29:53 PM]


Using Alternate TCP Port Numbers with Modbus Ethernet DAServer

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).

file:///C|/inetpub/wwwroot/t002725/t002725.htm[1/22/2013 1:29:53 PM]


Using Alternate TCP Port Numbers with Modbus Ethernet DAServer

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.

file:///C|/inetpub/wwwroot/t002725/t002725.htm[1/22/2013 1:29:53 PM]


Using Alternate TCP Port Numbers with Modbus Ethernet DAServer

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).

file:///C|/inetpub/wwwroot/t002725/t002725.htm[1/22/2013 1:29:53 PM]


Using Alternate TCP Port Numbers with Modbus Ethernet DAServer

FIGuRE 9: UNmODIfIED TSXQuaNtum CONfIGuRatION VIEwED IN XML NOtEpaD

2. Right-click on the IP Address item and click Insert (Figure 10 below).

file:///C|/inetpub/wwwroot/t002725/t002725.htm[1/22/2013 1:29:53 PM]


Using Alternate TCP Port Numbers with Modbus Ethernet DAServer

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).

file:///C|/inetpub/wwwroot/t002725/t002725.htm[1/22/2013 1:29:53 PM]


Using Alternate TCP Port Numbers with Modbus Ethernet DAServer
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).

file:///C|/inetpub/wwwroot/t002725/t002725.htm[1/22/2013 1:29:53 PM]


Using Alternate TCP Port Numbers with Modbus Ethernet DAServer

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 [email protected].

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.

file:///C|/inetpub/wwwroot/t002725/t002725.htm[1/22/2013 1:29:53 PM]

You might also like