Hello, Looking for better internet friendly solution for pressure monitoring which we want to use in transistor manufacturing industry where we are working as technician, As per suggestions on google about IOT device we bought particle photon and with help of documentation we are progressing towards the solution we want to analyze, for pressure monitoring we found barometer sensor https://store.ncd.io/product/lps25hb-mems-pressure-sensor-260-1260-hpa-absolute-digital-output-barometer-i2c-mini-module/ which we are thinking to buy and start implementing on it,
But for push notification I read some of the post and need to know minimum time which photon should take to respond the pressure readings on particle console which should be precise and quick to use this kind of solution with industrial pressure system,
Because of newbie and having very few knowledge about this area any kind of leads or some example which help us to make this kind of solution will be very helpful.
Could you elaborate a bit more on that?
What exactly do you mean or where did you read that?
What would be the demands your setup would need to meet?
Hello @ScruffR
Its like, When ever there will be some change in air pressure then the criteria of sending data from sensor to cloud should in microseconds or less than that like if there will continuous decrease or increase in air pressure then continuously I ll be able to check the data which I am not sure how much this process takes place
I'm not quite sure if that really makes sense. What do you consider a change in air pressure?
Have you got a sensor that has a micro or even nano bar precission?
What's your tolerance on change of pressure?
How volatile would you expect your pressure change to be?
Since barometric pressure is something rather difficult to measure exactly the time factor of actually reporting any change should not be the prime concern.
If you were intending to monitor the decompression rate of a popping balloon, then I'd expect micro seconds to be interesting, but in "normal" atmospheric conditions milliseconds or even seconds should not pose any considerable issue.
Also what would you do in case of an unexpected change?
Could react and counteract in microseconds?
Just an FYI, I took a look at the datasheet provided on the ncd.io site. It looks like that sensor runs in I2C fast mode (400kHZ) and it would take a minimum of 57 bits to get one reading from thesensor. 57 Bits / 400 kHZ = .0001425 seconds = 142.5 uSec.
When you transmit to the cloud, you are at the mercy of network conditions. You should measure a round trip ping response. When I ping particle.io (although the device would probably be contacting api.particle.io or some variant) from my wired desktop, I get 15 mSec. I’m sure a ping from my wireless network would have higher latency. So your response time cannot be any faster than a read from the sensor and a round trip ping to the Particle cloud. And if you don’t have SLAs with every network between you and Particle, then there’s no guarantee that the ping time will be stable.
Your desire for microSecond responses using the Particle cloud is unrealistic. You haven’t stated your full use-case but I would not use cloud communication for super critical work especially if it involves human safety.
And to add to the excellent comment made by @ninjatill, industrial controllers do critical control locally, not over a network (not to be confused with a local bus). Otherwise, life, safety or materiel loss will be at risk.
Just to reiterate what has been said, the problem that you are trying to solve should not be done with a Photon-style IOT device.