Technical Tips
Messaging in a MicroLogix 1100
This TechNote is an example of the Rockwell Automation Knowledgebase documents that are available to customers. Customers with a TechConnect Support contract will be able to access higher level TechNotes. If you would like to know more about TechConnect please contact your local authorised Rockwell Automation Distributor.
Configuring a message (MSG) instruction to communicate over Ethernet in MicroLogix 1100
Question:
How do I do a message (MSG) instruction in a MicrolLogix 1100 over Ethernet?
Answer:
Note:
This document assumes the user has a working knowledge of the proper programming of messages for the MicroLogix family of controllers. All MSG programming guidelines and techniques must be followed. Messaging for the MicroLogix 1100 is no different then for any other member of the MicroLogix family.
Explanation:
A new data table file is used for Ethernet messaging in the MicroLogix 1100. This new file stores all the routing and IP address information required to communicate on Ethernet. This “Routing Information File” or RIF is simply a file that the controller uses to store the Ethernet information entered into the Message (MSG) instruction.
Programmers and Users should not directly modify, add, or delete any information in the RIF. Doing so could cause MSG instruction executing and communications issues.
Step 1:
Add a MSG to your program. Select the MG file to use and then proceed into the setup screen to complete the MSG configuration.
Step 2 (This Controller):
- To communicate via Ethernet first select the correct communications Channel. The Ethernet channel for a MicroLogix 1100 is “ 1 (Integral)”.
- Select a MSG read or write for the communication command.
- Enter the data table address of this MicroLogix 1100 that you wish to MSG to/from.
- Enter the size in elements of the data you will read or write.
- Enter the Data Table address for the target device.
Note:
Only after selecting channel 1 will the Target Device area of the set-up screen change to reveal the “Routing Information File” data field.
- In the Routing Information File data field enter the address of the RIF data table file you wish to use.
Enter RIx:y, where x is the file number and y is the element number.
- For this example a RIF file was created as File #10 and we will use element 0 for this example.
Enter RI10:0 for the Routing Information File.
RSLogix 500 v7.0 will create the RIF file for you once correct information is entered into the RIF data field.
Each RI element uses up 20 data table words and each Ethernet MSG instruction needs its own RIx:y element, even if its routing to the same device as another MSG instruction.
See below for steps 2, 3 & 4
Step 5 (Final Step):
- Select the “MultiHop” tab on the MSG setup screen.
- Enter the IP address of the destination controller or device.
How to configure the route in the Multihop tab to a MSG to a ControlLogix, FlexLogix or CompactLogix controller:
- Enter the IP address if messaging to another Micro 1100, an ENI/ENIW, a SLC 5/05 or a PLC-5E.
- If routing to a ControlLogix, FlexLogix or CompactLogix controller, a second line must be inserted by pressing "Insert" on the keyboard.
Select "ControlLogix Backplane" and enter the controller backplane slot number (always 0 for FlexLogix and CompactLogix).
ROCKWELL AUTOMATION DOES NOT WARRANT THE COMPLETENESS, TIMELINESS OR ACCURACY OF ANY OF THE DATA CONTAINED IN THIS WEB SITE AND MAY MAKE CHANGES THERETO AT ANY TIME IN ITS SOLE DISCRETION WITHOUT NOTICE. FURTHER, ALL INFORMATION CONVEYED HEREBY IS PROVIDED TO USERS "AS IS." IN NO EVENT SHALL ROCKWELL BE LIABLE FOR ANY DAMAGES OF ANY KIND INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS PROFIT OR DAMAGE, EVEN IF ROCKWELL AUTOMATION HAVE BEEN ADVISED ON THE POSSIBILITY OF SUCH DAMAGES.
ROCKWELL AUTOMATION DISCLAIMS ALL WARRANTIES WHETHER EXPRESSED OR IMPLIED IN RESPECT OF THE INFORMATION (INCLUDING SOFTWARE) PROVIDED HEREBY, INCLUDING THE IMPLIED WARRANTIES OF FITNESS FOR A PARTICULAR PURPOSE, MERCHANTABILITY, AND NON-INFRINGEMENT. Note that certain jurisdictions do not countenance the exclusion of implied warranties; thus, this disclaimer may not apply to you.
