View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0006099NodeSets, XSDs and Generated CodeApi Changepublic2020-09-29 16:042020-11-17 16:48
ReporterJim Luth Assigned ToRandy Armstrong  
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionfixed 
Summary0006099: Missing values in NodeSet2 XML
Description

The states and transitions of ExcluesiveLimitStateMachine and ShelvingStateMachine (may be more) are defined in Opc.Ua.NodeSet2.xml.

All those states and transitions have a prperty "StateNumber" or "TransitionNumber" which shall be unique croess the states / transitions of a StateMachine.

The XML does not contain any value for these numbers, i.e. after import the numbers are 0.
The states / transitions do not have a modelling rule in the type definition, i.e. they are not copied to the state machine instances (ok), but then the states / transitions in the state machine type need unique numbers.

Every server, which imports the standard nodeset have to provide unique values to those numbers!
The numbers can differ from server to server.

I would prefer that state / transitions numbers of state machines defined in the specification should be defined both in specification (seems to be missing - at least I found no state numbers documened) AND in NodeSet2 XML.

TagsNo tags attached.
Commit Version
Fix Due Date

Relationships

related to 0004217 closedJeff Harding 10000-020: File Transfer Missing values in NodeSet2 XML 
related to 0006239 closedRandy Armstrong NodeSets, XSDs and Generated Code Missing values in NodeSet2 XML 

Activities

Jim Luth

2020-09-29 16:04

administrator   ~0012989

Change Part 5 to indicate StateNumber is optional.

Jeff Harding

2020-09-29 16:04

reporter   ~0012990

Changed StateType StateNumber property to Optional rather than mandatory.

Thomas Merk

2020-09-29 16:04

reporter   ~0012991

This does not solve the issue.
At least all well-known state machines described in NodeSet2 XML should have unique numbers assigned.
Some do have such numbers (e.g. ProgramStateMachineType), but others still miss the numbers (e.g. FileTransferStateMachineType).

But I think that is not affecting part 5, but more nodeset XML...

Jim Luth

2020-09-29 16:04

administrator   ~0012992

We agreed to back out the change to make the numbers optional and clone this to Nodeset and A&C to assign numbers to all transitions and states.

Randy Armstrong

2020-11-15 02:32

administrator   ~0013211

Fixed in 1.04.8.

Jim Luth

2020-11-17 16:48

administrator   ~0013253

Agreed to 1.04.8 Errata and nodeset.

Issue History

Date Modified Username Field Change
2020-09-29 16:04 Jim Luth New Issue
2020-09-29 16:04 Jim Luth Status new => assigned
2020-09-29 16:04 Jim Luth Assigned To => Randy Armstrong
2020-09-29 16:04 Jim Luth Issue generated from: 0004217
2020-09-29 16:04 Jim Luth Note Added: 0012989
2020-09-29 16:04 Jim Luth Note Added: 0012990
2020-09-29 16:04 Jim Luth Note Added: 0012991
2020-09-29 16:04 Jim Luth Note Added: 0012992
2020-09-29 16:04 Jim Luth Relationship added related to 0004217
2020-09-29 16:04 Jim Luth Project 10000-005: Information Model => NodeSets, XSDs and Generated Code
2020-09-29 16:04 Jim Luth Category Spec => Api Change
2020-11-10 17:07 Jim Luth Target Version => 1.04
2020-11-10 17:07 Jim Luth Issue cloned: 0006239
2020-11-10 17:07 Jim Luth Relationship added related to 0006239
2020-11-15 02:32 Randy Armstrong Status assigned => resolved
2020-11-15 02:32 Randy Armstrong Resolution open => fixed
2020-11-15 02:32 Randy Armstrong Note Added: 0013211
2020-11-17 16:48 Jim Luth Status resolved => closed
2020-11-17 16:48 Jim Luth Fixed in Version => 1.04
2020-11-17 16:48 Jim Luth Note Added: 0013253