bcarbo (Customer) asked a question.
Productivity 3000 PLC to PLC communication
I am trying to setup PLC to PLC comms with 2 Productivity PLCS. I followed the video examples and I keep getting a 0x128 error.
- LRJ (Customer)
Uncheck the 'Include Run/Idle Header' option in the T->O (Input) tab in the E/IP client properties.
- PouchesInc (Customer)
If it is between two Productivity's why not use ProNet or the Network Write/Read instructions instead? You get better integration than an setting up as an EIP adapter.
- ADC Community_02 (Automationdirect.com)
+1 @PouchesInc (Customer) @bcarbo (Customer) please reference help topic P281 for additional details.
- bcarbo (Customer)
I was not aware of the Write/Read instructions. That was much easier. I am not familiar with ProNet.
- PouchesInc (Customer)
ProNet is pretty cool. The Do-More line also has the same feature but it is called something different. It is basically a protocol to communicate only within the same PLC family and to easily make data available to all PLCs on the network of that family.
If you are going just between 2 PLCs then Network Read and Write is probably better, but if you go between more than 2 PLCs then ProNet will likely be better.
You set it up in hardware config, and just make a publisher on whatever PLC you want to make data available from. Select an array of data you want available, a global ID number, and that's it. That array of tag data is now available to any other Productivity PLC on the network. All you have to do on any PLC you want that information on is make a subscriber and tell it what global ID you want to look at, and what array you will be placing the available data into.
Expand Post
- LWgreys (Customer)
From the P3000 user manual page 6-76.
Status Error: 0x0128 = Invalid Target to Originator Size
This error is returned when the Target to Originator (Input data) size
specified in the Forward Open does not match what is in Target.
Consult the documentation of the Adapter device to verify the required
size. Note that if the Run/Idle header is requested, it will add
4 additional bytes and must be accounted for in the Forward Open
calculation. The Productivity3000 CPU does not support a Run/Idle
header for the T -> O (Input) data. Some devices may publish the
size that they are looking for as an additional attribute (Unsigned
Integer 16 value) of the Extended Error Code. An array can be defined
for this field in order to view the extended error code attributes.
NOTE: This error may also be generated when a Connection Point
value that is invalid for IO Messaging (but valid for other cases
such as Explicit Messaging) is specified, such as 0. Please verify
if the Connection Point value is valid for IO Messaging in the target
device.
Expand Post
If it is between two Productivity's why not use ProNet or the Network Write/Read instructions instead? You get better integration than an setting up as an EIP adapter.