View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
000908210000-006: MappingsSpecpublic2023-08-05 00:182023-10-10 17:01
ReporterStefan Pledl Assigned ToRandy Armstrong  
PriorityhighSeverityminorReproducibilityalways
Status closedResolutionfixed 
Product Version1.05.02 
Fixed in Version1.05.03 
Summary0009082: Clarify generation of <SymbolName> for DefaultBinary/DefaultXML nodes in csv files
Description

What is the correct <SymbolName> for DefaultBinary/DefaultXML instance nodes for writing into a csv file?

Output of Siemens SiOME:
DefaultBinary,5001,Object
DefaultXML,5002,Object
DefaultBinary,5003,Object
DefaultXML,5004,Object

Output of Unified Automation UaModeler:
Example1StructType_Encoding_DefaultBinary,5001,Object
Example1StructType_Encoding_DefaultXML,5002,Object
Example2StructType_Encoding_DefaultBinary,5003,Object
Example2StructType_Encoding_DefaultXML,5004,Object

UaModeler prefixes DefaultBinary/DefaultXML in a csv file with '<TYPE>Encoding'
e.g.
<TYPE>_Encoding_DefaultBinary
<TYPE>_Encoding_DefaultXML
This style is also used in the official csv files from the OPC Foundation.

The Siemens support says that the behavior of SiOME is correct and that the generation of <SymbolName> for DefaultBinary/DefaultXML ist not exactly specified in
https://reference.opcfoundation.org/Core/Part6/v105/docs/A.3
and should therfore be clarified.

Kind regards
Stefan Pledl

Steps To Reproduce

Create a simple nodes set with a custom structure type and instaciate this type.
Afterwards export the NodeID's to a csv file.

Compare the results generated by SiOME and UaModeler.

TagsNo tags attached.
Commit Version1.05.03
Fix Due Date2023-11-01

Activities

Randy Armstrong

2023-08-05 01:40

administrator   ~0019841

The appendix was not intended to defined a strict syntax, however, there is an implicit requirement that all browse paths in a file be unique and it is not clear how the Siemens SiOME output could ensure uniqueness.

The need for uniqueness is why the appendix explains how browse paths for instances are constructed.

The specification will be updated to explicitly state that each browse path in a file must be unique.

Jim Luth

2023-08-08 16:01

administrator   ~0019851

Agreed that most of A.3 is not normative. Needs to be edited or even removed.

Randy Armstrong

2023-10-04 07:04

administrator   ~0020084

Added requirement for uniqueness. Made the syntax informative.

Jim Luth

2023-10-10 17:01

administrator   ~0020122

Agreed to changes in Web Meeting.

Issue History

Date Modified Username Field Change
2023-08-05 00:18 Stefan Pledl New Issue
2023-08-05 01:40 Randy Armstrong Note Added: 0019841
2023-08-08 16:01 Jim Luth Note Added: 0019851
2023-08-08 16:01 Jim Luth Assigned To => Randy Armstrong
2023-08-08 16:01 Jim Luth Status new => assigned
2023-08-08 16:03 Jim Luth Commit Version => 1.05.03
2023-08-08 16:03 Jim Luth Fix Due Date => 2023-11-01
2023-10-04 07:04 Randy Armstrong Status assigned => resolved
2023-10-04 07:04 Randy Armstrong Resolution open => fixed
2023-10-04 07:04 Randy Armstrong Note Added: 0020084
2023-10-10 17:01 Jim Luth Status resolved => closed
2023-10-10 17:01 Jim Luth Fixed in Version => 1.05.03
2023-10-10 17:01 Jim Luth Note Added: 0020122