1
|
High-speed data link connects the two Copros.
|
2
|
Using the high-speed data link, the primary CPU controller communicates with the standby CPU every 10 milliseconds.
|
3
|
Primary CPU sends either:
|
Step
|
Action
|
Result
|
---|---|---|
1
|
Standby CPU does not hear from the primary CPU on the high-speed data link
|
|
If ...
|
Then ...
|
---|---|
RIO Head finds the RIO link not active
|
|
RIO Head finds the RIO link is active
|
Message received from primary CPU must be either:
|
1
|
If the message is an I/O transaction, the RIO Head:
|
2
|
If you never configure an I/O drop, the high-speed data link could cause the standby CPU to assume control since the standby CPU RIO head will never receive any I/O transaction message.
|
3
|
After any CPU error is detected:
|
Step
|
Action
|
Result
|
---|---|---|
1
|
After the primary CPU controller goes offline,
|
A health message from the standby CPU controller is the only message received by the standby CPU RIO Head.
|
2
|
Standby CPU controller listens to the high-speed data link for one scan.
|
|
3
|
If standby CPU controller hears nothing,
|
standby CPU knows that the cause must be on both the primary CPU Copro and primary CPU.
|
4
|
Standby CPU assumes control.
|
|