View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
000714310000-003: Address SpaceSpecpublic2021-07-28 04:342022-06-20 14:33
ReporterPaul Hunkar Assigned ToJim Luth  
PriorityhighSeverityfeatureReproducibilityalways
Status closedResolutionfixed 
Fixed in Version1.05.01 
Summary0007143: Non-Volatile Storage
Description

we should extend the AccessLevelExType definition with an additional Bit label NonVolatileData, description would be "Indicates that the value is stored in Non-Volatile storage and will be restored on a restart of the server (1 mean Non-Volatile storage is supported).

Additional Information

This functionality is commonly available in current controllers and PLC and knowledge of whether a variable is stored in Non-Volatile storage can be very helpful to applications. FLC would utilize this bit in its information model.

TagsNo tags attached.
Commit Version
Fix Due Date

Relationships

related to 0008060 closedKarl Deiretsbacher 10000-007: Profiles Non-Volatile Storage 

Activities

Jim Luth

2021-09-07 15:56

administrator   ~0014822

Last edited: 2021-09-07 15:57

Agreed states would be 0 == presumed Volatile (i.e. volatile or don't know)
1 == guaranteed non-volatile

FLC needs this soon - target 1.05.01

Jeff Harding

2021-09-27 18:06

developer   ~0015031

Added a bit to AccessLevelEx definition.

Jim Luth

2021-10-12 15:30

administrator   ~0015162

Needs to be rolled back from 1.05.00 and fixed in 1.05.01.

Jeff Harding

2021-10-27 18:39

developer   ~0015235

Added a bit to AccessLevelEx definition.

Jim Luth

2021-11-09 20:03

administrator   ~0015298

We agreed to an alternate solution with the three bits named differently and with slightly different meaning. Jim will edit Part 3 and 5 with the new proposal.

Jeff Harding

2022-01-13 19:24

developer   ~0015709

AccessLevelEx was extended to include 2 new bits (NonVolatile and Constant).

Jim Luth

2022-06-20 11:58

administrator   ~0016871

Agreed that this is published in 1.05.01.

Issue History

Date Modified Username Field Change
2021-07-28 04:34 Paul Hunkar New Issue
2021-09-07 15:56 Jim Luth Note Added: 0014822
2021-09-07 15:57 Jim Luth Note Edited: 0014822
2021-09-07 15:58 Jim Luth Assigned To => Jeff Harding
2021-09-07 15:58 Jim Luth Status new => assigned
2021-09-27 18:06 Jeff Harding Status assigned => resolved
2021-09-27 18:06 Jeff Harding Resolution open => fixed
2021-09-27 18:06 Jeff Harding Fixed in Version => 1.05.00
2021-09-27 18:06 Jeff Harding Note Added: 0015031
2021-10-12 15:30 Jim Luth Status resolved => feedback
2021-10-12 15:30 Jim Luth Resolution fixed => reopened
2021-10-12 15:30 Jim Luth Note Added: 0015162
2021-10-12 15:31 Jim Luth Status feedback => assigned
2021-10-12 15:32 Jim Luth Fixed in Version 1.05.00 =>
2021-10-27 18:39 Jeff Harding Status assigned => resolved
2021-10-27 18:39 Jeff Harding Resolution reopened => fixed
2021-10-27 18:39 Jeff Harding Fixed in Version => 1.05.01
2021-10-27 18:39 Jeff Harding Note Added: 0015235
2021-11-09 20:03 Jim Luth Note Added: 0015298
2021-11-09 20:03 Jim Luth Assigned To Jeff Harding => Jim Luth
2021-11-09 20:03 Jim Luth Status resolved => assigned
2022-01-13 19:24 Jeff Harding Status assigned => resolved
2022-01-13 19:24 Jeff Harding Note Added: 0015709
2022-06-20 11:58 Jim Luth Status resolved => closed
2022-06-20 11:58 Jim Luth Note Added: 0016871
2022-06-20 14:33 Jim Luth Issue cloned: 0008060
2022-06-20 14:33 Jim Luth Relationship added related to 0008060