Each NET-ENI module has its own IP address which is what RSLinx is using to communicate with the SLC5/03’s. If I understand correctly you have two SLC5/03’s each with a NET-ENI connected to them via DF1 full duplex. I’m not really sure what you mean in your answer. So go ahead and set up separate areas of memory for your control block and your data payload and verify that you've configured the Net-ENI correctly on both sides, and let us know what you find. Can you describe in detail where that error message appears ?

RSLogix 500 doesn't know anything about IP addresses when you're using an SLC-5/03 controller, and there are only three error codes the Net-ENI can generate, none of which are specific to IP addresses. I'm not sure why you would get a message that says 'No IP Address Configured On Network'. If this is the only MSG that's outgoing, you should be OK.Ĥ. Remember that the Net-ENI has only a small number of TCP connections it can handle two incoming, two outgoing, and two either way. You need to have configured the IP address of the target device equivalent to DF1 Node 0 in the Net-ENI utility or by using a configuration message inside the SLC-5/03.Ĭonfiguring the DF1:IP table is described in the 1761-UM006 user manual for the 1761-NET-ENI on page 4-6 and in Chapter 5.ģ. Sending an outgoing message via a 1761-NET-ENI requires you to use the DF1 Address : IP Address table inside the Net-ENI. I typically do not use the same data file for my Control Blocks as for the actual data payloads, and I use separate data files for data I'm transmitting and data I expect to receive.Ģ. Your actual data payload must use different memory addresses. If you are planning to use N7:0 as the start of your Control Block, you need to reserve N7:0 through N7:13. The Control Block for a MSG instruction that uses the SLC-5/03 serial port is 14 Words long.

This is an intermediate difficulty programming challenge.

Rslogix 500 user manual