ENA Amplifier - Monitoring

The ENA Amplifier provides extensive monitoring capabilities.

What can be supervised?

• Temperatures (always on). A number of temperature sensors in the ENA amplifier will generate error report if the temperature is outside valid range.
• Software faults (always on)
• AC Power and/or DC Power. Monitors the precense of the external power source. Monitoring must enabled in Amplifier Settings > Advanced Config > Power Source Monitoring section
• Internal voltages and currents. Monitored by default. Some monitoring parameters might be adjusted in Amplifier Settings > Advanced Config > Internal Power Monitoring Parameters section
• Amplifier shutdown (always on).
• Fan. Monitors the operation of the cooling fan inside the amplifier. Monitoring is enabled by default. Some monitoring parameters might be adjusted in Amplifier Settings > Advanced Config > Fan Monitoring Parameters section
• Ethernet port(s). Monitors that the ethernet link is up. Monitoring is enabled per ethernet port in Amplifier Settings > Advanced Config > Ethernet Switch Port Monitoring section
• Speaker Line (SLM) faults. The ENA amplifier can monitor impedance changes on each channel. This is used to detect fault such as load change, open/short and ground faults. A load change must be minimum 15% before it is reported as an error. The SLM can be individually turned on or off for each channel in Amplifier Settings > Line Control > Channel 1/2 > Line Monitoring. In order to make the Line Monitoring work, the speaker line needs to be calibrated. This is done from the GUI or the web interface of the ENA amplifier.
• LET (Line End Transponder). LET units can be connected on the loudspeaker line to ensure reliable monitoring of the line. There can be multiple LET units on one speaker line. The LET Monitoring can be individually turned on or off for each channel in Amplifier Settings > Line Control > Channel 1/2 > LET Monitoring. Here you also specify the quantity of LET units on the line.
• Remote Control Input (RCI). In order to monitor RCIs one have to connect two resistors as close as possible to the external switch/relay. The monitoring must be enabled per input in Amplifier Settings > RCO/RCI Config > RCIs section
• Remote Control Output (RCO). The control outputs can be monitored for short circuit and overload. Parameters might be adjusted in Amplifier Settings > RCO/RCI Config > RCOs section
• Headphone. Monitors that the headphone is connected at the front panel of the amplifier. Monitoring must be enabled in Amplifier Settings > Advanced Config > Headphone section
• Microphone. When the Line In is used for microphone, the presence of the microphone can be supervised. The monitoring is enabled in Amplifier Settings > Line Control > Line In > Phantom Microphone Monitoring.
• Line Input. When the Line In is set to "Line Input", the input can be used to detect Pilot Tone. The Pilot Tone monitoring is enabled in Amplifier Settings > Line Control > Line In > Pilot Tone Sensing.

Error reporting

Fault and Warning icons in Amplifier display

• Fault Relay: The Fault Relay on the back of the amplifier will trigger whenever there is an error. The relay will remain triggered as long as one or more errors are present.
• Amplifier GUI display: Faults are indicated in the Amplifier GUI display with a red icon. Warnings are indicated with a yellow icon. Use the Menu Selecetion Knob in front of the amplifier to navigate to Service > Local Message List to view current error messages
• Amplifier web interface: In the Faults section in the Amplifier Settings > Status menu there is a live update of current active faults. The page is automatically refreshed every 10 seconds.
• AlphaCom System Log: Amplifier errors are reported to the AlphaCom, which will forward the error reports via the System Log. Log data can be stored in a local log file on the AMC-IP board, or sent to external log recipient via SysLog, E-Mail or SNMP trap.
• AlphaCom Event Handler: Amplifier errors are reported by the Event Handler of the AlphaCom, event 43 - Station Fault Report. One can use the "subevent" to filter on specific fault types. The fault events can be used e.g. to generate fault messages to a display station.