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

so, i just put together the uradmonitor kit1, but i don’t have an isp programmer to upload the hex. but i have a lots of arduinos around…

this guide will show you how to upload the hex file to the uradmonitor kit1, using an arduino uno r3 + windoze

you will need:
– arduino uno
– 6 male to female jumper wires
– latest arduino ide
– hex file

please note: this article is for arduino uno r3, i will not explain here how to use other models. however, with a little googling + thinkering it is not complicated to adapt. for other mcu you can start here.

also, be sure to use tightly fitting jumper cables, you do not want to lose power or data while uploading the hex file! do not move / touch the setup while uploading!

steps:

0) download and install the latest arduino ide + drivers (arduino.cc)

1) open the ide, and go to: file > examples > arduinoisp and open the arduinoisp sketch

2) uncomment line 81 (// #define USE_OLD_STYLE_WIRING)

3) note the com port number in: tools > port (you will need this number later)

4) upload the sketch to the uno r3

5) close the arduino ide

6) remove the display (and ethernet module) from the uradmonitor board

7) unplug the arduino usb cable from the pc. connect the jumper wires as follows (see image):

uno -> kit1

gnd -> 4
5v -> 2
pin 10 (ss) -> 5
pin 11 (mosi) -> 1
pin 12 (miso) -> 9
pin 13 (sck) -> 7

it’s a good idea to write the arduino port numbers on the pcb, for future software upgrades:

8) double check the wiring between the uno and uradmonitor

9) copy ‘avrdude.conf’ file from*: c:\Users\wanek\AppData\Local\Arduino15\packages\arduino\tools\avrdude\6.3.0-arduino6\etc\
to: c:\Users\wanek\AppData\Local\Arduino15\packages\arduino\tools\avrdude\6.3.0-arduino6\bin\

*please note: the path can be slightly different, based on the ide version

10) copy the uradmonitor hex file to: c:\Users\wanek\AppData\Local\Arduino15\packages\arduino\tools\avrdude\6.0.1-arduino6\bin\ and rename to: ‘uradmonitor.hex’

11) open a terminal (go to start > search, type ‘cmd’ then press enter)

12) copy – paste this in the terminal (replace “wanek” with your user name):
cd c:\Users\wanek\AppData\Local\Arduino15\packages\arduino\tools\avrdude\6.3.0-arduino6\bin\

13) connect the arduino to the pc usb port

14) replace xx (use notepad) in step 15 and 16, with the port number you noted in step 4.

15) copy – paste in the terminal:
avrdude -P COMxx -b 19200 -c avrisp -p m328p -v -e -U lfuse:w:0xdc:m -U hfuse:w:0xdf:m

you should see something similar:

16) now enter this:
avrdude -P COMxx -b 19200 -c avrisp -p m328p -v -e -U flash:w:uradmonitor.hex -U lock:w:0x0F:m

it will take a while, but if you’re seeing this, it means you have succeeded!

17) unplug the usb cable, remove the jumper wires, remount the modules and power up the device. it should start up with the uradmonitor logo. now you can connect to the global network.

attention:
if something went wrong, and after hexing there are verification errors, answer no and try again. check the quality of the wiring, do not use too long cables (max. 20cm)

i’m not sure why these errors occur, but once i answered yes, and the process apparently halted. so i closed the terminal and after that, the microcontroller is not working… probably i’ve bricked it.

radhoo has some very detailed article about mcu flashing, here

written in 2016, using arduino ide 1.6.11, on windoze 1607.

hello everyone!

here is a post about my diy kit1, based on the v1.1.104 pcb. it was made with minor modifications / improvements regarding the original model. as radhoo said, maybe other builders will be interested in this, so i published here.

first of all, i’m a beginner in all this electronics and coding stuff, so if i wrote something stupid, please correct me. i’m always open for constructive criticism. second, sorry for my english, it is not my native language, but i’ll try to do my best 🙂

the differences compared to the original kit1 are:
– incorporated lithium battery
– built in battery charger module + micro usb port
– low dropout (0.17v) regulator
– real PoE connectivity, no additional cable / port needed on the device side, just the rj45 connector
– transparent case made from plexiglass

updated bom, with the components i used (if something is missing, please let me know):
BOM, updated

i have built 2 kits: one for me and on for a friend. ha asked to make it portable, because he will use mainly on field, as a mobile unit, outdoors and on industrial working sites.
this raised two challenge: the final product has to have a
– reliable and high capacity rechargeable battery
– a robust but not to bulky case

please note, that the components for these kits i bought from local stores, the best available quality. hence, these components visual aspect are differ from the originals, shipped with the kit1. i measured all of them before soldering, to make sure everything is up to the specs.

regarding the pcbs, after some emails, radhoo was so kind to send me 2 pieces, thank you again! because i didn’t want to ‘destroy’ these beauties, all the modifications are made without hacking the pcb.

power supply / charger / power consumption:

nowadays the “standard” power supply for handheld devices is the type b micro usb port. you can find them virtually everywhere. also, it is fairly easy and very cheap to implement into diy stuff, using these chinese modules:
battery charger, ali

as for the battery, probably everybody has access to some broken smartphones… although the phone or display is broken, chances are good that the battery is still functional. you just have to hook up to the output of the charging module and the input of the voltage stabiliser, it is ready to use.
i’ve used one cell from an old macbook battery, scavenged. it contains 4 lithium cells, similar like on this site:

they are roughly the size of the kit1 pcb. this way, the charger + battery ain’t cost anything to me (0.3 euro).
to keep a safe distance between the batteries aluminum foil and the bottom of the pcb, i’ve used 4 self adhesive rubber shoes, the ones used for furniture feets.

most lithium batteries have a nominal voltage of 3.6v (min 3.0v, max 4.2v). the recommended operating voltage for the kit1 is min 3.0v, max 3.3v. to take maximum use of the battery, i opted for a 3.0v voltage regulator. it has to have ultra low dropout voltage, in order to maximize battery life.
so, i had to replace the original lm1117 voltage stabiliser, lm1117 datasheet, because it has a large dropout voltage, 1.1v. (this would be 3.0 + 1.1 = 4.1v -> maybe just 5% of the overall battery capacity. not too efficient…)

after a lot of searching, i bought the MCP1700-3002E/TO regulator mcp1700 datasheet. it has very low dropout, only 0.17v. it means: 3.0 + 0.17 = 3.17v, i can use around 95% battery capacity. good.
the max output current for the mcp1700 is 250mA, and the max input voltage is 6.0v. as the lithium battery never goes above 4.2v, its ok for me.

to estimate the battery life, i’ve made some measurements:
(because the battery is quite old and tired, the 3700mA nominal capacity was irrelevant)
the kit1 has the following current consumption @ 3.0v (with the red led desoldered from the ethernet module):

offline mode, backlight off: 36mA
backlight: 18mA
online mode, backlight off: 147mA
maximum peak current: 170mA

in online mode, with fully charged battery (4.2v) it took 18 hours to discharge it to 2.9v.
discharging under 2.9v it is harmful for the lithium batteries lithium info, so even if the kit1 kept working at 2.9v, i stopped the measurement. it then took around 5 hours to fully charge the battery (from a usb port).

based on the above current consumption scenarios and the measured 18 hours, it is fairly safe to estimate 50 hours uptime in offline mode. more than adequate for daily use on the field.

this regulator has a different pinout, regarding the original model. i had to make a tricky implementation, but it worked.

at the moment, the only flaw is, that the kit1 keeps working even under 2.7v, over-discharging the battery. in the long run this will damage the lithium cell. the firmware should be modified to post a ‘low battery’ message to the screen and standby the unit, if the voltage drops below 2.85v. (we need to have full access to the source code to implement this)

also, it would be nice to have a voltage divider on the battery terminals (say 4.2v -> 3.0v) and implement a battery voltage monitoring function in the firmware. this way the user can have a feedback about the battery state. there are 2 unused analog pins on the mcu , this shouldn’t be a problem.

the MCP1700 needs 2 filtering capacitors to work properly. i’ve just replaced the original c3 with 1uf ceramic, the other one (cout) was soldered on the back side of the pcb.

because the charger module covered some holes of the on / off switch on the pcb, i’ve used a different switch, placed on the right side of my case:

PoE:

for the stationary unit installed outside, i wanted to have just one single cable (for supply + ethernet).
according to wikipedia poe wiki the poe standard uses 2 modes: A and B.

unfortunately, after some fiddling i’ve realised that none of these modes are implemented in the hr911105a rj45 connector, used on the enc28j60 ethernet modules. rj45 datasheet

what a pity! all the 8 pins are galvanically isolated. i needed access to pins 4+5 for dc+, respectively pins 7+8 for dc-. poe pinouts

custom made ethernet cable: on the router end has an additional usb cable, serving to inject 5v dc. this will be powered from the unused usb port on my router. the other end is just a standard rj45 connector.

hacking the rj45:

it is possible to open the metal sheet on the connector. then i’ve removed some plastic with a red-hot cutter blade, to expose the pins.

the isolation transformers for rx and tx are clearly visible

cleaning and soldering the wires to the selected pins was easy. for tapping i’ve removed one of the lateral side tin. after putting some layers of insulation to the exposed pins i’ve closed the connector.

the terminal wires were soldered to the appropriate INPUT pins (+5v and gnd) on the micro usb charger module. now i have a real poe module!

attention:
do not solder the +5v cable to the charger module OUTPUT, because it will overcharge the lithium battery! lithium batteries, if charged beyond 4.3v can explode or catch fire!

of course, this modification doesn’t deal with the two 75 ohm resistors, which kinda “short” the usb port.

but if you do the math: 2 x 75r = 150r. for 5v / 150r = 33mA extra current consumption for the usb port. the usb port standard specifies at least 500mA / port. the whole device does not absorb more than 200 mA, i think this is on the safe side.

regarding the heat production on the two 75 ohm resistors:
0.033A x 5v = 0,166W total. there are 2 resistors, so this is 0.083W / resistor. even if the resistors will burn out, i do not care, they are useless in this configuration (i think).

please note: using 5v dc with poe is not recommended on long cable runs, because, when load applied, the voltage drops quickly. in my case, i needed 5m ethernet cable. with the device connected, the 5v dropped to 4.3v. this means, that the charger module will output max 4.0 volts, so the battery will be never charged to 100%. this is not a problem for me, as the router will continuously supply the power. for much longer cables, one should consider using a dc to dc booster between the usb port and ethernet cable to compensate for the voltage drop.

bme280:

the v1.1.104 pcb has a nice feature, the extension port. i’ve populated this port with a bme280 module. bme280 specs

you can buy one here: bme ali

these sensors are very high quality and one can obtain a lots of info, with proper code implementation:
– temperature
– pressure
– altitude (uncalibrated)
– relative humidity
– dew point
– heat index (shadow)
– heat index (sunlight)

i’ve wrote a small arduino sketch to display all these values, using the SparkFunBME280 library. bme280 sketch

unfortunately, at the time of writing this article, the uradmonitor source code (v117) is not fully open. we have to wait for radhoo to implement this sensor, or much better, to publish the full source code on github.

case design:

for the device to be fully usable outdoors and to have a better visual experience, needs a case. i’ve designed the case in corel draw x8. made two very similar models, one for wall mounted fix station, one for portable device. despite my very limited knowledge in corel, i managed to finish it with quite good results. it was then laser cut from 3mm clear plexiglass.

since the enc28j60 chip produces a lot of heat, in a closed case this would deteriorate the temperature readings.
i’m interested in the REAL outdoor readings. if the temperature value is not correct, all the other values are useless. the humidity calculation formula is also based on temperature. accordingly, i had to assure a very good ventilation for the sensor.

designed a lots of ventilation holes on strategic parts of the case. these are circles 1.5mm in diameter. this is the smallest diameter the laser can cut, without melting too much plexi around. i hope the insects will not pass these holes. they will surely try. when winter coming, a ‘heated’ hotel is very attractive…

as hot air always goes up, the components arrangement is not very fortunate for the sensor, since it is placed exactly above the biggest heat source in the kit1.
i decided to mount the whole device upside down to the wall, this way the bme280 will be under the ethernet module. the ventilation holes should produce a chimney effect, that will take care to transport the air from bottom to top. theoretically, the sensor will always receive the unheated air from outside, obtaining correct readings.
i will test this theory when the device is mounted on the wall, placing an external temperature sensor near the case, and compare the 2 values.

while used as a fix station, the micro usb port will be out of order. hence, it will be covered with a cap, to keep the bugs at bay.

if anyone is interested to build one of these case, here are the corel draw x8 files:
fixed station with bme sensor
portable, without bme sensor

i will add new photos when it will be installed in its final place. for high resolution pictures you can visit: album

thank you radu for all the big effort and helpful attitude in this worldwide project!
thanks for reading,

written in 2016, oradea.

Voltage is not updated in uRADMonitorX for my old A1 model, now with 118 firmware. Maybe due to different prefix spelling? “vol:” vs “voltage:”

webserver:
URADMONITOR 11000003
type:1 hw:100 sw:118 SBM20radiation:18CPM (22.76CPM)
temperature:29.00C

vol:379V (46%/15.50kHz)
uptime:2764s wdt:3s

eth:10.0.0.24 (23.239.13.18)
http:200 46/46

JSON: {“data”:{ “id”:”11000003″,”type”:”1″,”detector”:”SBM20″,”voltage”:378,”cpm”:27,”temperature”:29.89,”uptime”: 160}}

My KIT1 which reports voltage fine in uRADMonitorX

webserver:
uRADMonitor 51000042
type:5 hw:103 sw:115 SBM20radiation:14CPM
average:21CPM
voltage:378V (69%)
ip:10.0.0.23
http:200

JSON: {“data”:{ “id”:”51000042″,”type”:”5″,”detector”:”SBM20″,”cpm”:18,”temperature”:0.00,”uptime”: 70203}}

Thanks for the note about the orientation of the tube, wasn’t sure if it was important. I originally based it on the photos from this blog post which shows the tube installed upside down: https://www.uradmonitor.com/model-kit1-production-ready/

I’ve swapped it around now and am looking for an enclosure to mount it in. Are there any specific requirements? Plastic, metal, height off the ground outdoors? Also if I was to add something like the BME280 would there need to be holes in the enclosure rather than having it watertight?

Regarding powering the device, something like this kit would be very useful: http://www.tp-link.com/en/products/details/cat-4794_TL-POE200.html

It allows you to inject a 12V into the spare cores on an Ethernet cable and pull them out at the other end (it’s an injector and splitter, and not a standard 802.3x POE).

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

so, i just put together the uradmonitor kit1, but i don’t have an isp programmer to upload the hex. but i have a lots of arduinos around…

this guide will show you how to upload the hex file to the uradmonitor kit1, using an arduino uno r3 + windoze

you will need:
– arduino uno
– 6 male to female jumper wires
– latest arduino ide
– hex file

please note: this article is for arduino uno r3, i will not explain here how to use other models. however, with a little googling + thinkering it is not complicated to adapt. for other mcu you can start here.

also, be sure to use tightly fitting jumper cables, you do not want to lose power or data while uploading the hex file! do not move / touch the setup while uploading!

steps:

0) download and install the latest arduino ide + drivers (arduino.cc)

1) open the ide, and go to: file > examples > arduinoisp and open the arduinoisp sketch

2) uncomment line 81 (// #define USE_OLD_STYLE_WIRING)

3) note the com port number in: tools > port (you will need this number later)

4) upload the sketch to the uno r3

5) close the arduino ide

6) remove the display (and ethernet module) from the uradmonitor board

7) unplug the arduino usb cable from the pc. connect the jumper wires as follows (see image):

uno -> kit1

gnd -> 4
5v -> 2
pin 10 (ss) -> 5
pin 11 (mosi) -> 1
pin 12 (miso) -> 9
pin 13 (sck) -> 7

it’s a good idea to write the arduino port numbers on the pcb, for future software upgrades:

8) double check the wiring between the uno and uradmonitor

9) copy ‘avrdude.conf’ file from*: c:\Users\wanek\AppData\Local\Arduino15\packages\arduino\tools\avrdude\6.3.0-arduino6\etc\
to: c:\Users\wanek\AppData\Local\Arduino15\packages\arduino\tools\avrdude\6.3.0-arduino6\bin\

*please note: the path can be slightly different, based on the ide version

10) copy the uradmonitor hex file to: c:\Users\wanek\AppData\Local\Arduino15\packages\arduino\tools\avrdude\6.0.1-arduino6\bin\ and rename to: ‘uradmonitor.hex’

11) open a terminal (go to start > search, type ‘cmd’ then press enter)

12) copy – paste this in the terminal (replace “wanek” with your user name):
cd c:\Users\wanek\AppData\Local\Arduino15\packages\arduino\tools\avrdude\6.3.0-arduino6\bin\

13) connect the arduino to the pc usb port

14) replace xx (use notepad) in step 15 and 16, with the port number you noted in step 4.

15) copy – paste in the terminal:
avrdude -P COMxx -b 19200 -c avrisp -p m328p -v -e -U lfuse:w:0xdc:m -U hfuse:w:0xdf:m

you should see something similar:

16) now enter this:
avrdude -P COMxx -b 19200 -c avrisp -p m328p -v -e -U flash:w:uradmonitor.hex -U lock:w:0x0F:m

it will take a while, but if you’re seeing this, it means you have succeeded!

17) unplug the usb cable, remove the jumper wires, remount the modules and power up the device. it should start up with the uradmonitor logo. now you can connect to the global network.

attention:
if something went wrong, and after hexing there are verification errors, answer no and try again. check the quality of the wiring, do not use too long cables (max. 20cm)

i’m not sure why these errors occur, but once i answered yes, and the process apparently halted. so i closed the terminal and after that, the microcontroller is not working… probably i’ve bricked it.

radhoo has some very detailed article about mcu flashing, here

written in 2016, using arduino ide 1.6.11, on windoze 1607.

hello everyone!

here is a post about my diy kit1, based on the v1.1.104 pcb. it was made with minor modifications / improvements regarding the original model. as radhoo said, maybe other builders will be interested in this, so i published here.

first of all, i’m a beginner in all this electronics and coding stuff, so if i wrote something stupid, please correct me. i’m always open for constructive criticism. second, sorry for my english, it is not my native language, but i’ll try to do my best 🙂

the differences compared to the original kit1 are:
– incorporated lithium battery
– built in battery charger module + micro usb port
– low dropout (0.17v) regulator
– real PoE connectivity, no additional cable / port needed on the device side, just the rj45 connector
– transparent case made from plexiglass

updated bom, with the components i used (if something is missing, please let me know):
BOM, updated

i have built 2 kits: one for me and on for a friend. ha asked to make it portable, because he will use mainly on field, as a mobile unit, outdoors and on industrial working sites.
this raised two challenge: the final product has to have a
– reliable and high capacity rechargeable battery
– a robust but not to bulky case

please note, that the components for these kits i bought from local stores, the best available quality. hence, these components visual aspect are differ from the originals, shipped with the kit1. i measured all of them before soldering, to make sure everything is up to the specs.

regarding the pcbs, after some emails, radhoo was so kind to send me 2 pieces, thank you again! because i didn’t want to ‘destroy’ these beauties, all the modifications are made without hacking the pcb.

power supply / charger / power consumption:

nowadays the “standard” power supply for handheld devices is the type b micro usb port. you can find them virtually everywhere. also, it is fairly easy and very cheap to implement into diy stuff, using these chinese modules:
battery charger, ali

as for the battery, probably everybody has access to some broken smartphones… although the phone or display is broken, chances are good that the battery is still functional. you just have to hook up to the output of the charging module and the input of the voltage stabiliser, it is ready to use.
i’ve used one cell from an old macbook battery, scavenged. it contains 4 lithium cells, similar like on this site:

they are roughly the size of the kit1 pcb. this way, the charger + battery ain’t cost anything to me (0.3 euro).
to keep a safe distance between the batteries aluminum foil and the bottom of the pcb, i’ve used 4 self adhesive rubber shoes, the ones used for furniture feets.

most lithium batteries have a nominal voltage of 3.6v (min 3.0v, max 4.2v). the recommended operating voltage for the kit1 is min 3.0v, max 3.3v. to take maximum use of the battery, i opted for a 3.0v voltage regulator. it has to have ultra low dropout voltage, in order to maximize battery life.
so, i had to replace the original lm1117 voltage stabiliser, lm1117 datasheet, because it has a large dropout voltage, 1.1v. (this would be 3.0 + 1.1 = 4.1v -> maybe just 5% of the overall battery capacity. not too efficient…)

after a lot of searching, i bought the MCP1700-3002E/TO regulator mcp1700 datasheet. it has very low dropout, only 0.17v. it means: 3.0 + 0.17 = 3.17v, i can use around 95% battery capacity. good.
the max output current for the mcp1700 is 250mA, and the max input voltage is 6.0v. as the lithium battery never goes above 4.2v, its ok for me.

to estimate the battery life, i’ve made some measurements:
(because the battery is quite old and tired, the 3700mA nominal capacity was irrelevant)
the kit1 has the following current consumption @ 3.0v (with the red led desoldered from the ethernet module):

offline mode, backlight off: 36mA
backlight: 18mA
online mode, backlight off: 147mA
maximum peak current: 170mA

in online mode, with fully charged battery (4.2v) it took 18 hours to discharge it to 2.9v.
discharging under 2.9v it is harmful for the lithium batteries lithium info, so even if the kit1 kept working at 2.9v, i stopped the measurement. it then took around 5 hours to fully charge the battery (from a usb port).

based on the above current consumption scenarios and the measured 18 hours, it is fairly safe to estimate 50 hours uptime in offline mode. more than adequate for daily use on the field.

