View Issue Details

IDProjectCategoryView StatusLast Update
000136710000-004: Servicespublic2012-02-09 22:42
ReporterNathan PocockAssigned ToMatthias Damm  
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionfixed 
Product Version1.01 
Fixed in Version1.02 
Summary0001367: Call Service: What if a Method cannot be invoked due to timing?
Description

On Page 0000059 the 2nd paragraph says:

"Because Methods may control some aspect of plant operations, method invocation may depend on environmental or other conditions. This may be especially true when attempting to re-invoke a method immediately after it has completed execution. Conditions that are required to invoke the method might not yet have returned to the state that permits the method to start again."

In the case of the LAST SENTENCE, what should the Server do/return if it cannot invoke the method? Should it:

(a) return GOOD and simply ignore the request since the conditions have not reached a state where the method can be invoked again.

(b) return an error code stating the method cannot be invoked yet, perhaps Bad_TooManyOperations since it is listed in Table 62 (along with Bad_NothingToDo). Or, seek an alternate error code like Bad_InvalidState?

TagsNo tags attached.
Commit Version
Fix Due Date

Activities

Matthias Damm

2011-03-07 18:02

developer   ~0002335

Telco March 7, 2011

Add Bad_NoCommunication to list of status codes to cover the generic situatuion that the device is not ready or availablt.

Add this status code also to Write to be consitent.

Matthias Damm

2011-03-12 14:04

developer   ~0002379

Added Bad_NoCommunication to list of standard error codes for Call and Write to cover the case where the data source is configured but not available.

Change is part of the draft version "OPC UA Part 4 - Services Draft 1.02.02 Body.doc"

Randy Armstrong

2011-05-23 16:57

administrator   ~0002744

Closed in Walldorf

Issue History

Date Modified Username Field Change
2010-08-24 15:07 Nathan Pocock New Issue
2011-02-14 06:21 Randy Armstrong Status new => assigned
2011-02-14 06:21 Randy Armstrong Assigned To => Matthias Damm
2011-03-07 18:02 Matthias Damm Note Added: 0002335
2011-03-12 14:04 Matthias Damm Status assigned => resolved
2011-03-12 14:04 Matthias Damm Resolution open => fixed
2011-03-12 14:04 Matthias Damm Note Added: 0002379
2011-05-23 16:57 Randy Armstrong Status resolved => closed
2011-05-23 16:57 Randy Armstrong Note Added: 0002744
2012-02-09 22:42 Jim Luth Fixed in Version => 1.02