View Issue Details

IDProjectCategoryView StatusLast Update
0010312Compliance Test Tool (CTT) Unified Architecture5 - General Problempublic2025-04-29 17:07
ReporterKevin Herron (Inductive Automation) Assigned To 
PrioritynormalSeverityminorReproducibilityalways
Status newResolutionopen 
Summary0010312: CTT does not correctly handle ExpandedNodeId with explicit namespace URI
Description

Address Space Base 001 fails with a bunch of BadNodeIdUnknown errors when some of the References returned by a Server use ExpandedNodeId with an explicit namespace URI set instead of a namespace index.

There are parts of whatever this test does where it browses types and then attempts to read attributes from the references it just browsed, and it can be seen in a Wireshark capture that instead of resolving the namespace URI returned in the references it instead issues a read for ns=0;s=... - the wrong namespace index.

I've published a server to Docker that you can use to reproduce this. It's at https://hub.docker.com/repository/docker/kevinherron/server-29307/general

To run it:

docker pull kevinherron/server-29307
docker run --rm -it -p 4840:4840 kevinherron/server-29307
TagsNo tags attached.
Attached Files
image.png (123,168 bytes)   
image.png (123,168 bytes)   
Files Affected

Activities

Kevin Herron (Inductive Automation)

2025-04-29 17:07

reporter   ~0022691

Ah, you can close this. See https://reference.opcfoundation.org/Core/Part4/v105/docs/7.30, which says that for ReferenceDescription the ExpandedNodeId must be relative (use index, not namespace URI) when the target Node is local.

Issue History

Date Modified Username Field Change
2025-04-29 11:04 Kevin Herron (Inductive Automation) New Issue
2025-04-29 11:04 Kevin Herron (Inductive Automation) File Added: image.png
2025-04-29 17:07 Kevin Herron (Inductive Automation) Note Added: 0022691