• Skip to primary navigation
  • Skip to main content
PMT Security Logo

PMT Security

Advanced Access Control

  • Home
  • About Us
    • Our Partners
    • Our Integrators
  • Solutions
    • Residential
    • Government Facilities
    • Education
    • Retirement
    • Manufacturing
    • Retail Businesses
    • Campgrounds & Outdoor Resorts
  • Products
    • Access Control
      • Control Features
      • Reporting & Monitoring
      • Control Module
      • Digital IO Module
      • Reader Module
      • Readers
    • Video Management
      • Analytics
      • Security Cameras
    • Visitor Management
  • Support
    • Knowledgebase
    • Download Center
    • License Request
    • RMA Request Form
  • Blog
  • Contact Us

AmanoNet

TCP and UDP ports for ImproNet/AmanoNet

TCP and UDP ports for ImproNet/AmanoNet

Ports that AmanoNet uses to Communicate Properly

Ports in AmanoNet are used for various purposes and protocols. Here is a list of TCP and UDP ports along with their corresponding functionalities:

TCP Ports:

– Port 80: Used for HTTP Web Reports.

– Port 443: Used for SSL Web Reports.

– Port 1433: Used for MS SQL.

– Port 3050: Used for Firebird.

– Port 10008: Used for All IP Terminals.

– Port 10500: Used for Discovery.

– Port 11010: Used for Morpho.

– Port 26661: Used for Alarm Viewer.

– Port 26663: Used for Transaction Viewer.

– Port 26665: Used for Messaging Port.

– Port 26667: Used for Door Status Port.

– Port 26668: Used for Engine Status Port.

– Port 26669: Used for Host Validation Port.

– Port 26680: Used for Security Server Port.

UDP Ports:

– Port 10002: Used for EC2 Controller.

– Port 10008: Used for IP Terminals.

– Port 10500: Used for Discovery.

These ports play a crucial role in facilitating communication and data transfer within the AmanoNet system.

Need further assistance?

Submit a Support Ticket

Submit a Support Ticket

FAQ

General

Can I initiate RS485 comms to a terminal from an existing IP terminal?

How to Select the Right Cable for the job

IDEMIA Sigma Lite Readers NOT compatible for use in AmanoNet or Nexus220

Network Configuration – Best Practices

Technical Bulletins

OMNIA Run as a Service fix for v4.x

Access Control

AmanoNet

AmanoNet Back up using IB Console

AmanoNet Minimum PC Requirements and Specifications

AmanoNet System Migration Notes

Archive Tagholders in AmanoNet

Archive Transactions in AmanoNet

AutoID IP Hardware in AmanoNet

How to move AmanoNet Access Control System from one PC to another (Firebird)

IDEMIA Sigma Lite Readers NOT compatible for use in AmanoNet or Nexus220

ImproNet/AmanoNet Database Backup: SQL

NOTICE! UPGRADE TO AMANONET 7.74 – EC2/400i NO LONGER AVAILABLE

Nexxus220

Change Default Password in Nexus220
Database Migration from Nexus220/IXP220 to OMNIA
How to fix a Java SE Binary Error in Nexus220 Software
How to get a copy of a database from Nexus220 Software
How to move Nexus220 to a different PC
IDEMIA Sigma Lite Readers NOT compatible for use in AmanoNet or Nexus220
Move Nexus220 Access Control System from one PC to another (Firebird)
Nexus220 Firmware Upgrade
Nexus220 Notifications Configuration/Email Configuration
Nexus220 The number of doors for this license has been exceeded
Nexus220 Web Reports Using Microsoft Edge
Reduce length of time on buzzer for readers in Nexus220

Omnia

Adding Widgets to the OMNIA Dashboard

Basic Trouble Shooting OMNIA

Batch Operations OMNIA

Change SYSDBA Password in OMNIA

Configuring Web Session Timeouts in OMINA

Create a Database for OMNIA 4.5 After Running the .iso

Create a Site Lockdown Input for OMNIA

