- The standard NXT controller requires new firmware revision 2.05.22.
- The NXT Reader requires new firmware revision 3.01.01 specifically to enable the In/Out reader function. If this feature is not being used then the previous version of reader firmware (v3.00.01) continues to be fully functional.
- The Reader Interface Module (RIM) requires new firmware revision 3.02.05.
- The 4x4 I/O Module requires new firmware revision 3.00.02.
- The Mercury Inside gateway (MSC) requires that NXT controllers have new MSC firmware revision 136.
Note: Due to networking restrictions built into the Home versions of Windows operating systems, Doors.Net software is NOT compatible with any Home version of Windows XP, Windows Vista, or Windows 7. Doors.NET IS compatible with the Business, Professional, and Ultimate versions (both 32-bit and 64-bit) of Windows XP, Windows Vista, and Windows 7.
- Added the ability to display a photo associated with an event in the Live Events window. When an applicable event occurs, if the cardholder screen is open a double-click displays the cardholder record. If the cardholder screen is not open, a tool tip with the cardholder photo, last name, first name, middle name is displayed.
- Added the Personal Identity Verification (PIV) 75-bit format to the Wiegand library of standard card formats.
- Added a Block Delete cardholder feature. This is useful if a Block Enrollment is done incorrectly and needs to be deleted and performed again, saving time in the cardholder deletion process. Block Delete is limited to 50 credentials at a time.
- Added support for the NXT-6RK keypad reader.
- Added support for keypad commands when using a Wiegand keypad with NXT controllers with Mercury Inside firmware.
- Added support for Elevator Control when using NXT controllers with Mercury Inside firmware.
- Added In/Out Reader support for NXT controllers with Mercury Inside firmware.
- Added support for ASSA Aperio wireless door locks when using NXT controllers with Mercury Inside firmware.
- Added support for Axis M1054 and M1103 cameras.
- Corrected an issue where the software installer unnecessarily installed the Doors.NET Services Tray Application on client-only installs. This application is only needed on the host computer running the Application Server.
- Corrected an issue with license reactivation while Internet access was unavailable (typically done when a user adds a new licensed feature). The License Manager would lock the program, waiting for an activation response until Internet access was restored. The system will now allow the program to operate without the new feature addition, requiring the user to repeat the activation process when Internet access is finally restored.
- Added a notification for the user such that if a Gateway is offline when a Synchronize Clocks command is performed a notification dialog appears to alert the user that the Gateway could not be synchronized.
- Added an automatic Gateway assignment such that when a new Gateway is added in the Gateway Wizard, that new Gateway is automatically selected before continuing to the activation step. Previously you had to manually select the newly created Gateway.
- Added cut-and-paste capability when entering a starting IP address during auto-configuration. The address field will parse the data being entered and delete it out if invalid characters are entered.
- Disabled the Apply button during an auto-configuration. The Apply button has no purpose during the auto-configuration process, so it is now disabled (grayed out) during auto-configuration to minimize confusion during the auto-configuration process.
- Corrected the status update process following an auto-configuration to only collect status on the selected controllers. This speeds up the status collection time and does not collect unneeded data.
- Corrected an auto-configuration issue with very old NXT firmware revisions (2.03.12 or earlier) where the software is waiting for a specific response from the firmware that early firmware revisions do not provide.
- Added a notification regarding the proper method to change a controller's IP address. A user cannot change a controller's IP address from the Communication Setting property, it must be changed during auto-configuration.
- Increased the time out values used for firmware updates to accommodate updating via slow, wireless networks.
- Implements an Update Network Required notification to be displayed in multiple places when applicable. Certain types of system changes are not automatically updated on the network. These notifications alert the Operator to the need to perform a manual update when ever necessary.
- Corrected a settings issue with keypad readers where if you changed to a non-standard setting the keypad reader would work correctly, but if you made a subsequent change to any other reader value, the keypad reader would revert to default settings.
- Corrected a display issue under Access Groups where Keypad readers were listed by code number and not manufacturer model.
- Corrected an interface display issue where the correct state for disabled readers was not displayed properly following an auto-configuration until the user client was restarted.
- Corrected a Controller status issue that prevented the Reader status from being properly displayed under certain conditions.
- Corrected an issue with Access Groups that allowed multiple Reader assignments in an Access Group for Readers on buses 2, 3, or 4.
- Added time duration information to the Lock Out Duration parameter for keypad readers. The tool tip associated with this field now explicitly states the time out is in minutes.
- Removed the facility code field from the Credentials window for NXT credentials. NXT credentials do not use a facility code field.
- Added a Close button to the Block Enrollment window that is enabled once a block enrollment command is performed. The Block Enrollment window has the operating system default "X" box to close the window, but adding an explicit Close button makes the process more obvious.
- Restored a missing card number field to cardholder reports. When running a report on cardholders, if you selected the card number column to be included in the report, the reported value came up blank. When selected, the report now shows the card number for the cardholders.
- Suppressed a spurious "No Search Results Found" warning message that would appear in brand new software installations where no cardholders have been enrolled. This message is now suppressed if there are no cardholders in the database.
- Increased the number of characters allowed in the Contact and Company data fields under cardholders from 50 to 256.
- Corrected a credential editing issue that prevented an operator from manually adding a credential to a cardholder record immediately following a credential deletion operation. Previously the credential deletion locked the credential fields and required the operator to exit then reenter the cardholder record. This is no longer necessary.
- Increased the number of characters allowed for cardholder address entry from 50 to 256.
- Corrected an issue such that any change entered for cardholders prompts a database save operation. This ensures that all changes have the opportunity to be saved.
- Corrected an issue in changing the Expiration Date for credentials once an Expiration Reason has been added; adding a reason prevented the date from being changed.
- Added an auto-fill feature when presentation enrolling credentials. All information gleaned from the presentation enrollment is now automatically inserted into the appropriate credential fields in the database.
- Corrected data field display issues when using Presentation Enrollment. Depending upon enrollment type, certain field values would reset to default or null values between steps in the operation.
- Corrected a display issue when enrolling MS credentials where the credential imprint number was not being automatically entered in it's field on the GUI.
- Added the ability for the operator to edit the description of card formats.
- Added more options to the context menus used when creating an email/SMS messaging macro. This makes it easier to include a greater variety of information to these types of messages.
- Corrected operator permissions when setting holidays or time schedules. An operator with view-only permission for these two fields was still able to add new holidays or time schedules.
- Removed the default password when confirming Intrusion device type Alerts. The use of passwords for confirmation is optional.
- Corrected a display issue under Local Linkage triggers where readers were listed by bus number and not by reader name.
- Corrected an issue where certain user interface screens would not update their data in real-time. You had to close and then reopen the screen to get current information.
- Changed the Request to Exit default setting from Disabled to Momentary.
- Corrected several language translation text errors.
- Corrected an issue with the Hardware Browser where the Save All button did not highlight when more than one hardware change was made.
- Corrected an issue where there were certain categories of events that would not activate Alarm Sounds when sounds were assigned to these events.
- Moved all line supervision settings to the Advanced View feature set as line supervision is not a commonly used feature.
- Corrected an issue where certain 3-state and 4-state supervision events were not being reported correctly.
- Changed the descriptions of certain local linkage actions to be more descriptive of the action.
- Corrected an issue where changes to a link action pulse time were never recognized; the pulse time never varied from the default value.
- Added an automatic Access Group assignment such that if an operator is allowed to create a new Access Group, that operator will automatically be allowed to assign that Access Group to other users.
- Corrected an issue in reporting the Credential Lock Out event in the Live Events window. This event is generated when the maximum number of PIN attempts are made on a keypad reader.
- Corrected the timing on Door Held Open events. The Door Held Open timer had been set to start when the door lock is energized. This resulted in the Door Held Open time functionally being the same as the Door Strike Time. Timing has now been changed such that the Door Held Open timer now starts when the Door Contact shows the door has been physically opened.
- Removed the requirement to select a day-of-the-week when setting a Primary Schedule. This allows a schedule to be created based only on time interval and holiday type.
- Corrected an issue where the Situation Manager did not properly handle a specific security level switching option. The system would correctly switch from less secure Card-Only to more secure Two-Card required, but would not switch back to the less secure option.
- Standardized the wording for all Situation Manager states and all related event messages.
- Corrected an issue where setting Operator Permissions did not correctly handle permissions for System Options.
- Provided a warning that when making changes to operator permissions, these changes will not take effect until the client has logged out and logged back in.
- Corrected an Operator Permissions issue when working with credential Block Enrollment. Block Enrolled credentials are assigned to No Access Group. An operator who has been granted restricted permission to view Access Groups may not be able to view credentials assigned to No Access Group. These operators are now able to view this group of credentials only on the All Cardholders report or when first entering the cardholder menu.
- Changed the way Operator Permissions can be set for System Administrator accounts. It had been possible for an Operator to set Permissions for all Operators in a manner that disallowed ALL Operators access to Operator Permissions. This meant that no further Permission changes could be made for any Operator. Now the software will allow Operator Permission changes to be made to all other Operators, but not to the Operator making these changes. This ensures that at least one Operator retains full Permission changing ability.
- Corrected an issue with Reports for all Readers. If a Reader was offline, it would not be included in the report.
- Changed the text for NXT controller reader status from device online/offline to reader online/offline. This improves report readability and is consistent with what is reported for Mercury Inside controllers.
- Added flexibility to client reports by changing from fixed report date periods of 1 to 4 weeks to flexible date report periods of 1 to 30 days.
- Improved the method by which controller events can be searched when creating reports. Events can now be searched by either server time stamp or controller time stamp.
- Set default start and end dates in the Reports feature to display the current day. This is a requested convenience when generating reports later in the year as it saves the user from having to step through calendar settings that begin at the first of the year.
- Corrected an issue when searching by User Groups. Searching does not work when multiple user groups are assigned to cardholders.
- Set data filtering to default to filtering by controller. This can be changed to be specific to reader, input, output, etc.
- Corrected an issue with text searches in Property Filters. If you entered text into the Property Filter search field that is not present in the Property, the Property window stops responding. The Administrative client had to be restarted to restore functionality.
- Corrected an issue when creating monitoring filters. Certain filter types would not save properly, rendering those filters unavailable.
- Corrected an issue when applying either the Mask Forced or Mask Both filters. A Reader Contact - Door Closed event message would display in Live Events, but its corresponding Reader Contact - Door Opened event would not. Both events now appear in Live Events in proper order.
- Corrected an SQL issue where database backups would only be successfully performed if the default backup name was used.
- Corrected a database issue where the database was not updated in a timely manner following a controller deletion, allowing stale information to be displayed in the grid.
- Corrected default settings for the Vivotek video driver.
- Corrected a positioning issue with the Photo Recall feature where horizontal docking would come up initially in a vertical orientation. Horizontal docking now comes up in the correct orientation all of the time.
- Corrected a template display difference between the program client and the Photo-ID client that could make it difficult to properly edit the template.
- Removed the Factory Defaults option from the Mercury Inside controller options pull-down list as it does not apply to this controller type.
- Corrected a Mercury Inside gateway issue that had the Gateway Wizard automatically assigning a default Mercury controller type to the gateway, even if None was selected.
- Corrected an issue when assigning an IP address to a controller with Mercury Inside firmware. When configuring a panel and assigning an IP address, you must save the IP address before performing other tasks. The warning message to alert the user to this requirement was not appearing when needed, allowing a user to make other changes that invalidate the IP address assignment.
- Corrected an issue with the Request Status command when using Mercury hardware or NXT hardware with Mercury Firmware. Not all status fields would be updated and the controller date stamp would not be updated.
- Corrected a parameter update issue with NXT controllers using Mercury Firmware. Certain parameter changes require the controller board to be reset, and this wasn't always being announced to the user. When necessary, the program now will automatically perform the reset as a part of the parameter save operation.
- Extended IP addressing support in the Gateway for Mercury products.
- Added Suspend/Restore functions for Door override functions on NXT controllers with Mercury Firmware.
- Door strike outputs cannot be reassigned from a controller to a 4x4. This should be allowed in the software, but when you assign a 4x4 output to be a "Strike," the corresponding drop-down list is not displaying the Readers that can be reassigned to that output. This only applies to new reassignments. If you upgrade the software from a previous revision and have these types of reassignments applied, they correctly remain active. You just cannot make new assignments.
- Chinese (Simplified)
- Chinese (Traditional/Taiwan)
- English (UK)
- French (France)
- Spanish (Castilian)
Translations Pending Updates *:
- Arabic (UAE)
- Dutch (Belgium)
- French (Belgium)
* 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.
Required Firmware Upgrades
Standard NXT Firmware v2.05.22
- Corrects an issue where presenting the same credential to a Reader multiple times would cause the Controller to process the same credential data multiple times, delaying the controller from processing data from a new credential. This additional processing time, in turn, would delay the unlocking of the door for the new credential.
- Corrects an issue with incremental credential adds and deletes that prevented some credentials from being granted access until a full card holder database update was performed.
- Adds the ability to change the Server ID, Controller ID, and Network Data using Telnet commands. This feature can be useful when configuring Controllers that are spread out over a WAN.
NXT Reader Firmware v3.01.01
- Provides support for In-door/Out-door Readers (also known as Primary/Secondary Readers). This feature allows two Readers to be managed from one bus on the Controller, with both readers controlling one door; one Reader for the In/Entry direction and one Reader for the Out/Exit direction. A Reader with this firmware revision or greater can be toggled between In-door and Out-door configurations. This is done by presenting an NXT Address Change Control Card to the reader within the first 60 seconds of reader power up.
Note: Having two Readers of the same configuration on one bus (both In-door or both Out-door) is an illegal configuration resulting in neither Reader being recognized or acknowledged by the system.
RIM Firmware v3.02.05
4x4 Firmware v3.00.02
- Provides complete hardware information when a status command is performed.
Mercury Inside (MSC) Firmware v136
- Remembers the controller's assigned IP instead of resetting the IP to a default value whenever the controller is reset.
- Provides support for In/Out NXT Readers.
- Provides support for Assa Aperio wireless locks.