this regulator has a different pinout, regarding the original model. i had to make a tricky implementation, but it worked.

at the moment, the only flaw is, that the kit1 keeps working even under 2.7v, over-discharging the battery. in the long run this will damage the lithium cell. the firmware should be modified to post a ‘low battery’ message to the screen and standby the unit, if the voltage drops below 2.85v. (we need to have full access to the source code to implement this)

also, it would be nice to have a voltage divider on the battery terminals (say 4.2v -> 3.0v) and implement a battery voltage monitoring function in the firmware. this way the user can have a feedback about the battery state. there are 2 unused analog pins on the mcu , this shouldn’t be a problem.

the MCP1700 needs 2 filtering capacitors to work properly. i’ve just replaced the original c3 with 1uf ceramic, the other one (cout) was soldered on the back side of the pcb.

because the charger module covered some holes of the on / off switch on the pcb, i’ve used a different switch, placed on the right side of my case:

PoE:

for the stationary unit installed outside, i wanted to have just one single cable (for supply + ethernet).
according to wikipedia poe wiki the poe standard uses 2 modes: A and B.

unfortunately, after some fiddling i’ve realised that none of these modes are implemented in the hr911105a rj45 connector, used on the enc28j60 ethernet modules. rj45 datasheet

what a pity! all the 8 pins are galvanically isolated. i needed access to pins 4+5 for dc+, respectively pins 7+8 for dc-. poe pinouts

custom made ethernet cable: on the router end has an additional usb cable, serving to inject 5v dc. this will be powered from the unused usb port on my router. the other end is just a standard rj45 connector.

hacking the rj45:

it is possible to open the metal sheet on the connector. then i’ve removed some plastic with a red-hot cutter blade, to expose the pins.

the isolation transformers for rx and tx are clearly visible

cleaning and soldering the wires to the selected pins was easy. for tapping i’ve removed one of the lateral side tin. after putting some layers of insulation to the exposed pins i’ve closed the connector.

the terminal wires were soldered to the appropriate INPUT pins (+5v and gnd) on the micro usb charger module. now i have a real poe module!

attention:
do not solder the +5v cable to the charger module OUTPUT, because it will overcharge the lithium battery! lithium batteries, if charged beyond 4.3v can explode or catch fire!

of course, this modification doesn’t deal with the two 75 ohm resistors, which kinda “short” the usb port.

but if you do the math: 2 x 75r = 150r. for 5v / 150r = 33mA extra current consumption for the usb port. the usb port standard specifies at least 500mA / port. the whole device does not absorb more than 200 mA, i think this is on the safe side.

regarding the heat production on the two 75 ohm resistors:
0.033A x 5v = 0,166W total. there are 2 resistors, so this is 0.083W / resistor. even if the resistors will burn out, i do not care, they are useless in this configuration (i think).

please note: using 5v dc with poe is not recommended on long cable runs, because, when load applied, the voltage drops quickly. in my case, i needed 5m ethernet cable. with the device connected, the 5v dropped to 4.3v. this means, that the charger module will output max 4.0 volts, so the battery will be never charged to 100%. this is not a problem for me, as the router will continuously supply the power. for much longer cables, one should consider using a dc to dc booster between the usb port and ethernet cable to compensate for the voltage drop.

bme280:

the v1.1.104 pcb has a nice feature, the extension port. i’ve populated this port with a bme280 module. bme280 specs

you can buy one here: bme ali

these sensors are very high quality and one can obtain a lots of info, with proper code implementation:
– temperature
– pressure
– altitude (uncalibrated)
– relative humidity
– dew point
– heat index (shadow)
– heat index (sunlight)

i’ve wrote a small arduino sketch to display all these values, using the SparkFunBME280 library. bme280 sketch

unfortunately, at the time of writing this article, the uradmonitor source code (v117) is not fully open. we have to wait for radhoo to implement this sensor, or much better, to publish the full source code on github.

case design:

for the device to be fully usable outdoors and to have a better visual experience, needs a case. i’ve designed the case in corel draw x8. made two very similar models, one for wall mounted fix station, one for portable device. despite my very limited knowledge in corel, i managed to finish it with quite good results. it was then laser cut from 3mm clear plexiglass.

since the enc28j60 chip produces a lot of heat, in a closed case this would deteriorate the temperature readings.
i’m interested in the REAL outdoor readings. if the temperature value is not correct, all the other values are useless. the humidity calculation formula is also based on temperature. accordingly, i had to assure a very good ventilation for the sensor.

designed a lots of ventilation holes on strategic parts of the case. these are circles 1.5mm in diameter. this is the smallest diameter the laser can cut, without melting too much plexi around. i hope the insects will not pass these holes. they will surely try. when winter coming, a ‘heated’ hotel is very attractive…

as hot air always goes up, the components arrangement is not very fortunate for the sensor, since it is placed exactly above the biggest heat source in the kit1.
i decided to mount the whole device upside down to the wall, this way the bme280 will be under the ethernet module. the ventilation holes should produce a chimney effect, that will take care to transport the air from bottom to top. theoretically, the sensor will always receive the unheated air from outside, obtaining correct readings.
i will test this theory when the device is mounted on the wall, placing an external temperature sensor near the case, and compare the 2 values.

while used as a fix station, the micro usb port will be out of order. hence, it will be covered with a cap, to keep the bugs at bay.

if anyone is interested to build one of these case, here are the corel draw x8 files:
fixed station with bme sensor
portable, without bme sensor

i will add new photos when it will be installed in its final place. for high resolution pictures you can visit: album

thank you radu for all the big effort and helpful attitude in this worldwide project!
thanks for reading,

written in 2016, oradea.

Voltage is not updated in uRADMonitorX for my old A1 model, now with 118 firmware. Maybe due to different prefix spelling? “vol:” vs “voltage:”

webserver:
URADMONITOR 11000003
type:1 hw:100 sw:118 SBM20radiation:18CPM (22.76CPM)
temperature:29.00C

vol:379V (46%/15.50kHz)
uptime:2764s wdt:3s

eth:10.0.0.24 (23.239.13.18)
http:200 46/46

JSON: {“data”:{ “id”:”11000003″,”type”:”1″,”detector”:”SBM20″,”voltage”:378,”cpm”:27,”temperature”:29.89,”uptime”: 160}}

My KIT1 which reports voltage fine in uRADMonitorX

webserver:
uRADMonitor 51000042
type:5 hw:103 sw:115 SBM20radiation:14CPM
average:21CPM
voltage:378V (69%)
ip:10.0.0.23
http:200

JSON: {“data”:{ “id”:”51000042″,”type”:”5″,”detector”:”SBM20″,”cpm”:18,”temperature”:0.00,”uptime”: 70203}}

Thanks for the note about the orientation of the tube, wasn’t sure if it was important. I originally based it on the photos from this blog post which shows the tube installed upside down: https://www.uradmonitor.com/model-kit1-production-ready/

I’ve swapped it around now and am looking for an enclosure to mount it in. Are there any specific requirements? Plastic, metal, height off the ground outdoors? Also if I was to add something like the BME280 would there need to be holes in the enclosure rather than having it watertight?

Regarding powering the device, something like this kit would be very useful: http://www.tp-link.com/en/products/details/cat-4794_TL-POE200.html

It allows you to inject a 12V into the spare cores on an Ethernet cable and pull them out at the other end (it’s an injector and splitter, and not a standard 802.3x POE).

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

so, i just put together the uradmonitor kit1, but i don’t have an isp programmer to upload the hex. but i have a lots of arduinos around…

this guide will show you how to upload the hex file to the uradmonitor kit1, using an arduino uno r3 + windoze

you will need:
– arduino uno
– 6 male to female jumper wires
– latest arduino ide
– hex file

please note: this article is for arduino uno r3, i will not explain here how to use other models. however, with a little googling + thinkering it is not complicated to adapt. for other mcu you can start here.

also, be sure to use tightly fitting jumper cables, you do not want to lose power or data while uploading the hex file! do not move / touch the setup while uploading!

steps:

0) download and install the latest arduino ide + drivers (arduino.cc)

1) open the ide, and go to: file > examples > arduinoisp and open the arduinoisp sketch

2) uncomment line 81 (// #define USE_OLD_STYLE_WIRING)

3) note the com port number in: tools > port (you will need this number later)

4) upload the sketch to the uno r3

5) close the arduino ide

6) remove the display (and ethernet module) from the uradmonitor board

7) unplug the arduino usb cable from the pc. connect the jumper wires as follows (see image):

uno -> kit1

gnd -> 4
5v -> 2
pin 10 (ss) -> 5
pin 11 (mosi) -> 1
pin 12 (miso) -> 9
pin 13 (sck) -> 7

it’s a good idea to write the arduino port numbers on the pcb, for future software upgrades:

8) double check the wiring between the uno and uradmonitor

9) copy ‘avrdude.conf’ file from*: c:\Users\wanek\AppData\Local\Arduino15\packages\arduino\tools\avrdude\6.3.0-arduino6\etc\
to: c:\Users\wanek\AppData\Local\Arduino15\packages\arduino\tools\avrdude\6.3.0-arduino6\bin\

*please note: the path can be slightly different, based on the ide version

10) copy the uradmonitor hex file to: c:\Users\wanek\AppData\Local\Arduino15\packages\arduino\tools\avrdude\6.0.1-arduino6\bin\ and rename to: ‘uradmonitor.hex’

11) open a terminal (go to start > search, type ‘cmd’ then press enter)

12) copy – paste this in the terminal (replace “wanek” with your user name):
cd c:\Users\wanek\AppData\Local\Arduino15\packages\arduino\tools\avrdude\6.3.0-arduino6\bin\

13) connect the arduino to the pc usb port

14) replace xx (use notepad) in step 15 and 16, with the port number you noted in step 4.

15) copy – paste in the terminal:
avrdude -P COMxx -b 19200 -c avrisp -p m328p -v -e -U lfuse:w:0xdc:m -U hfuse:w:0xdf:m

you should see something similar:

16) now enter this:
avrdude -P COMxx -b 19200 -c avrisp -p m328p -v -e -U flash:w:uradmonitor.hex -U lock:w:0x0F:m

it will take a while, but if you’re seeing this, it means you have succeeded!

17) unplug the usb cable, remove the jumper wires, remount the modules and power up the device. it should start up with the uradmonitor logo. now you can connect to the global network.

attention:
if something went wrong, and after hexing there are verification errors, answer no and try again. check the quality of the wiring, do not use too long cables (max. 20cm)

i’m not sure why these errors occur, but once i answered yes, and the process apparently halted. so i closed the terminal and after that, the microcontroller is not working… probably i’ve bricked it.

radhoo has some very detailed article about mcu flashing, here

written in 2016, using arduino ide 1.6.11, on windoze 1607.

hello everyone!

here is a post about my diy kit1, based on the v1.1.104 pcb. it was made with minor modifications / improvements regarding the original model. as radhoo said, maybe other builders will be interested in this, so i published here.

first of all, i’m a beginner in all this electronics and coding stuff, so if i wrote something stupid, please correct me. i’m always open for constructive criticism. second, sorry for my english, it is not my native language, but i’ll try to do my best 🙂

the differences compared to the original kit1 are:
– incorporated lithium battery
– built in battery charger module + micro usb port
– low dropout (0.17v) regulator
– real PoE connectivity, no additional cable / port needed on the device side, just the rj45 connector
– transparent case made from plexiglass

updated bom, with the components i used (if something is missing, please let me know):
BOM, updated

i have built 2 kits: one for me and on for a friend. ha asked to make it portable, because he will use mainly on field, as a mobile unit, outdoors and on industrial working sites.
this raised two challenge: the final product has to have a
– reliable and high capacity rechargeable battery
– a robust but not to bulky case

please note, that the components for these kits i bought from local stores, the best available quality. hence, these components visual aspect are differ from the originals, shipped with the kit1. i measured all of them before soldering, to make sure everything is up to the specs.

regarding the pcbs, after some emails, radhoo was so kind to send me 2 pieces, thank you again! because i didn’t want to ‘destroy’ these beauties, all the modifications are made without hacking the pcb.

power supply / charger / power consumption:

nowadays the “standard” power supply for handheld devices is the type b micro usb port. you can find them virtually everywhere. also, it is fairly easy and very cheap to implement into diy stuff, using these chinese modules:
battery charger, ali

as for the battery, probably everybody has access to some broken smartphones… although the phone or display is broken, chances are good that the battery is still functional. you just have to hook up to the output of the charging module and the input of the voltage stabiliser, it is ready to use.
i’ve used one cell from an old macbook battery, scavenged. it contains 4 lithium cells, similar like on this site:

they are roughly the size of the kit1 pcb. this way, the charger + battery ain’t cost anything to me (0.3 euro).
to keep a safe distance between the batteries aluminum foil and the bottom of the pcb, i’ve used 4 self adhesive rubber shoes, the ones used for furniture feets.

most lithium batteries have a nominal voltage of 3.6v (min 3.0v, max 4.2v). the recommended operating voltage for the kit1 is min 3.0v, max 3.3v. to take maximum use of the battery, i opted for a 3.0v voltage regulator. it has to have ultra low dropout voltage, in order to maximize battery life.
so, i had to replace the original lm1117 voltage stabiliser, lm1117 datasheet, because it has a large dropout voltage, 1.1v. (this would be 3.0 + 1.1 = 4.1v -> maybe just 5% of the overall battery capacity. not too efficient…)

after a lot of searching, i bought the MCP1700-3002E/TO regulator mcp1700 datasheet. it has very low dropout, only 0.17v. it means: 3.0 + 0.17 = 3.17v, i can use around 95% battery capacity. good.
the max output current for the mcp1700 is 250mA, and the max input voltage is 6.0v. as the lithium battery never goes above 4.2v, its ok for me.

to estimate the battery life, i’ve made some measurements:
(because the battery is quite old and tired, the 3700mA nominal capacity was irrelevant)
the kit1 has the following current consumption @ 3.0v (with the red led desoldered from the ethernet module):

offline mode, backlight off: 36mA
backlight: 18mA
online mode, backlight off: 147mA
maximum peak current: 170mA

in online mode, with fully charged battery (4.2v) it took 18 hours to discharge it to 2.9v.
discharging under 2.9v it is harmful for the lithium batteries lithium info, so even if the kit1 kept working at 2.9v, i stopped the measurement. it then took around 5 hours to fully charge the battery (from a usb port).

based on the above current consumption scenarios and the measured 18 hours, it is fairly safe to estimate 50 hours uptime in offline mode. more than adequate for daily use on the field.

this regulator has a different pinout, regarding the original model. i had to make a tricky implementation, but it worked.

at the moment, the only flaw is, that the kit1 keeps working even under 2.7v, over-discharging the battery. in the long run this will damage the lithium cell. the firmware should be modified to post a ‘low battery’ message to the screen and standby the unit, if the voltage drops below 2.85v. (we need to have full access to the source code to implement this)

also, it would be nice to have a voltage divider on the battery terminals (say 4.2v -> 3.0v) and implement a battery voltage monitoring function in the firmware. this way the user can have a feedback about the battery state. there are 2 unused analog pins on the mcu , this shouldn’t be a problem.

the MCP1700 needs 2 filtering capacitors to work properly. i’ve just replaced the original c3 with 1uf ceramic, the other one (cout) was soldered on the back side of the pcb.

because the charger module covered some holes of the on / off switch on the pcb, i’ve used a different switch, placed on the right side of my case:

PoE:

for the stationary unit installed outside, i wanted to have just one single cable (for supply + ethernet).
according to wikipedia poe wiki the poe standard uses 2 modes: A and B.

unfortunately, after some fiddling i’ve realised that none of these modes are implemented in the hr911105a rj45 connector, used on the enc28j60 ethernet modules. rj45 datasheet

what a pity! all the 8 pins are galvanically isolated. i needed access to pins 4+5 for dc+, respectively pins 7+8 for dc-. poe pinouts

custom made ethernet cable: on the router end has an additional usb cable, serving to inject 5v dc. this will be powered from the unused usb port on my router. the other end is just a standard rj45 connector.

hacking the rj45:

it is possible to open the metal sheet on the connector. then i’ve removed some plastic with a red-hot cutter blade, to expose the pins.

the isolation transformers for rx and tx are clearly visible

cleaning and soldering the wires to the selected pins was easy. for tapping i’ve removed one of the lateral side tin. after putting some layers of insulation to the exposed pins i’ve closed the connector.

the terminal wires were soldered to the appropriate INPUT pins (+5v and gnd) on the micro usb charger module. now i have a real poe module!

attention:
do not solder the +5v cable to the charger module OUTPUT, because it will overcharge the lithium battery! lithium batteries, if charged beyond 4.3v can explode or catch fire!

of course, this modification doesn’t deal with the two 75 ohm resistors, which kinda “short” the usb port.

but if you do the math: 2 x 75r = 150r. for 5v / 150r = 33mA extra current consumption for the usb port. the usb port standard specifies at least 500mA / port. the whole device does not absorb more than 200 mA, i think this is on the safe side.

regarding the heat production on the two 75 ohm resistors:
0.033A x 5v = 0,166W total. there are 2 resistors, so this is 0.083W / resistor. even if the resistors will burn out, i do not care, they are useless in this configuration (i think).

please note: using 5v dc with poe is not recommended on long cable runs, because, when load applied, the voltage drops quickly. in my case, i needed 5m ethernet cable. with the device connected, the 5v dropped to 4.3v. this means, that the charger module will output max 4.0 volts, so the battery will be never charged to 100%. this is not a problem for me, as the router will continuously supply the power. for much longer cables, one should consider using a dc to dc booster between the usb port and ethernet cable to compensate for the voltage drop.

bme280:

the v1.1.104 pcb has a nice feature, the extension port. i’ve populated this port with a bme280 module. bme280 specs

you can buy one here: bme ali

these sensors are very high quality and one can obtain a lots of info, with proper code implementation:
– temperature
– pressure
– altitude (uncalibrated)
– relative humidity
– dew point
– heat index (shadow)
– heat index (sunlight)

i’ve wrote a small arduino sketch to display all these values, using the SparkFunBME280 library. bme280 sketch

unfortunately, at the time of writing this article, the uradmonitor source code (v117) is not fully open. we have to wait for radhoo to implement this sensor, or much better, to publish the full source code on github.

case design:

for the device to be fully usable outdoors and to have a better visual experience, needs a case. i’ve designed the case in corel draw x8. made two very similar models, one for wall mounted fix station, one for portable device. despite my very limited knowledge in corel, i managed to finish it with quite good results. it was then laser cut from 3mm clear plexiglass.

since the enc28j60 chip produces a lot of heat, in a closed case this would deteriorate the temperature readings.
i’m interested in the REAL outdoor readings. if the temperature value is not correct, all the other values are useless. the humidity calculation formula is also based on temperature. accordingly, i had to assure a very good ventilation for the sensor.

designed a lots of ventilation holes on strategic parts of the case. these are circles 1.5mm in diameter. this is the smallest diameter the laser can cut, without melting too much plexi around. i hope the insects will not pass these holes. they will surely try. when winter coming, a ‘heated’ hotel is very attractive…

as hot air always goes up, the components arrangement is not very fortunate for the sensor, since it is placed exactly above the biggest heat source in the kit1.
i decided to mount the whole device upside down to the wall, this way the bme280 will be under the ethernet module. the ventilation holes should produce a chimney effect, that will take care to transport the air from bottom to top. theoretically, the sensor will always receive the unheated air from outside, obtaining correct readings.
i will test this theory when the device is mounted on the wall, placing an external temperature sensor near the case, and compare the 2 values.

while used as a fix station, the micro usb port will be out of order. hence, it will be covered with a cap, to keep the bugs at bay.

if anyone is interested to build one of these case, here are the corel draw x8 files:
fixed station with bme sensor
portable, without bme sensor

i will add new photos when it will be installed in its final place. for high resolution pictures you can visit: album

thank you radu for all the big effort and helpful attitude in this worldwide project!
thanks for reading,

written in 2016, oradea.

Voltage is not updated in uRADMonitorX for my old A1 model, now with 118 firmware. Maybe due to different prefix spelling? “vol:” vs “voltage:”

webserver:
URADMONITOR 11000003
type:1 hw:100 sw:118 SBM20radiation:18CPM (22.76CPM)
temperature:29.00C

vol:379V (46%/15.50kHz)
uptime:2764s wdt:3s

eth:10.0.0.24 (23.239.13.18)
http:200 46/46

JSON: {“data”:{ “id”:”11000003″,”type”:”1″,”detector”:”SBM20″,”voltage”:378,”cpm”:27,”temperature”:29.89,”uptime”: 160}}

My KIT1 which reports voltage fine in uRADMonitorX

webserver:
uRADMonitor 51000042
type:5 hw:103 sw:115 SBM20radiation:14CPM
average:21CPM
voltage:378V (69%)
ip:10.0.0.23
http:200

JSON: {“data”:{ “id”:”51000042″,”type”:”5″,”detector”:”SBM20″,”cpm”:18,”temperature”:0.00,”uptime”: 70203}}

Thanks for the note about the orientation of the tube, wasn’t sure if it was important. I originally based it on the photos from this blog post which shows the tube installed upside down: https://www.uradmonitor.com/model-kit1-production-ready/

I’ve swapped it around now and am looking for an enclosure to mount it in. Are there any specific requirements? Plastic, metal, height off the ground outdoors? Also if I was to add something like the BME280 would there need to be holes in the enclosure rather than having it watertight?

Regarding powering the device, something like this kit would be very useful: http://www.tp-link.com/en/products/details/cat-4794_TL-POE200.html

It allows you to inject a 12V into the spare cores on an Ethernet cable and pull them out at the other end (it’s an injector and splitter, and not a standard 802.3x POE).

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