Creating an Input on a Wiegand Reader Module to Generate a Lockdown/Emergency Mode For a Single APC Controller In OMNIA

Creating Operator Profiles

Creating Relay Actions I/O in OMNIA

Omnia Lite

Convert a Nexus Lite Database into OMNIA Lite Database

OMNIA LiTE Backup

PM Tronics Hardware

Amano Readers and Credentials

Change Modulation mode on XQT904 Quad Transmitter
How do I change Wiegand Output Mode on Amano readers?

Legacy Hardware

Factory Reset legacy Amano IP Cameras (sold prior to 2018)

Factory Reset Nexus220 controller

How do I factory reset the EC2 (400i) controller?

Setting IP on PMTronics Inc. Access Control Hardware

Partner Products

Partner Products

IDEMIA Sigma Lite Readers NOT compatible for use in AmanoNet or Nexus220

Setting Read Range on a Conekt Reader

Video Management Systems

Cathexis Video (Amano Vision)

Cathexis Video AV (AntiVirus Exceptions)

AmanoDVMS

Which AmanoDVMS ports need to be open on my firewall?

Vision

AmanoVision web access user name case sensitivity usage

Unlock on First Tag in AmanoNet

Setting up Unlock on First Tag in AmanoNet

Steps and Procedure to Configure a Valid Tag to Open and Keep a door unlocked for a specific amount of time in AmanoNet.

Unlock on First Tag feature in AmanoNet provides the facility of unlocking selected door(s) when the first valid Tag is presented during a specified time period. The door remains unlocked for that time period, but is locked outside that time period, opening only on presentation of a valid Tag.


Example
In the following example procedure, activate the Unlock on First Tag feature only on weekdays from 7 am to 5 pm. This means that you must create the following Device Time Patterns (in Access) for the Terminal(s) concerned:

  • A Device Time Pattern from 7 am until 5 pm on weekdays (Monday to Friday). This is the period for which the Unlock on First Tag feature must be enabled.
  • A Device Time Pattern from Sunday until Friday, 5 pm until 12 am. This is the remaining time on each of the above days during which the Unlock on First Tag feature must be disabled.
  • A Device Time Pattern from Sunday until Friday, 12 am until 7 am. The Sunday period covers the time from midnight to 7 am on Monday.
  • A Device Time Pattern called Deactivate Relay at 17:00. Set the start time to 5 pm and select Monday to Friday. This will End the Unlock on First Tag
  • A Device Time Pattern for Saturday, Sunday and public holidays for the full 24 hours. These are the days on which the Unlock on First Tag feature must be disabled.


Device Time Pattern Setup


1. In Access, in the Navigate Pane (from the Hierarchical Tree) select Device Time Patterns

2. In the Main Pane, click the Plus button.

In AmanoNet select "Device Time Patterns" from system menu located to the left. Then select the "+" symbol at the bottom of the window.

3. In the Description textbox, enter a name for the Device Time Pattern.

4. If required, complete the Start Date and Stop Date textboxes.

5. In the Start Time field, enter 0700.

6. In the Duration field, enter 1000.

7. Select the Monday through Friday checkboxes.

Set-up your time pattern.
Describe the pattern, set your dates and time durations, and select the days of the week required for this device time pattern.

8. Repeat the processes mentioned in steps 2 to 7 for the remaining Device Time Patterns. When are complete it should look similar to Below.

Follow steps 2 -7 for your remaining device time patterns, when you are finished your device time patterns will be displayed accordingly in AmanoNet.

Relay Action Setup

NOTE: This Action enables the relay for an indefinite period.

Create New Action – Mon-Fri 07:00-17:00 Device Time Pattern


1. Select the Actions tab, for the output relay on the Terminal controlling the door strike.

2. In the Main Pane, click the Plus Button.

3. In the Action Name textbox, assign your action the name Enable Relay Indefinitely.

4. Alongside the Time Pattern textbox, click the browse button.

