You are on page 1of 4

Release notes for version 5.2.

1
WARNINGS

1. DO NOT CONTINUE if this version of software has not been legitimately purchased from the
factory. 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. When upgrading from a previous version, be sure to read the Features removed from this release and
Upgrade Considerations below. This version may not be compatible with the existing system
configuration.
3. For details on how to register this software, search on Registration in the on-line help after
installation.
4. If multiple workstations will be required, refer to Network Installation before proceeding.

New features in this release


1. Added ability to add eMAX-MR200 panels to eMAX-EP1501 area controllers in GUI.

1. Added ability to split panels between the two RS-485 SIO ports on the eMAX-EP2500.
2. Fixed issue that limited the number of panels to 100 in GUI.
3. Fixed issue where Operators could not be given privileges to edit reports.
4. Added "Sensor open" and "Sensor closed" messages to eMAX-EP hardware.
5. Fixed issues where dependencies to Arm and Disarm alarm zones on eMAX-EP hardware did not
work as expected.
6. Fixed issue where eMAX sensors could not have both Supervision and Invert set at the same time.
7. Fixed issue where Supervised sensors may report with incorrect point name.
8. Fixed issue with Supervised REX sensors not reporting a Fault condition.
9. Fixed issue where Global antipassback could cause MultiPort to crash when using eMAX-EP
hardware.
10. Fixed issue where Reporter would crash when using the Send to... option.
11. Changed upgrade scripts to correct existing panel types and alarm zone addresses.
12. Added offline level settings for Elevator control with eMAX-EP and eMAX-MR hardware to
provide some failsafe mode operation.
13. Added override level settings for Elevator control with eMAX-EP and eMAX-MR hardware to
provide scheduled free access operation.

Back to top

Features removed from this release


1. Due to changes in the database, the Notifications integrator library has been removed until further
notice.
2. The IQinVision integrator library is not currently available.

Back to top
Upgrade considerations
1. Before upgrading from a version prior to 5.0, see application note AN-107 for upgrade
instructions.
The following information is provided to help prepare for the upgrade instructions, and should
not be used in place of AN-107.
2. Be sure that all applications and services have been stopped and closed before attempting the
upgrade.
3. Back up the database.
4. Back up any files in the Data Directory on the server that are unique and important to the site.
5. The database will need to be re-registered for the site after performing any upgrade.
6. After installation of the new version, any customized files such as templates or reports will need to
be transferred to the database before they will be available for use. The Resource Manager
application has been added to allow data files to be imported into the database. To use the Resource
Manager, in the Desktop go to Tools and Resource Manager. When the Resource manager opens,
click on Help for more information.
7. After all installation is complete and verified, the old Server is no longer required and may be
optionally uninstalled using the Windows' Add or Remove Programs application manager. The
obsolete files in the Data Directory are no longer required, and may also be deleted or archived as
desired.
8. CAUTION: When the upgraded system is started for the first time, the firmware in the eRAM and
netEDGE area controllers must be upgraded to the latest version included with this release BEFORE
making any configuration changes to the system. Failure to do this may cause the area controllers to
malfunction until updated.
9. This version of the software is designed to use firmware version 07-205A or later in the BarLock
panels when connected to eRAM area controllers. See Known Issues when using older versions.
10. In previous versions of the software, an item not assigned to any partition was available to all
partitions. This is no longer true and an item must be assigned to the partition to be available to a
partitioned operator.
11. This version includes updated firmware for all EP controllers. Be sure to update all EP hardware in
the field using the MultiPort Manager command “Download EP firmware”.

Back to top

Network Installation
If multiple workstations will be installed, proceed as follows:

