WeatherDuino Forum

Hi Developers,

As per my Davis AirLink, I am aware that the 1,3,12 & 24 Hour averages reset on power cycling.
I find this slightly annoying with my AirLink and the similar situation applies with the AQM III.

The thought I had was for avaerages to be periodically saved to NVRAM??? on the ESP32 periodically and then reloaded at boot.

A check could be made as to the saved time Vs the boot time and if under say 5 minutes then they could be deemed valid and then restored.
If more than 5 minutes old, then discarded.

Other option would be a web-page reset option, but that could well require extra code.

Also with regards to the dust sensor read interval of 10 minutes, is there any problem with lowering it's value to say 1 or 2 minutes?
I am using Sensirion SPS30 Sensors & understand they have a very long life span quoted on the datasheet as > 10 years @ 24 hour operation.
 

Just not sure how a one minute interval would time in with the 40 second startup wait time.

Also I notice that the two Leds on the PCB receive very little mention in the code.
Just the pin definitions & the Fade option for Led1.

Do others have any suggested uses to which they can be put that are of value?

Thanks

Phil.

(30-09-2021, 08:19)Phil23 Wrote: [ -> ]Hi Developers,

As per my Davis AirLink, I am aware that the 1,3,12 & 24 Hour averages reset on power cycling.
I find this slightly annoying with my AirLink and the similar situation applies with the AQM III.

The thought I had was for avaerages to be periodically saved to NVRAM??? on the ESP32 periodically and then reloaded at boot.

A check could be made as to the saved time Vs the boot time and if under say 5 minutes then they could be deemed valid and then restored.
If more than 5 minutes old, then discarded.

Hi Phil,

I understand your suggestion, however even when using some level of wear levelling, NVS is best used to persist things like configuration information that doesn't change frequently. It's not a great choice for storing information that's updated often.
If you want to know why you can search on google.

(30-09-2021, 08:19)Phil23 Wrote: [ -> ]Also with regards to the dust sensor read interval of 10 minutes, is there any problem with lowering it's value to say 1 or 2 minutes?
I am using Sensirion SPS30 Sensors & understand they have a very long life span quoted on the datasheet as > 10 years @ 24 hour operation.
 

Code:

const uint8_t readInterval  = 10;
const uint8_t readsPerHour  = 60 / readInterval;

Just not sure how a one minute interval would time in with the 40 second startup wait time.

Its highly recommended to not change that setting, otherwise it would have been placed on the Config_Options.
Why you are thinking on changing things, even before having it running for time enough to compare the resulting AQ Index with your AirLink?

On the large majority of situations, the AQ Index resulted from the 1,3,12 & 24 Hour averages isn't much affected by doing a measure every minute or every 10 minutes. Exception may be when used very near of an high traffic road. On rural zones, doing measurements every minute doesn't make sense at all.

For health purposes, the most significant is the AQ Index resulting from the 12 or 24 hours averages.

Quote:... life span quoted on the datasheet as > 10 years @ 24 hour operation.

In just an year of operation the amount of dust that becomes accumulated inside the read chamber of a dust sensor which runs 24/7 can be quite high... dust doesn't reduce the life span, but reduces precision.

The AQM-III runs the fan just four minutes on each hour...

(30-09-2021, 08:19)Phil23 Wrote: [ -> ]Also I notice that the two Leds on the PCB receive very little mention in the code.
Just the pin definitions & the Fade option for Led1.

Here is a explanation of the LED functions:

https://www.meteocercal.info/forum/Threa...0#pid16190

Rgs.