Testing of energy consumption by Geiger counter GGreg20_V3
Our company has conducted a thorough testing of the power consumption of the Geiger counter module GGreg20_V3, intended for use in DIY projects. The purpose of the study was to…
Our company has conducted a thorough testing of the power consumption of the Geiger counter module GGreg20_V3, intended for use in DIY projects. The purpose of the study was to…
Technical note on manual initial diagnostics of the GGreg20_V3 module with J305 tube to check the main module voltages at the control points and determine the module's operability
Our site and the GGreg20_V3 DIY Geiger counter product are referenced by the author of the book Francesco Riggi, published by Springer in April 2024 under the title Educational and Amateur Geiger Counter Experiments.
We have previously written about how to calculate the coefficients for the SBM20 tube and the J305, tube that come with our Geiger counter module GGreg20_V3 for DIY / IoT…
Copyright 2023 IoT-devices, LLC, Kyiv - Ukraine As participants in the DIY IoT market, we see that the same faulty or exhausted SBM-20 Geiger tubes are resold from hand to…
може сховати лістинг у акордеон? ####### ggreg20_esp8266_esphome.yaml ##### esphome: name: esphome_node1 # Controller Unique Name platform: ESP8266 # Platform type you have to select when creating new yaml-config in ESP Home board: nodemcuv2 # Controller type you have to select when creating new yaml-config in ESP Home wifi: ssid: "YourWiFiSSID" password: "SSIDPassword" # Enable fallback hotspot (captive portal) in case wifi connection fails ap: ssid: "Esphome Node1 Fallback Hotspot" password: "Cpxg9hRIBU7M" captive_portal: # Enable logging logger: # Enable Home Assistant API api: password: "APIpassword" ota: password: "OTApassword" # Just embedded test D3 (GPIO0) button on every ESP8266 Devboard # You can press D3 button several times to simulate incoming GGreg pulses binary_sensor: - platform: gpio name: "D3 Input Button" pin: number: 0 inverted: True mode: INPUT_PULLUP # Here we calc and include to the firmware a power and doze values of ionizing radiation as sensor outputs sensor: - platform: pulse_counter pin: D3 unit_of_measurement: 'mkSv/Hour' name: 'Ionizing Radiation Power' count_mode: rising_edge: DISABLE falling_edge: INCREMENT update_interval: 60s accuracy_decimals: 3 id: my_doze_meter filters: - sliding_window_moving_average: # 5-minutes moving average (MA5) here window_size: 5 send_every: 5 - multiply: 0.0054 # SBM20 tube conversion factor of pulses into mkSv/Hour - platform: integration name: "Total Ionizing Radiation Doze" unit_of_measurement: "mkSv" sensor: my_doze_meter # link entity id to the pulse_counter values above icon: "mdi:radioactive" accuracy_decimals: 5 time_unit: min # integrate values every next minute filters: - multiply: 0.00009 # obtained doze (from mkSv/hour into mkSv/minute) conversion factor: 0.0054 / 60 minutes = 0.00009; so pulses * 0.00009 = doze every next minute, mkSv. ####### END of ggreg20_esp8266_esphome.yaml #####