Description

Learn how to connect to a ControlLogix through another ControlLogix Gateway using ENBT.

Video recorded using: Ignition 8.1

Transcript

(open in window)

[00:00] In this lesson, I'll demonstrate how to connect to an Allen-Bradley ControlLogix PLC through another ControlLogix gateway using ENBT. This is important when you have PLCs on two different subnets and Ignition is only on one of those subnets. By chaining the PLCs together, Ignition will be able to talk to both PLCs at the same time. Before getting started, I'd like to walk through a diagram of an example setup. From Ignition, this routes into the first ControlLogix PLC through an ENBT module. Then it goes out a separate ENBT module and into a second ControlLogix PLC, and then goes to its processor. We can tell Ignition how to navigate this with a connection path. Connection paths will be unique to a setup, so let's look at a table that describes how to build one and run through each part. In the example, the first number in the connection path is always going to be a one, and that means to move to the back plane of the first device. The second number is going to be the slot number of the module that we want to move to.

[01:04] This example has another ENBT module in slot number three. So the second number in the connection path is a three. The third number is the exit port or the channel of that module. In this case, the ethernet port is port two. The fourth number is going to depend on the module we're connecting to and the target PLC. This will either be a ControlNet address, a DH+ station number, or in the case of this lesson, an IP address of an ENBT module. The IP address here is "192.1.68.0.56". The fifth number is going to be one again to move to the back plane of the second device. And finally, the sixth number is going to be the processor number or the slot number of the module to move to. In this example, we want to connect to the processor in slot zero. Now that we've walked through building a connection path, I'll show you what it actually looks like to do this in Ignition. I'll start in the config section of my gateway webpage, and I'll scroll down to OPC UA and click on device connections and create a new connection.

[02:04] The PLC that I want to connect to is a ControlLogix on a firmware version greater than 21. So I'll choose the Logix driver. I'll need to give the connection a name, so I'll just call mine ControlLogix ENBT. Next, I need to specify the host name or IP address of the ControlLogix gateway. So if we look back at that example diagram, this would be the first PLC. Then I'm gonna scroll all the way down to the connection path property. My path is gonna look a little different than the example we looked at earlier, but it's built in the exact same way. My first number is going to be a one to move to the back plane of my gateway. Then my ENBT module is in slot number two. The ethernet exit port is port two. Then the fourth number is the IP address of the ENBT module for the second device, which in my case is 10.25.4.65 and then I need to move to the back plane of the second device, which means I put a one and finally, I'll move to the processor in slot zero. Now that I have my specific connection path configured, I can click create new device.

[03:07] Once my device status says connected, I can confirm I'm getting values by connecting to the OPC quick client, and I'll find my device and I can start seeing my tags.

You are editing this transcript.

Make any corrections to improve this transcript. We'll review any changes before posting them.