View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
000421710000-020: File TransferApi Changepublic2018-03-29 15:052021-05-04 15:56
ReporterThomas Merk Assigned ToJeff Harding  
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionfixed 
Summary0004217: 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.
Attached Files
Commit Version
Fix Due Date

Relationships

related to 0006099 closedRandy Armstrong NodeSets, XSDs and Generated Code Missing values in NodeSet2 XML 
related to 0006100 closedPaul Hunkar 10000-009: Alarms and Conditions Missing values in NodeSet2 XML 
related to 0006260 closedPaul Hunkar 10000-009: Alarms and Conditions Missing values in NodeSet2 XML 

Activities

Jim Luth

2018-04-24 15:52

administrator   ~0009010

Change Part 5 to indicate StateNumber is optional.

Jeff Harding

2018-09-20 09:47

developer   ~0009377

Changed StateType StateNumber property to Optional rather than mandatory.

Thomas Merk

2020-09-22 12:56

reporter   ~0012958

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:02

administrator   ~0012988

Last edited: 2020-09-29 16:03

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.

Wolfgang Mahnke

2020-09-29 16:10

developer   ~0012997

Will be fixed in NodeSet file - see related issue - and no changes in Part 16. I did undo all changes in Part 16

Jim Luth

2020-09-29 16:10

administrator   ~0012998

Agreed to changes backed out of 1.05 draft.

Randy Armstrong

2020-11-15 02:13

administrator   ~0013208

Assigned StateNumbers need to be added to FileTransfer and Alarms.

Randy Armstrong

2020-11-15 02:16

administrator   ~0013210

FileTransferStateMachine needs state numbers added to document.
See attached spreadsheet.

statenumbers.xlsx (9,214 bytes)

Jeff Harding

2020-12-02 16:18

developer   ~0013359

Added table 18 which now defines the Value Attribute values for each of the states and transitions.

Jim Luth

2021-05-04 15:56

administrator   ~0014317

Agreed to changes in telecon.

Issue History

Date Modified Username Field Change
2018-03-29 15:05 Thomas Merk New Issue
2018-04-24 15:51 Jim Luth Project NodeSets, XSDs and Generated Code => 10000-005: Information Model
2018-04-24 15:51 Jim Luth Category Implementation Bug => Api Change
2018-04-24 15:51 Jim Luth Assigned To => Jeff Harding
2018-04-24 15:51 Jim Luth Status new => assigned
2018-04-24 15:52 Jim Luth Note Added: 0009010
2018-09-20 09:47 Jeff Harding Note Added: 0009377
2018-09-20 09:47 Jeff Harding Status assigned => resolved
2018-09-20 09:47 Jeff Harding Fixed in Version => 1.05
2018-09-20 09:47 Jeff Harding Resolution open => fixed
2020-09-22 12:56 Thomas Merk Status resolved => feedback
2020-09-22 12:56 Thomas Merk Resolution fixed => reopened
2020-09-22 12:56 Thomas Merk Note Added: 0012958
2020-09-29 16:01 Jim Luth Assigned To Jeff Harding => Wolfgang Mahnke
2020-09-29 16:02 Jim Luth Status feedback => assigned
2020-09-29 16:02 Jim Luth Note Added: 0012988
2020-09-29 16:03 Jim Luth Note Edited: 0012988
2020-09-29 16:04 Jim Luth Issue cloned: 0006099
2020-09-29 16:04 Jim Luth Relationship added related to 0006099
2020-09-29 16:05 Jim Luth Project 10000-005: Information Model => 10000-016: State Machines
2020-09-29 16:06 Jim Luth Issue cloned: 0006100
2020-09-29 16:06 Jim Luth Relationship added related to 0006100
2020-09-29 16:10 Wolfgang Mahnke Status assigned => resolved
2020-09-29 16:10 Wolfgang Mahnke Resolution reopened => no change required
2020-09-29 16:10 Wolfgang Mahnke Note Added: 0012997
2020-09-29 16:10 Jim Luth Status resolved => closed
2020-09-29 16:10 Jim Luth Fixed in Version 1.05 =>
2020-09-29 16:10 Jim Luth Note Added: 0012998
2020-11-15 02:13 Randy Armstrong Assigned To Wolfgang Mahnke => Paul Hunkar
2020-11-15 02:13 Randy Armstrong Status closed => new
2020-11-15 02:13 Randy Armstrong Resolution no change required => reopened
2020-11-15 02:13 Randy Armstrong Note Added: 0013208
2020-11-15 02:14 Randy Armstrong Assigned To Paul Hunkar => Jeff Harding
2020-11-15 02:16 Randy Armstrong File Added: statenumbers.xlsx
2020-11-15 02:16 Randy Armstrong Note Added: 0013210
2020-11-16 14:11 Jim Luth Project 10000-016: State Machines => 10000-020: File Transfer
2020-11-16 14:16 Jim Luth Status new => assigned
2020-11-16 14:17 Jim Luth Issue cloned: 0006260
2020-11-16 14:17 Jim Luth Relationship added related to 0006260
2020-12-02 16:18 Jeff Harding Status assigned => resolved
2020-12-02 16:18 Jeff Harding Resolution reopened => fixed
2020-12-02 16:18 Jeff Harding Fixed in Version => 1.05
2020-12-02 16:18 Jeff Harding Note Added: 0013359
2021-05-04 15:56 Jim Luth Status resolved => closed
2021-05-04 15:56 Jim Luth Note Added: 0014317