Hi,

Technically it is also a “standard Property” that is optional to any Variable node: https://reference.opcfoundation.org/Core/Part3/v105/docs/5.6.2 (with some limitations). For the EUInformation Structure itself see: https://reference.opcfoundation.org/v104/Core/docs/Part8/5.6.3/.

SDK contains some help from the ” “Codes for Units of Measurement” published by the “United Nations Centre for Trade Facilitation and Electronic Business”” in in com.prosysopc.ua.stack.core.StandardEngineeringUnits. It is .. maybe not the easiest to use, but it has static methods: ‘List getAll()’, ‘EUInformation getByCommonCode(String commonCode)’ and ‘getByUnitId(int unitId)’. There are .. a lot of units, but here the StandardEngineeringUnits.DEGREE_CELSIUS and DEGREE_FAHRENHEIT are most likely the ones you look for. A “°C or °F” from a different “EUInformation”-namespace than the “https://opcfoundation.org/UA/units/un/cefact” might mean a different thing (doublecheck does the euromap say anything about this, if not I would assume it to mean this one). And it probably would be better to use the namespace+unitId instead of any displayname/desription for other than visualization purposes. But in general I would sort of say it is the same thing with localization, these are features added to the spec, but possibly like never (yet) used.

1. No, it is just extra info about the “type/kind” of the value, so here it is either °C or °F, but there are no automatic conversions (spec-wise). You can only set one of them. In the localization the locales are transmitted as part of the ActivateSession; there is nothing similar for this. In theory client can of course convert values by itself, but it would be a purely client-side thing.

2. It means the literal value given (by the server maker etc.) can either be given/set as farenheit or celcius and the EngineeringUnits Property shall be set to the same so that there is no confusion for clients which one it is. (so if you set it in celsius, you would also use StandardEngineeringUnits.DEGREE_CELSIUS as the EngineeringUnits).

3. For units of measurement, not that I know. For currency it would seem at some point this was added: https://reference.opcfoundation.org/Core/Part3/v105/docs/8.61.