Forum Replies Created
You can simply connect them in parallel but that will:
1) increase capacitance -> you’ll need to recalculate the compensation capacitor or add one if there is none
2) increase the count due to combined detection volume -> you’ll need to change the calculations interpreting your CPM to eq. dose rate.
That’s a very nice enclosure!November 16, 2022 at 6:55 pm in reply to: How long does it take for a sensor to show on the public map? #29411
Sorry for the late answer. If you are referring to 82000204 I see this unit is offline since Oct 29. It will not show up unless you check “show offline units” from left menu.
Get it back online so I can have another look at it.
Thanks!October 13, 2022 at 8:56 pm in reply to: How long does it take for a sensor to show on the public map? #29406
hi! by default the map shows “outdoor” units, unless you check the “show indoor” option in the left menu. See picture.
You can configure your unit as indoor or outdoor in the dashboard.
Also, make sure the coordinates are set and that when you look at the map you select a parameter that your unit measures .June 21, 2022 at 11:09 am in reply to: A new all purpose monotoring device for fixed installation? #29340
That’s a wonderful idea, Wolferl, thank you!
Thanks, I will see how this can be done for future releases.
As Wolferl said, we need more input from you.
New devices can be configured via USB to increase the “sendint” interval . This impacts the watchdog directly.
The formula for watchdog reboot in latest Firmware is: 5* SENDINT + 2* WARMUP. Setting the SENDINT to a very high value can limit WD reboots to only a few / month.
This is all explained here: https://www.uradmonitor.com/direct-data-access/
Thanks Wolferl for clarifying this for me
Problem fixed. The unit was flagged on the server for its radiation readings, possible something bad happened in the past.
Also another fix for the unit in Moscow – a DIY KIT1 unit, class 0x13: Link:https://www.uradmonitor.com/?sensor=cpm&open=13000200
It was sending the “Tube type parameter” – index “10” (hex) defined in Exp protocol Link:https://github.com/radhoo/uradmonitor_kit1/blob/master/code/misc/expProtocol.h as “0x1” .
This did not work because of the 0x , therefore your unit’s factor was set to 0, making sievert/h outputs 0. Code on server was modified to check and convert such inputs. It is now all set.
Seems it is up and running: https://uradmonitor.com/tools/dashboard-04/?open=13000214
The unit is online.
What seems to be the problem?
Can you post what you see on all the screens of your KIT1 unit?
Keep it outdoors for a few days so its internal auto-calibration mechanism kicks in.
Hi Richard, you can also use the USB command “default” to do a factory reset , if needed.
The FAN has a dual purpose:
– it pushes air through a narrow path inside the PM sensor
– it pushes air across all sensitive elements
While an open case (A3 Stevenson shield) can take advantage of the natural air convection, wind, or general air movement, the PM sensor will still need a controlled airflow.
So to make this work, the only option to lower noise is to reduce its frequency, using the sleep mode option.
On the other hand, the noise itself is ~35dB near the unit, quite low. If you have the A3 you can evaluate that yourself.
Gopher’s right. You might want to request a RMA. The MOX sensor is very low cost, but sadly we need to arrange shipping the unit back and forth. No other way around this.