configuring abtcp daserver to communicate with ab plc5 using suitelink protocol

2/17/12 Configuring ABTCP DAServer to Communicate with AB PLC5 Using SuiteLink Protocol

1/8fa.sammicomputer.co.kr/TECH/html/t001083.htm

Tech Note 288

Configuring ABTCP DAServer to Communicate with AB PLC5Using SuiteLink Protocol

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

Topic#: 001083Created: November 2002

The Wonderware ABTCP DAServer allows Windows applications program such as InTouchapplication to access data in Allen-Bradley programmable controllers such as SLC-500 series,PLC-5, and PLC5/250 over the Ethernet network. You can use this server as a DDE, SuiteLink, orOPC server to communicate with Wonderware InTouch applications or Windows programs capableof being a DDE, FastDDE, Suitelink, or OPC client.

This technote shows how to configure and use Wonderware's ABTCP DAServer with the Allen-Bradley PLC5 using DDE / SuiteLink protocol. Before you continue, make sure you have thefollowing:

• Follow the instructions in the documents for proper installation procedures andsupported Operating systems. • Installed the latest version of the ABTCP DAServer. If a previous version was installed, be sure to uninstall it using Add/Removeprogram in the Control Panel. This technote is written using ABTCP DAServer version 1.0.• Installed and configured TCP/IP network protocol and the network interface card(NIC) so that it can communicate with the PLC via Ethernet using Winsock interface.• Properly configure your Allen-Bradley Processor communications so that you cancommunicate with the PLC via Ethernet.

Note -- This technote assumes the user has a basic working knowledge and understanding ofEthernet networking, Allen-Bradley PLC5 software/hardware, MicroSoft operating system,Wonderware FactorySuite components, WWCLient, and ABTCP DAServer.

Configuration Instructions

1. Determine the hierarchical structure of the network and PLC rack. The ABTCP DAServer starts at the TCPIP object, which is a logical representation of the Ethernet port for the Ethernet communication in the computer.

2. Start up the DAS Control Client from the task bar using Start / Programs / Wonderware /DAServer / Wonderware DAS Control Client. The DASControlClient window appears as in Figure 1.



FIGURE 1. DASCONTROLCLIENT

3. Expand LocalNode / ArchestrA.DASABTCP.1 / Configuration. It should now appear as in Figure 2.

FIGURE 2. GLOBAL PARAMETER

4. Right-Click Configuration and select Add Port_TCPIP Object as shown in Figure 3. A default name New_PORT_TCPIP_000 is assigned to the Ethernet port.



FIGURE 3: TCPIP PARAMETERS CONFIGURATION

From this branch of the hierarchy, the following objects can be created:

PLC5_TCPIP for PLC5/20E through PLC5/80ESLC500_TCPIP for SLC5/05 PLCPYRAMID_EI for Pyramid Integrator network

5. Since we will communicate with a PLC5/20E, right-click on the New_PORT_TCPIP_000 branchand select Add PLC5_TCPIP Object. On the New_PLC5_TCPIP_000 Parameters configurationview, enter either the PLC's host name OR IP address.

Figure 4 shows the TCPIP Parameters Configuration with the IP address for PLC5/20E configuredfor this technote. Click the Apply button to implement the changes. After all modifications aremade, you will be prompted to save the changes to the configuration set.

• Host Name: The Host Name OR IP Address of the PLC. The host name is defined in the hosts file which is used to resolve the PLC's hostname and IP address.• Data block Size: The number of date bytes can be sent in a messages. Valid range for PLC5 and the pyramid are from 2 to 2000. For SLC500 PLC is from 2to 510.• Connection Timeout: Time (in milliseconds) allowed to establish the connection tothe PLC. Valid range: 1000 - 20000 msec.• Reply Timeout: Time (in seconds) the ABTCP DAServer is to wait for theacknowledgement after sending out a message. The DAServer will resend the message when the timeout is done. Valid range: 1 to300 seconds.



FIGURE 4. TCPIP PARAMETERS CONFIGURATION

6. Now click on the Device Groups tab to create and configure device group definitions (alsoknown as topic definitions). Right-Click the area in the Device Group and use the context menuto add a new device group.

A default name (Topic_0) will be given to the new device group as shown in Figure 5 below. Youcan change it by clicking on the name (Topic_1) and enter a meaningful name (maximum 32-characters long.)

Click the Apply button to implement the changes. After all modifications are made, you will beprompted to save the changes to the configuration set.

Note -- You can change the Update Interval (in milliseconds) as your wish by double-clickingon the number and modifying it. The update interval can be changed to help reduce the traffic inyour network when you have multiple device groups in the list. If you want to configure the groupfor unsolicited messages, set the update interval to zero (0) millisecond.



FIGURE 5: DEVICE GROUPS CONFIGURATION

7. In the hierarchy tree on the left pane, right-click on ArchestrA.DASABTCP.1 and select theActivate Server in the context menu to start the DAServer. The icon next toArchestrA.DASABTCP.1 will change from red to green as shown in Figure 6.



FIGURE 6. ABTCP DASERVER STARTED

The ABTCP DAServer is ready for use. We are now going to do a quick communications test toverify that we can establish the connection to the PLC.

8. Click Start / Programs / Wonderware / Common / WWClient to start the WonderwareWWClient program. On the menu bar, select Connections / Create. The Create Connection dialog box will appear. Enter appropriate information as shown in Figure7 below, where:

• Node: is blank since the ABTCP DAServer and the WWClient are on the samecomputer. Otherwise, enter the computer name of the machine running the DAServer.• Application: DASABTCP which is the name of the ABTCP DAServer.• Topic: Topic_0 which is the exact name of the new device group we just createdin the DAServer.• Connection Type: IOT which is the SuiteLink protocol using for this technote.

FIGURE 7. WWCLIENT'S CREATE CONNECTION DIALOG BOX



9. Click Create, then Done. The WWClient window should now be similar to that in Figure 8:

FIGURE 8. WWCLIENT SHOWING CONNECTION WITH THE ABTCP DASERVER

10. Now, click on the Item on the menu bar. Enter a known good PLC register address, such asS:23 ( a built-in second timer for PLC5). Click the AdviseEX button to register and advise the item. If the Ethernet connection to the PLC is good, you should see the S:23 timer timing as shownin Figure 9 below:

FIGURE 9. WWCLIENT DISPLAYING PLC5'S TIMER S:23 VALUES

By Brian Nguyen

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 softwareproducts at www.wonderware.com/support/mmi

For technical support questions, send an e-mail to [email protected].

back to top

©2012 Invensys Systems, Inc. All rights reserved. No part of the material protected by this copyright may bereproduced 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 InvensysSystems, Inc. Terms of Use.

configuring abtcp daserver to communicate with ab plc5 using suitelink protocol

Documents