View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0009322 | Part 83: UAFX Offline Engineering | Spec | public | 2023-12-20 16:20 | 2024-09-13 11:47 |
| Reporter | Marco Hoch | Assigned To | Emanuel Kolb | ||
| Priority | normal | Severity | minor | Reproducibility | have not tried |
| Status | assigned | Resolution | open | ||
| Product Version | 1.00.02 | ||||
| Target Version | 1.00.03 | ||||
| Summary | 0009322: References using ExplicitNodeId (e.g., NodeId, BrowsePath) are not according to AutomationML concepts | ||||
| Description | In OPC UA, a PublishedDataSet set refers to the included variables (PublishedVariable of PublishedData) and the used data type (DataType of DataSetMetData) by using the NodeId. If NodeIds are present in the descriptor, it can be used and easily resolved. Using the BrowsePath for referencing in an AutomationML is more complex. In previous versions, referencing by GUID or CAEX path was allowed and AmlEngine functions could be used. It should be checked if the referencing can be simplified especially by BrowsePath. When the Opc2Aml converter creates an AML file, the reference to a DataType is done by the RootNodeId, but datatypes does not contain any NodeIds in the AML model. This means that it cannot be resolved. Attached are examples for the mentioned references. | ||||
| Tags | No tags attached. | ||||
| Attached Files | |||||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2023-12-20 16:20 | Marco Hoch | New Issue | |
| 2023-12-20 16:20 | Marco Hoch | Status | new => assigned |
| 2023-12-20 16:20 | Marco Hoch | Assigned To | => Emanuel Kolb |
| 2023-12-20 16:20 | Marco Hoch | File Added: ReferenceByUsingNodeId_PublishedVariableExample.PNG | |
| 2023-12-20 16:20 | Marco Hoch | File Added: ReferenceByUsingNodeId_DataTypeExample.PNG | |
| 2024-09-13 11:47 | Emanuel Kolb | Product Version | 1.00.03 => 1.00.02 |
