Hi
In my system, i have a Clx as the 'main' plc, and it is swapping data with 2 Mlx and 1 SLC. I have my IO in the clx mapped to slc IO. From the main switch, i can see every plc and have gone online with them. my problem is i can't get the clx to see the mlx or slc. oh, they are mlx 1500's connected to eth by a 1761-net-eni module
1) do i need to somehow add the mlx's or eni to the clx io tree using a generic ethernet module? that way i could browse to it in the message path.
2) can i do the messaging from the clx or does it need to be initiated in the mlx?
once i have these answered, i'll have more specific questions about what to enter for the messaging, but the first step is getting them to see each other. i've done it over controlnet with clx to clx, but this seems a bit trickier.
thanks!
Full Version: Clx to MLx Messaging (Eth)
I have configured the ENI using the com port redirector and the eni config utility. but i read on the knowledge base that i have to configure my messages in there? does this sound correct? i have no internet in the field so i have to get this pretty well under wraps before going back out.
QUOTE(IamJon @ Jan 15 2009, 09:42 AM) [snapback]77736[/snapback]
1) do i need to somehow add the mlx's or eni to the clx io tree using a generic ethernet module? that way i could browse to it in the message path.
No, in fact you cannot add these to the I/O configuration if you wanted to.
QUOTE
2) can i do the messaging from the clx or does it need to be initiated in the mlx?
Yes. I would suggest, from lessons of BobLfoot, that you only use read messages. So the Micrologix and Controllogix will both have a read message in them
Controllogix - Setup an SLC Typed Read message pointing to the Data Table address you wish to read, specify the length and destination. The Communications tab is where you specify your path. It will be the name of your ENBT module, 2, then the IP Address. So if your ENBT is named myenbt and your IP Address is 123.123.123.123 your path will be myenbt,2,123.123.123.123
Micrologix - You will setup routing in the ENI from the Controllogix IP Address to a node on the serial side. This must be node 45-49 for a Controllogix and the Controllogix processor must reside in slot 0. From there your must map the tag to SLC/PLC5 tag, and setup a 500CPU Read message in the Micrologix pointing to the data address you specified in your mapping and the node address configured in the ENI
Running short on time, hope this helps
QUOTE(TWControls @ Jan 15 2009, 10:15 AM) [snapback]77739[/snapback]
QUOTE(IamJon @ Jan 15 2009, 09:42 AM) [snapback]77736[/snapback]
1) do i need to somehow add the mlx's or eni to the clx io tree using a generic ethernet module? that way i could browse to it in the message path.
No, in fact you cannot add these to the I/O configuration if you wanted to.
QUOTE
2) can i do the messaging from the clx or does it need to be initiated in the mlx?
Yes. I would suggest, from lessons of BobLfoot, that you only use read messages. So the Micrologix and Controllogix will both have a read message in them
Controllogix - Setup an SLC Typed Read message pointing to the Data Table address you wish to read, specify the length and destination. The Communications tab is where you specify your path. It will be the name of your ENBT module, 2, then the IP Address. So if your ENBT is named myenbt and your IP Address is 123.123.123.123 your path will be myenbt,2,123.123.123.123
Micrologix - You will setup routing in the ENI from the Controllogix IP Address to a node on the serial side. This must be node 45-49 for a Controllogix and the Controllogix processor must reside in slot 0. From there your must map the tag to SLC/PLC5 tag, and setup a 500CPU Read message in the Micrologix pointing to the data address you specified in your mapping and the node address configured in the ENI
Running short on time, hope this helps
The '2' in the path is the slot of the enbt correct? so if it's in slot 1, i should have a 1 there?
and yes, it should help
thanks.
No, the name myenbt identifies the slot. The 2 tells it which port to route the message through. 1 would send it back through the backplane. 2 sends it out the Ethernet port.
Paths are actually very easy to follow once you get the hang of them. Each path segment is made up of a Port and a Module.
So your message is starting out in the processor. There are two ways out of the processor. 1 which sends the message to the backplane or 2 which sends out the CH0 serial port. Then, in your case you will be going to slot 1. So your first path segment is "1,1". If your ENBT module is named myenbt then the "1,1" will automatically be replaced with "myenbt". Then you will want to go out the Ethernet port and to your destination IP Address. So to get out of the ENBT will will use a 2, then the IP Address which makes our full path "1,1,2,123,123,123,123" or again if your ENBT is named myenbt it will be "myenbt,2,123.123.123.123".
It makes for very easy routing across various networks. Just remember, you start at the processor and must pick a port to go out of the processor on. From there just alternate between port and module until you reach your message destination.
As a general rull of thumb your ports are:
1 - Backplane
2 - Primary communications port such as Ethernet, Devicenet, or Controlnet port on the front of processor
3 - Secondary communications port. The only one that comes to mind right now is the DHRIO module
Paths are actually very easy to follow once you get the hang of them. Each path segment is made up of a Port and a Module.
So your message is starting out in the processor. There are two ways out of the processor. 1 which sends the message to the backplane or 2 which sends out the CH0 serial port. Then, in your case you will be going to slot 1. So your first path segment is "1,1". If your ENBT module is named myenbt then the "1,1" will automatically be replaced with "myenbt". Then you will want to go out the Ethernet port and to your destination IP Address. So to get out of the ENBT will will use a 2, then the IP Address which makes our full path "1,1,2,123,123,123,123" or again if your ENBT is named myenbt it will be "myenbt,2,123.123.123.123".
It makes for very easy routing across various networks. Just remember, you start at the processor and must pick a port to go out of the processor on. From there just alternate between port and module until you reach your message destination.
As a general rull of thumb your ports are:
1 - Backplane
2 - Primary communications port such as Ethernet, Devicenet, or Controlnet port on the front of processor
3 - Secondary communications port. The only one that comes to mind right now is the DHRIO module
QUOTE(TWControls @ Jan 15 2009, 01:28 PM) [snapback]77748[/snapback]
As a general rull of thumb your ports are:
1 - Backplane
2 - Primary communications port such as Ethernet, Devicenet, or Controlnet port on the front of processor
3 - Secondary communications port. The only one that comes to mind right now is the DHRIO module
That is the main thing i needed. Thanks for the help and i'll try to remember to let you know how it went when I finish it up.
QUOTE(TWControls @ Jan 15 2009, 01:28 PM) [snapback]77748[/snapback]
No, the name myenbt identifies the slot. The 2 tells it which port to route the message through. 1 would send it back through the backplane. 2 sends it out the Ethernet port.
Paths are actually very easy to follow once you get the hang of them. Each path segment is made up of a Port and a Module.
So your message is starting out in the processor. There are two ways out of the processor. 1 which sends the message to the backplane or 2 which sends out the CH0 serial port. Then, in your case you will be going to slot 1. So your first path segment is "1,1". If your ENBT module is named myenbt then the "1,1" will automatically be replaced with "myenbt". Then you will want to go out the Ethernet port and to your destination IP Address. So to get out of the ENBT will will use a 2, then the IP Address which makes our full path "1,1,2,123,123,123,123" or again if your ENBT is named myenbt it will be "myenbt,2,123.123.123.123".
It makes for very easy routing across various networks. Just remember, you start at the processor and must pick a port to go out of the processor on. From there just alternate between port and module until you reach your message destination.
As a general rull of thumb your ports are:
1 - Backplane
2 - Primary communications port such as Ethernet, Devicenet, or Controlnet port on the front of processor
3 - Secondary communications port. The only one that comes to mind right now is the DHRIO module
Thanks for the help. I finally got out on site and things went smoothly. Nothing was wired for io testing but we could pass dates and times between processors.
Great! Thanks for letting us know how it turned out
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.