View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0010156 | Part 81: UAFX Connecting Devices and Information Model | Spec | public | 2025-02-17 13:43 | 2025-02-19 08:10 |
Reporter | Matthias Damm | Assigned To | |||
Priority | normal | Severity | minor | Reproducibility | have not tried |
Status | new | Resolution | open | ||
Product Version | 1.00.02 | ||||
Target Version | 1.00.03 | ||||
Summary | 0010156: Issue with ConnectionConfigurationSet file content - Namespaces | ||||
Description | F.2 ConnectionConfigurationSet file content Required are: | ||||
Additional Information | OPC UA Part 5: OPC UA Part 14: | ||||
Tags | No tags attached. | ||||
|
Please increase Mantis priority. |
|
This file format is for CCS information - and the http://opcfoundation.org/UA/FX/AC/ does not exist in a CCS - so I am confused by the requirement for this namespace in the configuration? Removing the http://opcfoundation.org/UA/ namespace is just a textual update and can easily be accomplished (no nodeset changes required) |
|
Paul you are right - I was refering to ConnectionEndpointTypeId NodeId in the Endpoint structure that contains typically a NodeId from the AC namespace. But this is the NodeId related to the server where the endpoint is created and therefore the namespace table of the server entry is relevant. But we need Data and CM namespaces |
Date Modified | Username | Field | Change |
---|---|---|---|
2025-02-17 13:43 | Matthias Damm | New Issue | |
2025-02-17 15:47 | Matthias Damm | Description Updated | |
2025-02-18 16:45 | muetzeclaudia | Note Added: 0022397 | |
2025-02-19 05:43 | Paul Hunkar | Note Added: 0022399 | |
2025-02-19 08:10 | Matthias Damm | Note Added: 0022400 |