Release notes for version 6.2.1.

17215
Release date: August 3rd, 2017.

WARNINGS

1. DO NOT CONTINUE unless this version of software has been legitimately purchased. This
installation must be registered with the factory to receive a valid license otherwise it will expire in 20
days and the feature set will be limited. 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 sections below.
NOTE: The existing system may be using hardware that may not be compatible with this version of
software.
3. For details on how to register this software, search on Registration in the on-line help after installation.
4. If the site will include multiple workstations, refer to the Network Installation section.
5. SQL Server must not be installed on a domain controller. For detail regarding why, see Microsoft
knowledge base article: https://support.microsoft.com/kb/2032911

Operating Systems and SQL Server editions supported

1. Supported Windows Operating Systems:
1. Windows 7 (x86, x64)
2. Windows Server 2008 (x86, x64)
3. Windows Server 2008 R2 (x64)
4. Windows 8 (x86, x64)
5. Windows 8.1 (x86, x64)
6. Windows Server 2012 (x64)
7. Windows Server 2012 R2 (x64)
8. Windows 10 (x86, x64)
9. Windows Server 2016 (x64)
2. Supported SQL Server Database Engines:
1. SQL Server 2005: Express, Standard, Enterprise (x86, x64)
2. SQL Server 2008: Express, Standard, Enterprise (x86, x64)
3. SQL Server 2008 R2: Express, Standard, Enterprise (x86, x64)
4. SQL Server 2012: Express, Standard, Enterprise (x86, x64)
5. SQL Server 2014: Express, Standard, Enterprise (x86, x64)
6. SQL Server 2016: Express, Standard, Enterprise (x64)
3. This installation media includes SQL Server 2008 R2 Express edition (x86), and SQL Server 2016
SP1 Express edition (x64). The version that will be installed automatically will depend on the operating
system of the computer where SQL Server will be installed.
1. SQL Server 2008 R2 Express: will be the default database engine for any 32 bit operating
system as well as 64 bit editions of the following version or Windows:
Windows 7, Windows Server 2008, and Windows Server 2008 R2.
2. SQL Server 2016 SP1 Express: will be the default database engine for the following 64 bit
editions of Windows:
Windows 8, Windows 8.1, Windows 10, Windows Server 2012, and Windows Server 2016.

NOTE: the x86 version of SQL Server 2008 R2 Express will install on both x86 and x64 versions
of Windows where applicable.
NOTE: When installing SQL Server Express onto a 32 bit OS, it is important to ensure that the
OS has been updated with the current Windows patches. Failure to do so may cause the SQL
Server installation to fail.

NOTE: When upgrading the security management software on an existing PC, the SQL Server
Express editions supplied on this installation media are not required.

NOTE: If one of the supported SQL Server versions is already installed, the supplied Express
edition of SQL Server is not required. To create a new database on an existing SQL Server, the
connection information for a sys admin login on that SQL Server instance will be required during
the installation. Following the creation of the database, the sys admin login is no longer required.

NOTE: SQL Server must not be installed on a domain controller. For details, see Microsoft
knowledge base article: https://support.microsoft.com/kb/2032911

New features
1. Added MX+ web server cardholder administration support, using HTML5.
2. MX+ web server replaces older Silverlight based IMM.
3. Added support for Mercury Software House Bridge hardware.
4. Added support for Honeywell ProWatch and WinPak hardware.
5. Added support for Acuant ScanShell drivers license scanners and SDK.
6. Improved low battery annunciation for Salto Sallis hardware through eMAX controllers.
Required updated versions of Salto Sallis firmwares and eMAX firmware included.
7. Improved low battery annunciation for Salto SVN hardware.
8. Resolved issue with Scheduled Reports integrator and predefined reports.
9. Improved Scheduled Reports to include options for SSL encrypted connections for sending email.
10. Improved Import/Export Integrator to allow easier import of cardholder levels.
11. Added support for HotKeys integrator.
12. Added integrator for SeeTec Cayuga video management system.
13. Added integrator for Hanwha Techwin video management system.
14. Added integrator for 3XLogic Vigil video management system.
15. Added integrator for ACTI SDK 2200 video management system.
16. Added support for PCSC IQ Elevator panels.
17. Improved PCSC cardholder processing when downloading large numbers of cardholders.
18. Improved support for counters with PCSC hardware.
19. Miscellaneous bug fixes.

