Good day to you Anto, just wanted to say thank you so very much for making this project open source and for the time taken to propely document it and have it available most importantly with the code and schematic ! You are AWESOME ! 1 Quick question, can i use a really tiny OLED that has only just started production these days, its really small, 70x40:https://www.aliexpress.com/item/Highlight-0-42-inch-OLED-Display-Screen-LCD-Module-72-40-OLED-Module-IIC-SPI-Interface/33008298116.html?spm=2114.search0104.3.3.1f542648ofCZv1&ws_ab_test=searchweb0_0,searchweb201602_6_10065_10130_10068_10547_319_317_10548_10696_10192_10190_453_10084_454_10083_10618_10307_10820_10301_10821_10303_537_536_10059_10884_10887_321_322_10103,searchweb201603_52,ppcSwitch_0&algo_expid=2bf5646c-c2e5-4397-963c-8223f95d1880-0&algo_pvid=2bf5646c-c2e5-4397-963c-8223f95d1880 Sorry for the long link, i dont know how to shorten these lol What would i need to change in the code, could you kindly help supply the code to help display just the voltage and current in the most simplest way because the OLED is so small, only limited data will be displayed This is because im wanting to make this into an existing tool i made, really simple MT3608 adjustable DC to DC step up converter and i wanted this project to display the output voltage and current. the same i wanted to incorporate this into a few other DC to DC converter projects, all only upto 5amps, probably wont get any higher and maybe upto 30 volts max for the voltage reading. Would you be able to help please please ? the reason why i need this tiny OLED is because i will make a homebrew PCB for it and space is severely LIMITED :( No rush at all, please take your time, id be extremely grateful for the help PS i use cadsoft Eagle for my homebrew PCB's Thanks loads in advance, you are my HERO !!!!

Interesting -- thanks.  I should perhaps go back and test it again -- but I do not think that at either end of the P2 setting I got any sounds other than when there was a signal.  This signal was two small keys jangling together -- which caused sound from the speaker (and 'signal' LED) 7m away from the detector.    I have never heard any 'spurious' sounds from the speaker.  Should I have heard 'unexpected' sounds at some point? (But yes, I can think of many improvements to the project -- I'm not an analogue person, but would add USB-C charging of an internal battery, maybe an SD card to record signals, perhaps bluetooth support for connecting headphones or a martphone app...)

Hi, Why do you discuss about my nice CUDDLY mouse inside this trap ? It's ELECTRONIC PROJECT to describe LoRaWAN : a node, a gateway.... You will use this project for your mailbox... Best regards Jennifer  

In order to enhance 0/1 ratio compensation, I did some improvements on the MCU firmware. The 0/1 ratio is now trimmed at the end of every cluster. The flash program memory address Z=0x00AE contains a constant (now set at 0x24A3) that enables very precise 0/1 ratio trimming.  After all the adjustments of S5,S6 and S7 with help of BSA, the precise trimming of 0/1 can be done by changing the 16-bit value at 0x00AE - increasing this constant increases the number of ones, decreasing it increases the number of zeroes. For even better NIST testing results!

I think you have missed one factor that can make the illogical logical: the law. There is a legal requirement for facilities where food is produced to control pests, and to make sure that dead vermin are removed within 24 hours. Non-compliance is expensive, a facility could potentially be locked down for a period of time after a violation. This is what makes the business case for the 'smart' mouse traps, and indeed it is already being commercially exploited, see for instance https://www.xignal.com/products/xignal-mousetrap.  On a tangent, it is probably more 'humane' to kill a mouse than to catch it alive. The mouse will experience a lot of stress, starve quite quickly, and will probably die shortly after being released anyway...