GBolin1972
Member
This is my first post on ANY forum and following the first private message I received I am posting this here so bear with me.
I have been working on making our new Productivity Family PLCs talk using EtherNet/IP to our Allen-Bradley Micrologix 1100, and 1400 PLCs.
Up to this point, I have not seen any successful information on this, so when I managed to get some success I figured I should share it. I am hoping this doesn't open up any IP rights' can of worms and I don't know how to tell but I share this to at least help fellow integrators and so I also being cautious with this.
I was able to setup a Productivity 2000 processor and have it read N7 and other files on several (10) ML1100s and 1400s using the Productivity as a client.
First setup, the Micrologix family plc as EtherNet/IP generic client using the default port 44818, and the applicable IPv4 address. I used a structure for the parameters.
Next setup an EMSG Instruction. Set it to the correct device name created above. Set the connection to "Unconnected MSG" and the service to "Generic". You should now have a Service ID of "75 dec, 0x4b". Next set the Class ID to "103 dec, 0x67". Do not use the Attribute ID. Finally, Set the Instance ID to "1 dec, 0x1". Most of this I discovered using packet/frame analysis with Wireshark.
The next thing you need to do is enable input and output. Depending on what you are needing to do the size of the data Arrays will vary. I will tackle a protected read with three address fields so I will need an output or "Command" array that is one row and 17 columns and is typed as an 8-bit Integer, 1 dimension array.
The initial values of this array are basically the same as the DF-1 commands (See Rockwell Publication 1770-6.5.16 of October 1996 page 7-17) However there is a header that must be added.
At this point I used another project called EtherNet/IP Explorer authored by Frederic Chaxel to find out the EtherNet/IP Identity parameters from the Productivity processor to help create the command string.
Pausing here depending on if I have done everything properly thus far (awaiting moderator feedback) I will post the structure of the input and output arrays and hopefully move this a proper thread as they are the key to this.
See Communicating with RA Products Using EtherNet/IP Explicit Messaging (Rev. 1.2) for help if turns out you need to proceed on your own.
I have been working on making our new Productivity Family PLCs talk using EtherNet/IP to our Allen-Bradley Micrologix 1100, and 1400 PLCs.
Up to this point, I have not seen any successful information on this, so when I managed to get some success I figured I should share it. I am hoping this doesn't open up any IP rights' can of worms and I don't know how to tell but I share this to at least help fellow integrators and so I also being cautious with this.
I was able to setup a Productivity 2000 processor and have it read N7 and other files on several (10) ML1100s and 1400s using the Productivity as a client.
First setup, the Micrologix family plc as EtherNet/IP generic client using the default port 44818, and the applicable IPv4 address. I used a structure for the parameters.
Next setup an EMSG Instruction. Set it to the correct device name created above. Set the connection to "Unconnected MSG" and the service to "Generic". You should now have a Service ID of "75 dec, 0x4b". Next set the Class ID to "103 dec, 0x67". Do not use the Attribute ID. Finally, Set the Instance ID to "1 dec, 0x1". Most of this I discovered using packet/frame analysis with Wireshark.
The next thing you need to do is enable input and output. Depending on what you are needing to do the size of the data Arrays will vary. I will tackle a protected read with three address fields so I will need an output or "Command" array that is one row and 17 columns and is typed as an 8-bit Integer, 1 dimension array.
The initial values of this array are basically the same as the DF-1 commands (See Rockwell Publication 1770-6.5.16 of October 1996 page 7-17) However there is a header that must be added.
At this point I used another project called EtherNet/IP Explorer authored by Frederic Chaxel to find out the EtherNet/IP Identity parameters from the Productivity processor to help create the command string.
Pausing here depending on if I have done everything properly thus far (awaiting moderator feedback) I will post the structure of the input and output arrays and hopefully move this a proper thread as they are the key to this.
See Communicating with RA Products Using EtherNet/IP Explicit Messaging (Rev. 1.2) for help if turns out you need to proceed on your own.