View Full Version : MSG - Compact Logix to Micro1200 via ENI

February 2nd, 2011, 06:07 PM
I have a compact logix l32E. On the network, I have a Micrologix1200 connencted to a NET-ENI module to create ethernet connectivity.

In the CLX, I'm using a MSG instruction I am stuck on the path.

I have entered the following:

LocalENB, 2,
LocalENB, 2,,0,0
LocalENB, 2,,1,1

None of which have worked. Simply trying to X'fer N7:0 with 10 elements.

Err = 16#0001 with extended error 16#0204

Basically, MSG timing out because the path is incorrect.

Requesting assistnace with the proper path.



February 2nd, 2011, 06:14 PM
How is it connected? can you take screens shots of the settings for both?

February 2nd, 2011, 06:26 PM
It is connected via ethernet switch. In RSLinx, the ENI is showing proper configuration as the icon show the PLC. In addition, I can browse the data tables.

It's all about the path I believe. No screen shots right now, might be able to get some tonight or morning.

Ken Roach
February 2nd, 2011, 06:45 PM
When you're sending a MSG to a PLC, SLC, or MicroLogix device, the CIP path is "1,0" after the target IP. It's treating the controller as though it's in Slot 0.

Ken Roach
February 2nd, 2011, 06:47 PM
I'm not certain that 0x0204 is the error you'll get from an invalid path... that's usually a straightforward Timeout.

Try 1,0 as the last hop, then start thinking about the CIP Connection limit on the Net-ENI. It can handle up to 4 incoming CIP connections, so the RSLinx browse is one, and the MSG from the ControlLogix is another. If there are multiple PC's running RSWho with Autobrowse checked, they might be using up all the CIP connections of the Net-ENI.

You can determine the Net-ENI's CIP connection status via Telnet... there's an RA Knowledgebase document about that.

February 2nd, 2011, 06:59 PM
we might be on to something. I can ping the NET-ENI but I cannot Telnet to it.
In my statement above, I am incorrect about being connected via switch. We are connected via VPN to remote site (I"m offiste programming).

Two networks connected via VPN, 192.168.125x and 192.168.126.x

When I try to telnet is indicates that port 23 is not open. However, I can ping with no problem.


Ken Roach
February 2nd, 2011, 07:25 PM

Are the ControlLogix and the Net-ENI on the same 192.168.126.xxx subnet ?

Can you determine what Series letter the Net-ENI is, and what firmware revision ? I don't know if the built-in web page of the Net-ENI shows the firmware rev.

I've never had a problem connecting with Telnet to the Net-ENI.

We're having two different problems.... the MSG from the ControlLogix to the MicroLogix and now the curious Telnet failure.

Try using TCPING (http://www.elifulkerson.com/projects/tcping.php) to check the ability of your PC to connect to the Net-ENI on TCP Port 80, TCP port 23, and TCP Port 44818 (which is EtherNet/IP).

February 2nd, 2011, 07:53 PM
I can get to the web page ok.

Net-eni is series D
Firmware 03.21

The diagnostics page showed that two ethernet connections were made, both RSLinx on two seperate PC's. I have since taken them off and only one RSLinx instance has a connection. Still can't telnet....

Going to try the msg again now that he ethernet connection is down to 1

February 2nd, 2011, 07:59 PM
Great tool tcping, never used it.
It shows 80 and 44818 open but not 23.

I will dig on this

February 2nd, 2011, 08:10 PM
There is a setting on the ENI setup utility to select for compact logix routing. Does this come in to play here?

February 2nd, 2011, 08:10 PM
It currently is not selected.

February 2nd, 2011, 08:24 PM
I'm now connected directly to the network with the ENI and cannot access port 23 from telnet or tcping. Is there something in the setup or possibly a firmware revision needed here?

Ken Roach
February 2nd, 2011, 09:10 PM
Ah, my recollection is refreshed (http://rockwellautomation.custhelp.com/app/answers/detail/a_id/68548); Telnet is moved to TCP Port 1500, so "Telnet 1500" from the command prompt.

But that's not the real problem, the MSG instruction is.

If you can browse the Net-ENI with RSLinx, you know it's communicating and you're sure of the IP address.

You tried treating it as the endpoint of the CIP Path, right ? With no "1, 0" at the end of the path.

You definitely don't need to enable "CompactLogix Routing". Net-ENI to MicroLogix 1200 is the way they're supposed to work, from the first releases.

February 2nd, 2011, 09:34 PM
Yep, port 1500 works :)
confirmed on browsing and IP address.
I tried is as the endpoint (first try)
I am also able to configure the ENI via ethernet now that I have downloaded the software.

February 2nd, 2011, 09:38 PM
Communication settings in MSG instruction:
CIP selected

Configuration settings in MSG instruction:
Type: SLC Typed Read
Source: N7:0
Elements: 1
Dest. Element: WBPS_N7_0 (Type INT)

Consistenly returns Error: 16#00001 and Extend Error: 16#0204

enable MSG instructino and after about 30s it Errors.

Ken Roach
February 2nd, 2011, 11:27 PM
30 seconds is the standard CIP Connection timeout.

It really, truly, genuinely sounds like an honest-to-goodness IP addressing problem.

Are you certain that the two devices are on the same IP subnet ? Post the actual IP address and Subnet Mask of both the 1756-ENBT and the 1761-NET-ENI.

To do anything else you're going to need a mirror port or remote capture of the Ethernet traffic.

One more thing: The 1761-NET-ENI tool, for some reason, requires you use leading zeroes in the fields in which you place the octets of the IP address. It always interprets these as decimal values.

In any other notation, including the Windows command line and the CIP path field in RSLogix 5000, a leading zero in an IP address octet denotes that it's an Octal number, not a Decimal number and 80 is an invalid number in Octal.

Your postings show that the last octet is entered in RSLogix 5000 as "80" but I wanted to cover this little detail. It has always irritated me that the Net-ENI utility forces you to use an incorrect notation.

February 3rd, 2011, 08:37 PM
Problem fixed. The compact logix did not have the gateway address listed in it's processor port configuration for TCP/IP. Even though the network VPN could communicate, the PLC did not konw how to leave the network to cross over to the secondary side. Oversight but costly in time.

LocalENB, 2, was the proper path syntax.

Gateway is not an issue if all devices are on the same network as a lot of systems are. PLC was setup over a year ago and this information was left out, probably because the PLC was setup offsite.

Lesson learned!

Ken Roach
February 3rd, 2011, 09:15 PM
Thanks very much for posting your followup findings.

January 7th, 2017, 10:22 AM
i know this is a old thread but i am having the same issue. i tried to download the telnet tool but it appears to not be working on my computer. i am online with both devices currently. could that be taking up too many cip connections and causing the message to fail?