WH Dde
WH Dde
applicom®
5. Diagnostic Interface.....................................................................12
Communication requests.......................................................................................14
Communication optimization .................................................................................15
Item Watch View ...................................................................................................16
Exporting item syntaxes ........................................................................................18
Message View .......................................................................................................20
The DDE/SuiteLink WHDDE server is an application (“whdde.exe”) which can run in Windows
Windows environments:
Either as a conventional application (ordinary executable file),
Or as a Windows service.
The DDE/SuiteLink server can be used locally (from a client application located on the same
machine) or remotely (from a client application located on another machine connected by the
network). In the second case, if the client application uses the SuiteLink protocol, the client/server
connection will take place via TCP/IP sockets.
See also:
In the knowledge base
Use of the DDE/Suitelink server with InTouch®
The DDE/SuiteLink servers cannot cohabit simultaneously on the same computer with the
OPC server. However, the two DDE/SuiteLink servers can cohabit and be used
simultaneously by the same application.
To run the WHDDE server, some of the Factory Suite components must necessarily be present on
the machine:
These components are automatically installed with all the FactorySuite Software
(InTouch,...) or can be eventually installed in stand alone.
Otherwise, a message indicating that a DLL (commonui.dll) cannot be found will be
displayed when trying to start the server.
To make it easier to insert tag names in the supervision software, the WHDDE server proposes, via
its diagnostic interface, the display in tree structure of all available syntaxes.
Basic parameters
All the configuration required to use the DDE/SuiteLink WHDDE server is carried out from the
configuration console, in the configuration description view.
Caution: these parameters are generally taken into account when you boot the server. You must
therefore reboot it after making any modifications.
Menu Description
Starting WHDDE as This option allows you to use the DDE/SuiteLink server as Windows service. The
Windows Service server will start automatically when starting Windows, even before a user logs in.
When this option is validated, the “Starting a client service area” allows you, if
necessary, to synchronize the start-up of another Windows service, DDE/SuiteLink
client.
Caution: When starting WHDDE in service mode the icon representing the
presence of the server will not be displayed in the Windows task bar. Consequently,
you will not be able to obtain the server diagnostic view.
In addition, in the service set-up parameters, the box Authorize the service to
interact with the Desktop must never be enabled.
Initialization of applicom® If this option is validated, the DDE/SuiteLink server automatically triggers
boards before server start- initialization of the boards when starting up. This option is not available if the server
up is used as Windows service.
Starting a client application This option allows you to automatically trigger the start-up of a DDE/SuiteLink client
application when the server has finished its start-up.
This option is not available if the server is used as Windows service.
Starting a client service This option allows you to automatically trigger the start-up of a DDE/SuiteLink client
service when the server also used as service has finished its start-up. This option is
only available if the server is used as Windows service.
See also:
In the documentation:
Implementation: Global command of the File menu
The DDE protocol identifies a data item via a three-part address. The three parts are Application,
Topic and Item.
Application
Refers to the Windows program (server) which can access the data items. Here, the
Application part of the DDE address is “WHDDE”.
Topic
The DDE/SuiteLink WHDDE server uses a random name called topic as access path
to the variables. With the WHDDE server you must specify the topic name of the
targeted Control Logix device, as it was configured in the configuration console. Only
the topics referencing devices on Logix5000 messaging will be recognized by the
WHDDE server.
Item
Determines a data item within the specified topic. In this specific case you must
specify the item name, as defined within the Control Logix device configuration.
However, the topic contains the following parameter which you can modify:
“Optimize access to structure fields”
If this parameter is checked and an item representing a field of a structure whose size is
less than or equal to 488 bytes is requested by a client, the tag identifying the complete
structure will be placed in a transaction. Consequently, if any other item representing a
different field in this structure is added, no transaction modification will be necessary. If this
parameter is not checked, each field of the structure will be added in the transactions
independently.
Limitations
The product used with the Logix5000 controller does not support the following standard
functionalities:
The extensions _B (BCD format) and _S (Forcing in signed value)
Syntaxes Description
Device statuses
STATUS For each Topic, you can read a local write status (STATUS_WRITE), a local read status
STATUS_READ (STATUS_READ) and a status combining both (STATUS). They provide information
STATUS_WRITE about the access to the device. The Status values range from 0 to 65535.The main
statuses are given below.
For further information, please consult the protocol manuals in chapter “Function return
statuses”.
Normal values:
0: No error.
255: this is the initial value of the status items for a topic as long as no transaction
has been carried out with the board.
Number of advise faults
ADVISE_FAILED Used to access the number of advise faults which have occurred for a “Standard topic”,
i.e. the number of points refused by WHDDE because of bad syntax. This item is read
only.
Number of write errors
WRITE_ERROR Used to access the number of write errors which have occurred for a “Standard topic”.
This item is read only.
Number of read errors
READ_ERROR Used to access the number of read errors which have occurred for a “Standard topic”.
This item is read only.
To access the diagnostic interface, first select the option Authorize Display of the Server
Diagnostic in the Properties of the WHDDE Server (see cross-reference below). It is shown by
an icon in the Windows task bar upon start-up of WHDDE server.
Double-clicking on the icon displays the diagnostic environment. Right-clicking on the mouse brings
up a menu enabling the user:
to display the diagnostic window. Diagnostic menu
to close the WHDDE server. Exit menu
The diagnostic interface is only useful when debugging your application. It is very resource-hungry
to use. Consequently, it must not be activated during the operation phases. The diagnostic interface
can be used to:
create a file which contains information about the communication requests. This file can be
used by the application “DumpLogger.exe”
create a file which contains information about the communication optimization. This file can
be used by the application “DumpLogger.exe”
watch more closely the events occurring on an item
display information on the server execution.
By pressing the following button: , the file “dumpDDE.xml” is generated in the current
configuration directory. The application “DumpLogger.exe” starts and immediately loads the above
file.
This window display is static and is built when you click on the display button.
The right-hand side of the view shows information about the object selected in the left-hand
window. This information is not documented but can be used by technical support.
This view is divided into three areas. At the top left there is a browser to consult the accessible
data. The area at the bottom left shows the list of items to be monitored, and the right-hand area
displays the event messages affecting the items in the list.
To Watch an Item
• Select the item to be monitored in the browser
• Click and drag from the browser to the list below
• if necessary, complete the syntax (press F2 to rename) and click on the check box to select
the item
You can now no longer modify the items in active watch. However, you can add items to the list or
modify those which are not active.
Notes:
• You can if you wish simply click and drag between the items in the connection view and
the list of items to be watched.
• The list of items to be watched can be saved and restored.
Commands available
Watch - Find Finds a character string in the current window. The case is
unimportant.
Watch - Traces - Clear Deletes all messages in the message view.
Watch - Traces - Copy Copies the text selected in the message view to the
clipboard. It can therefore be easily pasted into any other
text file.
Watch - Start Starts the watch on all items selected in the list.
Watch - Item List - Add Adds the item selected in the tree to the list.
Watch - Item List - Delete Deletes the selected item from the list.
You can stop the message trace in the Windows by selecting the Diagnostic - Messages – Stop
command. Use the Restart command to resume the traces. These two commands act on all
message Windows at the same time. When stopping or resuming, a message is shown in each tab.
Caution: All messages between stopping and resuming are lost.
Use the Clear command to delete all messages in the visible tab. The messages of the other tabs
are not affected by this command.
Remark:
The Logger Parameters... command in the Diagnostic menu enables the user to save all
messages displayed in the view(s) in a “WHDDE.log” file located in the configuration directory.
Caution: these parameters are applied both to the “DDE.log” file and to the “Spy.log” file used to
save the item watch messages.