Back to top

Features removed from this release

1. There are no features that have been removed in this release.

Back to top
Upgrade considerations
This version of software is designed to allow direct upgrades from version 4.4.1 or later. If the
currently installed version is prior to version 4.4.1, or the current system is using MultiDrop,
RAMM or MultiRAMM, please contact the factory before starting an upgrade on that system.

When this version of software will be installed onto a system with versions prior to 5, be sure to
uninstall the previous version completely before starting the installation process.

When installing the Workstation for this version over an existing version 6.0.2 or earlier
Workstation that also includes ViewPoint, be sure to manually uninstall ViewPoint before
installing the new version.

General upgrade considerations.

1. Be sure to read and follow the upgrade instructions in application note AN-140 before and during the
upgrade process. It is preferred that the upgrade be performed onto a new server rather than performing
an upgrade on top of an existing server. However an upgrade on top of an existing server is a viable
option when there are no other options.
2. Be sure that all programs (Desktops, Reporters, Communication Modules, etc.) on all workstations have
been stopped and closed before attempting the upgrade.
3. Back up the database and store the backup in a safe location.
4. After the system has been upgraded, the site will need to be registered with the factory before any
significant changes to the database may be made.
5. This version of the software includes updated firmware packages for the eMAX area controllers. All
eMAX area controllers that will communicate with this software should be updated with the included
firmware. Failure to do so may result in unanticipated results.
6. This version of the software includes an updated firewall rules package for the eRAM and netEDGE
area controllers. All eRAM and netEDGE area controllers that will communicate with this software
should be updated with the included firewall rules.
7. After the software upgrade is completed, the existing hardware will require an initialization. This step is
required to ensure proper operation, and failure to initialize the hardware will likely result in undesired
operations.
8. Due to customizable nature of the SQL Server database on site, it is possible for the Database upgrade
process to report errors. This does not normally happen, however, should it occur during an upgrade,
please contact Technical Support prior to continuing. Most often these errors can be resolved quickly
and easily, and usually do not prevent the upgrade from being completed successfully.

4.4.1 to version 6.x upgrade considerations.

1. Back up any files in the Data Directory on the server that are unique to this site.
2. After upgrading the workstation that was previously the AXxess Server, custom files that have been
added in the server Data Directory will need to be imported into the database using the Resource
Manager. This includes reports, templates, badge designs, cardholder pictures, etc. To use the Resource
Manager, in the Desktop go to Tools and Resource Manager. When the Resource manager opens, click
on Help.
3. CAUTION: When the upgraded system is started for the first time, any eRAM and netEDGE area
controllers that are not already upgraded to the latest firmware version will return an alarm indicating
that the firmware must be updated. The firmware must be upgraded BEFORE making any configuration
changes to the system. Failure to do this may cause the area controllers to malfunction. Use the Area
Controller Configuration Utility to perform this upgrade.
4. 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.
5. 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.
6. In previous versions of the software, the [BadgeDate] and [BadgeCount] fields in the cardholder table
were used to track printing of badges. Since the newer versions of software allow for multiple badges
per cardholder, these fields have been moved to the [LastPrintDate] and [PrintCount] fields in the
[Badges] table so that they more accurately track the printing of individual badges.
7. For Salto SVN support, this version of software requires Salto ProAccess Space version 2.0.8.4 or
later. Using earlier versions of Salto ProAccess Space or Salto ProAccess RW will produce undesirable
results and will not be supported by Maxxess.

Back to top

Network Installation
If the system includes multiple workstations, proceed as follows:

