Configuring the DAServer

Note: This DAServer is hosted by the DAServer Manager, a Microsoft Management Console (MMC) snap-in, which is part of the ArchestrA System Management Console (SMC) suite of utilities. Many high-level functions and user-interface elements of the DAServer Manager are universal to all DAServers, and only the documentation for the DAServer Manager contains descriptions of those universal functions/UI elements. Therefore, reading the documentation for both the MMC and the DAServer Manager is critical to understanding this user’s guide. To read the documentation about the MMC and DAServer Manager, click the Help topics on the SMC Help menu. Both the MMC and DAServer Manager Help is displayed. An Adobe Acrobat version of the DAServer Manager documentation (DAServerManager.pdf) is provided.

Note: The shortcut menu items described in this document typically represent only a subset of any actual shortcut menu. Most items in each shortcut menu are standard Windows commands. See the MMC’s Help for more information about those commands.

Before the DAServer can be configured, the Ethernet adapter and TCP/IP software must be installed on your computer; and, if you plan to configure your DAServer using Host Names rather than the IP addresses directly, the Host Names for all PLCs on the Ethernet need to be defined by modifying the hosts file.

To install the Ethernet adapter

1. Install the Ethernet adapter and TCP/IP software following the instructions provided by the manufacturer.

2. The DAServer configuration accepts either Host Names or IP addresses directly.

   • You can configure Host Names directly in the DAServer Manager.

   • Optionally, if Host Names will be used, then the Host Names for all PLCs on the network need to be defined by modifying the hosts file.

   • Refer to the documentation provided by Microsoft for information about the location of the hosts file and the format of its contents.

     Note: All configuration files will be moved to "C:\Documents and Settings\All Users\Application Data\Wonderware\DAServer\DASABTCP" on Windows XP and Windows Server 2003 operating systems and to "C:\ProgramData\Wonderware\DAServer\DASABTCP" on Windows Vista and above operating systems. The rule file will provide the version information.

3. Restart the computer.

To prepare the ABTCP DAServer

4. Install the ABTCP DAServer from Windows by running the Setup.exe program.

Note: DAServer installation instructions are included in a separate Help file (.chm extension).

5. Accept all the default settings during installation.

Note: Since there are no default values for security settings, you must take note of the User Name and password selected during install.

6. After the ABTCP DAServer has been installed, a small amount of configuration is required. Start the System Manager Console by clicking the Start button on the Windows taskbar, and pointing to Programs.

7. Point to the Wonderware folder that contains the System Management Console, then click System Management Console.

8. From the System Management Console tree, click on DAServer Manager.

   

9. Click on Local Domain, then Local Node.

   • Under the Local Node, the DAServer name is ArchestrA.DASABTCP.3.

Note: See the DAServer Manager Online Help for general information about working in this snap-in environment.

10. Before the DAServer is started, the device hierarchy must first be built to establish communications to each of the controllers.

Important! For step-by-step procedures on how to build the device hierarchy, please see the section, "ABTCP Hierarchy in the DAServer Manager."

Note: Selecting the Configuration object of the hierarchy tree displays the Global Parameters interface for this DAServer. The default Poke Mode settings for the DAServer is Optimization mode. Configure all other global parameters as required for this DAServer. For more information about the Global Parameters dialog box, including descriptions of the different Poke Modes, see the DAServer Manager documentation. You can access that documentation by clicking the DAServer Manager icon and selecting the Help topics on the Help menu, and then navigating through the DAServer Manager book.

Important! Any Global Parameters that appear dimmed are not supported.

11. When the ABTCP hierarchy build has been completed, you can start configuring the respective devices for communications.

    • Optionally, the desired device groups can be created under the Device Groups tabbed page with each of the PLC objects.

    • Desired device items can also be optionally created under the Device Items tabbed page with each of the PLC objects.

Note: The hierarchy entry is added in the "edit mode," providing a convenient place for you to appropriately describe components of your specific hardware environment. Both hierarchy node name and device group name are numerically sequenced by default. They can be renamed at any time.

The DAServer will be ready to use after it is activated.

• If you are using an OPC Client, the DAServer will auto-start.

• If you are using DDE/SuiteLink, you must start the DAServer either as a manual or automatic service.

• The DAServer can be activated by right-clicking on ArchestrA.DASABTCP.3 and selecting Activate Server from the shortcut menu.

Note: To run the ABTCP DAServer as a service, right-click on the DAServer name and select Configure As Service from the shortcut menu. You can configure it as an auto service or manual service. For more information about configuring the DAServer as a service, see the Activation/Deactivation/Service Component of the DAServer Manager documentation.

Note: When any configuration view is in an open state and you open the same server the second time, the DAServer locks the second instance of this same-server access for any update or configuration activities. Access to this second opening instance will resume after the first one has been closed.