hdbob1340

Thanks for your replys so far. However, please look at my original post again. I CAN rout messages FROM my clx with the ENBT to my 1761-NET-ENI's and to their DF1 attached clx processors. What I haven't been able to do is route FROM a clx processor through DF1 to the 1761 NET-ENI to the clx with an ENBT. I DO have all the correct message tags that are required and I want to write to the ENBT processor. The 1761 NET-ENI has the IP address of the clx with the ENBT at node 49 as per NET-ENI manual (clx with ENBT's must be addressed at nodes 45-49). It seems like my message routing should just look like 2,49 but this does not work. Since I CAN message to the NET-ENI's FROM the the ENBT processor, maybe I should just do a read message instead of a write from the NET-ENI. I WOULD like to write to the ENBT if I can get this communication path figured out. Has anybody messaged to an ENBT from a NET-ENI like this and, if so, what is the communication path?

You are correct on all fronts.

Help Forum! I am having trouble with a communication path for a message originating in a compactlogix controller to a 1761 net-eni to compactlogix controller with a 1756 enbt built in ethernet port. I can message out of the latter controller to the net-eni controller (I have others with net-eni's) with this path: LocalENBT, 2, IP address, 3,1. My net-eni has the processor with the enbt addressed at node 49 with just the IP address. If I enter the path as 2,49 I get an error "messaging connection lost". What am I missing?

Thanks to all for the help! Everything is up and working now. Just a few comments from my experience that may help others that are new to the 1761-NET-ENI and Ethernet networking with PLC's: 1) You must use a crossover cable when connecting directly to an Ethernet device from your PC (Ethernet switches excluded) 2) You don't need the latest version of RSLinx to communicate with these devices, nor is Windows Vista an issue 3) Use the regular Ethernet driver in RSLinx; it allows you to see all of your devices, not just the NET-ENI 4) Don't use any dynamic addressing and change the IP address on your computer to a manually set address that is consistent with the addressing protocol of the rest of the system 5) I had to make up my own Ethernet cables for this project and it took a bit of practice. I was also set straight on the wire assignments by a good IT guy

Mercedes98, That helps alot actually. Could you explain readdressing from automatic to entering a manual address a little more in depth? Does the address need to relate to the configured address of the NET-ENI in some way?

I am in the process of setting up a small network of mostly CompactLogix processors and a couple of SLC’s and a couple of MicroLogix 1000’s. I will be doing a small amount of messaging between processors and eventually have a SCADA system. I want everything to go over Ethernet. I am having a heck of a time getting the 1761-NET-ENI’s working properly. I was able to use the configuration utility and assign IP addresses using my serial cable. Once this was done there were no more fault lights and everything seems ok. I can find the 1761-NET-ENI using the Ether/IP driver but if I click on it, it goes unresponsive. If I use the Ethernet driver, it shows up with the dreaded red X. I’ve tried going online with a SLC 5/03 using who’s active and the Ether/IP driver and again things go unresponsive when I click on the device. Lastly, I am using an older version of RSLinx Lite, 2.43.01.23 (CPR 6) and my laptop is running Vista. I haven’t had any problems with any other drivers or versions of RSLogix except help menus while running Vista. Anyone have any ideas? Thanks!