Using OmniServer with Client Programs Please note: This only applies to the OmniServer Server Edition and the OmniServer Professional Edition. Using OmniServer with InTouch Purpose: The purpose of this document is to show you what you need to know in order to connect Wonderware products to the OmniServer via the Suitelink interface. This covers InTouch Version 10 (standalone) and versions prior to 10. Configuration: Step 1: Bring up the OmniServer Configuration program. This will allow you to add and/or change your configuration. For this example, we will be using the stock devices and protocols that come with OmniServer, in addition to creating our own topic. Of course, you are welcomed to substitute your own devices, protocols, and topics. The configuration program can be normally found from the Start menu. If you are running OmniServer interactively (as opposed to a service), you can also get to the Configuration program by double-clicking on the OmniServer icon in the icon tray. If the icon is not there, then you must use the Start menu. Step 2: Setting up the Device. You will need to setup your device in OmniServer. The device is what defines which port will be used (Serial, Ethernet, etc). You will double-click on the port (or create a new one if it is not listed) and insure that your parameters are correct. In our example, we will use COM1.   Step 3: Configure the protocols. Next, you will configure your protocol to match the data stream from the device (see the Help File for detailed information on creating the protocol). OmniServer comes with the following sample protocol configurations, in addition to any others that might be added in the future: Barcode Euro808 ModbusA ModbusR Scale These protocols are shown below We will use the MODBUSR protocol for our example: Step 4: Cofiguring the Topic. Next, you will need to configure your topic. Create a new topic and select the Device and Protocol that will be used. The Topic is what OmniServer uses to assign a protocol to a device, and open the items in the protocol to the outside world. In our example, we have created a topic called ModbusRTU1, which has had the device assigned as COM1 and the protocol assigned as MODBUSR. Step 5: The Client Application Finally, go to the Clients screen and hover your mouse over the "Factory Suite". This will tell you the "Application Name" that OmniServer uses for the Suitelink interface. This is the name you will use in InTouch. The name used is: OSRVPOLL Step 6: Configuring the Wonderware Access Name: The Configuration for OmniServer is now complete. The next step is to tie OmniServer in with InTouch. What you will need to do is configure a new Access Name. Bring up InTouch, go into WindowMaker, and create a new Access Name. Given the information above, here is how a typical Wonderware Access Name would be setup: Access Name: <your-choice> Application Name: OSRVPOLL. This must match name name given in Step 5 above. Topic: ModbusRTU1 [see the sample below]. This must match the name of your topic in Step 4 above. The remaining options for the access name will be to use Suitelink, and to Advise only active items. Step 7: Create Tags Finally, you will need to create your tags. There are three important pieces of information you need here: Make sure that the "Type" is an I/O type, such as I/O Discrete, I/O Real, etc. It will need to match the type of the Item defined within your protocol. In our example, the data type of Holding Register #0 is Integer, so the type here will be I/O Integer. Make sure the Access Name is the one you have defined above in Step 6. Make sure the "Item" is a name that has been defined in the server. In this example, using the ModBusR protocol, the item AO0 is used to get Holding Register #0. All other fields are not used by the server, so you can use them as you please. You are now finished.