May 16, 2017 In the simplest sense FactoryTalk Historian is just a private-labeled version of the PI Server from OSIsoft. It leverages the PI Server’s highly efficient architecture for capturing, organizing, and storing process data. That provides the ideal foundation for today’s rapidly growing crop of advanced analytics like our PlantESP. FactoryTalk Historian To Historian Interface User Guide 1 Chapter 1. Introduction The Rockwell FactoryTalk Historian to Historian interface copies tag data from one Historian Server to another. Data is moved in one direction, meaning data is copied from the source to the receiving Historian Server (also referred to as target Historian Server).
Advertising
Historian Point Configuration
16
user‘s manual for detailed discriptions of the Historian Point Attributes that are relavant to
the interface.
the interface.
The following section describes common point attributes. The second and third sections
describe how input and output points are configured and used.
describe how input and output points are configured and used.
Point Attributes
The following Historian Point Attributes are used by UniInt based interfaces. Refer to the
interface documentation to determine whether the standard UniInt implementation for a
particular attribute is applicable. Some attributes may have additional or different meanings
for individual interfaces. If the specific attribute is not mentioned by the interface
documentation of a UniInt based interface, then the attribute will affect the data in
accordance with the explanation in this manual. Also, most UniInt based interfaces use a
number of attributes that are not described here.
interface documentation to determine whether the standard UniInt implementation for a
particular attribute is applicable. Some attributes may have additional or different meanings
for individual interfaces. If the specific attribute is not mentioned by the interface
documentation of a UniInt based interface, then the attribute will affect the data in
accordance with the explanation in this manual. Also, most UniInt based interfaces use a
number of attributes that are not described here.
Tag
The words point and tag are frequently used interchangeably, but there is a difference. A tag
is a label or name for a point. Any tag name can be used in accordance with the normal
Historian point naming conventions.
is a label or name for a point. Any tag name can be used in accordance with the normal
Historian point naming conventions.
PointSource
The PointSource is a unique, single or multi-character string that is used to identify the
Historian point as a point that belongs to a particular interface. For example, a single point
source using the letter R may be chosen to identify points that belong to the Random
interface. In order to implement this, the PointSource attribute should be set to R for every
Historian Point that is configured for the Random interface. Then, if /ps=R is specified on
the startup-command-line of the Random interface, the Random interface will search the
Historian Point Database for every Historian point that is configured with a PointSource of
R. Likewise, a multi-character PointSource using the string Boiler1 may be used to
identify points that belong to the PIIFC Interface. To implement this, the PointSource
attribute would be set to Boiler1 for every Historian Point that is configured for the PIIFC
Interface. Then, if /ps=Boiler1 is used on the startup command-line of the PIIFC
Interface, the Interface will search the Historian Point Database for every Historian point that
is configured with a PointSource of Boiler1
Historian point as a point that belongs to a particular interface. For example, a single point
source using the letter R may be chosen to identify points that belong to the Random
interface. In order to implement this, the PointSource attribute should be set to R for every
Historian Point that is configured for the Random interface. Then, if /ps=R is specified on
the startup-command-line of the Random interface, the Random interface will search the
Historian Point Database for every Historian point that is configured with a PointSource of
R. Likewise, a multi-character PointSource using the string Boiler1 may be used to
identify points that belong to the PIIFC Interface. To implement this, the PointSource
attribute would be set to Boiler1 for every Historian Point that is configured for the PIIFC
Interface. Then, if /ps=Boiler1 is used on the startup command-line of the PIIFC
Interface, the Interface will search the Historian Point Database for every Historian point that
is configured with a PointSource of Boiler1
Before an interface loads a point, the
interface usually performs further checks by examining additional Historian Point Attributes
to determine whether a particular point is valid for the interface. For additional information,
see the /ps parameter.
to determine whether a particular point is valid for the interface. For additional information,
see the /ps parameter.
The following table explains length limits imposed on the PointSource for different
configurations. When the maximum possible lengths differ for the software installed on site,
the shortest length applies.
configurations. When the maximum possible lengths differ for the software installed on site,
the shortest length applies.
PI API
Historian Server
PI SDK How to download sketchup to mac.
Maximum Length
1.6 or higher
2.x or higher
na
100
Advertising
Popular Brands
Popular manuals
Advertising
UniInt Interface User Manual Anime studio pro 10 download mac.
17
PI API
Historian Server
PI SDK
Maximum Length
na
Below 2.x
![Rockwell Pi To Pi Interface User Manual Rockwell Pi To Pi Interface User Manual](/uploads/1/3/3/9/133936326/163481677.jpg)
Disabled
1
![Interface Interface](/uploads/1/3/3/9/133936326/992499356.jpg)
Below 1.6
na
Disabled
1
na
na
Rockwell Pi To Pi Interface User Manual Youtube
Enabled
100
Case-sensitivity for PointSource Attributes
In all cases, the point source character that is supplied with the /ps command-line parameter
is not case sensitive. That is, /ps=P and /ps=p are equivalent.
is not case sensitive. That is, /ps=P and /ps=p are equivalent.
Best vpn for mac pcmag. Reserved and Illegal Point Sources
Several subsystems and applications that ship with Historian 3 are associated with default
point source characters The Totalizer Subsystem uses the point source character T, the Alarm
Subsystem uses G and @, and the Performance Equations Subsystem uses C. Rockwell
Automation recommends not using these point source characters. Also, if a point source
character is not specified when creating a Historian point, the point is assigned a default
point source character of Lab. Therefore, it would be confusing to use L or Lab as the point
source character for an interface.
point source characters The Totalizer Subsystem uses the point source character T, the Alarm
Subsystem uses G and @, and the Performance Equations Subsystem uses C. Rockwell
Automation recommends not using these point source characters. Also, if a point source
character is not specified when creating a Historian point, the point is assigned a default
point source character of Lab. Therefore, it would be confusing to use L or Lab as the point
source character for an interface.
The * and the ? characters are invalid point sources as they are wild card characters for
searching the database. These characters cannot be any part of a multi-character point source.
searching the database. These characters cannot be any part of a multi-character point source.
PointType
Consult the interface documentation to determine which point types are supported for
individual interfaces. Not all point types that are supported by the Server are necessarily
supported by an interface.
individual interfaces. Not all point types that are supported by the Server are necessarily
supported by an interface.
Typically, DCS point types do not need to correspond to Historian point types but this may
be a requirement for certain interfaces. For example, integer values from a DCS can be sent
to floating point or digital Historian tags. Similarly, a floating-point value from the DCS can
be sent to integer or digital Historian tags, although the values will be truncated. This rule
does not extend to string tags. UniInt will not convert an integer, float, or digital type value
to a string. Unless the interface documentation specifies these conversions, only string and
blob type data will be saved to a string Historian tag.
be a requirement for certain interfaces. For example, integer values from a DCS can be sent
to floating point or digital Historian tags. Similarly, a floating-point value from the DCS can
be sent to integer or digital Historian tags, although the values will be truncated. This rule
does not extend to string tags. UniInt will not convert an integer, float, or digital type value
to a string. Unless the interface documentation specifies these conversions, only string and
blob type data will be saved to a string Historian tag.
Note: If an interface is not using the extended PI API functionality, negative integer
values from the DCS must be stored in floating point tags in Historian because
negative integers cannot be transmitted by the traditional PI API. If using the
extended PI API, int16 and digital tags are the only Historian point types with this
limitation.
negative integers cannot be transmitted by the traditional PI API. If using the
extended PI API, int16 and digital tags are the only Historian point types with this
limitation.
ExcMin, ExcMax, ExcDev and ExcDevPercent
These are the exception specification attributes.
Advertising
Popular Brands
Rockwell Pi To Pi Interface User Manual Software
Popular manuals