beautypg.com

Exception data collection – Rockwell Automation FactoryTalk Historian SE 3.0 H2H Interface User Guide User Manual

Page 77

background image

FactoryTalk Historian To Historian Interface User Guide

71

.BAT

.INI

Description

/ns

Optional

--

Boundary condition for data retrieval with a time-
range specific history recovery.
When specified the interface will start history
recovery beginning with the first value prior to the
start time. The default behavior is to begin with
the first value after the start time.

/rh=#

Optional
Default:

/rh=8

HistRecovery

Hours of history recovery to perform.
There is no limit on the number of hours for
history recovery. However special preparations
may be necessary if the recovery period spans
beyond the primary archive. For example there
may not be enough space in the target (non-
primary) archive for the recovery data, or non-
primary archives may not have space allocated for
newly created tags. See the Historian Server
System Management Guide for information on
backfilling data.

/rh_inc=#

Optional
Default:

/rh_inc=24

MaxArcTimespan

Time increments within the total

/rh

recovery

period.
For example,

/rh

=48 and

/rh_inc

=24. The

interface will cycle through the tag list twice. On
the first cycle, data recovery is performed for the
first 24-hour period. On the second cycle, the
second 24-hour period is collected to complete
the total 48 hour recovery period.

/rh_qcheck=#

Optional
Default:

/rh_qcheck=5

For exception data scan classes, sets the time
interval between clearing the exception queue on
the source Historian Server during history
recovery.
By default the interface will collect exceptions
from the source Historian Server every 5 seconds
during history recovery to prevent overflowing the
queue. Users may want to adjust this time interval
to tune history recovery performance.

Exception Data Collection

.BAT

.INI

Description

/me=#

Optional
Default:

/me=5000

--

Sets the maximum number of exception events
retrieved per data request. A large count reduces the
number of calls required for acquiring exception
updates. A small count reduces the time to complete
each request (for troubleshooting network timeout
issues).

/sn

Optional

--

Bypass exception filtering for data collected from the
source Historian Server. This data has already
passed exception for the source tag so additional
data filtering can only lead to data mismatches
between Historian Servers.