Doors.NET Release Notes - 01298-014 Rev. A
Doors.NET v5.3.0 Software - 02635-014
Operating System Compatibility
Doors.NET series 5 software IS COMPATIBLE with:
- Windows 8.1
- Windows 10 - all versions
- Windows 11 - all versions
- Windows Server 2012 and 2012 R2
- Windows Server 2016
- Windows Server 2019
- Windows Server 2022
All other operating systems are NOT SUPPORTED.
Microsoft .NET Framework Notes
- Doors.NET v4.8.0 and higher uses .NET Framework v4.8.
- If your PC does not already have .NET Framework v4.8 installed, the Doors.NET installer will stop and prompt you to install it.
- All supported operating systems are compatible with Microsoft.NET Framework v4.6.2 or greater.
- PhotoID Badging requires .NET Framework v3.5. If you are running the Microsoft Server 2019 operating system, you must install .NET Framework v3.5 prior to installing Doors.NET software, or else the PhotoID installation will fail. This is done via Server Manager > Manage > Add Roles and Features > Install .NET Framework v3.5.
SQL Server Compatibility
If SQL is ALREADY INSTALLED on your computer:
- The Doors.NET installer will poll the host computer and use the SQL version that is already installed.
- This is true for both new Doors.NET installations and for Doors.NET upgrades.
If SQL is NOT INSTALLED on your computer:
64-bit computers using Windows 10, Windows Server 2016, or Windows Server 2019:
- SQL Server 2019 Express will be installed if SQL server is not already present.
64-bit computers using Windows Server 2012 or 2012 R2:
- You must manually install Microsoft SQL Server Express 2016 or 2017 if SQL server is not already present.
Link to Microsoft's SQL Server Express 2016 SP1 download page:
https://www.microsoft.com/en-us/download/confirmation.aspx?id=54276
Link to Microsoft's SQL Server Express 2017 download page:
https://www.microsoft.com/en-us/download/confirmation.aspx?id=55994
32-bit computers:
- You must manually install the SQL revision appropriate for your operating system.
- Keri recommends installing SQL Server 2014 (the last SQL Server supporting 32-bit computers).
Link to Microsoft's SQL Server Express 2014 download page:
https://www.microsoft.com/en-us/download/details.aspx?id=42299
Please Note
- Doors.NET software installation will not begin if a Windows Update is in progress or a computer restart is pending due to a Windows Update. Make sure all Windows Updates have been completed prior to installing Doors.NET.
Support for PXL and Entraguard has Ended
Doors.NET v5.2.0 was the last software revision that supports the PXL and Entraguard controller types. Ongoing support and development for these products will be in Borealis.
Support for PXL and Entraguard Modem Communication Has Ended
Doors.NET v4.8.0 was the last software revision that will support modem communication for PXL and Entraguard products.
Modem communication for PXL and Entraguard units IS NOT SUPPORTED beginning with Doors.NET v4.9.0.
Installers are notified of this change when selecting an Upgrade Installation in the Doors.NET installation program. Systems that have existing modem communication with controllers can continue to use modem communication using the existing configuration information. The Advanced View option will continue to display this information. Any new controllers added to an existing system must be added using either a serial connection or a LAN network connection. Should someone attempt to select modem communications a popup message box appears stating modem communication is no longer supported. Further, should someone change an existing communication path from modem to serial or network that change is made permanent and there is no reverting to modem communication.
This change was made due to the rapid conversion by telecommunication providers from POTS lines, which are completely modem compatible, to VOIP lines, which do not transfer data packets reliably and have differences that vary from vendor to vendor, making it impossible for us to ensure modem compatibility with all VOIP vendors and the VOIP hardware they use.
You can switch from modem communications to either of the following communication methods:
For Data Communication with Either PXL or Entraguard Units
- Keri recommends replacing your modems with a LAN-520 Ethernet module.
- Alternatively, if your computer has a serial communication port, you can use a direct-connection cable.
For Voice Communication with Entraguard Units
- You will need a VOIP converter for voice calling between Entraguard units and tenants.
- Keri recommends the Cisco SPA 112 VOIP Adapter, however your ISP likely has their preferred unit.
Note: Please keep in mind, if you are using modems for Entraguard and controller communication, Doors.NET v4.8.0 is the last version that fully supports modem communication.
New Features
None at this time
Doors.NET Improvements
- Corrected an issue where a PXL Exit reader would sometimes display in access groups. The PXL Exit reader will now never be displayed on the access groups page.
- The Global Linkage Service (GLS) has been optimized so that the service starts and restarts quicker(and does not retrieve database information that it not required).
- The default baud rate for an NXT-MSC controller port set to Mercury Security is now 38,400 instead of 9,600. 38,400 is the default baud rate for all Mercury downstream controllers and modules.
- Updated the Controller Port Select All Stored Procedure.
- Added Cypress 37-bit credential format (Toll Tag).
- Corrected an Elevator Control issue where some floors would not respond to a scheduled override setting.
- Corrected various output control issues related to Elevator Control, activating outputs using a time schedule or temp unlocking floors (using NXT-MSC controllers and 4X4 or GIOX modules).
- Corrected an issue with Video Integration where recorded video retrieval would sometimes fail to retrieve recorded video clips.
- Corrected an issue where an NXT-MSC controller would be duplicated on the scan page if the MAC address was manually entered using colons instead of dashes.
- Corrected an issue where a Local Linkage template could not be used in Doors.NET v5.2.0 if it was created in a previous version of Doors.NET.
- Corrected an issue on a very large database where a controller update could fail if multiple controllers were sent an update in quick succession.
- Updated the text order of Local Linkage source type for controller inputs.
- Corrected a Local Linkage configuration issue where the controller tamper alarm input source number being sent incorrectly.
- Corrected an issue where the user interface was not correctly restricting the number of NXT time schedules for a mixed NXT and NXT-MSC system.
- Removed unsupported controller options for NXT-MSC controllers (i.e OTIS Destination Dispatch and dormakaba Wi-Q).
- Updated the PXL gateway to optimize system performance.
- Updated the NXT gateway to optimize system performance.
- Updated the MSC gateway to optimize system performance.
Improvements to Both Doors.NET and Visual Doors
Telepathy Improvements
Visual Doors Improvements
Current Firmware Revisions
For NXT Hardware:
- NXT-MSC Controller - v1.294
- Standard NXT Controller - 2.05.80
- NXT Controller Bootloader - 2.00.01
- NXT Reader - 4.00.03
- Standard and WIPLUS Reader Interface Modules (RIMs) - 3.03.21
- Wiegand-Only Reader Interface Modules (now obsolete - replaced by the WIPLUS)
- 3.03.21 provides single-line LED support for Wiegand-Only RIMs
- 3.03.10 provides dual-line LED support for Wiegand-Only RIMs
- 4x4 I/O Module - 3.00.03
- GIOX Motherboard - 1.00.21
- GIOX Input Module - 1.00.10
- GIOX Output Module - 1.00.10
For PXL:
- Standard PXL Controller - 8.6.09
- Legacy PXL Controller - 8.5.22 (requires a Legacy license for operation)
For Entraguard:
- Standard Titanium and Silver - 7.8.02
- Standard Platinum - 9.2.02
- Legacy Titanium and Silver - 7.6.13 (requires a Legacy license for operation)
- Legacy Platinum - 9.1.09 (requires a Legacy license for operation)
For Neutron:
- Neutron Controller - 1.00.19
- Neutron Bootloader - 1.00.08
For Mercury LP Hardware:
- LP Controller - v1.31.0 (new revision - see information below).
For Mercury EP Hardware:
Firmware Improvements
Mercury LP Controller Firmware v1.31.0
- Mercury LP Controller Firmware v1.31.0
- Allow 2.0 migration packages from webpage
- Resolved report correct MAC address on controller power-up
- Resolved strike relay not activating correctly.
- Resolved door strikes firing at the same time
- Resolved incorrect relay is firing in Primary/Secondary reader setup
- Resolved DHCP not sending out new DHCP Request/Discovery when link goes from down to up
- Resolved LED & Relay not following strike time
- Resolved issue causing reader LED to be out of sync
- Resolved reporting Held open transaction instead of forced open
- Resolved relay not pulsing in ACR tailgate mode
- Resolved strike incorrectly deactivating in certain ACR modes
- Resolved Forced Open transaction in Primary/Secondary reader setup.
Known Issues
- AH40 Remains offline after completing a firmware upgrade to the controller and a controller reset is required to bring the AH40 back online. Applies to Mercury LP controller only.