In an M580 ERIO architecture, let’s consider 3 different use cases for Hot Standby hot swap:
1 - Send swap command via DDT control bit -> swap is OK, inputs are properly managed by default / by design
2 - Power off primary rack -> swap is OK, inputs are properly managed by default / by design
3 - Disconnect/remove both ERIO cables on the Primary CPU
Standby will take over, but Inputs bump to 0 could be visible depending on task duration.
If you are concerned by the 3rd use case, to work around this behavior you need to consider the drop health bit: e.g. RACK1_MOD_COM.DROP_COM_HEALTH
1 - Send swap command via DDT control bit -> swap is OK, inputs are properly managed by default / by design
2 - Power off primary rack -> swap is OK, inputs are properly managed by default / by design
3 - Disconnect/remove both ERIO cables on the Primary CPU
Standby will take over, but Inputs bump to 0 could be visible depending on task duration.
If you are concerned by the 3rd use case, to work around this behavior you need to consider the drop health bit: e.g. RACK1_MOD_COM.DROP_COM_HEALTH
Опубліковано для: Schneider Electric Україна
