dual_output_el_switch_on_loss_of_all_output_interfaces
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
dual_output_el_switch_on_loss_of_all_output_interfaces [2024/05/23 16:51] – walkeradmin | dual_output_el_switch_on_loss_of_all_output_interfaces [2024/05/23 17:42] – [nCompass Changes] walkeradmin | ||
---|---|---|---|
Line 32: | Line 32: | ||
\\ | \\ | ||
---- | ---- | ||
- | ==== ==== | + | ==== nCompass Changes ==== |
+ | \\ | ||
+ | There are a couple of things we need to change in nCompass. One is the criticality of an alarm and the other is a config file. | ||
+ | \\ | ||
+ | \\ | ||
+ | We know that if one of our output interfaces goes down, the ELs will switch, for this reason we need to change the criticality of an interface down alarm. If we do this and nothing else, if both interfaces go down, then we will NOT get an encoder switch, so we need to change an nCompass file. | ||
+ | \\ | ||
+ | \\ | ||
+ | === Alarm Criticality === | ||
+ | \\ | ||
+ | By default, an interface down on an Encoder will result in a <color # | ||
+ | \\ | ||
+ | \\ | ||
+ | Unplug the first output data interface on the first EL, this will cause an Alarm in nCompass ESM. | ||
+ | \\ | ||
+ | \\ | ||
+ | {{ : | ||
+ | \\ | ||
+ | Because this system is encoding four services, I get an alarm for each service: | ||
+ | \\ | ||
+ | \\ | ||
+ | {{ : | ||
+ | \\ | ||
+ | Right click on one of the alarms and select ' | ||
+ | \\ | ||
+ | \\ | ||
+ | {{ : | ||
+ | \\ | ||
+ | Now select the ' | ||
+ | \\ | ||
+ | \\ | ||
+ | This fixes the issue where an encoder will switch on a single interface alarm, however at this time the encoder will never switch due to interface alarms, we need to make some more changes. | ||
+ | \\ | ||
+ | \\ | ||
+ | === nCompass AlarmHandlerService.exe.config === | ||
+ | \\ | ||
+ | The nCompass AlarmHandlerService.exe.config file is found in the following location: | ||
+ | \\ | ||
+ | C:\Program Files (x86)\MediaKind\nCompass Control\Bin | ||
+ | \\ | ||
+ | Open this file in notepad++ (or your favorite editor, just not notepad) and scroll down until you see the line: | ||
+ | \\ | ||
+ | <add key=" | ||
+ | \\ | ||
+ | It is line 165 in this example, this line does change over time as things are added to the nCompass Configuration. | ||
+ | \\ | ||
+ | \\ | ||
+ | {{ : | ||
+ | \\ | ||
+ | Add your EL output interfaces to this line - '< | ||
+ | \\ | ||
+ | \\ | ||
+ | What this means is that only when (in this example) eno3 and eno4 are failed, will the Encoder switch. | ||
+ | \\ | ||
+ | \\ | ||
+ | You can use this command to test the state of the encoder | ||
+ | \\ | ||
+ | \\ | ||
+ | http://< | ||
+ | \\ | ||
+ | \\ | ||
+ | {{ : | ||
+ | \\ | ||
+ | \\ | ||
+ | Scroll down until you see the enox information for your Encoders. | ||
+ | \\ | ||
+ | \\ | ||
+ | There are two important pieces of information here <color # | ||
+ | \\ | ||
+ | \\ | ||
+ | This means if you are trying to test to see how this works, it will not work with set down commands, only if you actually unplug the cable to the interface. | ||
+ | \\ | ||
+ | \\ | ||
+ | The operstate will show ' | ||
+ | \\ | ||
+ | \\ | ||
+ | Save the AlarmHandlerService.exe.config file and from Windows Services restart the Mediakind Alarm Handler service. | ||
+ | \\ | ||
+ | \\ | ||
+ | {{ : |
dual_output_el_switch_on_loss_of_all_output_interfaces.txt · Last modified: 2024/05/24 10:13 by walkeradmin