so, i just put together the uradmonitor kit1, but i don’t have an isp programmer to upload the hex. but i have a lots of arduinos around…

this guide will show you how to upload the hex file to the uradmonitor kit1, using an arduino uno r3 + windoze

you will need:
– arduino uno
– 6 male to female jumper wires
– latest arduino ide
– hex file

please note: this article is for arduino uno r3, i will not explain here how to use other models. however, with a little googling + thinkering it is not complicated to adapt. for other mcu you can start here.

also, be sure to use tightly fitting jumper cables, you do not want to lose power or data while uploading the hex file! do not move / touch the setup while uploading!

steps:

0) download and install the latest arduino ide + drivers (arduino.cc)

1) open the ide, and go to: file > examples > arduinoisp and open the arduinoisp sketch

2) uncomment line 81 (// #define USE_OLD_STYLE_WIRING)

3) note the com port number in: tools > port (you will need this number later)

4) upload the sketch to the uno r3

5) close the arduino ide

6) remove the display (and ethernet module) from the uradmonitor board

7) unplug the arduino usb cable from the pc. connect the jumper wires as follows (see image):

uno -> kit1

gnd -> 4
5v -> 2
pin 10 (ss) -> 5
pin 11 (mosi) -> 1
pin 12 (miso) -> 9
pin 13 (sck) -> 7

it’s a good idea to write the arduino port numbers on the pcb, for future software upgrades:

8) double check the wiring between the uno and uradmonitor

9) copy ‘avrdude.conf’ file from*: c:\Users\wanek\AppData\Local\Arduino15\packages\arduino\tools\avrdude\6.3.0-arduino6\etc\
to: c:\Users\wanek\AppData\Local\Arduino15\packages\arduino\tools\avrdude\6.3.0-arduino6\bin\

*please note: the path can be slightly different, based on the ide version

10) copy the uradmonitor hex file to: c:\Users\wanek\AppData\Local\Arduino15\packages\arduino\tools\avrdude\6.0.1-arduino6\bin\ and rename to: ‘uradmonitor.hex’

11) open a terminal (go to start > search, type ‘cmd’ then press enter)

12) copy – paste this in the terminal (replace “wanek” with your user name):
cd c:\Users\wanek\AppData\Local\Arduino15\packages\arduino\tools\avrdude\6.3.0-arduino6\bin\

13) connect the arduino to the pc usb port

14) replace xx (use notepad) in step 15 and 16, with the port number you noted in step 4.

15) copy – paste in the terminal:
avrdude -P COMxx -b 19200 -c avrisp -p m328p -v -e -U lfuse:w:0xdc:m -U hfuse:w:0xdf:m

you should see something similar:

16) now enter this:
avrdude -P COMxx -b 19200 -c avrisp -p m328p -v -e -U flash:w:uradmonitor.hex -U lock:w:0x0F:m

it will take a while, but if you’re seeing this, it means you have succeeded!

17) unplug the usb cable, remove the jumper wires, remount the modules and power up the device. it should start up with the uradmonitor logo. now you can connect to the global network.

attention:
if something went wrong, and after hexing there are verification errors, answer no and try again. check the quality of the wiring, do not use too long cables (max. 20cm)

i’m not sure why these errors occur, but once i answered yes, and the process apparently halted. so i closed the terminal and after that, the microcontroller is not working… probably i’ve bricked it.

radhoo has some very detailed article about mcu flashing, here

written in 2016, using arduino ide 1.6.11, on windoze 1607.

hello everyone!

here is a post about my diy kit1, based on the v1.1.104 pcb. it was made with minor modifications / improvements regarding the original model. as radhoo said, maybe other builders will be interested in this, so i published here.

first of all, i’m a beginner in all this electronics and coding stuff, so if i wrote something stupid, please correct me. i’m always open for constructive criticism. second, sorry for my english, it is not my native language, but i’ll try to do my best 🙂

the differences compared to the original kit1 are:
– incorporated lithium battery
– built in battery charger module + micro usb port
– low dropout (0.17v) regulator
– real PoE connectivity, no additional cable / port needed on the device side, just the rj45 connector
– transparent case made from plexiglass

updated bom, with the components i used (if something is missing, please let me know):
BOM, updated

i have built 2 kits: one for me and on for a friend. ha asked to make it portable, because he will use mainly on field, as a mobile unit, outdoors and on industrial working sites.
this raised two challenge: the final product has to have a
– reliable and high capacity rechargeable battery
– a robust but not to bulky case

please note, that the components for these kits i bought from local stores, the best available quality. hence, these components visual aspect are differ from the originals, shipped with the kit1. i measured all of them before soldering, to make sure everything is up to the specs.

regarding the pcbs, after some emails, radhoo was so kind to send me 2 pieces, thank you again! because i didn’t want to ‘destroy’ these beauties, all the modifications are made without hacking the pcb.

power supply / charger / power consumption:

nowadays the “standard” power supply for handheld devices is the type b micro usb port. you can find them virtually everywhere. also, it is fairly easy and very cheap to implement into diy stuff, using these chinese modules:
battery charger, ali

as for the battery, probably everybody has access to some broken smartphones… although the phone or display is broken, chances are good that the battery is still functional. you just have to hook up to the output of the charging module and the input of the voltage stabiliser, it is ready to use.
i’ve used one cell from an old macbook battery, scavenged. it contains 4 lithium cells, similar like on this site:

they are roughly the size of the kit1 pcb. this way, the charger + battery ain’t cost anything to me (0.3 euro).
to keep a safe distance between the batteries aluminum foil and the bottom of the pcb, i’ve used 4 self adhesive rubber shoes, the ones used for furniture feets.

most lithium batteries have a nominal voltage of 3.6v (min 3.0v, max 4.2v). the recommended operating voltage for the kit1 is min 3.0v, max 3.3v. to take maximum use of the battery, i opted for a 3.0v voltage regulator. it has to have ultra low dropout voltage, in order to maximize battery life.
so, i had to replace the original lm1117 voltage stabiliser, lm1117 datasheet, because it has a large dropout voltage, 1.1v. (this would be 3.0 + 1.1 = 4.1v -> maybe just 5% of the overall battery capacity. not too efficient…)

after a lot of searching, i bought the MCP1700-3002E/TO regulator mcp1700 datasheet. it has very low dropout, only 0.17v. it means: 3.0 + 0.17 = 3.17v, i can use around 95% battery capacity. good.
the max output current for the mcp1700 is 250mA, and the max input voltage is 6.0v. as the lithium battery never goes above 4.2v, its ok for me.

to estimate the battery life, i’ve made some measurements:
(because the battery is quite old and tired, the 3700mA nominal capacity was irrelevant)
the kit1 has the following current consumption @ 3.0v (with the red led desoldered from the ethernet module):

offline mode, backlight off: 36mA
backlight: 18mA
online mode, backlight off: 147mA
maximum peak current: 170mA

in online mode, with fully charged battery (4.2v) it took 18 hours to discharge it to 2.9v.
discharging under 2.9v it is harmful for the lithium batteries lithium info, so even if the kit1 kept working at 2.9v, i stopped the measurement. it then took around 5 hours to fully charge the battery (from a usb port).

based on the above current consumption scenarios and the measured 18 hours, it is fairly safe to estimate 50 hours uptime in offline mode. more than adequate for daily use on the field.

this regulator has a different pinout, regarding the original model. i had to make a tricky implementation, but it worked.

at the moment, the only flaw is, that the kit1 keeps working even under 2.7v, over-discharging the battery. in the long run this will damage the lithium cell. the firmware should be modified to post a ‘low battery’ message to the screen and standby the unit, if the voltage drops below 2.85v. (we need to have full access to the source code to implement this)

also, it would be nice to have a voltage divider on the battery terminals (say 4.2v -> 3.0v) and implement a battery voltage monitoring function in the firmware. this way the user can have a feedback about the battery state. there are 2 unused analog pins on the mcu , this shouldn’t be a problem.

the MCP1700 needs 2 filtering capacitors to work properly. i’ve just replaced the original c3 with 1uf ceramic, the other one (cout) was soldered on the back side of the pcb.

because the charger module covered some holes of the on / off switch on the pcb, i’ve used a different switch, placed on the right side of my case:

PoE:

for the stationary unit installed outside, i wanted to have just one single cable (for supply + ethernet).
according to wikipedia poe wiki the poe standard uses 2 modes: A and B.

unfortunately, after some fiddling i’ve realised that none of these modes are implemented in the hr911105a rj45 connector, used on the enc28j60 ethernet modules. rj45 datasheet

what a pity! all the 8 pins are galvanically isolated. i needed access to pins 4+5 for dc+, respectively pins 7+8 for dc-. poe pinouts

custom made ethernet cable: on the router end has an additional usb cable, serving to inject 5v dc. this will be powered from the unused usb port on my router. the other end is just a standard rj45 connector.

hacking the rj45:

it is possible to open the metal sheet on the connector. then i’ve removed some plastic with a red-hot cutter blade, to expose the pins.

the isolation transformers for rx and tx are clearly visible

cleaning and soldering the wires to the selected pins was easy. for tapping i’ve removed one of the lateral side tin. after putting some layers of insulation to the exposed pins i’ve closed the connector.

the terminal wires were soldered to the appropriate INPUT pins (+5v and gnd) on the micro usb charger module. now i have a real poe module!

attention:
do not solder the +5v cable to the charger module OUTPUT, because it will overcharge the lithium battery! lithium batteries, if charged beyond 4.3v can explode or catch fire!

of course, this modification doesn’t deal with the two 75 ohm resistors, which kinda “short” the usb port.

but if you do the math: 2 x 75r = 150r. for 5v / 150r = 33mA extra current consumption for the usb port. the usb port standard specifies at least 500mA / port. the whole device does not absorb more than 200 mA, i think this is on the safe side.

regarding the heat production on the two 75 ohm resistors:
0.033A x 5v = 0,166W total. there are 2 resistors, so this is 0.083W / resistor. even if the resistors will burn out, i do not care, they are useless in this configuration (i think).

please note: using 5v dc with poe is not recommended on long cable runs, because, when load applied, the voltage drops quickly. in my case, i needed 5m ethernet cable. with the device connected, the 5v dropped to 4.3v. this means, that the charger module will output max 4.0 volts, so the battery will be never charged to 100%. this is not a problem for me, as the router will continuously supply the power. for much longer cables, one should consider using a dc to dc booster between the usb port and ethernet cable to compensate for the voltage drop.

bme280:

the v1.1.104 pcb has a nice feature, the extension port. i’ve populated this port with a bme280 module. bme280 specs

you can buy one here: bme ali

these sensors are very high quality and one can obtain a lots of info, with proper code implementation:
– temperature
– pressure
– altitude (uncalibrated)
– relative humidity
– dew point
– heat index (shadow)
– heat index (sunlight)

i’ve wrote a small arduino sketch to display all these values, using the SparkFunBME280 library. bme280 sketch

unfortunately, at the time of writing this article, the uradmonitor source code (v117) is not fully open. we have to wait for radhoo to implement this sensor, or much better, to publish the full source code on github.

case design:

for the device to be fully usable outdoors and to have a better visual experience, needs a case. i’ve designed the case in corel draw x8. made two very similar models, one for wall mounted fix station, one for portable device. despite my very limited knowledge in corel, i managed to finish it with quite good results. it was then laser cut from 3mm clear plexiglass.

since the enc28j60 chip produces a lot of heat, in a closed case this would deteriorate the temperature readings.
i’m interested in the REAL outdoor readings. if the temperature value is not correct, all the other values are useless. the humidity calculation formula is also based on temperature. accordingly, i had to assure a very good ventilation for the sensor.

designed a lots of ventilation holes on strategic parts of the case. these are circles 1.5mm in diameter. this is the smallest diameter the laser can cut, without melting too much plexi around. i hope the insects will not pass these holes. they will surely try. when winter coming, a ‘heated’ hotel is very attractive…

as hot air always goes up, the components arrangement is not very fortunate for the sensor, since it is placed exactly above the biggest heat source in the kit1.
i decided to mount the whole device upside down to the wall, this way the bme280 will be under the ethernet module. the ventilation holes should produce a chimney effect, that will take care to transport the air from bottom to top. theoretically, the sensor will always receive the unheated air from outside, obtaining correct readings.
i will test this theory when the device is mounted on the wall, placing an external temperature sensor near the case, and compare the 2 values.

while used as a fix station, the micro usb port will be out of order. hence, it will be covered with a cap, to keep the bugs at bay.

if anyone is interested to build one of these case, here are the corel draw x8 files:
fixed station with bme sensor
portable, without bme sensor

i will add new photos when it will be installed in its final place. for high resolution pictures you can visit: album

thank you radu for all the big effort and helpful attitude in this worldwide project!
thanks for reading,

written in 2016, oradea.

Voltage is not updated in uRADMonitorX for my old A1 model, now with 118 firmware. Maybe due to different prefix spelling? “vol:” vs “voltage:”

webserver:
URADMONITOR 11000003
type:1 hw:100 sw:118 SBM20radiation:18CPM (22.76CPM)
temperature:29.00C

vol:379V (46%/15.50kHz)
uptime:2764s wdt:3s

eth:10.0.0.24 (23.239.13.18)
http:200 46/46

JSON: {“data”:{ “id”:”11000003″,”type”:”1″,”detector”:”SBM20″,”voltage”:378,”cpm”:27,”temperature”:29.89,”uptime”: 160}}

My KIT1 which reports voltage fine in uRADMonitorX

webserver:
uRADMonitor 51000042
type:5 hw:103 sw:115 SBM20radiation:14CPM
average:21CPM
voltage:378V (69%)
ip:10.0.0.23
http:200

JSON: {“data”:{ “id”:”51000042″,”type”:”5″,”detector”:”SBM20″,”cpm”:18,”temperature”:0.00,”uptime”: 70203}}

Thanks for the note about the orientation of the tube, wasn’t sure if it was important. I originally based it on the photos from this blog post which shows the tube installed upside down: https://www.uradmonitor.com/model-kit1-production-ready/

I’ve swapped it around now and am looking for an enclosure to mount it in. Are there any specific requirements? Plastic, metal, height off the ground outdoors? Also if I was to add something like the BME280 would there need to be holes in the enclosure rather than having it watertight?

Regarding powering the device, something like this kit would be very useful: http://www.tp-link.com/en/products/details/cat-4794_TL-POE200.html

It allows you to inject a 12V into the spare cores on an Ethernet cable and pull them out at the other end (it’s an injector and splitter, and not a standard 802.3x POE).

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

so, i just put together the uradmonitor kit1, but i don’t have an isp programmer to upload the hex. but i have a lots of arduinos around…

this guide will show you how to upload the hex file to the uradmonitor kit1, using an arduino uno r3 + windoze

you will need:
– arduino uno
– 6 male to female jumper wires
– latest arduino ide
– hex file

please note: this article is for arduino uno r3, i will not explain here how to use other models. however, with a little googling + thinkering it is not complicated to adapt. for other mcu you can start here.

also, be sure to use tightly fitting jumper cables, you do not want to lose power or data while uploading the hex file! do not move / touch the setup while uploading!

steps:

0) download and install the latest arduino ide + drivers (arduino.cc)

1) open the ide, and go to: file > examples > arduinoisp and open the arduinoisp sketch

2) uncomment line 81 (// #define USE_OLD_STYLE_WIRING)

3) note the com port number in: tools > port (you will need this number later)

4) upload the sketch to the uno r3

5) close the arduino ide

6) remove the display (and ethernet module) from the uradmonitor board

7) unplug the arduino usb cable from the pc. connect the jumper wires as follows (see image):

uno -> kit1

gnd -> 4
5v -> 2
pin 10 (ss) -> 5
pin 11 (mosi) -> 1
pin 12 (miso) -> 9
pin 13 (sck) -> 7

it’s a good idea to write the arduino port numbers on the pcb, for future software upgrades:

8) double check the wiring between the uno and uradmonitor

9) copy ‘avrdude.conf’ file from*: c:\Users\wanek\AppData\Local\Arduino15\packages\arduino\tools\avrdude\6.3.0-arduino6\etc\
to: c:\Users\wanek\AppData\Local\Arduino15\packages\arduino\tools\avrdude\6.3.0-arduino6\bin\

*please note: the path can be slightly different, based on the ide version

10) copy the uradmonitor hex file to: c:\Users\wanek\AppData\Local\Arduino15\packages\arduino\tools\avrdude\6.0.1-arduino6\bin\ and rename to: ‘uradmonitor.hex’

11) open a terminal (go to start > search, type ‘cmd’ then press enter)

12) copy – paste this in the terminal (replace “wanek” with your user name):
cd c:\Users\wanek\AppData\Local\Arduino15\packages\arduino\tools\avrdude\6.3.0-arduino6\bin\

13) connect the arduino to the pc usb port

14) replace xx (use notepad) in step 15 and 16, with the port number you noted in step 4.

15) copy – paste in the terminal:
avrdude -P COMxx -b 19200 -c avrisp -p m328p -v -e -U lfuse:w:0xdc:m -U hfuse:w:0xdf:m

you should see something similar:

16) now enter this:
avrdude -P COMxx -b 19200 -c avrisp -p m328p -v -e -U flash:w:uradmonitor.hex -U lock:w:0x0F:m

it will take a while, but if you’re seeing this, it means you have succeeded!

17) unplug the usb cable, remove the jumper wires, remount the modules and power up the device. it should start up with the uradmonitor logo. now you can connect to the global network.

attention:
if something went wrong, and after hexing there are verification errors, answer no and try again. check the quality of the wiring, do not use too long cables (max. 20cm)

i’m not sure why these errors occur, but once i answered yes, and the process apparently halted. so i closed the terminal and after that, the microcontroller is not working… probably i’ve bricked it.

radhoo has some very detailed article about mcu flashing, here

written in 2016, using arduino ide 1.6.11, on windoze 1607.

hello everyone!

here is a post about my diy kit1, based on the v1.1.104 pcb. it was made with minor modifications / improvements regarding the original model. as radhoo said, maybe other builders will be interested in this, so i published here.

first of all, i’m a beginner in all this electronics and coding stuff, so if i wrote something stupid, please correct me. i’m always open for constructive criticism. second, sorry for my english, it is not my native language, but i’ll try to do my best 🙂

the differences compared to the original kit1 are:
– incorporated lithium battery
– built in battery charger module + micro usb port
– low dropout (0.17v) regulator
– real PoE connectivity, no additional cable / port needed on the device side, just the rj45 connector
– transparent case made from plexiglass

updated bom, with the components i used (if something is missing, please let me know):
BOM, updated

i have built 2 kits: one for me and on for a friend. ha asked to make it portable, because he will use mainly on field, as a mobile unit, outdoors and on industrial working sites.
this raised two challenge: the final product has to have a
– reliable and high capacity rechargeable battery
– a robust but not to bulky case

please note, that the components for these kits i bought from local stores, the best available quality. hence, these components visual aspect are differ from the originals, shipped with the kit1. i measured all of them before soldering, to make sure everything is up to the specs.

regarding the pcbs, after some emails, radhoo was so kind to send me 2 pieces, thank you again! because i didn’t want to ‘destroy’ these beauties, all the modifications are made without hacking the pcb.

power supply / charger / power consumption:

nowadays the “standard” power supply for handheld devices is the type b micro usb port. you can find them virtually everywhere. also, it is fairly easy and very cheap to implement into diy stuff, using these chinese modules:
battery charger, ali

as for the battery, probably everybody has access to some broken smartphones… although the phone or display is broken, chances are good that the battery is still functional. you just have to hook up to the output of the charging module and the input of the voltage stabiliser, it is ready to use.
i’ve used one cell from an old macbook battery, scavenged. it contains 4 lithium cells, similar like on this site:

they are roughly the size of the kit1 pcb. this way, the charger + battery ain’t cost anything to me (0.3 euro).
to keep a safe distance between the batteries aluminum foil and the bottom of the pcb, i’ve used 4 self adhesive rubber shoes, the ones used for furniture feets.

most lithium batteries have a nominal voltage of 3.6v (min 3.0v, max 4.2v). the recommended operating voltage for the kit1 is min 3.0v, max 3.3v. to take maximum use of the battery, i opted for a 3.0v voltage regulator. it has to have ultra low dropout voltage, in order to maximize battery life.
so, i had to replace the original lm1117 voltage stabiliser, lm1117 datasheet, because it has a large dropout voltage, 1.1v. (this would be 3.0 + 1.1 = 4.1v -> maybe just 5% of the overall battery capacity. not too efficient…)

after a lot of searching, i bought the MCP1700-3002E/TO regulator mcp1700 datasheet. it has very low dropout, only 0.17v. it means: 3.0 + 0.17 = 3.17v, i can use around 95% battery capacity. good.
the max output current for the mcp1700 is 250mA, and the max input voltage is 6.0v. as the lithium battery never goes above 4.2v, its ok for me.

to estimate the battery life, i’ve made some measurements:
(because the battery is quite old and tired, the 3700mA nominal capacity was irrelevant)
the kit1 has the following current consumption @ 3.0v (with the red led desoldered from the ethernet module):

offline mode, backlight off: 36mA
backlight: 18mA
online mode, backlight off: 147mA
maximum peak current: 170mA

in online mode, with fully charged battery (4.2v) it took 18 hours to discharge it to 2.9v.
discharging under 2.9v it is harmful for the lithium batteries lithium info, so even if the kit1 kept working at 2.9v, i stopped the measurement. it then took around 5 hours to fully charge the battery (from a usb port).

based on the above current consumption scenarios and the measured 18 hours, it is fairly safe to estimate 50 hours uptime in offline mode. more than adequate for daily use on the field.

