Historian Raw Float Precision

Hello!

We are trying to understand why we are observing a lack of precision in our raw float values. Our data source is Ignition with Cirrus Link MQTT. In most cases, the raw historian data—when viewed from the Historian tile—displays only 1-3 decimals of precision. There are a few instances where we observe 5 decimals of precision. In all cases, the values are stored as R4 (Ignition Float4/32-bit).

Upon examining the birth message, we identified one of the affected tags. Interestingly, the initial value in the birth message is capped at 3 decimals. It is unclear why this is happening:

{
  "name": "Battery 1/Cell Voltage Average",
  "timestamp": 1738825877285,
  "dataType": "Float",
  "metaData": { ... },
  "properties": {
    "engUnit": { "type": "String", "value": "V" }
  },
  "value": 3.621
}

We used a third-party quick client to subscribe to this tag in real time. This revealed that the value is actually precise out to 16 decimals:

{
  "name": "Battery 1/Cell Voltage Average",
  "timestamp": "1739931062394",
  "isNull": false,
  "properties": {},
  "floatValue": 3.6440000534057617
}

Despite this, when viewing the same tag in the historian tile, it is still limited to 3 decimals, which notably matches the initial value in the birth message.

Curiously we see this pattern of matching initial value from birth message here as well:

    {
      "name": "Battery 1/Power Limit of Discharge",
      "timestamp": 1738825877285,
      "dataType": "Float",
      "metaData": {...},
      "properties": {
        "engUnit": { "type": "String", "value": "MW" }
      },
      "value": 0.20193
    },

And the historian data:

We are looking for some clarification on why this rounding/loss of precision is occurring, and whether it could be related to the birth message, the historian configuration, or some other factor.