Designing a sensor is easily the most challenging, time-consuming part of this project. It might also be the most costly based on the R&D required. This blog post isn't going to go into the nitty gritty technical requirements of a sensor (sorry to all tech lovers out there), but it does discuss the overview for laypeople trying to understand the device's basic parameters.
If you're still keen on learning the nuts and bolts of such a device, that'll come later once we unveil the gist of the blueprint itself.
Size
Most air quality sensors are large pieces of machinery, resembling the size and look of a backup power generator. This is to keep them well-insulated from the elements, and because of the large quantity of data it collects. It may also house the data collection device itself, thus increasing its bulk substantially. The method of collection used by these pieces also require significantly more parts.
LeapSense, however, is developing a much smaller sensor--think the size of your internet modem at home. The size reduction is achievable for a few reasons; for one, LeapSense is not interested in collecting many of the data pieces obtained from larger devices. Our collection method uses much lighter, nimble inputs (optical).
Detection
Air quality sensors measure a variety of units, including O3, CO, PM10, and PM2.5. The LeapSense device will focus on detecting PM10 and PM2.5, as these are the particulate matters most relevant to traffic congestion, health problems, and industrial output (ie, the issues we wish to solve). When discussing "air pollution" as a topic, this is usually understood to mean a region's PM10 and 2.5 levels.
Power Requirements
The sensor will function using a combination of renewable batteries and solar power. With a quality lithium battery, the charge may last between 6 months and 2 years. Its solar power device will then kick in to recharge the battery--this means that little, if any deployment will be necessary for the purpose of regenerating the unit's power. Solar power is an excellent choice for Chennai given its consistently sunny weather.
Packaging
Perhaps surprisingly, packaging is as important as the device itself. It must protect the unit but not impinge on its readability--a tough balance from an engineering standpoint. Packaging must also be done to withstand the city's heat, notorious dust and humidity. LeapSense hasn't yet appointed a materials engineer, but we're keen on merging their expertise with that of our existing team's.
Data Frequency
This requirement relates to how often the sensor should transmit feedback: twice a minute? Every hour? twice a day? Twice a week? Once a month? The more frequent the better, but this has to be balanced with the power requirements and ease of data transmission. The frequency should give insight about how pollution levels change with seasonality, weather patterns, traffic, and wind speed.
Because LeapSense is focusing on hyper-local, specific data collection, our device will ideally collect readings every ten minutes. This frequency will provide crucial information such as the best days to venture outdoors, the Chennai weather most conducive to clean air, and it can also inform citizens if routine events are occurring that cause a spike in pollution (such as garbage burning).
Data Transmission
This requirement is all about getting the sensor readings from the unit translated and sent into an easily understood format. Achieving this requires installing wireless capability into every sensor unit and will happen through analog digital converters sending the information to the GPRS backhaul.
GPS
In order to deploy sensors across the city, each unit must be equipped with a GPS functionality. Otherwise, determining the source of the readings is impossible. GPS is also useful if the device has been removed but is still transmitting info, as may be the case in the event of theft or even innocuous maintenance. Anyone analyzing the data can check the location if the sensor is transmitting data highly inconsistent with previous readings. If the GPS coordinates differ, then the data may be tossed out and the results won't interfere with the pool.
Cost
The range of cost is as varied for sensors as it is cars. The variability is based on similar criteria, too: quality of parts, durability, functionality, and use. Some air quality sensors act like military-grade Hummers--they are industrial, high-use, bulky, exceptionally precise, capable of performing a variety of functions, expensive, and high-tech. Others are like a Honda, where they are mass-produced, simple in its functionality (getting from point A to point B), low-cost, light weight, and produced for the masses.
In terms of the sensor we're designing, it's very much aligned with the Honda functionality (or Toyota, Maruti, Ford, VW, or whatever other car brand one wishes to insert into this analogy). Low-cost is a critical aspect of the LeapSense device. The figure we have in mind is $100 per device. We know this is not at all achievable in the prototype and testing phase, but can be achieved through high volume manufacturing.
Maintenance
The device should be low-maintenance. With so many sensors deployed throughout the city, it's important that the device can be left alone for months--even years--without requiring removal either for power regeneration, parts/packaging failure, or data transmission errors. Quality of inputs, long-lasting power sources, and secure deployment will no doubt assist with low maintenance.
If you're still keen on learning the nuts and bolts of such a device, that'll come later once we unveil the gist of the blueprint itself.
Size
Most air quality sensors are large pieces of machinery, resembling the size and look of a backup power generator. This is to keep them well-insulated from the elements, and because of the large quantity of data it collects. It may also house the data collection device itself, thus increasing its bulk substantially. The method of collection used by these pieces also require significantly more parts.
LeapSense, however, is developing a much smaller sensor--think the size of your internet modem at home. The size reduction is achievable for a few reasons; for one, LeapSense is not interested in collecting many of the data pieces obtained from larger devices. Our collection method uses much lighter, nimble inputs (optical).
Detection
Air quality sensors measure a variety of units, including O3, CO, PM10, and PM2.5. The LeapSense device will focus on detecting PM10 and PM2.5, as these are the particulate matters most relevant to traffic congestion, health problems, and industrial output (ie, the issues we wish to solve). When discussing "air pollution" as a topic, this is usually understood to mean a region's PM10 and 2.5 levels.
Power Requirements
The sensor will function using a combination of renewable batteries and solar power. With a quality lithium battery, the charge may last between 6 months and 2 years. Its solar power device will then kick in to recharge the battery--this means that little, if any deployment will be necessary for the purpose of regenerating the unit's power. Solar power is an excellent choice for Chennai given its consistently sunny weather.
Packaging
Perhaps surprisingly, packaging is as important as the device itself. It must protect the unit but not impinge on its readability--a tough balance from an engineering standpoint. Packaging must also be done to withstand the city's heat, notorious dust and humidity. LeapSense hasn't yet appointed a materials engineer, but we're keen on merging their expertise with that of our existing team's.
Data Frequency
This requirement relates to how often the sensor should transmit feedback: twice a minute? Every hour? twice a day? Twice a week? Once a month? The more frequent the better, but this has to be balanced with the power requirements and ease of data transmission. The frequency should give insight about how pollution levels change with seasonality, weather patterns, traffic, and wind speed.
Because LeapSense is focusing on hyper-local, specific data collection, our device will ideally collect readings every ten minutes. This frequency will provide crucial information such as the best days to venture outdoors, the Chennai weather most conducive to clean air, and it can also inform citizens if routine events are occurring that cause a spike in pollution (such as garbage burning).
Data Transmission
This requirement is all about getting the sensor readings from the unit translated and sent into an easily understood format. Achieving this requires installing wireless capability into every sensor unit and will happen through analog digital converters sending the information to the GPRS backhaul.
GPS
In order to deploy sensors across the city, each unit must be equipped with a GPS functionality. Otherwise, determining the source of the readings is impossible. GPS is also useful if the device has been removed but is still transmitting info, as may be the case in the event of theft or even innocuous maintenance. Anyone analyzing the data can check the location if the sensor is transmitting data highly inconsistent with previous readings. If the GPS coordinates differ, then the data may be tossed out and the results won't interfere with the pool.
Cost
The range of cost is as varied for sensors as it is cars. The variability is based on similar criteria, too: quality of parts, durability, functionality, and use. Some air quality sensors act like military-grade Hummers--they are industrial, high-use, bulky, exceptionally precise, capable of performing a variety of functions, expensive, and high-tech. Others are like a Honda, where they are mass-produced, simple in its functionality (getting from point A to point B), low-cost, light weight, and produced for the masses.
In terms of the sensor we're designing, it's very much aligned with the Honda functionality (or Toyota, Maruti, Ford, VW, or whatever other car brand one wishes to insert into this analogy). Low-cost is a critical aspect of the LeapSense device. The figure we have in mind is $100 per device. We know this is not at all achievable in the prototype and testing phase, but can be achieved through high volume manufacturing.
Maintenance
The device should be low-maintenance. With so many sensors deployed throughout the city, it's important that the device can be left alone for months--even years--without requiring removal either for power regeneration, parts/packaging failure, or data transmission errors. Quality of inputs, long-lasting power sources, and secure deployment will no doubt assist with low maintenance.
nice we are offering
ReplyDeleteair quality sensor manufacturer visit this page