# CompactLogix v32 connectivity lost

**URL:** <https://forum.inductiveautomation.com/t/compactlogix-v32-connectivity-lost/42839>\
**Category:** Ignition\
**Tags:** ignition79, scripting\
**Created:** [February 1, 2021, 7:46pm UTC](https://forum.inductiveautomation.com/t/compactlogix-v32-connectivity-lost/42839 "2021-02-01T19:46:22Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![AIO](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/aio/32/87549_2.png) [@AIO](https://forum.inductiveautomation.com/u/AIO)\
**Post date:** [February 1, 2021, 7:46pm UTC](https://forum.inductiveautomation.com/t/compactlogix-v32-connectivity-lost/42839/1 "2021-02-01T19:46:22Z")

</div>

Hi folks,

Ignition 7.9.6

We’ve got a v32 5069 processor that’s been running and connected for several months with no issues. Over the weekend, it seems to have lost connectivity to Ignition. We’ve power cycled the device, restarted the logix driver, it just won’t connect properly.

In the gateway, it shows as “Connected,” but I cannot view the details.

 ![Ignition_SS1](https://us1.discourse-cdn.com/inductiveautomation/original/3X/e/6/e6c445f277c30134d8a03c8e511dd54763f044e5.png)

In the log, we get the following:

```auto
LogixDriver	01Feb2021 11:35:37
	Browse failed: com.digitalpetri.enip.cip.CipResponseException: status=0x05 [path destination unknown] , additional=[0x0000]

```

```auto
java.util.concurrent.CompletionException: com.digitalpetri.enip.cip.CipResponseException: status=0x05 [path destination unknown] , additional=[0x0000]
at java.util.concurrent.CompletableFuture.encodeThrowable(Unknown Source)
at java.util.concurrent.CompletableFuture.completeThrowable(Unknown Source)
at java.util.concurrent.CompletableFuture.biRelay(Unknown Source)
at java.util.concurrent.CompletableFuture$BiRelay.tryFire(Unknown Source)
at java.util.concurrent.CompletableFuture$CoCompletion.tryFire(Unknown Source)
at java.util.concurrent.CompletableFuture.postComplete(Unknown Source)
at java.util.concurrent.CompletableFuture.completeExceptionally(Unknown Source)
at com.inductiveautomation.xopc.drivers.logix.browse.LogixBrowse.lambda$null$20(LogixBrowse.java:271)
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.completeExceptionally(Unknown Source)
at com.inductiveautomation.xopc.drivers.logix.browse.LogixBrowse.lambda$readTemplateAttributes$22(LogixBrowse.java:310)
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.completeExceptionally(Unknown Source)
at com.digitalpetri.enip.cip.CipClient.lambda$invokeUnconnected$2(CipClient.java:128)
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.lambda$sendUnconnectedData$8(CipClient.java:201)
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.EtherNetIpClient$PendingRequest.lambda$new$0(EtherNetIpClient.java:309)
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.EtherNetIpClient.onChannelRead(EtherNetIpClient.java:188)
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)
at java.util.concurrent.ForkJoinWorkerThread.run(Unknown Source)
Caused by: com.digitalpetri.enip.cip.CipResponseException: status=0x05 [path destination unknown] , additional=[0x0000]
at com.digitalpetri.enip.cip.services.GetAttributeListService.decodeResponse(GetAttributeListService.java:45)
at com.digitalpetri.enip.cip.services.GetAttributeListService.decodeResponse(GetAttributeListService.java:12)
at com.digitalpetri.enip.cip.services.UnconnectedSendService.decodeResponse(UnconnectedSendService.java:122)
at com.digitalpetri.enip.cip.CipClient.lambda$invokeUnconnected$2(CipClient.java:112)
... 22 common frames omitted

```

Despite my best efforts, I cannot seem to get this device reconnected and I have no idea what’s taken it offline.I expect it may be related to the Logix driver version, but it still leaves me wondering why it ran fine for the last 6 months. Thoughts?

Cheers.

---

<div class="post-metadata">

**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\
**Post date:** [February 1, 2021, 7:55pm UTC](https://forum.inductiveautomation.com/t/compactlogix-v32-connectivity-lost/42839/2 "2021-02-01T19:55:13Z")

</div>

I think you’re running into a firmware bug we’ve seen a few times before.

If you were to upgrade to the latest 7.9 version I suspect it would connect but you’d fine some tags were unavailable. In older versions before we had first seen the bug the entire connection process gets derailed by this.

Re-downloading the program is the only way to fix it regardless of the version.

---

<div class="post-metadata">

**Author:** ![AIO](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/aio/32/87549_2.png) [@AIO](https://forum.inductiveautomation.com/u/AIO)\
**Post date:** [February 1, 2021, 7:59pm UTC](https://forum.inductiveautomation.com/t/compactlogix-v32-connectivity-lost/42839/3 "2021-02-01T19:59:06Z")

</div>

Thanks, Kevin, for the reply.

To be clear, re-downloading to the PLC is the recommended fix? Consider this a “Click yes to continue” popup. 😉 I’m always hesitant to go down that path (taking it offline), but can do so.

Cheers!

---

<div class="post-metadata">

**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\
**Post date:** [February 1, 2021, 7:59pm UTC](https://forum.inductiveautomation.com/t/compactlogix-v32-connectivity-lost/42839/4 "2021-02-01T19:59:50Z")

</div>

In every case we’ve seen it so far re-downloading the program immediately clears it up.

edit: I think usually, though, the customer has already upgraded Ignition to a newer version.

---

<div class="post-metadata">

**Author:** ![AIO](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/aio/32/87549_2.png) [@AIO](https://forum.inductiveautomation.com/u/AIO)\
**Post date:** [February 1, 2021, 8:22pm UTC](https://forum.inductiveautomation.com/t/compactlogix-v32-connectivity-lost/42839/5 "2021-02-01T20:22:10Z")

</div>

Kevin,

Confirmed, the re-download fixed the issue.

Unfortunately, I’ve already brought up upgrading and it hasn’t gone anywhere - the rest of the company is running 7.8. 🤷‍♂️

That said, when I went online to save the project, I encountered a `CIP Error: Address Out of Range` error in Studio 5000. Seems like [Rockwell Technote #BF23652](https://rockwellautomation.custhelp.com/app/answers/answer_view/a_id/1089948/loc/en_US#__highlight) addresses the issue, and the first recommended fix is also a re-download. Seems like a v32 issue, potentially.

Thank you again for your assistance.  
Cheers!

---

<div class="post-metadata">

**Author:** ![JordanCClark](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/jordancclark/32/83362_2.png) [@JordanCClark](https://forum.inductiveautomation.com/u/JordanCClark)\
**Post date:** [February 24, 2021, 3:36pm UTC](https://forum.inductiveautomation.com/t/compactlogix-v32-connectivity-lost/42839/6 "2021-02-24T15:36:11Z")

</div>

We had the exact issue with v32 mentioned in the Technote you linked to. Easily reproduced on my test bed by doing an online edit, then cycling power.

I’ve not had this issue with v33 firmware.
