Version 3.5.1.15
Operating System Requirements
Doors.Net software IS NOT compatible with any Home version of Windows XP, Windows Vista, and Windows 7.
This is due to networking restrictions built into the Home versions of Windows operating systems.
Doors.NET IS compatible with the Business, Professional, Ultimate, and Enterprise versions (both 32-bit and 64-bit) of Windows XP, Windows Vista, and Windows 7; as well as Windows Server versions 2003 and 2008 (both 32-bit and 64-bit).
New Features
- Releases a PXL Gateway that supports PXL-500 controllers in the Doors.NET program. This gateway provides free Doors.NET software support for new PXL-500 controller/site installations. Existing Doors32 sites with PXL-500 controllers (now deemed Legacy PXL controllers) can be upgraded to Doors.NET software via a purchased license upgrade. Please contact your RSM or Keri Inside Sales person for upgrade information.
Note: Sites with the following types of controllers are not eligible for upgrading to Doors.NET at this time.
- Entraguard telephone entry controllers (including mixed PXL and Entraguard sites)
- PXL-510 controllers for alarm panel control
- LC-502/-508 controllers for elevator control
Unique to Keri NXT Mercury Powered Controllers (MSC):
Program Improvements
For All Hardware Platforms:
- Updated the MadCap Help Viewer program to the current v6.1 release.
- Added a wide variety of AXIS video plug-ins.
- Corrected an issue when reassigning a door strike from a controller to a 4x4 I/O module. The reader assignment list was not being filled with all the available readers.
- Corrected an issue in actively updating Access Group information between clients when multiple clients are open. The client saving an Access Group change would correctly display the new Access Group name; remote clients would display "New Group" until the remote clients were closed and then re-opened. Now all clients display the new Access Group name whenever changes are saved, regardless of client.
- Improved Temporary Card date resolution by including hours, minutes, seconds to the date selection. In certain applications, a Temporary Card set for one day access would expire immediately after being issued. The full date/time stamp ensures one day Temporary Cards operate correctly.
- Corrected an issue where the online help file would not open when an operator pressed F1 in certain software installations. When certain options were selected, the online help viewer program was not properly being registered during the installation process. The installer has been changed to ensure proper help viewer registration regardless of software installation options.
- Added several new options to the default list of entries for the Emergency Contacts screen.
- Corrected several refresh issues with data entries in the cardholder grid not being displayed until the cardholder grid was closed and then re-opened.
- Added a check that will not allow an Access Group to be deleted if there are still Readers assigned to that group. This allows an Operator an opportunity to ensure that Access Group should be deleted and to reassign any Reader assignments that still exist.
- Increased the number of events that are posted to Live Events to include credential/reader mode changes. This allows the system to maintain a more complete history of credential and reader activity.
- More tightly enforce the rules for disabling overrides with credential mode changes when in the global lock and global unlock state.
- Added value comparison between minimum and maximum Strike times. Previously the program allowed these values to be set independently, and did not check to see if an illogical entry was made (i.e., setting a maximum Strike time to a value less than the minimum Strike time). The program now automatically increases the maximum time if the minimum time is set to a value greater than the existing maximum time and decreases the minimum time if the maximum time is set to a value less than the existing minimum time. In both cases, the maximum and minimum times will be the same.
- Added a value check to entries to the cardholder grid. If an invalid data value was entered into one of the cardholder grid fields the grid display could go blank. The program now checks and rejects invalid data entries.
- The program now requires that a new cardholder entry be saved before attaching a photo to that cardholder. This ensures the new cardholder entry is created in the database, providing the proper database location for the photo to be attached.
Unique to NXT Controllers:
- Corrected an issue when in Lock-down Mode. RTE requests were being performed by the system when they should not be. When in Lock-down Mode, an RTE request should generate an event, but not be performed. Lock-down Mode now operates correctly.
-
Corrected a status display issue with RIMs when performing a Firmware Update. When an update network was completed, the timing for requesting updated status was performed so quickly that some RIMs had not completely rebooted following the firmware update. These RIMs would not display on the status screen though they had been correctly updated and were actually operating. The system now has a slight delay between completing the update and requesting status from the RIMs to ensure the RIMs have enough time to reboot and come back on line. Opening the firmware update screen for NXT controllers now requests status of the controllers so the screen is up to date with the modules that are online.
- Added the Smart Update feature for NXT controllers. When a smart update is performed only newly entered changes are uploaded to the controllers.
- Improved the tracking of updates for controllers that are offline at the time an update is performed. Controllers are marked in the user interface as needing specific updates if they were offline when the update was performed. When these controllers come back online, these updates are automatically performed. Successful updates will clear these update markers and failed updates will reset these markers.
- Improved the reporting of controller firmware revisions in Live Events. If a controller failed to report its firmware revision, Live Events now reports the command failed. If a controller reports a revision that is out of date, Live Events shows both the current and the expected revision numbers.
- Corrected an issue where a change to a door strike time was not received by the controller unless the gateway was restarted.
- Changed the door contact default value to No Door Contact (which disables the call outs for strike minimum time and strike mode). This accommodates the majority of our customers who do not use a door contact on their installations.
Unique to Keri NXT Mercury Powered Controllers (MSC):
- Added a Special Event option to the Holiday Schedule list. This allows a one-time special event schedule to be defined that does not affect any other existing schedule.
- Added support for the Assa Aperio AH-30 hub supporting 8 wireless locks with a 50 foot range.
- Added firmware upgrade status messages to provide active feedback during an upgrade.
- Added options to the System Calendar allowing a Full Cardholder Download and an Update Network to be scheduled operations.
- Corrected an issue with setting a vacation date. Vacation Settings are used to temporarily disable a credential when a cardholder goes on vacation. The program originally assumed a vacation would start at some date in the future and run some number of days. If an operator set a credential's vacation date to begin immediately, that start date would not be applied correctly. The program now accepts immediate vacation start dates.
Known Issues
Firmware Requirements
For NXT controllers and peripherals:
- Standard NXT controllers require new firmware revision 2.05.23.
- NXT controllers with Mercury Inside firmware require new revision 1.01.40.
- NXT Readers require current firmware revision 3.01.01.
- Reader Interface Modules (RIMs) require current firmware revision 3.02.05.
- 4x4 I/O Modules require current firmware revision 3.00.02.
For PXL:
- PXL controllers require current firmware revision 8.6.04
- 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)
Note: Legacy PXL controllers require an optional license to be used with Doors.NET software.
For Mercury Inside (MSC) NXT controllers:
- MSC NXT controllers require new MSC firmware revision 1.01.40.
Firmware Upgrades
Standard NXT Firmware v2.05.23
- Turns off multicast support within the firmware as the Doors.NET software does not communicate with the NXT controller via multicast. This allows the NXT controller to ignore an entire class of Ethernet communication that does not apply to the controller.
Mercury Powered NXT Firmware (MSC) v1.01.40
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.