Release Notes 250-441

NOTE: This document contains a list of features and fixes for each major release of the software.
If
you are upgrading to a version greater than 4.1 from a version prior to version 4.1, be sure to
read the release notes for version 4.1 as there were major changes in that release.
For details on how to register this software, search on Registration in the on-line help after installing the
workstation.
WARNING
1. If you have not legitimately purchased this version of AXxess DO NOT CONTINUE. This
installation must be registered with the factory to receive a valid license otherwise it will
expire in 20 days. To register the site, the factory must have a valid purchase order on file.
2. Attention, Communications in AXxess version 4.3 have changed, all MultiRAMM modules
will be changed on upgrade from MultiRAMM to MultiPort.
Note: If using dialup RAMM please see the section below under AXxess Upgrade
Considerations.
3. Site codes need to be set under Access Level, Options or you may receive a denied access or
invalid site message.
If upgrading from a previous version, do the following to ensure that no data is lost:
1. Read the section titled "AXxess Upgrade Considerations" below.
2. Backup the database.
3. Backup or copy the Server’s Data Directory files with the exception of the DB folder.
For additional information on this version, please refer to the following documents in the AXxess 200
Server installation folder after the server files have been installed:
Readme.rtf This document
Release notes.rtf Provides details on the significant changes in previous major releases of the
software. See below for changes in this release.
Installation notes.rtf Details the various installation options and settings when installing the software.
For details on how to register this software, search on Registration

in the on-line help after installing the workstation.
AXxess Upgrade Considerations

AXxess 4.4.0 will upgrade any version 4.0.4 or later software. As a convenience when upgrading from a
version prior to 4.0.4, there is a copy of AXxess 4.0.4 software available on the AXxess 4.4.0 CD.
This allows the user to upgrade to 4.0.4 before upgrading to 4.4.0
On start up after the AXxess upgrade to version 4.4.0 from any version prior to 4.3.0, communications to
the eRAMs and RAMMs will automatically convert from MultiRAMM to MultiPort.
MultiPort is a Windows Service that is used for communication to Area Controllers as well as many
other custom libraries (DVR, NVR, email, burglar panels, etc.). Windows Services have some specific
requirements.
1. Any MultiPort connecting to the AXxess Server over the network must do so through a UNC
(Universal Naming Convention). Mapped Drives are not valid for Windows Services.
2. Any MultiPort connecting to the AXxess Server over the network must be configured to login
using an local Admin level user account. This user account must have read/write privileges to
the AXxess folder on the AXxess Server.
After the upgrade, it may be necessary to do one or both of the following in order to start the MultiPort
service. This is only required once after the upgrade.
1. In Control Panel, Administrative Tools, Services, select the MultiPort service and if disabled,
enable and start.
2. If the service is enabled and started go to the MultiPort Manager located in the Start, All
Programs, AXxess, Accessories program group and select MultiPort Manager. Double click
on the MultiPort Manager icon on the lower right tool bar then stop the service by clicking on
the Stop button then start the service by clicking on the green Start button.
If using Precision Access Templates, there has been a change in functionality in 4.3 or later where the
configuration change of a Precision Template will change cardholders that have been assigned that
template. This is different from the previous version which did not make changes to the cardholders.
MultiPort does not support dialup RAMM. For those systems using dialup RAMM, a MultiRAMM
will be required to run the dialup RAMM. The MultiRAMM can not run on the same computer as the
MultiPort which communicates to hardwired and networked RAMMs as well as networked eRAM
Area Controllers.
If using RAW commands to set site code, there has been a change in functionality between 4.3.2 and
4.3.3. In 4.3.2 the site codes would be entered in HEX, i.e. RAW command would be "12 3060" for
site codes 48 and 96. In 4.3.3, this string will need to be changed manually to "12 4896" for proper
operation.
Upon upgrading to version 4.4.1 from versions prior to 4.3.4, all existing manually created schedules
will be updated with a simple name to convert them to named schedules which were introduced in
version 4.2.0. The user will need to open Configuration / Schedules, and locate each newly named
schedule, and change the name to something meaningful. New schedules may only be created in the
Configuration / Schedules window, where before a user could create a schedule in the function that
was to be scheduled.
Opto 22 integration is no longer supported by the AXxess software.
Upon upgrading from a version prior to 4.1, when the first Desktop is started, there may be errors
regarding an invalid object "files". These errors can be ignored.
New features and fixes in version 4.4.1

Added support for new netEDGE Area Controller features, revision (08-324) or later.
Suggested eRAM revision (08-179) or later.
Suggested BLP PROM revision (07-025) or later. (07-205 required for some features)
Release Date November 26th, 2008
AXxess MultiPort
1. Using Manual Control window to "move" a cardholder for Global Antipassback now updates
the AXxess database. (OFI-7235)
Feature changes in 4.4.1

netEDGE
1. Implemented the Health inputs (Tamper, Battery Fail, AC Fail).
2. Implemented door sensor supervision.
3. Added support for site code verification degraded mode.
4. Implemented area tracking and global antipassback.
5. Added support for reader enable from REX input.
6. Impemented keypad PIN support for "Reader and Keypad", "Reader or Keypad", "Keypad
Only", and "Dailycode".
7. Added a door sensor debounce timer.
8. Added Two badge operation mode support.
9. Enabled the Auxiliary relay.
10. Added support for magnetic reader track 2.
New known issues found in 4.4.1

Desktop
1. The "Computer Name" field for an Area Controller may be changed when the Area Controller
is used by Doors, Sensors, Outputs, etc. Once the cumputer name has been changed, the
connection to the points will be lost. (OFI 7197)
Communication modules (MultiDrop, MultiRAMM, MultiPort)

1. During an initialization of an eRAM or netEDGE, the current area is not set, essentially
forgiving all cardholders at all door on the initialized area controller. (OFI 7364)
Current known issues found prior to 4.4.1

Desktop
1. If using encryption between workstations and the network connection between the
workstations is slow or the network traffic is heavy, the Desktop may display some
transactions containing garbage characters. Other Desktops will display it correctly and the
entry in the Transaction Log will be correct. (OFI-2559)
2. When a panel is set for 1 door mode and Show in Control List is checked for both doors, the
manual control screen will show entries for both door 1 and 2. If door 2 is selected and
unlocked, relay 2 will unlock not relay 1 as expected for a 1 door panel. (OFI-2001)
3. When using operators with multiple languages, ensure that you configure the templates
under each language. (OFI-2428)
4. When deleting and archiving cardholder records, the archive location must already exist or
you will get an error. (OFI-2297)
5. If the site code for a site has not been programmed into Access Levels, Options, and a card is
presented at a reader for the first time the site code is not programmed correctly and you may
get a Denied Access message for eRAM and an Invalid Site message for RAMM and
MultiDrop. (OFI-5810)
6. Icons in the toolbar no longer show the tooltips explaining what the icon is. (OFI 6112)
7. Precision Access Templates may be saved with the same name as an Access Level. This
causes an issue where the Template cannot be modified, and must be renamed. (OFI 6110)
8. The text for acknowledged alarms in the Alarm Log window remains the color for the priority
of the alarm. (OFI-6679)
9. Changing the point address of an Elevator Reader to 0 from 1 or 2, and then back will cause
all Outputs to be deleted. (OFI-6742)
10. When using the Video window on the Desktop to display a DVR/NVR camera, the Desktop
can pause for a significant amount of time if the DVR/NVR cannot be connected to. (OFI-
6795)
11. When configuring Alarm Zones for MultiPort libraries, the Area, Exit Delay, Arm Not Ready,
Disable Sensors and Access Levels options are available, but do not apply. (OFI-6810)
12. When adding an netEDGE, the Door Data does not get created in the DoorData table until the
Door has been modified. (OFI-6823)
13. The font used in the Alarm Notes window cannot be changed. (OFI-6955)
14. The Desktop must be closed and re-opened in order to save the changes made to the column
widths. (OFI-6957)
15. If the Desktop Properties window is open past the “Configuration Timeout”, the window will
close without saving the changes. (OFI-6968)
16. When modifying the Desktop Properties, using the Mouse scroll wheel may cause the
Desktop to crash. (OFI-6969)
17. The Alarm Comments window name has changed to “Alarm Notes”, the term “Alarm Notes”
and “Comments” are currently used interchangeably in the Help andDesktop Properties. (OFI-
6973, OFI-6974)
18. The Alarm Notes window may show the “First Time” and “Last Time” values as the same,
even though there have been multiple occurrences of the event. (OFI-6985)

1. The Desktop may not link with the communication modules if the computer names start with
a number.
2. If having trouble linking between the Desktop and Communication modules, review the
troubleshooting in the on-line help for Desktop Links.
3. You must be using Windows sockets to do dependencies between MultiDrop & MultiRAMM
modules.
4. A dialup RAMM cannot have address 16. Address 16 is not recommended for any RAMM ,
eRAM or netEDGE. (OFI-300, OFI-2294)
5. After installation of this software, a new version of firmware will be added for the RAMM.
You must upgrade to a version newer than ‘K’ to use RAMM Encryption (AXxess NS only)
or Elevators (AXxess 202 or NS). Older revisions, which may be left from previous versions
of AXxess, should not be used.
6. Dependencies to Arm or Disarm Alarm zones will not work if the Alarm zone name has a
period in it. The period must be changed to another character to allow the dependency to
work. (OFI 5536)
7. If a badge is granted scheduled access (not 24 hour), and the update for that badge does not
make it to an eRAM, the badge will post as a “Voided card”, not a “Valid Access (Learn
MR)” as expected. The badge record must be modified to force another update to the eRAM
to get downloaded, or changed to 24 Hour which will cause a learn. (OFI-6011)
8. If MultiPort loses connection to the database, there is the possibility that one message per
module may not make it to the database once the connection is restored. (OFI-6697)
9. Scheduling Alarm Zones for MultiPort libraries does not function. (OFI-6811)
10. When using SQL Server 2005, Dependencies to send emails for normal priority events does
not work. (OFI-6849)
11. The “Control, Command” window may not come up when selecting it from the MultiPort
Manager menu. Selecting the Command button from the toolbar will bring up the command
window. (OFI-6889)
12. MultiPort Manager may not update the panel status correctly for a panel addressed as “99”.
(OFI-6896).
13. The Inovonics library installation package requires Microsoft .net 3.5 be installed for the
installation to proceed. The library does not require or use .net 3.5. (OFI-6931)
eRAM & netEDGE