1. When the first workstation is installed from the installation media, usually on the SQL Server machine,
ensure that the Network Install box is checked. This will install the necessary files, and provide the
required network installation password to allow additional workstations to be installed over the network
without needing the installation media.
2. Prior to the network files being installed, the system will prompt for the folder location where the
network files should be installed on the local workstation. If the system is being upgraded from a
previous version and the server has not changed, the location will default to the original Data Directory.
3. After installation is complete, the network install password will be presented along with the count of
installed features. The password will be required when installing the additional workstations. Use the
following space to log the password and computer name for the network installation server for the site.

Network install password: _________________________________________________________

Network install Computer Name: _______________________________________________________

4. After installation is complete, the installation folder must be shared on the network with permissions that
will allow the additional workstations to connect and run the setup.
5. If the shared folder will only be used for the installation of additional workstations, then the permissions
only need to allow read-only privileges. However, if the shared folder will also be used for saving files
from different workstations such as exports and archives, then the permissions will need to allow both
read and write privileges. Normally read and write privileges will be selected, however if network
security is a higher concern, the shared folder may be set for read-only privileges or it may even be
unshared after all the workstations have been 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. Please refer to the windows
help, if necessary.

Network installation shared path: _______________________________________________________

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. 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.
Install the necessary components the same as the main workstation.

Back to top

Basic operation, things to know

