10.36.9 Fault Slaves Mask
Each of the 213 pages has its own Fault Slaves Mask, whose bits are defined as follows:
| Page31 fault slave |
Page30 fault slave |
Page29 fault slave |
Page28 fault slave |
Page27 fault slave |
Page26 fault slave |
Page25 fault slave |
Page24 fault slave |
| Page23 fault slave |
Page22 fault slave |
Page21 fault slave |
Page20 fault slave |
Page19 fault slave |
Page18 fault slave |
Page17 fault slave |
Page16 fault slave |
| Page15 fault slave |
Page14 fault slave |
Page13 fault slave |
Page12 fault slave |
Page11 fault slave |
Page10 fault slave |
Page9 fault slave |
Page8 fault slave |
| Page7 fault slave |
Page6 fault slave |
Page5 fault slave |
Page4 fault slave |
Page3 fault slave |
Page2 fault slave |
Page1 fault slave |
Page0 fault slave |
Each page can have multiple fault slave pages. When a fault occurs on any pages, if its response is set to shut down, all slave pages are also shut down. If retries are specified for the master page, the slave page(s) remain running until all retries are exhausted. The slave pages are shut down using sequence off dependencies and TOFF_DELAY. The dependent pages do not perform any retries as a result of this action.
After being shut down, slave rails are latched off as if they had experienced the fault. To re-enable their outputs, an off command must be received before another on command is accepted. A status bit is set in their MFR_STATUS word indicating the reason they are latched off.
The fault slaves Mask is also part of graceful shutdown function, which is defined in the 10.6(MONITOR_CONFIG command).During the graceful shutdown period, the UV faults from those rails defined by the Mask are not logged and responded.