Remconnjoin Row Details

Remote

Select (...) and select the name of the remote that is associated with this connection from the Remote Select dialog box.

Connection

Select (...) and select the name of the connection record that is associated with the remote device from the Connection Select dialog box.

Cost Factor

Enter the cost factor of the connection. This value is a number that indicates the relative cost of the connection. Higher numbers indicate higher cost of usage.

Failure

Timeout

Enter the length of time (in seconds) that a remote can fail to communicate over its current connection before it fails over to the next cheapest connection. A value of zero disables connection failovers.

Inhibit Autopoll

Select the checkbox for Omnicomm to only pass commands that are sent to Omnicomm (including poll commands) to the remote. The commands also include those that are sent to Omnicomm by the remote scheduler. Normally, Omnicomm polls its remote devices regularly, establishing a connection when necessary.

Good Test Frequency

Enter the time (in minutes) that must pass before the next test poll can be issued to this remote over this connection if the remconnjoin status is in a good state (for example the State column in the Communication Statistics Summary is Normal).

Refer to the AVEVA Enterprise SCADA HMI Controller documentation for more information about the Communication Statistics Summary.

The actual time may be longer depending on the frequency that the ConnectionController executable is scheduled to run. The ConnectionController executable is started in the run_processes. When changing the frequency in the ConnectionController, RealTime must be restarted before the change takes effect.

A value of zero indicates that testing will never occur.

Bad Test Frequency

Enter the time (in minutes) that must pass before the next test poll can be issued to this remote over this connection if the remconnjoin status is in a bad state (for example, the State column in the Communication Statistics Summary is anything other than Normal).

The actual time may be longer depending on the frequency that the ConnectionController executable is scheduled to run. The ConnectionController executable is started in the run_processes. When changing the frequency in the ConnectionController, RealTime must be restarted before the change takes effect.

A value of zero indicates that testing will never occur.