Improvement #633
Updated by Carlos Rodriguez del Castillo almost 4 years ago
The point here is more that the paramRev and valRev are not bound to the process as such. It is an internal status of the device, and this is what is confusing here.
If we consider the internal configuration of the device as the “process” related to these DAs, then, there is no contradiction in any parts.
As per 7-2, the initial value will be read from the internal configuration, because it may change during running of the device, and so the SCD value is no more relevant.
Then, based on part 6 comment, this will be decided by the device manufacturer how this value is managed and the engineer have to know how it is managed (here we may have a hole in the standard…). The device may initialize the value from the SCD and store it in the internal configuration, or the device may manage it totally independently of the SCD and so the internal database will have to be updated also on configuration update, but with internal value.
And part 7-3 is clear on how the value have to be updated.
The certification test is not based on the paramRev, valRev values written in the SCD, but check that after import values are updated.
And choice of FC=ST for these values is because CF are not bound to trigger options and there is no process regarding live update of CF data attributes.
So maybe what could be clarified in the standard are:
- What is “process” for ST bound to internal data of the device
- Improve description of the management of the value initialisation by the device