View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
000350410000-003: Address SpaceSpecpublic2016-08-08 14:482017-01-12 17:02
ReporterThomas Merk Assigned Tojeffhardingabb  
PrioritynormalSeverityminorReproducibilityhave not tried
Status closedResolutionfixed 
Summary0003504: AccessLevel - StatusWrite bit
Description

The attributes of variable describe:

StatusWrite : Indicates if the current StatusCode of the value is writable (0 means not writable, 1 means writable).

For the attribute "TimestampWrite" it is clear that a NULL timestamp shall be allowed if write of timestamps is not supported.
If a server denies StatusWrite - what StatusCode (in the DataValue) shall indicate a NULL status code?
Is this the "Good"?

Part 4 states that Bad_WriteNotSupported shall be returned if "any value, quality, timestamp combination" is not supported by server.
BTW: Why is the StatusCode here named "quality"?

How a server shall react if a "NULL" status code is given on a Write service and server denies write of status?

  • The status code of the variable remains unchainged (e.g. Uncertain)?
  • The status code "Good" is the new status code (i.e. status code IS written)?
    ...

Some clarification necessary.

TagsNo tags attached.
Commit Version
Fix Due Date

Activities

Jim Luth

2016-08-30 16:13

administrator   ~0007163

Clarify that the status code for a variable could change in a write even when the Status Code is "not writeable" due to internal server logic. (E.g. a server sets the status to Good - Local Override).

Jim Luth

2016-08-30 16:15

administrator   ~0007164

Move to Part 4 if necessary.

jeffhardingabb

2016-12-16 17:37

developer   ~0007631

Clarifying text has been added to Section 5.6.2 Variable NodeClass to better explain the meaning of 'StatusWrite' bit on both AccessLevel and UserAccessLevel. Note: TimestampWrite has also been clarified.

The text now explains that "(0 means only StatusCode Good is writable, 1 means any StatusCode is writable)"

Jim Luth

2017-01-12 17:02

administrator   ~0007730

agreed to changes in telecon.

Issue History

Date Modified Username Field Change
2016-08-08 14:48 Thomas Merk New Issue
2016-08-30 16:13 Jim Luth Note Added: 0007163
2016-08-30 16:14 Jim Luth Assigned To => Wolfgang Mahnke
2016-08-30 16:14 Jim Luth Status new => assigned
2016-08-30 16:15 Jim Luth Note Added: 0007164
2016-11-29 14:10 Jim Luth Assigned To Wolfgang Mahnke => jeffhardingabb
2016-12-16 17:37 jeffhardingabb Note Added: 0007631
2016-12-16 17:37 jeffhardingabb Status assigned => resolved
2016-12-16 17:37 jeffhardingabb Fixed in Version => 1.04
2016-12-16 17:37 jeffhardingabb Resolution open => fixed
2017-01-12 17:02 Jim Luth Note Added: 0007730
2017-01-12 17:02 Jim Luth Status resolved => closed