5. From the list of displayed Device Time Patterns, select the Mon-Fri 07:00-17:00 record.

6. Click the button Save Button.

7. At the New Action dialog, click the save button.

8. In the Action Parameters dialog, set the Duration (0.1s) to 65535.

9. Click the Save Button.

Create New Action - Mon-Fri 07:00-17:00 Device Time Pattern.

Select the Actions tab, for the output relay on the Terminal controlling the door strike. Select the "+" symbol.
Displays how to Enable Relay in AmanoNet.
To activate indefinitely in AmanoNet set duration to 65535

Create New Action – Sat, Sun, Hol 24hrs Device Time Pattern


1. In the Main Pane, click the Plus Button.

2. In the Action Name textbox, assign the action a name (for example Drive Relay 4 Seconds).

3. Alongside the Time Pattern textbox, click the browse button.

4. From the list of displayed Device Time Patterns, select the Sat, Sun, Hol 24 Hrs record.

5. Click the Save Button.

6. At the New Action dialog, click the Save Button

7. In the Action Parameters dialog, set the Duration (0.1s) to 40 (4 seconds).

8. At the Action Parameters dialog, click the Save Button.

Create New Action - Sat, Sun, Hol 24hrs Device Time Pattern
Sat, Sun, Hol 24hrs Device Time Pattern duration 40


Edit Action – Sun-Fri 17:00-00:00 Device Time Pattern


1. In the Main Pane select the existing Relay – Allowed In Action.

2. Click the Gear button.

3. In the Action Name textbox, assign the action a new name (for example Sun-Fri 1700-0000).

4. Alongside the Time Pattern textbox, click the browse button.

5. From the list of displayed Device Time Patterns, select the Sun-Fri 17:00-00:00 record.

6. Click the Save Button.

7. At the Edit Action dialog, click the Save Button

Create New Action – Sun-Fri 00:00-07:00 Device Time Pattern


1. In the Main Pane, click the Plus Button.

2. In the Action Name textbox, assign your action a name (for example Sun-Fri 0000-0700).

3. Alongside the Time Pattern textbox, click the browse button.

4. From the list of displayed Device Time Patterns, select the Sun-Fri 00:00-07:00 record.

5. Click the Save Button.

6. At the New Action dialog, click the Save Button.

7. At the Action Parameters dialog, click the Save Button.

Create New Action – Deactivate Relay at 17:00 Device Time Pattern


1. In the Main Pane, click the Plus Button.

2. In the Action Name textbox, assign your action a name (for example Deactivate Relay).

3. Alongside the Time Pattern textbox, click the browse button.

4. From the list of displayed Device Time Patterns, select the Deactivate Relay at 17:00 record.

5. Click the Save Button.

6. At the New Action dialog, click the Save Button.

7. In the Action Parameters dialog, set the Duration (0.1s) to 65535.

8. At the Action Parameters dialog, click the Save button.

Create New Action - Deactivate Relay at 17:00 Device Time Pattern
To deactivate indefinitely set duration to 65535

AmanoNet New Action – All Relays


1. In the Main Pane, click the Plus Button.

2. From the Select Action Type drop-down list, select the Multiple Actions option.

3. In the Action Name textbox, assign your action a name (for example All Relays).

4. Click the Save Button

5. In the Action Parameter dialog, for the First Action, click the 1 button.

6. From the list of displayed actions, select the Sun-Fri 1700-0000 action created earlier.

7. For the Second Action, click the 2 button.

8. From the list of displayed actions, select the Sun-Fri 0000-0700 action created earlier.

9. For the Third Action, click the 3 button.

10. From the list of displayed actions, select the Enable Relay Indefinitely action created earlier.

11. For the Fourth Action, click the 4 button.

12. From the list of displayed actions, select the Drive Relay 4 Seconds action created earlier.

13. Click the Save button.

14. At the Action Parameters dialog, click the Save button.

NOTE: Steps 5 through 12 are shown all at once for clarity. The Action Selector window will close and open between each step after selecting the Save Button (13)

