RikDrabs
commented
7 months ago 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 https://github.com/opendata-stuttgart/sensor.community/issues/230, or unsubscribe https://github.com/notifications/unsubscribe-auth/AJLIM7EF6OSVXCQYIXT2OEDYTWZWLAVCNFSM6AAAAABDJXNKXCVHI2DSMVQWIX3LMV43ASLTON2WKOZSGEZTKOBSGE3DSOI . You are receiving this because you are subscribed to this thread.Message ID: @.***>
ricki-z
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.