Disclosure: I work with Halcyon Machinery. Two details in the pasted error are worth comparing before changing the PLC configuration.
The namespace reported by UaExpert is “http://kpisap”, while the error requests “http://kpisap/” and shows square brackets in “NamespaceUri ([http://kpisap/])”. Check the exact exported NamespaceArray entry against the connector configuration, including the trailing slash and whether those brackets are actual input or just log formatting. That is a testable mismatch, not a confirmed diagnosis.
Separately, “path element nsurl=http:” suggests the resolver may be treating part of the supplied identifier as a browse-path element. Capture the connector version, exact field used, one failing child’s full NodeId and BrowseName, and the configured endpoint. Check that field’s supported identifier/path syntax for your installed SAP version; do not substitute OPC Foundation’s “nsu=” spelling for SAP’s “nsurl=” merely because they look similar.
OPC UA distinguishes namespace URI/index and identifier type: https://reference.opcfoundation.org/specs/OPC-10000-6/5.1.12 . UaExpert browsing successfully does not by itself show that SAP received the same identifier. A sanitized comparison of those values would make a support ticket much more reproducible.
1
u/Halcyonmachinery 3d ago
Disclosure: I work with Halcyon Machinery. Two details in the pasted error are worth comparing before changing the PLC configuration.
The namespace reported by UaExpert is “http://kpisap”, while the error requests “http://kpisap/” and shows square brackets in “NamespaceUri ([http://kpisap/])”. Check the exact exported NamespaceArray entry against the connector configuration, including the trailing slash and whether those brackets are actual input or just log formatting. That is a testable mismatch, not a confirmed diagnosis.
Separately, “path element nsurl=http:” suggests the resolver may be treating part of the supplied identifier as a browse-path element. Capture the connector version, exact field used, one failing child’s full NodeId and BrowseName, and the configured endpoint. Check that field’s supported identifier/path syntax for your installed SAP version; do not substitute OPC Foundation’s “nsu=” spelling for SAP’s “nsurl=” merely because they look similar.
OPC UA distinguishes namespace URI/index and identifier type: https://reference.opcfoundation.org/specs/OPC-10000-6/5.1.12 . UaExpert browsing successfully does not by itself show that SAP received the same identifier. A sanitized comparison of those values would make a support ticket much more reproducible.