AmanoNet Active System Events Edit

1. In the Main Pane, click the Active System Events button.

On opening, under Actions for Allowed Events, the First Action appears as Sun-Fri 1700-0000,

add the remaining actions as follows:


2. Under Actions For Allowed Events, replace the First Action, by clicking the 1 button.

3. From the list of actions displayed, select the All Relays action you created earlier.

4. Click the Save Button.

5. At the Active System Events Editor dialog, click the Save Button.

6. At the Confirm Save dialog, click the Yes button.

AmanoNet Time Triggered Action Setup

1. In Access, in the Navigate Pane (from the Hierarchical Tree), select Time Triggered Actions.

2. In the Main Pane, click the Plus Button.

3. In the Action Name textbox, give your Time Triggered Action a meaningful name (for example

Deactivate Relay 1).

4. Click the Trigger Time’s associated browse button.

5. From the list of displayed Device Time Patterns, select the Deactivate Relay at 17:00 record.

6. Click the Save Button.

7. Click the Execute Action’s associated browse button.

8. From the list of displayed actions, select the Deactivate Relay action created earlier.

9. Click the Save Button.

10. At the Create Time Triggered Action dialog, click the Save Button

Need further assistance?

Submit a Support Ticket

Submit a Support Ticket

FAQ

General

Can I initiate RS485 comms to a terminal from an existing IP terminal?

How to Select the Right Cable for the job

IDEMIA Sigma Lite Readers NOT compatible for use in AmanoNet or Nexus220

Network Configuration – Best Practices

Technical Bulletins

OMNIA Run as a Service fix for v4.x

Access Control

AmanoNet

AmanoNet Back up using IB Console

AmanoNet Minimum PC Requirements and Specifications

AmanoNet System Migration Notes

Archive Tagholders in AmanoNet

Archive Transactions in AmanoNet

AutoID IP Hardware in AmanoNet

How to move AmanoNet Access Control System from one PC to another (Firebird)

IDEMIA Sigma Lite Readers NOT compatible for use in AmanoNet or Nexus220

ImproNet/AmanoNet Database Backup: SQL

NOTICE! UPGRADE TO AMANONET 7.74 – EC2/400i NO LONGER AVAILABLE

Nexxus220

Change Default Password in Nexus220
Database Migration from Nexus220/IXP220 to OMNIA
How to fix a Java SE Binary Error in Nexus220 Software
How to get a copy of a database from Nexus220 Software
How to move Nexus220 to a different PC
IDEMIA Sigma Lite Readers NOT compatible for use in AmanoNet or Nexus220
Move Nexus220 Access Control System from one PC to another (Firebird)
Nexus220 Firmware Upgrade
Nexus220 Notifications Configuration/Email Configuration
Nexus220 The number of doors for this license has been exceeded
Nexus220 Web Reports Using Microsoft Edge
Reduce length of time on buzzer for readers in Nexus220

Omnia

Adding Widgets to the OMNIA Dashboard

Basic Trouble Shooting OMNIA

Batch Operations OMNIA

Change SYSDBA Password in OMNIA

Configuring Web Session Timeouts in OMINA

Create a Database for OMNIA 4.5 After Running the .iso

Create a Site Lockdown Input for OMNIA

Creating an Input on a Wiegand Reader Module to Generate a Lockdown/Emergency Mode For a Single APC Controller In OMNIA

Creating Operator Profiles

Creating Relay Actions I/O in OMNIA

Omnia Lite

Convert a Nexus Lite Database into OMNIA Lite Database

OMNIA LiTE Backup

PM Tronics Hardware

Amano Readers and Credentials

Change Modulation mode on XQT904 Quad Transmitter
How do I change Wiegand Output Mode on Amano readers?

Legacy Hardware

Factory Reset legacy Amano IP Cameras (sold prior to 2018)

Factory Reset Nexus220 controller

How do I factory reset the EC2 (400i) controller?

