Skip to main content
Version: 5.5

System requirements

Windows systems:​

  • .NET 8 (will be installed if necessary)
  • Computer performance: We recommend running server applications on appropriately equipped hardware (multi-core processor, at least 8 GB RAM, and SSD storage).
  • Operating system: We recommend Microsoft Windows Server operating systems. Client operating systems (64-bit) can also be used for testing purposes.

The following Windows versions are supported:

  • Windows Server 2016 x64
  • Windows Server 2019 x64
  • Windows Server 2022 x64
  • Windows Server 2025 x64
    • Windows 10 x64
  • Windows 10 IoT x64
  • Windows 11 x64
note

A web browser is required to display OPC Router 5 Management.

Supported web browsers are:

  • Google Chrome
  • Microsoft Edge

In the versions currently available for the release of OPC Router 5. (Minimum version 100)

note

Please check your local firewall to ensure that a connection to OPC Router 5 Management is possible. By default, OPC Router Management is installed on port 5000 (http://localhost:5000).

If this port is already in use, the next available port will be used (e.g., 5001).

warning

Attention: Productive operation with client operating systems: Due to technical limitations, inray strongly recommends operating with server operating systems.

note

Note: Client operating systems, such as Windows 10, can lead to undesirable behavior and unplanned system restarts due to unforeseen forced upgrades, resulting in incomplete recordings. Other technical limitations, such as the limited number of incoming TCP/IP connections, can lead to connection failures, especially in large projects.

Before installation, please check whether operating the OPC Router on a client operating system meets your requirements and is compatible with Microsoft's licensing rights.

warning

Caution: When using a virus scanner, we strongly recommend defining an exception for the OPC Router directory in the virus scanner settings. Virus scanners can affect system performance and, under certain circumstances, incorrectly classify OPC Router files as threats. Such false alarms can be triggered by updates to virus definitions and, in the worst case, lead to unexpected production downtime. By setting an exception for the OPC Router directory, you minimize the risk of performance losses and prevent false positives that could disrupt operations.

Docker systems:​

  • SingleCore 600MHz 64-bit CPU, architecture requirements vary depending on the image:
    • Runtime image (with integrated MongoDB):
      • x86_64 processors with AVX instruction set
      • ARM64 processors from ARMv8.2-A
  • Service image (without integrated MongoDB):
    • x86_64 processors with AVX instruction set
    • ARM/ARM64 processors from ARMv7
  • 512 MB RAM
  • 3 GB free hard disk space
tip

OPC Router uses an internal database to display data transfers in real time and historically.

For optimal performance, OPC Router should be run on a system with a multi-core CPU and at least 4 GB of RAM.