Comments (7)
I got the following answer from our engineers:
The typical particle size (TPS) is not a function of the other SPS30 outputs, but an independent output. It gives an indication on the average particle diameter in the sample aerosol. Such output correlates with the weighted average of the number concentration bins measured with a TSI 3330 optical particle sizer.
Following this definition, lighter aerosols will have smaller TPS values than heavier aerosols.
The reactiveness of this output increases with the particle statistics: a larger number of particles in the environment will generate more rapidly meaningful TPS values than a smaller number of particles (i.e., clean air).
I hope this cleans things up for you 🙂 Maybe we should add this to the README.
from embedded-sps.
Hi @michapr
What do the other values for PM2.5, PM4 and PM10 show? All 105 I assume since you didn't mention them?
Is this not a middle value? How it will be calculated? (if most particles <= 0.5μm )
I'm not sure about the exact calculation, but I will forward your question on how to interpret the "typical particle size" value.
from embedded-sps.
As sample - actual: 30.75 / 35.2 / 35.4 / 35.4 / 35.4 #/cm³ -> 0.54μm
So I would assume that "typical particle size" is <0.5μm .
Thanks!
from embedded-sps.
According to the datasheet: PMx defines particles with a size smaller than “x” micrometers (e.g., PM2.5 = particles smaller than 2.5 μm).
That means (taking the samples mentioned above):
30.75 have a size up to 0.5 um >> avg. size impact = 30.75 * 0.5
35.2 - 30.75 have a size between 0.5 and 1 >> avg size impact = (35.2 - 30.75) * 1
35.4 - 35.2 have a size between 1 and 2.5 um >> etc
Add the avg size impact values ( 20.325) and divide by total = PM10 = 35.4) gives a calculated avg size of 0.57.
PM0.5 | PM1 | PM2.5 | PM4 | PM10 | avg size |
---|---|---|---|---|---|
30.75 | 35.2 | 35.4 | 35.4 | 35.4 | 0.54 |
0.5 | 1 | 2.5 | 4 | 10 | |
15.375 | 4.45 | 0.50 | 0 | 0 | 20.325 |
0.574152542372881 |
It is not a 100% fit. Maybe they apply different multiplier for size impact, maybe have more information in the sensor than exposed, maybe include a number of the previous measurements in the calculations to prevent the number jump up and down too much between the snap-shots. Maybe Michapr can find out.
I had a sketch running for 175 samples, sample every 3 seconds
The average for the 175 typical size was : 0,575451860465117 um
The average for 175 calculated avg was : 0,583083779069767 um,
Thus a delta of 0,007631918604651 over 175 samples. The error margin of 1.33%. I can live with that.
from embedded-sps.
Thanks, In the meantime I came to the same calculations ;)
Have calculated about 2000 samples within a week - my error margin is also often about 1.5%
If @rnestler agree with this he could close it ;)
Thanks.
from embedded-sps.
BTW: your calculation is not full correct ;)
30.75 have a size up to 0.5 um >> avg. size impact = 30.75 * 0.5
35.2 - 30.75 have a size between 0.5 and 1 >> avg size impact = (35.2 - 30.75) * 1
35.4 - 35.2 have a size between 1 and 2.5 um >> etc
up to 0.5 means between 0 and 0.5 - so it will be 30.75 * 0.4 (as sample, because most will be near 0.5)
for size between 0.5 and 1.0 the middle value is 0.75 .. etc.
PM0.5 PM1 PM2.5 PM4 PM10 avg size
30.75 35.2 35.4 35.4 35.4 0.54
0.4 0.75 1.75 3.25 7
12.3 3.34 0.35 0 0 15.99
0.4517
So it is in a lot of cases a bit away from displayed value ;)
But sometimes it is ok :)
from embedded-sps.
I'll close this for now, feel free to reopen if you have any further questions regarding the typical particle size.
from embedded-sps.
Related Issues (13)
- Arduino platform errors - please use https://github.com/sensirion/arduino-sps / 'sensirion-sps' from Library Manager HOT 30
- use of "stop measurement" HOT 10
- reset Data-Ready Flag HOT 3
- outside usage? HOT 4
- I2C fails to initialise when using with nRF52 DK HOT 5
- SPS30 sensor get serial fail HOT 11
- why so much error in compiling HOT 1
- Getting almost same values for 2p5 to 10p HOT 1
- Driver returning very strange readings. HOT 2
- Getting the values for PM2.5 and PM10.0 is giving me values of 5000+ when using the example application. HOT 4
- Device does not return measurements. Getting serial or device register works though... HOT 1
- Set pointer address does not work for locations greater than 0x0300 HOT 12
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from embedded-sps.