12-08-2021, 19:39
Hello edr1924,
Since adding an Wakeup command before send any other command to the sensor, worked for you, it will work for others too. I don't see any problem in adding that line on next firmware release.
I may be wrong, however as said by PM, I believe the issue only happen when the sensor was previously used with a software which sets the working period to something different than the default factory setting. If the working period was previously set to 30s per example, then, when the AQM III software tries to initialize it, the sensor still is in sleep mode. The working mode is stored on the sensor, and survives to a power down.
I should have predicted that possibility. Starting the sensor initialization with an Wakeup command makes sense.
Thank you for your experimentations and for sharing them.
Kind regards.
Since adding an Wakeup command before send any other command to the sensor, worked for you, it will work for others too. I don't see any problem in adding that line on next firmware release.
Quote:I think that I have a different version of the SDS011? I read somewhere that different versions behave differently!
I may be wrong, however as said by PM, I believe the issue only happen when the sensor was previously used with a software which sets the working period to something different than the default factory setting. If the working period was previously set to 30s per example, then, when the AQM III software tries to initialize it, the sensor still is in sleep mode. The working mode is stored on the sensor, and survives to a power down.
I should have predicted that possibility. Starting the sensor initialization with an Wakeup command makes sense.
Thank you for your experimentations and for sharing them.
Kind regards.