Nothing Special   »   [go: up one dir, main page]

Configuracion FSgateway

Download as pdf or txt
Download as pdf or txt
You are on page 1of 9

Tech Note 563

Configuring FSGateway to Access Historian Data from Wonderware Application Server

All Tech Notes, Tech Alerts and KBCD documents and software are provided "as is" without warranty of any kind. See the Terms of Use for more information.
Topic#: 002315
Created: January 2009

Introduction
Wonderware IndustrialSQL Server Historian provides an I/O Server called aahIOSvrSvc. This I/O Server is an interface
for clients to access data from the Historian. It uses the SuiteLink protocol. The Historian I/O Server is re-configured with
a single topic called tagname. The InSQL I/O Server listens for clients that are attempting to establish a connection using
the pre-configured topic.
Wonderware FSGateway is a communications protocol converter. It is used to link clients and data sources
communicating with different communication protocols such as SuiteLink, DDE, FastDDE, and ArchestrA Message Exchange.
This Tech Note provides the step-by-step procedure to:

Configure the FSGateway to communicate with the Historian I/O Server


Configure the OPCClient proxy object from the Wonderware Application Server to access data from the Historian /
FSGateway OPC Server via OPC protocol.

Application Versions

InSQL Historian v 9.0 Patch 1

FSGateway v 1.5 Service Pack 1

Wonderware Application Server v3.0 Patch 2

Microsoft SQL Server 2005 Service Pack 2

Assumptions
This Tech Note assumes that you are knowledgeable on the following products and protocols:

IndustrialSQL Server Historian v9.0 or later

FSGateway v1.5 or later

Wonderware Application Server (WAS) v3.0 or later

SuiteLink and OPC communication protocols

Procedure
1. Install FSGateway, and add the SuiteLink Object from the FSGateway item in the SMC (Figure 1 below).

Figure 1: Add the SuiteLink Object After Installing FSGateway


2. Type the Server Name as aahIOSvrSvc and the Server Node which is the name of the computer running
the Historian Server.

Figure 2: Server Name


3. Select the Read Only and Change Topic Name options.
4. Enter tagname in the Topic Name.

Figure 3: Read Only and Topic Name Configuration


5. Activate the FSGateway server.
6. Create an instance of the OPCClient object.
7. Enter the corresponding computer name running the FSGateway into Server node field.
8. Select ArchestrA.FSGateway.1 from the Server name list.

Figure 4: Computer Name and Server Name


9. Click the Scan Group tab and add a scan group there.

Figure 5: Add a Scan Group


10. Save your changes and check in the OPCClient object instance.
11. Create an instance of the UserDefined object.
12. Add your field attributes. For this example, we use two of the Historian's built-in System tags
SysminutesRun and SystimeSec.
Add two Analog attributes and name them SysminutesRun and SystimeSec.
13. Assign the I/O Input source for these attributes. For this example they are:

OPCClient_001.group01.SuiteLink.InSQLTopic.SysMinutesRun
OPCClient_001.group01.SuiteLink.InSQLTopic.SysTimeSec

Figure 6: Create Field Attributes for Historian Tags


14. Deploy all the objects, then open the ObjectViewer.
15. Select the UserDefined object and add the attributes you created in the previous steps to the Watch
window.

You see updated data for these attributes:

Figure 7: ObjectViewer Updates


B. Nguyen
Tech Notes are published occasionally by Wonderware Technical Support. Publisher: Invensys Systems, Inc., 26561 Rancho Parkway South, Lake Forest,
CA 92630. There is also technical information on our software products at Wonderware Technical Support.

For technical support questions, send an e-mail to support@wonderware.com.

Back to top
2009 Invensys Systems, Inc. All rights reserved. No part of the material protected by this copyright may be reproduced or utilized in any form or by
any means, electronic or mechanical, including photocopying, recording, broadcasting, or by anyinformation storage and retrieval system, without
permission in writing from Invensys Systems, Inc. Terms of Use.

You might also like