Is there a delay or trick to getting the internal air temp sensor value to reflect the bias value I apply. I was able to add a -20 deg F bias several weeks ago, but when I changed it to -30 there was no apparent change to the thermometer display.
I’m wondering if this value is read/updated relatively infrequently, and maybe I just assumed it was every few seconds (or faster).
Not a critical question, just unsure how to interpret an unpredictable response.
The bias values are not applied retroactively, only to new data. But that should arrive within a maximum of 10 minutes. We’ll have a quick look at your data-stream and update this post shortly.
Your last 10 temperature readings were (all times are UTC):
+---------------------+---------------------+--------+
| Received | Timestamp | Temp |
+---------------------+---------------------+--------+
| 2019-08-22 22:46:50 | 2019-08-22 22:46:46 | 88.78 |
| 2019-08-22 22:36:49 | 2019-08-22 22:36:45 | 88.73 |
| 2019-08-22 22:26:49 | 2019-08-22 22:26:44 | 88.69 |
| 2019-08-22 22:16:54 | 2019-08-22 22:16:43 | 88.6 |
| 2019-08-22 22:06:47 | 2019-08-22 22:06:43 | 118.49 |
| 2019-08-22 22:04:05 | 2019-08-22 22:04:02 | 98.48 |
| 2019-08-22 21:58:12 | 2019-08-22 21:58:09 | 98.42 |
| 2019-08-22 21:54:06 | 2019-08-22 21:54:03 | 98.44 |
| 2019-08-22 21:44:07 | 2019-08-22 21:44:03 | 98.35 |
| 2019-08-22 21:35:58 | 2019-08-22 21:35:55 | 98.21 |
+---------------------+---------------------+--------+
This appears to reflect your changes between 22:04:54 and 22:07:28 UTC (you tried a few different values, but your last one was to -30 at 22:07:28).
Note that once you change the bias value, you have to wait for new data to appear before it will be reflected on the main interface (i.e. the thermometer). If the vessel is moving, this will generally occur within 30 seconds. If the vessel is stationary, within 10 minutes.
Hope that clarifies, but please let us know if anything is unclear or is not consistent with what you’re seeing at your end.