Release Note Exigo 1.2

From exigoWiki
Revision as of 13:33, 20 December 2016 by Hlindem (talk | contribs) (Software Included in the EXIGO-1.2.3.13.zip file)
Jump to navigation Jump to search

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.

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, TA-10, TKIE-2, TKIS-2, IP-Speaker
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 Issues in RSTP Setup (MTN-995, MTN-967, MTN-960)

Network storm could be generated and destabilize the system during a combination of high system traffic and connection issues on the primary Flowire link to a panel.

Database on ENA Sometimes Lost when Device is Rebooted During High Traffic (MTN-1000)

Buffered configuration data was not written to configuration file if the device rebooted during high traffic situations.

AlphaSys Long Term Stability (MTN-965)

Reboot was observed after 3+ months of continuously monitoring the internal DSPs status.

Fault List and Attached Device List not Being Synchronized (MTN-973)

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 (MTN-1001)

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 Some Cases (MTN-966)

Due to tolerances of the line monitoring, sometimes the wrong fault state was reported. Now state "open" and "shorted" are both reported as "Line fault".

Fault LED Stops Indicating Local Faults if Local ESC1 is Down (MTN-1026)

Exigo Panels configured with fault-LED for indication of local fault does not show local fault if the ESC1 is down.

Alarm 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.

Panel Lock Up During Software Upgrade

There has been observation of panels not rebooting correctly after software upgrade.

CRM-V Panel Issues with LED behaviour

  • 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 Still in Suspended Monitoring after ESC1(s) Reboot

If monitoring was suspended on an ENAx and the controller rebooted, the monitoring would not be reactivated.

ECPIR Panel Activity LED Issues

  • 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.

Click Noise Heard when Canceling Live Speech with PTT

When releasing the ptt button on EMMAR-1H, the noise from the mechanical button could be heard on the PA system .

Tick Tone Test in Zone not Working for TKIS Kits

The tick tone test was not supported for the IP speakers.

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 Seconds 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 seconds timeout.

Known Issues

(Numbers in brackets are used for internal references).

INCA CRM-V Panels

The INCA-CRM-V 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.
Unsupported Features on the CRM-V panel

  • Call Escalation function. (AL-2354)
  • Panel lamp test. (AL-2352)
  • Zone select option "Deselect Zone(s) after activity". (AL-2025)

Issues with CRM LEDs Activity Indications

  • When triggering local mute control from a DAK on CRM-V, the green LED blinks. Should be steady. (AL-2353)
  • Recall record green LEDs active when mic test is performed. (AL-2351)
  • If mic test is stopped by timeout, green LED never goes off (this also goes for recall record LEDs). (AL-2351)
  • Red LED never active when performing mic test. (AL-2351)
  • 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. (AL-2349)
  • Zone select DAK keys can trigger activity indicators green led on other DAK keys with same zone. (AL-2591,AL-2590)
  • DAKs with message/program/live speech/alarm programmed with zones only triggers green LED when activated. (AL-2266)
  • Zone selection to all zones on DAK. No LED activity when audio activity in only some zones. (AL-2266)
  • LED for live speech lit when recall control active (and vice versa). (AL-2265)

Workaround: Avoid use of CRM-V panels for functionality that is not supported.

System Configuration Issues and Workaround

Adding a new non-existing panel to the system will only report "missing device" in the ESC1 A. (AL-2585)
(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 once.

Newly configured ENAx does not receive audio. (AL-2345)
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 status status from B (AL-2207)
Workaround: If changing the configuration of origin A/B system from where "System Status DAK LED" should be showing, reboot the panel involve to assure changes to take effect.

Device IP settings in WEB lost after upgrading from 4.1 to 4.2. Device stil has the same static IP address. (AL-1668)
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 removed from system for up to 5 minutes, (AL-2177)
Workaround: Unplug the panel or wait for 5 minutes.

ESC1 Call list: Program names longer than X characters will not be displayed correctly (AL-2531)
Workaround: Use short program names.

EMT - SNMP Community string allows space characters but SNMP does not support space. (AL-2550)
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. (AL-2209,AL-2458)
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". (AL-2610)
Workaround: Avoid using this configuration.

"Live Speech" from DAK with "Wait for PTT" and "Timeout", starts timer from when DAK is pressed, not when PTT is pressed. (AL-2197)
Workaround: Add additional 5 second Live Speech timeout when using this configuration. (Wait for PTT timeout is 5 sec.)

Call Escalation

In some situations the activity LEDs will not be correct when Call Escalation is activated and a panel is used for Live Speech with PTT or ReCall. (AL-2596, AL-2285, AL-2283)

Line Monitoring

During continuous LET monitoring and GA at high volume, LETs sometimes fail. (AL-2153)
Workaround: Always have suspend monitoring enabled.