FactoryTalk View SE - Adding The Data Server Name and Tag Address To The Tag Address Syntax For Third Party OPC Servers

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

ID: BF17968 | Access Levels: TechConnect

FactoryTalk View SE - Adding the Data


Server name and tag address to the tag
address syntax for Third Party OPC servers

Document ID BF17968

Published Date 11/02/2021

Summary
FactoryTalk View SE - Adding the Data Server name and tag address to the tag address
syntax for Third Party OPC servers

Problem
How do I add the Data Server name to the tag address syntax for Third Party OPC
servers used in a Factory Talk View SE Standalone application?
How do I point to the tag address instead of the tag name in the syntax for Third
Party OPC?
When using a Third Party OPC server (for instance Kepware as in the example below)
and browsing for tags in Factory Talk View Studio, it does not add the data server
name to the tag address syntax. This causes requests for tag data to query all
servers in the area for the tag. This can be critical in an Factory Talk View SE
Standalone application and especially if there is more than one data server used in
the application.

Environment
Factory Talk View Studio
Third Party OPC
Old browser version not supported
Solution
To receive the best experience please download or update to the latest version of Chrome,
Add the data
Edge,server
Firefoxname in front of the tag
or Safari.
Before:
Channel.Device1._System._Error

Old browser version not supported


To receive the best experience please download or update to the latest version of Chrome,
Edge, Firefox or Safari.
This will cause performance issues when you have multiple data servers because when
tags are requested, they will query every available data server to try and resolve the tag
name.
 

The solution would be to add the data server name in front of the tag.

After:
:KEPWARE:Channel.Device1._System._Error

The data server name is the name entered in the project tree by the person who has created the application.

In the project example shown above, the data server is named KEPWARE so you need to add the data server
name to the beginning of the tag name. Now when the tag is requested; the request will go directly to the
specified data server.
 

Refer to the tag address instead of the tag name

If you need to refer to the tag address instead of the tag name, then change the syntax as
below

Old browser version not supported


Before:
To receive the best experience please download or update to the latest version of Chrome,
Channel2.Device1.Prgm_Example.test.DN
Edge, Firefox or Safari.
After:
:Channel2.Device1.PROGRAM:EXAMPLE.TEST.DN

Old browser version not supported


To receive the best experience please download or update to the latest version of Chrome,
Edge, Firefox or Safari.
With the OPC Data server named kep: 
:kep:Channel2.Device1.PROGRAM:EXAMPLE.TEST.DN

Old browser version not supported


To receive the best experience please download or update to the latest version of Chrome,
Edge, Firefox or Safari.
For additional References see:

FactoryTalk View SE Area Best Practices - Guidelines for structuring Areas in a


FactoryTalk View SE Application.
Using the Kepware OPC Server
Kepware communication troubleshooting Tips

Recently Viewed

Using the Kepware OPC Server


Old browser version not supported
v4.5 and earlier
To receive the best experience please download or update to the latest version of Chrome,
Edge, Firefox or Safari.
 
DISCLAIMER
This knowledge base web site is intended to provide general technical information on a particular subject or
subjects and is not an exhaustive treatment of such subjects. Accordingly, the information in this web site is not
intended to constitute application, design, software or other professional engineering advice or services. Before
making any decision or taking any action, which might affect your equipment, you should consult a qualified
professional advisor.

ROCKWELL AUTOMATION DOES NOT WARRANT THE COMPLETENESS, TIMELINESS OR ACCURACY OF ANY OF THE
DATA CONTAINED IN THIS WEB SITE AND MAY MAKE CHANGES THERETO AT ANY TIME IN ITS SOLE DISCRETION
WITHOUT NOTICE. FURTHER, ALL INFORMATION CONVEYED HEREBY IS PROVIDED TO USERS "AS IS." IN NO EVENT
SHALL ROCKWELL BE LIABLE FOR ANY DAMAGES OF ANY KIND INCLUDING DIRECT, INDIRECT, INCIDENTAL,
CONSEQUENTIAL, LOSS PROFIT OR DAMAGE, EVEN IF ROCKWELL AUTOMATION HAVE BEEN ADVISED ON THE
POSSIBILITY OF SUCH DAMAGES.
ROCKWELL AUTOMATION DISCLAIMS ALL WARRANTIES WHETHER EXPRESSED OR IMPLIED IN RESPECT OF THE
INFORMATION (INCLUDING SOFTWARE) PROVIDED HEREBY, INCLUDING THE IMPLIED WARRANTIES OF FITNESS
FOR A PARTICULAR PURPOSE, MERCHANTABILITY, AND NON-INFRINGEMENT. Note that certain jurisdictions do
not countenance the exclusion of implied warranties; thus, this disclaimer may not apply to you.

www.rockwellautomation.com

Copyright © 2023 Rockwell Automation, Inc. All Rights Reserved.


  

Old browser version not supported


To receive the best experience please download or update to the latest version of Chrome,
Edge, Firefox or Safari.

You might also like