1. The MX+ web server requires .NET framework 4.6 to operate. Please ensure that .NET framework 4.6
has been installed on the server that will be hosting the MX+ web server. Note this version of .NET
framework is only a requirement for the server, and not for the clients.
2. A few MultiPort and ViewPoint integrators, as well as a few Optional modules require .NET framework
version 2.0 or 3.5 to operate. Please ensure that the .NET framework 3.5 feature (which includes .NET
2.0) has been installed on the workstation before installing optional components. The feature may be
added through the Control Panel, Programs and features option on Windows 7 and Windows 8, or in the
Server Manager on Windows Server 2008 and Windows Server 2012 and Windows Server 2016.
3. When a door sensor or REX input is release from their normal duties for general purpose use, the
sensors are automatically deleted from the database. This is done to avoid invalid messages from
disconnected inputs. If the input will actually be used, the sensor will need to be added back into the
database before it will report.
4. When auxiliary outputs will need to be momentarily unlocked manually, the Outputs/Energize scale
factor: setting will need to be modified on each workstation from the default 3600 to 1. The default scale
factor equals 1 hour, so the time setting in the manual control window will be multiplied by one hour. A
scale factor of 1 equals one second, and a scale factor of 60 equals one minute. Currently the minimum
allowed momentary unlock time is 7 seconds.
NOTE: This feature is currently non-operational, see Known Issues in this release section for more
information.
5. Schedule special days have changed. Different hardware offers different operation of the holiday
types/special schedules. The look of the Calendar and Schedules windows will change depending on the
hardware that is configured in the database. Care must be taken when configuring schedules within a
system with mixed hardware platforms.
1. eRAM/netEDGE area controllers allow 3 holiday types/special schedules. Only one holiday
type is active on any given day on eRAM/netEDGE hardware.
2. eMAX area controllers allow up to 8 holiday types/special schedules. All 8 holiday types may be
active on any given day on eMAX hardware.
3. Salto SVN hardware allows up to 3 holiday types/special schedules. All 3 holiday types may be
active on any given day in the Salto SVN
6. When using Windows Authentication for SQL Server, the MultiPort service must be configured to
login using a valid Windows account with access to the SQL Server. NOTE: this is not the default
method used to authenticate when using the supplied SQL Server engine.
7. When using Alarm Routing, alarm events may be seen at all workstations before the Alarm Routing
Delay has passed if a non-routed alarm comes in during the delay period.
8. When using Door or Output groups that span modules, commands to unlock or lock the group from
the Desktop Plan window will generate as many commands as there are area controllers for each area
controller. Causing many duplicate commands to be sent.
9. After the system has been registered for the first time, be sure to log out and log back in before adding
hardware to the Plan window.
10. When adding panels to the system, the Add Points check box may be used to add basic access control
points, it will not add points for an Elevator. Be sure to uncheck the box when adding a panel for
Elevator control.
11. Adjusting the time zone or DST setting of the PC while the Desktop is open may cause a "This
registration is not valid for this site or the database has been restored or modified!" error message when
the Desktop is closed. This is expected behavior, and will only be seen the first time the Desktop is
closed following a time zone or DST change.
12. Area Controllers cannot be added to the system through the Plan Design window, but must be added
through the "Configuration" window before panels may be added to the controller.
13. When performing an upgrade on a system that is using badge designs that is a version 5 or earlier, in
order to convert the existing badge designs to work with in this version, the selected badge design
cannot be read only.
14. Access Level names cannot begin with a 1-9 character. Zero is a valid first digit for the name of an
access level. For example "12345 Access Level" is not valid, however "012345 Access Level" is a valid
access level name.
15. Systems with mixed hardware platforms (eRAM-BLP, eMAX, PCSC, and Salto SVN) will have items
in Configuration screens that do not pertain to all hardware platforms. The following is a partial list.
1. PCSC hardware requires a "secondary expiration" field for badges that will show in the Badge
edit screen. The field is not supported on eMAX or SVN hardware.
2. SVN hardware requires a "new key can be cancelled through blacklist" checkbox in the Badge
edit screen. eMAX and SVN hardware do not support this function.
3. The Access Levels options for "Activate datetime", "Deactivate datetime", "Escort", and "Escort
required" are only supported on eMAX hardware. PCSC and SVN hardware do not support
these functions.
4. With SVN hardware, there will be 256 Calendars added to the system named "Calendar000"
through "Calendar255". These calendars are only applicable to SVN hardware.
5. The Schedules configuration option for "One Time Events" is only applicable to eRAM-
BLP/netEDGE and eMAX hardware. The function is not downloaded to eMAX hardware and
requires MutliPort connectivity for schedule changes.
6. The Bulk Add function is not applicable for SVN hardware.
16. When changing the antipassback mode of a system (i.e. none, soft, or hard), all existing cardholders
must be forgiven through the "Manual Control" window to prevent antipassback violations.
17. In template design, the badge type "CSN" is not fully implemented and should not be used at this time.
18. When using Morpho readers with this version of software, the "Morpho_Manager_6.1.2.15092.iso"
must be used to install the Morpho Manager application. Other versions of Morpho Manager may not
have been tested with this version software, and may cause undesirable results if used. The supported
Morpho reader firmwares are included in the Morpho Bio Toolbox application on this ISO image.
19. When using the Remote Point PDA with this version software, the "Remote_Point_6.1.2.15092.iso"
must be used to install the Remote Point server software. Other versions of Remote Point may not have
been tested with this version software, and may cause undesirable results if used.
20. Dependencies that have an email action will require an email account to send through. The email
account SMTP settings must be configured in the Desktop Settings for the system before emails will be
sent. The SMTP Server, account name, account password, SMTP port number must all be known and
entered in the correct "email" section for "_All Workstations".
21. When enabling or disabling case sensitive user names in operator options, it is important to note that all
operator records must be edited and their user names must be tickled so that the record can be saved
with the new rules in place. This must be completed before logging out of the Desktop application.
Failure to do so will result in failed login attempts and will require the operator to use the lost password
procedure.
22. The maximum allowed Expiration date for an Access Level is currently "2030-12-31 23:59:59". Any
date/time greater than this value will result in cardholders not being granted access using those access
levels.