1. For an eRAM panel, the "Disable" menu option in Desktop Plans does not take effect until the
eRAM is initialized. To disable an eRAM sensor without initializing, uncheck the "Enable"
box for that sensor in Configuration \ Devices \ Sensors, or disarm an Alarm Zone for that
sensor. (OFI 6136)
2. On eRAM doors with “Log Access When Unlocked” set to “No”, there are some scenarios
where a Valid Access or REX message will come through when the door is unlocked. (OFI-
6919, OFI-6839, OFI-6840)
3. It is possible to get an eRAM into a state where the tables do not contain the complete dataset.
This can happen if an eRAM is rebooted during an initialization, specifically for a very brief
period after the “Block Transfer Complete” message. (OFI-6693)
4. eRAM will fire the outputs assigned to the Elevator Group for the last Valid Access event at
the reader if a user performs a momentary on the output that matches the reader address from
either Plans, or Manual Control. (OFI-6743)
5. Dependencies for disassociated door sensors will not fire unless the “Do command if
disabled” check box is checked for the dependency. (OFI-6898)
6. With eRAM, a valid pin entry for a badge that is not allowed at a reader will post “Invalid
PIN” instead of “Wrong Shift” or “Denied Access”. (OFI-6915)
RAMM
1. Unlocking and Locking of RAMM doors from Schedule, Manual Control or Plan icon will
always fire Output 1 for Door 1, and Output 2 for Door 2, regardless of the "Assign door lock
output" setting. If the Output for a Door has been re-assigned, then Scheduled unlocks for that
Door must be done through the Output. (OFI 6137)
2. RAMM Elevator readers will report "Valid Access" but not unlock any outputs for any badge
read until an Elevator Group for that reader has been assigned to at least one access level.
(OFI 6087)
BLP Panel
1. Reader LED will only fire for 4 seconds In firmware 07-025 and earlier, not the selected
unlock time. (OFI 6131)
2. BLP firmware 07-205 or later is required for Shunt operation on eRAM. (OFI 6115)
3. Failsafe Site code verify option will not work well on badge formats that do not have a
definable site code, i.e. MiFare. (OFI 6050)
Reporter
1. If you attempt to run large reports, a large number of temporary files may be created. This can
consume a great deal of disk space. If you run out of disk space, the reporter and other
programs on the computer may lock up requiring a reboot. If this occurs, increase the amount
of free space on the computer's default drive by installing a larger drive or deleting
unnecessary files.
2. The Reporter may shutdown improperly when using command “1026 Report Print” from
Dependencies, Buttons, or Scheduled Report reminders. The report may be manually printed
without a crash. (OFI-6932)
3. The Reporter does not show a correct “Start Time” or “Stop Time” for “One Time Events”.
User must currently look at the schedule through the Desktop. (OFI-6989)
DataSync
1. If you use the DataSync utility to convert a database table with an identity field, you must
disable the identity field before running the conversion.
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

Added support for eRAM-Edge Area Controller revision (08-179) or later.
Suggested eRAM revision (08-179) or later.
Suggested BLP PROM revision (07-025) or later. (07-205 required for some features)
Release Date July 15th, 2008
eRAM Setup Utility

1. Added support for eRAM-Edge devices.
2. Added support for field upgrade of OS Kernel.
AXxess Desktop
2. Configuration items moved from Settings.ini to database. (OFI 3688, OFI-4993, OFI-6526,
OFI-6565)
3. Resolved issue with inconsistent dialog box behavior on Pop-Up commands for buttons.
(OFI-3564)
4. Removed unnecessary Area Controller commands. (OFI-3022)
5. Resolved issue with adding DVTel sensors to a plan window. (OFI-3941)
6. Resolved issue with acknowledging alarms from plan window after adding comments to the
alarm. (OFI-4254)
7. Corrected icon for Antipassback tab in Manual Control window. (OFI-4660)
8. Corrected issue where scheduled daily backup would not run on weekend days. (OFI-4964)
9. Resolved issue where deleting Operators or Devices left orphan data in database. (OFI-4998,
OFI-6172)
10. Corrected issue where camera icon would show in transaction log on workstations without
ViewPoint. (OFI-5508)
11. Resolved issue where the picture of a cardholder would show on top of the Door List of the
Precision Access tab. (OFI-5588)
12. Removed ability to put a space at the beginning of an Access Level name. (OFI-5651)
13. Resolved issue where floating windows could be closed by pressing <Enter> or <ESC>.
(OFI-6107)
14. No longer allows first character of a Precision Access Template to be a number. (OFI-6134)
15. Resolved issue where if the FloorPlan field was “_None” for an input, the plan image would
disappear whenever a message came in from that input. (OFI-6143)
16. Added Camera icon to Alarm for camera linked inputs. (OFI-6341)
17. Added ability to modify sensors with A-F in the Panel and Point addresses for MultiPort
libraries. (OFI-6463)
18. Fixed issue with putting a device on All plans. (OFI-6521)
19. Fixed issue where the maximum number of alarms would limit to 100 regardless of setting in
Desktop Properties. (OFI-6545)
20. Desktop buttons may now be configured to change CCTV views on a different Workstation.
(OFI-6551)
21. Corrected Alarm Notes window title. (OFI-6580)
22. Corrected rare improper shutdown of Desktop when the “Link All” button was clicked too
soon after enabling a module. (OFI-6610)
23. Corrected issues with Alarm Log window showing all alarms when acknowledging and
deleting alarms. (OFI-6614)
24. Corrected occasional improper shutdown of Desktop when modifying Desktop Properties.
(OFI-6609, OFI-6633, OFI-6645, OFI-6821)
25. Corrected issues where modifying Badge designs may affect site codes for access. (OFI-6641,
OFI-6642, OFI-6647)
AXxess MultiPort
2. Added support for Inovonics devices.
Area Controllers
1. Added eRAM-Edge Area Controller.
2. Added notification for doors that do not have a valid badge decode script. (OFI-6663)
3. Corrected eRAM issue where a door may unlock if the eRAM is rebooted after being
initialized when the door unlocked. (OFI-6700)
4. Corrected eRAM issue where door sensor input would not be shunted when their Alarm Zone
was disarmed. (OFI-6393)
5. Corrected eRAM issue where the door may stop unlocking the door for valid badge reads.
(OFI-6685)
Reporter
1. Corrected date format on log table reports. (OFI-6763, OFI-6764, OFI-6765, OFI-6856)
Feature changes in 4.4.0

Desktop
1. The Network and Port Settings for Area Controllers have moved to the Properties window
opened by clicking Configure. (OFI-6904)
2. For RAMM Area Controllers, the “Set” button used to configure the IP Address of a RAMM
has moved to the IP Address item in the Properties window. (OFI-6904)
3. eRAM-Edge doors cannot be added through plan design mode. They must be added in the
Configuration window, then added to the correct plan. (OFI-6913)
New known issues found in 4.4.0

Desktop
1. The text for acknowledged alarms in the Alarm Log window remains the color for the priority
of the alarm. (OFI-6679)
2. Changing the point address of an Elevator Reader to 0 from 1 or 2, and then back will cause
all Outputs to be deleted. (OFI-6742)
3. When using the Video window on the Desktop to display a DVR/NVR camera, the Desktop
can pause for a significant amount of time if the DVR/NVR cannot be connected to. (OFI-
6795)
4. When configuring Alarm Zones for MultiPort libraries, the Area, Exit Delay, Arm Not Ready,
Disable Sensors and Access Levels options are available, but do not apply. (OFI-6810)
5. When adding an eRAM-Edge, the Door Data does not get created in the DoorData table until
the Door has been modified. (OFI-6823)
6. The font used in the Alarm Notes window cannot be changed. (OFI-6955)
7. The Desktop must be closed and re-opened in order to save the changes made to the column
widths. (OFI-6957)
8. If the Desktop Properties window is open past the “Configuration Timeout”, the window will
close without saving the changes. (OFI-6968)
9. When modifying the Desktop Properties, using the Mouse scroll wheel may cause the
Desktop to crash. (OFI-6969)
10. The Alarm Comments window name has changed to “Alarm Notes”, the term “Alarm Notes”
and “Comments” are currently used interchangeably in the Help and Desktop Properties.
(OFI-6973, OFI-6974)
11. The Alarm Notes window may show the “First Time” and “Last Time” values as the same,
even though there have been multiple occurrences of the event. (OFI-6985)

1. If MultiPort loses connection to the database, there is the possibility that one message per
module may not make it to the database once the connection is restored. (OFI-6697)
2. Scheduling Alarm Zones for MultiPort libraries does not function. (OFI-6811)
3. When using SQL Server 2005, Dependencies to send emails for normal priority events does
not work. (OFI-6849)
4. The “Control, Command” window may not come up when selecting it from the MultiPort
Manager menu. Selecting the Command button from the toolbar will bring up the command
window. (OFI-6889)
5. MultiPort Manager may not update the panel status correctly for a panel addressed as “99”.
(OFI-6896).
6. The Inovonics library installation package requires Microsoft .net 3.5 be installed for the
installation to proceed. The library does not require or use .net 3.5. (OFI-6931)
eRAM & eRAM-Edge

1. With “Log Access When Unlocked” set to “No”, there are some scenarios where a Valid
Access or REX message will come through when the door is unlocked. (OFI-6919, OFI-6839,
OFI-6840)
2. When using eRAM-Edge, the reader LED doesn’t change state for REX events. It does
change state for Valid Access events. (OFI-6945)
3. It is possible to get an eRAM into a state where the tables do not contain the complete dataset.
This can happen if an eRAM is rebooted during an initialization, specifically for a very brief
period after the “Block Transfer Complete” message. (OFI-6693)
4. eRAM will fire the outputs assigned to the Elevator Group for the last Valid Access event at
the reader if a user performs a momentary on the output that matches the reader address from
either Plans, or Manual Control. (OFI-6743)
5. Dependencies for disassociated door sensors will not fire unless the “Do command if
disabled” check box is checked for the dependency. (OFI-6898)
6. With eRAM, a valid pin entry for a badge that is not allowed at a reader will post “Invalid
PIN” instead of “Wrong Shift” or “Denied Access”. (OFI-6915)
Reporter
1. The Reporter may shutdown improperly when using command “1026 Report Print” from
Dependencies, Buttons, or Scheduled Report reminders. The report may be manually printed
without a crash. (OFI-6932)
2. The Reporter does not show a correct “Start Time” or “Stop Time” for “One Time Events”.
User must currently look at the schedule through the Desktop. (OFI-6989)