this regulator has a different pinout, regarding the original model. i had to make a tricky implementation, but it worked.

at the moment, the only flaw is, that the kit1 keeps working even under 2.7v, over-discharging the battery. in the long run this will damage the lithium cell. the firmware should be modified to post a ‘low battery’ message to the screen and standby the unit, if the voltage drops below 2.85v. (we need to have full access to the source code to implement this)

also, it would be nice to have a voltage divider on the battery terminals (say 4.2v -> 3.0v) and implement a battery voltage monitoring function in the firmware. this way the user can have a feedback about the battery state. there are 2 unused analog pins on the mcu , this shouldn’t be a problem.

the MCP1700 needs 2 filtering capacitors to work properly. i’ve just replaced the original c3 with 1uf ceramic, the other one (cout) was soldered on the back side of the pcb.

because the charger module covered some holes of the on / off switch on the pcb, i’ve used a different switch, placed on the right side of my case:

PoE:

for the stationary unit installed outside, i wanted to have just one single cable (for supply + ethernet).
according to wikipedia poe wiki the poe standard uses 2 modes: A and B.

unfortunately, after some fiddling i’ve realised that none of these modes are implemented in the hr911105a rj45 connector, used on the enc28j60 ethernet modules. rj45 datasheet

what a pity! all the 8 pins are galvanically isolated. i needed access to pins 4+5 for dc+, respectively pins 7+8 for dc-. poe pinouts

custom made ethernet cable: on the router end has an additional usb cable, serving to inject 5v dc. this will be powered from the unused usb port on my router. the other end is just a standard rj45 connector.

hacking the rj45:

it is possible to open the metal sheet on the connector. then i’ve removed some plastic with a red-hot cutter blade, to expose the pins.

the isolation transformers for rx and tx are clearly visible

cleaning and soldering the wires to the selected pins was easy. for tapping i’ve removed one of the lateral side tin. after putting some layers of insulation to the exposed pins i’ve closed the connector.

the terminal wires were soldered to the appropriate INPUT pins (+5v and gnd) on the micro usb charger module. now i have a real poe module!

attention:
do not solder the +5v cable to the charger module OUTPUT, because it will overcharge the lithium battery! lithium batteries, if charged beyond 4.3v can explode or catch fire!

of course, this modification doesn’t deal with the two 75 ohm resistors, which kinda “short” the usb port.

but if you do the math: 2 x 75r = 150r. for 5v / 150r = 33mA extra current consumption for the usb port. the usb port standard specifies at least 500mA / port. the whole device does not absorb more than 200 mA, i think this is on the safe side.

regarding the heat production on the two 75 ohm resistors:
0.033A x 5v = 0,166W total. there are 2 resistors, so this is 0.083W / resistor. even if the resistors will burn out, i do not care, they are useless in this configuration (i think).

please note: using 5v dc with poe is not recommended on long cable runs, because, when load applied, the voltage drops quickly. in my case, i needed 5m ethernet cable. with the device connected, the 5v dropped to 4.3v. this means, that the charger module will output max 4.0 volts, so the battery will be never charged to 100%. this is not a problem for me, as the router will continuously supply the power. for much longer cables, one should consider using a dc to dc booster between the usb port and ethernet cable to compensate for the voltage drop.

bme280:

the v1.1.104 pcb has a nice feature, the extension port. i’ve populated this port with a bme280 module. bme280 specs

you can buy one here: bme ali

these sensors are very high quality and one can obtain a lots of info, with proper code implementation:
– temperature
– pressure
– altitude (uncalibrated)
– relative humidity
– dew point
– heat index (shadow)
– heat index (sunlight)

i’ve wrote a small arduino sketch to display all these values, using the SparkFunBME280 library. bme280 sketch

unfortunately, at the time of writing this article, the uradmonitor source code (v117) is not fully open. we have to wait for radhoo to implement this sensor, or much better, to publish the full source code on github.

case design:

for the device to be fully usable outdoors and to have a better visual experience, needs a case. i’ve designed the case in corel draw x8. made two very similar models, one for wall mounted fix station, one for portable device. despite my very limited knowledge in corel, i managed to finish it with quite good results. it was then laser cut from 3mm clear plexiglass.

since the enc28j60 chip produces a lot of heat, in a closed case this would deteriorate the temperature readings.
i’m interested in the REAL outdoor readings. if the temperature value is not correct, all the other values are useless. the humidity calculation formula is also based on temperature. accordingly, i had to assure a very good ventilation for the sensor.

designed a lots of ventilation holes on strategic parts of the case. these are circles 1.5mm in diameter. this is the smallest diameter the laser can cut, without melting too much plexi around. i hope the insects will not pass these holes. they will surely try. when winter coming, a ‘heated’ hotel is very attractive…

as hot air always goes up, the components arrangement is not very fortunate for the sensor, since it is placed exactly above the biggest heat source in the kit1.
i decided to mount the whole device upside down to the wall, this way the bme280 will be under the ethernet module. the ventilation holes should produce a chimney effect, that will take care to transport the air from bottom to top. theoretically, the sensor will always receive the unheated air from outside, obtaining correct readings.
i will test this theory when the device is mounted on the wall, placing an external temperature sensor near the case, and compare the 2 values.

while used as a fix station, the micro usb port will be out of order. hence, it will be covered with a cap, to keep the bugs at bay.

if anyone is interested to build one of these case, here are the corel draw x8 files:
fixed station with bme sensor
portable, without bme sensor

i will add new photos when it will be installed in its final place. for high resolution pictures you can visit: album

thank you radu for all the big effort and helpful attitude in this worldwide project!
thanks for reading,

written in 2016, oradea.

Voltage is not updated in uRADMonitorX for my old A1 model, now with 118 firmware. Maybe due to different prefix spelling? “vol:” vs “voltage:”

webserver:
URADMONITOR 11000003
type:1 hw:100 sw:118 SBM20radiation:18CPM (22.76CPM)
temperature:29.00C

vol:379V (46%/15.50kHz)
uptime:2764s wdt:3s

eth:10.0.0.24 (23.239.13.18)
http:200 46/46

JSON: {“data”:{ “id”:”11000003″,”type”:”1″,”detector”:”SBM20″,”voltage”:378,”cpm”:27,”temperature”:29.89,”uptime”: 160}}

My KIT1 which reports voltage fine in uRADMonitorX

webserver:
uRADMonitor 51000042
type:5 hw:103 sw:115 SBM20radiation:14CPM
average:21CPM
voltage:378V (69%)
ip:10.0.0.23
http:200

JSON: {“data”:{ “id”:”51000042″,”type”:”5″,”detector”:”SBM20″,”cpm”:18,”temperature”:0.00,”uptime”: 70203}}

Thanks for the note about the orientation of the tube, wasn’t sure if it was important. I originally based it on the photos from this blog post which shows the tube installed upside down: https://www.uradmonitor.com/model-kit1-production-ready/

I’ve swapped it around now and am looking for an enclosure to mount it in. Are there any specific requirements? Plastic, metal, height off the ground outdoors? Also if I was to add something like the BME280 would there need to be holes in the enclosure rather than having it watertight?

Regarding powering the device, something like this kit would be very useful: http://www.tp-link.com/en/products/details/cat-4794_TL-POE200.html

It allows you to inject a 12V into the spare cores on an Ethernet cable and pull them out at the other end (it’s an injector and splitter, and not a standard 802.3x POE).

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

so, i just put together the uradmonitor kit1, but i don’t have an isp programmer to upload the hex. but i have a lots of arduinos around…

this guide will show you how to upload the hex file to the uradmonitor kit1, using an arduino uno r3 + windoze

you will need:
– arduino uno
– 6 male to female jumper wires
– latest arduino ide
– hex file

please note: this article is for arduino uno r3, i will not explain here how to use other models. however, with a little googling + thinkering it is not complicated to adapt. for other mcu you can start here.

also, be sure to use tightly fitting jumper cables, you do not want to lose power or data while uploading the hex file! do not move / touch the setup while uploading!

steps:

0) download and install the latest arduino ide + drivers (arduino.cc)

1) open the ide, and go to: file > examples > arduinoisp and open the arduinoisp sketch

2) uncomment line 81 (// #define USE_OLD_STYLE_WIRING)

3) note the com port number in: tools > port (you will need this number later)

4) upload the sketch to the uno r3

5) close the arduino ide

6) remove the display (and ethernet module) from the uradmonitor board

7) unplug the arduino usb cable from the pc. connect the jumper wires as follows (see image):

uno -> kit1

gnd -> 4
5v -> 2
pin 10 (ss) -> 5
pin 11 (mosi) -> 1
pin 12 (miso) -> 9
pin 13 (sck) -> 7

it’s a good idea to write the arduino port numbers on the pcb, for future software upgrades:

8) double check the wiring between the uno and uradmonitor

9) copy ‘avrdude.conf’ file from*: c:\Users\wanek\AppData\Local\Arduino15\packages\arduino\tools\avrdude\6.3.0-arduino6\etc\
to: c:\Users\wanek\AppData\Local\Arduino15\packages\arduino\tools\avrdude\6.3.0-arduino6\bin\

*please note: the path can be slightly different, based on the ide version

10) copy the uradmonitor hex file to: c:\Users\wanek\AppData\Local\Arduino15\packages\arduino\tools\avrdude\6.0.1-arduino6\bin\ and rename to: ‘uradmonitor.hex’

11) open a terminal (go to start > search, type ‘cmd’ then press enter)

12) copy – paste this in the terminal (replace “wanek” with your user name):
cd c:\Users\wanek\AppData\Local\Arduino15\packages\arduino\tools\avrdude\6.3.0-arduino6\bin\

13) connect the arduino to the pc usb port

14) replace xx (use notepad) in step 15 and 16, with the port number you noted in step 4.

15) copy – paste in the terminal:
avrdude -P COMxx -b 19200 -c avrisp -p m328p -v -e -U lfuse:w:0xdc:m -U hfuse:w:0xdf:m

you should see something similar:

16) now enter this:
avrdude -P COMxx -b 19200 -c avrisp -p m328p -v -e -U flash:w:uradmonitor.hex -U lock:w:0x0F:m

it will take a while, but if you’re seeing this, it means you have succeeded!

17) unplug the usb cable, remove the jumper wires, remount the modules and power up the device. it should start up with the uradmonitor logo. now you can connect to the global network.

attention:
if something went wrong, and after hexing there are verification errors, answer no and try again. check the quality of the wiring, do not use too long cables (max. 20cm)

i’m not sure why these errors occur, but once i answered yes, and the process apparently halted. so i closed the terminal and after that, the microcontroller is not working… probably i’ve bricked it.

radhoo has some very detailed article about mcu flashing, here

written in 2016, using arduino ide 1.6.11, on windoze 1607.

hello everyone!

here is a post about my diy kit1, based on the v1.1.104 pcb. it was made with minor modifications / improvements regarding the original model. as radhoo said, maybe other builders will be interested in this, so i published here.

first of all, i’m a beginner in all this electronics and coding stuff, so if i wrote something stupid, please correct me. i’m always open for constructive criticism. second, sorry for my english, it is not my native language, but i’ll try to do my best 🙂

the differences compared to the original kit1 are:
– incorporated lithium battery
– built in battery charger module + micro usb port
– low dropout (0.17v) regulator
– real PoE connectivity, no additional cable / port needed on the device side, just the rj45 connector
– transparent case made from plexiglass

updated bom, with the components i used (if something is missing, please let me know):
BOM, updated

i have built 2 kits: one for me and on for a friend. ha asked to make it portable, because he will use mainly on field, as a mobile unit, outdoors and on industrial working sites.
this raised two challenge: the final product has to have a
– reliable and high capacity rechargeable battery
– a robust but not to bulky case

please note, that the components for these kits i bought from local stores, the best available quality. hence, these components visual aspect are differ from the originals, shipped with the kit1. i measured all of them before soldering, to make sure everything is up to the specs.

regarding the pcbs, after some emails, radhoo was so kind to send me 2 pieces, thank you again! because i didn’t want to ‘destroy’ these beauties, all the modifications are made without hacking the pcb.

power supply / charger / power consumption:

nowadays the “standard” power supply for handheld devices is the type b micro usb port. you can find them virtually everywhere. also, it is fairly easy and very cheap to implement into diy stuff, using these chinese modules:
battery charger, ali

as for the battery, probably everybody has access to some broken smartphones… although the phone or display is broken, chances are good that the battery is still functional. you just have to hook up to the output of the charging module and the input of the voltage stabiliser, it is ready to use.
i’ve used one cell from an old macbook battery, scavenged. it contains 4 lithium cells, similar like on this site:

they are roughly the size of the kit1 pcb. this way, the charger + battery ain’t cost anything to me (0.3 euro).
to keep a safe distance between the batteries aluminum foil and the bottom of the pcb, i’ve used 4 self adhesive rubber shoes, the ones used for furniture feets.

most lithium batteries have a nominal voltage of 3.6v (min 3.0v, max 4.2v). the recommended operating voltage for the kit1 is min 3.0v, max 3.3v. to take maximum use of the battery, i opted for a 3.0v voltage regulator. it has to have ultra low dropout voltage, in order to maximize battery life.
so, i had to replace the original lm1117 voltage stabiliser, lm1117 datasheet, because it has a large dropout voltage, 1.1v. (this would be 3.0 + 1.1 = 4.1v -> maybe just 5% of the overall battery capacity. not too efficient…)

after a lot of searching, i bought the MCP1700-3002E/TO regulator mcp1700 datasheet. it has very low dropout, only 0.17v. it means: 3.0 + 0.17 = 3.17v, i can use around 95% battery capacity. good.
the max output current for the mcp1700 is 250mA, and the max input voltage is 6.0v. as the lithium battery never goes above 4.2v, its ok for me.

to estimate the battery life, i’ve made some measurements:
(because the battery is quite old and tired, the 3700mA nominal capacity was irrelevant)
the kit1 has the following current consumption @ 3.0v (with the red led desoldered from the ethernet module):

offline mode, backlight off: 36mA
backlight: 18mA
online mode, backlight off: 147mA
maximum peak current: 170mA

in online mode, with fully charged battery (4.2v) it took 18 hours to discharge it to 2.9v.
discharging under 2.9v it is harmful for the lithium batteries lithium info, so even if the kit1 kept working at 2.9v, i stopped the measurement. it then took around 5 hours to fully charge the battery (from a usb port).

based on the above current consumption scenarios and the measured 18 hours, it is fairly safe to estimate 50 hours uptime in offline mode. more than adequate for daily use on the field.

this regulator has a different pinout, regarding the original model. i had to make a tricky implementation, but it worked.

at the moment, the only flaw is, that the kit1 keeps working even under 2.7v, over-discharging the battery. in the long run this will damage the lithium cell. the firmware should be modified to post a ‘low battery’ message to the screen and standby the unit, if the voltage drops below 2.85v. (we need to have full access to the source code to implement this)

also, it would be nice to have a voltage divider on the battery terminals (say 4.2v -> 3.0v) and implement a battery voltage monitoring function in the firmware. this way the user can have a feedback about the battery state. there are 2 unused analog pins on the mcu , this shouldn’t be a problem.

the MCP1700 needs 2 filtering capacitors to work properly. i’ve just replaced the original c3 with 1uf ceramic, the other one (cout) was soldered on the back side of the pcb.

because the charger module covered some holes of the on / off switch on the pcb, i’ve used a different switch, placed on the right side of my case:

PoE:

for the stationary unit installed outside, i wanted to have just one single cable (for supply + ethernet).
according to wikipedia poe wiki the poe standard uses 2 modes: A and B.

unfortunately, after some fiddling i’ve realised that none of these modes are implemented in the hr911105a rj45 connector, used on the enc28j60 ethernet modules. rj45 datasheet

what a pity! all the 8 pins are galvanically isolated. i needed access to pins 4+5 for dc+, respectively pins 7+8 for dc-. poe pinouts

custom made ethernet cable: on the router end has an additional usb cable, serving to inject 5v dc. this will be powered from the unused usb port on my router. the other end is just a standard rj45 connector.

hacking the rj45:

it is possible to open the metal sheet on the connector. then i’ve removed some plastic with a red-hot cutter blade, to expose the pins.

the isolation transformers for rx and tx are clearly visible

cleaning and soldering the wires to the selected pins was easy. for tapping i’ve removed one of the lateral side tin. after putting some layers of insulation to the exposed pins i’ve closed the connector.

the terminal wires were soldered to the appropriate INPUT pins (+5v and gnd) on the micro usb charger module. now i have a real poe module!

attention:
do not solder the +5v cable to the charger module OUTPUT, because it will overcharge the lithium battery! lithium batteries, if charged beyond 4.3v can explode or catch fire!

of course, this modification doesn’t deal with the two 75 ohm resistors, which kinda “short” the usb port.

but if you do the math: 2 x 75r = 150r. for 5v / 150r = 33mA extra current consumption for the usb port. the usb port standard specifies at least 500mA / port. the whole device does not absorb more than 200 mA, i think this is on the safe side.

regarding the heat production on the two 75 ohm resistors:
0.033A x 5v = 0,166W total. there are 2 resistors, so this is 0.083W / resistor. even if the resistors will burn out, i do not care, they are useless in this configuration (i think).

please note: using 5v dc with poe is not recommended on long cable runs, because, when load applied, the voltage drops quickly. in my case, i needed 5m ethernet cable. with the device connected, the 5v dropped to 4.3v. this means, that the charger module will output max 4.0 volts, so the battery will be never charged to 100%. this is not a problem for me, as the router will continuously supply the power. for much longer cables, one should consider using a dc to dc booster between the usb port and ethernet cable to compensate for the voltage drop.

bme280:

the v1.1.104 pcb has a nice feature, the extension port. i’ve populated this port with a bme280 module. bme280 specs

you can buy one here: bme ali

these sensors are very high quality and one can obtain a lots of info, with proper code implementation:
– temperature
– pressure
– altitude (uncalibrated)
– relative humidity
– dew point
– heat index (shadow)
– heat index (sunlight)

i’ve wrote a small arduino sketch to display all these values, using the SparkFunBME280 library. bme280 sketch

unfortunately, at the time of writing this article, the uradmonitor source code (v117) is not fully open. we have to wait for radhoo to implement this sensor, or much better, to publish the full source code on github.

case design:

for the device to be fully usable outdoors and to have a better visual experience, needs a case. i’ve designed the case in corel draw x8. made two very similar models, one for wall mounted fix station, one for portable device. despite my very limited knowledge in corel, i managed to finish it with quite good results. it was then laser cut from 3mm clear plexiglass.

since the enc28j60 chip produces a lot of heat, in a closed case this would deteriorate the temperature readings.
i’m interested in the REAL outdoor readings. if the temperature value is not correct, all the other values are useless. the humidity calculation formula is also based on temperature. accordingly, i had to assure a very good ventilation for the sensor.

designed a lots of ventilation holes on strategic parts of the case. these are circles 1.5mm in diameter. this is the smallest diameter the laser can cut, without melting too much plexi around. i hope the insects will not pass these holes. they will surely try. when winter coming, a ‘heated’ hotel is very attractive…

as hot air always goes up, the components arrangement is not very fortunate for the sensor, since it is placed exactly above the biggest heat source in the kit1.
i decided to mount the whole device upside down to the wall, this way the bme280 will be under the ethernet module. the ventilation holes should produce a chimney effect, that will take care to transport the air from bottom to top. theoretically, the sensor will always receive the unheated air from outside, obtaining correct readings.
i will test this theory when the device is mounted on the wall, placing an external temperature sensor near the case, and compare the 2 values.

while used as a fix station, the micro usb port will be out of order. hence, it will be covered with a cap, to keep the bugs at bay.

if anyone is interested to build one of these case, here are the corel draw x8 files:
fixed station with bme sensor
portable, without bme sensor

i will add new photos when it will be installed in its final place. for high resolution pictures you can visit: album

thank you radu for all the big effort and helpful attitude in this worldwide project!
thanks for reading,

written in 2016, oradea.

Voltage is not updated in uRADMonitorX for my old A1 model, now with 118 firmware. Maybe due to different prefix spelling? “vol:” vs “voltage:”

webserver:
URADMONITOR 11000003
type:1 hw:100 sw:118 SBM20radiation:18CPM (22.76CPM)
temperature:29.00C

vol:379V (46%/15.50kHz)
uptime:2764s wdt:3s

eth:10.0.0.24 (23.239.13.18)
http:200 46/46

JSON: {“data”:{ “id”:”11000003″,”type”:”1″,”detector”:”SBM20″,”voltage”:378,”cpm”:27,”temperature”:29.89,”uptime”: 160}}

My KIT1 which reports voltage fine in uRADMonitorX

webserver:
uRADMonitor 51000042
type:5 hw:103 sw:115 SBM20radiation:14CPM
average:21CPM
voltage:378V (69%)
ip:10.0.0.23
http:200

JSON: {“data”:{ “id”:”51000042″,”type”:”5″,”detector”:”SBM20″,”cpm”:18,”temperature”:0.00,”uptime”: 70203}}

Thanks for the note about the orientation of the tube, wasn’t sure if it was important. I originally based it on the photos from this blog post which shows the tube installed upside down: https://www.uradmonitor.com/model-kit1-production-ready/

I’ve swapped it around now and am looking for an enclosure to mount it in. Are there any specific requirements? Plastic, metal, height off the ground outdoors? Also if I was to add something like the BME280 would there need to be holes in the enclosure rather than having it watertight?

Regarding powering the device, something like this kit would be very useful: http://www.tp-link.com/en/products/details/cat-4794_TL-POE200.html

It allows you to inject a 12V into the spare cores on an Ethernet cable and pull them out at the other end (it’s an injector and splitter, and not a standard 802.3x POE).

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

