You will install the DAServer, which will install into the SMC (Start->All Programs>Wonderware->System Management Console).

It will be located under DAServer Manager>Default Group->Local->ArchestrA.DASMBTCP.1. Once its installed you will expand ArchestrA.DASMBTCP.1 and then right-click on Configuration Select Add TCPIP_PORT Object (rename if you please) Right-click on the newly added port, and then select Add ModbusPLC Object (rename if you please) In this new object you will see a field titled Network address:. Here you will enter the hostname or IP address of the PLC. You will also need to pay close attention to the Register size (digits) drop-down list. It is 6 by default, so, for example, if your item names are only 5 characters long, then you will need to make the appropriate change here. In the same object there is a tab titled Device Groups, which is there for Topic definition. Go to that tab, right-click in a blank area, and then select Add. The new item will already be in rename mode. This is your Topic, so rename it as appropriate. If you want to modify the Update Interval, then simply right-click on the default 1000, and select Modify Update Interval. When finished click on the little blue floppy-disk icon in the upper-right hand corner to save your settings. If you want the DAServer to start-up automatically when the computer starts up, then right-click on ArchestrA.DASMBTCP.1, hover over Configure As Service, and then select the startup type you desire. Then to actually get the DAServer up and running, right-click on ArchestrA.DASMBTCP.1 and hit Activate Server.

NOTES: 1) If this is for a SCADAPack32 device, then there are 3 setting which must be made. They are as follows: The unit ID of the SCADAPack32 device needs to be changed to 255 (this is a change that is accomplished in the end device itself) The "Register size (digits):" field within the DASMBTCP Modbus PLC Object needs to be changed to 5 The "Maximum outstanding messages:" field within the DASMBTCP Modbus PLC Object needs to be changed to 1 2) If this is being used for a Unity Simulator or Premium PLC, then take note that individual bit writes are not possible. This is because the two referenced types do not support Modbus function code 22. 3) When defining connection information you will use the following information: Node: <NodeNameRunningDAServer> Application: dasmbtcp Topic: <WhatYouDefineInTheDeviceGroupsTabOfTheDAServer> Protocol: DDE (for local comms) or SuiteLink (aka IOT, for off-node comms)

OPTIONAL: Once you get the DAServer up and running, then you may want to verify that everything can talk. I have pasted a link below to one of our Tech Notes that discusses the use of the WWClient (Wonderware Client) utility to test communications. Link to Wonderware PacWest Tech Note 62: How to monitor and troubleshoot communication using Wonderware Client utility: http://www.pacwest.wonderware.com/web/Support/Technotes/TechNote.aspx? NewsThreadID=4&NewsID=202221