This is a bit strange, you should get a perfect match on formaldehyde. Please note the server returns it in PPB, as the local embedded webserver returns it in PPM. Make sure there are no digits lost there due to Integer operations trimming the complete values. Also make sure you local read operations are completed successfully, it is possible you sometimes get timeouts and your values stay 0.

Regardless of this, please note that the correct way to go about this is to use the Server API. You can find examples and full details on http://www.uradmonitor.com/dashboard

The local JSON is only offered as a bonus and for quick debug tests. It is important you use the Server API to get meaningful readings. Also because there is a calibration layer implemented only on the server side, that does some compensations for temperature and humidity on the models with the sensor placed inside (to correct aberrations caused by internal heating), but it also computes PM1 and PM10, and also VOC AQI otherwise not available locally.

Let me know if you need any help migrating to the Server API.

Radu

Type is the device class as defined in specs v1. Originally the model A was 1, the A2 was 4, the KIT1 was 5 , the D was 6 , the A3 was 8.
It was the first digit of the Device ID. You’re using an A3 so it starts with 8.

The second digit was a code for the Geiger tube used. 1 was SBM20 while the 2 was SI29BG. 4 was LND712. So your device ID starts with 82.

Having the Geiger tube encoded in the device ID started to loose meaning with the recent units that only do Air Quality monitoring and have no radiation sensors. So the device class defined in specs v2 became two digits big. As an example, the device class for an INDUSTRIAL is 14.

HW is the hardware version. Each model was multiple iterations. With the A3, HW103 and HW105 were the most common. You can still see a first HW100 (first iteration) here: https://www.uradmonitor.com/?open=82000001 . This particular unit is not only part of the first production batch, but it is also the very first uRADMonitor A3 unit produced. It is installed on a bus in the city of Cluj Napoca. Its data is linked to an external GPS module so we have the Air Quality measurements mapped to location. Here’s how that looks: http://www.uradmonitor.com/cluj

SW is the firmware version, the actual software running on the devices themselves. This can be updated from time to time, as I push out newer software versions to fix bugs or add new features: https://www.uradmonitor.com/firmware-upgrade-a3-wifi/

VOL is the voltage on the Geiger tube. It is configured to 380V in software, as the Geiger tube needs this High Voltage to run. It is low current, so you cannot electrocute yourself, however touching the internals while the device is running can give you a little shock. So don’t do it.

VOC is the Volatile Organic Compounds sensor. You can read about those here: https://www.uradmonitor.com/products/?sel=4 under the “IMPACT” tab or in the datasheet here: https://www.uradmonitor.com/wordpress/wp-content/uploads/2017/02/datasheet_a3.pdf

WDT is the watchdog, a timer that will reboot the device when it reaches a certain value. Normally this doesn’t happen, as periodically the Watchdog is reset to 0 if all critical operations are successful (mainly reading the sensors and communicating the data to the server). Resetting the watchdog is called “patting the dog”.

INT is the time interval for sending data. It is set to 60seconds on the A3. This means that every minute your A3 will send data. This can be customised.

HTTP is the server’s return code when the A3 send some data. 200 means OK. Anything else means error. There can be various errors codes. These are the standard HTTP Error codes, you can find documentation about them online if interested.

Let me know if you have any additional questions here, and thanks for your interest. This is much appreciated.

Radu

Greetings all.

Thanks to the generosity of Radu, I am the proud operator of the following devices:

https://www.uradmonitor.com/?open=110000F8 (This is a fixed Model A that is currently undergoing some tests; its geographic address is 7101 Ottawa Rd NE, Albuquerque, NM 87110 rather than Grants as it currently displays on the map)

https://www.uradmonitor.com/?open=51000016 (This is a KIT1 that is installed on the bedroom wall at my primary residence, and displays location correctly on the map. Its reading is high for the area due to background from radioactive collectibles throughout the home, so please do not interpret this measurement as representative of Albuquerque.)

Personal background
I’m a nuclear engineer (currently titled “Health Physicist”) at a US government facility, and live in Albuquerque, New Mexico. I also teach an introductory nuclear engineering course at the University of New Mexico. Most of my background has been involved with particle accelerator applications. Avocational pursuits have included building fusion neutron generators (I was an active admin / participant on the http://www.fusor.net forums for most of the last two decades); traveling to radioactive destinations such as Chernobyl, Semipalatinsk, and Fukushima; and collecting radioactive items (I have a personal blog linked in my profile where that stuff tends to be discussed). I’m also an amateur radio operator (KF4KIG).

I have a strong interest in radiation detection and measurement, and some ideas for expanding on the uRADMonitor hardware to create a high-sensitivity neutron detection station, which should provide some insights into secondary cosmic ray backgrounds and their variation.

I look forward to contributing to and interacting with this community.

Best regards,
Carl Willis

@Wolferl is right, and his comment made me look at something else. I don’t know how I checked this first, because I had it on my mind: https://www.uradmonitor.com/tools/dashboard-04/?open=11000007

The duty cycle is too high. The firmware reboots the unit when the duty cycle reaches 80% . So this is why it appeared as having network issues, the reboot happened right after Ethernet initialisation (including DHCP lease), just to take everything all over again.
This is not the true duty cycle received by the switching transistor because there is a second blocking transistor that quick closes the gate so it is not dangerous for the parts even if the value seems high.

The model A doesn’t have a voltage multiplier, so the inverter works harder to jump from 5V to 380V needed for the tube. The ferrite core’s permeability is affected by temperature, but I see the weather is chill there. Replacing the inductor would help, but let’s put software first: I can provide a modified firmware that lowers the switching frequency and achieves higher voltage with less effort. It will also remove It approaches the audible spectrum though, as we are already at about 15.5KHz

Please check your mail.

Thanks both for your help and patience!

Hi Richard, I will see what can be done, others requested this as well.
I was reluctant to allowing such long strings due to the limited amount of RAM on the microcontroller of the model D.

Dear Radu

can you change my flag to Switzerland for my Unit 82000076 (A3 Model)

thx

Hello Costo, thanks for the message, yet I must admit I have little success in understanding what troubles you: you can still open the map with radiation selected by default: http://uradmonitor.com/?sensor=cpm

The model A is still part of the portfolio, being one of the best products designed so far. So is the A3, which continues the radiation monitoring legacy.

Pollution affects more people (about 7million/year worldwide and about half a million per year in Europe) than radiation related incidents did during history. And the numbers are increasing considering where our society and way of living is going.

So the project tries to help more people, adding more sensors and leveraging on the mature IOT infrastructure developed so far. What’s wrong with that?

Hi there,

Are you interested in the model A unit?