___________________________________________ ADAM Peripheral Controller, Version 10.17.0 ___________________________________________ File type: Motorola File offset: 0 EPROM type: 29F040 Checksums: Standard version: U2 = e37b, U4 = bfc9 Standard version (with alarms): Not yet released Japanese: Not yet released ____________ Update Notes ____________ With one exception, the complete intercom configuration is stored in configuration flash in the frame 1 DBX cards (slots 8 and 9). (The execption is the Authentication table - see below.) 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. _____________ Compatibility _____________ Peripheral Controller: Requires version 10.17.x as the standby controller. When updating from version 10.16.x or earlier, the Peripheral Controller will perform a first birthday. This is normally not a problem, since the complete intercom configuration is stored in the DBX. However, communications settings for the J9/J10 (or J7/J8) AZedit ports will be lost. This can be avoided by going to Options / Preferences in AZedit, selecting the Startup / Shutdown tab, and checking the option "Save advanced communications settings locally". When updating from version 10.5.x or earlier, the Peripheral Controller should be updated before the frame 1 DBX cards. Bus Expanders: Requires DBX version 1.17.x. Can be used with version 1.2.x or later during the upgrade procedure. Trunk Master: English builds require version 7.3.0 or greater, including any version of TM-2000. Japanese builds require TM-2000 version 8.5.0 or greater. TM-2000 version 8.6.0 required for support of Special Lists across trunking. AZedit: Requires version 3.0.0 or later for full support of all features, including authentication, VOX, and snoop tallies. AIO-8 Card: Requires AIO-8 version 10.3.0 or later. The Japanese version of the AIO card is required for Japanese versions of MC firmware. AIO firmware version 9.x.x can be used while upgrading. AIO-16 Card: Requires AIO-16 version 1.0.0 (1.1.0 or later required for VOX). UIO-256: Requires version 2.0 (checksum 78b5), with the UIO-256 configured in multi-drop mode (DIP switch S1 position 2 closed, and with the RS-485 data going to J2 of each unit). PAP-940/951/952: Requires version 7.3.x or later. PAP-32: Works with any version on J3. Requires PAP-32 v0.0.2 for any PAP connected to J4. Requires v0.0.3 or later in order to be able to configure the PAP-32 from AZedit. ____________ DIP Switches ____________ Position Meaning -------- ------- 1 J1 baud rate for AZedit: Closed = 38.4K, Open = 9600 baud 2 Unused 3 Unused 4 Unused 5 Should be closed (enables monitoring for loss of backplane clock) 6 Closed - Use J7/J8 instead of J9/J10 for aux. AZedit sessions 7 Closed = frame 1. Open = slave frame. 8 Reserved, must be open ___________________ Memory Requirements ___________________ Currently, the largest configurable intercom (with standard resources) is approximately 816-squared for a 4-frame DBX system with AIO-16 support. For Japanese versions of firmware, the largest configurable intercom (with standard resources) is approximately 744-squared for a 4-frame DBX system with AIO-16 support. ______________ Authentication ______________ Starting with Periph Ctlr version 10.16.0, the intercom supports AZedit authentication. By default, authentication is disabled (not required). Authentication allows controlled access to the intercom, in which a valid user name and password must supplied before AZedit can connect. Also, authentication can specify that a particular user cannot connect unless AZedit also has a valid restrictions file. Authentication can be enabled/disabled globally, and individually on J9 and J10 sessions. The J1 session never needs authentication. Unlike other configuration data, the authentication information is *not* stored in the DBX, but only in the Peripheral Controller. Also, the authentication information is lost if the intercom is reconfigured or performs a first birthday (e.g. after upgrading to a new version of firmware). Note that this is in contrast to the MCII-e Peripheral Controller, which preserves the authentication information even when the intercom is reconfigured. ______________ Change History ______________ New in version 10.17.0 ---------------------- * Added descriptions for I/O cards, PAPs, and LCP-102s. * If multiple AZedit sessions are active, a download of I/O cards (especially DBX cards) could take a long time. 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 10.16.1 ---------------------- * Exclusive control lockout after firmware download When more than one AZedit session is connected, and new firmware is downloaded to the PC, then after the PC resets, the DBX still thought exclusive control was granted to an AZedit session. Fixed. New in version 10.16.0 ---------------------- * Added Authentication See the description above. * 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. New in version 10.15.0 ---------------------- * Support for 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. New in version 10.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. * Support for Search & Replace from AZedit This function allows the user to automatically replace all occurrences of a given key assignment with another, either system-wide or on selected keypanels. * Trunking enhancements If the intercom is not talking to a Trunk Master, the ports which are marked as trunk ports can be cleared (marked as no longer being a trunk). This is done by going to Status / Ports in AZedit, selecting "Show Enhanced Status", and then selecting the appropriate port(s) and right-clicking. * 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. * AZedit could not clear communications error counters for standby MCs. Fixed. New in version 10.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 New in version 10.12.0 ---------------------- * Supports Peripheral Controllers in slave frames, with PAPs and LCPs DIP switch position 7 must now be closed for Peripheral Controllers in frame 1, and open for Peripheral Controllers in slave frames. It is not necessary to have Peripheral Controllers in any slave frame which doesn't have any PAPs or LCPs connected. * Supports up to 5 PAPs on J4, polled at 9600 baud * Supports independent tally configuration options There are now separate configuration options to determine whether trunks that are in use generate a tally; whether off-hook TIFs generate a tally; and whether local PLs generate a 10-second incoming call tally or an indefinite tally. These used to all be controlled by a single configuration option. New in version 10.11.2 ---------------------- * Fixed problem in which standby controller could occasionally go active briefly (typically when downloading new AIO card firmware). New in version 10.11.1 ---------------------- * Added support for Unicode alphas between the intercom and the TM-2000. * Status / Standby Controller would show "OK Cur" while the standby was being updated. Fixed. It now shows "OK Old" until the standby is up-to-date. * Fixed a problem which could cause the MC to reset in large (4-frame or greater) Japanese systems. * Improved communications between active/standby controllers. New in version 10.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. Note: This version of firmware does not support transferring Unicode (Kanji) alphas between the MC and the Trunk Master. Support for this will be added in MC version 9.20.1, which will require TM-2000 version 8.5.0. New in version 10.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. New in version 10.9.1 --------------------- * Support SL <--> SL calls across trunking (J5 only) * Fixed response time for on-board GPI inputs If no devices (UIOs / PAPs / LCPs) were connected to J3, response time for on-board GPI inputs was poor (in the order of 1/2 second). Fixed. New in version 10.9.0 --------------------- * 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 or later 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). * 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. New in version 10.8.4 --------------------- * Fixed problem with automatic 4-wire port handling In J5 systems, when making a 4-wire port assignment from the keypad, if the associated GPI input was already asserted, the panel could get an extra copy of the 4-wire port in the call-waiting window; this would also result in 2 copies of the panel's assignment being made on the 4-wire port's virtual keypanel. Fixed. * Fixed response time for on-board GPI inputs If no devices (UIOs / PAPs / LCPs) were connected to J3, response time for on-board GPI inputs was poor (in the order of 1/2 second). Fixed. * Fixed a problem which could cause the MC to reset in large (4-frame or greater) Japanese systems. * Status / Standby Controller would show "OK Cur" while the standby was being updated. Fixed. It now shows "OK Old" until the standby is up-to-date. New in version 10.8.3 --------------------- * Fixed PAP-32 / LCP-102 update problem If a transfer of control occurred in the frame 1 DBX cards (e.g. because new firmware was downloaded to the active DBX), any LCP-102 or PAP-32 panels connected to the system would not be updated for a while. It was sometimes necessary to disconnect and reconnect the panels in order for them to be updated. Fixed. (This problem exists in Peripheral Controller versions 10.8.0 through 10.8.2, and in versions 10.7.3 and earlier.) New in version 10.8.2 --------------------- * Support for TIF dial-out across trunking In order to dial out on a TIF connected to another intercom, the following conditions must be satisfied: - The intercoms are connected to a TM-2000 running software version 8.2.1 or later - Both the intercom from where the user is dialing and the intercom with the TIF must support TIF dial-out across trunking - There must be a trunk which is allocated between the user doing the dialing and the TIF. (This will normally be satisfied when the user enters the dial programming sequence and latches on the talk key.) New in version 10.8.1 --------------------- * If an alpha was restricted, keypanels' scroll lists were not updated properly. Fixed. (Problem only affects v10.8.0.) * In rare circumstances, it was possible for keypanels to continue to display the old alpha when the alpha for a key assignment was changed. Fixed. * For J5 systems: When a keypanel was powered up, it was not being informed which keys had TIF assignments. This meant that certain automatic TIF handling features were not working. Fixed. New in version 10.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 * Support for alpha change counters (enables ADAMedit to automatically refresh alphas when changed by another session, or from a remote intercom) * 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 10.7.4 --------------------- * Fixed PAP-32 / LCP-102 update problem If a transfer of control occurred in the frame 1 DBX cards (e.g. because new firmware was downloaded to the active DBX), any LCP-102 or PAP-32 panels connected to the system would not be updated for a while. It was sometimes necessary to disconnect and reconnect the panels in order for them to be updated. Fixed. (This problem also exists in Peripheral Controller versions 10.8.0 through 10.8.2.) New in version 10.7.3 --------------------- * Full support of 4-, 6-, and 8-character alphas when trunked In previous versions of intercom firmware, only 4-character alphas were forwarded to remote intercoms via the Trunk Master. With this version, all 3 sizes of aliases are forwarded (so that intercoms of different alpha sizes can each get the size it wants), and the intercom will receive the correct size of alpha from the Trunk Master. Note that support of all alpha sizes across intercoms requires a TM-2000 Trunk Master. If an FR9589 Trunk Master is used, only 4-character alphas are forwarded. * Fixed "clear inaccessible remote assignments" In previous versions, clearing remote assignments (from the Status / Remote Intercoms) was selected, ADAMedit would report the number of applicable remote assignments that were found, but the assignments wouldn't actually be cleared. Fixed. New in version 10.7.2 --------------------- * Added command-line protocol capability * Fixed a problem in handling remote alphas In some cases, a remote alpha was not being deleted even when it was fully restricted. Fixed. New in version 10.7.1 --------------------- * Panels should get their alphas much faster after a system power-up * In J5 systems, panels would sometimes not get alphas at power-up. Fixed. * In J5 systems, with keypanels with dedicated page-change buttons, when changing setup pages, the setup page indicator would revert back to the previous setup page for a second, and then return to showing the page just selected. Fixed. New in version 10.7.0 --------------------- * Support 6- and 8-character alphas. 6- and 8-character alphas are enabled only if used with DBX version 1.7.0 or later. It is fine to use Peripheral Controller version 10.7.x with DBX version 1.6.x if only 4-character alphas are desired. New in version 10.6.0 --------------------- * 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. * LCP-102 would show "N/A" for certain volumes When trying to adjust a crosspoint volume (in PAP mode) or a PL volume (in CDP) mode, the LCP-102 would display "N/A" for the volume, even though it could adjust the volume. Fixed. * Fixed trunking problem It was possible for the DBX card to think there was no communications with the Trunk Master, when in fact the TM was talking. This would result in trunked calls getting "busy" tallies, even though the call would go through. (The Trunk Master status in ADAMedit was correct, because the Peripheral Controller was communicating with the TM. The problem occurred because of a discrepancy between the Peripheral Controller and the DBX.) Fixed. * J5 systems: Could not clear "loss of clock" alarm On system power-up, the "loss of clock" alarm would be asserted (because the peripheral controllers finish initialization before the DBX cards start driving clock), but the alarm could not be cleared. Fixed. New in version 10.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). * DBX could get wrong list of talking intercoms In certain circumstances (e.g. a transfer of control from one DBX to another), the peripheral controller could send the wrong data when telling the DBX which intercoms are talking. This could cause a user to get an unexpected "busy" tally because the DBX thought the target intercom was not talking (although the audio would still go through). Fixed. * Improved Trunk Master communications Lower-priority data (including port and party line activity status) that was queued for the TM might be delayed in certain circumstances. This means that a listen request which was inactive because of "wait for talk" might take longer to activate after the function being monitored went active. The delay has been removed. New in version 10.4.0 --------------------- * Added support for PAP-32 panels New in version 10.3.0 --------------------- * Full support for auto-table across intercoms Note that this requires Trunk Master version 7.5.0 and DBX version 1.3.0 for proper operation. * Control bus errors encountered by DBX cards are now included in the I/O card error counters * Added support for "busy" tallies for requests to non-talking intercoms These tallies are actually generated by the DBX; however, the information needed to generate these tallies is now passed on from the peripheral controller to the DBX. * 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 10.2.4 --------------------- * Trunking improvements - When a local panel turns a key on or off, and the key has a remote assignment, the request has to be forwarded to the Trunk Master. However, the Peripheral Controller was sometimes delaying up to a tenth of a second before forwarding the request. Fixed. - In a system with 2 or more DBX cards in each frame, if there was a transfer of control between DBX cards in the first frame, the DBX card which becomes active might not have proper trunk information. Hence, existing trunk requests might be lost. Fixed. New in version 10.2.3 --------------------- * Fixed remote alpha problem In certain occasions, remote scroll lists (other than point-to-point lists) could be lost. Fixed. New in version 10.2.2 --------------------- * Support for wait-for-talk trunk allocation New in version 10.2.1 --------------------- * Key assignments (when changed from ADAMedit) are now sent to the keypanels much more quickly * 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 10.2.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. New in version 10.1.6 --------------------- * Fixed bug which prevented new firmware from being downloaded to keypanels * Fixed message pacing to avoid causing DBX card to be too busy * Fixed bug where DBX trunk requests were discarded instead of queued if the trunk master was marked as not talking. New in version 10.1.5 --------------------- * Improved speed for handling various ADAMedit requests. Modified ADAMedit message handling so that ADAMedit is less prone to getting disconnected. * Improved active/standby communications so standby comes up to date much more quickly * On a first birthday, ports 201+ are scroll restricted. (If this isn't done, KP-96 panels can crash when ports are scroll restricted, for very large systems.) * Data sent to the DBX is paced so that the DBX does not get overloaded. * Panels now get their alpha data much faster when the system is powered on or a file is sent from ADAMedit * Added DIP switch: Use J7/J8 instead of J9/J10 for auxiliary ADAMedit sessions Communication ports J9 and J10 have no hardware buffering, so they are very prone to overrun errors, especially at 19200 baud and higher. If DIP switch position 6 is closed, the Peripheral Controller uses J7 instead of J9, and J8 instead of J10. These serial ports have hardware FIFO's, so they are much less prone to overrun errors. However, note that these ports are 2-wire RS-485 only, and hence require the use of a Telebyte or equivalent adapter. * Allow for non-redundant systems: 2 or 3 frame systems with a single DBX per frame * Trunking bug fixes: - Trunking could stop working - Trunking would not work if the number of setup pages was not 4 - If a trunk was undefined, it was not fully cleaned up (ADAMedit still saw the port as a trunk port; trunking key assignments weren't deleted from the page) * Keypad programming bug fix Using the keypad to reprogram a key on an expansion panel: the new assignment would appear on the main panel. New in version 10.0.0 --------------------- * Support for split functionality with Dual Bus Expander In this version, most of the basic intercom functionality has been moved from the MC to the DBX. Since the DBX has much more RAM available, this means that the maximum supported intercom size is now much larger. Since the Master Controller is now largely handling peripheral devices (ADAMedit, Trunk Master, UIO-256s, PAPs), it is now called a "Peripheral Controller". The Peripheral Controller has no functionality without at least one DBX card being present. The system will have some functionality if it has DBX cards but no peripheral controllers - for example, panels will still show their existing assignments, but new assignments cannot be programmed, and if a a panel is powered on, it will come up with no assignments.