Issues #657
Publish/subscribe enum with negative value
Added by Richard Schimmel over 3 years ago.
Updated 9 months ago.
Discuss in Upcoming Meeting:
No
Clause Reference:
Part 8 Clause 8.1.2.2
Closed Reason:
--Not Set---
Description
Item 7 from Christophe Camelis list;
I do not understand the problem. A hint would be helpful here Richard.
- Clause Reference set to Part 8 Clause 8.1.2.2
Clause 8.1.2.2 states: "Enumerated values outside the standardized range but within the MMS integer size shall be assumed to be value extensions and shall not cause a protocol error".
So we have to add this to the conformance test
Richard's reference follows:
The size of the MMS data type shall be the minimum size required to contain the maximum standardized value.
The size of the integer is 8 bits for all currently published enumerations.
I think this is good to test that negative enuemration does not cause trouble with the subscribers.
Nevertheless, I do not see the use case where there are more negative values that positive ones - in other words, the smallest negative value forces the size of the enumeration requires a INT16.
- Assignee set to Richard Schimmel
- Priority changed from Normal to Low
Richard to draft test case, probably same as 656.
- Related to Issues #656: Publish/subscribe enum with value > 127 added
- Due date set to 10/04/2022
- Status changed from New to In Progress
- Test Case ID set to sGos9
The issue is not only for the scope of fixed-length GOOSE tests, but also for BER-encoded GOOSE tests.
Additionally, the test procedure shall indicate that the EnumType in the SCD is indicating ord values that are negative, or bigger than 129,...
- Due date changed from 10/04/2022 to 02/07/2023
- Due date changed from 02/07/2023 to 02/21/2023
- Due date changed from 02/21/2023 to 03/07/2023
- Status changed from In Progress to Resolved
- Status changed from Resolved to Closed
- Updated Test Document set to TP1.3
Also available in: Atom
PDF