Connect different controllers for remote access and data
Last updated on 22 September 2026
A test rig, logistics installation or special-purpose machine does not always fit one standard solution. A ServiceGate provides a common foundation for access and data logging. With unusual equipment, a useful integration starts with the interfaces and data actually available.
Access
Reach only the agreed controller.
Data
Read selected measurements.
Configuration
Validate the integration before use.
Remote Engineer · Knowledge base
What problem does this address?
For a mixed installation, you do not want a separate access process and dashboard for every brand. That does not require replacing all controllers, but it does require careful design. Identify what you want to operate, what you only want to read and what must remain outside the remote connection.
Brands, controllers and protocols
Omron NX102: assess OPC UA data
Omron specifies an OPC UA server interface for the NX102. In a mixed installation, investigate which exposed variables are useful. EtherNet/IP or EtherCAT availability does not mean a logger automatically reads all process data. Select the data interface deliberately.
Beckhoff TwinCAT: separate IP, ADS and the data model
Beckhoff documents OPC UA data through configured variables and ADS routes. When combining industrial PCs and other controllers, specify where the OPC UA server runs and which systems it exposes. VPN reachability alone does not configure variables or trust relationships.
ABB AC500: Modbus TCP as an agreed interface
ABB documents Modbus TCP in AC500 processors. A configured server and register map can expose selected data. Explicitly check read and write functions: dashboard access does not need to grant permission to modify the controller.
Connecting the ServiceGate
Connect the ServiceGate to the selected network segment and test one device first. Configure suitable service access and a small validated dataset. If there is no useful standard interface, assess a gateway, local application or custom protocol. A controller running your own software may suit this approach, but only after reviewing documentation, licensing and maintainability.
From a connection to useful insight
Example setup: a test rig combines controller measurements with industrial-PC status. A shared dashboard makes the relationship visible, while users access only their own location. Future AI or predictive maintenance additionally requires representative historical data and reliable fault labels. A connection alone does not deliver a predictive model.
Remote access and data logging, with clear boundaries
All ServiceGate routers support remote access and data logging/monitoring. The actual integration depends on model, firmware, interface and configuration. With VPN, your computer connects to the authorised location; configured VNC, RDP, HTTP or HTTPS services provide another access route through the portal. For logging, configure the protocol, data points and destination. The router receives that configuration and forwards data to the relevant service. Then configure dashboards, alarms and events. A named brand is a technical example, not a statement of certification, partnership or support for every model.
Permissions and traceable connections
Assign routers to locations and grant users or groups only the permissions they need. The portal shows who connected to which location. This records connections, not automatically every action inside the machine. For audit purposes, also define retention periods and any additional log sources. Agree a firewall profile for each customer or location, such as deny by default with explicit exceptions. Segmentation does not replace controller and machine security updates.
What do we need to assess your integration?
- Brand, exact model, firmware and installed software licences.
- Network diagram, IP addresses, interfaces and the owner’s approval.
- Required service tasks and the people who may access the installation.
- Measurements with register or object lists, units and collection intervals.
- Requirements for alarms, retention and any on-site logging during connection loss.
Remote Engineer has worked on remote access and controller solutions since 2008. Share your documentation and application with our team. We assess what is standard and where configuration or custom development is needed. Contact us for pricing and a suitable proposal.
Continue with your application
Sources and scope
Manufacturer documentation consulted on 22 September 2026. The examples describe possible architectures, not completed integration tests or customer results. Always check the exact model’s documentation before implementation. Trademarks belong to their respective owners.
All guides for this sector
This knowledge-base route concerns technical installations on luxury yachts. Course and speed operation are excluded from the remote-access design.
In this article
