920 Resetable Counter is NOT resetable
- Created
- 19 Sep 2012
- Status
- In Force (green)Closed: the solution is part of the standard. No further comments are taken. Show the workflow
- Part
- Part 7-4 (2010; Edition 2)
- Links
- None
- Page
- 42
- Clause
- 5.7.3
- Paragraph
- Category
- Issue may impact interoperability of implementations of Edition 2
Issue
For the LN GGIO there is a declared DO "CntRs1" with the CDC "BCR".
The semantic of the abbreviation means the same like the decription: "Counter, resettable" but the CDC "BCR" (7-3) means "Binary counter reading".
At LN FCNT there is the same usage but with other description "Counter"
Proposal
Either: change the CDC from BCR to INC
or: change the name form CntRs to CntRd "Counter readable"
| Discussion | Created |
|---|---|
| In Force (green) | 05 Dec 12 |
| Discussion (red) Proposal: Change the DOname of GGIO.CntRs to GGIO.CntVal (multiple instances allowed, presence - optional). Change also the DOname FCNT.CntRs to CntVal (mandatory). | 25 Oct 12 |
|
Discussion (red)
For binary counters, resetting is not a local issue; there is the possibility to do a reste after a freeze. But this is not the same semantic "resettable" as used in other cases (e.g. a OpCntRs - resetable operation counter).
So I would support the suggestion, to rename the DO, but the appropriate name would simply be CntVal - for counter value |
22 Sep 12 |
|
Triage
This was raised as UML issue wg10-0404. Resolution was: GGIO.CntRs and FCNT.CntRs should remain BCR as they are; improve documentation about "resettable": (resetting is a local issue). |
22 Sep 12 |