IP FORWARDING TO DH+
There is a feature in the newest ANC-100e firmware (01.02.17) to forward up to 5 IP addresses to specific DH+ nodes.
If you CAN NOT use a communication path, you may use this feature to communicate with 5 DH+ devices using an IP address for each one.
(If you have an outdated firmware, please let us know to send you the latest)
To make use of this feature, just log in to the web interface of the ANC-100e and go to the “HMI” tab
Then turn “ON” the rows that you will use and enter a different IP address in each row (These IP addresses must be unused in the Ethernet network) and enter the desired DH+ node for each IP address.
Finally, click “Apply” button and wait for the unit to reboot (5 seconds)
Now the ANC-100e will listen in these addresses and depending on the destination IP, it will forward the messages to the specified DH+ node
If can use connection paths in your Ethernet/IP Framework, here is some information about it:
About the communication method to the DH+ devices, you need to know a path when trying to send messages in and out. Remember our ANC-100e works as a Controllogix Gateway. Here is an extract from Ignition Inductive Automation user manual about DH+. If you want more information I can give you the link to it. But this is the information you may need to understand how to message a DH+ device from Ethernet using our product:
Allen Bradley Ethernet
Allen Bradley Connection Paths Explained
All of the Allen Bradley drivers have a Connection Path property that is used when the device uses a special Ethernet card (instead of having an Ethernet connection built in) or if you are using another device to act as a bridge. That is, connections to ControlLogix, CompactLogix, PLC-5, MicroLogix and SLC Allen-Bradley processors bridged through a ControlLogix Gateway require a connection path. The connection path is unique to your setup and is dependent on what modules the connection is being routed through. With there being nearly an endless number of ways to route your connection from device to device it is impossible to give an example of every possible connection path, but in general there is a pattern to how the connection path is specified.
Here is a basic outline for figuring out your connection path, but for more specific information on individual device types, see the individual connection pages.
Follow the Path
A connection path is exactly what it sounds like. It is a path that when followed will lead a processor residing in a numbered slot of a chassis somewhere on site. You merely have to follow the path and build the connection path as you go. The first connection point between Ignition and the device is a ControlLogix Ethernet module such as an ENET, ENBT or EN2T module. The slot number of this module doesn’t matter and there is no need to specify it in the connection path. The first entry in any connection path will be a 1, which specifies moving to the back plane. You then specify the slot of the module you wish to move to, followed by the port or channel of that module that you wish to exit through. Finally you specify the address of your entry point to the next module and the process starts all over again. This process may sound complicated at first but after some practice it will get easier.
Move to the backplane.
Specify the slot number of the module you are moving to.
Specify the exit port or channel.
Specify address of entry point (DH+ Station Number / ControlNet Address / IP Address of Ethernet module).
Move to the backplane.
Specify processor slot number OR the slot number of the module you wish to exit through.
Connection Path Entries for Different Module Types
How you specify your exit point from a module is slightly different depending on which module type you are using. You can only move in two directions once you are “in” a module: out to the back plane, or out through the module port/channel. Ethernet modules have ethernet ports and an IP address; ControlNet modules have ControlNet Ports and ControlNet addresses; DHRIO modules have channels and station numbers. Below is a list of different kinds of modules and what numbers you specify in the connection path when you are exiting or entering those modules. When in a module, an entry of 1 will always take you to the backplane.
ENET, ENBT, and EN2T:
1 = Backplane
2 = Ethernet Port
1 = Backplane
2 = ControlNet Port
1 = Backplane
2 = DH+ Channel A
3 = DH+ Channel B
DH+ Station Number (an octal value between 0-77)
You use these numbers to specify how to move out of the module, then you specify where you are moving to by either specifying the DH+ station number, ControlNet address, or the IP address of another Ethernet module. Your connection path will always be an even number of entries due to the fact that you always move in two steps: out of a module and then in to another module. So if your connection path ends up with an odd number of entries you have missed a step somewhere and you’ll have to go back and trace the path again.
As an example, lets have:
SLC5/04 on DH+ node 03
PLC5 on DH+ node 04
ANC-100e on DH+ node 77 octal
ANC-100e IP address: 192.168.0.230
Computer IP addres: 192.168.0.100
The connection path would be:
192.168.0.230, 1, 1, 2, ##
Where ## is the DH+ node number
And the “1, 1, 2” part will be always the same for our ANC-100e. The only variable will be the IP address and the DH+ node number.
To Connect with the SLC5/04 of the example: 192.168.0.230, 1, 1, 2, 03
To Connect with the PLC5 of the example: 192.168.0.230, 1, 1, 2, 04
Again, this example is coming from Ignition software, other software may represent the values in a different way. For instance:
192.168.0.230, 1, 1, A, ##
But the meaning is the same:
192.168.0.230 – IP address of the ANC-100e (working as ENET module)
1 – Go to backplane
1 – Go to Slot 1 (DHRIO module)
A – Go to Channel A
## – Target DH+ Node number