Created Date: February 11,2016

Created by: ADC_CommTeam01

To use the Explicit Message in the PSeries the Device you are trying to communicate with, in this case the ML1100 or SLC500, must have a place to set up the adapter the PSeries is communicating to. In the adapter setup in the AB controller you would set up the addresses you wish to be read or written to by the EtherNet/IP client, in this case the PSeries controller and it would give you the Class ID, Instance ID, & Attribute ID. I think some AB series have this option and some don't, you would have to check AB documentation. If you can't set the AB up as an adapter you cannot use P Series Explicit messaging to it. In the Pseries Explicit Message you are just entering in this information and entering in the location where you wish for the data to be placed in or written from in the PSeries Controller. Some AB controllers support a EtherNet/IP CIP layer called PCCC, this does not require setting up an adapter, but at this time the PSeries does not support the PCCC for EtherNet/IP, only I/O Messaging and Generic Explicit Messaging.

Created Date: February 12,2016

Created by: OkiePC

To the best of my knowledge, your only method to communicate with the SLC and Micrologix controllers will be Modbus.

The older Series A Micrologix 1100 and 1400 units do not support Modbus TCP.

As far as I know, all of them support Modbus RTU on their serial ports.

I am not sure about the limitations and capabilities of Modbus on the SLC serial and Ethernet ports.

If you can set up the port(s) on the Micrologix and SLC controllers as Modbus TCP (Ethernet port) or Slave protocol (serial), you can choose data files to correlate with Modbus addresses. This is the route I would take since the messaging flexibility in the P2K is superior to the A/B offering. If you set up a serial port in the A/B controller for Modbus Master, then the messaging will have to be initiated there, and you will have to live with the limitations of the Modbus message structure (reading or writing one data type per message).

Choosing Modbus for the Ethernet ports will not prevent you from continuing to communicate with it using "normal " EIP messages. The Ethernet port can handle both protocols...at least that is what I have read.

On the serial ports, it will be one protocol only. If you set it up for Modbus, there will not be any DF1 (or other) protocol functionality.

Please do post your findings if possible. I may set up a test myself. I have several Modbus devices that need to talk to each other and both types of controllers on hand. I don't have an immediate need to make the MIcrologix "talk " to the P2k, but it would be useful to know if it is possible and what all the ins and outs are.

Created Date: February 12,2016

Created by: jackson

The way I have done it is the other way around. Setup the P2 or P3 as the Adapter and use MSG instructions in the ML1100 to do Explicit Messaging to them. It is fairly straight forward in that direction.

The P2/3 Adapter setup gives you all the info you need to populate the fields of the MSG instruction (Service, Class, Instance and Attribute).

Created Date: February 09,2016

Created by: Biff Bates

I would like to eliminate all of the rockwell SLC500 and Micro1100 that are installed, a mix of about 40 processors.

To do that i need to be able to communicate to them using the P2k or P3k.

i have tried explicit messaging to the micro1100 so far and have only been able to get vendor ID, device type and product code out of it using Service ID-0Eh, Class ID-1h, Instance ID-1h and Attribute ID-1h

i need to read and write N7 and F8 information only

has anybody else succeeded in this type of communication?