@nekitoss
I used 3.3V pro mini with regulator removed and powered by Vin pin. Also removed leds from the pro mini.
I used minicore bootloader.
I used the small pir sensors and again removed the regulator to power directly from the pro mini outputs.
After that sleep the node and trigger on interrupt.
Send battery level once a day.
Use inbuilt battery level monitor and not external components that constantly drain power to get battery level.
1.8V is 0% on the graph (not visible yet!) but I have had nodes working below 1.7V It's a matter of luck with that it seems.
Hope this helps you on the right track. I'll try and help if you want.
This is the latest image and still going strong after 18 months. Voltage is at 2.903V
Here is photo of the test example - I need to make a case and produce more of them over winter.....
Here is the same build/code of a window sensor. Similar time frame but hardly triggered.....
@sundberg84
I also on my last work removed the LG33, it's faster
Well this most likely have been provided as info, but else it's here:
Remember to burn new OPTIBOOT 8MHz into the Arduino Pro Mini
and then I also use avrdude with a usbtinyISP to set the fuse to not check battery voltage monitoring, this is done after I have flashed this with Arduino IDE
avrdude -c usbtiny -p m328p -U efuse:w:0x07:m```
Finally solved a lot of problems and checked a lot of mistakes. But now the first version of this device works almost properly :trollface:
I will make a small report in the description asap
@Puneit-Thukral
Could you post your full working sketch please?
I'm revisiting some of my 51822 nodes that have sat collecting dust for a long time and thought i might try to get them working again.
@chbla said in Multiple uses battery RFM69 node:
Can anyone suggest a source for the parts? Are there any sources that you can upload the files by any chance?
If you mean can you upload a BOM to a company and then it generates a basket of the items, then i know that farnell and maybe digikey do this. But i only use this feature that is built into EAGLE pcb designer, so i'm not sure if they support it directly on their websites, might be worth a look.
http://www.farnell.com/
http://www.digikey.co.uk
@NeverDie Thx for appreciating the work done. There will also be an open source part in the future. When and how extensive the open source part will be, remains to be seen. The release of certain information (block diagram, ..., in this post) is related to those open source parts.
There are some OBD solutions, however most of them (in my experience) give back low frequency data put by the car manufacturer on the OBD-bus (CAN, ...). Therefore transients evolving directly from the battery could only be recorded if the manufacturer sends those data accordingly on the bus. Due to the small bandwidth(also because of other car data that have to be sent, ...), such battery data are sent more often once per second or less. Fast battery events (i.e. cranking events, ...) are therefore imperceptible. Unless the manufacturer processes the fast events and then sends them (once per second or less), which is very unlikely if the manufacturer does not market this feature itself. Third parties devices for high frequency sensing costs several hundreds dollars.
In my experience, important battery states (especially the fast ones) are recorded by measuring and processing corresponding data directly on the battery.
I agree with you about the limits related to the communication over Bluetooth. But i think Bluetooth 5.0 will improve a lot. However, WiFi will always remain an important option due to the high data throughput. The combination of both (BLE & WiFi), especially with regard to energy consumption, will gain in importance.