Back to top
Basic operation, things to know when using eMAX and
eRAM/netEDGE hardware
1. When adding an EP1501, the Add Points option will only add door 1 to the EP1501 internal panel. If
the internal panel will be used as an in-out reader, door 2 must be manually added to the system, and
configured as the paired reader in door 1.
2. The netEDGE configuration tab will not be visible unless the system is registered for netEDGE doors
and at least one eRAM or netEDGE device is in the database.
3. When using Floor reporting with eMAX elevators, accesses that occur while the "Offline" or
"Override" schedules are active will be reported as accesses from the elevator reader only, and will not
send the floor selected.
4. Before changing the Door Lock Output of an eMAX door that is configured with an Alarm Shunt
Output, be sure to disable the Alarm Shunt Output and save the door before setting the new door lock
output. Then save the door record again before re-enabling the alarm shunt output.
5. If PIN will be used on one or more eMAX doors, and one or more cardholders will not need a PIN,
"NONE" should be entered as the PIN for each cardholder which does not need a PIN.
6. Firmware updates to serially connected EP area controllers will take longer to complete than network
connected EP area controllers.
7. eMAX-MR51e devices may be saved without an IP Address or MAC address. The units will not
function until these settings are correctly entered.
8. Changes to the IP and MAC addresses of the eMAX-MR51e require a reset and initialize of the
eMAX-EP area controller it is assigned to.
9. After the system has been registered for the first time, be sure to log out and log back in before adding
hardware to the Plan window.
10. With Salto SVN doors, the "Audit on Keys" configuration setting is only valid for offline locks. While
the setting exists for Control Units and Wireless locks, the feature does not apply to them.
11. When adding panels to the system, the Add Points check box may be used to add basic access control
points, it will not add points for an Elevator. Be sure to uncheck the box when adding a panel for
Elevator control.
12. Adjusting the time zone or DST setting of the PC while the Desktop is open may cause a "This
registration is not valid for this site or the database has been restored or modified!" error message when
the Desktop is closed. This is expected behavior, and will only be seen the first time the Desktop is
closed following a time zone or DST change.
13. When using Panel Encryption for eMAX panels, the following list is the minimum firmware version
required for the MR panels. Versions later than those listed below will support panel encryption.
eMAX-MR50 - revision 1.40.3
eMAX-MR52 - revision 1.40.1
eMAX-MR51e - revision 1.2.6
eMAX-MR16IN - revision 1.31.1
eMAX-MR16OUT - revision 1.31.1
eMAX-MR200 - encryption not supported
14. When using the Aperio AH30 Mecury Hub 8, the Aperio locks and Aperio Hub 8 firmwares must be
version 3.0 or greater for manual unlock/lock to function. Additionally the eMAX-EP firmware must be
version 1.21.2 or later.

Back to top
Basic operation, things to know when using Salto SVN hardware
1. There must only be one Salto SVN area controller defined in the database. If multiple Salto SVN area
controllers are defined in the database, some features will use the configured values for the first Salto
SVN area controller added to the system. NOTE: Currently the system will not prevent the user
from adding multiple Salto SVN area controllers to the system.
2. For Salto SVN support, this version of software requires Salto ProAccess Space version 2.0.8.4 or
later. Using earlier versions of Salto ProAccess Space or Salto ProAccess RW will produce undesirable
results.
3. The Salto SVN hardware line uses an additional communication service. The Salto RW service must be
running as well as the MultiPort service in order for the MultiPort to communicate with the Salto SVN
hardware.
4. Before Salto SVN hardware may be added to the system, the Salto SVN Interface optional module
must be installed, and MultiPort must be restarted. Until this is complete, the hardware will not be
visible in the Desktop for selection.
5. When a door sensor or REX input is release from their normal duties for general purpose use, the
sensors are automatically deleted from the database. This is done to avoid invalid messages from
disconnected inputs. If the input will actually be used, the sensor will need to be added back into the
database before it will report.
6. Salto Sallis and Salto SVN GEO cylinder locks may only be paired with one Salto site code or
database. Once a Salto GEO cylinder has been paired with a database using the Portable Programming
Device, it cannot be moved to another Salto system with another site code. This functionality is by
design and unique to the Salto GEO cylinder locks.
7. When a Salto SVN user is deleted, their key becomes blacklisted in the Salto hardware network. If the
user reads their badge after they have been deleted, the Salto hardware will return a "Voided card"
event with the raw key number for the details. This will only happen on the first read, any subsequent
read attempts will return an empty details for the "Voided card" event.
8. The calendar for Salto SVN doors is not currently configurable. All doors will use "Calendar000" at this
time. This is a limitation of the Salto SVN protocol. Cardholders may be configured to use any of the
available 256 calendars.
9. The address for the Salto SVN interface must be between 1 and 999. Values outside that range will
cause unexpected results.
10. With Salto SVN, the "Two-Person rule" open mode is not operational with SVN GEO locks.
11. Salto SVN locks do not support Scheduled Door Group unlock. Manual and Dependency Door Group
unlocks are supported by Salto SVN online and wireless online locks.
12. Offline Salto SVN locks may only be unlocked using the PPD or by schedule.
13. Changes to the configuration of the Salto SVN integration will require a reload of the MultiPort service
before the changes will take effect.
14. Currently the Salto SVN "Description" fields for "Access Levels", "Schedules", and "Calendars" do
not exist. The description fields do exist for "Doors", "Door Groups", and "Automatic Changes".
15. When adding a new Door Group the "Description" field is not sent to the Salto SVN database. To send
the description to the Salto SVN database after the record has been added, the description must be
entered, and the list of door points must be altered.
16. With Salto SVN the total number of Doors, Door Groups/Zones, and Access Levels that can be assigned
to each cardholder is 96.
17. Changes to the Cardholder Enable for a Salto SVN cardholder will require the key to be updated
before the change will take effect.
18. With Salto SVN doors, the "Audit on Keys" configuration setting is only valid for offline locks. While
the setting exists for Control Units and Wireless locks, the feature does not apply to them.
19. The Schedule day named "Special 3" is "Holiday 2" for Salto SVN hardware in a system with eMAX
hardware.
20. Schedules on Salto SVN hardware only Start/End on the even 10 minute interval. I.e. schedules that are
set to change state at 15 minutes after the hour will actually change state at 10 minutes after the hour,
and schedule that are set to change state at 45 minutes after the hour will actually change stat at 40
minutes after the hour.

