Skip to content

v0.11.0

Choose a tag to compare

@github-actions github-actions released this 03 Nov 09:01
57353d8

Date: 2026-11-03
Previous release: v0.10.0

Summary

Two more reference stacks: cB-Sigma dnp3 v0.3.0 (Go, Apache-2.0, master and
outstation) and nfm-dnp3 1.0.1 (Python, MIT, master over TCP), both
published. Container contract 1.5 and fixture format 1.0 unchanged; the
existing adapters are unchanged.

Changes

Adapters

  • cbsigma (dnp3-interop-cbsigma): both roles over TCP, UDP, serial and TLS, secure authentication v5, file transfer, device attributes (master), freezes and counter increments. Serves the baseline fixture.
  • nfmdnp3 (dnp3-interop-nfmdnp3): the master over TCP. Its defects are reported upstream (fxodell/dnp3py#1 to #10) and are known bugs here.
  • versions.yaml, scripts/check-versions.sh, scripts/latest-upstream.py, the Release, Upstream and own-stack workflows and THIRD_PARTY_NOTICES.md cover both.

Self-test

  • Event read of one group: a READ of g32 returns only the analog input events; the binary input events stay buffered for the next event poll.
  • scripts/smoke.sh: SMOKE_SERVER_FIXTURE picks the fixture of the server (the nfmdnp3 smoke runs against the dnp3py fixture); the counter-increment check expects a usage error on an image without counterIncrementServer.
  • The value checks of scripts/interop.sh and the file agreement check of scripts/features.sh can be matched by a known bug.
  • Known bugs (tests/known-bugs.tsv): cB-Sigma's cached answer to a repeated request, FREEZE AND CLEAR without counter event, GET_FILE_INFO name and keep-alive interval, and two differences from the contract; nfm-dnp3's defects; the opendnp3 master reading the g52v1 delay as milliseconds; the DSC master ignoring challenges that are not 32 octets.

Docs

  • README, CAPABILITIES, COMPATIBILITY (matrix and findings), COVERAGE, PLAN and THIRD_PARTY_NOTICES describe the five stacks.

Images

Image Digest
ghcr.io/otfabric/dnp3-interop-opendnp3:v0.11.0 sha256:ccc55f25dc0119d3007a9d37fd5bfe35e92eb58f8194466d295ba3a536e20578
ghcr.io/otfabric/dnp3-interop-dscsystems:v0.11.0 sha256:cf080446f229a6a192197f3cdf2cf24634375eb041cb4080cdb44aa323969c2f
ghcr.io/otfabric/dnp3-interop-dnp3py:v0.11.0 sha256:b8b5a431b660510737b80fcdc01040bfd2a9778c90feed2704857bead0c4758a
ghcr.io/otfabric/dnp3-interop-cbsigma:v0.11.0 sha256:9ef028cbe51607ca8568dc1bdd0b202554e027a08b3efe9f17112b839ce64262
ghcr.io/otfabric/dnp3-interop-nfmdnp3:v0.11.0 sha256:92d2ecc7a74cfbbbfae1da49524cf54e5204301042e269b80705bbc55ec4d78d

The dnp3c runner (dnp3-interop-dnp3c, the DNP3 IED Certification Procedure as Step Function I/O's dnp3c implements it, GPL-3.0-only) is not published: make image-dnp3c VERSION=v0.11.0 builds it, fetching dnp3c from Maven Central. See docs/CONFORMANCE.md.

Pinning in a consumer

DNP3_INTEROP_OPENDNP3_IMAGE=ghcr.io/otfabric/dnp3-interop-opendnp3@sha256:ccc55f25dc0119d3007a9d37fd5bfe35e92eb58f8194466d295ba3a536e20578
DNP3_INTEROP_DSCSYSTEMS_IMAGE=ghcr.io/otfabric/dnp3-interop-dscsystems@sha256:cf080446f229a6a192197f3cdf2cf24634375eb041cb4080cdb44aa323969c2f
DNP3_INTEROP_DNP3PY_IMAGE=ghcr.io/otfabric/dnp3-interop-dnp3py@sha256:b8b5a431b660510737b80fcdc01040bfd2a9778c90feed2704857bead0c4758a
DNP3_INTEROP_CBSIGMA_IMAGE=ghcr.io/otfabric/dnp3-interop-cbsigma@sha256:9ef028cbe51607ca8568dc1bdd0b202554e027a08b3efe9f17112b839ce64262
DNP3_INTEROP_NFMDNP3_IMAGE=ghcr.io/otfabric/dnp3-interop-nfmdnp3@sha256:92d2ecc7a74cfbbbfae1da49524cf54e5204301042e269b80705bbc55ec4d78d
# built locally (see above), not pulled:
DNP3_INTEROP_DNP3C_IMAGE=ghcr.io/otfabric/dnp3-interop-dnp3c:v0.11.0

manifest.json records the upstream revisions these images were built from, and under localOnly the pins of the dnp3c image you build yourself. The published images contain MIT, Apache-2.0 and GPL-3.0-or-later software and are for interoperability testing. See THIRD_PARTY_NOTICES.md.