Scribd
Upload
716 views

0048 Using WWClient To Check I - O Server Communication

The document describes how to use the WWClient utility to test communication between an I/O server and a PLC. It explains how to initiate a connection, advise of data changes, and poke values to test read and write functionality.

Uploaded by

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

0048 Using WWClient To Check I - O Server Communication

The document describes how to use the WWClient utility to test communication between an I/O server and a PLC. It explains how to initiate a connection, advise of data changes, and poke values to test read and write functionality.

Uploaded by

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

8/23/13

Using WWClient to Check I/O Server Communication

Tech Note 48

Using WWClient to Check I/O Server Communication


All Tech Notes and KBC D documents and software are provided "as is" without warranty of any kind. See the
Terms of Use for more information.
Topic#: 000411
C reated: March 14, 1997

Introduction
WWClient is a generic DDE-aware utility that is provided on Wonderwares Knowledge Base. This
utility allows you to quickly and easily test a Wonderware DDE I/O Server configuration.
(WWClient also provides scripting capabilities to automate the process.) This article shows how
you can use WWClient to test a Wonderware I/O Servers communications to a PLC device or to
troubleshoot a I/O Server by temporarily eliminating communications from specific client
applications, such as InTouch.
This article will show an example that uses the Wonderware Allen-Bradley Ethernet Direct I/O
Server (ABTCP) for Windows NT and the Allen Bradley PLC 5/20E. The Topic and Items names
shown here will vary depending on your I/O Server and PLC. (For information on how to configure
the ABTCP I/O Server, consult the Wonderware User Guide for the ABTCP I/O Server or see the
corresponding Knowledge Base articles on the ABTCP I/O Server.)

Overview of the WWClient Menus


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

After you install WWClient from the KBCD and start it up, you should see the following WWClient
window appear:

Under the DDE menu, WWClient gives you the following menu choices:
INITIATE

Connects to a I/O Server.

TERMINATE

Disconnects from a connected I/O Server.

ADVISE

Creates a DDE Hot Link to topic which will update when the data changes.

UNADVISE

Disconnects and closes an advised Hot Link.

https://wdnresource.wonderware.com/support/kbcd/html/1/using_ww.htm

1/5

8/23/13

Using WWClient to Check I/O Server Communication

REQUEST

Requests data from a topic only one time (that is, it will not receive any
further updated data).

POKE

Sends data to a I/O Server.

EXECUTE

Sends a command to a I/O Server.

Note that if you click the right mouse button anywhere in the WWClient window, it will also
display the same DDE functin menu options.

Installing WWClient
Go to the Knowledge Base WWClient topic to install the WWClient utility.

Testing the I/O Server With an Initiate/Advise


Follow these steps to test the I/O Server configuration which will use the WWClient Initiate and
Advise commands.
1. Start the WWClient utility. Select Initiate from the DDE menu, as shown here:

The Initate dialog box should appear:

https://wdnresource.wonderware.com/support/kbcd/html/1/using_ww.htm

2/5

8/23/13

Using WWClient to Check I/O Server Communication

2. Type the Application name of the I/O Server (example, abtcp for the ABTCP I/O Server)
and the configured Topic (example, abplc). Click the OK button.
Note If the I/O Server is on a remote computer, then you will need to include the
nodename of the remote computer in the Node listbox. Make sure that Wonderware
NetDDE is installed on both the remote node and the local node.
You should see the established initiated DDE conversation to the I/O Server appear in the
WWClient window as shown here:

If the DDE conversation to the I/O Server does not appear, then the attempted Initiate
failed. This is the same as InTouch issuing the error Could not Initiate DDE Conversation.
If WWClient failed to initiate a DDE conversation with the PLC, then you need to check the
following:
1. Verify that the I/O Server is running properly.
2. Verify that the I/O Servers name is spelled correctly in the Application listbox on the
Initiate dialog box.
3. Verify that the Topic name was create in the I/O Server or that the Topic name was
spelled correctly in the Topic listbox on the Initiate dialog box.
4. Once the DDE conversation has successfully initiated, select Advise from the
WWClient DDE menu. The Advise dialog box should appear.

Type the Item name that you wish to Advise (example, S:23 which is the real time in
seconds for the Allen Bradley PLC 5/20E). Click the Advise button, then the Done button.
You should see the Item updating in the WWClient window as shown here, which indicates
that the I/O Server is configured properly:
https://wdnresource.wonderware.com/support/kbcd/html/1/using_ww.htm

3/5

8/23/13

Using WWClient to Check I/O Server Communication

If you do not see the Item displayed in the WWClient window, then WWClient will display
an error stating that the Advise operation failed. You should then check the I/O Server
configuration, the PLC hardware, cabling, and so on.

Testing the I/O Server With a Poke


Follow these steps to see if WWClient can successfully Poke a value to an Item in the PLC.
1. Follow steps 1 and 2 in Testing the I/O Server With Initiate/Advise if you have not yet
performed an Initate command In WWClient to the I/O Server.
2. Select Poke from the WWClient DDE menu. The Poke dialog box should appear:

Type in the Item name to which you wish to Poke a value, along with the actual value.
Click the Poke button, then the Generate button, and then the Done button.
3. Confirm that the Poke command was successful by executing the PLCs programming
software and view the data tables in the PLC.
Or, create another Topic name in the I/O Server and reference the same Item that was
advised in Testing the I/O Server With Initiate/Advise through the newly created Topic
name. Then Poke the new Topic name.
For example, here are two different Topics that were Initiated, abplc and abplc2:

https://wdnresource.wonderware.com/support/kbcd/html/1/using_ww.htm

4/5

8/23/13

Using WWClient to Check I/O Server Communication

The first Topic, abplc, is advising the Item c5:0.pre which is the Allen-Bradley PLC 5
counter C5:0 preset value. Then, there is a Poke on this same Item by the second Topic
abplc1. By using this method, you can confirm that the Poke command successfully
changed the Item c5:0.pre without having to run the PLC programming software to find
out.
G.Tillery
The Tech Note is published occasionally by Wonderware Technical Support. Editors: Sabrina Abercromby and
Kelly Hauser; Publisher: Wonderware C orporation, 100 Technology Drive, Irvine C A 92618. There is also
technical information on our software products at Wonderware Technical Support, our WonderFax fax-ondemand system at (949) 450-5050, and the C omprehensive Support Knowledge Base.
For technical support questions, send an e-mail to [email protected].

back to top
2013 Wonderware C orporation. All rights reserved. Terms of Use.

https://wdnresource.wonderware.com/support/kbcd/html/1/using_ww.htm

5/5

You might also like