Setting IP on PMTronics Inc. Access Control Hardware

Partner Products

Partner Products

IDEMIA Sigma Lite Readers NOT compatible for use in AmanoNet or Nexus220

Setting Read Range on a Conekt Reader

Video Management Systems

Cathexis Video (Amano Vision)

Cathexis Video AV (AntiVirus Exceptions)

AmanoDVMS

Which AmanoDVMS ports need to be open on my firewall?

Vision

AmanoVision web access user name case sensitivity usage

ImproNet/AmanoNet Database Backup: SQL

ImproNet/AmanoNet Database Backup: SQL

How to make an ImproNet/AmanoNet SQL Database Backup

It is essential that regular backups are made and kept on removable media, or on a networked drive.

Storing backups on the local disk will not prevent data loss if the hard drive fails.

To Backup your ImproNet/AmanoNet SQL Database:

  • Open Sql Server Management Studio
  • Login using your Login Details

Windows Authentication should be sufficient unless the site has no allowed Windows Authentication
            Defaults: (Username: Sysdba, Password: masterkey). (Username: sa, Password:                                                    M@sterkey1)

  • Click on Connect
  • Expand the Database Folder by clicking on the + next to Databases
  • Right Click on the ImproNet/AmanoNet SQL Database, The Database name is DB400.                      DB400 > Tasks> Back Up…
  • Click on the Add… Button
  • Click on the … Button and Navigate to the following location: [Drive:] \ImproNet\database\Backups OR The location you want to store backups to
  • Enter a name for your backup with a suffix off: .Bak
  • Click on Ok,
  • Verify the Backup Name and Location. Click on the OK Button on Select Backup Destination Window
  • Select the Correct Path from above then Select OK.
  • The Backup will begin.
  • The backup is now complete and at the location you selected in a previous step.

Need further assistance?

Submit a Support Ticket

Submit a Support Ticket

FAQ

General

Can I initiate RS485 comms to a terminal from an existing IP terminal?

How to Select the Right Cable for the job

IDEMIA Sigma Lite Readers NOT compatible for use in AmanoNet or Nexus220

Network Configuration – Best Practices

Technical Bulletins

OMNIA Run as a Service fix for v4.x

Access Control

AmanoNet

AmanoNet Back up using IB Console

AmanoNet Minimum PC Requirements and Specifications

AmanoNet System Migration Notes

Archive Tagholders in AmanoNet

Archive Transactions in AmanoNet

AutoID IP Hardware in AmanoNet

How to move AmanoNet Access Control System from one PC to another (Firebird)

IDEMIA Sigma Lite Readers NOT compatible for use in AmanoNet or Nexus220

NOTICE! UPGRADE TO AMANONET 7.74 – EC2/400i NO LONGER AVAILABLE

Replace 400i Controller over Ethernet

Nexxus220

Change Default Password in Nexus220
Database Migration from Nexus220/IXP220 to OMNIA
How to fix a Java SE Binary Error in Nexus220 Software
How to get a copy of a database from Nexus220 Software
How to move Nexus220 to a different PC
IDEMIA Sigma Lite Readers NOT compatible for use in AmanoNet or Nexus220
Move Nexus220 Access Control System from one PC to another (Firebird)
Nexus220 Firmware Upgrade
Nexus220 Notifications Configuration/Email Configuration
Nexus220 The number of doors for this license has been exceeded
Nexus220 Web Reports Using Microsoft Edge
Reduce length of time on buzzer for readers in Nexus220

Omnia

Adding Widgets to the OMNIA Dashboard

Basic Trouble Shooting OMNIA

Batch Operations OMNIA

Change SYSDBA Password in OMNIA

Configuring Web Session Timeouts in OMINA

Create a Database for OMNIA 4.5 After Running the .iso

Create a Site Lockdown Input for OMNIA

Creating an Input on a Wiegand Reader Module to Generate a Lockdown/Emergency Mode For a Single APC Controller In OMNIA

Creating Operator Profiles

