______________________________________ ADAM Dual Bus Expander, Version 1.24.0 ______________________________________ File type: Motorola File offset: 0 EPROM type: 29F040 Checksums: Standard: CRC = 7d58 J6: Not yet released ________________ Increased Memory ________________ The original DBX card has 2M of configuration flash and 32M of DRAM installed. A revised version of the DBX card doubles this amount, to 4M of configuration flash and 32M of DRAM. Support for the larger amount of memory is included starting with the following versions: - DBX version 1.19.3 - DBX Boot Loader version 0.1.0 These are the minimum version requirements for DBX cards with the additional memory. Cards with the smaller amount of memory can use any version of DBX firmware and any version of DBX Boot Loader firmware. ____________ Update Notes ____________ The complete intercom configuration is stored in configuration flash in the frame 1 DBX cards (slots 8 and 9). Portions of the configuration are also kept in the Peripheral Controllers (e.g. alphas, key assignments). When updating a DBX system, it is possible for the DBX cards and the PCs to have different configurations (e.g. if the DBX or the PC performs a first birthday). In this case, the DBX cards' copy of the setup is used. The DBX and the PC will sync their data when they first start communicating. If this is the case, the following procedure is recommended: - Wait for the PC to come up to date. (AZedit will not be able to communicate with the intercom until the PC is up to date.) - In AZedit, go on-line. - Make a minor change in AZedit (e.g. change a key assignment). Send the change to the intercom. This will ensure that the Peripheral Controllers have up-to-date configuration flash. - Reset both Peripheral Controllers. When updating from DBX 1.5.0 / Periph 10.5.0 or earlier, the Peripheral Controllers should be updated to v10.11.0 *before* updating the frame 1 DBX cards. It is not important whether the slave frame DBX cards are updated before or after the DBX / PC cards. When updating from DBX v1.12.0 or earlier, slave frame DBX cards must be updated before the DBX cards in frame 1. _______________ Boot Downloader _______________ The DBX firmware is composed of 2 pieces: A boot downloader, and the fully-functional DBX firmware. The "dbx.hex" file can be downloaded via AZedit. This version does not include the boot downloader. The U21 and U22 files are EPROM images, to be used when using a device programmer to program the EPROMs. These images cannot be downloaded via AZedit. It is possible to update the boot downloader by downloading the DBX from AZedit; instructions for doing that are included with the boot downloader image, which is distributed separately. _____________ Compatibility _____________ DBX: Requires V1.3 (V1.4 recommended) of the FPGA image in the socketed EPC1 chip at U69 in all DBX cards. Requires version 1.24.x in all DBX cards. When upgrading from a previous version, DBX cards in slave frames should be updated before updating the DBX cards in frame 1. The DBX will come up with a blank setup when upgrading from version 1.22.x or earlier, but will remember the system size. It will perform a first birthday when upgrading from version 1.12.2 or earlier, and will resize itself to a 2-frame, 480-squared system. PeriphII-e Requires version 1.24.x. The Japanese build of the DBX requires a Japanese build of the PeriphII-e. Peripheral Controller: Requires version 10.24.x. The Japanese build of the DBX requires a Japanese build of the Peripheral Controller. AZedit: Requires version 3.9.0 or later for full support of all features. A Unicode build of AZedit is required for full access to all features when talking to a Japanese version of Controller firmware. AIO-8 Card: Requires version 10.3.0 or later. Requires version 10.3.6 or later for support of keypanel colors. Requires version 10.4.0 or later for support of a separate CWW key. Requires the Japanese version of the AIO card for Japanese versions of DBX firmware. AIO firmware version 9.x.x can be used while upgrading. AIO-16 Card: Requires AIO-16 version 1.0.0 or later. Requires version 1.1.0 or later for VOX support. Requires version 1.1.4 or later for support of keypanel colors. Requires version 1.2.0 or later for support of a separate CWW key. Requires a Kanji build of the AIO-16 firmware for Japanese versions of firmware. GPIO-16: Supports any version of GPIO-16. Trunk Master: Requires Trunk Master version 7.3.0 or later. Japanese builds require TM-2000 version 8.5.0 or later. Requires version 8.8.0 for support of more resources across trunking. Requires version 8.9.0 for MC/TM communications via Ethernet PAP-32: Works with any version on J3. PAP-32's connected to J4 require v0.0.2 or later, since they are polled at 9600 baud. Requires v0.0.3 or later in order to be able to configure the PAP-32 from AZedit. ____________ DIP Switches ____________ Switch 1: Closed = disable link A test audio Switch 2: Closed = disable link B test audio (see v1.0.4 description) Switches 6-3: Unused, should be left open Switch 7: Closed = frame 1, Open = slave frame Switch 8: Must be open ___________________ Memory Requirements ___________________ Systems which use DBX cards with the original (smaller) amounts of memory are limited to about 2 frames. For larger systems, the DBX cards must be upgraded to versions with additional memory. The largest possible system size is 848 ports (if test audio is enabled) or 880 ports (if test audio is disabled). ______________ Change History ______________ New in version 1.24.0 --------------------- * Added support for a separate CWW key for the KP 32 CLD The KP 32 CLD supports up to 64 talk and 64 listen keys, plus a separate call-waiting window key. In earlier versions, key 16 was the CWW key, and these two keys operated in parallel. Starting with KP 32 CLD v1.2.0, the intercom now supports a separate CWW key, and key 16 is now a regular talk/listen key. Note that the I/O card firmware (and any RVON firmware, if applicable) must be updated to a version that supports a separate CWW key. If any one of the devices (intercom controller, I/O card, or keypanel) does not support a separate CWW key, the system will operate normally, but the KP 32 CLD will operate without a separate CWW key (i.e. key 16 will be the CWW key). * Added full support for MADI-16+ cards Support for 16-channel MADI-16+ cards was added in v1.23.0. This version of firmware adds support for MADI-16+ cards with up to 64 channels of audio. * Added Port Allocation Table The Port Allocation Table controls which ports are allocated to which I/O cards. This is necessary when using MADI-16+ cards with more than 16 channels of audio. * UPL force-key actions cannot touch trunk ports In previous versions, a UPL statement with an output action to force a key on or off could interfere with trunking operation. Fixed. New in version 1.23.0 --------------------- * Added support for MADI cards A new screen allows MADI cards to be configured. This screen has 3 tabs. One tab allows card attributes to be configured (pass-through data, reference clock, sampling rate, etc. Another tab controls the mapping between intercom channels and MADI channels. The third tab displays the status of the various MADI cards in the system. * Added support for TM-2000 communications via Ethernet Note: This is actually a feature of the PeriphII-e. It is mentioned here because of the strict correspondence of firmware versions between the DBX and the PeriphII-e. * Ensure RVON-IO gets local GPIO status If an RVON-8 or RVON-16 is reset or plugged in, and that RVON card has links to 1 or more RVON-IO cards, the RVON-IO card might not get the status of the local GPI outputs for its ports, if there is no keypanel attached. Fixed. New in version 1.22.0 --------------------- Version 1.22.0 is based on version 1.19.x, with support for keypanel colors. Its purpose is to make keypanel colors available in larger systems with DBX cards that do not have the additional memory. Other features in v1.20.0 do not exist in this version. New in version 1.21.0 --------------------- * Added support for keypanel colors The intercom now supports configuring colors used on the KP 32 CLD family of keypanels. The following can be configured: - default key assignment colors (per function type) - remote key assignment colors (per remote matrix + function type) - local key assignment colors (per local assignment) - colors for talk and listen indicators * Fixed possible controller reset problems It was possible for the controller's watchdog to trip if the active controller was very busy. Fixed. * Fixed slave frame controller operation In version 1.20.0, some alpha changes might not be forwarded to Peripheral Controllers in a slave frame. (This would only affect PAP-32 and LCP-102 operation; it did not affect keypanels.) Fixed. * Unassigned keys on a PAP-32 were displayed wrongly. Fixed. (Problem only exists in version 1.20.0.) New in version 1.20.0 --------------------- * Support for more resources across trunking Remote scroll lists of up to 1000 items are now supported. * Support for more total resources In previous versions, an intercom was limited to approximately 2040 total local scrollable resources (key assignments). This has been increased; now, the total number of resources is only limited by the available memory, although each scroll list (PL, IFB, etc.) is limited to a maximum of 1000 items. * Support for Arbitrary Crosspoints An optional crosspoint (input port and output port) can be associated with each UPL Resource. If a crosspoint is defined, then that crosspoint is closed whenever any panel is talking or listening to that UR assignment. There is also a Reciprocal flag. If this flag is checked, then the reciprocal crosspoint (from the output port to the input port) is also closed. If a user at a keypanel tries to adjust the volume of a UPL Resource, it adjusts the volume of the crosspoint (if it is defined). The volume of the reciprocal crosspoint is not affected. * Support for Centralized Auto-Dials The intercom supports up to 999 centralized auto-dials. Associated with each auto-dial is an alpha, a scroll restrict flag, and a telephone number. Auto-dial number NNN can be accessed by dialing the sequence #NNN (Dial "##" to generate a single "#" DTMF tone.) Centralized auto-dial numbers can also be accessed via the TIF dial menus in the KP32 and the KP32CLD, for keys which have an assignment for which the "Port is a TIF" flag is set. This requires the following minimum versions: - KP32 v2.1.1 - KP32CLD v1.0.4 * Support for Enhanced Assignment Groups Associated with each Assignment Group is a new checkbox, "Members Only". If this box is checked, then only keypanels that are members of the assignment group can access the assignment group. If the box is not checked, any keypanel can access the assignment group. New in version 1.19.3 --------------------- * Support larger memory sizes This version of firmware supports a revised version of the DBX hardware with larger amounts of configuration flash and DRAM memory, allowing larger system sizes to be supported. This firmware can be used on cards with either amount of memory installed. New in version 1.19.2 --------------------- * Prevent loss of audio on upper 8 channels of RVON-16 if card reset If an RVON-16 card was reset, crosspoints that were closed on the upper 8 channels before the card was reset were re-sent to the card correctly, but the volumes for these crosspoints were not, so the crosspoints were made but were muted. The volumes are now sent correctly. * Support for KP 32 CLD, DKP 16 CLD, and KP 12 CLD keypanel types. New in version 1.19.1 --------------------- * Prevent noise in systems with AIO-8 and AIO-16 cards An AIO-16 card could cause noise on channel 1 of an AIO-8 card in the next slot. Fixed. * Improvements to Control Bus handling See the description for Version 1.16.3 New in version 1.19.0 --------------------- * Added support for IFB program tracking A new configuration table allows IFB listen sources to automatically track IFB program sources. When an IFB program source is changed via a PAP or LCP-102, or via a UPL statement, the intercom looks up the new program source in the PGM Listen Source table; if there is a corresponding entry in this table, it is used to change the IFB listen source for the IFB. The PGM Listen Source table can be edited from AZedit via the PGM Listen Source entry in the System menu. * Listen panels can display IFB program sources If a key has the following assignments: Talk level 1: an IFB Talk level 2: any assignment with the alpha "@PGM" Listen: an auto-X function (e.g. auto-follow, auto-table) then the panel will display the alpha for the IFB's program source, rather than the alpha for the IFB. * IFB Listen works even if IFB has no output bus defined Previously, listening to an IFB had no effect if the IFB had no output bus defined. Now, if you listen to an IFB, you will hear the IFB program source, even if the IFB does not have an output bus defined. * Key labels display properly on PAM-32, LKP-957 panels In previous versions, a key label might not be displayed properly on a PAM-32 or LKP-957 panel. Fixed. * Support for RVON-16 cards New in version 1.18.0 --------------------- * Added support for GPIO-16 communications via UDP. Note that this feature requires the use of the MCII-e Peripheral Controller, rather than the standard Peripheral Controller. New in version 1.17.5 --------------------- * Added support for splitting RVON-8 DIP switch #1 In RVON-8 firmware v2.1.0 and later, DIP switch #1 has been split into two separate functions: - DIP switch #1: closed => AZedit cannot make any changes - DIP switch #2: closed => RVON card has the master configuration (If an RVON-8 is plugged into the frame, and the RVON-8 has a different configuration from the intercom, DIP switch #2 determines which configuration is used.) This version of firmware supports this change. If older DBX firmware is used, then AZedit cannot make changes to the RVON card if either DIP switch #1 or #2 is closed. * AZedit can configure an RVON-8 with an IP address of 0.0.0.0 In certain cases, AZedit would not recognize an RVON-8 card if it had an IP address of 0.0.0.0, which meant that the only way to configure the card was to first login via the serial port and set the IP address. Fixed. * Fixed problem with stuck crosspoints when accessing remote PLs If two people in the same intercom access the same remote PL, and share a trunk, a crosspoint is closed in the local intercom as required for them to hear each other. However, in certain cases that crosspoint would not be released. Fixed. * Miscellaneous fixes to Japanese builds of the firmware The following changes affect only Japanese (UNICODE) builds of the firmware. They reflect changes that have already been made in other firmware (e.g. single-frame MCII-e): - If "leave listen active" is enabled and the user is listening to a PL, and then changes setup pages so the PL assignment is no longer visible, when switching back, the user would then hear a +6dB increase in the PL listen volume - If the "audio page to P.A." option is selected for a group, you could get a stuck crosspoint after the group call is terminated - If "merge new callers" is enabled for a group, active/standby errors would be generated, and the corresponding alarm triggered, whenever a private conversation was established New in version 1.17.4 --------------------- * Support wait-for-talk (trunking) with LKP-957 and PAM panels In trunking, if Wait For Talk is enabled, then listening to a port does not tie up a trunk if there is a keypanel connected to that port and that keypanel does not have any talk keys turned on. However, that doesn't work properly if the keypanel is a listen-only device such as a PAM-32 or LKP-957. (In such cases, the port output audio feeds the panel, while the input audio would typically be some unrelated source.) Fixed. When listening to a port, the listen request is always active if there is a listen-only device connected to that port. * Intercom was unstable if intercom had more ports than hardware It is possible to configure the intercom with more ports than indicated by the hardware. For example, you could configure the intercom as a 3-frame, 720-port, high-density system; and then configure it for 120 ports in frames 1 and 2, and 240 ports in frame 3. (In this case, there is no hardware associated with ports 481-720.) In this configuration, the system could be unstable, with I/O cards and keypanels resetting periodically. Fixed. (This problem only occurs in versions 1.17.0 through 1.17.3.) New in version 1.17.3 --------------------- * UPL can generate /MACRO/START commands to Dynacord paging system New UPL actions have been added: Start Paging System Macro, and Stop Paging System Macro. When a UPL statement with one of these actions becomes true, a /MACRO/START command is transmitted on J1. Note that AZedit would need to be connected via J9, J10, or Ethernet in this case. * Fixed problem with IFBs over trunking If a trunk is being used to interrupt an IFB, and the trunk is undefined or put into maintenance mode, the trunk allocations might not be removed cleanly, leaving the trunk port still interrupting the IFB, even though the IFB assignment no longer appears on the (virtual) keypanel associated with the trunk port. Fixed. New in version 1.17.2 --------------------- * Talk to SL: Don't talk to self If a keypanel is a member of a special list, and calls that SL, the caller does not hear himself. However, the caller will hear himself if he listens to the SL. * Fixed key assignment update problem When a file was sent to the intercom, it was possible for a keypanel to display its new assignments, but the keys didn't work (or called what was previously assigned to them). Fixed. New in version 1.17.1 --------------------- * Added support for SNMP Most of the SNMP support is handled by the MCII-e Peripheral Controller. However, enhancements were added to the DBX to make the DBX link status and RVON-8 IP addresses available to SNMP. * Forward key assigns to Periph Ctlr when trunk port is undefined When a port gets defined as a trunk port, the DBX saves the current key assignments and IFB priority. This information is restored when that trunk becomes undefined. However, the key assignments were not being forwarded to the Peripheral Controller, so they wouldn't show up on the panel or in AZedit. (If the Peripheral Controller was reset, it would then get the assignments.) Fixed. New in version 1.17.0 --------------------- * Added descriptions for I/O cards, PAPs, and LCP-102s. * Prevent noise problem in AIO-16 systems In systems with AIO-16 cards, the 9th port of the AIO-16 card in slot 1 of a frame could experience noise problems. Fixed. * In a trunked environment, on a transfer of control of the Peripheral Controller, remote assignments on keypanels would turn generic (e.g. "023N") for a while, and then revert back to the proper alpha. Fixed. Now, if the standby Peripheral Controller is up to date, and a transfer of control occurs, remote alphas should not change. New in version 1.16.3 --------------------- * Improvements to Control Bus handling Several improvements in control bus handling were made, reducing the number of errors that occur. New in version 1.16.2 --------------------- * Prevent standby reset when extremely busy When the standby DBX in frame 1 becomes extremely busy (i.e. during trunk testing and a simultaneous attempt to write to configuration flash), the card could reset because the Idle task might get starved. Fixed New in version 1.16.1 --------------------- * Prevent reset when extremely busy When the DBX becomes extremely busy (i.e. at startup, or when multiple AZedit sessions are active), the card could conceivably reset because the Idle task might get starved, allowing the Watchdog timer to trip. Fixed. * Maintain communications with I/O cards even when extremely busy When the DBX becomes extremely busy, it could fail to stay in contact with I/O cards (causing them to reset after 30 seconds of no contact). Fixed. * GPI Input status not forwarded to peripheral controller When GPI Input status changes (in any frame), it needs to be forwarded to the main frame peripheral controller to report to AZedit. Fixed. New in version 1.16.0 --------------------- * Added support for UIO-256's in slave frames It is possible to have multiple UIO-256's at the same polling ID, as long as they are on different frames. In this case, the GPI inputs are or'd together (an input is asserted as long as it is asserted on at least one UIO-256); and the GPI outputs operate in parallel. * Improved response time for adjusting analog trims When adjusting input and output gains from AZedit, and the "Real-Time Changes" option is selected, there could be a delay of several seconds between when the change is made in AZedit and when the gain is actually changed in the I/O card. Fixed. * Group-call enhancements (Japanese version only) - If a panel is involved in a private conversation, it is removed from the private converstation when its Group talk key is turned off. - If there is a private conversation between g (a member of group G) and 1+ members of group H, and g stops talking to H, then the private conversation is broken up, and the members of H that were in the conversation re-page G. New in version 1.15.0 --------------------- * Added VOX support UPL can test for audio present on an input. If VOX is enabled on a port, and that port is a 4-wire port (i.e. audio only), then talk key #1 for that port will be turned on whenever incoming audio is detected on that port. VOX only works with ports that are driven by AIO-16 cards. AIO-16 version 1.1.0 is required for support of VOX. * New UPL condition: Any talk key closed? UPL can now test to see if any of the talk keys for a port are currently on. * Added Snoop Tallies An intercom can now be configured to enable Snoop Tallies. A panel displays a snoop tally if all of the following conditions hold: - The keypanel has a hot mic - None of the keypanel's keys are on - Another keypanel is listening to the panel via a point-to-point or a special list, but is not talking to the panel The snoop tally is indicated by turning the Mic Mute LED amber. In a trunked environment, snoop tallies may not always be displayed. If a panel displays a snoop tally, then someone is listening to that panel; however, depending on how trunks are allocated, it is possible for a keypanel in one intercom to snoop on a keypanel in a different intercom, without a snoop tally being displayed. * Added Do Not Interrupt feature Associated with each port is a Do Not Interrupt flag. If this flag is set, only one point-to-point call at a time is permitted to that port. If panel A is talking to panel B, and B has Do Not Interrupt set, panel C will get a busy tally if it tries to call B. In a trunked environment, trunk calls ignore Do Not Interrupt, i.e. trunk calls always go through. * Keypanel privacy enhancements Listening to a Special List respects keypanel privacy. (If a port has the privacy bit set, you cannot listen to it via a special list). A port can now listen to itself, via a Point-to-Point or a Special List, even if that port has keypanel privacy set. New in version 1.14.3 --------------------- * Fixed problem with spurious crosspoints In systems with 2 or more DBX cards per frame, it was possible to have crosspoints fail to turn on, or crosspoints not releasing when they should. Fixed. Note that this problem exists in v1.15.0, but is fixed in 1.16.0. New in version 1.14.2 --------------------- * Local GPIO outputs of RVON-IO could not be controlled by UPL unless a keypanel was attached. Fixed. New in version 1.14.1 --------------------- * System would not work properly if configured for 0 IFBs, 0 key labels, or 0 assignment groups. Fixed. * In large systems (600-squared or larger), the standby controller in frame 1 could sometimes reset. Fixed. * New version of boot downloader, to support Periph-IIe Starting with this version, the U21 and U22 EPROM image files include a new version of the boot downloader, with support for the Periph-IIe controller card. Note that downloading the "dbx.hex" file from AZedit does not touch the boot downloader - see the section describing the boot downloader, above. New in version 1.14.0 --------------------- * Support for Key Labels Normally, a keypanel displays the alpha for the function assigned to talk level 1. This version supports arbitrary key labels. If a key has a label associated with it, the keypanel displays the key label, rather than the alpha for the talk level 1 assignment. If the key is reprogrammed, either from the panel or via AZedit, any associated label is deleted. Because key labels can potentially use a lot of memory, by default a single-frame 272-squared system allows up to 68 ports to have labels associated with them, and up to 64 keys on a given port can have labels (this latter restriction is limiting only if the system is reconfigured to have more than 4 setup pages per port). These defaults can be changed via AZedit as part of the intercom reconfiguration procedure. No changes to keypanel firmware are required to support key labels. * Trunking enhancements If a port becomes a trunk port, the current key assignments and IFB priority are saved. If the trunk associated with that port is subsequently undefined, the key assignments and IFB priority are restored. * Stored Query responses are sent to all ports If Stored Queries (part of Command-Line Protocol) are used, responses are now sent to all serial ports (J1, J9, J10) which do not have active AZedit sessions running. Previously, SQ responses were sent to just a single port. * Support IFB Special Lists across trunking New in version 1.13.0 --------------------- * Support for AIO-16 cards DBX systems now support AIO-16 cards. As part of the intercom reconfiguration dialog, a new Intercom Resizing Wizard guides the user through resizing the intercom. Note that the DBX supports the existing wiring (N DBX per frame for a system of 2N+1 frames, but no more than 128 timeslots per frame), as well as a new "high-density" wiring scheme (N DBX per frame for a system of N+1 frames, used for systems with AIO-16 cards) The I/O Status screen in AZedit shows what ranges of ports are assigned to each card. * Added IFB Special Lists * Added Assignment Groups Assignment groups are another resource in the intercom. An assignment group consists of a list of key assignments of various types - ports, PLs, IFBs, etc. An assignment group can contain both local and remote assignments. Access to assignment groups requires the following firmware versions: - KP-32: v2.0.1 or later - KP-96: v8.9 or later * PAP-32's can be configured from AZedit * Eliminated support for IFB tone override inputs * Increased # of local GPIOs from 4 to 16 (for RVON-IO support) New in version 1.12.2 --------------------- * Made more memory available for large systems In version 1.12.x, a 7-frame 784-squared system would not have enough memory unless certain resources (e.g. Dim tables) were reduced or eliminated. This problem has been fixed. * Bug fix: KP-32 screen saver was sometimes not being updated New in version 1.12.1 --------------------- * Support for new FPGA image (8-pin EPC1, socketed chip U69) A new FPGA image changes the two ASICs' clocking of data associated with a DBX link in order to improve timing tolerances and reduce the possibility of noise introduced via thermal changes to clock edge transitions. NOTE: This version requires V1.3 of the FPGA image in the EPC1 chip at U69. Using V1.12.1 of DBX firmware with an earlier FPGA image, OR using an earlier DBX firmware with V1.3 of the FPGA image will cause audio between frames to appear in the incorrect timeslots. New in version 1.12.0 --------------------- * Supports up to 20 PAPs / LCPs per frame This version supports Peripheral Controllers in slave frames, each of which can talk to PAPs and LCPs. Also, Peripheral Controller v10.12.0 supports up to 5 PAPs / LCPs on J4 (at 9600 baud), in addition to 15 PAPs / LCPs on J3. UIO-256's can only be connected to the first frame. * Supports separate configuration options for tallies There used to be a single tally configuration option. This has now been split into 3 separate options: trunks in use don't generate in-use tallies; off-hook TIFs don't generate in-use tallies; and local party lines generate 10-second incoming call tallies (rather than indefinite tallies). New in version 1.11.1 --------------------- * In certain cases, slave frame DBX cards would power up, but would not communicate with the AIO cards in the frame. Fixed. * Modified link handling so that, where possible, each slave frame derives its backplane clock from a link connected directly to frame 1. New in version 1.11.0 --------------------- * Support for Unicode alphas (Japanese version only) This version of firmware supports a new alpha size, consisting of 8 Unicode (Kanji) alphas. The Kanji keypanels (KP-812K and KP-808K) support Kanji alphas. New in version 1.10.0 --------------------- * Support for RVON-8 card Allows viewing/changing the configuration of RVON-8 card and channels. Allows viewing RVON-8 channel status information. * Support for displaying card types on I/O Status screen AIO V10.2.1, AES-3 V1.0.1, and RVON-8 V1.0.0 report card types to intercom. Card types are used to ensure firmware downloads go to correct card types. * Improved communications between DBX cards in different frames New in version 1.9.2 -------------------- * Fixed several problems in J5 version - On setup page change: Check to see if active incoming calls should be added to or removed from call-waiting window: Include special lists in this check, in addition to P-P and group calls. - When a setup page is changed: If any listen keys are on: Force those keys off (unless they should be active on the new page because of Leave Listen Active). - When a keypanel got 2 incoming special list calls, it could get a tally stuck on for one of those keys after the calls have been terminated. Fixed. New in version 1.9.1 -------------------- * Support SL <--> SL calls across trunking (J5 only) * Added OFF tallies to Special List handling (J5 only) * Allow DIM tables to be used with Special Lists as well as point-to-point assignments (J5 only) * Improved CWW tally handling for panels with smart CWWs (J5 only) In certain cases, the tally for a CWW key was not being updated properly. Fixed. New in version 1.9.0 -------------------- * Leave Listen Active (Japanese version only) For each keypanel, there is now a "leave listen active" flag associated with each setup page. If a setup page is changed, and this flag is set, any active listen keys on that page are not deactivated before changing pages. * Enhanced Special Lists (Japanese version only) Enhanced special lists have some of the functionality of groups. A keypanel can only be a member of one SL. When a keypanel which is a member of an SL calls a point-to-point or another SL, the called panel(s) receive a tally from the caller's SL, rather than the caller's port. If a port is a member of an SL, it can listen to its own SL. Otherwise, an SL listen has no functionality. * Support for separate input and output alphas for each port In earlier versions, a port had a single alpha representing both the audio input, and audio output portions of the port. For keypanels, where both the input and output refer to the same device, this made sense. However, in other applications, the input and output paths of the port would often be used for different purposes (eg. IFB program inputs or listen sources on the input side, and an IFB output on the output side). In this version, it is now possible to give separate alphas to both the input and output portions of a port (by default, the input alpha tracks the output alpha unless you explicitly change the input alpha, so that normally they are the same which would be typical for ports with keypanels attached). Listen keys on keypanels, PAP-32's, and LCP-102's in PAP mode now receive input alphas for display. Some keypanels (like the LKP-957 V8.8) can also request to receive input alphas for display on talk keys as well. Scroll lists always contain output alphas, except when a keypanel requests a list of callers, in which case input alphas are sent to the keypanel. AZedit V2.06.00 is required to enable and support input alphas. In AZedit, input alphas are enabled from the Intercom Configuration dialog which will cause the intercom to re-configure itself and perform a first birthday (although it will remember the system size). When using AZedit with input alphas enabled, AZedit automatically displays the correct input or output alpha depending on the context (i.e. IFB program input lists contain input alphas, and IFB output lists contain output alphas). In situations where either could apply (such as on the Party Line membership view), a context menu allows switching between input and output port alphas as necessary. * Support for direct volume adjustment of incoming calls on the CWW A new feature in the KP-32 V1.2.8 (if enabled) allows the keypanel user to adjust the volume of an incoming caller simply by rotating the volume adjust knob within 5 seconds of the start of the call. The keypanel is able to implement this using existing protocol for all keys except the CWW. This version of firmware adds support to allow volume adjust on the CWW key also. * Fixed Active/Standby problem in v1.8.2 with IFBs With DBX version 1.8.2, IFBs could lose their program input assignments on a transfer of control. Fixed. New in version 1.8.2 -------------------- * Added UPL control of IFB program inputs A new UPL output action has been added: "Set IFB Program Input". When activated, the IFB program input is temporarily changed to the input specified in the UPL statement; when the UPL statement becomes false, the program input is restored. If a PAP or LCP-102 changes an IFB program input while UPL is controlling it, only the saved program input is changed, i.e. the new program input will take effect when the UPL statement becomes false. If ADAMedit or Command-Line Protocol changes an IFB program input while UPL is controlling it, the change takes place immediately: The IFB is switched to the new program input; nothing happens when the UPL statement becomes false. * Improved Command-Line Protocol update speed A command which affects only IFB program inputs now executes immediately, rather than taking several seconds. Also, the command will not be delayed, even if ADAMedit (on another control port) is currently making changes. * Improved response time in updating PAP-32 panels when an IFB program input changes. (These fixes exist in 1.7.4, but not in 1.8.0 or 1.8.1.) New in version 1.8.1 -------------------- * J5 systems: If a GPI input triggers a talk key, generate an indefinite tally for as long as the GPI input is asserted * J5 systems: Generate indefinite tallies for talk keys that are triggered by All-Call keys * A problem was identified which could cause the DBX card to halt, requiring a front-panel reset to restart it. Fixed. (Note: This problem exists in 1.7.2 and 1.8.0, but is fixed in 1.7.3 and 1.8.1.) New in version 1.8.0 -------------------- * Simultaneous support for 4, 6, and 8 character keypanels (only one size supported per AIO card) i.e. Ports 1-8 can support one size, Ports 9-16 can support another, and Ports 17-24 yet another size. * Support for up to 31 intercoms * For J5 version only: A new configuration option called "Don't hang up TIF when no one is talking". Normally, in J5 systems, the TIF's automatically hang up when there are no more keypanels talking to them. When this option is enabled, a TIF will not hang up unless commanded to by a keypanel. * For J5 version only: Automatic handling of 4-wire ports. Suppose a user at port X programs an assignment for port Y on his keypanel. If port Y is marked as a Virtual keypanel, and there is an All-Call (AC) assignment on port Y whose key is the target of a GPI Input definition, then an assignment for port X will be made on the first blank key to the left of the AC key on port Y. Similarly, when the user at port X deletes his assignment for port Y, the port X assignment on port Y will also be deleted. * For J5 version only: Support for alternative volume table. (+6dB to -21dB). * Fix for problem where exclusive control could get lost if ADAMedit session disconnected while holding exclusive control New in version 1.7.4 -------------------- * Improved response time in updating PAP-32 panels when an IFB program input changes. New in version 1.7.3 -------------------- * A problem was identified which could cause the DBX card to halt, requiring a front-panel reset to restart it. Fixed. (Note: This problem still exists in 1.8.0, but is fixed in 1.8.1.) New in version 1.7.2 -------------------- * Added the ability to force a key on or off from ADAMedit. ADAMedit version 2.00.01 or later is required in order to use this feature. * Fixed force/inhibit problem With earlier versions of firmware, if the intercom was configured for 7 frames (784-squared), crosspoints with input numbers of 670 or greater could not be forced or inhibited. Fixed. New in version 1.7.1 -------------------- * Intercom can control keypanels' headset transfer. (Requires KP-32 version 1.1.6 or later for this to work.) * Added command-line protocol capability. * KP-32 screen saver: Fixed display problem if screen saver is entirely blank. New in version 1.7.0 -------------------- * Intercom can be configured for 4-, 6-, or 8-character alphas New in version 1.6.1 -------------------- * Added fix for audio noise problem In unusual cases, it was possible for certain audio crosspoints to be noisy. Fixed. New in version 1.6.0 -------------------- * Added KP-32 menu passwords Two passwords can be set from ADAMedit: one for general access to the menus, and one for access to the Service menu. This requires KP-32 firmware version 1.1.6 or later. Older versions of KP-32 firmware will ignore any passwords set via ADAMedit. * Added KP-32 screen saver The screen saver displayed by the KP-32 can now be configured from ADAMedit. This requires KP-32 firmware version 1.1.6 or later. Older versions of KP-32 firmware will display the default screen saver. * Added new UPL action: Inhibit all crosspoints to a given output * Allow AT over non-IFB assignment The AT (Auto-Table) assignment can now be used over any key assignment, not just IFBs. If used over a non-IFB assignment, it acts like the AF (Auto-Follow) assignment. * Panel requests list of inaccessible assignments: Fixed handling When a panel requested a list of inaccessible assignments (e.g. assignments on unassigned setup pages), the panel would get the list, but in some cases would not be able to call the assignments in the list. Fixed. * Fixed All-Call problem If a key with an All-Call assignment was latched on, and the key assignment was changed via ADAMedit, the keys to the left would get stuck on. Fixed. * DBX could reset in unusual circumstances The DBX would sometimes reset itself if ADAMedit was used to view particular screens. Fixed. New in version 1.5.0 -------------------- * Full support of all current features This version represents a merging of two development streams: The standard ADAM development stream and the Japanese (J4) stream. This is most notable for the J5 version of firmware. It supports all the current ADAM features (e.g. intercom resizing, IFB dims, auto-table, UPL statments), as well as all the current J4 features (e.g. Katakana, groups, large-display panels, auto-dials, off tallies). * Fixed "busy" trunking problem If a trunk is put into maintenance mode, and the trunk was previously in use, the trunk master attempts to move the assignments to a different trunk. However, a problem in the Master Controller could result in the user getting a "busy" tally, even when the requests were successfully moved to a different trunk. Fixed. * Modified handling of local PL tallies Party line tallies can be individually enabled. If a party line has its local tally enabled, the generated tally depends on the intercom configuration. If reduced tallies are selected (Options / Intercom Configuration, "Don't generate tallies for TIF or trunk use" on the Options page), whenever anyone talks on a party line, anyone with that PL assigned to a key will see an incoming (10-second) call tally on that key. If the "reduced tallies" option is not selected, local party line tallies are similar to IFB / ISO tallies: a key with a party line assignment will generate an "in use" tally for as long as anyone is talking to the party line via a key. Permanent talkers never cause any tallies to be generated. * Improved DBX / Peripheral Controller communications Some minor improvements were made in sending messages to the Peripheral Controller. This should make ADAMedit lose communications with the intercom less frequently. * Support a full 256-squared intercom in 2 frames, with test audio If test audio is not enabled, the two links are redundant; the intercom will be fully functional as long as at least one of the links is up. If test audio is enabled, and both links are up, all 256 timeslots are available in both frames. If test audio is enabled, but only one link is up, only the first 124 timeslots will be forwarded from each frame. Hence, for example, panels in frame 1 will be able to hear all timeslots except for timeslots 253 through 256. New in version 1.4.0 -------------------- * Added support for PAP-32 panels New in version 1.3.0 -------------------- * Full support for auto-table across intercoms Note that this requires Trunk Master version 7.5.0 and peripheral controller version 10.3.0 or later for proper operation. * Control bus errors encountered by DBX cards are now included in the I/O card error counters In previous versions, errors were only shown for messages generated by the peripheral controller. Since most of the messages are now generated by the DBX, the error counters were artificially low. * "Busy" tallies generated for requests to non-talking intercoms If a key with a remote assignment is turned on, and the target intercom is not communicating with the Trunk Master, the user will see a "busy" tally. The tally is automatically cancelled if the key is turned off, or if communications with the remote intercom is re-established. * Remote PL users hear each other If two users share a trunk in order to talk to the same remote party line, crosspoints are closed in the local matrix to ensure that they hear each other as required (i.e. when one is talking and the other is listening). * Added support for allowing a keypanel to query the volume settings for each of its key assignments. Note that no keypanel currently uses this feature. * Port-is-TIF messages now sent to the panel If a key has an assignment for a port that is marked as a TIF port, a dial menu is automatically brought up whenever the key is turned on. However, the information required to support this was not being sent to the panel after power-on. New in version 1.2.6 -------------------- * Party line crosspoint problem fixed for transfer of control If a transfer of control occurred within frame 1, it was possible for the system to end up with some spurious party line crosspoints closed Also, less frequently, it was possible for other crosspoints which should be closed to be lost. Fixed. New in version 1.2.5 -------------------- * Scroll list problem fixed In a DBX system, it was possible for an AIO card to lose all local alphas and remote matrix names, preventing the user from scrolling. Fixed. * PAM-100 can now adjust output volume A problem in the DBX prevented the PAM-100 panel from adjusting the audio output level. * Fail LED suppressed It was possible for one of the Fail LEDs to be turned on if a non-critical error occurred when updating the configuration flash. The LED would then stay on until the A link went down and back up. Fixed. (If the frame 1 active DBX encounters a failure when updating its configuration flash, after doing a "Send Changes" from ADAMedit, ADAMedit will normally respond with an error message indicating this problem.) New in version 1.2.4 -------------------- * Crash problem fixed The DBX could sometimes stop processing requests, and then some time later crash. (The exact cause of the problem is not yet known; however, it only occurs in a trunked environment. It is suspected that the problem relates to trunked IFBs.) New in version 1.2.2 -------------------- * Several minor problems fixed * Added support for verifying that AIO cards have the right crosspoints closed The DBX continually verifies that the AIO cards and the DBX agree on which crosspoints should be closed. This requires AIO version 10.0.4 to work. Earlier versions of AIO card will work, but crosspoint verification will not occur. * Increased the buffer free pool size The number of messages available has been doubled. * Different diagnostic information recorded on crash If the DBX crashes because it runs out of buffers, information is preserved across reset, to help in determining where the buffers are being lost. New in version 1.2.1 -------------------- * Fixed assignment update problem for disconnected panel If ADAMedit is used to change a key assignment for a port, and there is no device responding on that port at the time, the key assignment was not being updated properly. Hence, if a keypanel were later connected to that port, the key would show a key assignment, but the key would not work. This problem affects DBX versions 1.1.1 and 1.2.0. New in version 1.2.0 -------------------- * Support for wait-for-talk trunk allocation * Fixed two All-Call problems - If a key with a trunked assignment was activated or deactivated via an all-call, the tally for the key was sometimes not updated. - If a key was on because of an all-call, and its assignment was changed (via either ADAMedit or the keypad), the assignment was not hot-switched properly. New in version 1.1.1 -------------------- * Key assignments (when changed from ADAMedit) are now sent to the keypanels much more quickly * Tallies are updated much more quickly * IFB tally bug fixed See v1.0.9 for a description of this problem * If look-up alphas are not enabled, ensure that look-up alphas are set to match standard port alphas during initialization A problem was discovered in which enabling look-up alphas, changing alphas, and then disabling look-up alphas could leave behind evidence of the look-up alphas. New in version 1.1.0 -------------------- * Trunking protocol changed The protocol used to communicate with the Trunk Master has been changed. The new protocol should be a lot more robust in the presence of errors. It also allows access to an arbitrary number of ports; the previous version limited trunking access to ports below 511. * Remote alphas validated via checksums If the intercom is disconnected from the trunk master and then reconnected, remote scroll lists are not discarded. Instead, the intercom and the trunk master exchange checksums; only those lists which are different are sent. This will reduce the time it takes for trunking data to come up to date. It also means that remote alphas should not go "generic" when trunking data is disconnected and then reconnected. * Support for remote party line tallies * Support for trunk inspect from ADAMedit * Allow ADAMedit to view which intercoms are communicating * Allow ADAMedit to delete old, inaccessible remote assignments * Allow ADAMedit to force keys off for disconnected panels * Allow IFB auto-table listen across intercoms If a listen key is turned on to listen to a remote IFB, and that IFB has a listen source defined, the listen source is heard, rather than the IFB program audio. * IFB tone override bug fixed If IFB tone overrides were defined, they would not work properly, and could also crash the intercom when the IFB was called. NOTE: Version 1.1.0 has the IFB tally problem which was fixed in version 1.0.9 New in version 1.0.9 -------------------- * IFB tally bug fixed If multiple IFB keys are activated together and then released after a very short interval (either pressing the keys together, or via an All Call), it is possible for one or more keys to continue to tally the IFB as being "in use" (e.g. slow flash on a KP-96). The problem only occurs if there is a standby DBX in the first frame. The problem does not occur in non-DBX systems. New in version 1.0.8 -------------------- * The DBX card now keeps track of how long it has been since it successfully transmitted or received a message on the control bus. If 30 seconds passes without successfully transmitting or receiving a control bus message, the DBX will reset the Altera control bus state machine. * Fixed a problem in the 2 frame redundant system (where there are 4 links between frames 1 and 2), in which multiple links could end up driving the same audio timeslots. This was mostly harmless because the same data was being driven. * Fixed a bug in which both cards in slots 8 and 9 in a slave frame could conceivably become Active at the same time. * Changed green LED #18 on the first DBX display page from meaning "the card is being downloaded with new firmware", to meaning "the card has received its configuration, including system size, and timeslots" which conveys to us more useful information. * Fixed a bug where the DBX card did not forward trunk requests to the MC if the Trunk Master was marked as not talking. However, the MC needed to receive these requests anyway, so that when communications with the Trunk Master was resumed, the queued requests could be sent to the TM. * Fixed a bug in the 2 frame non-redundant configuration where the slot 9 DBX in frame 2 failed to convince the AIO card in slot 8 to release the control bus clock. Also, in all configurations, slave frame cards in slots 8 and 9 that have a stable link in clock slave mode, now make an offer to take over the clock every 2 seconds to ensure that there is always a frame 1 clock in every slave frame. * Slowed down the speed at which messages were generated to avoid a condition where the Active DBX in frame 1 could become so busy that the Idle task would never run and the hardware watchdog would trip. * Fixed a bug where if a KP received a call from a port that was restricted, it was possible (likely) for the KP to receive a corrupt message trying to tell it to delete the caller's alpha from its scroll list. The corrupt message could cause the KP to go to "****" and come back. * Fixed a bug in the 2 frame non-redundant configuration in which the links would come up but neither link was chosen to drive audio. * Fixed a bug in which some frames in larger systems did not get their AIO cards initialized properly (the symptom was that the AIO cards could not report their versions). This was because a DBX card in a slot other than 8 or 9 was being used to deliver messages to these AIO cards, but the DBX card did not have the AIO card status and thought the AIO cards weren't talking so it did not deliver the messages. * Added more rigorous checking of trunking parameters, and log errors to help find any trunking problems. New in version 1.0.5 -------------------- * A Clear Allocations request made via CStrunk was not being handled properly. Fixed. * Fixed some trunking problems Certain problems were found, which could result in spurious audio related to trunking. These could result in either of two types of problems: audio being present for no apparent reason; and erroneous trunk requests being sent to the Trunk Master. These have been fixed. New in version 1.0.4 -------------------- * Added support for system sizes other than 3 frame redundant. The system may now be configured from 2 to 5 frames in either redundant or non-redundant configurations. In addition, 6 and 7 frame non-redundant configurations are supported. * You can disregard test audio on a given link (regardless of the system wide setting from ADAMedit). Setting DIP switch position 1 ON affects PORT A, while position 2 ON affects PORT B. When either of these DIP switches is ON, the test audio for the affected port is monitored and transmitted, but the link is never torn down because of test audio, even if the test audio if bad. Note that you must set the appropriate DIP switch at BOTH ends of a link in order to ignore test audio on that link. * Fixed bugs related to operation of DBX cards in slots other than 8 or 9. * Fixed bug related to setting listen key states * Fixed bug related to receiving GPI input status * Fixed bugs related to trunking * Improved messaging speed and capabilities New in version 1.0.0 -------------------- * Initial release