Slad (Customer) asked a question.
Communications between Micrologix and Click over Ethernet/IP.
Hi
Has anyone tried communications between Micrologix (1400 in my case) and Click over Ethernet/IP?
- Todd Dice (Customer)
No, but I would recommend setting up the Ethernet IP adapter in the Click, and have the Click software create the EDS file. This is only anecdotal evidence but I had a customer network a product of my design operating on a Click to a Micrologix. I sent them the EDS file and never heard back so I assume they had no problems.
- Slad (Customer)
Unfortunately micrologix controllers can’t be an eip client and no option of importing eds file in rslogix 500 as far as I know, I was thinking may be someone tried just using msg instructions.
- ADC TechnologyGroup_05 (AutomationDirect)
Whereas the MicroLogix 1400 cannot be and EtherNet/IP IO Messaging client, I believe that it can still be an EtherNet/IP Unconnected Explicit Messaging client. I am not an AB user, but I believe it supports this on Channel 1 with the use of MSG instructions. If this is true, then the MicroLogix 1400 can still target the CLICK CPU, targeting the same Assembly Instances and using the Get_Attribute_Single and Set_Attribute_Single services for reading Input data and writing Output data. You may need to reference the MicroLogix 1400 literature for details.
Expand Post - mikeexplorer (Customer)
I have been learning about MODBUS communication and I have been experimenting using a Micrologix 1400 and a Click PLC. I am using the COM1 on the Micrologix with the converter box for RS485.
- ADC TechnologyGroup_05 (AutomationDirect)
Configuring a MicroLogix 1400 to communicate with a CLICK CPU using EtherNet/IP Unconnected Explicit Messaging:
Two MSG Files should be created; one for the Get_Attribute_Single request (READ) and one for the Set_Attribute_Single request (WRITE). Two Extended Routing Information Files shoudl also be created for these requests.
The Class, Instance, and Attribute information for the READ request in the MSG File should match those of the Input Assembly in the CLICK EtherNet/IP Adapter Setup, as well as the requested data size.
The MultiHop setup should specify the CLICK's IP Address as the target.
The Class, Instance, and Attribute information for the WRITE request in the MSG File should match those of the Output Assembly in the CLICK EtherNet/IP Adapter Setup, as well as the requested data size.
The MultiHop setup should specify the CLICK's IP Address as the target.
Attached is a Wireshark capture showing these requests successfully being executed.
Expand Post
Configuring a MicroLogix 1400 to communicate with a CLICK CPU using EtherNet/IP Unconnected Explicit Messaging:
The Class, Instance, and Attribute information for the READ request in the MSG File should match those of the Input Assembly in the CLICK EtherNet/IP Adapter Setup, as well as the requested data size.
The MultiHop setup should specify the CLICK's IP Address as the target.
The Class, Instance, and Attribute information for the WRITE request in the MSG File should match those of the Output Assembly in the CLICK EtherNet/IP Adapter Setup, as well as the requested data size.
The MultiHop setup should specify the CLICK's IP Address as the target.
Attached is a Wireshark capture showing these requests successfully being executed.
ML1400_to_CLICK