Re: CIP Path
You should not attempt to put the MicroLogix 1100 into the I/O tree of the ControlLogix. The MicroLogix 1100 does not support cyclic I/O connections and the ControlLogix will be waste connection resources attempting to create one if you try to put the MicroLogix 1100 into the I/O tree.
Instead, you create the CIP Path manually, following the descriptions in the online Help for the MSG instruction.
I've explained this many times before but I'll re-explain it briefly here:
CIP Paths are composed of pairs of values: one Port number, and one Address number.
The most important Port numbers are Port 1 (the ControlLogix backplane or CompactLogix virtual backplane) and Port 2 (the network port of any module).
Addresses can be IP addresses, Slot numbers, or nodes on a ControlNet, DeviceNet, DH+, DH485, or DF1 network.
A good example of the CIP Path between a ControlLogix and a MicroLogix 1100 would be:
"1, 3, 2, 192.168.1.10"
In that example, the message goes from the CPU to the ControlLogix backplane (1), then to a 1756-ENBT module in Slot 3.
Then, the message goes out the Ethernet port (2) of the 1756-ENBT and over the IP network to the MicroLogix at IP address 192.168.1.10.
If you have a named 1756-ENBT in your I/O tree, the ENBT's name will be automatically substituted for the "1, 3", so the Path will read like "Scanner_ENBT, 2, 192.168.1.10".