View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
000610010000-009: Alarms and ConditionsSpecpublic2020-09-29 16:062020-11-17 16:32
ReporterJim Luth Assigned ToPaul Hunkar  
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionduplicate 
Summary0006100: 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

duplicate of 0006260 closedPaul Hunkar 10000-009: Alarms and Conditions Missing values in NodeSet2 XML 
related to 0004217 closedJeff Harding 10000-020: File Transfer Missing values in NodeSet2 XML 

Activities

Jim Luth

2020-09-29 16:06

administrator   ~0012993

Change Part 5 to indicate StateNumber is optional.

Jeff Harding

2020-09-29 16:06

developer   ~0012994

Changed StateType StateNumber property to Optional rather than mandatory.

Thomas Merk

2020-09-29 16:06

reporter   ~0012995

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

administrator   ~0012996

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

administrator   ~0013209

New statenumbers in attached spreadsheet.

statenumbers.xlsx (9,214 bytes)

Paul Hunkar

2020-11-17 16:32

developer   ~0013247

two entered for same issue

Paul Hunkar

2020-11-17 16:32

developer   ~0013248

duplicate

Issue History

Date Modified Username Field Change
2020-09-29 16:06 Jim Luth New Issue
2020-09-29 16:06 Jim Luth Status new => assigned
2020-09-29 16:06 Jim Luth Assigned To => Paul Hunkar
2020-09-29 16:06 Jim Luth Issue generated from: 0004217
2020-09-29 16:06 Jim Luth Note Added: 0012993
2020-09-29 16:06 Jim Luth Note Added: 0012994
2020-09-29 16:06 Jim Luth Note Added: 0012995
2020-09-29 16:06 Jim Luth Note Added: 0012996
2020-09-29 16:06 Jim Luth Relationship added related to 0004217
2020-09-29 16:07 Jim Luth Project 10000-016: State Machines => 10000-009: Alarms and Conditions
2020-11-15 02:14 Randy Armstrong File Added: statenumbers.xlsx
2020-11-15 02:14 Randy Armstrong Note Added: 0013209
2020-11-17 16:32 Paul Hunkar Status assigned => resolved
2020-11-17 16:32 Paul Hunkar Resolution open => duplicate
2020-11-17 16:32 Paul Hunkar Note Added: 0013247
2020-11-17 16:32 Paul Hunkar Relationship added duplicate of 0006260
2020-11-17 16:32 Paul Hunkar Status resolved => closed
2020-11-17 16:32 Paul Hunkar Note Added: 0013248