[SOLVED] Option to activate/deactivate the PM2005 particle sensor

[stephane]

Hi Vladimir!

I have the CDM7160 + PM2005 sensor.
I would like to know my CO2 rate in my chamber during night but the PM2005 particle sensor is too noisy.
Is it possible to temporarily disable it ?

Thanks a lot for your help 

[admin]

yeah, just give me a day or 2, i also noticed that it is a bit noisy especially with the turning on and off and in quiet environments.

How would you prefer it ? manual deactivation, or some "quiet period" e.g. from 22 to 8 ? that you can specify in the config (the time would be read via the wifi connection)

[stephane]

I think that a on/off manual option will be a good start.
And given the noise generated, if I could choose the time period which the sensor makes its measurement (say by example one measure each 10 minutes), it will be perfect for me 

In any case, thank you for your investment 

[admin]

Alright, i believe this can be done as well (currently i am using some default mode in which the sensor operates, and this is why i need some time to check how to switch the mode, and what the consequences are)

[alexei]

(10-05-2016, 01:34 PM)admin Wrote: yeah, just give me a day or 2, i also noticed that it is a bit noisy especially with the turning on and off and in quiet environments.

How would you prefer it ? manual deactivation, or some "quiet period" e.g. from 22 to 8 ? that you can specify in the config (the time would be read via the wifi connection)

is that this motor sound occured every minute? if yes - please add ability to reschedule it for quiet hours!

[admin]

(10-16-2016, 08:16 AM)alexei Wrote: is that this motor sound occured every minute? if yes - please add ability to reschedule it for quiet hours!

yeah, this is it. i will add it, just that this thing with the EMI intolerance of some of the CDM7160's took all my time in the last week

[admin]

I just made an update to support quiet hours. i still haven't integrate it with the UI though, maybe in the next 1-2 days i will do
but if you want to give it a try, you need to send two commands via the config tool

pm2005quiet 20:00,08:00,180

this will turn on quite hours from 20 - 8h, and 180 is the timezone offset from GMT (e.g. 3 hours), also it could be -180.. etc (usually the config tool would set it)
for now - daylight changes are not reflected

pm2005int 0,3600

set the interval to measure in active and quiet time in seconds - first is active then quiet
anything below 300 (5 minutes) will turn on Dynamic mode - in this mode, the device turns on the fan for 36 seconds, then off for 24 - this is one cycle. The next cycle - it turns it on and if in the first 6 seconds the change in the dust levels was negligible it turns the fan off and then retries in 54 seconds - else it continues a normal cycle.

Anything above 300 seconds will set the interval to so much seconds, and at the start of each interval - the device will turn on the fan for 36 seconds

you can update to the latest version and give it a try if you like using a command

otah

[stephane]

Hi Vladimir !

I have quickly tested yesterday night but the quiet mode was not working. However I have done correctly updated the device with the last version before test.
My command was pm2005quiet 21:00,07:00,60 


I have also tried this second command : pm2005int 350,3600 but I'm not sure to have well understood.
With my command the device should be active during 350 seconds and then in quiet mode during 3600 secondes, correct?

[Vladimir Savchenko]

it is rather
350 seconds - measurement interval during active mode : 7-21
3600 seconds - measurement interval in quiet mode 21-7

in each interval - the first 36 seconds the fan works and then is off
I will check again if something could be wrong... try to enable debug mode with 'debug' command.. and then press the Test Configuration button.. and paste the log output

[stephane]

ok it's clear for me now. 
But yesterday night at 23:00, I've heard the noise fan every 350 seconds whereas the interval should have been every 3600 seconds.

I will give a another try, may be I have input the second command before the first? Probably that has made the misfunction.