View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0003535 | 10000-003: Address Space | Spec | public | 2016-09-17 07:03 | 2017-01-10 16:26 |
Reporter | Karl Deiretsbacher | Assigned To | jeffhardingabb | ||
Priority | normal | Severity | minor | Reproducibility | have not tried |
Status | closed | Resolution | fixed | ||
Product Version | 1.03 | ||||
Summary | 0003535: Need attribute to indicate atomicity | ||||
Description | Some systems - in particular in hard realtime control - do not allow inhibiting interrupts and therefore cannot guarantee atomic access in all cases, in particular for variables that are structures or arrays. Proposal: Add an optional attribute ("atomicity") per Variable. | ||||
Tags | No tags attached. | ||||
Commit Version | |||||
Fix Due Date | |||||
related to | 0003536 | closed | jeffhardingabb | 10000-003: Address Space | No access level flag for optional IndexRange write |
related to | 0003311 | closed | randyarmstrong | 10000-006: Mappings | New DataTypeDefinition Attribute |
|
My recommendation is to add a new bit mask attribute instead of a Boolean attribute just for atomicity. We extended the AccessLevel in the past with additional related information. But the AccessLevel mask is full. It is already foreseeable that we need additional flags e.g. an indication that a variable cannot be used for real-time communication. CANopen has such flags in addition to simple read/write (read/write flags + cyclic/real-time access flags + safety flags). My proposal would be to introduce an AccessRestrictions or AccessLimitations Attribute that is a bit mask. If a flag is set in this mask, it indicates a restriction e.g. no atomicity or no real-time access. The default would be false. |
|
Added attribute Atomicity in Part 3 section 5.6.2 |
|
There are more requirements we need to cover with the new attribute and therefore we should use a more generic name and add other features (see 0003536) and ma concrete proposal in 'OPC UA Part 3 - Address Space Model 1.04.05 Draft Specification Jim Luth Comments_MD.docx' |
|
The attribute is now called AccessLevelEx and new Bits are already included. |
|
Agreed to changes edited in telecon. |
Date Modified | Username | Field | Change |
---|---|---|---|
2016-09-17 07:03 | Karl Deiretsbacher | New Issue | |
2016-09-20 16:04 | Jim Luth | Assigned To | => Wolfgang Mahnke |
2016-09-20 16:04 | Jim Luth | Status | new => assigned |
2016-10-06 10:53 | Matthias Damm | Note Added: 0007191 | |
2016-11-29 14:10 | Jim Luth | Assigned To | Wolfgang Mahnke => jeffhardingabb |
2016-12-09 12:08 | jeffhardingabb | Note Added: 0007473 | |
2016-12-09 12:08 | jeffhardingabb | Status | assigned => resolved |
2016-12-09 12:08 | jeffhardingabb | Fixed in Version | => 1.04 |
2016-12-09 12:08 | jeffhardingabb | Resolution | open => fixed |
2016-12-10 12:59 | Matthias Damm | Relationship added | related to 0003536 |
2016-12-10 13:01 | Matthias Damm | Note Added: 0007503 | |
2016-12-10 13:01 | Matthias Damm | Status | resolved => feedback |
2016-12-10 13:01 | Matthias Damm | Resolution | fixed => reopened |
2016-12-10 22:00 | Matthias Damm | Relationship added | related to 0003311 |
2016-12-13 20:06 | Karl Deiretsbacher | Note Added: 0007518 | |
2016-12-13 20:06 | Karl Deiretsbacher | Status | feedback => assigned |
2016-12-13 20:06 | Karl Deiretsbacher | Status | assigned => resolved |
2016-12-13 20:06 | Karl Deiretsbacher | Resolution | reopened => fixed |
2017-01-10 16:26 | Jim Luth | Note Added: 0007706 | |
2017-01-10 16:26 | Jim Luth | Status | resolved => closed |