so, i just put together the uradmonitor kit1, but i don’t have an isp programmer to upload the hex. but i have a lots of arduinos around…

this guide will show you how to upload the hex file to the uradmonitor kit1, using an arduino uno r3 + windoze

you will need:
– arduino uno
– 6 male to female jumper wires
– latest arduino ide
– hex file

please note: this article is for arduino uno r3, i will not explain here how to use other models. however, with a little googling + thinkering it is not complicated to adapt. for other mcu you can start here.

also, be sure to use tightly fitting jumper cables, you do not want to lose power or data while uploading the hex file! do not move / touch the setup while uploading!

steps:

0) download and install the latest arduino ide + drivers (arduino.cc)

1) open the ide, and go to: file > examples > arduinoisp and open the arduinoisp sketch

2) uncomment line 81 (// #define USE_OLD_STYLE_WIRING)

3) note the com port number in: tools > port (you will need this number later)

4) upload the sketch to the uno r3

5) close the arduino ide

6) remove the display (and ethernet module) from the uradmonitor board

7) unplug the arduino usb cable from the pc. connect the jumper wires as follows (see image):

uno -> kit1

gnd -> 4
5v -> 2
pin 10 (ss) -> 5
pin 11 (mosi) -> 1
pin 12 (miso) -> 9
pin 13 (sck) -> 7

it’s a good idea to write the arduino port numbers on the pcb, for future software upgrades:

8) double check the wiring between the uno and uradmonitor

9) copy ‘avrdude.conf’ file from*: c:\Users\wanek\AppData\Local\Arduino15\packages\arduino\tools\avrdude\6.3.0-arduino6\etc\
to: c:\Users\wanek\AppData\Local\Arduino15\packages\arduino\tools\avrdude\6.3.0-arduino6\bin\

*please note: the path can be slightly different, based on the ide version

10) copy the uradmonitor hex file to: c:\Users\wanek\AppData\Local\Arduino15\packages\arduino\tools\avrdude\6.0.1-arduino6\bin\ and rename to: ‘uradmonitor.hex’

11) open a terminal (go to start > search, type ‘cmd’ then press enter)

12) copy – paste this in the terminal (replace “wanek” with your user name):
cd c:\Users\wanek\AppData\Local\Arduino15\packages\arduino\tools\avrdude\6.3.0-arduino6\bin\

13) connect the arduino to the pc usb port

14) replace xx (use notepad) in step 15 and 16, with the port number you noted in step 4.

15) copy – paste in the terminal:
avrdude -P COMxx -b 19200 -c avrisp -p m328p -v -e -U lfuse:w:0xdc:m -U hfuse:w:0xdf:m

you should see something similar:

16) now enter this:
avrdude -P COMxx -b 19200 -c avrisp -p m328p -v -e -U flash:w:uradmonitor.hex -U lock:w:0x0F:m

it will take a while, but if you’re seeing this, it means you have succeeded!

17) unplug the usb cable, remove the jumper wires, remount the modules and power up the device. it should start up with the uradmonitor logo. now you can connect to the global network.

attention:
if something went wrong, and after hexing there are verification errors, answer no and try again. check the quality of the wiring, do not use too long cables (max. 20cm)

i’m not sure why these errors occur, but once i answered yes, and the process apparently halted. so i closed the terminal and after that, the microcontroller is not working… probably i’ve bricked it.

radhoo has some very detailed article about mcu flashing, here

written in 2016, using arduino ide 1.6.11, on windoze 1607.

hello everyone!

here is a post about my diy kit1, based on the v1.1.104 pcb. it was made with minor modifications / improvements regarding the original model. as radhoo said, maybe other builders will be interested in this, so i published here.

first of all, i’m a beginner in all this electronics and coding stuff, so if i wrote something stupid, please correct me. i’m always open for constructive criticism. second, sorry for my english, it is not my native language, but i’ll try to do my best 🙂

the differences compared to the original kit1 are:
– incorporated lithium battery
– built in battery charger module + micro usb port
– low dropout (0.17v) regulator
– real PoE connectivity, no additional cable / port needed on the device side, just the rj45 connector
– transparent case made from plexiglass

updated bom, with the components i used (if something is missing, please let me know):
BOM, updated

i have built 2 kits: one for me and on for a friend. ha asked to make it portable, because he will use mainly on field, as a mobile unit, outdoors and on industrial working sites.
this raised two challenge: the final product has to have a
– reliable and high capacity rechargeable battery
– a robust but not to bulky case

please note, that the components for these kits i bought from local stores, the best available quality. hence, these components visual aspect are differ from the originals, shipped with the kit1. i measured all of them before soldering, to make sure everything is up to the specs.

regarding the pcbs, after some emails, radhoo was so kind to send me 2 pieces, thank you again! because i didn’t want to ‘destroy’ these beauties, all the modifications are made without hacking the pcb.

power supply / charger / power consumption:

nowadays the “standard” power supply for handheld devices is the type b micro usb port. you can find them virtually everywhere. also, it is fairly easy and very cheap to implement into diy stuff, using these chinese modules:
battery charger, ali

as for the battery, probably everybody has access to some broken smartphones… although the phone or display is broken, chances are good that the battery is still functional. you just have to hook up to the output of the charging module and the input of the voltage stabiliser, it is ready to use.
i’ve used one cell from an old macbook battery, scavenged. it contains 4 lithium cells, similar like on this site:

they are roughly the size of the kit1 pcb. this way, the charger + battery ain’t cost anything to me (0.3 euro).
to keep a safe distance between the batteries aluminum foil and the bottom of the pcb, i’ve used 4 self adhesive rubber shoes, the ones used for furniture feets.

most lithium batteries have a nominal voltage of 3.6v (min 3.0v, max 4.2v). the recommended operating voltage for the kit1 is min 3.0v, max 3.3v. to take maximum use of the battery, i opted for a 3.0v voltage regulator. it has to have ultra low dropout voltage, in order to maximize battery life.
so, i had to replace the original lm1117 voltage stabiliser, lm1117 datasheet, because it has a large dropout voltage, 1.1v. (this would be 3.0 + 1.1 = 4.1v -> maybe just 5% of the overall battery capacity. not too efficient…)

after a lot of searching, i bought the MCP1700-3002E/TO regulator mcp1700 datasheet. it has very low dropout, only 0.17v. it means: 3.0 + 0.17 = 3.17v, i can use around 95% battery capacity. good.
the max output current for the mcp1700 is 250mA, and the max input voltage is 6.0v. as the lithium battery never goes above 4.2v, its ok for me.

to estimate the battery life, i’ve made some measurements:
(because the battery is quite old and tired, the 3700mA nominal capacity was irrelevant)
the kit1 has the following current consumption @ 3.0v (with the red led desoldered from the ethernet module):

offline mode, backlight off: 36mA
backlight: 18mA
online mode, backlight off: 147mA
maximum peak current: 170mA

in online mode, with fully charged battery (4.2v) it took 18 hours to discharge it to 2.9v.
discharging under 2.9v it is harmful for the lithium batteries lithium info, so even if the kit1 kept working at 2.9v, i stopped the measurement. it then took around 5 hours to fully charge the battery (from a usb port).

based on the above current consumption scenarios and the measured 18 hours, it is fairly safe to estimate 50 hours uptime in offline mode. more than adequate for daily use on the field.

this regulator has a different pinout, regarding the original model. i had to make a tricky implementation, but it worked.

at the moment, the only flaw is, that the kit1 keeps working even under 2.7v, over-discharging the battery. in the long run this will damage the lithium cell. the firmware should be modified to post a ‘low battery’ message to the screen and standby the unit, if the voltage drops below 2.85v. (we need to have full access to the source code to implement this)

also, it would be nice to have a voltage divider on the battery terminals (say 4.2v -> 3.0v) and implement a battery voltage monitoring function in the firmware. this way the user can have a feedback about the battery state. there are 2 unused analog pins on the mcu , this shouldn’t be a problem.

the MCP1700 needs 2 filtering capacitors to work properly. i’ve just replaced the original c3 with 1uf ceramic, the other one (cout) was soldered on the back side of the pcb.

because the charger module covered some holes of the on / off switch on the pcb, i’ve used a different switch, placed on the right side of my case:

PoE:

for the stationary unit installed outside, i wanted to have just one single cable (for supply + ethernet).
according to wikipedia poe wiki the poe standard uses 2 modes: A and B.

unfortunately, after some fiddling i’ve realised that none of these modes are implemented in the hr911105a rj45 connector, used on the enc28j60 ethernet modules. rj45 datasheet

what a pity! all the 8 pins are galvanically isolated. i needed access to pins 4+5 for dc+, respectively pins 7+8 for dc-. poe pinouts

custom made ethernet cable: on the router end has an additional usb cable, serving to inject 5v dc. this will be powered from the unused usb port on my router. the other end is just a standard rj45 connector.

hacking the rj45:

it is possible to open the metal sheet on the connector. then i’ve removed some plastic with a red-hot cutter blade, to expose the pins.

the isolation transformers for rx and tx are clearly visible

cleaning and soldering the wires to the selected pins was easy. for tapping i’ve removed one of the lateral side tin. after putting some layers of insulation to the exposed pins i’ve closed the connector.

the terminal wires were soldered to the appropriate INPUT pins (+5v and gnd) on the micro usb charger module. now i have a real poe module!

attention:
do not solder the +5v cable to the charger module OUTPUT, because it will overcharge the lithium battery! lithium batteries, if charged beyond 4.3v can explode or catch fire!

of course, this modification doesn’t deal with the two 75 ohm resistors, which kinda “short” the usb port.

but if you do the math: 2 x 75r = 150r. for 5v / 150r = 33mA extra current consumption for the usb port. the usb port standard specifies at least 500mA / port. the whole device does not absorb more than 200 mA, i think this is on the safe side.

regarding the heat production on the two 75 ohm resistors:
0.033A x 5v = 0,166W total. there are 2 resistors, so this is 0.083W / resistor. even if the resistors will burn out, i do not care, they are useless in this configuration (i think).

please note: using 5v dc with poe is not recommended on long cable runs, because, when load applied, the voltage drops quickly. in my case, i needed 5m ethernet cable. with the device connected, the 5v dropped to 4.3v. this means, that the charger module will output max 4.0 volts, so the battery will be never charged to 100%. this is not a problem for me, as the router will continuously supply the power. for much longer cables, one should consider using a dc to dc booster between the usb port and ethernet cable to compensate for the voltage drop.

bme280:

the v1.1.104 pcb has a nice feature, the extension port. i’ve populated this port with a bme280 module. bme280 specs

you can buy one here: bme ali

these sensors are very high quality and one can obtain a lots of info, with proper code implementation:
– temperature
– pressure
– altitude (uncalibrated)
– relative humidity
– dew point
– heat index (shadow)
– heat index (sunlight)

i’ve wrote a small arduino sketch to display all these values, using the SparkFunBME280 library. bme280 sketch

unfortunately, at the time of writing this article, the uradmonitor source code (v117) is not fully open. we have to wait for radhoo to implement this sensor, or much better, to publish the full source code on github.

case design:

for the device to be fully usable outdoors and to have a better visual experience, needs a case. i’ve designed the case in corel draw x8. made two very similar models, one for wall mounted fix station, one for portable device. despite my very limited knowledge in corel, i managed to finish it with quite good results. it was then laser cut from 3mm clear plexiglass.

since the enc28j60 chip produces a lot of heat, in a closed case this would deteriorate the temperature readings.
i’m interested in the REAL outdoor readings. if the temperature value is not correct, all the other values are useless. the humidity calculation formula is also based on temperature. accordingly, i had to assure a very good ventilation for the sensor.

designed a lots of ventilation holes on strategic parts of the case. these are circles 1.5mm in diameter. this is the smallest diameter the laser can cut, without melting too much plexi around. i hope the insects will not pass these holes. they will surely try. when winter coming, a ‘heated’ hotel is very attractive…

as hot air always goes up, the components arrangement is not very fortunate for the sensor, since it is placed exactly above the biggest heat source in the kit1.
i decided to mount the whole device upside down to the wall, this way the bme280 will be under the ethernet module. the ventilation holes should produce a chimney effect, that will take care to transport the air from bottom to top. theoretically, the sensor will always receive the unheated air from outside, obtaining correct readings.
i will test this theory when the device is mounted on the wall, placing an external temperature sensor near the case, and compare the 2 values.

while used as a fix station, the micro usb port will be out of order. hence, it will be covered with a cap, to keep the bugs at bay.

if anyone is interested to build one of these case, here are the corel draw x8 files:
fixed station with bme sensor
portable, without bme sensor

i will add new photos when it will be installed in its final place. for high resolution pictures you can visit: album

thank you radu for all the big effort and helpful attitude in this worldwide project!
thanks for reading,

written in 2016, oradea.

Voltage is not updated in uRADMonitorX for my old A1 model, now with 118 firmware. Maybe due to different prefix spelling? “vol:” vs “voltage:”

webserver:
URADMONITOR 11000003
type:1 hw:100 sw:118 SBM20radiation:18CPM (22.76CPM)
temperature:29.00C

vol:379V (46%/15.50kHz)
uptime:2764s wdt:3s

eth:10.0.0.24 (23.239.13.18)
http:200 46/46

JSON: {“data”:{ “id”:”11000003″,”type”:”1″,”detector”:”SBM20″,”voltage”:378,”cpm”:27,”temperature”:29.89,”uptime”: 160}}

My KIT1 which reports voltage fine in uRADMonitorX

webserver:
uRADMonitor 51000042
type:5 hw:103 sw:115 SBM20radiation:14CPM
average:21CPM
voltage:378V (69%)
ip:10.0.0.23
http:200

JSON: {“data”:{ “id”:”51000042″,”type”:”5″,”detector”:”SBM20″,”cpm”:18,”temperature”:0.00,”uptime”: 70203}}

Thanks for the note about the orientation of the tube, wasn’t sure if it was important. I originally based it on the photos from this blog post which shows the tube installed upside down: https://www.uradmonitor.com/model-kit1-production-ready/

I’ve swapped it around now and am looking for an enclosure to mount it in. Are there any specific requirements? Plastic, metal, height off the ground outdoors? Also if I was to add something like the BME280 would there need to be holes in the enclosure rather than having it watertight?

Regarding powering the device, something like this kit would be very useful: http://www.tp-link.com/en/products/details/cat-4794_TL-POE200.html

It allows you to inject a 12V into the spare cores on an Ethernet cable and pull them out at the other end (it’s an injector and splitter, and not a standard 802.3x POE).

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

so, i just put together the uradmonitor kit1, but i don’t have an isp programmer to upload the hex. but i have a lots of arduinos around…

this guide will show you how to upload the hex file to the uradmonitor kit1, using an arduino uno r3 + windoze

you will need:
– arduino uno
– 6 male to female jumper wires
– latest arduino ide
– hex file

please note: this article is for arduino uno r3, i will not explain here how to use other models. however, with a little googling + thinkering it is not complicated to adapt. for other mcu you can start here.

also, be sure to use tightly fitting jumper cables, you do not want to lose power or data while uploading the hex file! do not move / touch the setup while uploading!

steps:

0) download and install the latest arduino ide + drivers (arduino.cc)

1) open the ide, and go to: file > examples > arduinoisp and open the arduinoisp sketch

2) uncomment line 81 (// #define USE_OLD_STYLE_WIRING)

3) note the com port number in: tools > port (you will need this number later)

4) upload the sketch to the uno r3

5) close the arduino ide

6) remove the display (and ethernet module) from the uradmonitor board

7) unplug the arduino usb cable from the pc. connect the jumper wires as follows (see image):

uno -> kit1

gnd -> 4
5v -> 2
pin 10 (ss) -> 5
pin 11 (mosi) -> 1
pin 12 (miso) -> 9
pin 13 (sck) -> 7

it’s a good idea to write the arduino port numbers on the pcb, for future software upgrades:

8) double check the wiring between the uno and uradmonitor

9) copy ‘avrdude.conf’ file from*: c:\Users\wanek\AppData\Local\Arduino15\packages\arduino\tools\avrdude\6.3.0-arduino6\etc\
to: c:\Users\wanek\AppData\Local\Arduino15\packages\arduino\tools\avrdude\6.3.0-arduino6\bin\

*please note: the path can be slightly different, based on the ide version

10) copy the uradmonitor hex file to: c:\Users\wanek\AppData\Local\Arduino15\packages\arduino\tools\avrdude\6.0.1-arduino6\bin\ and rename to: ‘uradmonitor.hex’

11) open a terminal (go to start > search, type ‘cmd’ then press enter)

12) copy – paste this in the terminal (replace “wanek” with your user name):
cd c:\Users\wanek\AppData\Local\Arduino15\packages\arduino\tools\avrdude\6.3.0-arduino6\bin\

13) connect the arduino to the pc usb port

14) replace xx (use notepad) in step 15 and 16, with the port number you noted in step 4.

15) copy – paste in the terminal:
avrdude -P COMxx -b 19200 -c avrisp -p m328p -v -e -U lfuse:w:0xdc:m -U hfuse:w:0xdf:m

you should see something similar:

16) now enter this:
avrdude -P COMxx -b 19200 -c avrisp -p m328p -v -e -U flash:w:uradmonitor.hex -U lock:w:0x0F:m

it will take a while, but if you’re seeing this, it means you have succeeded!

17) unplug the usb cable, remove the jumper wires, remount the modules and power up the device. it should start up with the uradmonitor logo. now you can connect to the global network.

attention:
if something went wrong, and after hexing there are verification errors, answer no and try again. check the quality of the wiring, do not use too long cables (max. 20cm)

i’m not sure why these errors occur, but once i answered yes, and the process apparently halted. so i closed the terminal and after that, the microcontroller is not working… probably i’ve bricked it.

radhoo has some very detailed article about mcu flashing, here

written in 2016, using arduino ide 1.6.11, on windoze 1607.

hello everyone!

here is a post about my diy kit1, based on the v1.1.104 pcb. it was made with minor modifications / improvements regarding the original model. as radhoo said, maybe other builders will be interested in this, so i published here.

first of all, i’m a beginner in all this electronics and coding stuff, so if i wrote something stupid, please correct me. i’m always open for constructive criticism. second, sorry for my english, it is not my native language, but i’ll try to do my best 🙂

the differences compared to the original kit1 are:
– incorporated lithium battery
– built in battery charger module + micro usb port
– low dropout (0.17v) regulator
– real PoE connectivity, no additional cable / port needed on the device side, just the rj45 connector
– transparent case made from plexiglass

updated bom, with the components i used (if something is missing, please let me know):
BOM, updated

i have built 2 kits: one for me and on for a friend. ha asked to make it portable, because he will use mainly on field, as a mobile unit, outdoors and on industrial working sites.
this raised two challenge: the final product has to have a
– reliable and high capacity rechargeable battery
– a robust but not to bulky case

please note, that the components for these kits i bought from local stores, the best available quality. hence, these components visual aspect are differ from the originals, shipped with the kit1. i measured all of them before soldering, to make sure everything is up to the specs.

regarding the pcbs, after some emails, radhoo was so kind to send me 2 pieces, thank you again! because i didn’t want to ‘destroy’ these beauties, all the modifications are made without hacking the pcb.

power supply / charger / power consumption:

nowadays the “standard” power supply for handheld devices is the type b micro usb port. you can find them virtually everywhere. also, it is fairly easy and very cheap to implement into diy stuff, using these chinese modules:
battery charger, ali

as for the battery, probably everybody has access to some broken smartphones… although the phone or display is broken, chances are good that the battery is still functional. you just have to hook up to the output of the charging module and the input of the voltage stabiliser, it is ready to use.
i’ve used one cell from an old macbook battery, scavenged. it contains 4 lithium cells, similar like on this site:

they are roughly the size of the kit1 pcb. this way, the charger + battery ain’t cost anything to me (0.3 euro).
to keep a safe distance between the batteries aluminum foil and the bottom of the pcb, i’ve used 4 self adhesive rubber shoes, the ones used for furniture feets.

most lithium batteries have a nominal voltage of 3.6v (min 3.0v, max 4.2v). the recommended operating voltage for the kit1 is min 3.0v, max 3.3v. to take maximum use of the battery, i opted for a 3.0v voltage regulator. it has to have ultra low dropout voltage, in order to maximize battery life.
so, i had to replace the original lm1117 voltage stabiliser, lm1117 datasheet, because it has a large dropout voltage, 1.1v. (this would be 3.0 + 1.1 = 4.1v -> maybe just 5% of the overall battery capacity. not too efficient…)

after a lot of searching, i bought the MCP1700-3002E/TO regulator mcp1700 datasheet. it has very low dropout, only 0.17v. it means: 3.0 + 0.17 = 3.17v, i can use around 95% battery capacity. good.
the max output current for the mcp1700 is 250mA, and the max input voltage is 6.0v. as the lithium battery never goes above 4.2v, its ok for me.

to estimate the battery life, i’ve made some measurements:
(because the battery is quite old and tired, the 3700mA nominal capacity was irrelevant)
the kit1 has the following current consumption @ 3.0v (with the red led desoldered from the ethernet module):

offline mode, backlight off: 36mA
backlight: 18mA
online mode, backlight off: 147mA
maximum peak current: 170mA

in online mode, with fully charged battery (4.2v) it took 18 hours to discharge it to 2.9v.
discharging under 2.9v it is harmful for the lithium batteries lithium info, so even if the kit1 kept working at 2.9v, i stopped the measurement. it then took around 5 hours to fully charge the battery (from a usb port).

based on the above current consumption scenarios and the measured 18 hours, it is fairly safe to estimate 50 hours uptime in offline mode. more than adequate for daily use on the field.

