Version 3.5.1.18

(1) The ASSA gateway is not yet Windows 8 compatible for IP locks (Wifi and POE). The software installer will not allow the ASSA gateway to be installed if the operating system is Windows 8.

Note: Doors.Net software IS NOT compatible with any Home/Basic version of Windows XP, Windows Vista, Windows 7, or Windows 8.
This is due to networking restrictions built into the Home/Basic versions of Windows operating systems.

New Features

For All Hardware Platforms:

• Added a linkage Export/Import function that allows a programmed linkage to be exported from one controller and then imported by another on the same system or on a completely different system. This feature is available via local linkage.
• Added a Apply Template/Save Template for all controllers. This feature saves the existing properties of a controller and its devices to a template file. That file can then be applied to another controller of the same type. Available only in Design mode.

Unique to Keri NXT Controllers:

• None at this time.

Unique to Keri PXL Controllers:

• Implemented the Global Unlock/Lock feature set in Doors.NET. When the corresponding input is activated, these features automatically either lock or unlock ALL of the online and functioning doors in the PXL system; it does not allow selected doors to be excluded from the lock or unlock command. Since these features are hardware controlled they are not dependent upon the PC to be activated. If controllers are offline when a Unlock/Lock command is issued they will not respond to the Unlock/Lock command until they come back online.
• The Global Unlock/Lock functionality of PXL hardware can be extended using the Situation Manager within Doors.NET software. This provides you with greater control and flexibility in how the Global Unlock/Lock features are implemented, including varying restriction levels of lock and unlock and the ability to assign/unassign specific doors. The Situation Manager requires the Primary controller always be online with the host PC.

Unique to Keri NXT Mercury Powered Controllers and Mercury Hardware:

• None at this time.

Unique to ASSA Lock Hardware:

• None at this time.

Program Improvements

For All Hardware Platforms:

• Corrected an issue where the Archive database could not connect when using Windows 8. Windows 8 uses SQL Server 2012 which has a slightly different structure for its connection information. The program now recognizes when SQL Server 2012 is active and adjusts its connection information accordingly.
• Corrected an issue where both a door strike and a door forced alarm could be assigned to the same control point (when reassigning a door strike from its default control point) resulting in unexpected operation. The program now prevents the control point from being assigned to door forced if already assigned to door strike.
• Corrected an issue that, in certain applications, would not allow a temporary unlock command to be overridden by a lock command.
• Restricted access to Design Mode to operators designated as System Administrators. You must also be in Advanced View to access Design Mode. Design Mode allows an operator to change the appearance and layout of program screens.
• If a gateway disconnects from the host PC, the status grid will set all controllers on that gateway to offline status.
• Added a "Remove All" option to Local Linkage triggers and procedures. You must be a System Administrator to perform a Remove All and you must remove triggers before you remove procedures.
• If a reader is an exit reader or does not have Door Contact enabled the Door Status grid would not display status in the Door Forced or Door Held fields.
• A "Client Only" installation was unnecessarily installing the Gateway Wizard. If no gateway is being installed, the program now does not install the Gateway Wizard.

Unique to NXT Controllers:

• None at this time.

Unique to PXL Controllers:

NOTE: For PXL installations, Keri strongly recommends upgrading to the 3.5.1.18 release to take advantage of the improvements made for data throughput and event collection, and for Primary/Secondary controller updating.

• Made multiple improvements in data handling and event collection in the gateway, increasing data throughput when multiple Primary controllers are connected.
• The PXL controller firmware revision was not being displayed in the grid.
• Provided the ability to allow PXL masters to be placed in different world time zones.
• Optimized timing parameters in the gateway to improve data throughput.
• Added a check on credential block enroll for quantity of more than 100 records and automatic download is enabled on any PXL Primary. If those two conditions are met, a message is displayed to the user with two options 1) either reduce the quantity or 2) set the PXL to manual update. This check is necessary due to the slow data transfer rate from Primary to Secondary units.
• Changed the level of detail on certain Live Event messages to be less technical and more user friendly.
• Ensured that if a Smart Update was initiated on a Primary controller, any Secondary controllers also requiring an update were updated as well.
• Added the ability to select if an Update Network or Smart Update command applies to the Primary only or to the Primary and slaves.
• Added a check to Holiday scheduling to ensure only a holiday type of 1, 2, or 3 is selected. The PXL cannot support greater than 3 holiday types.

