View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0002501NodeSets, XSDs and Generated CodeImplementation Bugpublic2013-06-27 13:452015-02-26 22:12
ReporterKarl Deiretsbacher Assigned ToRandy Armstrong  
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionfixed 
Product Version1.02 
Summary0002501: Add new operational StatusCode "Good_Edited"
Description

FDI has the notion of an EditContext (a cache). Clients can create such an EditContext and register Variables with it; write operations to these regsitered Variables will then occur in this cache. Read and Subscription as well.

Internal business logic in the Server, however, can update the Variable in the Device in which case the edited Value will be cleared.

Clients need to know in Read and DataChange whether a Value stems from the Device (the real source) or whether it is an edited Value.

Proposal is to define a new StatusCode "Good_Edited" that would be used for this use case.

TagsNo tags attached.
Commit Version
Fix Due Date

Activities

Karl Deiretsbacher

2013-07-09 17:19

reporter   ~0004769

2013-07-09: UA Meeting
We decided that OPC UA companion standards shall be able to define their own status codes. These codes have to be part of the global CSV as we have to avoid overloads.

Good_Edited shall be added as a new status code but will be specified as part of the FDI specification.

Jim Luth

2013-07-10 14:00

administrator   ~0004795

It would be nice if we had a process for adding these external status codes. I suggest that we – in a first step – create a document (Part 99 – External StatusCodes) where we list all codes that we have added based on request from companion specs. This is for internal bookkeeping but also allows detecting codes that several standards need.

-Karl

Jim Luth

2013-07-10 14:01

administrator   ~0004796

I don’t like the proposal that we create a document for internal bookkeeping of the error codes. Having to keep the CSV (code) file in sync with the bookkeeping file is a maintenance headache. I would much prefer that the code file be the bookkeeping file. If the CSV file is not sufficient for this maybe we should change it to an XML file where we can also use it for bookkeeping.

  • Jim

Jim Luth

2013-07-10 14:02

administrator   ~0004797

I thought that in a word document we could organise the requested codes.
So we could have a section header FDI, S95, MTConnect and others followed by a table with the codes.

I guess this can be accomplished in the CSV or an XML file as well.
CSV: add another column to indicate the organization
XML: use an attribute for this purpose

-Karl

Randy Armstrong

2013-08-06 04:11

administrator   ~0004882

Added
Good_Edited,220

With description:
The value does not come from the real source and has been edited by the server.

Jim Luth

2015-02-26 22:12

administrator   ~0005859

OKed to close by Karl

Issue History

Date Modified Username Field Change
2013-06-27 13:45 Karl Deiretsbacher New Issue
2013-07-09 17:15 Karl Deiretsbacher Status new => assigned
2013-07-09 17:15 Karl Deiretsbacher Assigned To => Randy Armstrong
2013-07-09 17:16 Karl Deiretsbacher Project 10000-004: Services => NodeSets, XSDs and Generated Code
2013-07-09 17:19 Karl Deiretsbacher Note Added: 0004769
2013-07-10 14:00 Jim Luth Note Added: 0004795
2013-07-10 14:01 Jim Luth Note Added: 0004796
2013-07-10 14:02 Jim Luth Note Added: 0004797
2013-08-06 04:11 Randy Armstrong Status assigned => resolved
2013-08-06 04:11 Randy Armstrong Resolution open => fixed
2013-08-06 04:11 Randy Armstrong Note Added: 0004882
2015-02-18 14:28 Randy Armstrong Category (No Category) => Implementation Bug
2015-02-26 22:12 Jim Luth Note Added: 0005859
2015-02-26 22:12 Jim Luth Status resolved => closed