FLR_TAG,TABLE_HELP,Tag Copy Definition

This table contains the tags that will be used for 
the Tag Copy functionality in the Redundancy module.

With the Tag Copy function RTDB tag synchronization
can be realized between the master and the slave 
system by using PowerNet. The table must be as 
configured as follows:

    User tag    Master tag    Slave tag
    user_temp   temp          RNode:temp

PowerNet will update temp and RNode:temp via the LAN
in case READWRITE has been specified in PowerNet.

Also the Disable Trigger functionality can be 
implemented by the Tag Copy functionality. For 
example:

    User tag    Master tag    Slave tag
    trigger     sectime       0

In this case when the system is running in master the 
sectime will be copied to the trigger and when running 
in slave mode then only once a zero will be copied into 
the trigger. The trigger can be used in communication 
panels.
$
FLR_TAG,USER,User Tag
Required

Valid entry: Standard tag name

Tag which will be used in the application. When using
it with the RTDB Tag Synchronization function it probably
will be used in the graphics task. For use with the 
Trigger Disable function it will be used in the communication
panels of a protocol driver.
$
FLR_TAG,DIM,Dimension
Optional

Valid entry: number in range of 0 to 9999

Dimension of the user, master and slave tag. This field must be
specified in case an array will be used. Note that all three 
tags must be arrays with the minimun size of dimension
$
FLR_TAG,MASTER,Master Source Value
Required

Valid entry: Standard tag name or constant

The Tag Copy function will copy values between the master 
and User tag when the system is running in master mode. 
When the system is running in slave mode then this tag
will be dummy.

When a constant is specified then this value will be copied
once to the User Tag when the mode is changed to master.

$
FLR_TAG,SLAVE,Slave Source Value
Required

Valid entry: Standard tag name or constant

The Tag Copy function will copy values between the slave 
and User tag when the system is running in slave mode. 
When the system is running in master mode then this tag
will be dummy.

When a constant is specified then this valu will be copied
once to the User Tag when the mode is changed to slave.
$
FLR_ACT,TABLE_HELP,Mode Change Actions Definition

This table contains the actions that will be performed on
tags in case of a mode change from master to slave or vice
versa.
$
FLR_ACT,ACTTAG,Source Tag
Required

Valid entry: Standard tag name

The tag on which the specified action will be performed on.

$
FLR_ACT,WHEN,New Mode
Required

Valid entry: MASTER
             SLAVE

Definition when the action will be performed. The action will
be performed in case the value of the field corresponds to the
new mode of the redundancy task.
$
FLR_ACT,ACT,Action
Required

Valid entry: 
             NULL
             OFF
             ON
             TGL
             SET
             ADD
             SUB

This field specifies the action which will be performed
on the tag.
$
FLR_ACT,VAL,Value
Optional

Valid entry: Constant number

The value will be used with the following operations:

             SET
             ADD
             SUB

The value will be don't care with all other operations.
$
FLR_MCI,TABLE_HELP,Dataset duplication definition

This table defines the relation between MCI based decoder 
tasks and MCI based protocol drivers. The redundancy module
will intercept all MCI messages and route them to the 
correct task depending on the mode.
$
FLR_MCI,DREQ,Decoder Request Mailbox
Required

Valid entry: Standard tag name

The MCI based decoder task will write its request into the
Decoder Request Mailbox. Usually the decoder would write 
direct into the protocol driver's mailbox. The references
to the protocol drivers mailbox must be replaced with this 
mailbox.
$
FLR_MCI,DRSP,Decoder Reply Mailbox
Required

Valid entry: Standard tag name

The redundancy task routes responses which originate from
the protocol driver to the Decoder Response Mailbox. This 
mailbox must be specified as the task's mailbox in the decoder
(mailbox definition).

MCI messages received in the Protocol Driver Response Mailbox
can be routed to the Decoder Response Mailbox.
$
FLR_MCI,PREQ,Protocol Driver Request|Mailbox
Required

Valid entry: Standard tag name

The redundancy task routes requests which originate from 
the MCI based decoder to the Protocol Driver Request mailbox.
This mailbox must be specified as the task's mailbox of the 
protocol driver (mailbox definition).

MCI messages received in the Decoder Request Mailbox can be
routed to this mailbox.
$
FLR_MCI,PRSP,Protocol Driver Reply Mailbox
Required

Valid entry: Standard tag name

The protocol driver will write its responses into the Protocol
Driver Reply mailbox. Usually the protocol driver writes its 
response direct into the mailbox of the decoder. The references 
to the decoder mailbox in the protocol driver must be replaced 
with this mailbox.
$
FLR_HIST,TABLE_HELP,Database Synchronization Definition