Unique to Keri NXT Mercury Powered Controllers and Mercury Hardware:

• When adding controllers manually, the program's user interface now waits until a controller update is complete before allowing the next controller to be added.
• Added an automatic status update request following a firmware upgrade on RIMs and 4x4s to collect the information needed to immediately update the unit's status following the upgrade.
• When manually adding Mercury Hardware, the software automatically adds a network communication channel to support the hardware, instead of requiring the communication channel to be added manually. Conversely, if you manually remove hardware its communication channel is now automatically removed as well.
• If a controller's Daylight Savings Time rules are changed, the controller is now tagged as needing to be reset so the new DST rules can be applied to the controller.
• Controllers would not enforce DST rules following a reset as the information was cleared. Controllers now retain this information regardless of the reset function.
• If you deleted an elevator controller from the hardware tree before deleting elevator access groups, you could not remove the elevator access groups from the access group list.
• A new communication channel for a controller is only created if a unique IP address is provided and controller/channel is enabled.

ASSA Gateway:

• Corrected an issue when adding a new access group. The ASSA gateway required a restart to accept the access group. A restart when adding an access group is no longer needed.
• Added new message types to increase the reporting ability of ASSA hardware events.
• Added a Lock/Unlock feature for ASSA IP locks. This feature is enabled only when the lockset is set to Always Connect.

Archive Service

• Made the maximum database size variable based on the SQL revision: SQL 2008 R2 and higher allows a maximum database size of 10 GB, SQL 2008 and lower allows a maximum database size of 4 GB.
• Changed the decision to archive to being based on either of two criteria: the database size in MB or the maximum number of days to keep records in the message table.

Time and Attendance

• Added new access granted event codes to accommodate ASSA and Ingersoll Rand wireless and IP lock products.

Known Issues

• The recent Doors.NET v3.5.1.18 release includes a number of PXL gateway changes that improve data throughput speed between Primary controller and host computer. As a part of this release a body of network characterization work was performed and optimum values were determined for controller timeout and network timeout. These new values are implemented as part of a new PXL installation. However, they are not updated if a software upgrade is performed from Doors.NET software revisions prior to v3.5.1.18. This results in increasing network communication degradation as the number of Primary controllers increases. To correct this issue the Controller Timeout and Network Timeout values must be changed to the optimum values. Refer to the Set PXL Network Timeout Settings section for information on how to make these changes.

Firmware Requirements

For NXT controllers and peripherals:

• Standard NXT controllers require new firmware revision 2.05.27.
• NXT Readers require firmware revision 3.00.01 or greater.
• Reader Interface Modules (RIMs) require firmware revision 3.02.05.
• 4x4 I/O Modules require firmware revision 3.00.02.

For PXL:

• PXL controllers require new firmware revision 8.6.09.
• Legacy PXL controllers should be at firmware revision 8.4.49 or greater (this minimum firmware revision is programmed with the current U.S. Daylight Savings Time dates and has the complete PXL implementation of Anti-Passback).
  

For Mercury Powered NXT controllers and Mercury Hardware:

• Mercury Powered NXT controllers require new firmware revision 1.179.

Firmware Upgrades

NXT Firmware v2.05.27

• A number of communication improvements have been made with NXT readers to ensure proper communication with older reader firmware revisions as well as current releases.

PXL Firmware v8.06.09

• Improves the functionality of the Global Unlock/Lock feature for PXL controllers.

Mercury Hardware Firmware v1.179

• Corrected an issue with properly restoring an NXT reader's LED state following a power cycle.
• Added new message types to increase the reporting ability of certain hardware events.
• Improved communication connectivity with 4x4 units to minimize unit disconnections.
• Updated the collection of data from the 4x4 status command to include more information.

Translations

Completed Translations:

• Chinese (Simplified)
• Chinese (Traditional/Taiwan)
• English (UK)
• French (France)
• Polish
• Russian
• Slovenian
• Spanish (Castilian)
• Turkish
  
  

Translations Pending Updates *:

• Arabic (UAE)
• Dutch (Belgium)
• French (Belgium)
• Italian
  
  

* These translation file sets are not yet complete pending submissions from our translators. If you use these translations you will find mislabeled and/or non-translated ribbon and menu fields in some sections of the program. Non-translated fields will be displayed in US English.