Ethernet IP error with Rockwell Armorpoint I/O

[tstahl]

I am attempting to communicate between a PC and Rockwell Armorpoint I/O module (1738-AENT). I am using the Access Assembly Instance Data (Explicit) VI from the examples to test this. The get assembly instance returns an empty array. The set assembly instance produces:

Error -251723760 occurred at EthernetIP CIP Set Attribute Single.vi;
Details: CIP Error - Extended status may be available
CIP Status: 0x8 (Service code unsupported)

There is a third assembly that is used to configure the module. This also produces the same error when I try and write the configuration to that assembly. Rockwell technical support confirms the values I'm attempting to send, however they stopped support as they have not tested with and do not support National Instruments products.

[Aix-La-Chapelle]

Hi tshal,

Apologies in the delay in response. 

It looks like you are using the example project with the example VI for Explicit messaging to communicate with the Rockwall Armorpoint I/O module.  It looks that you are receiving a CIP error.  Rockwell has mentioned that what you are sending is valid.  The CIP error message typically pertains to something the device connected to the NI adapter sends back to us.  It would seem the service code being provided to the device is not valid.  Could you provide the data sheet for your device, as well as screenshots of the front panel for the example code.  Can you also provide a Wireshark capture of the data as well?  Thank you.

[tstahl]

Matt -

Attached is the manual for the Armorpoint and POINT I/O modules (same thing in a different package). Screenshot and Wireshark capture also attached.

Tim Stahl

[tstahl]

Rockwell technical support must have looked at the bytes being sent again. We recalculated the byte lengths and they were incorret. The correct values should have been 13 and 7 instead of 21 and 8. The correct values have not changed the errors or behavior.

[LewisL]

Hi Tim,

It's totally possible that an EIP adapter selectively supports CIP Get/Set Attribute Single (one of the many service codes out there) for a given brand/type.

I didn't spot explicit description regarding this information. Maybe this is not the claimer doc. (there is only a slight mention of Get Attribute Single being used on a particular class/attribute as a diagnostic measure, and nothing seems to be mentioned about the assembly attribute.) You might as well confirm with Rockwell whether this device supports assembly being accessed explicitly using CIP Get/Set Attribute Single.

From the capture, set is not supported, get is.

Also, NI EIP toolkit does not support configuration assembly. 

[sschwar2]

Has anything been found on this problem? I have a similar issue where I can't set the service code for the message. Any ideas how to set the service code on the CIP message? I'm using the NI CIP Get Attribute Single VI.

[tstahl]

We put a little PLC in the middle; this was the cheap and fast solution.

[sschwar2]

Wow, that's a huge bummer. I was really hoping to avoid this. Thanks for the response!