Specifications

A - 4 RSLinx – Training Guide
RSView32 connecting to RSView32:
1. Start the DDE server in RSView32. To do this check the DDE Server check
box in the RSView32 startup editor, or execute the command DDEServerOn.
2. Create a DDE node in RSView32 with the following information:
Application = \\computer_name\ndde$
Topic = RTDataProject_Name$
The RSView32 DDEshare is automatically configured as
RTDataProject_Name$ This DDEshare name must be used in the
RSView32 client topic configuration.
3. Set the RSView32 client tag address to the name of the tag on the
RSView32 Server.
EXCEL connecting to RSView32:
1. Start the DDE server in RSView32. To do this check the DDE Server check
box in the RSView32 startup editor, or execute the command DDEServerOn.
2. Client application name = '\\computer_name\ndde$'
3. The RSView32 DDEshare is automatically configured as
RTDataProject_Name$ This DDEshare name must be used in the EXCEL
topic configuration.
4. The EXCEL item should be the name of the RSView32 Server tag.
5. The complete entry in the EXCEL 97 cell would appear as:
='\\computer_name\ndde$'|'RTDataProject_Name$'!'tag_name'
NetDDE Common Pitfalls:
• The server node name cannot have a dash "-" in the name. Use an
underscore "_" instead of a dash.
• NetDDE is not running on a Windows95 client. To start NetDDE click on
start, run and run "NetDDE".
• #N/A means that the link could not be established which may indicate the
user logging in does not have read rights to the data. If "everyone" in the
DDEshare permissions has rights try creating a specific user and give that
user read rights. If there is a user name created try deleting and re-create
the user. A user may exist but not be functional.
• In DDEshare the application and topic name was not under the STATIC
section.
• In DDEshare under trusts the start application enabled and initiate to
application enabled must be checked.
• The DDEPokeEnable command must be issued at the RSView32 server
to enable DDE poking of data from a client.