PMT Security

Advanced Access Control

Security Best Practices & Support

Network Configuration – Best Practices

Network Configuration – Best Practices

The world has changed in many ways and computing devices are becoming more mobile and data is rapidly moving into widely distributed environments.  It is clear and increasingly necessary that industries evolve to provide solutions utilizing private and public communications methods in a safe and secure way.  This ranges from large scale complex computer networks down to the simplest of IoT devices.   Somewhere in the middle of all this, lies Physical Access Control Systems (PACS) and Video Surveillance such as those offered by Amano McGann.

Before we begin, it is our recommendation that you consult a network engineer or other professional when configuring your network, especially in cases involving access communications outside your local area network. In general, network configuration lies outside the scope of the access control software and must be configured properly to allow our system to function.

Our products and systems do not have any problem communicating over LAN, WAN and VPN networks where routing is done properly.  Wherever possible, avoid the use of NAT rules, port forwarding, public IP addresses, and the like and instead connect our system components within the same LAN.  If you must connect in any a scenario other than one on a LAN, you may experience difficulty with installation and day to day communications, especially when using public IP Addresses.

If you choose to utilize a public IP addresses (anything other than RFC1918 addresses), NAT rules, port forwarding, public IP addresses, etc. please be aware that we will NOT be able to support or troubleshoot communications issues you experience.

Routers, managed switches, and other complex networking components must be set up by network professionals.  If you must implement complex networking configurations, please realize that you may be utilizing a bit of a trial and error to setup and communicate with various components in the system.  

Network Requirements Specification 

Communications

  • 100Mbps Ethernet Network Interface (between Hardware and Server/Clients)
  • LAN, VPN and most properly configured WANs are supported.
  • Static IP addresses are strongly recommended for all system components including the server(s).

NOTE: While technically possible, hardware connected via the Internet using NAT Translation, port forwarding, public IP (non RFC1918 addresses) is not supported.  Please use a Local LAN whenever possible.

Remote Client Connection

When using a remote client computer, you must be able to communicate with the server via IP address or DNS name on the assigned TCP Port (defaults listed below).  

Network Ports

Both TCP and UDP protocols are utilized and require the following ports be open for the listed components. 

Related Docs:

Address Allocation for Private Internets – https://tools.ietf.org/html/rfc1918

Need further assistance?

Submit a Support Ticket

Submit a Support Ticket

FAQ

Access Control

PM Tronics Hardware

Partner Products

Video Management Systems

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

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

Extending RS485 comms from an IP terminal to a remote terminal is not possible since you must always have one side of the RS485 loop connected back to a system controller. However, each RS485 connected device can daisy chain additional RS485 terminals together.

Whenever using RS485 communications, it is imperative to follow a few basic rules.  See the KB article on RS485 best practices for more details.

Need further assistance?

Submit a Support Ticket

Submit a Support Ticket

FAQ

Access Control

PM Tronics Hardware

Partner Products

Video Management Systems

How to Select the Right Cable for the job – RS485 Cabling

How to Select the Right Cable for the job – RS485 Cabling

Reliable access control and communication systems start with the right cabling.

Networks are highly sensitive to noise, signal loss, and poor installation practices. Choosing the correct cable type is critical to maintaining stable communication between controllers, readers, and field devices — especially in multi-door or multi-building environments.

This guide outlines PMT Security’s recommended RS485 cable characteristics to help reduce communication issues, improve long-term reliability, and support scalable security system designs.

Ensure the following when selecting cable: 

  • For the RS485 Comms Bus, use twisted-pair Mylar shielded cable only. 
  • For RS485 Ports, the individual cross-sectional area of the each conductor in the cable must not be less than 0.2 mm² (0.0003 in²). 
  • For RS485 Ports, the maximum permissible cable length is 1 000 m (3 281 ft). 
  • For RS232 Ports, the individual core cross-sectional area of the each conductor in the cable must not be less than 0.2 mm² (0.0003 in²). 
  • For RS232 Ports, the maximum permissible cable length is 25 m (82.02 ft). Cables must be: 
    • Neatly laid out 
    • Labelled correctly on both ends with cable markers 
    • Earthed correctly—connect the shield of the cable to the Earth terminal on the unit. In turn, connect the unit to a good Earth point. The earth must be a low resistance connection to Earth and not an arbitrary Earth connection. 

NOTE:  Connect the shield at one end of the cable only.

Keep cable joins to a minimum. However if necessary, connect cable joins using proper connecting strips. 

On shielded cables, connect the shield to ground (earth) as follows: 

  • Strip to the required length exposing the internal wires 
  • Untwist the excess length of metallic foil and plastic covering and remove the plastic 
  • Twist the metallic foil to form a wire tail 
  • Connect the shield lead to the Earth terminal. Earthing is at ONE end of the cable only.

Cable layout of an installation must be documented, and the documents placed under configuration control.

Daisy-chain formations are preferable to Star formations. 

Sites where transmission lines are long, or multiple star formations are used, may experience timeouts on certain ImproX Controllers or Terminals. These are caused by reflections on the RS485 lines. To solve the problem, it may be necessary to terminate the lines. Termination resistors are added at the end of a cable run only and not at every Terminal.

Need further assistance?

Submit a Support Ticket

Submit a Support Ticket

OMNIA Run as a Service fix for v4.x

OMNIA Run as a Service fix for v4.x

The OMNIA installation for version 4.x has a problem with the batch files that allow you to setup OMNIA to run as a service.

Please download these attached files and replace the batch files that are in the OMNIA installation folder.

Remember that you must shut down OMNIA, then run the correct batch file for your OS from an elevated command prompt when installing the new service.

Please call 727-786-1900 if you have any questions on this procedure.

Need further assistance?

Submit a Support Ticket

Submit a Support Ticket

FAQ

Access Control

PM Tronics Hardware

Partner Products

Video Management Systems