this regulator has a different pinout, regarding the original model. i had to make a tricky implementation, but it worked.

at the moment, the only flaw is, that the kit1 keeps working even under 2.7v, over-discharging the battery. in the long run this will damage the lithium cell. the firmware should be modified to post a ‘low battery’ message to the screen and standby the unit, if the voltage drops below 2.85v. (we need to have full access to the source code to implement this)

also, it would be nice to have a voltage divider on the battery terminals (say 4.2v -> 3.0v) and implement a battery voltage monitoring function in the firmware. this way the user can have a feedback about the battery state. there are 2 unused analog pins on the mcu , this shouldn’t be a problem.

the MCP1700 needs 2 filtering capacitors to work properly. i’ve just replaced the original c3 with 1uf ceramic, the other one (cout) was soldered on the back side of the pcb.

because the charger module covered some holes of the on / off switch on the pcb, i’ve used a different switch, placed on the right side of my case:

PoE:

for the stationary unit installed outside, i wanted to have just one single cable (for supply + ethernet).
according to wikipedia poe wiki the poe standard uses 2 modes: A and B.

unfortunately, after some fiddling i’ve realised that none of these modes are implemented in the hr911105a rj45 connector, used on the enc28j60 ethernet modules. rj45 datasheet

what a pity! all the 8 pins are galvanically isolated. i needed access to pins 4+5 for dc+, respectively pins 7+8 for dc-. poe pinouts

custom made ethernet cable: on the router end has an additional usb cable, serving to inject 5v dc. this will be powered from the unused usb port on my router. the other end is just a standard rj45 connector.

hacking the rj45:

it is possible to open the metal sheet on the connector. then i’ve removed some plastic with a red-hot cutter blade, to expose the pins.

the isolation transformers for rx and tx are clearly visible

cleaning and soldering the wires to the selected pins was easy. for tapping i’ve removed one of the lateral side tin. after putting some layers of insulation to the exposed pins i’ve closed the connector.

the terminal wires were soldered to the appropriate INPUT pins (+5v and gnd) on the micro usb charger module. now i have a real poe module!

attention:
do not solder the +5v cable to the charger module OUTPUT, because it will overcharge the lithium battery! lithium batteries, if charged beyond 4.3v can explode or catch fire!

of course, this modification doesn’t deal with the two 75 ohm resistors, which kinda “short” the usb port.

but if you do the math: 2 x 75r = 150r. for 5v / 150r = 33mA extra current consumption for the usb port. the usb port standard specifies at least 500mA / port. the whole device does not absorb more than 200 mA, i think this is on the safe side.

regarding the heat production on the two 75 ohm resistors:
0.033A x 5v = 0,166W total. there are 2 resistors, so this is 0.083W / resistor. even if the resistors will burn out, i do not care, they are useless in this configuration (i think).

please note: using 5v dc with poe is not recommended on long cable runs, because, when load applied, the voltage drops quickly. in my case, i needed 5m ethernet cable. with the device connected, the 5v dropped to 4.3v. this means, that the charger module will output max 4.0 volts, so the battery will be never charged to 100%. this is not a problem for me, as the router will continuously supply the power. for much longer cables, one should consider using a dc to dc booster between the usb port and ethernet cable to compensate for the voltage drop.

bme280:

the v1.1.104 pcb has a nice feature, the extension port. i’ve populated this port with a bme280 module. bme280 specs

you can buy one here: bme ali

these sensors are very high quality and one can obtain a lots of info, with proper code implementation:
– temperature
– pressure
– altitude (uncalibrated)
– relative humidity
– dew point
– heat index (shadow)
– heat index (sunlight)

i’ve wrote a small arduino sketch to display all these values, using the SparkFunBME280 library. bme280 sketch

unfortunately, at the time of writing this article, the uradmonitor source code (v117) is not fully open. we have to wait for radhoo to implement this sensor, or much better, to publish the full source code on github.

case design:

for the device to be fully usable outdoors and to have a better visual experience, needs a case. i’ve designed the case in corel draw x8. made two very similar models, one for wall mounted fix station, one for portable device. despite my very limited knowledge in corel, i managed to finish it with quite good results. it was then laser cut from 3mm clear plexiglass.

since the enc28j60 chip produces a lot of heat, in a closed case this would deteriorate the temperature readings.
i’m interested in the REAL outdoor readings. if the temperature value is not correct, all the other values are useless. the humidity calculation formula is also based on temperature. accordingly, i had to assure a very good ventilation for the sensor.

designed a lots of ventilation holes on strategic parts of the case. these are circles 1.5mm in diameter. this is the smallest diameter the laser can cut, without melting too much plexi around. i hope the insects will not pass these holes. they will surely try. when winter coming, a ‘heated’ hotel is very attractive…

as hot air always goes up, the components arrangement is not very fortunate for the sensor, since it is placed exactly above the biggest heat source in the kit1.
i decided to mount the whole device upside down to the wall, this way the bme280 will be under the ethernet module. the ventilation holes should produce a chimney effect, that will take care to transport the air from bottom to top. theoretically, the sensor will always receive the unheated air from outside, obtaining correct readings.
i will test this theory when the device is mounted on the wall, placing an external temperature sensor near the case, and compare the 2 values.

while used as a fix station, the micro usb port will be out of order. hence, it will be covered with a cap, to keep the bugs at bay.

if anyone is interested to build one of these case, here are the corel draw x8 files:
fixed station with bme sensor
portable, without bme sensor

i will add new photos when it will be installed in its final place. for high resolution pictures you can visit: album

thank you radu for all the big effort and helpful attitude in this worldwide project!
thanks for reading,

written in 2016, oradea.

Voltage is not updated in uRADMonitorX for my old A1 model, now with 118 firmware. Maybe due to different prefix spelling? “vol:” vs “voltage:”

webserver:
URADMONITOR 11000003
type:1 hw:100 sw:118 SBM20radiation:18CPM (22.76CPM)
temperature:29.00C

vol:379V (46%/15.50kHz)
uptime:2764s wdt:3s

eth:10.0.0.24 (23.239.13.18)
http:200 46/46

JSON: {“data”:{ “id”:”11000003″,”type”:”1″,”detector”:”SBM20″,”voltage”:378,”cpm”:27,”temperature”:29.89,”uptime”: 160}}

My KIT1 which reports voltage fine in uRADMonitorX

webserver:
uRADMonitor 51000042
type:5 hw:103 sw:115 SBM20radiation:14CPM
average:21CPM
voltage:378V (69%)
ip:10.0.0.23
http:200

JSON: {“data”:{ “id”:”51000042″,”type”:”5″,”detector”:”SBM20″,”cpm”:18,”temperature”:0.00,”uptime”: 70203}}

Thanks for the note about the orientation of the tube, wasn’t sure if it was important. I originally based it on the photos from this blog post which shows the tube installed upside down: https://www.uradmonitor.com/model-kit1-production-ready/

I’ve swapped it around now and am looking for an enclosure to mount it in. Are there any specific requirements? Plastic, metal, height off the ground outdoors? Also if I was to add something like the BME280 would there need to be holes in the enclosure rather than having it watertight?

Regarding powering the device, something like this kit would be very useful: http://www.tp-link.com/en/products/details/cat-4794_TL-POE200.html

It allows you to inject a 12V into the spare cores on an Ethernet cable and pull them out at the other end (it’s an injector and splitter, and not a standard 802.3x POE).

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

so, i just put together the uradmonitor kit1, but i don’t have an isp programmer to upload the hex. but i have a lots of arduinos around…

this guide will show you how to upload the hex file to the uradmonitor kit1, using an arduino uno r3 + windoze

you will need:
– arduino uno
– 6 male to female jumper wires
– latest arduino ide
– hex file

please note: this article is for arduino uno r3, i will not explain here how to use other models. however, with a little googling + thinkering it is not complicated to adapt. for other mcu you can start here.

also, be sure to use tightly fitting jumper cables, you do not want to lose power or data while uploading the hex file! do not move / touch the setup while uploading!

steps:

0) download and install the latest arduino ide + drivers (arduino.cc)

1) open the ide, and go to: file > examples > arduinoisp and open the arduinoisp sketch

2) uncomment line 81 (// #define USE_OLD_STYLE_WIRING)

3) note the com port number in: tools > port (you will need this number later)

4) upload the sketch to the uno r3

5) close the arduino ide

6) remove the display (and ethernet module) from the uradmonitor board

7) unplug the arduino usb cable from the pc. connect the jumper wires as follows (see image):

uno -> kit1

gnd -> 4
5v -> 2
pin 10 (ss) -> 5
pin 11 (mosi) -> 1
pin 12 (miso) -> 9
pin 13 (sck) -> 7

it’s a good idea to write the arduino port numbers on the pcb, for future software upgrades:

8) double check the wiring between the uno and uradmonitor

9) copy ‘avrdude.conf’ file from*: c:\Users\wanek\AppData\Local\Arduino15\packages\arduino\tools\avrdude\6.3.0-arduino6\etc\
to: c:\Users\wanek\AppData\Local\Arduino15\packages\arduino\tools\avrdude\6.3.0-arduino6\bin\

*please note: the path can be slightly different, based on the ide version

10) copy the uradmonitor hex file to: c:\Users\wanek\AppData\Local\Arduino15\packages\arduino\tools\avrdude\6.0.1-arduino6\bin\ and rename to: ‘uradmonitor.hex’

11) open a terminal (go to start > search, type ‘cmd’ then press enter)

12) copy – paste this in the terminal (replace “wanek” with your user name):
cd c:\Users\wanek\AppData\Local\Arduino15\packages\arduino\tools\avrdude\6.3.0-arduino6\bin\

13) connect the arduino to the pc usb port

14) replace xx (use notepad) in step 15 and 16, with the port number you noted in step 4.

15) copy – paste in the terminal:
avrdude -P COMxx -b 19200 -c avrisp -p m328p -v -e -U lfuse:w:0xdc:m -U hfuse:w:0xdf:m

you should see something similar:

16) now enter this:
avrdude -P COMxx -b 19200 -c avrisp -p m328p -v -e -U flash:w:uradmonitor.hex -U lock:w:0x0F:m

it will take a while, but if you’re seeing this, it means you have succeeded!

17) unplug the usb cable, remove the jumper wires, remount the modules and power up the device. it should start up with the uradmonitor logo. now you can connect to the global network.

attention:
if something went wrong, and after hexing there are verification errors, answer no and try again. check the quality of the wiring, do not use too long cables (max. 20cm)

i’m not sure why these errors occur, but once i answered yes, and the process apparently halted. so i closed the terminal and after that, the microcontroller is not working… probably i’ve bricked it.

radhoo has some very detailed article about mcu flashing, here

written in 2016, using arduino ide 1.6.11, on windoze 1607.

hello everyone!

here is a post about my diy kit1, based on the v1.1.104 pcb. it was made with minor modifications / improvements regarding the original model. as radhoo said, maybe other builders will be interested in this, so i published here.

first of all, i’m a beginner in all this electronics and coding stuff, so if i wrote something stupid, please correct me. i’m always open for constructive criticism. second, sorry for my english, it is not my native language, but i’ll try to do my best 🙂

the differences compared to the original kit1 are:
– incorporated lithium battery
– built in battery charger module + micro usb port
– low dropout (0.17v) regulator
– real PoE connectivity, no additional cable / port needed on the device side, just the rj45 connector
– transparent case made from plexiglass

updated bom, with the components i used (if something is missing, please let me know):
BOM, updated

i have built 2 kits: one for me and on for a friend. ha asked to make it portable, because he will use mainly on field, as a mobile unit, outdoors and on industrial working sites.
this raised two challenge: the final product has to have a
– reliable and high capacity rechargeable battery
– a robust but not to bulky case

please note, that the components for these kits i bought from local stores, the best available quality. hence, these components visual aspect are differ from the originals, shipped with the kit1. i measured all of them before soldering, to make sure everything is up to the specs.

regarding the pcbs, after some emails, radhoo was so kind to send me 2 pieces, thank you again! because i didn’t want to ‘destroy’ these beauties, all the modifications are made without hacking the pcb.

power supply / charger / power consumption:

nowadays the “standard” power supply for handheld devices is the type b micro usb port. you can find them virtually everywhere. also, it is fairly easy and very cheap to implement into diy stuff, using these chinese modules:
battery charger, ali

as for the battery, probably everybody has access to some broken smartphones… although the phone or display is broken, chances are good that the battery is still functional. you just have to hook up to the output of the charging module and the input of the voltage stabiliser, it is ready to use.
i’ve used one cell from an old macbook battery, scavenged. it contains 4 lithium cells, similar like on this site:

they are roughly the size of the kit1 pcb. this way, the charger + battery ain’t cost anything to me (0.3 euro).
to keep a safe distance between the batteries aluminum foil and the bottom of the pcb, i’ve used 4 self adhesive rubber shoes, the ones used for furniture feets.

most lithium batteries have a nominal voltage of 3.6v (min 3.0v, max 4.2v). the recommended operating voltage for the kit1 is min 3.0v, max 3.3v. to take maximum use of the battery, i opted for a 3.0v voltage regulator. it has to have ultra low dropout voltage, in order to maximize battery life.
so, i had to replace the original lm1117 voltage stabiliser, lm1117 datasheet, because it has a large dropout voltage, 1.1v. (this would be 3.0 + 1.1 = 4.1v -> maybe just 5% of the overall battery capacity. not too efficient…)

after a lot of searching, i bought the MCP1700-3002E/TO regulator mcp1700 datasheet. it has very low dropout, only 0.17v. it means: 3.0 + 0.17 = 3.17v, i can use around 95% battery capacity. good.
the max output current for the mcp1700 is 250mA, and the max input voltage is 6.0v. as the lithium battery never goes above 4.2v, its ok for me.

to estimate the battery life, i’ve made some measurements:
(because the battery is quite old and tired, the 3700mA nominal capacity was irrelevant)
the kit1 has the following current consumption @ 3.0v (with the red led desoldered from the ethernet module):

offline mode, backlight off: 36mA
backlight: 18mA
online mode, backlight off: 147mA
maximum peak current: 170mA

in online mode, with fully charged battery (4.2v) it took 18 hours to discharge it to 2.9v.
discharging under 2.9v it is harmful for the lithium batteries lithium info, so even if the kit1 kept working at 2.9v, i stopped the measurement. it then took around 5 hours to fully charge the battery (from a usb port).

based on the above current consumption scenarios and the measured 18 hours, it is fairly safe to estimate 50 hours uptime in offline mode. more than adequate for daily use on the field.

this regulator has a different pinout, regarding the original model. i had to make a tricky implementation, but it worked.

at the moment, the only flaw is, that the kit1 keeps working even under 2.7v, over-discharging the battery. in the long run this will damage the lithium cell. the firmware should be modified to post a ‘low battery’ message to the screen and standby the unit, if the voltage drops below 2.85v. (we need to have full access to the source code to implement this)

also, it would be nice to have a voltage divider on the battery terminals (say 4.2v -> 3.0v) and implement a battery voltage monitoring function in the firmware. this way the user can have a feedback about the battery state. there are 2 unused analog pins on the mcu , this shouldn’t be a problem.

the MCP1700 needs 2 filtering capacitors to work properly. i’ve just replaced the original c3 with 1uf ceramic, the other one (cout) was soldered on the back side of the pcb.

because the charger module covered some holes of the on / off switch on the pcb, i’ve used a different switch, placed on the right side of my case:

PoE:

for the stationary unit installed outside, i wanted to have just one single cable (for supply + ethernet).
according to wikipedia poe wiki the poe standard uses 2 modes: A and B.

unfortunately, after some fiddling i’ve realised that none of these modes are implemented in the hr911105a rj45 connector, used on the enc28j60 ethernet modules. rj45 datasheet

what a pity! all the 8 pins are galvanically isolated. i needed access to pins 4+5 for dc+, respectively pins 7+8 for dc-. poe pinouts

custom made ethernet cable: on the router end has an additional usb cable, serving to inject 5v dc. this will be powered from the unused usb port on my router. the other end is just a standard rj45 connector.

hacking the rj45:

it is possible to open the metal sheet on the connector. then i’ve removed some plastic with a red-hot cutter blade, to expose the pins.

the isolation transformers for rx and tx are clearly visible

cleaning and soldering the wires to the selected pins was easy. for tapping i’ve removed one of the lateral side tin. after putting some layers of insulation to the exposed pins i’ve closed the connector.

the terminal wires were soldered to the appropriate INPUT pins (+5v and gnd) on the micro usb charger module. now i have a real poe module!

attention:
do not solder the +5v cable to the charger module OUTPUT, because it will overcharge the lithium battery! lithium batteries, if charged beyond 4.3v can explode or catch fire!

of course, this modification doesn’t deal with the two 75 ohm resistors, which kinda “short” the usb port.

but if you do the math: 2 x 75r = 150r. for 5v / 150r = 33mA extra current consumption for the usb port. the usb port standard specifies at least 500mA / port. the whole device does not absorb more than 200 mA, i think this is on the safe side.

regarding the heat production on the two 75 ohm resistors:
0.033A x 5v = 0,166W total. there are 2 resistors, so this is 0.083W / resistor. even if the resistors will burn out, i do not care, they are useless in this configuration (i think).

please note: using 5v dc with poe is not recommended on long cable runs, because, when load applied, the voltage drops quickly. in my case, i needed 5m ethernet cable. with the device connected, the 5v dropped to 4.3v. this means, that the charger module will output max 4.0 volts, so the battery will be never charged to 100%. this is not a problem for me, as the router will continuously supply the power. for much longer cables, one should consider using a dc to dc booster between the usb port and ethernet cable to compensate for the voltage drop.

bme280:

the v1.1.104 pcb has a nice feature, the extension port. i’ve populated this port with a bme280 module. bme280 specs

you can buy one here: bme ali

these sensors are very high quality and one can obtain a lots of info, with proper code implementation:
– temperature
– pressure
– altitude (uncalibrated)
– relative humidity
– dew point
– heat index (shadow)
– heat index (sunlight)

i’ve wrote a small arduino sketch to display all these values, using the SparkFunBME280 library. bme280 sketch

unfortunately, at the time of writing this article, the uradmonitor source code (v117) is not fully open. we have to wait for radhoo to implement this sensor, or much better, to publish the full source code on github.

case design:

for the device to be fully usable outdoors and to have a better visual experience, needs a case. i’ve designed the case in corel draw x8. made two very similar models, one for wall mounted fix station, one for portable device. despite my very limited knowledge in corel, i managed to finish it with quite good results. it was then laser cut from 3mm clear plexiglass.

since the enc28j60 chip produces a lot of heat, in a closed case this would deteriorate the temperature readings.
i’m interested in the REAL outdoor readings. if the temperature value is not correct, all the other values are useless. the humidity calculation formula is also based on temperature. accordingly, i had to assure a very good ventilation for the sensor.

designed a lots of ventilation holes on strategic parts of the case. these are circles 1.5mm in diameter. this is the smallest diameter the laser can cut, without melting too much plexi around. i hope the insects will not pass these holes. they will surely try. when winter coming, a ‘heated’ hotel is very attractive…

as hot air always goes up, the components arrangement is not very fortunate for the sensor, since it is placed exactly above the biggest heat source in the kit1.
i decided to mount the whole device upside down to the wall, this way the bme280 will be under the ethernet module. the ventilation holes should produce a chimney effect, that will take care to transport the air from bottom to top. theoretically, the sensor will always receive the unheated air from outside, obtaining correct readings.
i will test this theory when the device is mounted on the wall, placing an external temperature sensor near the case, and compare the 2 values.

while used as a fix station, the micro usb port will be out of order. hence, it will be covered with a cap, to keep the bugs at bay.

if anyone is interested to build one of these case, here are the corel draw x8 files:
fixed station with bme sensor
portable, without bme sensor

i will add new photos when it will be installed in its final place. for high resolution pictures you can visit: album

thank you radu for all the big effort and helpful attitude in this worldwide project!
thanks for reading,

written in 2016, oradea.

Voltage is not updated in uRADMonitorX for my old A1 model, now with 118 firmware. Maybe due to different prefix spelling? “vol:” vs “voltage:”

webserver:
URADMONITOR 11000003
type:1 hw:100 sw:118 SBM20radiation:18CPM (22.76CPM)
temperature:29.00C

vol:379V (46%/15.50kHz)
uptime:2764s wdt:3s

eth:10.0.0.24 (23.239.13.18)
http:200 46/46

JSON: {“data”:{ “id”:”11000003″,”type”:”1″,”detector”:”SBM20″,”voltage”:378,”cpm”:27,”temperature”:29.89,”uptime”: 160}}

My KIT1 which reports voltage fine in uRADMonitorX

webserver:
uRADMonitor 51000042
type:5 hw:103 sw:115 SBM20radiation:14CPM
average:21CPM
voltage:378V (69%)
ip:10.0.0.23
http:200

JSON: {“data”:{ “id”:”51000042″,”type”:”5″,”detector”:”SBM20″,”cpm”:18,”temperature”:0.00,”uptime”: 70203}}

Thanks for the note about the orientation of the tube, wasn’t sure if it was important. I originally based it on the photos from this blog post which shows the tube installed upside down: https://www.uradmonitor.com/model-kit1-production-ready/

I’ve swapped it around now and am looking for an enclosure to mount it in. Are there any specific requirements? Plastic, metal, height off the ground outdoors? Also if I was to add something like the BME280 would there need to be holes in the enclosure rather than having it watertight?

Regarding powering the device, something like this kit would be very useful: http://www.tp-link.com/en/products/details/cat-4794_TL-POE200.html

It allows you to inject a 12V into the spare cores on an Ethernet cable and pull them out at the other end (it’s an injector and splitter, and not a standard 802.3x POE).

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

