<< Click to Display Table of Contents >> Navigation:  Basics > Redundancy & Status

The DDK automatically supports redundancy. All Managed infordrivers will follow the TxRx/RxOnly messages from CSI. There are various ways of observing or controlling the redundancy state.

 

Individual Infodrivers have an OnInfodriverStateChange event that will fire each time its redundancy state changes.  They also expose a function, SetInfodriverRedundancyState, to request a change of state for an individual managed infodriver from CSI.

 

The BNCSFramework also provides global GetInfodriversRedundancyState & SetInfodriversRedundancyState

 

The state of the managed infodrivers all contribute to the overall driver state that is exposed by BncsFramework.DriverState.  Drivers can also subscribe to the OnDriverStatusChange event that fires whenever the driver state changes amongst other triggers.

 

Monitored infodrivers do not automatically pickup a state from CSI.  Drivers can either set the state manually or provide a Managed Infodriver in the BncsFramework.AddMonitoredInfodriver method that the monitored infodriver will track.  This is particularly relevant for automatics where a typical pattern is to provide a managed infodriver to control the automatic redundancy/failover state which the automatics monitored infodrivers would then track.