Forum Replies Created
Would love to see that picture in higher resolution!!
This can happen if the unit is offline for the requested time interval.
Hi Adam, thanks for the clarifications. You can use your current firmware.
Starting with HW106, the A3 measures PM1, PM2.5 and PM10 . More details here: https://www.uradmonitor.com/producing-the-uradmonitor-a3/ and here https://www.uradmonitor.com/the-8th-model-a3/
Yes, time’s always an issue. Would you like to start the post now? Seems like you have some interesting things to share with the community!
Like Wolferl very well said, you won’t be able to use WPA3 with relatively limited embedded hardware, but WPA/WPA2 will work just fine.
What is your current wifi config?
Done, please confirm. Additionally you can also use the USB command “setmute”,”1″ , details here: https://www.uradmonitor.com/wordpress/wp-content/uploads/2019/01/uRADMonitor_USB_commands_comp.pdf
Please see the other thread on this.
I understand that, as I sometimes have a few of them running in parallel. The “Smoggie” has a smaller fan, see datasheet attached. For the A3 it might be possible to increase the sending interval and use powersave. With this setup, the unit will do the measurements, then go to sleep (including the fan) for the amount of time you define. Would this work?
The last A3 with Gamma sensor was HW105. Since HW106 it was removed in favour of an ozone sensor making it exclusively for Air quality monitoring.
See “future directions” on https://www.uradmonitor.com/producing-the-uradmonitor-a3/
Or the HW108 (current) datasheet: https://www.uradmonitor.com/wordpress/wp-content/uploads/2019/01/datasheet_a3_v107_en_comp.pdf
You can change the LAN IP with your DHCP table, as for the port, I could do that for you – providing a modified firmware version. There’s a promo if you want one now: https://www.uradmonitor.com/products/?sel=4
Would a built in POE still be needed given these excellent alternative solutions?
Thank you David for this nice contribution!
The VOC is not the easiest thing to interpret. You can read more on how a VOC sensor works: https://www.uradmonitor.com/metal-oxide-voc-sensors/
When Bosch manufactured their VOC capable BME680, they also provided a library that would compute a score 1 to 500 to do some estimations on the raw VOC levels. Sadly, this library was never integrated in the uRADMonitor products, it was too big for these embedded systems. On the other hand, current uRADMonitor devices are not using the BME680 anymore, it was too susceptible to failure.
The way that lib worked was that it kept a given interval of raw VOC history data. It then used it to compute a baseline and have a reference point to any upcoming raw VOC reading.
I implemented a similar mechanism for the VOC AQI . The last 24 hours of VOC raw data is analysed and the interval min and max are kept. Any new VOC value is compared against the two, and scaled across a 1-500 interval.
This approach worked amazingly well, and generated perfect alignments with other sensors, like the formaldehyde one. This was impressive as we are talking about two separated sensing elements, based on completely different detection technologies. See it here: https://twitter.com/RaduMotisan/status/1067894752027312128
There is a university in Canada currently using several A3 devices for research on how the VOC can be better used.
Sadly, this is most likely a formaldehyde sensor failure. Your unit variant uses analogue connection to sensors, so there is little we can investigate here. Newer A3’s communicate with the formaldehyde sensor via a serial connection.
Drop me an email on email@example.com if you want me to service it.