Creating Relay Actions I/O in OMNIA

Omnia Lite

Convert a Nexus Lite Database into OMNIA Lite Database

OMNIA LiTE Backup

PM Tronics Hardware

Amano Readers and Credentials

Change Modulation mode on XQT904 Quad Transmitter
How do I change Wiegand Output Mode on Amano readers?

Legacy Hardware

Factory Reset legacy Amano IP Cameras (sold prior to 2018)

Factory Reset Nexus220 controller

How do I factory reset the EC2 (400i) controller?

Setting IP on PMTronics Inc. Access Control Hardware

Partner Products

Partner Products

IDEMIA Sigma Lite Readers NOT compatible for use in AmanoNet or Nexus220

Setting Read Range on a Conekt Reader

Video Management Systems

Cathexis Video (Amano Vision)

Cathexis Video AV (AntiVirus Exceptions)

AmanoDVMS

Which AmanoDVMS ports need to be open on my firewall?

Vision

AmanoVision web access user name case sensitivity usage

IDEMIA Sigma Lite Readers NOT compatible for use in AmanoNet or Nexus220

IDEMIA Sigma Lite Readers are NOT compatible for use in AmanoNet or Nexus220

IDEMIA Sigma Lite Readers cannot be used in Nexus220 and AmanoNet (Legacy Mode)

IMPORTANT: Sigma Lite Firmware is no longer able to be downgraded into any legacy mode firmware

Sigma Lite Biometric readers are no longer able to be downgraded into Legacy Mode.

SIGMA Range
End of compatibility of Firmware: Legacy Morpho 2G and BioScrypt 4G


October 2021
In 2014, SIGMA range has introduced the 5G mode related to database structure and configurations with software, as a renewed basis to bring always more innovation and value to our customers. To provide continuity in Morpho (2G mode) and Bioscrypt (4G mode) installations and enable a smooth migration to SIGMA Range, IDEMIA has been developing specific firmware versions for the SIGMA range, called Legacy Firmware. This allows a new SIGMA terminal to be compatible with previous generations of terminals in 2G or 4G modes: when the administrator configures a SIGMA terminal in any of the Legacy firmware, it supports the database structures and configurations of the selected legacy terminal and software.
After 7 years providing and supporting migration, IDEMIA is now removing the Legacy Firmware from its portfolio. It will no longer be possible to install a Legacy firmware on a new SIGMA device starting January 2022.

Consequently, the following firmware versions will be discontinued on Jan 1st 2022:

  1. SIGMA Wide Firmware-upgrade-masigma_MA2G.4.9.8-prod.bin Firmware-upgrade masigma_MA4G.4.9.8-prod.bin
  2. SIGMA Lite Firmware-upgrade- malite_MA2G.4.9.8-prod.bin Firmware-upgrade- malite_MA4G.4.9.8-prod.bin
  3. SIGMA Lite+ Firmware-upgrade- malite-plus_MA2G.4.9.8-prod.bin Firmware-upgrade- malite-plus_MA4G.4.9.8-prod.bin
  4. SIGMA Extreme Firmware-upgrade-maxt_MA2G.4.9.8-prod.bin Firmware-upgrade-maxt_MA4G.4.9.8-prod.bin


In January 2022, the situation will be the following:
Will my Morpho or Bioscrypt legacy installation continue to work?
Yes – your installation will still be active as per current performances.
Is my Morpho or Bioscrypt legacy installation supported by IDEMIA?
No – As stated in the Maintenance and Support policy (October 2020), no more firmware nor software evolution will be performed. Support and repair activity is limited to legacy installations currently covered by a maintenance contract.

Will I be able to introduce a new SIGMA device into my BioScrypt legacy installation?
No – The SIGMA terminals purchased after January 2022 will not be compatible with the legacy Firmware versions
listed in the table above and Secure Admin software range is no more supported.

