1270   "t" can be timestamp of the last change of "stSeld"?

Created: 26 May 2014

Status: In Force (green)

Part: Part 7-3 (2010; Edition 2)

Links:

Page: 75

Clause: 8

Paragraph:

Category: No impact on this part

Issue

For all CDC control, data attribute "t" is applied to "q" and "stVal" only. But what about data attribute "stSeld"? Does it mean that "t" is not updated with a change of value of "stSeld"?

If this data attribute is used we have to known when the controllable data object has been selected and when is no more selected.

Proposal

For CDC SPC, DPC, INC, ENC, BSC, ISC, APC and BAC put "stSeld" in the column "data attribute t applies to".

Discussion Created Status
ballot date expired 08 Jun 15 In Force (green)
I Support the proposal from Wolfgang, how the Problem can be solved.

Proposed solution: TISSUE not accepted 		24 Apr 15 Ballot Period
A client keeping the last state can always determine if the event relates to stVal, stSeld or both. Thus the client can locally time stamp stSeld changes, if this is needed in the event log. 04 Nov 14 Discussion (red)
It's more at station level we can have a problem. If we have an HMI with the archiving, and we have a device controlled through SBO command, HMI should receive two events for the status change of "stSeld" attribute after a switch operation .
If timestamp is not updated, so both events will have the same timestamp with differents states of "stSeld" attribute.
 27 May 14 Discussion (red)
Yes, it means that t is not updated when state selected - stSeld - changes.
This is intentional as t determines per definition the last change of stVal, and q only, both relevant for the operation.
It is not important for the operation to know the time of a selection / deselection.
For the diagnostic, the service tracking offers a time stamp of selection / deselection.
stSeld main purpose in to solve the 1-of-n control.

26 May 14 Discussion (red)

 

Privacy | Contact | Disclaimer

Tissue DB v. 23.12.13.1