EthenetIP Tag Read / CIP Error Extented status may be available / CIP error 0x4

[petite01]

Hello,

i am using Labview 2018 SP1 with Ethenet IP adapter toolkit 18.0. 

I am connected to an Ethernet IP device (Zumbach ODAC laserHead) at the adress 192.168.1.30.

but i did not succeed in reading any Tags. i always have the error 0x4 .

i assumed the spelling of the tag ( prefix.suffix) is not right

so I connected a Scheiner PLC to the device to load the .eds file and read the Tag, it works perfectly well.

I copied the tag name in the labview code ( Inputs.Measure_Dimension_1) , it is not working.

I attache the screen shot of the PLC interface and the labview code with the error.

if someone have any idea of what i should do or try ...

 

 

 

  

[Mike15437]

This thread help me solve a similar problem attempting to communicate to an Allen Bradley Micro820.  In the Micro820 I observer the following behaviors:

If I attempt to append the backplane slot and port to the network path I get error code and message:

-251723760

EthernetIP Tag Read DINT.vi;

Details: CIP Error - Extended status may be available

CIP Status: 0x1 (Connection failure)

CIP Extended Status: 0x311 (Port not available)

 If I accidently enter in the HMI IP address instead of the Controller I get:

-251723760

EthernetIP Tag Read DINT.vi;

Details: CIP Error - Extended status may be available

CIP Status: 0x8 (Service code unsupported)

However, if I eliminate the backplane slot and port and interface the HMI I get a different error message:

-251723760

EthernetIP Tag Read DINT.vi;

Details: CIP Error - Extended status may be available

CIP Status: 0x4 (Invalid segment type/IOI)

In summary, using only the IP address as the network path, allowed me to read the Micro820 data without errors!

Thanks for the clue that helped me resolve my issue!!!

[petite01]

i don't get it ; you still have the issue ' 0x4' . right ?

here i also always get the error, i never found out a solution to read the tags in the device , when it is so easy with a plc.

Emmanuel

[Mike15437]

Thankfully for me, I was able to read the Micro850 Tags without errors!  

My first mistake was accidently attempting to communication to the HMI instead of the PLC.  When communicating to the PLC, I was still getting an error, because I had appended the backplane slot and port number as part of the Network address (192.168.0.140,1,0).  When I removed the backplane and port number (192.168.0.140) I was able to read the PLC Tags, without errors! 

It seems like each controller behaves a little bit differently.  Did you try adding a backplane slot and port number to the Network path?

Good luck!