Difference between revisions of "Release Note Exigo 1.2"
(→Software Included in the EXIGO-1.2.3.13.ZIP file) (Tag: Visual edit) |
Rlorentzen (talk | contribs) (→Line Monitoring) |
||
(51 intermediate revisions by 3 users not shown) | |||
Line 1: | Line 1: | ||
+ | = Exigo 1.2.3.14 = | ||
+ | |||
+ | Release: Official, available on request | ||
+ | Date: 2017-5-16 | ||
+ | Software Collection File: EXIGO-1.2.3.14.zip | ||
+ | |||
+ | ==Software Included in the EXIGO-1.2.3.14.zip file== | ||
+ | For upgrade procedures see PDF | ||
+ | document included in each product folder inside the EXIGO-1.2.3.14.zip file; | ||
+ | except VS-DEVICE-MIB, as this may vary between monitoring tools. | ||
+ | {| border="1" | ||
+ | |+ | ||
+ | |'''Product''' | ||
+ | |'''Version''' | ||
+ | |'''Description''' | ||
+ | |- | ||
+ | |EXI-Firmware | ||
+ | |4.2.3.14 | ||
+ | |Firmware for the following devices: ESC1(Secondary System Controller), ENA2200, ENA2400, ECPIR-3P, ECPIR-P, EAPIR-8, EAPFX-1, EAPFX-6, EAPII-1, EAPII-6, TKIS-2, TKIE-2 | ||
+ | |- | ||
+ | |AlphaSys Firmware | ||
+ | |12.2.3.13 | ||
+ | |Firmware for the ESC1 (Primary System Controller/AMC-IP board) | ||
+ | |- | ||
+ | |Exigo Management Tools | ||
+ | |1.2.3.7 | ||
+ | |Configuration tool, installed on a Windows PC | ||
+ | |- | ||
+ | |INCA Firmware | ||
+ | |2.20.3.6 | ||
+ | |Special Exigo software for the CRM-V based panel | ||
+ | |- | ||
+ | |VS-DEVICE-MIB | ||
+ | |201610190000Z | ||
+ | |SNMP MIB for Exigo EXI-Devices, for upload in 3rd-party SNMP based monitoring tools | ||
+ | |- | ||
+ | |} | ||
+ | <br> | ||
+ | |||
+ | == Improvements == | ||
+ | Support for new amplifier (ENA2x00) hardware, where Line input and Mic input have switched position. | ||
+ | |||
+ | == Known Issues == | ||
+ | |||
+ | === CRM-V Access Panels === | ||
+ | The CRM Access Panel is based on a different hardware and software than the other Exigo devices.<br> | ||
+ | Hence the functionality is limited compared to the native Exigo ECPIR panels. | ||
+ | |||
+ | '''Exigo Features Not Supported on the CRM-V Access Panel:''' | ||
+ | * Call Escalation function. | ||
+ | * Panel lamp test. | ||
+ | * Zone select option "Deselect Zone(s) after activity". | ||
+ | |||
+ | '''Deviant LED Behavior for the CRM-V Access Panel:''' | ||
+ | * When triggering local mute control from a DAK on CRM-V, the green LED blinks. Should be steady. | ||
+ | * Recall record green LEDs active when mic test is performed. | ||
+ | * If microphone test is stopped by timeout, green LED never goes off (this also goes for recall record LEDs). | ||
+ | * Red LED never active when performing mic test. | ||
+ | * DAK key with "Alarm stop with no zones", green led lit when alarm is active but DAK not possible to use for stopping the alarm. | ||
+ | * Zone select DAK keys can trigger activity indicators green led on other DAK keys with same zone. | ||
+ | * DAKs with message/program/live speech/alarm programmed with zones only triggers green LED when activated. | ||
+ | * Zone selection to all zones on DAK. No LED activity when audio activity in only some zones. | ||
+ | * LED for live speech lit when recall control active (and vice versa). | ||
+ | '''Workaround:''' Avoid use of CRM-V panels for functionality that is not supported. | ||
+ | |||
+ | === System Configuration (Commissioning) === | ||
+ | Adding a new non-existing panel to the system will only report "missing device" in the ESC1 A. (After first time registration of panel the "missing device" reports will always be displayed in both A and B controller.)<br> | ||
+ | '''Workaround:''' On commissioning, ensure that the panel has been registered. | ||
+ | |||
+ | Newly added ENAx does not receive audio. <br> | ||
+ | '''Workaround:''' On commissioning, ensure that ENAx is rebooted after first time configuration. | ||
+ | |||
+ | System Status DAK indicators - Incorrect status after reconfiguration from system status from A to system status from B <br> | ||
+ | '''Workaround:''' If changing the configuration of original A/B system from where "System Status DAK LED" should be showing, reboot the panel involved to assure changes take effect. | ||
+ | |||
+ | Device IP settings in WEB lost after upgrading from EXI-Firmware version 4.1 to 4.2. Device still has the same static IP address. <br> | ||
+ | '''Workaround:''' Exigo mode in device WEB has to be manually selected when going from 4.1 to 4.2. | ||
+ | |||
+ | ECPIR-3P behaves as registered, after being removed from system, for up to 5 minutes <br> | ||
+ | '''Workaround:''' Unplug the panel or wait for 5 minutes. | ||
+ | |||
+ | ESC1 Call list: Long program names will not be displayed correctly <br> | ||
+ | '''Workaround:''' Limit program names to 10 standard characters. | ||
+ | |||
+ | EMT - SNMP Community string allows space character but SNMP does not support space. <br> | ||
+ | '''Workaround:''' Avoid using space in the community string. | ||
+ | |||
+ | It is not possible to remove the options "Overwrite Destination" or "Timeout" from an already configured Call Escalation DAK without rebooting. <br> | ||
+ | '''Workaround:''' Panel must be rebooted after updated configuration sent from EMT. | ||
+ | |||
+ | Call option "Release delay" does not work in combination with call option "Wait for PTT". <br> | ||
+ | '''Workaround:''' Avoid using this combination. | ||
+ | |||
+ | "Live Speech" from DAK with "Wait for PTT" and "Timeout", starts timer from when DAK is pressed, not when PTT is pressed. <br> | ||
+ | '''Workaround:''' Add additional 5 second Live Speech timeout when using this configuration (Wait for PTT timeout is 5 sec). | ||
+ | |||
+ | === Line Monitoring === | ||
+ | During continuous LET monitoring and GA at high volume, LETs sometimes fail. <br> | ||
+ | '''Workaround:''' Always have "Suspend Monitoring" enabled. | ||
+ | |||
= Exigo 1.2.3.13 = | = Exigo 1.2.3.13 = | ||
Release: Official, available on request | Release: Official, available on request | ||
Date: 2016-12-19 | Date: 2016-12-19 | ||
− | Software Collection File: EXIGO-1.2.3.13. | + | Software Collection File: EXIGO-1.2.3.13.zip |
− | ==Software Included in the EXIGO-1.2.3.13. | + | ==Software Included in the EXIGO-1.2.3.13.zip file== |
− | + | For upgrade procedures see PDF | |
+ | document included in each product folder inside the EXIGO-1.2.3.13.zip file; | ||
+ | except VS-DEVICE-MIB, as this may vary between monitoring tools. | ||
{| border="1" | {| border="1" | ||
|+ | |+ | ||
Line 15: | Line 117: | ||
|EXI-Firmware | |EXI-Firmware | ||
|4.2.3.13 | |4.2.3.13 | ||
− | |Firmware for the following devices: ESC1(Secondary System Controller), ENA2200, ENA2400, ECPIR-3P, ECPIR-P, EAPIR-8, EAPFX-1, EAPFX-6, EAPII-1, EAPII-6 | + | |Firmware for the following devices: ESC1(Secondary System Controller), ENA2200, ENA2400, ECPIR-3P, ECPIR-P, EAPIR-8, EAPFX-1, EAPFX-6, EAPII-1, EAPII-6, TKIS-2 |
|- | |- | ||
|AlphaSys Firmware | |AlphaSys Firmware | ||
Line 27: | Line 129: | ||
|INCA Firmware | |INCA Firmware | ||
|2.20.3.6 | |2.20.3.6 | ||
− | | | + | |Special Exigo software for the CRM-V based panel |
|- | |- | ||
|VS-DEVICE-MIB | |VS-DEVICE-MIB | ||
Line 36: | Line 138: | ||
<br> | <br> | ||
<br> | <br> | ||
− | |||
− | == | + | == Corrections == |
− | === Flowire | + | === Flowire, RSTP Setup === |
− | Network storm could be generated and destabilize the system during a combination of high system traffic and connection | + | Network storm could be generated and destabilize the system during a combination of high system traffic and connection instability on the primary Flowire link to an Access Panel. |
− | === Database on ENA Sometimes Lost when Device is Rebooted During High Traffic | + | |
+ | === Database on ENA Sometimes Lost when Device is Rebooted During High Traffic === | ||
Buffered configuration data was not written to configuration file if the device rebooted during high traffic situations. | Buffered configuration data was not written to configuration file if the device rebooted during high traffic situations. | ||
− | === | + | === ESC1 Long Term Stability === |
− | Reboot | + | Reboot of ESC1 has been observed after 3+ months of continuously monitoring the internal DSPs status. |
− | === Fault List and Attached Device List | + | === ESC1 Fault List and Attached Device List Not Being Synchronized === |
− | After reset of an A/B system, B devices not connected would generate a system fault message in the A Controller | + | After reset of an A/B system, B devices not connected would generate a system fault message in the A Controller (should only report to B). <br> |
− | === White Noise on Devices | + | === White Noise on Devices Running EXI-Firmware === |
− | The internal audio driver could enter a faulty state resulting in noise from audio sources. The white noise could occur when the device was sourcing audio to "Live Speech" or "Program" | + | The internal audio driver could enter a faulty state, resulting in noise from audio sources. The white noise could occur when the device was sourcing audio to "Live Speech" or "Program" for all devices running EXI-Firmware. |
− | === Line Monitoring Reports Wrong Fault State in | + | === ENAx Line Monitoring Reports Wrong Fault State in Complex Speaker Line Configurations === |
− | Due to tolerances of the line monitoring sometimes the wrong fault state | + | Due to tolerances of the line monitoring, sometimes the wrong fault state has been reported. Now state "Open" and "Shorted" are both reported as "Line fault".<br> |
− | === Fault LED Stops Indicating Local Faults if Local | + | === Access Panel Fault LED Stops Indicating Local Faults if Local ESC1 is Down === |
− | Exigo Panels configured with fault-LED for indication of local fault does not show local fault if the | + | Exigo Panels configured with fault-LED for indication of local fault does not show local fault if the ESC1 is down. <br> |
− | === | + | === Audio Activity stops After Release Delay Timeout === |
− | Exigo Calls using the release delay feature would terminate if the call was re-started within the release delay timeout period. | + | Exigo Calls using the release delay feature would terminate if the call was re-started within the release delay timeout period. |
− | === Panel | + | === CRM-V Access Panel, LED behavior === |
− | + | * The activity range configuration for the Zone selection action was not working on the CRM-V station. | |
+ | * Microphone LED blinking when connected and with no faults in the system. <br> | ||
− | === | + | ===ENAx Remains in Suspended Monitoring if ESC1 Reboots During Suspension=== |
− | + | If monitoring was suspended on an ENAx and the controller rebooted, the monitoring would not be reactivated. <br> | |
− | |||
− | + | === ECPIR Access Panel, Activity LED Behaviour === | |
− | |||
− | |||
− | === ECPIR Panel Activity LED | ||
*Configuring and activating several call setup DAK keys with partly overlapping zones could indicate queued state on wrong DAK key.<br> | *Configuring and activating several call setup DAK keys with partly overlapping zones could indicate queued state on wrong DAK key.<br> | ||
− | *Using call escalation, with the option | + | *Using call escalation, with the option "always include" enabled, resulted in disabling the green LED indicating Live Speech when the call was escalated.<br> |
*Microphone Test: Call LED was lit when toggled off during playback. | *Microphone Test: Call LED was lit when toggled off during playback. | ||
− | + | === Tick Tone Test in Zone not Working for TKIS Kits and IP Speakers === | |
− | + | The tick tone test was not supported for TKIS kits and IP speakers. <br> | |
− | |||
− | === Tick Tone Test in Zone not Working for TKIS Kits === | ||
− | The tick tone test was not supported for | ||
− | === Drift in Audio Between A and B System === | + | === ENAx, Drift in Audio Between A and B System === |
The audio from A and B amplifiers could drift, if a call was active for a long time, due to increasing jitter buffer variations between the amplifiers. | The audio from A and B amplifiers could drift, if a call was active for a long time, due to increasing jitter buffer variations between the amplifiers. | ||
− | === Live Speech with Wait for PTT - | + | === Live Speech with Wait for PTT - Not Possible to Toggle off Before 5 Second Timeout === |
− | When starting a Live Speech with the option " | + | When starting a Live Speech with the option "Wait for PTT" enabled, without pressing the PTT-button, the waiting live speech could not be canceled before a 5 second timeout. <br> |
== Known Issues == | == Known Issues == | ||
− | ( | + | (AL-numbers in brackets are used for internal references). |
− | === | + | === CRM-V Access Panels === |
− | The | + | The CRM Access Panel is based on a different hardware and software than the other Exigo devices. <br> |
Hence the functionality is limited compared to the native Exigo ECPIR panels.<br> | Hence the functionality is limited compared to the native Exigo ECPIR panels.<br> | ||
− | ''' | + | '''Exigo Features Not Supported on the CRM-V Access Panel:''' |
− | *Call Escalation function. | + | * Call Escalation function. |
− | *Panel lamp test. | + | * Panel lamp test. |
− | *Zone select option "Deselect Zone(s) after activity". | + | * Zone select option "Deselect Zone(s) after activity". |
− | ''' | + | '''Deviant LED Bahaviour''' '''for the CRM-V Access Panel:''' |
− | *When triggering local mute control from a DAK on CRM-V, the green LED blinks. Should be steady. | + | * When triggering local mute control from a DAK on CRM-V, the green LED blinks. Should be steady. |
− | *Recall record green LEDs active when mic test is performed. | + | * Recall record green LEDs active when mic test is performed. |
− | *If | + | * If microphone test is stopped by timeout, green LED never goes off (this also goes for recall record LEDs). |
− | *Red LED never active when performing mic test. | + | * Red LED never active when performing mic test. |
− | *DAK key with "Alarm stop with no zones", green led lit when alarm is active but DAK not possible to use for stopping the alarm. | + | * DAK key with "Alarm stop with no zones", green led lit when alarm is active but DAK not possible to use for stopping the alarm. |
− | *Zone select DAK keys can trigger activity indicators green led on other DAK keys with same zone. | + | * Zone select DAK keys can trigger activity indicators green led on other DAK keys with same zone. |
− | *DAKs with message/program/live speech/alarm programmed with zones only triggers green LED when activated. | + | * DAKs with message/program/live speech/alarm programmed with zones only triggers green LED when activated. |
− | *Zone selection to all zones on DAK. No LED activity when audio activity in only some zones. | + | * Zone selection to all zones on DAK. No LED activity when audio activity in only some zones. |
− | * | + | * LED for live speech lit when recall control active (and vice versa). |
'''Workaround:''' Avoid use of CRM-V panels for functionality that is not supported. | '''Workaround:''' Avoid use of CRM-V panels for functionality that is not supported. | ||
− | === System Configuration | + | === System Configuration (Commissioning) === |
− | Adding a new non-existing panel to the system will only report "missing device" in the | + | Adding a new non-existing panel to the system will only report "missing device" in the ESC1 A. <br> |
(After first time registration of panel the "missing device" reports will always be displayed in both A and B controller.) <br> | (After first time registration of panel the "missing device" reports will always be displayed in both A and B controller.) <br> | ||
− | '''Workaround:''' On commissioning, ensure that the panel has been registered | + | '''Workaround:''' On commissioning, ensure that the panel has been registered.<br> |
<br> | <br> | ||
− | Newly | + | Newly added ENAx does not receive audio. <br> |
− | '''Workaround:''' On commissioning, ensure that | + | '''Workaround:''' On commissioning, ensure that ENAx is rebooted after first time configuration. <br> |
<br> | <br> | ||
− | System Status DAK indicators - Incorrect status after reconfiguration from system status from A to | + | System Status DAK indicators - Incorrect status after reconfiguration from ''system status from A'' to ''system status from B'' <br> |
− | '''Workaround:''' If changing the configuration of | + | '''Workaround:''' If changing the configuration of original A/B system from where "System Status DAK LED" should be showing, reboot the panel involved to assure changes take effect. <br> |
<br> | <br> | ||
− | Device IP settings in WEB lost after upgrading from 4.1 to 4.2. Device | + | Device IP settings in WEB lost after upgrading from EXI-Firmware version 4.1 to 4.2. Device still has the same static IP address. <br> |
− | '''Workaround:''' Exigo mode | + | '''Workaround:''' Exigo mode in device WEB has to be manually selected when going from 4.1 to 4.2.<br> |
<br> | <br> | ||
− | ECPIR-3P | + | ECPIR-3P behaves as registered, after being removed from system, for up to 5 minutes, <br> |
'''Workaround:''' Unplug the panel or wait for 5 minutes.<br> | '''Workaround:''' Unplug the panel or wait for 5 minutes.<br> | ||
<br> | <br> | ||
− | + | ESC1 Call list: Long program names will not be displayed correctly <br> | |
− | '''Workaround:''' | + | '''Workaround:''' Limit program names to 10 standard characters<br> |
− | |||
− | |||
− | |||
<br> | <br> | ||
− | + | EMT - SNMP Community string allows space character but SNMP does not support space. <br> | |
− | '''Workaround:''' Panel must be rebooted after updated configuration sent from EMT. | + | '''Workaround:''' Avoid using space in the community string.<br><br> |
+ | It is not possible to remove the options "Overwrite Destination" or "Timeout" from an already configured Call Escalation DAK without rebooting. <br> | ||
+ | '''Workaround:''' Panel must be rebooted after updated configuration sent from EMT. | ||
− | Call option "Release delay" does not work in combination with call option " | + | Call option "Release delay" does not work in combination with call option "Wait for PTT". <br> |
− | '''Workaround:''' Avoid using this | + | '''Workaround:''' Avoid using this combination. |
− | "Live Speech" from DAK | + | "Live Speech" from DAK with "Wait for PTT" and "Timeout", starts timer from when DAK is pressed, not when PTT is pressed. <br> |
− | '''Workaround:''' Add additional 5 second Live Speech timeout when using this configuration | + | '''Workaround:''' Add additional 5 second Live Speech timeout when using this configuration (Wait for PTT timeout is 5 sec). |
− | === | + | ===Line Monitoring === |
− | + | During continuous LET monitoring and GA at high volume, LETs sometimes fail. <br> | |
+ | '''Workaround:''' Always have "Suspend Monitoring" enabled.<br> | ||
− | + | [[Category:Release notes]] | |
− | |||
− |
Latest revision as of 08:00, 10 May 2022
Contents
- 1 Exigo 1.2.3.14
- 2 Exigo 1.2.3.13
- 2.1 Software Included in the EXIGO-1.2.3.13.zip file
- 2.2 Corrections
- 2.2.1 Flowire, RSTP Setup
- 2.2.2 Database on ENA Sometimes Lost when Device is Rebooted During High Traffic
- 2.2.3 ESC1 Long Term Stability
- 2.2.4 ESC1 Fault List and Attached Device List Not Being Synchronized
- 2.2.5 White Noise on Devices Running EXI-Firmware
- 2.2.6 ENAx Line Monitoring Reports Wrong Fault State in Complex Speaker Line Configurations
- 2.2.7 Access Panel Fault LED Stops Indicating Local Faults if Local ESC1 is Down
- 2.2.8 Audio Activity stops After Release Delay Timeout
- 2.2.9 CRM-V Access Panel, LED behavior
- 2.2.10 ENAx Remains in Suspended Monitoring if ESC1 Reboots During Suspension
- 2.2.11 ECPIR Access Panel, Activity LED Behaviour
- 2.2.12 Tick Tone Test in Zone not Working for TKIS Kits and IP Speakers
- 2.2.13 ENAx, Drift in Audio Between A and B System
- 2.2.14 Live Speech with Wait for PTT - Not Possible to Toggle off Before 5 Second Timeout
- 2.3 Known Issues
Exigo 1.2.3.14
Release: Official, available on request Date: 2017-5-16 Software Collection File: EXIGO-1.2.3.14.zip
Software Included in the EXIGO-1.2.3.14.zip file
For upgrade procedures see PDF document included in each product folder inside the EXIGO-1.2.3.14.zip file; except VS-DEVICE-MIB, as this may vary between monitoring tools.
Product | Version | Description |
EXI-Firmware | 4.2.3.14 | Firmware for the following devices: ESC1(Secondary System Controller), ENA2200, ENA2400, ECPIR-3P, ECPIR-P, EAPIR-8, EAPFX-1, EAPFX-6, EAPII-1, EAPII-6, TKIS-2, TKIE-2 |
AlphaSys Firmware | 12.2.3.13 | Firmware for the ESC1 (Primary System Controller/AMC-IP board) |
Exigo Management Tools | 1.2.3.7 | Configuration tool, installed on a Windows PC |
INCA Firmware | 2.20.3.6 | Special Exigo software for the CRM-V based panel |
VS-DEVICE-MIB | 201610190000Z | SNMP MIB for Exigo EXI-Devices, for upload in 3rd-party SNMP based monitoring tools |
Improvements
Support for new amplifier (ENA2x00) hardware, where Line input and Mic input have switched position.
Known Issues
CRM-V Access Panels
The CRM Access Panel is based on a different hardware and software than the other Exigo devices.
Hence the functionality is limited compared to the native Exigo ECPIR panels.
Exigo Features Not Supported on the CRM-V Access Panel:
- Call Escalation function.
- Panel lamp test.
- Zone select option "Deselect Zone(s) after activity".
Deviant LED Behavior for the CRM-V Access Panel:
- When triggering local mute control from a DAK on CRM-V, the green LED blinks. Should be steady.
- Recall record green LEDs active when mic test is performed.
- If microphone test is stopped by timeout, green LED never goes off (this also goes for recall record LEDs).
- Red LED never active when performing mic test.
- DAK key with "Alarm stop with no zones", green led lit when alarm is active but DAK not possible to use for stopping the alarm.
- Zone select DAK keys can trigger activity indicators green led on other DAK keys with same zone.
- DAKs with message/program/live speech/alarm programmed with zones only triggers green LED when activated.
- Zone selection to all zones on DAK. No LED activity when audio activity in only some zones.
- LED for live speech lit when recall control active (and vice versa).
Workaround: Avoid use of CRM-V panels for functionality that is not supported.
System Configuration (Commissioning)
Adding a new non-existing panel to the system will only report "missing device" in the ESC1 A. (After first time registration of panel the "missing device" reports will always be displayed in both A and B controller.)
Workaround: On commissioning, ensure that the panel has been registered.
Newly added ENAx does not receive audio.
Workaround: On commissioning, ensure that ENAx is rebooted after first time configuration.
System Status DAK indicators - Incorrect status after reconfiguration from system status from A to system status from B
Workaround: If changing the configuration of original A/B system from where "System Status DAK LED" should be showing, reboot the panel involved to assure changes take effect.
Device IP settings in WEB lost after upgrading from EXI-Firmware version 4.1 to 4.2. Device still has the same static IP address.
Workaround: Exigo mode in device WEB has to be manually selected when going from 4.1 to 4.2.
ECPIR-3P behaves as registered, after being removed from system, for up to 5 minutes
Workaround: Unplug the panel or wait for 5 minutes.
ESC1 Call list: Long program names will not be displayed correctly
Workaround: Limit program names to 10 standard characters.
EMT - SNMP Community string allows space character but SNMP does not support space.
Workaround: Avoid using space in the community string.
It is not possible to remove the options "Overwrite Destination" or "Timeout" from an already configured Call Escalation DAK without rebooting.
Workaround: Panel must be rebooted after updated configuration sent from EMT.
Call option "Release delay" does not work in combination with call option "Wait for PTT".
Workaround: Avoid using this combination.
"Live Speech" from DAK with "Wait for PTT" and "Timeout", starts timer from when DAK is pressed, not when PTT is pressed.
Workaround: Add additional 5 second Live Speech timeout when using this configuration (Wait for PTT timeout is 5 sec).
Line Monitoring
During continuous LET monitoring and GA at high volume, LETs sometimes fail.
Workaround: Always have "Suspend Monitoring" enabled.
Exigo 1.2.3.13
Release: Official, available on request Date: 2016-12-19 Software Collection File: EXIGO-1.2.3.13.zip
Software Included in the EXIGO-1.2.3.13.zip file
For upgrade procedures see PDF document included in each product folder inside the EXIGO-1.2.3.13.zip file; except VS-DEVICE-MIB, as this may vary between monitoring tools.
Product | Version | Description |
EXI-Firmware | 4.2.3.13 | Firmware for the following devices: ESC1(Secondary System Controller), ENA2200, ENA2400, ECPIR-3P, ECPIR-P, EAPIR-8, EAPFX-1, EAPFX-6, EAPII-1, EAPII-6, TKIS-2 |
AlphaSys Firmware | 12.2.3.13 | Firmware for the ESC1 (Primary System Controller/AMC-IP board) |
Exigo Management Tools | 1.2.3.7 | Configuration tool, installed on a Windows PC |
INCA Firmware | 2.20.3.6 | Special Exigo software for the CRM-V based panel |
VS-DEVICE-MIB | 201610190000Z | SNMP MIB for Exigo EXI-Devices, for upload in 3rd-party SNMP based monitoring tools |
Corrections
Flowire, RSTP Setup
Network storm could be generated and destabilize the system during a combination of high system traffic and connection instability on the primary Flowire link to an Access Panel.
Database on ENA Sometimes Lost when Device is Rebooted During High Traffic
Buffered configuration data was not written to configuration file if the device rebooted during high traffic situations.
ESC1 Long Term Stability
Reboot of ESC1 has been observed after 3+ months of continuously monitoring the internal DSPs status.
ESC1 Fault List and Attached Device List Not Being Synchronized
After reset of an A/B system, B devices not connected would generate a system fault message in the A Controller (should only report to B).
White Noise on Devices Running EXI-Firmware
The internal audio driver could enter a faulty state, resulting in noise from audio sources. The white noise could occur when the device was sourcing audio to "Live Speech" or "Program" for all devices running EXI-Firmware.
ENAx Line Monitoring Reports Wrong Fault State in Complex Speaker Line Configurations
Due to tolerances of the line monitoring, sometimes the wrong fault state has been reported. Now state "Open" and "Shorted" are both reported as "Line fault".
Access Panel Fault LED Stops Indicating Local Faults if Local ESC1 is Down
Exigo Panels configured with fault-LED for indication of local fault does not show local fault if the ESC1 is down.
Audio Activity stops After Release Delay Timeout
Exigo Calls using the release delay feature would terminate if the call was re-started within the release delay timeout period.
CRM-V Access Panel, LED behavior
- The activity range configuration for the Zone selection action was not working on the CRM-V station.
- Microphone LED blinking when connected and with no faults in the system.
ENAx Remains in Suspended Monitoring if ESC1 Reboots During Suspension
If monitoring was suspended on an ENAx and the controller rebooted, the monitoring would not be reactivated.
ECPIR Access Panel, Activity LED Behaviour
- Configuring and activating several call setup DAK keys with partly overlapping zones could indicate queued state on wrong DAK key.
- Using call escalation, with the option "always include" enabled, resulted in disabling the green LED indicating Live Speech when the call was escalated.
- Microphone Test: Call LED was lit when toggled off during playback.
Tick Tone Test in Zone not Working for TKIS Kits and IP Speakers
The tick tone test was not supported for TKIS kits and IP speakers.
ENAx, Drift in Audio Between A and B System
The audio from A and B amplifiers could drift, if a call was active for a long time, due to increasing jitter buffer variations between the amplifiers.
Live Speech with Wait for PTT - Not Possible to Toggle off Before 5 Second Timeout
When starting a Live Speech with the option "Wait for PTT" enabled, without pressing the PTT-button, the waiting live speech could not be canceled before a 5 second timeout.
Known Issues
(AL-numbers in brackets are used for internal references).
CRM-V Access Panels
The CRM Access Panel is based on a different hardware and software than the other Exigo devices.
Hence the functionality is limited compared to the native Exigo ECPIR panels.
Exigo Features Not Supported on the CRM-V Access Panel:
- Call Escalation function.
- Panel lamp test.
- Zone select option "Deselect Zone(s) after activity".
Deviant LED Bahaviour for the CRM-V Access Panel:
- When triggering local mute control from a DAK on CRM-V, the green LED blinks. Should be steady.
- Recall record green LEDs active when mic test is performed.
- If microphone test is stopped by timeout, green LED never goes off (this also goes for recall record LEDs).
- Red LED never active when performing mic test.
- DAK key with "Alarm stop with no zones", green led lit when alarm is active but DAK not possible to use for stopping the alarm.
- Zone select DAK keys can trigger activity indicators green led on other DAK keys with same zone.
- DAKs with message/program/live speech/alarm programmed with zones only triggers green LED when activated.
- Zone selection to all zones on DAK. No LED activity when audio activity in only some zones.
- LED for live speech lit when recall control active (and vice versa).
Workaround: Avoid use of CRM-V panels for functionality that is not supported.
System Configuration (Commissioning)
Adding a new non-existing panel to the system will only report "missing device" in the ESC1 A.
(After first time registration of panel the "missing device" reports will always be displayed in both A and B controller.)
Workaround: On commissioning, ensure that the panel has been registered.
Newly added ENAx does not receive audio.
Workaround: On commissioning, ensure that ENAx is rebooted after first time configuration.
System Status DAK indicators - Incorrect status after reconfiguration from system status from A to system status from B
Workaround: If changing the configuration of original A/B system from where "System Status DAK LED" should be showing, reboot the panel involved to assure changes take effect.
Device IP settings in WEB lost after upgrading from EXI-Firmware version 4.1 to 4.2. Device still has the same static IP address.
Workaround: Exigo mode in device WEB has to be manually selected when going from 4.1 to 4.2.
ECPIR-3P behaves as registered, after being removed from system, for up to 5 minutes,
Workaround: Unplug the panel or wait for 5 minutes.
ESC1 Call list: Long program names will not be displayed correctly
Workaround: Limit program names to 10 standard characters
EMT - SNMP Community string allows space character but SNMP does not support space.
Workaround: Avoid using space in the community string.
It is not possible to remove the options "Overwrite Destination" or "Timeout" from an already configured Call Escalation DAK without rebooting.
Workaround: Panel must be rebooted after updated configuration sent from EMT.
Call option "Release delay" does not work in combination with call option "Wait for PTT".
Workaround: Avoid using this combination.
"Live Speech" from DAK with "Wait for PTT" and "Timeout", starts timer from when DAK is pressed, not when PTT is pressed.
Workaround: Add additional 5 second Live Speech timeout when using this configuration (Wait for PTT timeout is 5 sec).
Line Monitoring
During continuous LET monitoring and GA at high volume, LETs sometimes fail.
Workaround: Always have "Suspend Monitoring" enabled.