______________________ ODIN Intercom Firmware ______________________ These are the release notes for the firmware for the ODIN intercom. The firmware consists of the following files: - ODIN-Firmware.mot - Downloadable from AZedit - ODIN-Firmware.capfw - Downloadable from FWUT (Firmware Upload Tool) The firmware files consist of several individual firmware components (e.g. Bootloader, Main Application, FPGA). The versions of these individual firmware components can be viewed in the front panel menu under Status | System | ODIN Versions and also in AZedit under Status | ODIN Hardware | Component Versions. The firmware can be updated with AZedit or the FWUT, with one exception. The Audio FPGA is only included in the ODIN-Firmware.capfw file and must be downloaded using the FWUT. The firmware files in this release include the following firmware components: - Main Application: 1.4.0 - RVON Application: 1.3.0 - Bootloader: 1.1.2 - Main FPGA: 3.0.1 - Audio FPGA: 7.01.8010 (.capfw files only) - FP Application: 1.4.0 - FP FPGA: 0.3.0 Known Update Issues =================== * Updating the Audio FPGA If ODIN is running version 1.1.2 or earlier, and the Firmware Upload Tool is used to update just the Audio FPGA (i.e. by uploading Odin-Firmware-Audinate_vxxx.capfw), the frame does not reboot at the end of the procedure, and so the Audio FPGA is not updated. It is necessary to cycle power to the frame to force it to load the new version. This issue is fixed with ODIN version 1.1.3. * Updating the Main FPGA If ODIN has version 1.1.0 or earlier of the Boot Loader, and the Firmware Upload Tool is used to download new firmware that includes a new version of the Main FPGA, the FPGA image in flash is updated. However, after it finishes updating the flash and restarts, the FPGA is not reloaded with the new image, and continues to report the old version. In this case it is necessary to cycle power to the frame to force it to load the new version. This issue is fixed with Boot loader version 1.1.2. ______________ Change History ______________ Version 1.4.0 ============= * Added support for connections to OMS intercoms and DBP Digital Beltpacks * Preferred alpha size is now a single system-wide setting The preferred alpha size is used when displaying or editing the setup from the front panel. Previously, each frame could have its own alpha size. This setting is also used for any KP-Series keypanels that are configured to take the alpha size from the system. Version 1.3.0 ============= * Support listen volume adjustment for remote assignments With ODIN v1.3.0 and TM-10K v10.1.0, it is now possible to control the volume at which a panel listens to remote P-P and PL assignments. The intercom must first be reconfigured to enable remote volume adjustment. The following items are configurable: - The maximum number of ports that have access to removte volume adjustment - The maximum number of (non-unity) remote volume settings per port This is similar to configuring support for key labels. Once the intercom has been configured to allow remote volume adjustment, it can be enabled on individual ports by going to the Keypanel view, clicking the Edit button, selecting the Advanced tab, and selecting "Allow Remote Volume Adjustment". Remote volume adjustment can be performed from AZedit or from the keypanel. In AZedit, a new view allows the configuration of remote volumes. For the keypanel, listen volume adjustment for remote assignments is exactly like listen volume adjustment for local assignments. If the remote intercom does not support remote volume adjustment, the intercom can still adjust remote volumes - but this will not work if the trunk is forked at the far end. In that case, the remote assignment will be heard at 0dB. Remote listen volume adjustment is a licensed feature. * Fixed background noise problem when Comfort Noise Generator (CNG) was active for the G.722 codec Version 1.2.1 ============= * Fix handling of SIP Server phone line status After power-on or a reset, ODIN would communicate with a SIP server but would ignore the phone line status received from the SIP server. (One symptom of this is that SIP line alphas would change when an autodial number was selected, but would not revert when the SIP call was dropped.) The problem would persist until the SIP phone line mapping was edited in AZedit. Fixed. Version 1.2.0 ============= * Added support for ST2110-30 audio * In rare instances, removing the OMNEO configuration for a channel could cause the frame to reset. Fixed. * In a multi-frame system, a frame could erroneously report "Dante route detected on a trunk port" for a non-trunk port. Fixed. * In rare instances, the frame and a keypanel could disagree on the state of a key (e.g. the frame thinks a key is on even though it has been turned off at the keypanel). Fixed. Version 1.1.3 ============= * When resizing system, frame could have stuck message "System is rebooting" In a multi-frame system, depending on the intercom configuration, if you go to Options | Intercom Configuration and then Test and then Apply the settings (without actually changing anything), the frames would display the message "Please wait. The intercom is rebooting." However, the frames would end up not rebooting, but leaving the message stuck on the display. (If a screen saver was enabled, the message would be cleared when the screen saver kicked in.) Fixed. Related to this, in other configurations the frames would reboot even when it was not necessary. Fixed. * Handle Trunk Master communications for Ethernet links with high latency If the Ethernet link to the Trunk Master has a high round-trip latency, then the communications would not be reliable: - The link might not come up for a long time - The link might come up, but then get torn down in the middle of transferring data Fixed. Note that resolving the second issue requires upgrading the TM-10K to version 10.0.3 or later. With this change, trunking can be carried on circuits where the round-trip delay is upwards of 800 mSec. * Panels connected via RVON might not get all scroll list updates. Fixed. * Force a restart after updating the Audio FPGA If the Firmware Upload Tool is used to update just the Audio FPGA, the Audio FPGA would not get reloaded, and would continue to run the older version, until the user cycled power or forced a restart. Fixed. Version 1.1.2 ============= * Added new IPedit command: Reset authentication If a user (logged in with Admin permissions) holds down Shift+Ctrl while right-clicking the ODIN OMNEO device in the catalog on the left-hand side, the pop-up context menu now includes the item "Reset Authentication Table". This command requires IPedit v3.6.2 or later. * Added security for various commands The following operations have been re-implemented so that they are more secure, and difficult to spoof: - Clear channel statistics - Tear down channel(s) These commands now require IPedit v3.6.2 or later. * Added security features for compliance with California Senate Bill 327 For new devices, authentication must now be configured when first connecting to the device. This is necessary for compliance with California Law, re: SB327: An act to add Title 1.81.26 (commencing with Section 1798.91.04) to Part 4 of Division 3 of the California Civil Code, relating to information privacy. No change needs to be made to existing devices when this version of firmware is downloaded; however, if the authentication table is reset, or a factory reset is performed on the device, it will then enter the state where it requires authentication to be configured. AZedit: With AZedit v5.4.2 or later, AZedit will display a message notifying the user of this requirement, and prompting them to set up authentication. (Authentication can also be disabled, although this is not recommended.) Until authentication has been configured, the intercom will not allow changes to be made; and AZedit (v5.4.2 or later) will be in View (read-only) mode, where the various edit controls are all disabled, and most edit fields are shown with a pink background. With earlier versions of AZedit, no notification will be displayed, but the intercom will refuse to accept any changes until authentication has been configured (via the Authentication | Configuration menu option). IPedit: With IPedit v3.6.2 or later, IPedit will switch to the Authentication tab, and display a message notifying the user of this requirement. Until authentication has been configured, the device will not allow any changes to be made; and IPedit (v3.6.2 or later) will switch to read-only mode. With earlier versions of IPedit, no notification will be displayed, but the device will still refuse to accept any changes until authentication has been configured. * Added Open Source software component information Open Source software information (OSS components used and the corresponding license text) can be uploaded by typing in the device's IP address in any browser such as Firefox, Chrome, or Edge. * Allocation for port 1 of a different frame could be reported as "None" In a system of 3 frames or larger, AZedit could report that port 1 of one of the frames was unallocated. Fixed. This was an AZedit reporting instance. The unallocated port would always be in a frame different than the one to which AZedit was connected. The only consequence of this was that AZedit would be unable to configure the port-specific information (e.g. the OMNEO connection details, for an OMNEO). In this instance, the simple work-around was to have AZedit connect to the frame in which the port was located. * Fixed handling of PAP-5032's in large systems When connected to a system with a large number of ports and/or IFBs, a PAP-5032 might not receive all of its data at power-up. It would typically show default alphas (e.g. N003, F129) rather than the correct alphas for some of its key assignments. Fixed. * Channel might come up but pass no audio If a channel was up and passing audio, and then got torn down (e.g. partner device was reset, channel was reconfigured), when the channel next came up it was possible that it would not handle any inbound audio. (The DSP to Micro Overrun errors would count continuously.) Resetting the channel would not help; the only solution was to reset the card. Fixed. * Fixed audio playout problems There could be occasional audio artefacts on one or more channels, accompanied by DSP to Micro Overrun errors (as shown in AZedit and IPedit). Fixed. Note that the main FPGA must be updated to version 3.0.1 (included as part of this release) to resolve this problem. * Fixed possible reset problem If an RVON channel was connected to a device X, and device X tore down the link (e.g. because the link was reconfigured, or because IPedit connected to device X told it to tear down the link), in rare cases this could cause the RVON processor to reset. Fixed. * RVON channel doesn't come up after changing the Port Allocation Map If the port mapping for a channel was changed (it becomes an RVON channel, or the RVON instance changes), and there was already a configuration defined for the channel, the channel wouldn't come up until the configuration was edited. Fixed. Version 1.1.1 ============= * Links to RVON-16 / RVON-8 / RVON-C might not come up If the partner device for an ODIN RVON channel was a legacy RVON device (RVON-16, RVON-8, or RVON-C), the link would not come up if the IP address of one device was 128.0.0.0 or greater AND the IP address of the other device was 127.255.255.255 or less. Fixed. * Report UPL IFB override to PAP-5032 If an IFB program input is being set via a UPL statement, that information is now forwarded to any PAP-5032 panels. This matches the behavior of the LCP-102 and PAP-32. * Unicode alphas were sometimes displayed incorrectly on the front panel. Fixed. * UART communications errors were charged to the wrong keypanel UART overrun and framing errors for the AIO ports could be charged to the wrong keypanel - and they could be charged to a panel in a different frame, resulting in an alarm that couldn't be cleared. Fixed. * Results of AZedit "clear remote alphas" request were garbled In AZedit, if you went to Status | Remote Intercoms and performed one of the Clear operations, the results (the number of remote assignments that were deleted, and the number of affected keypanels) might be reported incorrectly. Fixed. Version 1.1.0 ============= * Added RVON support Each ODIN frame now supports up to 16 channels of RVON. Supported codecs are G.711A, G.711u, G.729AB, and G.722. (Currently, the G.722 codec can be used for connections to RVON+ cards and to other ODIN frames.) The Port Allocation Table is used to determine which ports are RVON ports, and the mapping between intercom ports and RVON channels. In IPedit, ODIN now appears as two separate devices: An OMNEO device and an RVON device. NOTE: RVON support requires version 3.0.0 of the main FPGA firmware. If the main FPGA version is 2.0.4 or earlier, AZedit will generate an alarm warning of this, and RVON connections will not be established. The main FPGA is automatically updated when the "ODIN-Firmware" package is downloaded. (It does not require the use of the Firmware Update Tool.) * Added PAP-5032 support The intercom can be reconfigured to support up to 64 PAP-5032 panels. PAP-5032 panels connect to standard keypanel ports, via AIO, OMNEO, or RVON. The PAP-5032 Mapping Table (available under the Options menu in AZedit) must be edited to define which ports are PAP-5032 ports. The PAP-5032 can be used as a standard PAP (to view and change which Program Inputs feed which IFBs); it can also be used to adjust program source and IFB output levels, and to monitor (listen to) program sources and IFBs. * SNMP now implements the OMNEO and RVON MIBs * OMNEO partner device type reported incorrectly In certain cases, after making configuration changes, IPedit would report a partner device type of "OTHER" rather than the correct value. Fixed. * Fixed device resets Two situations have been identified which could lead to an ODIN frame resetting: - If any keypanels were connected via AIO (and powered up) to an ODIN frame, the ODIN frame could sporadically reset. - If IPedit requested that a channel be torn down, it could cause the ODIN frame to reset. * OMNEO clock status reported incorrectly At start-up, the front panel's OMNEO clock status screen could show misleading information (e.g. good clock, even though no clock source is connected). Fixed. Version 1.0.4 ============= * If an AIO port is unterminated, the polling data could be coupled to the audio input for that port (typically sounding like a ticking noise at approximately 4 Hz). To prevent this, polling of an AIO port is now disabled if the keypanel type for that port is set to any of the following: - Virtual - SSA-324 / 424 - SSA-424A / DSI-2008 - Camera Port - Non-Data Port - IFB Port Note that a keypanel connected to such a port will not power up until the keypanel type is set to something different. * Fix: A large amount of Ethernet traffic could cause the frame to reset. (This issue was addressed in version 1.0.3, but different scenarios could still trigger the problem.) * Fix: Changing the device name twice within a short time frame could cause the frame to reset. * Fix: For the Japanese variant, using a "," in an auto-dial number would cause the keypanel to ignore the auto-dial number, and instead display the standard TIF dial menu. Fixed. Now a "," inserts a 1-second pause. Version 1.0.3 ============= * Fix: A large amount of Ethernet traffic could cause the frame (or the FP Application) could reset after an extended period of time. * Fix: If AZedit (connected via the Management Port) disables AZedit on the Management Port, then no further changes can be made (from any AZedit, IPedit, or Front Panel session) until the frame is restarted. Version 1.0.2 ============= * Fix: In some cases, DHCP packets generated by other network devices could cause ODIN to reset, even if ODIN's DHCP server was disabled. * Fix: In some cases, when making changes from IPedit, IPedit would fail with various errors (authentication failed, no response, etc.). Resending the changes would usually succeed. * Fix: If the Firmware Upload Tool was used to update the firmware, the LEC Application would not get updated. Version 1.0.1 ============= * Fix: In some cases, ODIN was unable to resolve the IP address of devices in a different subnet. * Fix: In some cases, OMNEO audio routes were not established when trying to establish multiple audio channels to one device. * Fix: If an OMNEO device changed its IP address twice, ODIN would not detect the second change. Furthermore, once this occurred, changing the Destination Device Name would cause ODIN to reset. * Fix: When clearing or acknowledging many alarms consecutively in the front panel menu it possible to cause ODIN to reset. Version 1.0.0 ============= * Initial release