Desktop
1. If using encryption between workstations and the network connection between the
workstations is slow or the network traffic is heavy, the Desktop may display some
transactions containing garbage characters. Other Desktops will display it correctly and the
entry in the Transaction Log will be correct. (OFI-2559)
manual control screen will show entries for both door 1 and 2. If door 2 is selected and
unlocked, relay 2 will unlock not relay 1 as expected for a 1 door panel. (OFI-2001)
3. When using operators with multiple languages, ensure that you configure the templates
under each language. (OFI-2428)
4. When deleting and archiving cardholder records, the archive location must already exist or
you will get an error. (OFI-2297)
5. If the ODBC drivers for Microsoft Access on the Workstation are not 2.5 or later, the
Desktop may not run. Updated drivers are included on the CD.
presented at a reader for the first time the site code is not programmed correctly and you may
get a Denied Access message for eRAM and an Invalid Site message for RAMM and
MultiDrop. (OFI-5810)
8. Precision Access Templates may be saved with the same name as an Access Level. This
causes an issue where the Template cannot be modified, and must be renamed. (OFI 6110)

1. The Desktop may not link with the communication modules if the computer names start with
a number.
modules.
4. A dialup RAMM cannot have address 16. Address 16 is not recommended for any RAMM or
eRAM. (OFI-300, OFI-2294)
5. After installation of this software, a new version of firmware will be added for the RAMM.
You must upgrade to a version newer than ‘K’ to use RAMM Encryption (AXxess NS only)
or Elevators (AXxess 202 or NS). Older revisions, which may be left from previous versions
of AXxess, should not be used.
6. Dependencies to Arm or Disarm Alarm zones will not work if the Alarm zone name has a
period in it. The period must be changed to another character to allow the dependency to
work. (OFI 5536)
7. If a badge is granted scheduled access (not 24 hour), and the update for that badge does not
make it to an eRAM, the badge will post as a “Voided card”, not a “Valid Access (Learn
MR)” as expected. The badge record must be modified to force another update to the eRAM
to get downloaded, or changed to 24 Hour which will cause a learn. (OFI-6011)
eRAM
eRAM is initialized. To disable an eRAM sensor without initializing, uncheck the "Enable"
box for that sensor in Configuration \ Devices \ Sensors, or disarm an Alarm Zone for that
sensor. (OFI 6136)
RAMM
1. Unlocking and Locking of RAMM doors from Schedule, Manual Control or Plan icon will
always fire Output 1 for Door 1, and Output 2 for Door 2, regardless of the "Assign door lock
output" setting. If the Output for a Door has been re-assigned, then Scheduled unlocks for that
Door must be done through the Output. (OFI 6137)
2. RAMM Elevator readers will report "Valid Access" but not unlock any outputs for any badge
read until an Elevator Group for that reader has been assigned to at least one access level.
(OFI 6087)
BLP Panel
1. Reader LED will only fire for 4 seconds In firmware 07-025 and earlier, not the selected
unlock time. (OFI 6131)
3. Failsafe Site code verify option will not work well on badge formats that do not have a
definable site code, i.e. MiFare. (OFI 6050)
Reporter
consume a great deal of disk space. If you run out of disk space, the reporter and other
programs on the computer may lock up requiring a reboot. If this occurs, increase the amount
of free space on the computer's default drive by installing a larger drive or deleting
unnecessary files.
DataSync
1. If you use the DataSync utility to convert a database table with an identity field, you must
disable the identity field before running the conversion.
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
AXxess 4.3.6 and eRAM 07-330 Features,
Suggested BLP PROM revision 07-025 or later. (07-205 required for some features)
Release Date December 21st, 2007
eRAM Setup Utility

1. Resolved issue found after release of 4.3.5. There was a remote possibility of corrupting an
eRAM with the eRAM Setup Utility version 1.0.8 included with 4.3.5.

Desktop
1. If the last name of a cardholder is changed, you may get a double entry in the cardholder list. The
extraneous entry will not be cleared until you click on the Refresh button or exit and reenter the
screen.
2. If using encryption between workstations and you are using a slow network or the network traffic
is heavy, you may get a transaction message containing garbage characters. Other Desktops will
display it correctly and the entry in the Transaction Log will be correct.
3. If, in one door mode and using output 2 as a General Purpose output, you must configure the
output through the door 2 screen not through the Output 2 screen otherwise door 2 settings will be
lost.
manual control screen will show entries for both door 1 and 2. If door 2 is selected and unlocked,
relay 2 will unlock not relay 1 as expected for a 1 door panel.
5. If you edit the Desktop Properties while logged on with a different language from the default, the
Desktop returns to the default language when you save the changes.
6. When using operators with multiple languages, ensure that you configure the templates under
each language.
7. When deleting and archiving cardholder records, the archive location must already exist or you
will get an error.
8. Depending what model and version you are upgrading from, the Operator passwords and
privileges may not convert correctly. After upgrading, you should check Operators to ensure that
they updated correctly.
9. If the ODBC drivers for Microsoft Access on the Workstation are not 2.5 or later, the Desktop
may not run. Updated drivers are included on the CD.
10. Scheduling Antipassback mode, Message Disables, Miscellaneous mode, Alarm Delays and Daily
Code cannot be done from the Doors menu since they require specific data. They must be done
from the Scheduled Events screen.
11. To support the eRAM, the sensors screen allows inverting the REX inputs for either door. When
used with doors on MultiDrop or the RAMM, the setting for door 1 will affect both doors and the
door 2 setting is ignored.
presented at a reader for the first time the site code is not programmed correctly and you may get a
Denied Access message for eRAM and an Invalid Site message for RAMM and MultiDrop.
14. Precision Access Templates allow a user to enter a numeric name, and should not. Numeric
Access Template names can cause undesirable results when sending badge information. To
resolve, make certain the first character of an Access Level or Precision Access Template is not
numeric. (OFI 6134)
15. Precision Access Templates may be saved with the same name as an Access Level. This causes an
issue where the Template cannot be modified, and must be renamed. (OFI 6110)
16. Selecting a Desktop window and pressing the "Enter" key will cause that window to close. Must
either close and re-open the Desktop, or go to Configuration \ Desktop Properties, and reselect the
"Show ..." option for that window for it to return. (OFI 6107)
17. Removing a Door, Door Group, Output, Output Group, or Sensor from a plan by setting the
Location option to "_None" will cause the Desktop to blank out the plan background anytime a
message comes in from that device point. (OFI 6143)

1. The Desktop may not link with the communication modules if the computer names start with a
number.
modules.
4. A dialup RAMM cannot have address 16. Address 16 is not recommended for any RAMM or
eRAM.
5. After installation of this software, a new version of firmware will be added for the RAMM. You
must upgrade to a version newer than ‘K’ to use RAMM Encryption (AXxess NS only) or
Elevators (AXxess 202 or NS). Older revisions, which may be left from previous versions of
AXxess, should not be used.
6. Dependencies to Arm or Disarm Alarm zones will not work if the Alarm zone name has a period
in it. The period must be changed to another character to allow the dependency to work. (OFI
5536)
eRAM
1. Dependencies for messages that are default priority of disabled must have "Do Command if
Sensor Disabled" checked to be performed. This is required regardless of the current message
priority. Examples of common messages with default disabled priorities are "Sensor open",
"Sensor closed", "Zone Arm", "Zone Alarm", "Zone Disarm", "Locked", and "Unlocked". (OFI
6138)
eRAM is initialized. To disable an eRAM sensor without initializing, uncheck the "Enable" box
for that sensor in Configuration \ Devices \ Sensors, or disarm an Alarm Zone for that sensor.
(OFI 6136)
RAMM
1. Unlocking and Locking of RAMM doors from Schedule, Manual Control or Plan icon will always
fire Output 1 for Door 1, and Output 2 for Door 2, regardless of the "Assign door lock output"
setting. If the Output for a Door has been re-assigned, then Scheduled unlocks for that Door must
be done through the Output. (OFI 6137)
2. RAMM Elevator readers will report "Valid Access" but not unlock any outputs for any badge read
until an Elevator Group for that reader has been assigned to at least one access level. (OFI 6087)
BLP Panel
1. Reader LED will only fire for 4 seconds In firmware 07-025 and earlier, not the selected unlock
time. (OFI 6131)
3. Failsafe Site code verify option will not work well on badge formats that do not have a definable
site code, i.e. MiFare. (OFI 6050)
Reporter
consume a great deal of disk space. If you run out of disk space, the reporter and other programs
on the computer may lock up requiring a reboot. If this occurs, increase the amount of free space
on the computer's default drive by installing a larger drive or deleting unnecessary files.
2. The Duplicate Names report may give the following warning: Warning: Null value is
eliminated by an aggregate or other SET operation. The warning can be ignored as the report
works correctly otherwise.
DataSync
1. If you use the DataSync utility to convert a database table with an identity field, you must disable
the identity field before running the conversion.
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

Suggested BLP PROM revision 07-025 or later. (07-205 required for some features)
Release Date November 30th, 2007
MultiPort
1. Fixed issue where MultiPort would not communicate with RAMMs on a fiber optic loop. (OFI
5593)
2. Optimized card expiration process. (OFI 6256)
3. Fixed issue regarding "Warning, Error sending command (44 00 FF)" message in MultiPort.
(OFI 5986)
4. Fixed issue regarding error when firing multiple Door Groups dependencies from the same input
at the same time. (OFI 6127)
Desktop
1. Fixed issue where creating an Elevator Reader and an Elevator Output on the same panel.point
could cause Elevator function to be disabled after editing the Elevator Output. (OFI 4949 & 4950)
2. Fixed issue where user was required to enter a password to log out, even if the function was
disabled. (OFI 6145)
3. Added Schedule tab to configuration options for users. (OFI 6217)
4. Fixed issue found in 4.3.4 where the specific relay to be used for Shunt operation must be selected
when configuring Shunt on an eRAM panel. (OFI 6155)
Installation
1. Added eReports MultiPort library to Workstation installation.
2. Added Texecom MultiPort library to Workstation installation.
3. Added Cathexis Cheetah ViewPoint library to Workstation installation.
4. Added Vicon Net ViewPoint library to Workstation installation.
Archive
1. Fixed issue when archiving with extended notes option enabled. (OFI 6244)
MultiDrop
1. Fixed issues with Global AntiPassback and Timed AntiPassback. (OFI 4620, OFI 6165, OFI
6170, & OFI 6171)
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

