Clocking.HBus.AutoFallBack

Note: For more information about setting up CT bus clocking, and about the rules and restrictions that apply to setting up clocking with CG 6000C boards, refer to Section 3.5.

Note: CG 6000C boards operating in slave mode cannot fall back to Network 1.

Note: The physical timing references specified with the Clocking.HBus.ClockSource and Clocking.HBus.FallBackClockSource keywords must be present and not in alarm when the CG 6000C board's clocking is set up.

Note: Use the swish command queryBoardClck to determine what timing reference the board is actively using.

• If the primary clock master's first timing reference fails and then returns, the primary master's timing reference (and consequently that for any clock slaves) tries to switch back to the first source.

• If the primary clock master's first timing reference and fallback timing reference fail, the secondary clock master begins to drive the CT bus clock for all clock slaves. If either of the primary clock master's timing references then recover, the CT bus does not switch back to this either of these sources. The secondary master continues to drive the CT bus clock until directed otherwise.

• If the board is configured as the primary clock master and both timing references fail, the board reconfigures itself to become a slave to the secondary H100/H110 timing reference.

• If the board is configured in standalone mode and both the first timing reference and fallback timing references fail, the board automatically switches to OSC.