PMT Security

Advanced Access Control

Nexus220

Nexus220 The number of doors for this license has been exceeded

Nexus220 The number of doors for this license has been exceeded

If the Nexus220 database has more than 4 doors, you must have an licensed USB device (typically the Amano RS) properly connected and the correct driver installed before the software can open. Otherwise, you will get an error stating that “The number of doors has been exceeded for this license”.  

In most cases, the unit is simply not plugged in or the driver has not been installed properly.

Verify Devices show in Device Manager

In Device manager, you can verify if the devices exist and have their drivers installed properly.   You may see a couple of different options depending on the Windows version, and device manufacture date.

Look in the ports section for one or more of the following:

MDE USB VCom Port (COMx) 

ImproX USB to UART (COMx)

NEXUS220 VCom (COMx)

The x in COMx will refer to your local COM port in use for that device.  You MUST make certain that the MDE is at a higher COM Port than the RS if you are using both and that they are both using a COM port below 16.  In cases where you only have an MDE that is licensed (2019 and later), you only need to make sure the COM port is below 16.

NOTE: To open Device Manger, you can press the Windows Key plus the R key to open the run menu, then type devmgmt.msc and press OK.

Install the driver

  1. Download the driver setup application from the website or use this link.
  2. Run the setup.exe file as admin and click through to finish the installation.

Verify the software is trying to detect the license device

On the Logon screen, ensure “Security Device Search” field is set to Automatically Search.  If you fail to logon due to this automatic search, try manually entering a COM port name of the licensed device.  (e.g COM3, important that you do not use any spaces) 

Common Problems

Problem:  COM Port too high or COM Port of MDE lower than RS device.  Both must be below COM16.

Solution:  Change port to lower COM port number in Device Manger.

Problem:  USB Serial Device generic driver in use.   

Solution:  You can run the setup.exe and then apply the proper driver. In this case you also may need to go one step further to apply the non generic license. Open device manager and manually change to the MDE driver.  Below are some screenshots from Windows 10 that show how to make this change.

Need further assistance?

Submit a Support Ticket

Submit a Support Ticket

FAQ

Access Control

PM Tronics Hardware

Partner Products

Video Management Systems

How to fix a Java SE Binary Error in Nexus220 Software

How to fix a “Java SE Binary Error” in Nexus220 software.

When you open Amano Software, specifically on systems using the IDEMIA (Morphotrak) biometric integration, a Java SE Binary Error may appear on some systems where Data Execution Prevention is turned on to it’s highest setting.  Data Execution Prevention (DEP) prevents harmful code from running in protected memory locations reserved for Windows and other programs. 

WARNING!  Making chances to the Boot Configuration Data Options can cause your computer not to start.  Check with your local computer systems administrator before you proceed. 

The steps below will lower the Data Prevention Execution settings to allow some programs to OptOut of using it.

  1. Run a windows command prompt as an administrator.
  2. Type:  “bcdedit /set nx OptOut”
  3. You will see a message: “The operation completed successfully”  and you will need to restart the PC for the change to take effect.

NOTE: If you receive an error that says “This value is protected by Secure Boot Policy and cannot be modified or deleted” then you’ll need to enter your BIOS to disable secure boot. Booting onto your BIOS varies by the motherboard and is for advanced users only.  Proceed with caution.

How to revive a non-booting machine after setting DEP to AlwaysOff.

  1. If you have a Windows recovery disk, use it to boot your computer.  (You may make a Windows recovery disk from Windows installation media on another working PC)
  2. Once booted, open an command prompt as administrator.
  3. Type: “bcdedit /set nx AlwaysOn”
  4. You will see a message: “The operation completed successfully”  and you will need to restart the PC for the change to take effect.

NOTE: If you receive an error that says “This value is protected by Secure Boot Policy and cannot be modified or deleted” then you’ll need to enter your BIOS to disable secure boot. Booting onto your BIOS varies by the motherboard and is for advanced users only.  Proceed with caution.

Need further assistance?

Submit a Support Ticket

Submit a Support Ticket

FAQ

Access Control

PM Tronics Hardware

Partner Products

Video Management Systems

Move Nexus220 Access Control System from one PC to another (Firebird)

Move Nexus220 Access Control System from one PC to another (Firebird)

IMPORTANT!!!! Verify you are installing current or newer version of Nexus220 software than what is currently installed.

From the originating PC

  • Close all software on all computers running Nexus220
  • Copy the database file to an intermediate source such as a flash drive or network drive.
    • Default location: c:\nexus220\database\db220.fdb
  • Copy security file to an intermediate source such as a flash drive or network drive.

Default 32-bit path: c:\program files\firebird_2_1\firebird\security.fdb (This may also be called security2.fdb, or have another number appended to it.)

Default 64-bit path:  c:\program files (x86)\firebird_2_1\firebird\security.fdb (This may also be called security2.fdb, or have another number appended to it.)

*Firebird security file may be named security2.fdb

On new PC where software is being moved to:

IMPORTANT!!!! Verify you are installing current or newer version of Nexus220 software than what is currently installed.

  • Install new instance of software from installation disc or download
  • Rename database created during installation to db220_empty.fdb

