-
Notifications
You must be signed in to change notification settings - Fork 43
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for the Sensirion SEN55 sensor (PM1 + PM2,5 + PM4 + PM10 + Temp + Humi + VOC + NOx)? #230
Comments
In the mean time I saw this topic is already on the forum, and partially
solved.
The database remains to be adapted, also the map doesn't provide support
for VOC and NOx.
The sensor driver has already been done, and is apparently working in V1.34
of the software for DNMS, in which I'm also interested to deploy in Belgium.
How to proceed?
Does this notification needs to remain open, or are these requests now
handled through the forum only ?
Op do 15 feb 2024 om 08:23 schreef Rik Drabs ***@***.***>:
… This relatively new sensor (2022) has a similar communication protocol as
the SPS30, which is supported already.
Adapting the sensor software to the SEN55 should then not be too
difficult, or take too much space in the flash.
The only problem lies ahead in the data path, which has no support yet for
VOC or NOx (database, map, etc)
I find this an interesting addition to the features of the system.
Air quality is not only determined by the particulate matter in the air,
but also by the VOC and NOx in the air.
Adding these could mean a restart of intense activities around
sensor.community.
And in my 5,5 years experience with air quality problems around the PM
sensors of sensor.community, I had flagrant cases of air pollution with
both exterior VOC and NOx, harming people in their daily life and in their
health, while local government looked away, even accused the victims of
making it all up, while telling "WE have no meters, and WE smell nothing,
so there is NO problem".
Even a local stand-alone VOC meter in the hands of the victims, showing
excess values linked to changing health conditions, didn't change the
opinion of the local government.
There is really a need for VOC and NOx measurements on a wide scale, like
in the sensor.community network, to help these people.
So situations can be compared, and local problems brought to daylight.
If time is the problem, I would like to apply to make the simpler
adjustments to the sensor software via pull request in a separate branch.
—
Reply to this email directly, view it on GitHub
<#230>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AJLIM7EF6OSVXCQYIXT2OEDYTWZWLAVCNFSM6AAAAABDJXNKXCVHI2DSMVQWIX3LMV43ASLTON2WKOZSGEZTKOBSGE3DSOI>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
Such requests should be discussed through the forum. It seems easier for many people to use the forum than to use github. |
OK.
Op ma 19 feb 2024 om 19:36 schreef Rajko Zschiegner <
***@***.***>:
… Such requests should be discussed through the forum. It seems easier for
many people to use the forum than to use github.
And we should try to avoid spreading themes over different sites.
—
Reply to this email directly, view it on GitHub
<#230 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AJLIM7HO2NMOW4TMSV6E5A3YUOLTLAVCNFSM6AAAAABDJXNKXCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNJTGAYDEOJXGA>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This relatively new sensor (2022) has a similar communication protocol as the SPS30, which is supported already.
Adapting the sensor software to the SEN55 should then not be too difficult, or take too much space in the flash.
The only problem lies ahead in the data path, which has no support yet for VOC or NOx (database, map, etc)
I find this an interesting addition to the features of the system.
Air quality is not only determined by the particulate matter in the air, but also by the VOC and NOx in the air.
Adding these could mean a restart of intense activities around sensor.community.
And in my 5,5 years experience with air quality problems around the PM sensors of sensor.community, I had flagrant cases of air pollution with both exterior VOC and NOx, harming people in their daily life and in their health, while local government looked away, even accused the victims of making it all up, while telling "WE have no meters, and WE smell nothing, so there is NO problem".
Even a local stand-alone VOC meter in the hands of the victims, showing excess values linked to changing health conditions, didn't change the opinion of the local government.
There is really a need for VOC and NOx measurements on a wide scale, like in the sensor.community network, to help these people.
So situations can be compared, and local problems brought to daylight.
If time is the problem, I would like to apply to make the simpler adjustments to the sensor software via pull request in a separate branch.
The text was updated successfully, but these errors were encountered: