Remote Connection and Integration Guide for Hubbox Connect Series Devices
Remote Connection and Hubbox X2 Integration Guide
Hubbox X2 is an industrial IoT gateway device that allows you to access industrial field devices (PLC, HMI, Drives, etc.) securely, in isolation, and quickly. This guide details the connection hierarchy and technical requirements.
Engineer PC
Hubbox Desktop Client Software
Hubbox Connect X Series Devices
PLC / Machine / HMI
1. Operating Scenario
The remote connection process occurs in the following steps:
- The engineer opens the Hubbox Desktop Client application on their computer and authenticates.
- The system establishes an encrypted tunnel between the Engineer's PC and the cloud server.
- The Hubbox Connect X series devices in the field connect to this tunnel via their internet output.
- The engineer accesses their device via the local IP (e.g., 192.168.1.10) as if they were directly connected to the PLC with an Ethernet cable.
2. Technical IP Configuration
For the connection to be established, the IP address on the LAN side of the Hubbox device and the IP address of the PLC must be in the same subnet.
| Component | Example IP / Status | Subnet Mask | Note |
|---|---|---|---|
| Hubbox Connect X2 (LAN) | No need to change IP (Operates at L2 level.) | 255.255.255.0 | Gateway Device |
| Field PLC | 192.168.1.10 | 255.255.255.0 | Target Device |
| Engineer PC (Virtual Adapter) | 192.168.1.11 | 255.255.255.0 | VPN IP Range |
3. Security and Advantages
Unlike standard VPN solutions, the Hubbox solution provides end-to-end isolation:
- Firewall Friendly: No need to open inbound ports.
- Full Isolation: Only authorized users can access the relevant devices.
- Logged Activities: Who connected, when, and to which device can be reported.
Technical Tip: If the connection is established but you cannot "Ping" the PLC, ensure that the PLC is physically connected to the LAN port of your Hubbox Connect X series device.
Need further assistance?
Create Support Request
