System Requirements
Windows Systems:
-
.NET 8 (May be installed automatically)
-
System requirements: We recommend running server applications on appropriately equipped hardware (multi-core processor, at least 8 GB of RAM, and SSD storage).
-
CPU with AVX2 support
-
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
A web browser is required to view the OPC Router 5 Management interface.
Supported web browsers are:
- Google Chrome
- Microsoft Edge
In the versions currently available at the time of the OPC Router 5 release. (Min. Version 100)
Please check your local firewall to ensure 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)
Attention: Production operation with client operating systems: Due to technical limitations, inray strongly recommends operating with server operating systems.
Note: Client operating systems, such as Windows 10, can lead to undesirable behavior and unplanned system reboots due to unforeseen forced upgrades, resulting in incomplete logs. Additional technical limitations, such as the limited number of incoming TCP/IP connections, can lead to connection failures, especially in large-scale projects.
Please verify before installation whether running the OPC Router on a client operating system meets your requirements and is compatible with Microsoft’s licensing terms.
Warning: When using an antivirus scanner, we strongly recommend defining an exception for the OPC Router directory in the antivirus scanner’s settings. Virus scanners can impair system performance and, under certain circumstances, may incorrectly classify OPC Router files as threats. Such false positives 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 degradation and prevent false positives that could disrupt operations.
Docker Systems:
- Single-core 600 MHz 64-bit CPU; architectural requirements vary depending on the image:
- Runtime Image (with integrated MongoDB):
- x86_64 processors with AVX2 instruction set
- ARM64 processors starting with ARMv8.2-A
- Service Image (without integrated MongoDB):
- x86_64 processors with AVX2 instruction set
- ARM/ARM64 processors starting with ARMv7
- Runtime Image (with integrated MongoDB):
- 512 MB RAM
- 3 GB free hard disk space
The OPC Router uses an internal database to display data transfers in real time and historically.
For optimal performance, the OPC Router should be run on a system with a multi-core CPU and at least 4 GB of RAM.