adccommunitymod (AutomationDirect) asked a question.
Created Date: October 05,2016
Created By: Craymore
**** This post has been imported from our legacy forum. Information in this post may be outdated and links contained in the post may no longer work.****
Hello All; I am trying to figure out how to setup the communication between a CompactLogix plc and the P3K. I have the communication going one way, ie, I can retrieve tag data from the P3K in the CompactLogix using a message function (CIP Generic / Service function Get Attribute Single), but I can not send data. I am using the Set Attribute Single Service Type in the CIP Generic and getting an error that the Service Type is not supported. Has anyone done this before, I have read a lot of AB literature and they definitely don't like to explain how to connect to non-Rockwell products. Thanks in Advance -Allan
Created Date: October 05,2016
Created by: Craymore
Hello All;
I am trying to figure out how to setup the communication between a CompactLogix plc and the P3K. I have the communication going one way, ie, I can retrieve tag data from the P3K in the CompactLogix using a message function (CIP Generic / Service function Get Attribute Single), but I can not send data. I am using the Set Attribute Single Service Type in the CIP Generic and getting an error that the Service Type is not supported.
Has anyone done this before, I have read a lot of AB literature and they definitely don't like to explain how to connect to non-Rockwell products.
Thanks in Advance
-Allan
Created Date: October 05,2016
Created by: ADC_CommTeam02
Can you provide a screen shot from RSLogix 5000 of your message instruction configuration set up?
Created Date: October 05,2016
Created by: Craymore
Sure:
withing the screenshot:
Right image: Ethernet/ip adapter setup on the P3k
Left: module setup on the compact logix giving the communication path to the p3k
Far left: is the set attribute message that I am trying to use to update arrays on the p3k
n102948
Created Date: October 05,2016
Created by: ADC_CommTeam02
Change the instance ID to 102 in your message instruction.
Created Date: October 05,2016
Created by: Craymore
n102953 I have tried both 101 and 102. originally I had it as 102 but tried 101 because the get attribute single works on the 101 instance. When I change it to 102 I get the error.
Created Date: October 05,2016
Created by: Craymore
I figured out what I was doing wrong.
At the recommendation of checking the instance number I started looking at the arrays I was using in the PK3 in the Ethernet adapter setup and I had them backwards. I didn't realize that the Input data means input to the scanner (allen-Bradley) so I swapped those arrays and then double checked my setup in the controllogix Ethernet module. once I had the correct arrays setup the communication became automatic as it should with real time I/O. it turns out once it is setup properly you don't need to use the messaging functions. The compactlogix fills its I/O tags with the data at the RPI.
I am still not sure why the set message doesn't work but it isn't needed since I prefer implicit communication over explicit. I am going to leave it for now though.
Thanks for your help.
Created Date: October 06,2016
Created by: Tech_9282
Glad to hear your got it sorted out. The implicit (cyclic) messaging is really slick to use once it is setup. I am wondering if the error you were seeing with the explicit message block was because it looks like you had the instances already defined in a implicit configuration in the Ethernet I/O scanner tree.
Hopefully as per the road map they implement the tag based format for ethernet IP connections so you can implement communications with AB products in the typical produce/consume fashion. I am also eager to see a Ethernet IP adapter for the Protos X remote I/O blocks, which would make Remote I/O even more practical with the P2K/P3K systems.