so, i just put together the uradmonitor kit1, but i don’t have an isp programmer to upload the hex. but i have a lots of arduinos around…

this guide will show you how to upload the hex file to the uradmonitor kit1, using an arduino uno r3 + windoze

you will need:
– arduino uno
– 6 male to female jumper wires
– latest arduino ide
– hex file

please note: this article is for arduino uno r3, i will not explain here how to use other models. however, with a little googling + thinkering it is not complicated to adapt. for other mcu you can start here.

also, be sure to use tightly fitting jumper cables, you do not want to lose power or data while uploading the hex file! do not move / touch the setup while uploading!

steps:

0) download and install the latest arduino ide + drivers (arduino.cc)

1) open the ide, and go to: file > examples > arduinoisp and open the arduinoisp sketch

2) uncomment line 81 (// #define USE_OLD_STYLE_WIRING)

3) note the com port number in: tools > port (you will need this number later)

4) upload the sketch to the uno r3

5) close the arduino ide

6) remove the display (and ethernet module) from the uradmonitor board

7) unplug the arduino usb cable from the pc. connect the jumper wires as follows (see image):

uno -> kit1

gnd -> 4
5v -> 2
pin 10 (ss) -> 5
pin 11 (mosi) -> 1
pin 12 (miso) -> 9
pin 13 (sck) -> 7

it’s a good idea to write the arduino port numbers on the pcb, for future software upgrades:

8) double check the wiring between the uno and uradmonitor

9) copy ‘avrdude.conf’ file from*: c:\Users\wanek\AppData\Local\Arduino15\packages\arduino\tools\avrdude\6.3.0-arduino6\etc\
to: c:\Users\wanek\AppData\Local\Arduino15\packages\arduino\tools\avrdude\6.3.0-arduino6\bin\

*please note: the path can be slightly different, based on the ide version

10) copy the uradmonitor hex file to: c:\Users\wanek\AppData\Local\Arduino15\packages\arduino\tools\avrdude\6.0.1-arduino6\bin\ and rename to: ‘uradmonitor.hex’

11) open a terminal (go to start > search, type ‘cmd’ then press enter)

12) copy – paste this in the terminal (replace “wanek” with your user name):
cd c:\Users\wanek\AppData\Local\Arduino15\packages\arduino\tools\avrdude\6.3.0-arduino6\bin\

13) connect the arduino to the pc usb port

14) replace xx (use notepad) in step 15 and 16, with the port number you noted in step 4.

15) copy – paste in the terminal:
avrdude -P COMxx -b 19200 -c avrisp -p m328p -v -e -U lfuse:w:0xdc:m -U hfuse:w:0xdf:m

you should see something similar:

16) now enter this:
avrdude -P COMxx -b 19200 -c avrisp -p m328p -v -e -U flash:w:uradmonitor.hex -U lock:w:0x0F:m

it will take a while, but if you’re seeing this, it means you have succeeded!

17) unplug the usb cable, remove the jumper wires, remount the modules and power up the device. it should start up with the uradmonitor logo. now you can connect to the global network.

attention:
if something went wrong, and after hexing there are verification errors, answer no and try again. check the quality of the wiring, do not use too long cables (max. 20cm)

i’m not sure why these errors occur, but once i answered yes, and the process apparently halted. so i closed the terminal and after that, the microcontroller is not working… probably i’ve bricked it.

radhoo has some very detailed article about mcu flashing, here

written in 2016, using arduino ide 1.6.11, on windoze 1607.

hello everyone!

here is a post about my diy kit1, based on the v1.1.104 pcb. it was made with minor modifications / improvements regarding the original model. as radhoo said, maybe other builders will be interested in this, so i published here.

first of all, i’m a beginner in all this electronics and coding stuff, so if i wrote something stupid, please correct me. i’m always open for constructive criticism. second, sorry for my english, it is not my native language, but i’ll try to do my best 🙂

the differences compared to the original kit1 are:
– incorporated lithium battery
– built in battery charger module + micro usb port
– low dropout (0.17v) regulator
– real PoE connectivity, no additional cable / port needed on the device side, just the rj45 connector
– transparent case made from plexiglass

updated bom, with the components i used (if something is missing, please let me know):
BOM, updated

i have built 2 kits: one for me and on for a friend. ha asked to make it portable, because he will use mainly on field, as a mobile unit, outdoors and on industrial working sites.
this raised two challenge: the final product has to have a
– reliable and high capacity rechargeable battery
– a robust but not to bulky case

please note, that the components for these kits i bought from local stores, the best available quality. hence, these components visual aspect are differ from the originals, shipped with the kit1. i measured all of them before soldering, to make sure everything is up to the specs.

regarding the pcbs, after some emails, radhoo was so kind to send me 2 pieces, thank you again! because i didn’t want to ‘destroy’ these beauties, all the modifications are made without hacking the pcb.

power supply / charger / power consumption:

nowadays the “standard” power supply for handheld devices is the type b micro usb port. you can find them virtually everywhere. also, it is fairly easy and very cheap to implement into diy stuff, using these chinese modules:
battery charger, ali

as for the battery, probably everybody has access to some broken smartphones… although the phone or display is broken, chances are good that the battery is still functional. you just have to hook up to the output of the charging module and the input of the voltage stabiliser, it is ready to use.
i’ve used one cell from an old macbook battery, scavenged. it contains 4 lithium cells, similar like on this site:

they are roughly the size of the kit1 pcb. this way, the charger + battery ain’t cost anything to me (0.3 euro).
to keep a safe distance between the batteries aluminum foil and the bottom of the pcb, i’ve used 4 self adhesive rubber shoes, the ones used for furniture feets.

most lithium batteries have a nominal voltage of 3.6v (min 3.0v, max 4.2v). the recommended operating voltage for the kit1 is min 3.0v, max 3.3v. to take maximum use of the battery, i opted for a 3.0v voltage regulator. it has to have ultra low dropout voltage, in order to maximize battery life.
so, i had to replace the original lm1117 voltage stabiliser, lm1117 datasheet, because it has a large dropout voltage, 1.1v. (this would be 3.0 + 1.1 = 4.1v -> maybe just 5% of the overall battery capacity. not too efficient…)

after a lot of searching, i bought the MCP1700-3002E/TO regulator mcp1700 datasheet. it has very low dropout, only 0.17v. it means: 3.0 + 0.17 = 3.17v, i can use around 95% battery capacity. good.
the max output current for the mcp1700 is 250mA, and the max input voltage is 6.0v. as the lithium battery never goes above 4.2v, its ok for me.

to estimate the battery life, i’ve made some measurements:
(because the battery is quite old and tired, the 3700mA nominal capacity was irrelevant)
the kit1 has the following current consumption @ 3.0v (with the red led desoldered from the ethernet module):

offline mode, backlight off: 36mA
backlight: 18mA
online mode, backlight off: 147mA
maximum peak current: 170mA

in online mode, with fully charged battery (4.2v) it took 18 hours to discharge it to 2.9v.
discharging under 2.9v it is harmful for the lithium batteries lithium info, so even if the kit1 kept working at 2.9v, i stopped the measurement. it then took around 5 hours to fully charge the battery (from a usb port).

based on the above current consumption scenarios and the measured 18 hours, it is fairly safe to estimate 50 hours uptime in offline mode. more than adequate for daily use on the field.

this regulator has a different pinout, regarding the original model. i had to make a tricky implementation, but it worked.

at the moment, the only flaw is, that the kit1 keeps working even under 2.7v, over-discharging the battery. in the long run this will damage the lithium cell. the firmware should be modified to post a ‘low battery’ message to the screen and standby the unit, if the voltage drops below 2.85v. (we need to have full access to the source code to implement this)

also, it would be nice to have a voltage divider on the battery terminals (say 4.2v -> 3.0v) and implement a battery voltage monitoring function in the firmware. this way the user can have a feedback about the battery state. there are 2 unused analog pins on the mcu , this shouldn’t be a problem.

the MCP1700 needs 2 filtering capacitors to work properly. i’ve just replaced the original c3 with 1uf ceramic, the other one (cout) was soldered on the back side of the pcb.

because the charger module covered some holes of the on / off switch on the pcb, i’ve used a different switch, placed on the right side of my case:

PoE:

for the stationary unit installed outside, i wanted to have just one single cable (for supply + ethernet).
according to wikipedia poe wiki the poe standard uses 2 modes: A and B.

unfortunately, after some fiddling i’ve realised that none of these modes are implemented in the hr911105a rj45 connector, used on the enc28j60 ethernet modules. rj45 datasheet

what a pity! all the 8 pins are galvanically isolated. i needed access to pins 4+5 for dc+, respectively pins 7+8 for dc-. poe pinouts

custom made ethernet cable: on the router end has an additional usb cable, serving to inject 5v dc. this will be powered from the unused usb port on my router. the other end is just a standard rj45 connector.

hacking the rj45:

it is possible to open the metal sheet on the connector. then i’ve removed some plastic with a red-hot cutter blade, to expose the pins.

the isolation transformers for rx and tx are clearly visible

cleaning and soldering the wires to the selected pins was easy. for tapping i’ve removed one of the lateral side tin. after putting some layers of insulation to the exposed pins i’ve closed the connector.

the terminal wires were soldered to the appropriate INPUT pins (+5v and gnd) on the micro usb charger module. now i have a real poe module!

attention:
do not solder the +5v cable to the charger module OUTPUT, because it will overcharge the lithium battery! lithium batteries, if charged beyond 4.3v can explode or catch fire!

of course, this modification doesn’t deal with the two 75 ohm resistors, which kinda “short” the usb port.

but if you do the math: 2 x 75r = 150r. for 5v / 150r = 33mA extra current consumption for the usb port. the usb port standard specifies at least 500mA / port. the whole device does not absorb more than 200 mA, i think this is on the safe side.

regarding the heat production on the two 75 ohm resistors:
0.033A x 5v = 0,166W total. there are 2 resistors, so this is 0.083W / resistor. even if the resistors will burn out, i do not care, they are useless in this configuration (i think).

please note: using 5v dc with poe is not recommended on long cable runs, because, when load applied, the voltage drops quickly. in my case, i needed 5m ethernet cable. with the device connected, the 5v dropped to 4.3v. this means, that the charger module will output max 4.0 volts, so the battery will be never charged to 100%. this is not a problem for me, as the router will continuously supply the power. for much longer cables, one should consider using a dc to dc booster between the usb port and ethernet cable to compensate for the voltage drop.

bme280:

the v1.1.104 pcb has a nice feature, the extension port. i’ve populated this port with a bme280 module. bme280 specs

you can buy one here: bme ali

these sensors are very high quality and one can obtain a lots of info, with proper code implementation:
– temperature
– pressure
– altitude (uncalibrated)
– relative humidity
– dew point
– heat index (shadow)
– heat index (sunlight)

i’ve wrote a small arduino sketch to display all these values, using the SparkFunBME280 library. bme280 sketch

unfortunately, at the time of writing this article, the uradmonitor source code (v117) is not fully open. we have to wait for radhoo to implement this sensor, or much better, to publish the full source code on github.

case design:

for the device to be fully usable outdoors and to have a better visual experience, needs a case. i’ve designed the case in corel draw x8. made two very similar models, one for wall mounted fix station, one for portable device. despite my very limited knowledge in corel, i managed to finish it with quite good results. it was then laser cut from 3mm clear plexiglass.

since the enc28j60 chip produces a lot of heat, in a closed case this would deteriorate the temperature readings.
i’m interested in the REAL outdoor readings. if the temperature value is not correct, all the other values are useless. the humidity calculation formula is also based on temperature. accordingly, i had to assure a very good ventilation for the sensor.

designed a lots of ventilation holes on strategic parts of the case. these are circles 1.5mm in diameter. this is the smallest diameter the laser can cut, without melting too much plexi around. i hope the insects will not pass these holes. they will surely try. when winter coming, a ‘heated’ hotel is very attractive…

as hot air always goes up, the components arrangement is not very fortunate for the sensor, since it is placed exactly above the biggest heat source in the kit1.
i decided to mount the whole device upside down to the wall, this way the bme280 will be under the ethernet module. the ventilation holes should produce a chimney effect, that will take care to transport the air from bottom to top. theoretically, the sensor will always receive the unheated air from outside, obtaining correct readings.
i will test this theory when the device is mounted on the wall, placing an external temperature sensor near the case, and compare the 2 values.

while used as a fix station, the micro usb port will be out of order. hence, it will be covered with a cap, to keep the bugs at bay.

if anyone is interested to build one of these case, here are the corel draw x8 files:
fixed station with bme sensor
portable, without bme sensor

i will add new photos when it will be installed in its final place. for high resolution pictures you can visit: album

thank you radu for all the big effort and helpful attitude in this worldwide project!
thanks for reading,

written in 2016, oradea.

Voltage is not updated in uRADMonitorX for my old A1 model, now with 118 firmware. Maybe due to different prefix spelling? “vol:” vs “voltage:”

webserver:
URADMONITOR 11000003
type:1 hw:100 sw:118 SBM20radiation:18CPM (22.76CPM)
temperature:29.00C

vol:379V (46%/15.50kHz)
uptime:2764s wdt:3s

eth:10.0.0.24 (23.239.13.18)
http:200 46/46

JSON: {“data”:{ “id”:”11000003″,”type”:”1″,”detector”:”SBM20″,”voltage”:378,”cpm”:27,”temperature”:29.89,”uptime”: 160}}

My KIT1 which reports voltage fine in uRADMonitorX

webserver:
uRADMonitor 51000042
type:5 hw:103 sw:115 SBM20radiation:14CPM
average:21CPM
voltage:378V (69%)
ip:10.0.0.23
http:200

JSON: {“data”:{ “id”:”51000042″,”type”:”5″,”detector”:”SBM20″,”cpm”:18,”temperature”:0.00,”uptime”: 70203}}

Thanks for the note about the orientation of the tube, wasn’t sure if it was important. I originally based it on the photos from this blog post which shows the tube installed upside down: https://www.uradmonitor.com/model-kit1-production-ready/

I’ve swapped it around now and am looking for an enclosure to mount it in. Are there any specific requirements? Plastic, metal, height off the ground outdoors? Also if I was to add something like the BME280 would there need to be holes in the enclosure rather than having it watertight?

Regarding powering the device, something like this kit would be very useful: http://www.tp-link.com/en/products/details/cat-4794_TL-POE200.html

It allows you to inject a 12V into the spare cores on an Ethernet cable and pull them out at the other end (it’s an injector and splitter, and not a standard 802.3x POE).

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

so, i just put together the uradmonitor kit1, but i don’t have an isp programmer to upload the hex. but i have a lots of arduinos around…

this guide will show you how to upload the hex file to the uradmonitor kit1, using an arduino uno r3 + windoze

you will need:
– arduino uno
– 6 male to female jumper wires
– latest arduino ide
– hex file

please note: this article is for arduino uno r3, i will not explain here how to use other models. however, with a little googling + thinkering it is not complicated to adapt. for other mcu you can start here.

also, be sure to use tightly fitting jumper cables, you do not want to lose power or data while uploading the hex file! do not move / touch the setup while uploading!

steps:

0) download and install the latest arduino ide + drivers (arduino.cc)

1) open the ide, and go to: file > examples > arduinoisp and open the arduinoisp sketch

2) uncomment line 81 (// #define USE_OLD_STYLE_WIRING)

3) note the com port number in: tools > port (you will need this number later)

4) upload the sketch to the uno r3

5) close the arduino ide

6) remove the display (and ethernet module) from the uradmonitor board

7) unplug the arduino usb cable from the pc. connect the jumper wires as follows (see image):

uno -> kit1

gnd -> 4
5v -> 2
pin 10 (ss) -> 5
pin 11 (mosi) -> 1
pin 12 (miso) -> 9
pin 13 (sck) -> 7

it’s a good idea to write the arduino port numbers on the pcb, for future software upgrades:

8) double check the wiring between the uno and uradmonitor

9) copy ‘avrdude.conf’ file from*: c:\Users\wanek\AppData\Local\Arduino15\packages\arduino\tools\avrdude\6.3.0-arduino6\etc\
to: c:\Users\wanek\AppData\Local\Arduino15\packages\arduino\tools\avrdude\6.3.0-arduino6\bin\

*please note: the path can be slightly different, based on the ide version

10) copy the uradmonitor hex file to: c:\Users\wanek\AppData\Local\Arduino15\packages\arduino\tools\avrdude\6.0.1-arduino6\bin\ and rename to: ‘uradmonitor.hex’

11) open a terminal (go to start > search, type ‘cmd’ then press enter)

12) copy – paste this in the terminal (replace “wanek” with your user name):
cd c:\Users\wanek\AppData\Local\Arduino15\packages\arduino\tools\avrdude\6.3.0-arduino6\bin\

13) connect the arduino to the pc usb port

14) replace xx (use notepad) in step 15 and 16, with the port number you noted in step 4.

15) copy – paste in the terminal:
avrdude -P COMxx -b 19200 -c avrisp -p m328p -v -e -U lfuse:w:0xdc:m -U hfuse:w:0xdf:m

you should see something similar:

16) now enter this:
avrdude -P COMxx -b 19200 -c avrisp -p m328p -v -e -U flash:w:uradmonitor.hex -U lock:w:0x0F:m

it will take a while, but if you’re seeing this, it means you have succeeded!

17) unplug the usb cable, remove the jumper wires, remount the modules and power up the device. it should start up with the uradmonitor logo. now you can connect to the global network.

attention:
if something went wrong, and after hexing there are verification errors, answer no and try again. check the quality of the wiring, do not use too long cables (max. 20cm)

i’m not sure why these errors occur, but once i answered yes, and the process apparently halted. so i closed the terminal and after that, the microcontroller is not working… probably i’ve bricked it.

radhoo has some very detailed article about mcu flashing, here

written in 2016, using arduino ide 1.6.11, on windoze 1607.

hello everyone!

here is a post about my diy kit1, based on the v1.1.104 pcb. it was made with minor modifications / improvements regarding the original model. as radhoo said, maybe other builders will be interested in this, so i published here.

first of all, i’m a beginner in all this electronics and coding stuff, so if i wrote something stupid, please correct me. i’m always open for constructive criticism. second, sorry for my english, it is not my native language, but i’ll try to do my best 🙂

the differences compared to the original kit1 are:
– incorporated lithium battery
– built in battery charger module + micro usb port
– low dropout (0.17v) regulator
– real PoE connectivity, no additional cable / port needed on the device side, just the rj45 connector
– transparent case made from plexiglass

updated bom, with the components i used (if something is missing, please let me know):
BOM, updated

i have built 2 kits: one for me and on for a friend. ha asked to make it portable, because he will use mainly on field, as a mobile unit, outdoors and on industrial working sites.
this raised two challenge: the final product has to have a
– reliable and high capacity rechargeable battery
– a robust but not to bulky case

please note, that the components for these kits i bought from local stores, the best available quality. hence, these components visual aspect are differ from the originals, shipped with the kit1. i measured all of them before soldering, to make sure everything is up to the specs.

regarding the pcbs, after some emails, radhoo was so kind to send me 2 pieces, thank you again! because i didn’t want to ‘destroy’ these beauties, all the modifications are made without hacking the pcb.

power supply / charger / power consumption:

nowadays the “standard” power supply for handheld devices is the type b micro usb port. you can find them virtually everywhere. also, it is fairly easy and very cheap to implement into diy stuff, using these chinese modules:
battery charger, ali

as for the battery, probably everybody has access to some broken smartphones… although the phone or display is broken, chances are good that the battery is still functional. you just have to hook up to the output of the charging module and the input of the voltage stabiliser, it is ready to use.
i’ve used one cell from an old macbook battery, scavenged. it contains 4 lithium cells, similar like on this site:

they are roughly the size of the kit1 pcb. this way, the charger + battery ain’t cost anything to me (0.3 euro).
to keep a safe distance between the batteries aluminum foil and the bottom of the pcb, i’ve used 4 self adhesive rubber shoes, the ones used for furniture feets.

most lithium batteries have a nominal voltage of 3.6v (min 3.0v, max 4.2v). the recommended operating voltage for the kit1 is min 3.0v, max 3.3v. to take maximum use of the battery, i opted for a 3.0v voltage regulator. it has to have ultra low dropout voltage, in order to maximize battery life.
so, i had to replace the original lm1117 voltage stabiliser, lm1117 datasheet, because it has a large dropout voltage, 1.1v. (this would be 3.0 + 1.1 = 4.1v -> maybe just 5% of the overall battery capacity. not too efficient…)

after a lot of searching, i bought the MCP1700-3002E/TO regulator mcp1700 datasheet. it has very low dropout, only 0.17v. it means: 3.0 + 0.17 = 3.17v, i can use around 95% battery capacity. good.
the max output current for the mcp1700 is 250mA, and the max input voltage is 6.0v. as the lithium battery never goes above 4.2v, its ok for me.

to estimate the battery life, i’ve made some measurements:
(because the battery is quite old and tired, the 3700mA nominal capacity was irrelevant)
the kit1 has the following current consumption @ 3.0v (with the red led desoldered from the ethernet module):

offline mode, backlight off: 36mA
backlight: 18mA
online mode, backlight off: 147mA
maximum peak current: 170mA

in online mode, with fully charged battery (4.2v) it took 18 hours to discharge it to 2.9v.
discharging under 2.9v it is harmful for the lithium batteries lithium info, so even if the kit1 kept working at 2.9v, i stopped the measurement. it then took around 5 hours to fully charge the battery (from a usb port).

based on the above current consumption scenarios and the measured 18 hours, it is fairly safe to estimate 50 hours uptime in offline mode. more than adequate for daily use on the field.

