how to connect multiple machines with the same multiple IP addresses to internal netw

[biil2769]

When machine has only 1 IP, we hook up a wireless client and set a static IP. Works Fine

Alot of our newer machines have multiple IPs for PLC, HMI, Servo Drives, Vision Systems, ect.

what has happened is each machine has the same range.
Machine 1 has IPs 192.168.0.x
Machine 2 has IPs 192.168.0.x
Machine 3 has IPs 192.168.0.x


I'm looking for a solution to be able to add these machines to our network but without setting up a static IP for each machine and each device in the machine.

I have seen the netbiter device but we are trying to keep machines internal.

Any ideas would be much appreciated.

Thanks

 

[Paullys50]

You need a switch that can do NAT. Example 1783-NATR

 

[Helliana]

Check out the 9300-ENA from Rockwell. It was specifically designed for this purpose. IMO, it is easier to setup than any of the other NAT offerings from Rockwell.

 

[Christoff84]

Do these machines just have the same subnet 192,168.0.x, or do they have the exact same IPs?

If they are just the same subnet, you can add them to your network, assuming it's compatible with your network setup, or you may need a level 3 switch/router to go from 1 subnet to another.

 

[exabmorgan]

In particular the type of NAT you need is called 1 to 1 (1:1).
https://wiki.untangle.com/index.php/1:1_NAT
It allows a single hardware interface (typically called the WAN) on a router/firewall to have multiple IP addresses, then map over to the interfaces(s) (LAN side) with individual private space IP addresses.

One NAT router per machine. I did it with the free firewall/router software here:
http://m0n0.ch/wall/index.php
Loaded on your favorite embedded fanless PC (I used Soekris).

 

[Keystone]

Not sure what processor you are using but what we will do is put in two Ethernet cards. One on the 192.168.1.x for all the I/O, servos, etc and the second on a machine VLAN with a unique address so we can access the PLC & HMI. I does cost more but that way all our identical machines have the same IP address and you do not need BOOTP for you I/O devices you can just use the thumb wheels to set the last octet.

 

[robertmee]

Not sure what processor you are using but what we will do is put in two Ethernet cards. One on the 192.168.1.x for all the I/O, servos, etc and the second on a machine VLAN with a unique address so we can access the PLC & HMI. I does cost more but that way all our identical machines have the same IP address and you do not need BOOTP for you I/O devices you can just use the thumb wheels to set the last octet.

We do the same for all our designs....Machine network for devices pertinent to that PLC on one or more Enet modules, and a separate Enet module for the wide area network of all PLCs and HMIs. I can't imagine having all the local devices on a single wide area network....would be a major headache, and one malfunctioning AENT module takes down the entire plant. Bad design, IMO.

 

[biil2769]

Thanks for the Ideas, It looks like adding a NAT is an option to try.

For the future, I will recommend that a second Enet module be added for remote access.

 

[Helliana]

Thanks for the Ideas, It looks like adding a NAT is an option to try.

For the future, I will recommend that a second Enet module be added for remote access.

Depending on what PLCs you spec out, that is not an option. The L4 series CompactLogix that had multiple ethernet cards are outdated and cannot be flashed above V20. All the new 5370 controllers do not have a multiple ethernet cards available. Therefore, if you want the ability to use a firmware higher than version 20, you have to go the Controllogix 1756 route or use some type of NAT device.

 

[jdbrandt]

Thanks for the Ideas, It looks like adding a NAT is an option to try.

For the future, I will recommend that a second Enet module be added for remote access.

Hirschmann makes a device called the Eagle One Security Router, and it is a solid performer. (I've been to a site with dozens of them installed.)

 

[lostcontrol]

Machine level/IO traffic should never be on the same physical network as Admin.
As mentioned, the L1x series cannot have a 2nd Ethernet card, so we are hamstrung a wee bit.
But, a simple router that can do NAT solves the issue as mentioned already.
That's what Ive been doing anyways

 

[BAJ]

Not sure what processor you are using but what we will do is put in two Ethernet cards. One on the 192.168.1.x for all the I/O, servos, etc and the second on a machine VLAN with a unique address so we can access the PLC & HMI. I does cost more but that way all our identical machines have the same IP address and you do not need BOOTP for you I/O devices you can just use the thumb wheels to set the last octet.

+1 on this.

 

[BlueAltezza]

Red Lion's RAM 6021 is a cost effective network translator solution.