In case of failure of a SIGMA device loaded with a legacy firmware, will IDEMIA be able to repair it?
Yes – Please call Customer Care Center and mention which Legacy firmware is used. After repair, IDEMIA will return the device loaded with legacy firmware 4.9.8. From January 2024, repair feasibility will be evaluated case-by-base.

Need further assistance?

Submit a Support Ticket

Submit a Support Ticket

FAQ

General

Can I initiate RS485 comms to a terminal from an existing IP terminal?

How to Select the Right Cable for the job

Network Configuration – Best Practices

Technical Bulletins

OMNIA Run as a Service fix for v4.x

Access Control

AmanoNet

AmanoNet Back up using IB Console

AmanoNet Minimum PC Requirements and Specifications

AmanoNet System Migration Notes

Archive Tagholders in AmanoNet

Archive Transactions in AmanoNet

AutoID IP Hardware in AmanoNet

How to move AmanoNet Access Control System from one PC to another (Firebird)

ImproNet/AmanoNet Database Backup: SQL

NOTICE! UPGRADE TO AMANONET 7.74 – EC2/400i NO LONGER AVAILABLE

Replace 400i Controller over Ethernet

Nexxus220

Change Default Password in Nexus220
Database Migration from Nexus220/IXP220 to OMNIA
How to fix a Java SE Binary Error in Nexus220 Software
How to get a copy of a database from Nexus220 Software
How to move Nexus220 to a different PC
Move Nexus220 Access Control System from one PC to another (Firebird)
Nexus220 Firmware Upgrade
Nexus220 Notifications Configuration/Email Configuration
Nexus220 The number of doors for this license has been exceeded
Nexus220 Web Reports Using Microsoft Edge
Reduce length of time on buzzer for readers in Nexus220
Replacing Nexus220 Controller with APC Controller and Wiegand Reader Module

Omnia

Adding Widgets to the OMNIA Dashboard

Basic Trouble Shooting OMNIA

Batch Operations OMNIA

Change SYSDBA Password in OMNIA

Configuring Web Session Timeouts in OMINA

Create a Database for OMNIA 4.5 After Running the .iso

Create a Site Lockdown Input for OMNIA

Creating an Input on a Wiegand Reader Module to Generate a Lockdown/Emergency Mode For a Single APC Controller In OMNIA

Creating Operator Profiles

Creating Relay Actions I/O in OMNIA

Omnia Lite

Convert a Nexus Lite Database into OMNIA Lite Database

OMNIA LiTE Backup

PM Tronics Hardware

Amano Readers and Credentials

Change Modulation mode on XQT904 Quad Transmitter
How do I change Wiegand Output Mode on Amano readers?

Legacy Hardware

Factory Reset legacy Amano IP Cameras (sold prior to 2018)

Factory Reset Nexus220 controller

How do I factory reset the EC2 (400i) controller?

Setting IP on PMTronics Inc. Access Control Hardware

Partner Products

Partner Products

Setting Read Range on a Conekt Reader

Video Management Systems

Cathexis Video (Amano Vision)

Cathexis Video AV (AntiVirus Exceptions)

AmanoDVMS

Which AmanoDVMS ports need to be open on my firewall?

Vision

AmanoVision web access user name case sensitivity usage

AmanoNet Minimum PC Requirements and Specifications

AmanoNet Minimum PC Requirements and Specifications

Consider a number of factors when determining the correct PC specifications for different scenarios. The Database Server usually has the highest specification requirements.

Consider the following factors when specifying the Database Server:

  1. Number of doors (Terminals)
  2. Number of Tagholders supported by the System
  3. Number of client (Module) connections to the Database

Database Server

NOTE:  The number of client connections to the Database Server will affect the performance of the Database Server. Adjust the specification allowing for all client connections to perform Database tasks efficiently.

NOTE:   The volume of transactions per Site affects the performance of the Database Server. Adjust the specification allowing for rapid Database growth and Reports that work with large result sets.

NOTE:   This specification is for a dedicated Database Server only, without additional Software (third-party or AmanoNet Modules).

