I stumbled upon a post in Reddit from someone who used something I never noticed in AQS to set up a very clever way to get around the 12-hour shared memory limit in the free version of HWINFO. I do not need to employ this “cheat” since I have a HWINFO lifetime license, nor do I endorse doing so, but the way he did this leveraged a behavior in AQS that I do not understand. This led me to investigate what happens in AQS when shared memory is changed form enabled to disabled.

On my system, sensor data is imported from HWINFO via shared memory and displayed on an overview page. If I deactivate shared memory, the overview page continues to display values for about 26 seconds. A sensor data value from shared memory used as a Data Source in the Playground continues to display a value for about 36 seconds. These times are approximate and not always the same. In both cases (overview page and playground data source), I think the value displayed is the last value imported before shared memory was deactivated.

In the overview page, after ~26 seconds, the imported sensor data values change to “- -“. For the playground data source, instead of the sensor data changing to “- -“, it changes to the value 100. It doesn’t matter if the sensor data is a temp, voltage, current, wattage, etc., or what its normal value and range are. About 36 seconds after disabling shared memory, the value of the playground data source always changes to the value 100. This behavior is a key part of the guy's shared memory time limit work-around.

1. Why does AQS continue to display sensor data imported from HWINFO for almost 30 seconds after the shared memory is deactivated?
   
2. Is AQS displaying the last imported value during this time?
   
3. Why do the imported sensor values in overview pages change to “- -“ but in the playground they always change to the value 100?

Zitat von »Peter von Frosta«

There are some values in the Playground you can change for any Input, e.g. the time how long the last value will be displayed before the "emergency" value will be taken (in german: Rückfallzeit and Rückfallwert).

Thanks for your response. You are right and I totally forgot about the fallback value for a data source in the playground which is set to 100 by default. This explains why it always switches to 100. It also has a fallback time which is set to 10 seconds by default. It appears that the fallback countdown does not start until the values in the overview page switch to “- -“, which on my system occurs about 26 seconds after shared memory is deactivated.

Zitat von »Peter von Frosta«

The Time before changing to "--" can not be manipulated (afaik), because this is a value that is fix implemented in the AS Software.

The delay is also not consistent. On my system, it’s usually 26 seconds but sometimes it's less than 26 seconds, and sometimes it’s over 30 seconds. In all cases, the fallback timer does not start counting down until after the numbers in the overview page switch to “- -“. The minimum fallback time is 3 seconds but AQS will never switch to the fallback value that fast because the 3-second countdown does not start until after the ~26 seconds that it takes for the values in the overview page to switch to “- -“. I used the Shared Memory Viewer utility to confirm that HWINFO stops sending data to shared memory as soon as the Shared Memory Support checkbox is cleared and “OK” is clicked. The delay between disabling shared memory and starting the fallback timer and displaying “- -“ in an overview page is definitely in AQS. Due to this delay, a data source in the playground will not switch to its fallback value for at least 29 seconds despite being set to the minimum 3 seconds.