Dosimeter module RadSens I2C support required #4882
Comments
|
And what would be the best way to test these? |
TD-er
added
Category: Plugin
|
Dear friend, we will check it under normal environmental operating conditions. We won’t go to the nuclear power plant :)) |
|
I recently bought one of those things from Ali (not with a tube like this, which is probably more sensitive to alpha radiation) I don't have any old (greenish coloured) lenses, no 50's red pottery or any old smoke detector. I did order a few of those "magic amulet" thingy which claim to stop radiation and those are for sure as harmful as you wouldn't dare to think. So when adding support for this, I will also add some detailed info on this topic as it for sure needs some warnings on how to use it responsible. |
|
The RadSens sensor will be included in the weather station for round-the-clock environmental monitoring. At the moment, the ESPEasy firmware with pulse counting is used. A Chinese Geiger counter J305 (similar to M4011) is used. Measurement interval 600 seconds, conversion %value%*100/1510. I wanted to switch to a more modern RadSens module with an I2C bus connection. |
|
Just to get an idea of what this I2C version is doing... |
|
The RadSens module has its own microcontroller STМ32, which counts pulses and transmits the finished result via the I2C bus |
|
It would be better, of course, if the developer participates in the forum (I wrote to the ClimateGuard team). Based on the sources, there should be at least three values from RadSens
|
|
I don't think what they're selling is too expensive, absolutely not as the parts alone will cost you at least 35-ish euro. Only main advantage (apart from the relative small size) is that the counter can continue to count when the ESP is in deep sleep for example. |
The website claims it uses max. 50 mA, but it doesn't state if that's with the tube included/installed, as it also claims that for the modules without a tube. |
|
In my case, the rectified voltage will constantly be supplied to the RadSens module and the weather station as a whole. The transition to backup power is carried out from a 18650 lithium battery when the main one is unavailable. |
|
I have reserved P163 as the plugin ID for this sensor. |
The tube itself does not add much to the consumption under normal ambient conditions (assuming you are not in Chernobyl forest), so those 50 mA seem quite realistic for the simple mcu controlled HV power stage. However, best example I had consumed just ~20 uA without load, so there's much space for improvement. |
|
Dear developers, I understand how busy you are in developing the project and maintaining the stability of its work. But can I ask about the RadSens plugin, how soon can we expect support in ESPEasy? |
|
Well the past 2.5 months I have been 100% busy implementing support for ESP-IDF5.1 and adding support for ESP32-C2 and -C6 and IPv6 so we can soon add support for Matter. |
|
Thank you, I understand, if necessary, I can test RadSens remotely on the created versions of ESPEasy |
|
@Vladimir-by I've created a new plugin in PR #5104, and a GH Actions run is working on the build. Edit2: Updated GH Actions run. |
|
We decided to not add this plugin in any default build for ESP8266, as that platform is practically feature-frozen for ESPEasy. For ESP32 this plugin is, besides the |
|
And just to explain why we consider ESP8266 as 'feature frozen'... Some features may not be made to work on the ESP8266 anymore, like encryption or other feature which simply take up too much memory the ESP8266 simply does not have. |
|
Perhaps it's time to announce a strategy for ESP8266, set it aside with current features and move ahead with ESP32 family? |
|
I do not understand in which assembly to look for plugin 0163? |
|
You can use an ESP32 Collection G build for 4MB Flash units, or an ESP32 MAX build for 8MB and 16 MB Flash units. For ESP8266 you'll need to create a Custom build (compile yourself, from source...). |
Yep, that's what I was thinking about. |
|
Made some improvements to the plugin, to use the Count-average (when available) for checking the threshold. A GH Actions run is available here. |
|
Friends, I have a problem when using this plugin. |
|
I guess you're using an ESP8266, I haven't tested that (yet), might have memory capacity issues. Can you test on an ESP32? Edit: To get more detailed info, you can check the log while the page is submitted (extra tab on your browser on the Tools/Log page, or via an USB port on your computer, using some (serial)terminal software). |
No, I'm not using an ESP8266, I'm using a ESP Chip Frequency: | 240 [MHz] and yes, I also noticed that when setting CheckBox Status, if you wait VERY long, the interface comes to life, but in the dev list the Enable dev is false. |
|
1642951: EVENT: Clock#Time=Thu,16:31 |
|
Not sure why you have multiple restarts of the unit. |
@Vladimir-by, try to confirm or deny this error please (see my video) |
@tonhuisman Couldn't attach the video, it's large. I sent taskenable,5 and after that every time ESP went soft reboot If you don't set the STAT flag, there is no problem and everything works GREAT 1 minute later.... 5 min. latter......,.., |
|
Ton already found the issue, new build is pending :) |
|
I've found a small code issue, that I have now fixed 😅. Build should be ready in ca. 40 minutes from this Actions run |
|
I'm glad I was able to be helpful. I have another question, I did not find the data entry field setting “A command for configuring the sensitivity to adjust calibration for a different type of Geiger tube (impulses per microrad).”. Mentioned here https://github.com/letscontrolit/ESPEasy/pull/5104 |
|
That command is to be sent via http, serial or Rules, and is documented in this file in the PR. This will be available in the ESPEasy ReadTheDocs once the PR is merged into Here's a screenshot of how the Commands section will look like in the docs: |
|
I updated, checked, and the problem disappeared |
|
Another question has arisen. I checked with the manufacturer and he replied in the affirmative, “Unless this software (ESPeasy) accumulates them, but the board itself should not accumulate them.” :-( |
|
All values are read from the counter using the available library functions, and presented as received, overwriting previous values in ESPEasy. No autonomous counting or addition is done by ESPEasy on the values. The only 'special' handling is calculating the average value of counts for use as the trigger-delta to smoothen the sensitivity, but that's not stored other than in memory, and can also be seen in a graph when re-opening the Device configuration for the active sensor. |
|
On further investigation, the RadSens library does increment it's count value, without ever resetting it. If resetting the count after each read is the desired behavior, I can add that to the library, and also make it optional in ESPEasy, to either fetch the accumulated count like it is now, or get and reset the last available count. |
|
Rather not try to 'write' it to the sensor. |
|
I wonder if I'll write to the manufacturers, since they insist it should reset. |
Most likely they are talking about the counter, and not the library. So we're both right 😆 I'll fix the library (and make a PR there for my fixes), and add extra options to the plugin, just hang in there for a bit... |
|
@bubastic I've added the requested features to the plugin, a new build is in this Actions run |
|
Build: [ESP_Easy_mega_20240822_max_ESP32_16M1M Aug 22 2024] I was sure MAX included it. |
|
Which build did you try? This build should have it... |
I have received indirect confirmation that the meter does not reset when Count is read, contrary to the technical documentation, and some users confirm this information. I also see that you have made a change to the plugin. Thank you. |
Was sure it was included in the release 22 aug. :-) |
Hm, as I don't own such counter, and currently don't intend to order one, I can't test this myself, so have to depend on you (and others if & when available) for actual testing. And you have done a great job so far 😃. |
|
after updating the latest firmware, |
That's the price you pay for living on the edge... 🤣 |
|
My fixes have been merged in the RadSens library, so that's sort of a success 😃 |
|
That's extremely quick. |
yeah, that's right. And I want to point out that this is after a very long period of silence and the manufacturer's unwillingness to address this problem. Yesterday he wrote that he had made changes to the library |
It didn't happen quickly, it turned out that everyone didn't like it, everyone wrote a lot about it, but the wagon stood still. |
|
Colleagues, I’m joining in testing the plugin [P163] Environment - RadSens I2C radiation counter. There was no opportunity before, I was away. |
|
Thank you, I read the forum thread, the main errors in the firmware and pulse counting have already been corrected. Testing takes place on the platform ESP32-WROVER-B T18_3.0 + 18650 battery, RadSens Board ver-2v7 + Geiger tube SBM20, firmware ESP_Easy_mega_20240823_collection_G_ESP32_4M316k |
|
I am steadily receiving data from the RadSens ver-2v7 board; if additional errors are found, I will write. |
ClimateGuard offers ready-made solutions for environmental monitoring with RadSens and RadSens Mini radiation sensors. Please add this module for I2C operation as part of the ESPEasy firmware.
Links to the ClimateGuard project:
https://climateguard.info/
https://github.com/climateguard/RadSens/
https://climateguard.info/radsens/
https://climateguard.info/radsens_mini/
The text was updated successfully, but these errors were encountered: