580 Eliminate INT128 BasicTypeCreated: 06 Nov 2007 Status: In Force (green) Part: Part 7-2 (2003) Links: Page: 21 Clause: 5.5.2 Paragraph: Table 2 Category: Issue for edition 2 of this part Issue The INT128 datatype seems impractical to implement on almost any computer, but especially on IEDs. There is no standard way to store INT128 values on any modern computer. And the maximum value of an INT128 is larger than anyone is likely to need. The maximum value for an unsigned 64-bit integer is 18,446,744,073,709,551,615 (over 18 quintillion). An INT128 value would be roughly that number multiplied by itself. I won't attempt to even write it. Currently, INT128 is only used for the "actVal" and "frVal" of BCR (Binary counter reading).
Proposal Eliminate the INT128 datatype and use INT32 or INT32U in BCR. The maximum value for INT32U is 4,294,967,295 (over 4 billion). If that is not big enough, add an INT64 or INT64U datatype and use that. The INT64U could handle over 18 quintillion. The INT64 and INT64U types may not be supported as native datatypes on many embedded systems used for IEDs, but it would be reasonable to create software to perform INT64 operations on any 32-bit system.
Privacy | Contact | Disclaimer Tissue DB v. 24.4.30.1 |