AMANONet Module PC’S

IMPORTANT:   Ensure that you install all AMANONet Modules on dedicated PC’s.

Standard Software Modules
(Engine, Access (including Card Designer), QuickTag, Visitor, Transaction Viewer, Alarms Client)
Optional Client Software Modules (Graphics Designer, Graphics Runtime)
Optional Server Software Modules (Impro Touch, Impro Vision)

NOTE:  The number of third-party devices that are used by each optional Server affects the performance of the System. Adjust the specification to allow the optional Servers to run at an optimal level.

NOTE:  The number of client connections to each optional Server affects the performance of the System.

Need further assistance?

Submit a Support Ticket

Submit a Support Ticket

FAQ

General

Can I initiate RS485 comms to a terminal from an existing IP terminal?

How to Select the Right Cable for the job

IDEMIA Sigma Lite Readers NOT compatible for use in AmanoNet or Nexus220

Network Configuration – Best Practices

Technical Bulletins

OMNIA Run as a Service fix for v4.x

Access Control

AmanoNet

AmanoNet Back up using IB Console

AmanoNet System Migration Notes

Archive Tagholders in AmanoNet

Archive Transactions in AmanoNet

AutoID IP Hardware in AmanoNet

How to move AmanoNet Access Control System from one PC to another (Firebird)

IDEMIA Sigma Lite Readers NOT compatible for use in AmanoNet or Nexus220

ImproNet/AmanoNet Database Backup: SQL

NOTICE! UPGRADE TO AMANONET 7.74 – EC2/400i NO LONGER AVAILABLE

Replace 400i Controller over Ethernet

Nexxus220

Change Default Password in Nexus220
Database Migration from Nexus220/IXP220 to OMNIA
How to fix a Java SE Binary Error in Nexus220 Software
How to get a copy of a database from Nexus220 Software
How to move Nexus220 to a different PC
IDEMIA Sigma Lite Readers NOT compatible for use in AmanoNet or Nexus220
Move Nexus220 Access Control System from one PC to another (Firebird)
Nexus220 Firmware Upgrade
Nexus220 Notifications Configuration/Email Configuration
Nexus220 The number of doors for this license has been exceeded
Nexus220 Web Reports Using Microsoft Edge
Reduce length of time on buzzer for readers in Nexus220

Omnia

Adding Widgets to the OMNIA Dashboard

Basic Trouble Shooting OMNIA

Batch Operations OMNIA

Change SYSDBA Password in OMNIA

Configuring Web Session Timeouts in OMINA

Create a Database for OMNIA 4.5 After Running the .iso

Create a Site Lockdown Input for OMNIA

Creating an Input on a Wiegand Reader Module to Generate a Lockdown/Emergency Mode For a Single APC Controller In OMNIA

Creating Operator Profiles

Creating Relay Actions I/O in OMNIA

Omnia Lite

Convert a Nexus Lite Database into OMNIA Lite Database

OMNIA LiTE Backup

PM Tronics Hardware

Amano Readers and Credentials

Change Modulation mode on XQT904 Quad Transmitter
How do I change Wiegand Output Mode on Amano readers?

Legacy Hardware

Factory Reset legacy Amano IP Cameras (sold prior to 2018)

Factory Reset Nexus220 controller

How do I factory reset the EC2 (400i) controller?

Setting IP on PMTronics Inc. Access Control Hardware

Partner Products

Partner Products

IDEMIA Sigma Lite Readers NOT compatible for use in AmanoNet or Nexus220

Setting Read Range on a Conekt Reader

Video Management Systems

Cathexis Video (Amano Vision)

Cathexis Video AV (AntiVirus Exceptions)

AmanoDVMS

Which AmanoDVMS ports need to be open on my firewall?

Vision

AmanoVision web access user name case sensitivity usage

  • Page 1
  • Page 2
  • Page 3
  • Go to Next Page »

PMT Security

Copyright © 2025 PMT Security, Inc. | All Rights Reserved