View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0010312 | Compliance Test Tool (CTT) Unified Architecture | 5 - General Problem | public | 2025-04-29 11:04 | 2025-04-29 17:07 |
Reporter | Kevin Herron (Inductive Automation) | Assigned To | |||
Priority | normal | Severity | minor | Reproducibility | always |
Status | new | Resolution | open | ||
Summary | 0010312: 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 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:
| ||||
Tags | No tags attached. | ||||
Attached Files | |||||
Files Affected | |||||
|
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. |
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 |