1822   Functional constraint object non-volatility ambiguous

Created: 04 Apr 2022

Status: Drafting Implementation

Part: Part 7-2 (2020; Edition 2.1)

Links:

Page: 29

Clause: 5.7

Paragraph: Table 4

Issue

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
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 responsability / system management issue to command the ICT to use/retrieve or ignore the current online values during the next IID export."
28 Feb 23 Drafting Implementation
Last comment: "but a PIXIT entry remains required for "Initial value shall be as configured"."
-> no. The initial values are present in the SCD file that is imported by the ICT. The device is configured according to the imported SCD in the ICT.
From that time on, the device is responsible for managing proprietarily the non-volatile interface the way it stores the non volatile values.
The values remain in non-volatile interface until a new SCD is imported by the ICT, and the resulting new configuration is uploaded to the device. During this upload new configuration, the non-volatile values stored in the device are lost; the ICT may have retrieved the non-volatile values to update the values exposed in the IID file of the device, based on a user request.
Conclusion: no PIXIT entry required.


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 responsability / system management issue to command the ICT to use/retrieve or ignore the current online values during the next IID export."



24 Jan 23 Discussion (red)
No PIXIT is required to test "value shall be non-volatile" but a PIXIT entry remains required for "Initial value shall be as configured".
PIXIT entry would indicate how this is done (perhaps it is every time a new SCD is imported but there are probably other procedures or other variations on SCD import).
21 Dec 22 Discussion (red)
No PIXIT entry is required.
It is out of scope of the test how the non voltaile interface is realized, as mentioned in the text.
Relevant for the test: Change a non voltile object over communication, perform a power cycle of the device, and verify the that the modified values have been conserved.
21 Dec 22 Discussion (red)
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.
22 Nov 22 Discussion (red)

 

Privacy | Contact | Disclaimer

Tissue DB v. 23.3.6.1