Suggested BLP PROM revision 07-025 or later
Release Date August 13th, 2007
eRAM
1. Added feature to incrementally download schedule changes.
2. Returned REX function control to panel to speed processing of these events. This change
eliminates the ability to assign door REX to a different BLP.
3. Fixed issue where if the door sensor did not open, the "Request to exit" message would not be
returned to AXxess when using "REX bypass" function.
4. Fixed issue where reader LED would stop firing if the "Door lock relay" was changed from the
default.
5. Added function to restore Doors and Outputs to current unlock state when BLP power and/or
communication is restored.
6. Fixed issue where dependencies would fire for disabled sensors regardless of the "Do Command if
Sensor Disabled" setting.
7. Added Keypad functionality on Elevator readers. "Keypad only", "Reader or Keypad", and
"Reader and Keypad" now function on eRAM Elevator readers.
MultiPort
1. Implemented incremental updates to eRAM for Schedules.
Desktop
1. In order to improve incremental updating in RAMM and eRAM, removed the ability to create
manual schedules has been disabled.
2. To centrally locate the creation and modification of schedules, the schedule for “Schedule Start &
Expiration Check” must be edited through Configuration / Schedules, and then selected in Access
Levels / Options / Schedule Start & Expiration Check.
3. Some door and sensor configuration items changed to panel commands. See Application note
AN-063 for details.
4. Added feature to track the date and time of the last time a cardholder record was modified. Date
and time stored in "LastModifiedTime" field.
5. Improved Alarm comments. Changed to "Alarm notes", and now multiple comments may be
added to an alarm with logging (date/time and operator). Predefined alarm notes may aslo be
added to the system, and selected in Alarm notes window.
ViewPoint
1. Issue where entering the properties screen on Viewpoint would cause Viewpoint to crash has been
resolved.
Panel
1. Firmware version 07-205b improved failsafe operation of LEDs for badge and REX access.
2. Resolved issue where BLP would enter Failsafe mode imediately upon power up when Failsafe
mode is configured, but Failsafe timer is zero.
3. Firmware version 07-205b allows Shunt operation with eRAM.
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Suggested BLP PROM revision 07-025 or later
Release Date June 20, 2007
eRAM
1. Added feature to restore output unlock state on power restore.
2. Fixed issue where disabled door sensors could cause valid access messages to be disabled.
3. Fixed issue with "Do command if sensor disabled" option in dependencies. Dependency would
fire regardless of sensor disable state.
MultiPort
4. Fixed issue where code 3 of 9 barcode badge reads could display incorrect names.
5. Fixed issue where missing expiration dates could cause badges to not allow access.
6. Improved incremental updating to eRAM for Cardholder and Access level changes to Doors, Door
Groups, and Elevators.
Desktop
7. Made many internal changes to implement the incremental updating of eRAM.
8. Plan tooltips for icons may now be disabled.
9. Implemented automatic refresh of cardholder window when copying a cardholder.
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

AXxess 4.3.2 and eRAM 07-061 Features, Suggested BLP PROM revision 07-025
Release Date March 22, 2007
eRAM
1. Fixed issue where REX input while Door Sensor in Open state could disable card reads untile
door closed.
MultiPort
2. Enhanced Incremental Updates to eRAMs.
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

AXxess 4.3.1 and eRAM 07-045 Features, Suggested BLP PROM revision 07-025
Release Date February 23, 2007
RAMM
eRAM
1. Network Encryption option added.
2. Added internal system commands for getting eRAM panel status and alarm zone status.
3. Fixed several issues with alarm zones.
4. Fixed lockup issue related to dependencies triggering outputs (TB-029).
BLP Panel
3. Twelve (12) site codes downloaded to the BLP’s for degraded mode.
Desktop
5. Selecting a calendar for a RAMM is now a selection box instead of having to type the entry.
6. Virtual Alarm Events (via icons on plans)
7. Different starting plan by operator
8. Precision templates are now remembered so that changing a template will also update all the
cardholders using the template.
9. Individual cardholder templates allow their own site and badge structure.
10. Twelve (12) site codes definable in the GUI
11. Enhanced security, installation of workstations require password generated by the AXxess server,
a different password is generated on every install.
12. Windows authentication can now be used to log into the AXxess desktop.
13. Dependencies to run reports can now specify the workstation to run the report at.
14. Database Manager, SQL statements can now span lines by using a continuation character.
15. Activated Points and Disabled Sensor windows now show the total.
16. On new systems, a default access level called _None with no doors is added
17. Fixed picture showing in wrong tabs in cardholder template.
18. Fixed new schedules for cardholders not getting downloaded to RAMM’s or eRAM’s
19. Fixed cardholder changes being savable even if required fields weren’t filled in.
20. Fixed operator email changes not updating dependencies to send email.
View Point Monitor libraries*

21. CCTV Monitor renamed to ViewPoint
22. Stand-alone mode added to allow configuration and maintenance without having to run AXxess at
the workstation.
23. Major redesign of configuration screens.
24. New tabs for moving between search screens.
25. Added dynamic view mode to automatically add cameras to a view based on system events.
26. When adding a new device, a view for its cameras is automatically added.
27. Added drag and drop for adding cameras to views.
28. Fixed problem if multiple devices of the same type were used with MultiPort for event logging
from the cameras.
29. Dedicated Micro NetVU updated to version 4.2.4.6228
30. DVTEL updated to version 3.5
31. Webview updated to 4.3.0.6256
32. Open Eye updated to version 2.4.3.15
33. Local Capture now supports more than one device
34. New features added to American Dynamics Intellex
35. Implemented Samsung SVR
36. Implemented SYAC DVR
37. Implemented DSU 1000 (limited features)
NOTE: The ViewPoint must be licensed separately.

NOTE: The ViewPoint requires higher computer performance. Contact the factory for specific
requirements
MultiPort
38. Integrated all communications to RAMM and eRAM from MultiRAMM to MultiPort.
39. MultiPort Manager displays the communication status for both Area Controllers and door panels.
40. A common command engine in MultiPort allows dependencies, direct commands and scheduled
commands to support the same set of commands.
41. Runs as a service, log in not required
42. Higher security as a service
43. In case of a server restart, service starts communication to hardware with no user intervention/log
on.
44. Multithreaded - RAMMs and eRAMs communicate on separate threads simultaneously.
45. Upgrades convert automatically from MultiRAMM to MultiPort.
46. New features added to the Generic Interface Library to better extract data from variable strings.
Archive
47. Modified to improve performance during transaction delete. Previously on a large database, the
system could lock up when archive was deleting.
New Libraries
48. Import/Export (automatic) - see application note AN-045
49. Time and Attendance (calculations)
Reporter
50. Version information is in the database and the configuration report now shows the panel type such
as wiegand, barcode or input module.
51. Column sort feature added.
52. Colored lines added to make display more readable.
53. Several reports updated and corrected.
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
New features and fixes in version 4.2

General
2. The Microsoft Access database is no longer supported. When upgrading to this release, you must also
convert the database to SQL Server.
3. Support added for mixed systems that use both the new eRAM and older RAMM products.
4. Many changes and new features to support the new eRAM area controller.
5. A new Registration scheme was implemented with version 4.1. On new installations or when an older
system is upgraded to 4.1, you will need to contact the factory for a new registration number or file.
This registration file must then be loaded into the AXxess database. See the online help under
Registration.
6. A new Registration scheme has been implemented. On new installations or when an older system is
upgraded to 4.1, you will need to contact the factory for a new registration. If you r system is basic,
you will be given a new registration number. However, if you are using features such as CCTV or
MultiPort, you will receive a registration file. This registration file must then be loaded into the
AXxess database. See the online help under Registration.
7. Implemented a new method of installing optional CCTV and MultiPort modules from the server, just
like installing workstations.
eRAM
8. The eRAM is a new generation of Access Controller that combines many of the features of the existing
RAMM and BLP products. Many commands are done differently and most of the commands used by
the BLP panel are no longer sent directly to the panel as they are performed by eRAM. For example,
all relay timing is done by eRAM so command 10 is no longer sent to the panel. In addition, some of
the limitations of the RAMM/panel combination are no longer there such as some commands which
applied to both doors on a panel can now be set individually. For example, the REX input parameters
can now be set individually.
9. Added support for custom badge formats up to 64 bits and magnetic badges.
10. Allow custom PINs up to 8 digits.
11. Added capability of one time scheduled events.
BLP Panel
12. If you are using the new eRAM, you will need to upgrade the firmware in your panels to 06-018 or
later.
Desktop
13. The Cardholder table has been modified to create a unique identification field on each cardholder. As
a result, it is no longer necessary to add an entry in the IdNumber field on a template. Templates are
modified to use this Id field as the key field. To implement the Id field, the unique key has been
removed from the IdNumber field. If you are using custom templates, they will be updated to use the
Id field.
14. Major changes have been made to the way that commands are entered for Doors, Sensors, Outputs, etc.
Previously, commands were entered as they were sent to the panels. Several commands included
multiple features, which could be confusing. In the new layout, each entry configures only one feature
and the software recombines them before sending them to a panel. Refer to the on-line help for a cross
reference of the new and old commands.
15. New screen added to Control menu to forgive antipassback violators. Now based on areas, rather than
individual doors.
CCTV Monitor*
NOTE: The CCTV Monitor requires higher computer performance. Contact the factory for specific
requirements.
16. Added support for On-Net Surveillance NetDVR and NetDVMS.
EndPoint*
17. Added support for the new EndPoint product.
MultiPort*
18. Added support for DMP panel.
19. Added capability of sending strings to remote devices.
20. Added optional heartbeat to monitor remote communication.
21. Added Email Client to receive emails and process as an alarm.
MultiRAMM
22. Many updates to support new eRAM. See Desktop list for eRAM features.
23. Fixed Dependencies to off-line CCTV Monitors causing delay.
NOTE: Some features are not available in AXxess Lite or AXxess Express and are marked with *
Known issues with version 4.2
eRAM
1. This release of eRAM does not support communication encryption, elevator or dialup operation.
Consult factory for detailed limitations.
2. Momentary operation of output groups does not work correctly from the Desktop’s floor plan.
Desktop
3. If the last name of a cardholder is changed, you may get a double entry in the cardholder list. The
extraneous entry will not be cleared until you click on the Refresh button or exit and reenter the
screen.
4. If using encryption between workstations and you are using a slow network or the network traffic is
heavy, you may get a transaction message containing garbage characters. Other Desktops will display
it correctly and the entry in the Transaction Log, will be correct.
5. If, in one door mode and using output 2 as a General Purpose output, you must configure the output
through the door 2 screen not through the Output 2 screen otherwise door 2 settings will be lost.
6. An alarm zone without sensors does not indicate correctly in the Alarm Zone control screen. You must
have at least one sensor in the zone.
7. When a panel is set for 1 door mode and Show in Control List is checked for both doors, the manual
control screen will show entries for both door 1 and 2. If door 2 is selected and unlocked, relay 2 will
unlock not relay 1 as expected for a 1 door panel.
8. If you edit the Desktop Properties while logged on with a different language from the default, the
Desktop returns to the default language when you save the changes.
9. When using operators with multiple languages, ensure that you configure the templates under each
language.
10. When deleting and archiving cardholder records, the archive location must already exist or you will get
an error.
11. Depending what model and version you are upgrading from, the Operator passwords and privileges
may not convert correctly. After upgrading, you should check Operators to ensure that they updated
correctly.
12. If the ODBC drivers for Microsoft Access on the Workstation are not 2.5 or later, the Desktop may not
run. Updated drivers are included on the CD.
13. Scheduling Antipassback mode, Message Disables, Miscellaneous mode, Alarm Delays and Daily
Code cannot be done from the Doors menu since they require specific data. They must be done from
the Timed Events screen.
14. To support the eRAM, the sensors screen allows inverting the REX inputs for either door. When used
with doors on Multidrop or the RAMM, the setting for door 1 will affect both doors and the door 2
setting is ignored.
Communication modules (Multidrop, MultiRAMM, MultiPort)
15. The Desktop may not link with the communication modules if the computer names start with a
number.
17. You must be using Windows sockets to do dependencies between Multidrop & MultiRAMM modules.
18. A dialup RAMM cannot have address 16.
19. After installation of this software, a new version of firmware will be added for the RAMM. You must
upgrade to a version newer than ‘K’ to use RAMM Encryption (AXxess NS only) or Elevators
(AXxess 202 or NS). Older revisions, which may be left from previous versions of AXxess, should not
be used.
Reporter
consume a great deal of disk space. If you run out of disk space, the reporter and other programs on the
computer may lock up requiring a reboot. If this occurs, increase the amount of free space on the
computer's default drive by installing a larger drive or deleting unnecessary files.
21. The Duplicate Names report may give the following warning: Warning: Null value is eliminated by
an aggregate or other SET operation. The warning can be ignored as the report works correctly
otherwise.
DataSync
22. If you use the DataSync utility to convert a database table with an identity field, you must disable the
identity field before running the conversion.
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

