/try=x Optional Default: 300 Number of seconds to wait before trying to re-establish a lost connection to the DCS. Sometimes a node in the DCS becomes unreachable. In the interface log file, this is reported by error messages like “… object’s node not reachable”. In this case, the PI Interface for ABB Advant will try to re-establish the connection after a while. The default setting is /try=300, which means that an attempt to reconnect is made after 5 minutes. If the attempt fails, the next one is launched after another 5 minutes. It is possible to configure a different retry rate via /try=. You can choose an integer value between 0 and 3600. Note that the /try parameter has no effect if the ABB patch for fixing the “Node Down” problem has been applied (discussed in this manual) and the workaround (which actually uses the value set via /try) has therefore been disabled via /ndw=0 (see this parameter in this table). /UFO_ID=# Required for UniInt Failover Phase 1 or 2 Failover ID. This value must be different from the Failover ID of the other interface in the failover pair. It can be any positive, non-zero integer. /UFO_Interval=# Optional Default: 1000 for Phase 1 Failover Default: 5000 for Phase 2 Failover Valid values are 5020000. Failover Update Interval Specifies the heartbeat Update Interval in milliseconds and must be the same on both interface computers. This is the rate at which UniInt updates the Failover Heartbeat tags as well as how often UniInt checks on the status of the other copy of the interface. /UFO_OtherID=# Required for UniInt Failover Phase 1 or 2 Other Failover ID. This value must be equal to the Failover ID configured for the other interface in the failover pair.
Errors (Phase 2) Unable to open synchronization file Message 27-Jun-08 17:27:17 PI Eight Track 1 1> Error 5: Unable to create file ‘\\georgiaking\GeorgiaKingStorage\UnIntFailover\\PIEightTrack_eight_1.dat’ Verify that interface has read/write/create access on file server machine. Initializing UniInt library failed Stopping Interface Cause This message will be seen when the interface is unable to create a new failover synchronization file at startup. The creation of the file only takes place the first time either copy of the interface is started and the file does not exist. The error number most commonly seen is error number 5. Error number 5 is an “access denied” error and is likely the result of a permissions problem. Resolution Ensure the account the interface is running under has read and write permissions for the folder. The “log on as” property of the Windows service may need to be set to an account that has permissions for the folder. Error Opening Synchronization File Message Sun Jun 29 17:18:51 2008 PI Eight Track 1 2> WARNING> Failover Warning: Error = 64 Unable to open Failover Control File ‘\\georgiaking\GeorgiaKingStorage\Eight\PIEightTrack_eight_1.dat’ The interface will not be able to change state if PI is not available Cause This message will be seen when the interface is unable to open the failover synchronization file. The interface failover will continue to operate correctly as long as communication to the PI Server is not interrupted. If communication to PI is interrupted while one or both interfaces cannot access the synchronization file, the interfaces will remain in the state they were in at the time of the second failure, so the primary interface will remain primary and the backup interface will remain backup. Resolution Ensure the account the interface is running under has read and write permissions for the folder and file. The “log on as” property of the Windows service may need to be set to an account that has permissions for the folder and file.