Back to top

Basic operation, things to know when using PCSC hardware.

1. After adding an FTC, IQ, or SIM area controller to the system, be sure to send an "Initialize Area
Controller" command through the Service Manager, and once the initialization has completed, send the
"Reset Area Controller" command to pair the unit to the database.
2. Performing a hard reset of an IQ or SIM panel that has been connected to a MultiPort requires the
following steps to ensure proper operation of the panel.
1. Use Service Manager to reload the MultiPort that the panel connects through.
2. Stop the MultiPort and Panel Proxy services, then restart the MultiPort service.
3. Initialize the panel.
3. Configuring a DDM, IQ, or SIM input for supervision mode requires the following steps to activate the
changes.
1. Configure the hardware to have the supervised resistors in place, and in the secure state.
2. Configure the sensor for supervised = Yes, and save the changes.
3. Wait for incremental door updates to be processed by MultiPort, and wait for the unit to come
back online.
4. Configure the sensor for supervised calibrate = Yes, and save the changes.
5. Wait for the indicator LEDs on the DDM, IQ, or SIM to change.
6. Cycle the input point through the alarm and secure states, and verify the indicator LED changes.
Note: The sequence of this process is a requirement of the hardware
4. Changes to the Invert setting of an input sensor on a FTC/DDM/SDM , IQ, or SIM must be made with
supervision mode disabled.
5. Configuring a FTC/DDM/SDM , IQ, or SIM input for both invert state (secure open) and supervision
mode requires the following steps to activate the changes.
1. Configure the hardware to have the supervised resistors in place, and in the desired secure state.
2. Configure the input sensor invert setting as desired.
3. Send the Restart Area Controller command to the FTC, IQ, or SIM, and wait for the unit to come
back online.
4. Verify that the input sensor is inverted as desired.
5. Configure the sensor for supervised = Yes, and save the changes.
6. Send the Restart Area Controller command to the FTC, IQ, or SIM, and wait for the unit to come
back online.
7. Configure the sensor for supervised calibrate = Yes, and save the changes.
8. Wait for the indicator LEDs on the DDM/SDM, IQ, or SIM to change.
9. Cycle the input point through the alarm and secure states, and verify the indicator LED changes.
Note: The sequence of this process is a requirement of the hardware
6. FTC/DDM/SDM, IQ, and SIM doors on the same area controller within a single access level must all
use the same schedule. Some hardware does allow different schedules per door within the same access
level, because of this, the Desktop will not prevent a user from using different schedules within the same
access level.
Note: This requirement is a function of the hardware.
7. Only the primary FTC may be initialized. Attempts to initialize any FTC that is not the primary will be
ignored.
8. Each FTC group may have up to 120 units (FTC, DDM, SDM) in it, addressed 1-120.
The address of each FTC on any one MultiPort must be unique, i.e. there cannot be two FTC groups on
one MultiPort, each with address 1 for the primary, and 2 for the secondary FTC.
The addresses for all DDM and SDM units within an FTC group must be unique, however the addresses
do not have to remain unique across FTC groups. For example, each FTC group may have a unit with
address 10, and that unit may be a DDM in each FTC group.
9. Changes to the Invert setting of the door sensor or REX inputs on a SDM do not take effect until the
FTC is restarted.
10. Changes to the Door REX logging, Door REX unlock, and Door REX unlock time settings on a SDM
do not take effect until the FTC is restarted.
11. Changes to the Door Unlock time and Door Unlock time (Extended) on a SDM do not take effect until
the FTC is restarted.
12. Changes to the Card Data format setting on a DDM do not take effect until the FTC is restarted.
13. Using the Assign exit reader setting on a DDM will cause the DDM to fail in such a manner that the on
board Reset button must be pressed to clear the unit. Currently the Assign exit reader setting must not be
used on DDMs.
14. Invalid PIN messages from FTC/DDM/SDM, IQ, and SIM doors will only be seen following 4
consecutive invalid PIN attempts.
Note: This is a function of the firmware in the FTC/DDM/SDM, IQ, and SIM hardware.
15. Invalid site messages from FTC/DDM/SDM, IQ, and SIM doors will only be seen following 5
consecutive invalid site badge read attempts.
Note: This is a function of the firmware in the FTC/DDM/SDM, IQ, and SIM hardware.
16. For FTC, IQ, and SIM units, the Status... commands in the MutliPort Manager will report the data from
the previous Status request (either automatically or manually requested). Sending the command a second
time in a short period of time will report the current information.
Note: This is a function of the hardware interface.
17. Use of the reset button on an IQ or SIM unit will restore normal operation to any doors that have been
placed in lockdown mode. Plan icons for the restored doors will still indicate that the door is locked
down until they have been manually cleared from lock down mode.
18. Currently the maximum number of schedules allowed at any FTC, IQ, or SIM unit is reduced by 1 from
the published maximum for that unit.
19. When managing schedules, the Desktop will allow the user to create schedules with more time intervals
than the FTC, IQ, or SIM units can accommodate. This is by design, as schedules are not only used in
the hardware.
20. Disabling DDM or SDM panels does not prevent messages from being received in MultiPort.
21. Changes to the Badge count setting for FTC, IQ, or SIM unit require a MultiPort reload followed by an
initialization before the new setting will take effect.
22. The "Module" selection boxes that exist on many configuration screens will show all FTC units in a
group. Items in these configuration screens must be created on the primary FTC only. All other FTC
units in the group will automatically be updated from the primary.
23. When auxiliary outputs will need to be momentarily unlocked manually, the Outputs/Energize scale
factor: setting will need to be modified on each workstation from the default 3600 to 1. The default scale
factor equals 1 hour, so the time setting in the manual control window will be multiplied by one hour. A
scale factor of 1 equals one second, and a scale factor of 60 equals one minute. Currently the minimum
allowed momentary unlock time is 7 seconds.
24. Schedules are limited to 7 intervals for IQ, and SIM units. FTC units are limited to 12 intervals.
25. All doors assigned to an access level must all use the same schedule for granting access. Only the
schedule assigned to the first door assigned will be used for that access level on the FTC, IQ, or SIM.

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, the relay on the panel normally assigned to that door will unlock not the door relay for the
paired reader as expected. To eliminate this issue, ensure that only the master door is configured with
the Show in Control List option checked.
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.
5. Card access failsafe operation does not function correctly on badges such as MiFare CSN that do not
have a definable site code.
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 Service Manager.
8. The command list in Service Manager will be blank each time the Service Manager window is opened
from the Desktop tools menu. To get the list populated, minimize the Service Manager to the system
tray, and reopen. After logging in, the command list will be populated.
9. In Service Manager, the individual "Download..." commands should only be used when technical
support directs their use. Unusual and undesired results may be seen if used in an incorrect sequence.
10. The Schedule Pinpad disable setting for doors is not functional.
11. When initializing eRAM and netEDGE area controllers, the "Initialization sequence" events are no
longer returned to the MutliPort Manager window. This is a side effect of a new initialization process
that will minimize the down time of the eRAM and netEDGE during the initialization.
12. New systems will not allow the "Resource Manager", "Service Manager", or "Reporter" applications
to open without a valid password. On a new installation, if passwords have not been enabled, those
applications cannot be opened. To allow these applications to open without passwords, the System
Master password must be set, and then removed from the system.
13. Communication back message will show in Service Manager with a disabled priority. The message
does get logged correctly in the database.
14. In order for the new "Public DHCP" setting for eMAX-MR51e hardware to work, the eMAX-EP that it
is connecting through must also be configured for DHCP.
15. The Bulk Change utility may time out when there are a large number of cardholder records in the
database.
16. The "Add Points" check box on the Panels tab cannot automate the addition of Elevator
configurations.
17. Changes to eRAM elevator configuration (adding/editing/removing floor outputs or elevator groups)
are not incrementally updated to the eRAM.
18. When using the "Bulk Change" application, with localization files for "Croatian, Dutch, Greek, Polish,
Portuguese, and Turkish" languages, the application will report "Culture is not supported." and display
in English.
19. The "Time" parameter in the Outputs tab of the Manual Control window does not currently function.
This parameter should allow the operator to adjust how long a momentary unlock of an output will last.
20. The cardholder with [Id] = 1 will not save Salto SVN door and access level assignments correctly. All
other cardholder will save correctly.
21. On a purely Salto SVN system, the Access Levels/Options settings are not available. Adding a disabled
eRAM or eMAX area controller will enable the Access Levels/Options, allowing the operator to enable
Door Groups in access levels.
22. When modifying eMAX dependencies, if the dependency changes from having triggers and procedures
to not having triggers and procedures, saving the dependency will result in a database error. Must delete
the existing dependency and add new dependency.
23. Changes to the StartDate and ExpireDate of a cardholder will not cause the badges for the cardholder
to be downloaded. Changes to the StartDate or ExpireDate for a badge will cause the badge to
download.
24. In the Personnel screens, the Selection window does not allow for filtering on fields with NULL values.
25. Deleting an eMAX-EP area controller with Elevators still configured will leave orphan data related to
the Elevator configuration. To avoid leaving orphan data, be sure to delete the Elevator configuration
prior to deleting the eMAX-EP area controller.
26. The cardholder "Archive" feature does not currently export biometric templates for the deleted
cardholder.
27. When using the Desktop serial output, if the Desktop cannot open the port, it may become
unresponsive or even crash. To prevent this, be sure the serial port is available and operational before
starting the Desktop.
28. Using the Operator function "Password on Startup" with the Badging Desktop shortcut does not
operate as expected. The user is still required to log in after the Desktop opens.
29. If an operator has a configuration window open when their scheduled access expires, the configuration
window will simply close, and they will lose any changes.
30. On eMAX hardware, scheduled access for Precision Door assignment for cardholders should not be
used with this version. There is a small possibility that one of the schedules may not work for the
precision doors, resulting in a "Denied access" message.
31. Changes to the PIN for a Salto SVN credential do not update the Key status to indicate that the key
must be updated before the new PIN will be active.
32. The System Monitor service in the Optional Modules does not support monitoring of Area Controller
hardware when running on Windows 10 operating systems. The System Monitor service should be
installed on a Windows 7, Windows 8, Windows 8.1, Windows Server 2008, Windows Server 2008 R2,
Windows Server 2012, Windows Server 2016 operating system to operate properly.

Back to top