this regulator has a different pinout, regarding the original model. i had to make a tricky implementation, but it worked.

at the moment, the only flaw is, that the kit1 keeps working even under 2.7v, over-discharging the battery. in the long run this will damage the lithium cell. the firmware should be modified to post a ‘low battery’ message to the screen and standby the unit, if the voltage drops below 2.85v. (we need to have full access to the source code to implement this)

also, it would be nice to have a voltage divider on the battery terminals (say 4.2v -> 3.0v) and implement a battery voltage monitoring function in the firmware. this way the user can have a feedback about the battery state. there are 2 unused analog pins on the mcu , this shouldn’t be a problem.

the MCP1700 needs 2 filtering capacitors to work properly. i’ve just replaced the original c3 with 1uf ceramic, the other one (cout) was soldered on the back side of the pcb.

because the charger module covered some holes of the on / off switch on the pcb, i’ve used a different switch, placed on the right side of my case:

PoE:

for the stationary unit installed outside, i wanted to have just one single cable (for supply + ethernet).
according to wikipedia poe wiki the poe standard uses 2 modes: A and B.

unfortunately, after some fiddling i’ve realised that none of these modes are implemented in the hr911105a rj45 connector, used on the enc28j60 ethernet modules. rj45 datasheet

what a pity! all the 8 pins are galvanically isolated. i needed access to pins 4+5 for dc+, respectively pins 7+8 for dc-. poe pinouts

custom made ethernet cable: on the router end has an additional usb cable, serving to inject 5v dc. this will be powered from the unused usb port on my router. the other end is just a standard rj45 connector.

hacking the rj45:

it is possible to open the metal sheet on the connector. then i’ve removed some plastic with a red-hot cutter blade, to expose the pins.

the isolation transformers for rx and tx are clearly visible

cleaning and soldering the wires to the selected pins was easy. for tapping i’ve removed one of the lateral side tin. after putting some layers of insulation to the exposed pins i’ve closed the connector.

the terminal wires were soldered to the appropriate INPUT pins (+5v and gnd) on the micro usb charger module. now i have a real poe module!

attention:
do not solder the +5v cable to the charger module OUTPUT, because it will overcharge the lithium battery! lithium batteries, if charged beyond 4.3v can explode or catch fire!

of course, this modification doesn’t deal with the two 75 ohm resistors, which kinda “short” the usb port.

but if you do the math: 2 x 75r = 150r. for 5v / 150r = 33mA extra current consumption for the usb port. the usb port standard specifies at least 500mA / port. the whole device does not absorb more than 200 mA, i think this is on the safe side.

regarding the heat production on the two 75 ohm resistors:
0.033A x 5v = 0,166W total. there are 2 resistors, so this is 0.083W / resistor. even if the resistors will burn out, i do not care, they are useless in this configuration (i think).

please note: using 5v dc with poe is not recommended on long cable runs, because, when load applied, the voltage drops quickly. in my case, i needed 5m ethernet cable. with the device connected, the 5v dropped to 4.3v. this means, that the charger module will output max 4.0 volts, so the battery will be never charged to 100%. this is not a problem for me, as the router will continuously supply the power. for much longer cables, one should consider using a dc to dc booster between the usb port and ethernet cable to compensate for the voltage drop.

bme280:

the v1.1.104 pcb has a nice feature, the extension port. i’ve populated this port with a bme280 module. bme280 specs

you can buy one here: bme ali

these sensors are very high quality and one can obtain a lots of info, with proper code implementation:
– temperature
– pressure
– altitude (uncalibrated)
– relative humidity
– dew point
– heat index (shadow)
– heat index (sunlight)

i’ve wrote a small arduino sketch to display all these values, using the SparkFunBME280 library. bme280 sketch

unfortunately, at the time of writing this article, the uradmonitor source code (v117) is not fully open. we have to wait for radhoo to implement this sensor, or much better, to publish the full source code on github.

case design:

for the device to be fully usable outdoors and to have a better visual experience, needs a case. i’ve designed the case in corel draw x8. made two very similar models, one for wall mounted fix station, one for portable device. despite my very limited knowledge in corel, i managed to finish it with quite good results. it was then laser cut from 3mm clear plexiglass.

since the enc28j60 chip produces a lot of heat, in a closed case this would deteriorate the temperature readings.
i’m interested in the REAL outdoor readings. if the temperature value is not correct, all the other values are useless. the humidity calculation formula is also based on temperature. accordingly, i had to assure a very good ventilation for the sensor.

designed a lots of ventilation holes on strategic parts of the case. these are circles 1.5mm in diameter. this is the smallest diameter the laser can cut, without melting too much plexi around. i hope the insects will not pass these holes. they will surely try. when winter coming, a ‘heated’ hotel is very attractive…

as hot air always goes up, the components arrangement is not very fortunate for the sensor, since it is placed exactly above the biggest heat source in the kit1.
i decided to mount the whole device upside down to the wall, this way the bme280 will be under the ethernet module. the ventilation holes should produce a chimney effect, that will take care to transport the air from bottom to top. theoretically, the sensor will always receive the unheated air from outside, obtaining correct readings.
i will test this theory when the device is mounted on the wall, placing an external temperature sensor near the case, and compare the 2 values.

while used as a fix station, the micro usb port will be out of order. hence, it will be covered with a cap, to keep the bugs at bay.

if anyone is interested to build one of these case, here are the corel draw x8 files:
fixed station with bme sensor
portable, without bme sensor

i will add new photos when it will be installed in its final place. for high resolution pictures you can visit: album

thank you radu for all the big effort and helpful attitude in this worldwide project!
thanks for reading,

written in 2016, oradea.

Voltage is not updated in uRADMonitorX for my old A1 model, now with 118 firmware. Maybe due to different prefix spelling? “vol:” vs “voltage:”

webserver:
URADMONITOR 11000003
type:1 hw:100 sw:118 SBM20radiation:18CPM (22.76CPM)
temperature:29.00C

vol:379V (46%/15.50kHz)
uptime:2764s wdt:3s

eth:10.0.0.24 (23.239.13.18)
http:200 46/46

JSON: {“data”:{ “id”:”11000003″,”type”:”1″,”detector”:”SBM20″,”voltage”:378,”cpm”:27,”temperature”:29.89,”uptime”: 160}}

My KIT1 which reports voltage fine in uRADMonitorX

webserver:
uRADMonitor 51000042
type:5 hw:103 sw:115 SBM20radiation:14CPM
average:21CPM
voltage:378V (69%)
ip:10.0.0.23
http:200

JSON: {“data”:{ “id”:”51000042″,”type”:”5″,”detector”:”SBM20″,”cpm”:18,”temperature”:0.00,”uptime”: 70203}}

Thanks for the note about the orientation of the tube, wasn’t sure if it was important. I originally based it on the photos from this blog post which shows the tube installed upside down: https://www.uradmonitor.com/model-kit1-production-ready/

I’ve swapped it around now and am looking for an enclosure to mount it in. Are there any specific requirements? Plastic, metal, height off the ground outdoors? Also if I was to add something like the BME280 would there need to be holes in the enclosure rather than having it watertight?

Regarding powering the device, something like this kit would be very useful: http://www.tp-link.com/en/products/details/cat-4794_TL-POE200.html

It allows you to inject a 12V into the spare cores on an Ethernet cable and pull them out at the other end (it’s an injector and splitter, and not a standard 802.3x POE).

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

so, i just put together the uradmonitor kit1, but i don’t have an isp programmer to upload the hex. but i have a lots of arduinos around…

this guide will show you how to upload the hex file to the uradmonitor kit1, using an arduino uno r3 + windoze

you will need:
– arduino uno
– 6 male to female jumper wires
– latest arduino ide
– hex file

please note: this article is for arduino uno r3, i will not explain here how to use other models. however, with a little googling + thinkering it is not complicated to adapt. for other mcu you can start here.

also, be sure to use tightly fitting jumper cables, you do not want to lose power or data while uploading the hex file! do not move / touch the setup while uploading!

steps:

0) download and install the latest arduino ide + drivers (arduino.cc)

1) open the ide, and go to: file > examples > arduinoisp and open the arduinoisp sketch

2) uncomment line 81 (// #define USE_OLD_STYLE_WIRING)

3) note the com port number in: tools > port (you will need this number later)

4) upload the sketch to the uno r3

5) close the arduino ide

6) remove the display (and ethernet module) from the uradmonitor board

7) unplug the arduino usb cable from the pc. connect the jumper wires as follows (see image):

uno -> kit1

gnd -> 4
5v -> 2
pin 10 (ss) -> 5
pin 11 (mosi) -> 1
pin 12 (miso) -> 9
pin 13 (sck) -> 7

it’s a good idea to write the arduino port numbers on the pcb, for future software upgrades:

8) double check the wiring between the uno and uradmonitor

9) copy ‘avrdude.conf’ file from*: c:\Users\wanek\AppData\Local\Arduino15\packages\arduino\tools\avrdude\6.3.0-arduino6\etc\
to: c:\Users\wanek\AppData\Local\Arduino15\packages\arduino\tools\avrdude\6.3.0-arduino6\bin\

*please note: the path can be slightly different, based on the ide version

10) copy the uradmonitor hex file to: c:\Users\wanek\AppData\Local\Arduino15\packages\arduino\tools\avrdude\6.0.1-arduino6\bin\ and rename to: ‘uradmonitor.hex’

11) open a terminal (go to start > search, type ‘cmd’ then press enter)

12) copy – paste this in the terminal (replace “wanek” with your user name):
cd c:\Users\wanek\AppData\Local\Arduino15\packages\arduino\tools\avrdude\6.3.0-arduino6\bin\

13) connect the arduino to the pc usb port

14) replace xx (use notepad) in step 15 and 16, with the port number you noted in step 4.

15) copy – paste in the terminal:
avrdude -P COMxx -b 19200 -c avrisp -p m328p -v -e -U lfuse:w:0xdc:m -U hfuse:w:0xdf:m

you should see something similar:

16) now enter this:
avrdude -P COMxx -b 19200 -c avrisp -p m328p -v -e -U flash:w:uradmonitor.hex -U lock:w:0x0F:m

it will take a while, but if you’re seeing this, it means you have succeeded!

17) unplug the usb cable, remove the jumper wires, remount the modules and power up the device. it should start up with the uradmonitor logo. now you can connect to the global network.

attention:
if something went wrong, and after hexing there are verification errors, answer no and try again. check the quality of the wiring, do not use too long cables (max. 20cm)

i’m not sure why these errors occur, but once i answered yes, and the process apparently halted. so i closed the terminal and after that, the microcontroller is not working… probably i’ve bricked it.

radhoo has some very detailed article about mcu flashing, here

written in 2016, using arduino ide 1.6.11, on windoze 1607.

hello everyone!

here is a post about my diy kit1, based on the v1.1.104 pcb. it was made with minor modifications / improvements regarding the original model. as radhoo said, maybe other builders will be interested in this, so i published here.

first of all, i’m a beginner in all this electronics and coding stuff, so if i wrote something stupid, please correct me. i’m always open for constructive criticism. second, sorry for my english, it is not my native language, but i’ll try to do my best 🙂

the differences compared to the original kit1 are:
– incorporated lithium battery
– built in battery charger module + micro usb port
– low dropout (0.17v) regulator
– real PoE connectivity, no additional cable / port needed on the device side, just the rj45 connector
– transparent case made from plexiglass

updated bom, with the components i used (if something is missing, please let me know):
BOM, updated

i have built 2 kits: one for me and on for a friend. ha asked to make it portable, because he will use mainly on field, as a mobile unit, outdoors and on industrial working sites.
this raised two challenge: the final product has to have a
– reliable and high capacity rechargeable battery
– a robust but not to bulky case

please note, that the components for these kits i bought from local stores, the best available quality. hence, these components visual aspect are differ from the originals, shipped with the kit1. i measured all of them before soldering, to make sure everything is up to the specs.

regarding the pcbs, after some emails, radhoo was so kind to send me 2 pieces, thank you again! because i didn’t want to ‘destroy’ these beauties, all the modifications are made without hacking the pcb.

power supply / charger / power consumption:

nowadays the “standard” power supply for handheld devices is the type b micro usb port. you can find them virtually everywhere. also, it is fairly easy and very cheap to implement into diy stuff, using these chinese modules:
battery charger, ali

as for the battery, probably everybody has access to some broken smartphones… although the phone or display is broken, chances are good that the battery is still functional. you just have to hook up to the output of the charging module and the input of the voltage stabiliser, it is ready to use.
i’ve used one cell from an old macbook battery, scavenged. it contains 4 lithium cells, similar like on this site:

they are roughly the size of the kit1 pcb. this way, the charger + battery ain’t cost anything to me (0.3 euro).
to keep a safe distance between the batteries aluminum foil and the bottom of the pcb, i’ve used 4 self adhesive rubber shoes, the ones used for furniture feets.

most lithium batteries have a nominal voltage of 3.6v (min 3.0v, max 4.2v). the recommended operating voltage for the kit1 is min 3.0v, max 3.3v. to take maximum use of the battery, i opted for a 3.0v voltage regulator. it has to have ultra low dropout voltage, in order to maximize battery life.
so, i had to replace the original lm1117 voltage stabiliser, lm1117 datasheet, because it has a large dropout voltage, 1.1v. (this would be 3.0 + 1.1 = 4.1v -> maybe just 5% of the overall battery capacity. not too efficient…)

after a lot of searching, i bought the MCP1700-3002E/TO regulator mcp1700 datasheet. it has very low dropout, only 0.17v. it means: 3.0 + 0.17 = 3.17v, i can use around 95% battery capacity. good.
the max output current for the mcp1700 is 250mA, and the max input voltage is 6.0v. as the lithium battery never goes above 4.2v, its ok for me.

to estimate the battery life, i’ve made some measurements:
(because the battery is quite old and tired, the 3700mA nominal capacity was irrelevant)
the kit1 has the following current consumption @ 3.0v (with the red led desoldered from the ethernet module):

offline mode, backlight off: 36mA
backlight: 18mA
online mode, backlight off: 147mA
maximum peak current: 170mA

in online mode, with fully charged battery (4.2v) it took 18 hours to discharge it to 2.9v.
discharging under 2.9v it is harmful for the lithium batteries lithium info, so even if the kit1 kept working at 2.9v, i stopped the measurement. it then took around 5 hours to fully charge the battery (from a usb port).

based on the above current consumption scenarios and the measured 18 hours, it is fairly safe to estimate 50 hours uptime in offline mode. more than adequate for daily use on the field.

this regulator has a different pinout, regarding the original model. i had to make a tricky implementation, but it worked.

at the moment, the only flaw is, that the kit1 keeps working even under 2.7v, over-discharging the battery. in the long run this will damage the lithium cell. the firmware should be modified to post a ‘low battery’ message to the screen and standby the unit, if the voltage drops below 2.85v. (we need to have full access to the source code to implement this)

also, it would be nice to have a voltage divider on the battery terminals (say 4.2v -> 3.0v) and implement a battery voltage monitoring function in the firmware. this way the user can have a feedback about the battery state. there are 2 unused analog pins on the mcu , this shouldn’t be a problem.

the MCP1700 needs 2 filtering capacitors to work properly. i’ve just replaced the original c3 with 1uf ceramic, the other one (cout) was soldered on the back side of the pcb.

because the charger module covered some holes of the on / off switch on the pcb, i’ve used a different switch, placed on the right side of my case:

PoE:

for the stationary unit installed outside, i wanted to have just one single cable (for supply + ethernet).
according to wikipedia poe wiki the poe standard uses 2 modes: A and B.

unfortunately, after some fiddling i’ve realised that none of these modes are implemented in the hr911105a rj45 connector, used on the enc28j60 ethernet modules. rj45 datasheet

what a pity! all the 8 pins are galvanically isolated. i needed access to pins 4+5 for dc+, respectively pins 7+8 for dc-. poe pinouts

custom made ethernet cable: on the router end has an additional usb cable, serving to inject 5v dc. this will be powered from the unused usb port on my router. the other end is just a standard rj45 connector.

hacking the rj45:

it is possible to open the metal sheet on the connector. then i’ve removed some plastic with a red-hot cutter blade, to expose the pins.

the isolation transformers for rx and tx are clearly visible

cleaning and soldering the wires to the selected pins was easy. for tapping i’ve removed one of the lateral side tin. after putting some layers of insulation to the exposed pins i’ve closed the connector.

the terminal wires were soldered to the appropriate INPUT pins (+5v and gnd) on the micro usb charger module. now i have a real poe module!

attention:
do not solder the +5v cable to the charger module OUTPUT, because it will overcharge the lithium battery! lithium batteries, if charged beyond 4.3v can explode or catch fire!

of course, this modification doesn’t deal with the two 75 ohm resistors, which kinda “short” the usb port.

but if you do the math: 2 x 75r = 150r. for 5v / 150r = 33mA extra current consumption for the usb port. the usb port standard specifies at least 500mA / port. the whole device does not absorb more than 200 mA, i think this is on the safe side.

regarding the heat production on the two 75 ohm resistors:
0.033A x 5v = 0,166W total. there are 2 resistors, so this is 0.083W / resistor. even if the resistors will burn out, i do not care, they are useless in this configuration (i think).

please note: using 5v dc with poe is not recommended on long cable runs, because, when load applied, the voltage drops quickly. in my case, i needed 5m ethernet cable. with the device connected, the 5v dropped to 4.3v. this means, that the charger module will output max 4.0 volts, so the battery will be never charged to 100%. this is not a problem for me, as the router will continuously supply the power. for much longer cables, one should consider using a dc to dc booster between the usb port and ethernet cable to compensate for the voltage drop.

bme280:

the v1.1.104 pcb has a nice feature, the extension port. i’ve populated this port with a bme280 module. bme280 specs

you can buy one here: bme ali

these sensors are very high quality and one can obtain a lots of info, with proper code implementation:
– temperature
– pressure
– altitude (uncalibrated)
– relative humidity
– dew point
– heat index (shadow)
– heat index (sunlight)

i’ve wrote a small arduino sketch to display all these values, using the SparkFunBME280 library. bme280 sketch

unfortunately, at the time of writing this article, the uradmonitor source code (v117) is not fully open. we have to wait for radhoo to implement this sensor, or much better, to publish the full source code on github.

case design:

for the device to be fully usable outdoors and to have a better visual experience, needs a case. i’ve designed the case in corel draw x8. made two very similar models, one for wall mounted fix station, one for portable device. despite my very limited knowledge in corel, i managed to finish it with quite good results. it was then laser cut from 3mm clear plexiglass.

since the enc28j60 chip produces a lot of heat, in a closed case this would deteriorate the temperature readings.
i’m interested in the REAL outdoor readings. if the temperature value is not correct, all the other values are useless. the humidity calculation formula is also based on temperature. accordingly, i had to assure a very good ventilation for the sensor.

designed a lots of ventilation holes on strategic parts of the case. these are circles 1.5mm in diameter. this is the smallest diameter the laser can cut, without melting too much plexi around. i hope the insects will not pass these holes. they will surely try. when winter coming, a ‘heated’ hotel is very attractive…

as hot air always goes up, the components arrangement is not very fortunate for the sensor, since it is placed exactly above the biggest heat source in the kit1.
i decided to mount the whole device upside down to the wall, this way the bme280 will be under the ethernet module. the ventilation holes should produce a chimney effect, that will take care to transport the air from bottom to top. theoretically, the sensor will always receive the unheated air from outside, obtaining correct readings.
i will test this theory when the device is mounted on the wall, placing an external temperature sensor near the case, and compare the 2 values.

while used as a fix station, the micro usb port will be out of order. hence, it will be covered with a cap, to keep the bugs at bay.

if anyone is interested to build one of these case, here are the corel draw x8 files:
fixed station with bme sensor
portable, without bme sensor

i will add new photos when it will be installed in its final place. for high resolution pictures you can visit: album

thank you radu for all the big effort and helpful attitude in this worldwide project!
thanks for reading,

written in 2016, oradea.

Voltage is not updated in uRADMonitorX for my old A1 model, now with 118 firmware. Maybe due to different prefix spelling? “vol:” vs “voltage:”

webserver:
URADMONITOR 11000003
type:1 hw:100 sw:118 SBM20radiation:18CPM (22.76CPM)
temperature:29.00C

vol:379V (46%/15.50kHz)
uptime:2764s wdt:3s

eth:10.0.0.24 (23.239.13.18)
http:200 46/46

JSON: {“data”:{ “id”:”11000003″,”type”:”1″,”detector”:”SBM20″,”voltage”:378,”cpm”:27,”temperature”:29.89,”uptime”: 160}}

My KIT1 which reports voltage fine in uRADMonitorX

webserver:
uRADMonitor 51000042
type:5 hw:103 sw:115 SBM20radiation:14CPM
average:21CPM
voltage:378V (69%)
ip:10.0.0.23
http:200

JSON: {“data”:{ “id”:”51000042″,”type”:”5″,”detector”:”SBM20″,”cpm”:18,”temperature”:0.00,”uptime”: 70203}}

Thanks for the note about the orientation of the tube, wasn’t sure if it was important. I originally based it on the photos from this blog post which shows the tube installed upside down: https://www.uradmonitor.com/model-kit1-production-ready/

I’ve swapped it around now and am looking for an enclosure to mount it in. Are there any specific requirements? Plastic, metal, height off the ground outdoors? Also if I was to add something like the BME280 would there need to be holes in the enclosure rather than having it watertight?

Regarding powering the device, something like this kit would be very useful: http://www.tp-link.com/en/products/details/cat-4794_TL-POE200.html

It allows you to inject a 12V into the spare cores on an Ethernet cable and pull them out at the other end (it’s an injector and splitter, and not a standard 802.3x POE).