When all the on-site PLCs use the same static IP, how can secure subnet mapping achieve accurate maintenance and reliable PLC remote access?

In my conversations with machine builders, one topic comes up constantly: the power of standardization. To build machines efficiently and at scale, you create a master design—a template. The electrical drawings are identical, the cabinet layout is the same, and, crucially, the PLC is flashed with the exact same program and the exact same static IP address (say, 192.168.10.50) every single time. This is a brilliant manufacturing strategy.

But this production dream becomes a post-sales nightmare. You have 50 machines in the field at 30 different customer sites, and every single PLC has the IP address 192.168.10.50. A customer calls with an issue. You establish a VPN connection, but now what? How do you tell the network which specific machine you want to talk to? It's like trying to mail a letter to a country where every house has the same street address. Let's be clear: this "duplicate IP" problem has been a major barrier to efficient PLC remote access for years.

The very practice that makes you efficient in the factory—using a single, unchanging PLC configuration—cripples your ability to provide remote support. A standard VPN can get you onto the remote network, but it can't solve the fundamental problem of IP address conflicts.

This leaves you with two terrible options:

• Abandon Standardization: Create a unique IP scheme and a custom PLC configuration for every single machine you ship. This is a logistical nightmare that destroys your production efficiency, increases the risk of human error, and complicates documentation.
• Fly On-Site: Stick with the traditional, inefficient model of flying an engineer to the site for every software-related issue, costing you thousands of dollars and days of downtime for your customer.

Neither of these is a good choice. You need a third option that allows you to keep your standardized production methods while enabling precise and efficient PLC remote accesss.

This is where a purpose-built industrial VPN platform shows its value. RobustVPN, a core feature of our RCMS cloud, has a powerful function designed specifically for this problem: Subnet Mapping.

Instead of trying to change the PLC's "real" IP, we create a unique "virtual" IP for it that only exists within the VPN.

The process is managed centrally in RCMS and is remarkably straightforward:

1. On-Site Setup: Each machine is shipped with an embedded Robustel router connected to its PLC. The router is on the PLC's local network (e.g., the PLC is 192.168.10.50, the router is 192.168.10.1).
2. Central Mapping: In the RCMS platform, you create a mapping rule for each router.

• The router for Machine #001 is assigned the virtual subnet 10.10.1.0/24.
• The router for Machine #002 is assigned the virtual subnet 10.10.2.0/24.
• The router for Machine #157 is assigned the virtual subnet 10.10.157.0/24.

3. Remote Connection: The remote engineer connects their laptop to RobustVPN. Now, to access the PLC in Machine #157, they don't use its real IP. Instead, they point their PLC programming software to the unique virtual IP address: 10.10.157.50.

The RobustVPN platform acts as an intelligent traffic director. It sees the request for 10.10.157.50, knows that this address belongs to Machine #157's router, and forwards the traffic through the secure tunnel to that specific router. The router then translates the request to the PLC's real IP address, 192.168.10.50. The PLC responds, and the process happens in reverse.

To the engineer, it feels like they are on a massive, perfectly organized network where every machine has a unique, logical address.

This subnet mapping feature is the key that unlocks a hyper-efficient remote service model.

• Pinpoint Precision: You can connect to a specific machine with 100% certainty. This eliminates the catastrophic risk of accidentally connecting to and programming the wrong customer's machine.
• Keep Your Standardization: Your manufacturing team can continue to produce hundreds of identical machines with the same IP scheme, preserving production speed and simplicity. No more custom software loads for each order.
• Scalable Management: All IP mappings are managed in a single cloud interface. Onboarding a new machine for remote PLC maintenance is as simple as adding its router to RCMS and assigning the next virtual subnet. The system is built to handle tens of thousands of devices.
• Ironclad Security: The PLC’s real IP address is never exposed to the internet. Access is tightly controlled through the virtual IP, which can be enabled or disabled on-demand from the RCMS platform, ensuring the customer's OT network remains secure.

This approach has been proven to help machine builders cut annual travel expenses by 80% and resolve 90% of service tickets remotely.