Whenever a command is issued a code appears in the event log for each control operation. These are the following codes and the reasons indicating the status of each control operation.
CODE | REASON |
0 | Command completed successfully |
1 | Local command blocked because switch position is intermediate or unknown |
2 | Local command blocked because switch position is already in correct state |
3 | Local command cancelled by user |
4 | Switch position did not change within configured maximum operation time |
5 | Command blocked by Head Unit interlocks, e.g. motor supply fault or battery low |
6 | Command failed due to timeout waiting for enable from Head Unit |
7 | Local command blocked because disabled by configuration |
8 | Local command blocked because local/remote status is unknown |
9 | Local command blocked because local/remote status is remote |
10 | Local command blocked because automation is ON |
11 | Remote command blocked because automation is ON |
12 | Sectionalizer command blocked because automation is OFF |
13 | Sectionalizer command blocked because local/remote status is unknown |
14 | Sectionalizer command blocked because local/remote status is remote |
15 | Unexpected command source (firmware error) |
16 | Remote command blocked because requested position is not a valid value |
17 | Command blocked because a command is already in progress for this module |
18 | Command blocked because the power shutdown signal is active |
19 | Command blocked because a command is already in progress for another module |
20 | Command blocked because measured switch position is intermediate or unknown |
21 | Command blocked because measured switch position is same as the requested position |
22 | Command blocked because earth switch position is not closed |
23 | Open command blocked because external input is false |
24 | Open command blocked because external input is true |
25 | Close command blocked because external input is false |
26 | Close command blocked because external input is true |
27 | Commands blocked because module behaviour mode is OFF |