This table defines the database names which will be registered
for synchronization.
$
FLR_HIST,ALIAS,Database Alias Name
Required

Valid entry: ASCII string

The database alias name which must be registered for 
synchronization.
$
FLR_HIST,DTABLE,Database Table Name
Required

Valid entry: ASCII string

The database table name which must be registered for
synchronization.
$
FLR_HIST,DTIME,Time Key
Required

Valid entry: ASCII string of max 16 char

The column name of the column which contains the value
of sectime. This column must exist in order to
synchronize both systems.
$
FLR_HIST,HISTMBX,Historian Mailbox
Required

Valid entry: Standard tag name

The historian mailbox which has been specified in the
specific historian.
$
FLR_HIST,PRE,Pre Fault Time
Required

Valid entry: Number of 1 to 9999 minutes

Total time which will be registered as time to detect
a fault. This time usually can be calculated as:

   pre fault time = heart beat period * nr of retries

This period will also be synchronized by the redundancy
in case the fault has been solved.
$
FLR_HIST,POST,Post Fault Time
Required

Valid entry: Number of 1 to 9999 minutes

The post fault time is defined as the period needed to 
restore the system after the detection of both systems
running again. During this period the Tag Copy function
need to update all tags on both systems.

The historian synchronization function will also 
synchronize both systems during this time.

This period of time cannot be calculated and must be
estimated.
$
FLR_DEF,TABLE_HELP,Redundancy Setup Definition

This table defines global definitions of the redundancy
module.
$
FLR_DEF,DEFMODE,Default Mode
Required/Default=MASTER

Valid entry: MASTER or SLAVE

Default mode of the system. This value must be changed
when duplicating the application.

The system will start up in default mode and always return 
to the default mode after a fault period.
$
FLR_DEF,ALIVE,Heart Beat Trigger
Required

Valid entry: Standard tag name

This field must contain a trigger which has been specified
in the timer module. The trigger must be triggered with a
fixed period of time.

The heart beat trigger checks the presence of the remote
system. It triggers the heart beat functionality which
sends heart beat packets over the LAN.

The interval of the heart beat trigger is application
dependent.
$
FLR_DEF,RETRY,Num of Retries
Required

Valid entry: Number of 1 to 999

This field specifies the maximum number of retries before
a fault period will be detected. This value applies to the
LAN heart beat as well as to the IO heart beat.
$
FLR_DEF,IOTX,I/O Send Heart Beat
Optional

Valid entry: Standard tag name

The I/O heart beat tag is used to send a heart beat via the 
external device to the remote system. The redundancy task
will write an incrementing value to this tag. The remote
system will receive this value via the I/O receive heart
beat.

The I/O send heart beat must be specified in the protocol
driver as a write on exception element.
$
FLR_DEF,IORX,I/O Receive Heart Beat
Optional

Valid entry: Standard tag name

The I/O receive heart beat tag will receive a heart beat 
from the remote system via the external device. The 
redundancy task will check this value and check if the
remote system is still alive. The remote system will send
this value with the I/O send heart beat tag.

The I/O receive heart beat tag must be configred in the 
protocol driver for receiving the value.
$
FLR_DEF,SENDMBX,LAN Send Mailbox
Required

Valid entry: Standard tag name

Mailbox used for sending data via the FL-LAN mailbox. 
This mailbox must correspond to the mailbox specified 
in the FL-LAN task.
$
FLR_DEF,RECVMBX,LAN Receive Mailbox
Required

Valid entry: Standard tag name

Mailbox used for receiving data via the FL-LAN mailbox. 
This mailbox must correspond to the mailbox specified 
in the FL-LAN task.
$
FLR_DEF,REPLYMBX,Historian|Reply Mailbox
Optional

Valid entry: Standard tag name

Global historian reply mailbox for all used historians.
This mailbox does not have to be referenced in historian
tasks.
$
FLR_DEF,CURMODE,Mode Change Tag
Optional

Valid entry: Standard tag name

Trigger tag for changing the current mode from master to
slave or vice versa. The current mode will be changed to 
the opposite mode. The mode can only be changed when the
system is in the running state.

The redundancy task will send a request for mode change
to the remote system.
$
FLR_DEF,STATNR,Status number
Optional

Valid entry: Standard tag name

Tag which holds the current status of the redundancy 
module.
$
FLR_DEF,STATMSG,Status message
Optional

Valid entry: Standard tag name

Tag which displays information of the running state of
the redundancy module.
$