General
1. Many changes and new features to support the new eRAM area controller.
2. A new Registration scheme has been implemented. On new installations or when an older system is
upgraded to 4.1, you will need to contact the factory for a new registration file. This registration file
must then be loaded into the AXxess database. See the online help under Registration.
3. AXxess Lite and Express can now use a SQL Server database and use sockets for inter-module
communication.
4. PointLink sensors have been discontinued and may not be supported in future releases.
eRAM
5. The eRAM is a new generation of Access Controller that combines many of the features of the existing
RAMM and BLP products. Many commands are done differently and most of the commands used by
the BLP panel are no longer sent directly to the panel as they are performed by eRAM. For example,
all relay timing is done by eRAM so command 10 is no longer sent to the panel. In addition, some of
the limitations of the RAMM/panel combination are no longer there such as some commands which
applied to both doors on a panel can now be set individually. For example, the REX input parameters
can now be set individually.
BLP Panel
6. To use some of the new features of eRAM, such as keypad modes or badge universe greater than 5
digits, it may be necessary to purchase new firmware for the panels. Firmware version 05-111 or later
is required. Consult your dealer or the factory for requirements.
Desktop
7. The Cardholder table has been modified to create a unique identification field on each cardholder. As
a result, it is no longer necessary to add an entry in the IdNumber field on a template. The default
templates have been modified to use this Id field as the key field. However, if you have created custom
templates you should modify them to use the Id field for the key field. To implement the Id field, the
unique key has been removed from the IdNumber field. If you still want to use the IdNumber field for
templates, you must put this key back to ensure that duplicates IdNumbers cannot be created.
NOTE: You must use the Id field if you are using Precision Access.
8. Added new Schedule table and data entry screen for entering predefined schedules. These make
configuration easier and speed up system initialization when using RAMMs
9. Added option to ‘float’ the Desktop’s windows outside the desktop.
10. Desktop windows now have a title bar showing their status. When sizing the windows, the title bar
shows the window’s dimensions.
11. Add Enhanced Network setting in Remote Access Memory Module screen to support new eRAM
12. Implemented Precision Access for doors on the new eRAM
13. Added cardholder-selectable unlock time (ADA requirement) with eRAM
14. Add card use decrementing feature (debit) with eRAM.
15. Added better incremental updating of cardholders when using eRAM.
16. Added schedules to automatically perform daily database backups and monthly log archiving.
17. Disabled sensors or locked-down doors now display on the plan with a blue cross through them
18. Doors now display on the plan with a lock/unlocked icon so that they can indicated unlocked and open
and unlocked and closed, for example.
19. Deleting a MultiPort library now deletes all the sensors, etc.
20. Fixed problem with using the local default printer override when printing badges.
21. Bar codes can now be printed with .003” line width.
22. The Multi-modules are now minimized when an operator logs off or the Desktop is shut down.
23. Any open screens are closed when an operator logs off.
24. A new sound engine has been added that allows the Desktop operation to continue when multiple
sounds. This results in faster Desktop operation as well as preventing alarm icons from indicating
incorrectly if too many sounds were being played. Also multiple speech and sounds be used in an
alarm annunciation.
25. The CCTV Monitor and CCTV Configuration can now be started from the Desktop.
26. If capturing multiple images to a badge, you no longer have to capture and save each one separately.
27. Fixed problem in Update Database SQL causing database error when upgrading.
28. Running the Update Database SQL doesn’t reload the commands table anymore. Previously, if a user
had customized the panel commands, they would get overridden in an upgrade.
29. Added checkbox in Doors to set one-door mode.
30. Fixed problem with ‘Reload Picture’ commands from badging being accumulated in the Updates table
causing Multidrop and MultiRAMM to occasionally crash.
31. Fixed problem with Video window causing the Desktop to crash when it couldn’t connect to the
camera.
32. Fixed problem with printing the ongoing transactions to other than the default printer.
Archive
33. Added option to change the name of the saved file.
34. The end date is now saved so that subsequent archives will end the same number of days in the past.
35. Fixed problem with determining the start date if there were date errors in the Audit table.
CCTV Monitor*
36. Added new search screen for searching the transaction log for events associated with cameras.
NOTE: The CCTV Monitor is only supported on a SQL Server database and must be licensed separately.
requirements.
CCTV Monitor libraries*
37. Updated version for Cieffe DVR.
38. Fixed problem in Cieffe Proxima with playback time offset.
39. Fixed problem in Cieffe libraries causing the cameras to display in the wrong window if a server was
down.
40. Updated version for Pelco DX8000 DVR
41. New Pictures library to display pictures at multiple doors when badges are read.
42. New library for American Dynamics Intellex DVR.
MultiRAMM
43. Modified to support new eRAM.
44. See Desktop list for eRAM features.
Reporter
45. Report Open screen can now be resized allowed viewing of more reports.
46. Fixed problem with prompts on transaction type reports.
47. Add up/down buttons in wizard to make changing sort Order easier.
Analyze Levels
48. Increased timeout so wouldn’t fail when analyzing databases with a large number of scheduled access
level changes.
NOTE: Some features are not available in AXxess Lite or AXxess Express and are marked with *
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

Archive
1. Option to edit saved file name added
Desktop
2. If a new alarm arrived while comments were being added to an existing alarm, the wrong alarm could
get acknowledged.
3. Fixed monthly and annually scheduled reminders, reports and SQL’s not working.
4. Fixed badging sometimes blowing up when the capture screen displayed.
5. Fixed icon not returning to the default state after an alarm was acknowledged for certain messages
such as No Response.
6. Fixed some fields on a badge printing with the wrong data if other fields contained constants along
with a query.
7. Fixed partitioning not working correctly for doors or levels with 40 character names. *
8. Printing an empty barcode now doesn’t print anything. Used to print just the start and stop codes.
9. Editing a badge design used to cause a dialup MultiRAMM to dial its units.
10. Fixed an error in the !MID function
11. Updated help for command 34.
12. Updated help for Video Capture.
CCTV Monitor*
13. Added capability of displayed 25, 36, 49 and 64 cameras per view.
14. Deleting a CCTV Server did not delete all the corresponding cameras, sensors, etc.
15. Some types of configuration changes did not trigger a system reload. As a result, the communication
modules had to be manually restarted for changes to take effect.
16. The cameras windows did not maintain the correct aspect ratio as they became smaller.
NOTE: The CCTV Monitor is only supported on a SQL Server database.
requirements.
CCTV Monitor libraries*
17. Updated version for Cieffe DVR
18. Updated version for Dedicated Microsystems DVR
19. Updated version for OpenEye DVR
20. Added support for Toshiba Surveillix DVR
Multidrop
21. Display Multidrop version in title bar.
22. Fixed command 34 not getting sent to older version panels
MultiRAMM
23. Display Multidrop version in title bar.
24. Fixed site code getting sent incorrectly to BLP-200 barcode panels.
25. Disabled Record Not Found messages triggered by command 16.
26. Fixed MultiRAMM crashing if initialization commands were internally generated for disabled or non-
communicating units
27. Fixed alarm zone toggle dependency
Reporter
28. Fixed Alarms, Current report not working
Show Configuration
29. Fixed the configuration report from the Desktop’s About screen not always printing.
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

Desktop
1. Major changes to the Transaction Window including:
Cardholder transactions will show a cardholder icon if the cardholder has a picture on file. Clicking on the
transaction will show the picture. This allows viewing multiple pictures if several cardholders pass
through a door close together.*
Sensors with an associated camera will show a camera icon. Double clicking on the transaction will display
the recorded video associated with the event.*
If the transaction window is clicked on, it will start buffer events so that events can be reviewed without
scrolling off the screen. After 30 seconds, the screen will return to normal.
Additional columns have been added to the transaction and all columns can be individually hidden.
Horizontal lines are displayed between transactions to make them more readable.
2. Added warning if the Alarm Table gets too large as it can cause the system to slow down if proper
housekeeping is not performed.
3. The Department screen has been added for Lite and Express.
4. Output Groups have been added.
5. When adding a new Output, it would show a door icon instead of an output icon.
6. If the address of a door in a door group was changed, it could cause a door group that spanned
modules and cause inconsistent operation of the door group. This has been fixed.
7. Badge design now allows left, center and right justification on rotated text fields. *
8. In Badges, fixed a problem with pre or post constants in a field variable. e.g. 000000{badge from
AxPerson}223 would display correctly on the screen but the constants would be missing when printed.
*
9. The alternate printer mode in badges to allow different workstations to use a different printer for the
same badge has been fixed. *
10. In Badges. alternate save locations have been added for Pictures and Signatures to allow them to be
stored locally and on a server, for example. *
11. Video capture in badging implement using custom libraries. Libraries included for ValCam PTZ
camera, Axis PTZ camera, Sony PTZ camera as well as local video. *
12. If a template was converted from single to multiple page format, the top would be cut off. This has
been fixed. *
13. Can now set up monthly schedules for Reminders, Reports or Scheduled SQLs.
14. Changing the name of an area did not cause Multidrop and MultiRAMM to reload.
15. Fixed the problem with the schedule option for Alarm Zones disappearing.
16. If a panel was reset, the plan icons could get out of synchronization with the actual sensor. Now the
sensors are resynchronized when a panel is restored. *
17. A No Response message could cause the icon on the plan for a panel to change to the wrong icon. *
18. In the Configuration screen for doors, sensors, etc. the icon beside a variable is now more consistent
with the value of the variable.
19. The Dependency screen has had a major overhaul to allow more dependency options.
20. Dependencies to execute a program can now display any file type registered with Windows.
21. Buttons can now open any file type registered with Windows such as PDF or Word files. *
22. Alarms from MultiPort would continue to blink after being acknowledged. *
23. Help for door commands updated.
24. Help Screens updated.
CCTV Monitor*
25. Playback, Clip and Image support added for DVTel DVR.
26. Implemented video display of Integral DVR.
27. Implemented Sony web camera.
28. Implemented views by password.
29. Implemented sensor-camera links to allow video replay of events from the Desktop.
NOTE: The CCTV Monitor is only supported on a SQL Server database.
NOTE: The CCTV Monitor is not supported on a Microsoft Access database. SQL Server must be used.
requirements.
Multidrop
30. Dependencies downloaded to a panel are no longer performed by Multidrop as it could cause double
triggering if events were delayed in being received.
31. If new Dependencies were added, they were not downloaded to the panels, if that option was selected.
32. If Dependencies were deleted, they were sometimes not removed from the panels.
33. Out of Time Zone and Not Allowed functions implemented.
34. Fixed holiday schedules not getting downloaded to panels correctly if an alternate calendar had been
selected.
35. The lockdown command now works with older and newer panels, automatically by sending command
57 to new panels and command 09 to older panels.
36. If a badge was read at door 2 of a one-door panel and it had to be learnt, it would trigger the door 2
relay instead of the door 1 relay.
DataSync
1. Added new option to allow merging databases without overwriting duplicate records.
MultiPort*
1. Implemented Socket connections for attached devices.
2. New library included that monitors all the Multi-modules on all Workstations and records events in
the Windows log. This can be used to trigger emails for example if programs blow up or are shut
down.
RAMM / MultiRAMM
37. Disabled events were being stored in the Transaction log.
38. Internal changes made to speed up operation with large databases
39. Operation with dialup panels improved to ensure that updates made while connected get sent
immediately and do not have to redial up after disconnecting.
Reporter
40. Added drop list to select Archived Database for operator, alarm and Time and Attendance reports.
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

Desktop
1. Old Protocol is no longer supported.
2. The Badging shortcut from the Windows desktop did not come up in badging. *
3. Fixed data base error if field contained a single quote (multiple locations).
4. Added Help button to Location screen. *
5. Fixed crash if clicked on Plan Design button if plans were not being used. *
6. If deleted a Sensor, Door, etc., custom menus, messages and commands were not always removed
from the database. *
7. Fixed screens occasionally timing out prematurely.
8. The Desktop’s Personnel menu now updates to show the current operator’s templates after logon. *
9. The Dependencies screen overhauled to add additional dependencies and commands.
10. Implemented Font Scripts for the Transaction Screen and Alarm Screen.
11. Added capability to view and capture on the reverse side of a badge design from the Cardholder
Screen. *
12. The Custom Button can now execute command (.BAT) files. *
13. The Operator Screen did not list all installed templates, only those installed at the workstation. *
14. The Function list in the Operator screen had missing functions as well as functions unusable for the
version. *
15. The Access Level in the Cardholder Screen could default to the wrong one if his Access Level had
been deleted from the database.
16. Manual Refresh button added to the Cardholder Screen to reload the cardholder list.
17. Removed the Location button in AXxess Lite and Express.
18. Fixed the Picture Screen on the Desktop not showing correctly for Denied Access. *
19. When deleting an item in the Custom Menu screen, the wrong item could get deleted. *
20. Deleting an Elevator Group could delete the schedules for a Door Group with the same name. *
21. Simplified Elevator configuration. *
22. The Expired Badge and Invalid PIN messages now show the cardholder’s name.
23. Non-zero Time Zone entries in the RAMM settings were not saved correctly and could result in the
wrong time zone offset.
24. Actions defined for Single Click and Double Click on the Plan Screen only worked for
Administrators, not Operators. *
25. When adding a device from the Plan Screen, the icon would not always be located exactly where you
clicked. *
26. Added printing support for Code 128, module 43 for the health care industry. *
27. Fixed Code 128, subset C not printing correctly. *
28. Added capability to save a SQL Server backup with different names so as not to overwrite a previous
backup. *
29. Floor plan devices now support additional functions from the popup menus. *
30. Can now manually enter the workstation name instead of having to browse it in Multidrop and
RAMM screens.
31. Help Screens updated
CCTV Monitor
32. New module for CCTV monitoring and control added with links to Desktop icons.
33. Implemented support for Axis network cameras
34. Implemented support for Salient Systems CompleteView Digital Video Recorder.
Importer
35. The Importer task bar did not show progress correctly.
Multidrop
36. Old Protocol is no longer supported.
37. Multidrop could give an ‘hstmt’ error if running SQL Server when you went into the Sensor Control
or Alarm Zone Control screens on the Desktop.
38. Lost badge and Denied Access messages implemented.
39. The Cardholder’s Last Use fields could get updated out of sequence with dialup panels.
RAMM / MultiRAMM
40. Fixed nuisance error when disabling a sensor on a RAMM from the Plan Screen. *
41. Lost badge and Denied Access messages implemented.
42. Secure events from a RAMM were not prioritized correctly if set to Disabled or None.
43. The Cardholder’s Last Use fields could get updated out of sequence with dialup panels.
44. Valid Access (Learn) did not update the Last Use fields.
45. Points Status on the floor plan not always updated correctly with dialup panels.
46. Custom Messages and Priorities not downloaded correctly.
47. RAMM firmware modified for new limits as follows:
a. Access levels increased from 254 to 999.
b. Scheduled events increased from 2500 to 4000.
c. Maximum badge number reduced from 100000 to 98000.
d. Elevator configurations reduced from 14000 to 10000.
e. Minimum transactions stored when offline reduced from 10000 to 5000.
NOTE: If any of the above limits are exceeded, a warning message will be displayed and the discarded
items will be listed in the System Log. To ensure that the RAMM operates correctly, these discarded
items should be removed from the database.
48. AXxess Express now supports up to 5 RAMMs.
CCTV Distributor
49. Added CCTV integration to the Pelco 6700/6800 switch. *
50. Implement support for a socket connection to a device in the CCTV Distributor. *
MultiPort
51. Additional dependencies added to MultiPort. *
52. Added support for Salient Systems CompleteView motion and alarm reporting.
Reporter
53. Operator Log now uses new transaction report format.
54. Added drop list to select Archived Database.
55. Can now run multiple long reports in parallel.
56. Fixed Start time and Stop time in Archive reports showing the times in the live database.
Installation
57. The Adobe Acrobat viewer did not install from the CD menu.
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

NOTE: Some features are not available in AXxess Lite or AXxess Express and are marked with *. A
number of security features are only available in AXxess NS.
NOTE: Some of these changes were implemented in the limited release of AXxess, version 4.0.0.
Plans*
AXxess 202 and NS version 4.0.1 feature a major change in the way that operators interact with
the system both during initial configuration and also when monitoring the active site. This is
done using an interactive graphical interface based on plans of the site. Basic features of this
interface are:
1. Typically starting at a main campus plan, multiple sub-plans of the building are configured to create a
hierarchy of plans. Plan buttons are placed to allow navigating to the different plans that display the
site.
2. During configuration, doors, sensors and other points are placed on these plans. Icons are defined for
the different states and sensor functions.
3. The points indicate their real-time status, such as door opening and closing, by changing their image.
4. Alarms at unacknowledged alarm points indicate by flashing a red rectangle around them.
5. The current status of a point is displayed when the mouse cursor is positioned over it.
6. Points in alarm can be acknowledged by clicking on them.
7. Points can be controlled by left-mouse clicking or double clicking to execute user-defined commands.
8. Points can be controlled by right-mouse clicking on them to bring up user-definable menus of available
functions. Many systems functions and panel commands can be added to these user-definable menus.
9. Two new status windows allow monitoring points that are disabled or disarmed and points that are
unlocked or activated.
10. CCTV points allow selecting cameras and controlling PTZ domes and other CCTV equipment.
11. General purpose button points allow running external programs, displaying or printing reports,
executing SQLs or performing many other functions from a popup menu.
Security features (AXxess NS)*
12. Added 128 bit Rijndael encryption between modules to prevent unauthorized monitoring or control of
the system.
13. Added 128 bit Rijndael encryption between MultiRAMM and the RAMMs in direct connect, dialup
and network communication modes.
14. Implemented User Name and Password for operators.
15. Strong password option added.
16. Implemented partitioning of cardholders, doors and access levels to limit cardholder editing and
configuration by operator.
17. Added option to expire passwords.
Other enhancements and fixes
18. Many settings have been moved from the local SETTINGS.INI file to a new Settings table in the
database. This simplifies configuring the system from any workstation. This new screen is accessed by
clicking the Configuration and Desktop Properties menu and selecting the Settings tab (formerly
Miscellaneous).
19. Cardholder limit for AXxess Lite increased to 1000 with 20 access levels. Limits for AXxess Express
increased to 5000 with 100 access levels.
20. User interface in all modules are now Windows Xp format when running on Windows Xp.
21. Implemented different languages by operator login.
22. Badges can now expire at different times of day.
23. Desktop cardholder pictures can now be displayed from any door and image and include door location
and cardholder name.*
24. Desktop cardholder picture now times out.*
25. Messages, icons, sounds and instructions can now be customized for all door, sensor and output
messages.*
26. Password screen now pops back up if password error.
27. Added automatic logoff if no operator activity.
28. Increased the number of allowed templates and added the option to select any combination of template
for each operator.*
29. Added voice annunciation for alarms.*
30. Updated database to SQL Server 2000.*
31. SQL Server is now started automatically if not running.*
32. Badging now supports multiple batch files by Workstation and template.*
33. When starting up the Desktop, the password screen is optionally presented for immediate logon.
34. Added SQL to allow scheduled expiration of cards that have not been used for a number of days.*
35. The time to bring up the Configuration and Cardholder screens has been significantly sped up.
36. An icon has been added in the tool bar to display the communication link screen and to indicate the
link status.
37. New Archive program added to archive system logs. It runs as a separate independent program and
can be scheduled to run when the system is quiet.
38. New Show Configuration program added to display many system parameters such as firmware and
software versions and basic configuration settings. The output can be printed, emailed or saved to file.
39. New Importer program added to schedule automatic database updates from external sources.
40. New Analyze Access Levels program added for analyzing access levels in order to show duplicate
configurations and to help optimize configuration.
41. Added option to email alarms (requires Windows 2000 Server or Windows Messaging Services).*
42. Implemented door lockdown function.*
43. If an operator logged out without closing the configuration or cardholder screens, changes could still
be made. Now the operator cannot log off without closing the screens.
44. When you have multiple workstations and you use the incrementing badge variable, the potential for
generating the same badge number existed and could cause database errors on saving because of a
duplicate badge. An option was added to always increment the badge to ensure that this can’t happen.*
45. The configuration screens could take a long time to load if the computer could not find a default
printer.
46. Automatic relinking has been improved if a local or network module shuts down or the network drops
out.
47. When importing doors or upgrading from a previous revision, doors would not always show in the
Access Levels screen.
48. An access level with AND in the name causes an error when the access level is double clicked to go to
cardholder screen.
49. If you canceled out of the Comments screen, the alarm was still acknowledged.
50. If a text field was too long in a badge design, it could cause the desktop to blow up.*
51. When displaying badge design with localized setting set to metric, the default grid was too dense and
caused a gray screen.*
52. If storing the badge-printed date when a badge is printed with the date set to non-US format, you
would get a date format error when printing a badge.*
53. If you cut from one field and pasted into another in a cardholder record, you would lose the last
character.
54. The IdNumber field has been adding to the Transaction and Time & Attendance tabled allowing more
detailed cardholder reporting.
55. Added MultiPort module to integrate with other equipment such as fire panels and gas detectors.*
56. In Template or Badge Design, if you clicked on the Delete button in the Select Field screen to delete
a field, there was no way to cancel. Hitting the close button still deleted the field.*
57. In Template or Badge Design, if you added a new field to a database table in the Select Field screen,
the Select button was still grey and you had to click on the already selected new field to enable it.*
58. If run the SQL command to change RAMM 1 to RAMM 11, for example, you could not delete RAMM
1 because the MultiRAMM screen thought it was still in use.*
59. You could pick 'Disabled' and 'Command' in the dialout priority list for a RAMM, which are not valid
dialout priorities.
60. The Looked At alarm feature, which had never worked correctly, was removed.
61. The software no longer works under Windows 95.
62. With multiple domes connected to CCTV Distributors on different workstations, only the first one
selected could be controlled.*
63. Open CCTV Distributor ports were not closed when the device table was reloaded due to configuration
changes. Consequently, if serial ports were reassigned, the old port could not be reused until the
distributor was closed down.*
64. Added the capability of appending records in the DataSync program.
65. Added support for a single RAMM in AXxess Express.
66. Dependencies for RAMM alarm zones and door groups did not work between workstations.*
67. If a RAMM was offline, the Door Forced/Held and Closed messages could come in out of order.
68. If a single input was used to trigger dependencies on multiple RAMMs, some of them might not be
triggered..
69. MultiRAMM now sends messages to the Desktop on initialization progress and dialup connections
70. Improved performance for MultiRAMM dialup connections.
71. If all dependencies for a RAMM were removed from the database, they were not deleted at the
RAMM.
72. If a RAMM had elevators and certain changes were made to the RAMMs configuration, the elevator
mode could stop working until reinitialized.*
73. If a dependency cannot complete, it now creates an alarm message.
74. Implemented a new user interface for running transaction reports.
75. Added capability of reports using stored procedures in SQL Server.*
76. Format for dates in a report is now user-definable and defaults to the current locale.
77. Fixed memory leak when running repeating reports.
78. The reporter did not display Real, Numeric or GUID data types.
79. It was possible to configure an operator such that they could edit read-only reports.
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

DataSync
1. Fixed: If a table or field had been added with a space in the name, DataSync would give an error.
Desktop
2. Fixed: Version 3.0.6 did not allow entering custom Facility code
3. Fixed: If printing badges in batch mode, it would only print the default record.
4. Fixed: The Add Commands table (RAMM) SQL did not correctly set the mask for the RAMM
encryption key to allow A thru F to be entered.
MultiRAMM
5. Fixed: You could not disable requiring a password to open MultiRAMM.
6. Fixed: Acknowledged alarms show “Test” for the AcknowledgedBy field in the AlarmList report
Multidrop
7. Fixed: No Response from Command 56 on new doors. To fix existing doors, you must edit the
Keypad timer value under door 1 to ensure it is 5 digits.
8. Fixed: Dependencies were displaying in black rather than blue.
9. Fixed: If using cardholder ins & outs to arm & disarm alarm zones and a cardholder did not clock out,
he would not be able to disarm the system in the morning if it was armed from a schedule during the
night.
10. Fixed: You could not disable requiring a password to open Multidrop.
11. Fixed: Expired cards could sometimes unlock the door once after an initialization or schedule change.
12. Fixed: Could get “Connection is busy with results for another hstmt” if using a SQL Server database.
13. Fixed: If a door was in multiple door groups and those door groups were used for access control, only
one of the groups would be used and cards valid for the other groups would not be validated correctly
when the door is fully initialized. However, the badges were being corrected by learn mode or by
incremental updating such as tickling the door group in the access level screen.
14. Fixed: Perpetual holidays were not being downloaded to the panel if downloading schedules.
15. Fixed: Command 61 with a large number of Timed Events in the panel could cause a No Response and
the timed event messages would be returned a minimum of twice.
16. Fixed: If multiple zones are armed at the same time, the exit timer only works for one of them.
17. Fixed: In a dialup Multidrop, if entries exist in the database for missing points, it could create
commands that could not be sent. These would not be purged and could cause failure to dialout for
valid commands.
18. Fixed: If a PointLink sensor was inverted, it could indicate the incorrect state in the control window.
19. Enhancement: Multidrop will now automatically convert enhanced protocol command format to old
format for use in mixed protocol systems.
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

Desktop
1. If a template had a multi-line edit box, a database error would occur when you saved the record.
2. If using the Transaction printer and then disable it with transactions pending in the print buffer (shown
in status line), the buffer is not purged.
3. There was a memory leak in painting the headers at the top of the transaction windows. Given enough
time and transactions, the Desktop could blow up.
4. In version 3.0.5, the Not Allowed message is missing from the Cardholder Status box and there are
two Lost statuses.
5. In version 3.0.5, with old protocol, new doors do not show up in the access levels screen.
6. Logging on with the System Master passwords now allows viewing other operator’s passwords.
7. The capability of pulling up a different set of 20 templates by operator at the same workstation has
been added.
MultiRAMM
8. If had a dependency from one RAMM sensor to another RAMM output, the second RAMM would try
to poll the panel referenced in the sensor.
9. Duplicate elevator schedules were downloaded for elevators resulting in the RAMM reaching capacity
too soon.
10. The R1-R4 messages (panel resets) now increment the alarm count rather than create a new alarm.
11. MultiRAMM now polls RAMMs not on same port as the one being initialized.
12. Only cardholders with access allowed at a RAMM are downloaded, along with their access levels. As a
result, the 254 Access Level limit per system is now 254 per RAMM.
13. In version 3.0.5, the door type was being overwritten by lock and unlock messages. This could cause
Time & Attendance mode to be turned on or doors to be put into external verify mode.
14. If Trace mode was turned off for a card, the RAMM did not get correctly updated until a full initialize
was run.
Multidrop
15. If using dependencies, a dump of the dependencies to the system log occurred on many events thus
filling the system log.
16. The R1-R4 messages (panel resets) now increment the alarm count rather than create a new alarm.
RAMM version 7003030G
17. On previous versions, Access Levels with scheduled access only worked correctly if all its schedules
were the same. A single floor with a 24-hour schedule would cause all floors to be 24 hours.
18. "SQ Full!Cmnd-1008 Tossed" messages were created if the number of elevator schedules exceeded
about 400. This could result in some access levels initially not being allowed access until their
schedule rolled over.
19. Address 16 now works
20. Door status (command 26) now returns the door unlock times.
21. The limit of 256 tasks per schedule has been removed.
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

