- This topic has 4 replies, 3 voices, and was last updated 3 years, 2 months ago by .
Viewing 5 posts - 1 through 5 (of 5 total)
Viewing 5 posts - 1 through 5 (of 5 total)
- You must be logged in to reply to this topic.
// wp-content/mu-plugins/sanitize-uploads.php
A3
HW:108 SW:76
I have had occasional bad readings on the VOC sensor but lately it looks like it is failing (see attachment).
What do you think?
Ken
Definitely does not look normal, I would arrange replacement to check if the problem is inside the sensor itself. If you manage to do that please let us know the results.
Gopher’s right. You might want to request a RMA. The MOX sensor is very low cost, but sadly we need to arrange shipping the unit back and forth. No other way around this.
I have not replaced the sensor all this time and, old as it is, seems to be working. My conclusion is there must be some source out there that is producing intermittent bursts of VOC’s. Also, I have recently seen that, by refreshing the browser page, the spikes go away.
You know that competing sensors (of which there are several) all use 10-minute averages for the default plots. This would flatten out spikes and would greatly improve the appearance of the PM graphs. This would be done at the server end of things I suppose.
This summer, the formaldehyde sensor is – for the first time ever – starting to produce some readings. I wonder if you have changed some software? or if my air is dirtier this year than ever before?
The VOC and formaldehyde readings tend to track each other (mirror image) indicating a common gas is being detected. Probably not actually formaldehyde. Both sensors respond to a a variety of gasses.
Hello Ken,
You can change the mobile average interval yourself, using the “sendint” command via USB. If you increase the sending interval, the data will be averaged prior to upload to server.