Default Location: c:\nexus220\database\db220.fdb

  • Paste database copied from original PC into the c:\nexus220\database\ folder.
  • Rename security.fdb (or security2.fdb) file created during installation to securityOLD.fdb (or security2OLD.fdb respectively)
  • Paste security file copied from the original PC into the appropriate field.
  • Default 32-bit path: c:\program files\firebird_2_1\firebird\security.fdb
  • Default 64-bit path:  c:\program files (x86)\firebird_2_1\firebird\security.fdb
  • When you open the software it will prompt you to upgrade the DB
  • Ensure the database scripts are at or newer than the current version.  If they are older, run the updater tool and note any errors.  If there are errors, stop immediately and call Tech Support.

Need further assistance?

Submit a Support Ticket

Submit a Support Ticket

FAQ

Access Control

PM Tronics Hardware

Partner Products

Video Management Systems

Nexus220 Firmware Upgrade

Nexus220 Firmware Upgrade

Introduction to Nexus220 Firmware Upgrade

The Firmware Upgrade Utility lets you perform the following actions:

  1.  Identify Firmware versions of connected Hardware.
  2.  Selection and configuration of the Communications Port.
  3.  You may Ping the connected Hardware (feedback informs you of whether Hardware is connected and working as specified).
  4.  Perform in-field Firmware Upgrades to connected Hardware.

NOTE: For proper results, ensure you close the Nexus220 software before running the Firmware Upgrade Utility

Opening the Utility

On the Device where Nexus220 resides, go to  C:\Nexus220\bin\FirmwareUpgrade.exe.

Select and Configure the Communications Port

To specify a communication protocol, continue as follows:

1. In the Protocol group, select one of the following radio buttons:

  • RS232 – used where your Nexus220 Controller connects by RS232 or USB or where or you are using a communications     interface device, select the RS232 option and enter the relevant COM Port number.
  •  TCP/IP – used where your Nexus220 Controller connects by Ethernet.
  •  UDP – used when connecting UDP to a single Controller.
  •  UDP Multi Controller – used when connecting many UDP devices. On selection of the UDP Multi Controller radio button, a drop-down list displays, listing IP Mapping files created by the Nexus220 Base Application. Creation of these files takes place on closure of the Base Application Module, on hardware Auto-ID or on replacement of a Controller. From the drop-down list you can select a site matching to your Nexus220 setup. Once selected, the Firmware Upgrade Utility communicates with all the Site’s Controllers

2. Based on your selection made in step 1, complete the following activated fields:

  • Host IP – your Nexus220 Controller’s IP Address.
  • Host Port – enter the default Host Port number of 10005.
  • Local Port – enter the default Local Port number of 10005.
  • Baud Rate – use the default 38 400.

Ping Function

Ensure that all hardware is connected and working as specified by using the Ping tool.

  • Click the Ping button.
  • At the IP Door Controllers dialog, click the OK button.

Firmware Upgrade Procedure

NOTE: On Sites with installed iTT or iTRT Ethernet Terminals, upgrade the Controller’s Firmware and perform a Full Upload before upgrading the Terminal’s Firmware.

Controllers

To upgrade the Firmware on a Controller, proceed as follows:

  • Configure the Protocol settings specific to your Controller and installation requirements. Refer to the section Selecting and Configuring the Communications Port on page 5.
  • Ensure all hardware is connected and working as specified using the Ping tool. Refer to the section Ping Function on page 6.
  • Click the Controller’s Select checkbox. 
  • Click the Upgrade button.
  • Once the Upgrade is complete, perform a Full Upload. For information on performing a Full Upload, please refer to the section Full Upload in Part 3 – General Configuration.

NOTE: The Force Upgrade checkbox forces an upgrade on a unit that has a newer firmware version than is available with your current Nexus220 Software Suite. We recommend that you do not use this feature.

Terminals and Readers

To upgrade the Firmware on a Terminal or Reader proceed as follows:

  1. Configure the Protocol settings specific to your Controller and installation requirements. Refer above to the section Selecting and Configuring the Communications Port.
  2. Ensure all hardware is connected and working as specified using the Ping tool. Refer to the section Ping Function mentioned earlier in this document.
  3. Click the Terminal or Reader’s Select checkbox.

NOTE: Readers connected to a Terminal have the same fixed address as the Terminal itself. When upgrading a Terminal and its Readers, ensure that you select the check boxes of both the Readers and the Terminal.

  • 4. Click the Upgrade button.

NOTE: The Force Upgrade checkbox forces an upgrade on a unit that has a newer firmware version than is available with your current IXP220 Software Suite. We recommend that you do not use this feature.

NOTE: The ImproX iTT, iTRT, MDR and MDK allow for Zero Downtime Upgrade Support. During a firmware upgrade the affected Hardware continues to operate as expected, however for the ImproX MDR and MDK the LED flickers intermittently while the new file uploads. Once the upgrade is complete, a reset (about 30 seconds) takes place for the new firmware to load. During this reset, the related Hardware will not read Tags.

Display Firmware Versions (Available on the Software CD)

From the Config drop-down menu, select File Versions to view firmware file versions available on the local IXP220 Installation.

Need further assistance?

Submit a Support Ticket

Submit a Support Ticket

FAQ

Access Control

PM Tronics Hardware

Partner Products

Video Management Systems