General
1. Added support for SQL Server 7 and 2000.
2. SQL Server desktop version 7 included with Installation.
3. Added optional 128-bit encryption between all modules.
4. Added Cleanup utility to delete unused pictures, signatures and images and bulk delete cardholders.
5. Added DataSync utility to simplify converting and importing databases
CCTV
6. Added support for Betatech switcher.
7. Added support for Vicon switcher.
8. Password protection added.
9. Added support for parity and variable stop bits.
10. Fixed alarm processing pausing when a new Desktop logs in.
Desktop
11. Transaction window events color-coded to show priority.
12. Added multiple Calendar capability
13. Added support for localized badging, template and report subdirectories.
14. Added frame option for pictures and images.
15. Optimized badge edit and printing routines to speed up network access.
16. Added support for using the same badge design with different printers at different workstations.
17. Added support for picture directory tree to speed up network access of pictures.
18. Added Visitors template.
19. Added ‘Lost Badge’ status.
20. Implemented auto-add for drop down lists in a template.
21. Added ‘Show disabled’ selection to sensor control window.
22. Added warning if transaction table exceeds 100,000 events.
23. Added Browse button for Database archive location.
24. Desktop is now active during archiving.
25. Added support in Database Manager for conditional execution using IF and ELSE.
26. Added support in Database Manager for variables.
27. Added Copy button for Dependencies.
28. Multidrop, MultiRAMM and RAMM settings are now configured in the Desktop.
29. Department is now transmitted on the Desktop’s serial port as part of the transaction.
30. Added feature to create new database fields when designing templates or badges.
31. Add capability of viewing all Multidrop and MultiRAMM transactions, including disabled ones.
32. Added page view in badging.
33. Added persistence to character set in badge design allowing use of non-standard character sets.
34. Added option to disable Select button in Cardholder templates.
35. Added option to hide Archive box when deleting a cardholder.
36. Implemented directory tree based on date to store pictures to speed up access.
37. Passwords in Operator screen now hidden.
38. Implemented missing ‘Print To Batch’ badge function.
39. Fixed error when adding an alarm zone containing an apostrophe.
40. Fixed blowup problem if more than one image on a template,
41. Fixed cardholder picture from the previous selection displaying if new record doesn’t have one.
42. Fixed sensor status not displaying correctly in sensor control window if disabled while being
displayed.
43. Fixed Copy button in Imports not enabling for a read-only file.
44. Fixed ‘Change Computer Name’, ‘Change Multidrop number’ and ‘Change to RAMM’ routines not
updating Alarm Zone Outputs.
45. Fixed Inverted sensors not displaying in the Control & Sensors screen
46. Improved update response in Alarm Zone control window if many zones.
47. Fixed Access Level changes not updating RAMMs when Cardholder windows closed.
48. Archiving modified to not error on apostrophes (e.g. O’Neil)
49. Fixed clock stopping after a database backup
50. Deleting an alarm zone now removes sensors from that zone.
51. Fixed Multi-line input fields in templates.
52. Fixed next badge number incrementing if a New record was cancelled.
Multidrop
53. Configuration moved to the Desktop.
54. Now shows a blue line for dial-up panels
55. Sped up initialization when using levels with less than 5 cardholders.
56. Added password protection to Command and Initialize screens.
57. Commands are now removed if a dialup panel does not answer after 5 tries to prevent continuous
dialout attempts.
58. The sensor and door state are updated in the database when started.
59. Added department field for valid badge transactions.
60. Fixed problem with downloaded tasks on holidays if using BLP-200 00-070 or earlier
61. Fixed problem with dependencies still working for disabled sensors.
62. Fixed scheduled arming/disarming not working
63. Fixed Door Group dependencies not working
64. Sped up initialization when using Old Protocol.
65. Fixed Priority Units not polling faster.
66. Fixed elevator giving Wrong Shift for a Not Allowed badge.
MultiRAMM
67. Configuration moved to the Desktop.
68. The sensor and door state is updated in the database when started.
69. Added option for the panel check to send other commands such as command 17, Get Sensor Status.
70. Improved initialization reliability under adverse communication conditions.
71. Added modem re-initialization in case modem turned off.
72. Added password protection to Command and Initialize screens.
73. Added separate Calendar capability for each RAMM
74. The sensor and door state are updated in the database when started.
75. Added Learn mode for badges not known at the RAMM.
76. Added option to not unlock a door on Learn.
77. Fixed adding or deleting an access level causing Wrong Shift in elevators until re-initialized.
Reporter
78. Added capability of sending reports by email.
79. Added capability of exporting a report to a html (web format) page.
80. Added support for localized report directory.
81. Added support for multiple ANDs and ORs in the report query.
82. Added timer to provide automatic, periodic updating of a report.
83. Added support for UNION queries with a single prompt.
84. Added report to find duplicate badge and IDNumber fields.
85. Added option to only display recent events in the System Log.
86. Added User and Password fields for reports on other databases.
87. Several new reports added.
88. Fixed ampersands not displaying correctly in the header or footer.
89. Fixed Reporter blowing up if more than eight prompts.
RAMM Enhancements
90. Added option to ignore elevator site.
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Desktop
1. In Control & Outputs, added the capability of specifying the output energize time for HVAC control.
Added HVAC report.*
Multidrop
2. Stand-alone operation: In stand-alone operation, when Dynamic Data Exchange (DDE) must be used
for communication between the Desktop and Multidrop, Multidrop could create a General Protection
Fault (GPF) when the Desktop sent a command. The problem does not occur if Windows Sockets are
used.*
3. Dependencies: If multiple dependencies from an input and the first armed an alarm zone, subsequent
dependencies could be missed.*
4. Initialization speed with old protocol has been increased.*
MultiRAMM
5. Dialup RAMM: Commands were not sent correctly on the second and subsequent dial outs.*
6. Backup: MultiRAMM did not stop polling or sending commands during a backup operation.*
7. Initialization: Panels may not have all cardholders validated correctly on a small database (<500
cardholders) on a fast computer with multiple RAMMs. This problem will only occur when an
incremental database update is triggered by changing cardholders or access levels.*
8. Polling speed now shows total speed rather than average speed.*
9. Added capability of individually disabling communication with a RAMM.*
10. Added capability of individually enabling debug at a RAMM.*
11. Fixed potential timestamp error during initialization.*
12. Improved performance if some RAMMs down.*
13. Time & Attendance logging implemented.*
14. Added capability of selectively updating cardholders, levels and configuration when changes made.*
RAMM
15. Fixed problem with all transactions becoming disabled due to priorities being lost.*
16. Learn mode no longer sends forgive command unless antipassback mode.*
17. Database dump now gives a count of the messages.*
18. Card count correct if over 65535.*
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Desktop Enhancements
1. Added dealer phone number to About screen. Will prompt when first started up after upgrade.
2. The Control tabs for Sequences, Zones and Cameras are not shown if none installed.
3. The CCTV control buttons for a device are not shown unless that device is installed.
4. Combined the database maintenance functions and simplified them to create an archive database.
5. Added scheduled log archiving.
Multidrop Enhancements
6. Added dependencies between Multidrop panels and RAMM panels and vice versa.
7. Added message to indicate initialization complete.
Reporter Enhancements
8. Added reports for archived transaction logs.
9. Added title and report conditions to top of report.
RAMM Enhancements
10. Added relinking in case of intermittent networks.
11. Added dependencies between Multidrop panels and RAMM panels and vice versa.
12. Added direct commands to a RAMM from the Desktop.
13. Simplified the RAMM TCP/IP address configuration.
14. Added RAMM status command to MultiRAMM menu.
CCTV Enhancements
15. Added edit function in the CCTV Distributor for CCTV command strings.
16. Added more on-line help.
17. Added support for controlling devices from more than one computer.
Desktop
18. Acknowledged alarms from another Desktop created a red dot in the transaction window.
19. The Change Computer Name SQL would not change the name of the Multidrops.
20. The date was not fitting in the status line if 4 digit year.
21. The alarm list showed garbage characters if empty.
22. The badge Copy function was not enabling the Save button until a change was made.
23. A serial port could be assigned to both a communication module and a CCTV device.
24. If an output schedule was added to the output associated with an elevator reader, the reader could
revert to being a door.
25. The days in a month could be incorrect in Scheduled Reminders, Reports and SQLs after changing
from a weekly schedule.
26. Multiple page templates did not return to the same page.
27. Upper case masks in a template did not allow a space.
28. Fixed potential Disk Space Remaining error if disk greater than 2 gbytes.
29. The location of the batch printing file BATCH.$$$ depended on the starting directory.
30. Command 30 for old protocol was incorrect in Create Commands table (Old Protocol)
31. Picture directory in badge design could not be used or pictures were not saved.
32. Badge design could blow up if a field query was too long.
33. Could not capture signatures on a read-only badge design.
34. When using other than a 300 dpi printers, the badge was scaled wrong.
35. The database password was visible and readable in the database configuration screen.
Multidrop
36. Fixed date not fitting in the status line if 4 digit year
37. A direct command would not dial out if commands stuck in the RemCmnd table for other panels.
38. Unlock door command when multiple dialup panels always dialed the first one.
39. Multidrop with BLP-190s of 98-056 or later switched to enhanced panel, causing No Responses.
40. Commands 31,42,45,52 & 62 got sent to BLP-60s ( old Protocol) resulting in 'No Response' messages.
Reporter
41. Fields longer than 100 characters were truncated in printed report.
42. Could not export to a database requiring a password.
RAMM
43. MultiRAMM did not relink to a Network RAMM if network connection lost for over 5 seconds.
44. Dependencies from the wrong panels could be downloaded to the RAMM.

Release Notes 250-441

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Release Notes 250-441

Uploaded by

Copyright:

Available Formats

NOTE: This document contains a list of features and fixes for each major release of the software.

Readme.rtf This document

For details on how to register this software, search on Registration

AXxess Upgrade Considerations

Opto 22 integration is no longer supported by the AXxess software.

New features and fixes in version 4.4.1

Feature changes in 4.4.1

New known issues found in 4.4.1

Communication modules (MultiDrop, MultiRAMM, MultiPort)

Current known issues found prior to 4.4.1

Communication modules (MultiDrop, MultiRAMM, MultiPort)

eRAM & netEDGE

New features and fixes in version 4.4.0

eRAM Setup Utility

Feature changes in 4.4.0

New known issues found in 4.4.0

Communication modules (MultiDrop, MultiRAMM, MultiPort)

eRAM & eRAM-Edge

Current known issues found prior to 4.4.0

Communication modules (MultiDrop, MultiRAMM, MultiPort)

eRAM Setup Utility

Current known issues found prior to 4.3.6

Communication modules (MultiDrop, MultiRAMM, MultiPort)

New features and fixes in version 4.3.5

New features and fixes in version 4.3.4

New features and fixes in version 4.3.2

New features and fixes in version 4.3.1

View Point Monitor libraries*

NOTE: The ViewPoint must be licensed separately.

New features and fixes in version 4.2

New features and fixes in version 4.1

New features and fixes in version 4.0.4

New features and fixes in version 4.0.3

New features and fixes in version 4.0.2

New features and fixes in version 4.0.1

New features and fixes in version 3.0.7

New features and fixes in version 3.0.6

New features and fixes in version 3.0.5

You might also like