In order to allow the election process to be performed a preferred QINSy system priority list needs to be set up. Make sure that all QINSy instances are added to the list by entering the IP address of the network interface on which it can be reached. This is including the one on which QINSy is running.
Once the QINSy instances have been defined it might be necessary to tune the heartbeat message interval or heartbeat message time-out.
The settings dialog can also be used to determine the redundancy behavior when a 'former master' comes back online.
Observe a situation with two QINSy instances, of which system 1 has the highest priority for the two possible methods:
"Current master stays master"
"Former master becomes master again"
|Online||Online||Instance 1||Instance 1|
|Offline||Online||Instance 2||Instance 2|
|Online||Online||Instance 2||Instance 1|
Presentation of Status Information
In order to allow the user to monitor the outcome of the election process and the availability of each QINSy system the user interface contains a list of each detected/configured QINSy system and its status information. The list is according to the order in which the specific QINSy system will become the primary system if all QINSy systems above the specific system are no longer detected on the network. Below you will find a screen design for the user interface:
The outcome of the election process is displayed in the ‘Status’ field. This field can have the following values:
The election algorithm was unable to determine which system should be designated as the master system.
The election algorithm has designated this system as the master system.
The election algorithm has designated another system as the master system.
The information about each known QINSy Instance is displayed in the QINSy Instances grid control.
This grid control contains the following information about each of the QINSy instances:
IP address of network interface on which QINSy instance may be reached.
Status on QINSy instance. Possible value may be found in table below.
Age in seconds since last heartbeat message was received.
If no heartbeat messages have been received since startup of driver.
System is considered to be online because age of last heartbeat message is lower than heartbeat message time-out setting.
System is considered to be offline because age of last heartbeat message is greater than heartbeat message time-out setting or no heartbeat message has been received at all since start-up of driver.
|title||Time Synchronisation |
The rules mentioned under Interfacing Notes depend on a common time reference for each QINSy system.
This may be accomplished through:
- Central network time reference (i.e. domain controller)
- Time Synchronization System (formerly known as PPS system) to each QINSy system.
- PPS and Time Message
- Time Message Only @ 1Hz (ZDA / UTC / RMC / GGA)
The observation for the redundancy monitor can also be selected in the Generic Layout editor.
The value that is shown corresponds with the order so Master will have the value 1.
The Controller has Output driver settings which can be found under the Settings menu.
The dialog shows which output drivers are available and if they make use of the redundancy option or not.
In the dialog is also visble if the Redundancy Monitor driver is active or not and if the system is master or slave.