Error Reading DNP3 Conformance Level

Ignition
1

Wrapper log is filled with:

INFO   | jvm 1    | 2021/12/21 13:18:06 | E [d.dnp3                        ] [18:18:06]: Error reading conformance level:  device-name=XXXXXX
INFO   | jvm 1    | 2021/12/21 13:18:06 | java.lang.IndexOutOfBoundsException: null
INFO   | jvm 1    | 2021/12/21 13:18:06 | 	at io.netty.buffer.EmptyByteBuf.checkLength(EmptyByteBuf.java:1058)
INFO   | jvm 1    | 2021/12/21 13:18:06 | 	at io.netty.buffer.EmptyByteBuf.skipBytes(EmptyByteBuf.java:686)
INFO   | jvm 1    | 2021/12/21 13:18:06 | 	at com.inductiveautomation.xopc.drivers.dnp3.Dnp3Driver.lambda$readConformanceLevel$15(Dnp3Driver.java:467)
INFO   | jvm 1    | 2021/12/21 13:18:06 | 	at java.base/java.util.concurrent.CompletableFuture.uniWhenComplete(Unknown Source)
INFO   | jvm 1    | 2021/12/21 13:18:06 | 	at java.base/java.util.concurrent.CompletableFuture$UniWhenComplete.tryFire(Unknown Source)

I see a change log entry from a year ago that looks like it was addressing this:

Nightly Changelog: 7.9.17-b20201201

Connectivity
870: DNP3 driver conformance level read issues for versions 7.9.13 - 7.9.16
Support parameter error when reading conformance level

DNP3 driver 4.1.12, Ignition 8.1.12

I have 27 DNP3 devices connected, some level 2, some level 3 but all support reading of conformance level from device attributes.

Ideas?

2

I think you’ll need to open a ticket with support so they can help you get a Wireshark capture and upload it along with your logs.

3

Sounds good. I’ll see if I can figure out when it happens (maybe integrity poll once/hour?, or device restart?) and then I can set up a Wireshark capture for that time and filtered to a single device. Use that as the opening salvo for the support case :slight_smile: