Extended descriptor requirements, Invalid: no square brackets around the keyword – Rockwell Automation FactoryTalk Historian SE 3.0 UniInt Interface User Guide User Manual

Page 47

Advertising
background image

UniInt Interface User Manual

41

Trigger Rate

[UI_TRIGGERRATE]

Integer

Heartbeat

Reporting Period

Trigger Bad Value Rate

[UI_TRIGGERBVRATE]

Integer

Heartbeat

Reporting Period

Scan Class IO Rate

[UI_SCIORATE]

Integer

At Scan

At Scan

Scan Class Bad Value Rate

[UI_SCBVRATE]

Integer

At Scan

At Scan

Scan Class Scan Count

[UI_SCSCANCOUNT]

Integer

At Scan

Reporting Period

Scan Class Scans Skipped

[UI_SCSKIPPED]

Integer

At Scan

Reporting Period

Scan Class Point Count

[UI_SCPOINTCOUNT]

Integer

At Scan

na

Scan Class Scan Time

[UI_SCINSCANTIME]

Integer

At Scan

na

Scan Class Device Scan Time

[UI_SCINDEVSCANTIME]

Integer

At Scan

na

Extended Descriptor Requirements

All of the keywords entered into the ExDesc must adhere to the following rules. The
keywords must be the very first thing in the ExDesc with no spaces before the keyword, the
keyword must be surrounded by square brackets ([ ]) with no spaces between the brackets
and the keyword, and the keywords are all case sensitive. Additional text, such as a more
detailed description of the tag, can be added to the ExDesc after the keyword if the Historian
administrator would like a more detailed description or some other text that may help with
the administration of these Historian tags. The additional text is not required, has no standard
format and would serve no purpose other than helping a user or Historian administrator
determine a tag‘s purpose from looking at the exdesc where the keywords are found. For
example, the following is a valid extended descriptor for an IO Rate Health Point.

[UI_IORATE] Number of events per second for interface PIIFC

The following extended descriptors are examples of invalid keyword entries for an Interface
Health point. If the keyword is not specified exactly, the interface will try to load the point as
a regular interface point. This most likely will result in a message stating the point was not
loaded by the interface. This may also result in the point being loaded by the interface and
collecting unexpected data.

Invalid: no square brackets around the keyword

UI_IORATE Number of events per second for interface xyz

Invalid: spaces between the opening square bracket and the keyword

[ UI_IORATE] Events per second

Invalid: missing closing square bracket

[UI_IORATE

Invalid: keyword is in the wrong case

[ui_iorate] Number of events per second for interface xyz

Advertising