Network Message Example

ML1100 (1763) to CompactLogix (1769L32E, L35E) via Ethernet

The following illustrates a ML1100 processor (CH1 Ethernet IP address 100.100.115.1) sending a message to a CompactLogix system (1769-L32E or 1769-L35E, CH1 Ethernet IP address 100.100.115.21) via Ethernet.

Ethernet cables and an Ethernet hub were used to connect the ML100 and CompactLogix Ethernet ports together. Software & Hardware info used for testing this application: RSLogix5000 ver 15.00.00 1769-L35E FRN 15.3.24 RSLogix500 ver 7.00.00 RSLinx ver 2.50.00.20 The following is the Ladder code used in the ML1100 processor to initiate the MSG. Using the DN and ER bits to unlatch the EN bit allows the MSG to run continuously and is the recommended style for both the ML and SLC processors for continuous operation.

The following is the Message Setup screen.

Notice that MultiHop option is automatically configured for Yes once Channel setting has been selected for 1 (Integral). Another thing to note is the Routing Information File which is required and unique to the ML1100 processor. The Routing Information File or RIF is a new file that the ML1100 controller uses to store Ethernet IP address routing information required to communicate on Ethernet. * Modifying, adding, or deleting any information in the RIF will cause unexpected MSG executing and communications issues. The following is the MultiHop setup screen.

The destination/target IP address of the CompactLogix L32E/L35E processor is entered in the To Address field and than using the Insert key on the computers keyboard the second line can be entered allowing the slot number of the processor to be entered. The CompactLogix processor will always reside as slot 0.

The following is the ML1100 Data File screen from RSLogix500.

Note that the MG10 file and the RI12 file are both present and are required for the operation of the Ethernet MSG instruction. The MG is required for the message execution and the RI for the Ethernet IP routing information. * Modifying, adding, or deleting any information in the RIF or MG will cause unexpected MSG executing and communications issues.

The following is a view of the tag(s) that were used for the application in the CompactLogix processor.

Note that the tag used to MSG to the ML1100 is of the INT type. The following is the CompactLogix PLC/SLC Mapping screen associating/linking the ML1100 N7 data file to the CompactLogix tag From_ML1100.

Since the CompactLogix processor doesnt support file structure equivalent to that of the ML family, PLC/SLC mapping is required to associate a particular file to a Logix INT type tag. If more than one word is required than an Array Dimension for Dim 0 could be increased to allow for the maximum total number of words to be messaged when selecting the tag data type. In the example above the N7 data file will be linked to the tag From_ML1100. PLC/SLC Mapping is configured in RSLogix5000 title bar menu under the Logix and than selecting Map PLC/SLC Messages.