Definition of SP and CF and DC and SG each have same words "Initial value shall be as configured; value shall be non-volatile".
Upon restart, this could be interpreted as:
1. Values from SCL are used
2. Values from local non-volatile memory are used
Which is correct (or is this a "local issue")?
Is there some expectation that a device "know" that it is under initial configuration and to discard non-volatile values?
Proposal
Remove all Table 4 references to "non-volatile".
The expectation is that any changes to objects of these types cause an IID file to be generated with updated values. Somehow indicate that these updated IID files are expected to be incorporated into the SCD file.
Discussion
Created
Status
move to back conformance test preparation:
Test procedure needs to add steps to consider writable CF, SP, DC.
Agreed clarification editorial change:
behind "Initial value shall be as configured; value shall be non-volatile"
add:
", which means, that if the value has been changed online, upon restart that changed value shall be applied instead of the configured initial value. How the non volatile interface is realized is a local issue. Additionally, it is a user responsibility / system management issue to command the ICT to use/retrieve or ignore the current online values during the next IID export."
22 Aug 23
Conformance Test Preparation
TISSUE is not complete until test procedure has been created and validated. Propose to move back to stage "Conformance Test Preparation"
11 Jul 23
Ballot Period
Test procedure needs to add steps to consider writable CF, SP, DC.
11 Jul 23
Ballot Period
A new conformance test needs to be created for non-volatile value other than within a Control Block. sSg12 only tests that Control Block attributes remain unchanged through power cycles.
07 Jun 23
Ballot Period
Agreed clarification editorial change:
behind "Initial value shall be as configured; value shall be non-volatile"
add:
", which means, that if the value has been changed online, upon restart that changed value shall be applied instead of the configured initial value. How the non volatile interface is realized is a local issue. Additionally, it is a user responsibility / system management issue to command the ICT to use/retrieve or ignore the current online values during the next IID export."
06 Jun 23
Ballot Period
TPWG:
Already tested sSg12. No test plan change needed.
16 May 23
Conformance Test Verification
No compatibility issue could be found with the clarification of the non-volatile property.
Proposed clarification editorial change:
behind "Initial value shall be as configured; value shall be non-volatile"
add:
", which means, that if the value has been changed online, upon restart that changed value shall be applied instead of the configured initial value. How the non volatile interface is realized is a local issue. Additionally, it is a user responsibility / system management issue to command the ICT to use/retrieve or ignore the current online values during the next IID export."
02 May 23
Conformance Test Preparation
No comments received. => moving to next step...
Proposed clarification editorial change:
behind "Initial value shall be as configured; value shall be non-volatile"
add:
", which means, that if the value has been changed online, upon restart that changed value shall be applied instead of the configured initial value. How the non volatile interface is realized is a local issue. Additionally, it is a user responsibility / system management issue to command the ICT to use/retrieve or ignore the current online values during the next IID export."
02 May 23
Analysis Of Compatibility
seems we need more discussion.
As mentioned, it has relation to 80-7; but as well what was proposed in the second Amendment to 7-3.
So new proposal to keep explanation as is for the moment but make it a future issue.