1. When installing the first workstation from the CD, usually on the SQL Server machine, ensure that
the Network Install box is checked. This will install the necessary files to allow additional
workstations to be installed over the network.
2. The network installation package will prompt for a folder location on the local workstation. When
upgrading on the existing Server from a previous version, the location will default to the original
Data Directory since this folder will already be shared on the Network.
3. After installation is complete, a password will be provided. This password will be unique to each
installation, and must be used when installing the additional workstations.
4. After installation is complete, the network file folder will need to be shared on the network if not
already shared.
5. If the network share will only be used when installing additional workstations, the share can be
created with read-only privileges. However, if this same folder will be used for saving files from
different workstations such as exports and archives, then the users on those workstations will need
both read and write privileges on the share folder. Normally read and write privileges would be
selected, however if there are concerns regarding network security, it is possible to share it with
read-only privileges, and even remove the share after all the workstations are installed.
6. To share the folder, right click on it in Windows Explorer and select Share... or Sharing and
Security.... The procedure will differ depending on the operating system so refer to the windows
help, if necessary.
7. To verify that the folder is shared, click on the Windows' Start button and select Run then type
\\WORKSTATION where WORKSTATION is the name of the workstation and click on OK. This
will display the list of shared folders.
8. Due to changes in the operating system and third party firewalls, it may be necessary to configure
the firewall to allow remote connections when running multiple workstations. See application note
AN-009 for information regarding the network ports used by applications and hardware.
9. If SQL Server 2005 EXPRESS has been installed, firewall exceptions must be added and it must be
opened to the network before it will be visible to other computers. See
http://support.microsoft.com/kb/914277 for more information.
10. To install the workstation software on another computer, at the computer click on the Windows'
Start button and select Run. Type \\WORKSTATION where WORKSTATION is the name of the
main workstation above and click on OK. Locate the shared folder and open it and double click on
Setup. Enter the network installation password, and then install the necessary components the same
as the main workstation.

Back to top

Known Issues in this release


1. When a panel is set for 1 door mode (slaved reader) and Show in Control List is checked for both
doors, the manual control screen will show entries for both doors. If the slaved door is selected and
unlocked, relay 2 on the panel will unlock not the door relay as expected.
2. If antipassback is being used and a full initialization is performed on an eRAM or netEDGE area
controller, all cards will be forgiven.
3. If using eRAM and BarLock firmware prior to 07-205A, failsafe operation may unlock the wrong
door and keypad operation may be erratic if both keypads are used at the same time.
4. Using eRAM and BarLock firmware prior to 07-205 is not recommended as there are a number of
unsupported functions. However, 07-025 is fine with RAMMs.
5. Card access failsafe operation does not function correctly on badges that do not have a definable site
code such as MiFare.
6. Very large reports require a lot of memory and disk space and may cause a workstation to hang or
crash. If this occurs, limit the report size or increase the memory and drive space on the workstation.
7. The documentation for many of the Multiport libraries refers to configuration in the desktop.
Configuration is now done in MultiPort Manager.
8. When Inter-module encryption if first enabled, it may be required to restart MultiPort and re-link
MultiPort Manager for encryption to become fully enabled.
9. When the MultiPort service is started or has been reloaded, the status display in MultiPort Manager
may not display correctly. In these cases closing and reopening the MultiPort Manager or re-linking
to MultiPort will usually resolve the issue.
10. When adding eMAX panels, the maximum panel address allowed is one less than the Panel Count
value in the configuration of the area controller. For example, the default Panel Count for eMAX-
EP1502 and eMAX-EP2500 units is 20. The valid panel addresses when using the default are 0-19
for a total of 20 panels, however the Desktop will allow addresses 0-20 to be added to the area
controller.
11. Doors and Outputs may only be assigned to one door or output group.
12. When both readers of an eMAX-MR51e or eMAX-EP1501 are added to the system, the auxiliary
output on those units cannot be added to the system.
13. Cardholder names may not resolve correctly when using magnetic readers on RAMM elevators.
14. Some configuration changes to eMAX hardware may cause a momentary communication
interruption.
15. Picture display on badge activities is not supported on elevators with floor reporting enabled.
16. Pin entry on eMAX hardware will only resolve names for the primary site code.
17. eMAX hardware is limited to 256 access levels and 256 elevator levels per area controller. The list
of access levels and elevator levels is unique for each area controller.
18. The Save Picture function in Cardholder screen will report and error and the picture will not be
saved. To save a picture from the database, the Resource Manager must be used.

1. When using eMAX EP hardware with encrypted communication, there may be an increased
frequency of "Communication Lost" and Communication Back" messages from the encrypted
devices. Contact factory for more details.
2. Global antipassback may get out of sync on eRAM and netEDGE devices when areas are used by
doors on more than one MultiPort.

Back to top

You might also like