Allen Bradley Networking A control system to the Plant

Been looking through some of the Networking questions and wondered how this could get done. I know enough to get through some issues but stumped on how and what I need to ask.

History: The original system was Allen Bradley DH+ that is being converted to Ethernet. The computer in question is running Factorytalk V7.0 and is currently accessible by other plant personnel that are manipulating the Recipes and "pulling" status reports.

I have figured out that all I need to do is change the RSLINX OPC server to pull data from the new 5/05 processor (was 5/04). This however means that the IP addresses would be part of the factory architecture, not desirable.

So the machine ethernet will be on one IP network while leaving the factory IP address alone.

So is it as simple as adding a NIC card and adding the Machine network to that and allowing the existing network to continue functioning. Or do I add a router to manage the two IP addresses. Or do I need a managed switch (never used one).

If it is a router then how does this configured is this a basic thing for an IT specialist.


Does the second NIC card create entry points for the second possible IP address ??

I have included a hand drawing of the system

It's as simple as adding a NIC card and giving it a static IP address on the same subnet as the PLCs (192.168.1.x).

Because the enterprise network is a totally different IP subnet (10.x.y.z), the FactoryTalk computer will have no trouble differentiating between them.

I'm online with a ControlLogix doing exactly that sort of thing right now, while still connected to my office network (and the Internet, obviously).

+1 for Ken. It works well while keeping everything separate.

You can even use the same NIC and give it a secondary IP. Look in advanced settings of TCP/IP Properties

Just be sure that your IT network doesn't use those IP addresses anywhere. We are a rather large company and we have 10.x.x.x, 172.x.x.x and 192.168.x.x on our office network, and they are all routable, so adding something like this machine setup, I'd have to be very careful not to duplicate an IP already in use somewhere else which would cause a conflict.