Controllogix - Data error [path segment error]

Ignition
1

Hi everyone,
we’re having problems with some variables in different Data types.
The complete error is the following:

ReadTagsRequest Time:
08Aug2017 08:55:53
Message:
Error reading item Program:MX3.MX3M2.DriveRef: status=0x04 [path segment error] , additional=[]com.digitalpetri.enip.cip.CipResponseException: status=0x04 [path segment error] , additional=[]
at com.digitalpetri.enip.logix.services.ReadTagService.decodeResponse(ReadTagService.java:63)
at com.digitalpetri.enip.logix.services.ReadTagService.decodeResponse(ReadTagService.java:13)
at com.digitalpetri.enip.cip.services.MultipleServicePacketService.decodeResponse(MultipleServicePacketService.java:70)
at com.digitalpetri.enip.cip.services.MultipleServicePacketService.decodeResponse(MultipleServicePacketService.java:18)
at com.digitalpetri.enip.cip.CipClient.lambda$invokeConnected$0(CipClient.java:69)
at java.util.concurrent.CompletableFuture.uniWhenComplete(Unknown Source)
at java.util.concurrent.CompletableFuture$UniWhenComplete.tryFire(Unknown Source)
at java.util.concurrent.CompletableFuture.postComplete(Unknown Source)
at java.util.concurrent.CompletableFuture.complete(Unknown Source)
at com.digitalpetri.enip.cip.CipClient$ConnectedDataHandler.itemsReceived(CipClient.java:249)
at com.digitalpetri.enip.cip.CipClient.onUnitDataReceived(CipClient.java:218)
at com.digitalpetri.enip.EtherNetIpClient.onChannelRead(EtherNetIpClient.java:168)
at com.digitalpetri.enip.EtherNetIpClient.access$500(EtherNetIpClient.java:34)
at com.digitalpetri.enip.EtherNetIpClient$EtherNetIpClientHandler.lambda$channelRead0$0(EtherNetIpClient.java:245)
at java.util.concurrent.ForkJoinTask$RunnableExecuteAction.exec(Unknown Source)
at java.util.concurrent.ForkJoinTask.doExec(Unknown Source)
at java.util.concurrent.ForkJoinPool$WorkQueue.runTask(Unknown Source)
at java.util.concurrent.ForkJoinPool.runWorker(Unknown Source)

The problem is on the “path segment”, but not on every value with the same parameters.
The unique difference between a variable with the problem and a variable without the problem is on “Data quality”.
The first is “Unknown” and it will be one of the causes of the problem.
The second is “Good” and on these variables the problem doesn’t exist.

We did also a verify between tag path on PLC and tag path on Ignition, and both have the same tag path, so in my opinion the problem isn’t on that point but I’m not sure.

Thanks for your time.
Stefano

2

Can you read other members of whatever type Program:MX3.MX3M2 is?

3

Program : MX3.MX3M2 is a denomination to indicate the PLC program to control the “Mixing Station 3” (MX3) and the second part is referred to the “second motor” (MX3M2) of the station.
The program is about mixing paint in tanks with a vertical axe motor.

4

Okay, but MX3M2 is an instance of a UDT. You didn’t answer my question: can you read other members of it?