Hi, General description is available on english version. Sorry for bad translate.

I tested this device yesterday and found some issues. Now, I want to share results. The analog comparator circuit must be modified. AIN0 should left floating (unconnected) and to this pin need connect the internal 1.1V bandgap reference. The 5V_Fail signal must be connected to AIN1 pin. VD7 must be removed and DC-DC will be works all time except power save mode. Need to add the MOSFET for manage LiPo charger, because this IC interrupts accumulator detecting signal (this signal always near 4..5 volts). Need to add the 5V (external) detecting signal to the microcontroller . Many of the components values should be revised. All these remarks will be taken into account in the new revision. Everything else works perfectly! For the first revision of the device, I'm completely satisfied with the result.

@anticimex You are too fast Now the CERN files are uploaded!!

Hello Tilman, this is really a very nice design. I have ordered a pack of PCBs from elecrow, based on your gerber files, and have a few questions: in your BOM you have listed 5 smd-capacitors and 7 smd resistors, but on the PCB i have solderpads for 6 capacitors and 8 resistors. Can you just explain? is there a uniflächentaster-model for 2 ways? i think i have to flash the bootloader first, do you have a tutorial for this, and a sample-sketch for the board? Thank you very much

BTW, I like how you both made a case for it. Very nice!

@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

@pepson pcb2.* - main boards gerbers rfm69c_to_rfm69hc.* - adapter gerbers You need only main board gerbers

In deep Sleep the cunsumption is below 19µA, but i have to send with PA_MAX. On some Windows the open/close frequency is verry high, so the battery is to fast emty. The CR2032 is good, but i want more "lifetime"

You can put 100uf on each even 200uf would not be able to handle only one tx, so.. but you need them at least for coin cells. you would need more capa to handle tx..but the more capa the more time they take for recharging, and the recharging if big, increase internal res of the coin cell and that's not so good too; to prevent this that would need a current resistor limiter..etc a whole balance! On mine for instance, I have 100uF for coincell, 100uF for PIR and 86uf on radio. Fresh varta coincell 3.02V, after multiple presentation tx 2.85V if I remember, not so bad. but that's an homemade pcb. Another notes, it's better to use ceramic capacitor (because of leakage, if you want to optimize), and better smd, but that's not your case I think.

@NeverDie Yes, you are correct - it is based on ATMega1284P. So not relevant My point is that I'd rather stick to the datasheet rather than overclock, but that's just me. And yes I realise that Moteino is overclocking, but the size, voltage and flash are really appealing to me.

@mardah oh... you mean pin change system, not extint. You can use it of course.

Thanks again, learned a lot... I decide to give a try there, I also had a look on some components' datasheet and seems to be what I need... Let's see, if end up getting the boards I'll publish a review here later.

@JahFyahh - I still haven't managed to et round to it. I've been really busy since this project and its still hectic here. I'm sure i read a few reviews somewhere, here or google. Not sure.

Thats perfect.. definitely have to try this.. Thanks!!

Nice! Will be interesting to hear about how long the CR2032 lasts.

@MiKa which box are you referring to? Generic boxes are available here: https://www.mysensors.org/store/boxes

Hello, I'm sorry to insist on this one, but I'm a bit lost.... I could understand that the recommended bootloader is MiniCore. I installed it in my Arduino IDE and after several tries-and-errors I believe I was able to burn the MiniCore bootloader by using an USBasp2 connected to the ICSP on the slim board: /home/jabss/Desktop/arduino-1.8.2/hardware/tools/avr/bin/avrdude -C/root/.arduino15/packages/MiniCore/hardware/avr/2.0.1/avrdude.conf -v -patmega328p -cusbasp -Pusb -e -Ulock:w:0x3f:m -Uefuse:w:0xff:m -Uhfuse:w:0xd7:m -Ulfuse:w:0xe2:m avrdude: Version 6.3, compiled on Jan 17 2017 at 11:00:16 Copyright (c) 2000-2005 Brian Dean, http://www.bdmicro.com/ Copyright (c) 2007-2014 Joerg Wunsch System wide configuration file is "/root/.arduino15/packages/MiniCore/hardware/avr/2.0.1/avrdude.conf" User configuration file is "/home/jabss/.avrduderc" User configuration file does not exist or is not a regular file, skipping Using Port : usb Using Programmer : usbasp AVR Part : ATmega328P Chip Erase delay : 9000 us PAGEL : PD7 BS2 : PC2 RESET disposition : dedicated RETRY pulse : SCK serial program mode : yes parallel program mode : yes Timeout : 200 StabDelay : 100 CmdexeDelay : 25 SyncLoops : 32 ByteDelay : 0 PollIndex : 3 PollValue : 0x53 Memory Detail : Block Poll Page Polled Memory Type Mode Delay Size Indx Paged Size Size #Pages MinW MaxW ReadBack ----------- ---- ----- ----- ---- ------ ------ ---- ------ ----- ----- --------- eeprom 65 20 4 0 no 1024 4 0 3600 3600 0xff 0xff flash 65 6 128 0 yes 32768 128 256 4500 4500 0xff 0xff lfuse 0 0 0 0 no 1 0 0 4500 4500 0x00 0x00 hfuse 0 0 0 0 no 1 0 0 4500 4500 0x00 0x00 efuse 0 0 0 0 no 1 0 0 4500 4500 0x00 0x00 lock 0 0 0 0 no 1 0 0 4500 4500 0x00 0x00 calibration 0 0 0 0 no 1 0 0 0 0 0x00 0x00 signature 0 0 0 0 no 3 0 0 0 0 0x00 0x00 Programmer Type : usbasp Description : USBasp, http://www.fischl.de/usbasp/ avrdude: auto set sck period (because given equals null) avrdude: AVR device initialized and ready to accept instructions Reading | ################################################## | 100% 0.00s avrdude: Device signature = 0x1e950f (probably m328p) avrdude: erasing chip avrdude: auto set sck period (because given equals null) avrdude: reading input file "0x3f" avrdude: writing lock (1 bytes): /home/jabss/Desktop/arduino-1.8.2/hardware/tools/avr/bin/avrdude -C/root/.arduino15/packages/MiniCore/hardware/avr/2.0.1/avrdude.conf -v -patmega328p -cusbasp -Pusb -Uflash:w:/root/.arduino15/packages/MiniCore/hardware/avr/2.0.1/bootloaders/empty/empty.hex:i -Ulock:w:0x0f:m avrdude: Version 6.3, compiled on Jan 17 2017 at 11:00:16 Copyright (c) 2000-2005 Brian Dean, http://www.bdmicro.com/ Copyright (c) 2007-2014 Joerg Wunsch System wide configuration file is "/root/.arduino15/packages/MiniCore/hardware/avr/2.0.1/avrdude.conf" User configuration file is "/home/jabss/.avrduderc" User configuration file does not exist or is not a regular file, skipping Using Port : usb Using Programmer : usbasp AVR Part : ATmega328P Chip Erase delay : 9000 us PAGEL : PD7 BS2 : PC2 RESET disposition : dedicated RETRY pulse : SCK serial program mode : yes parallel program mode : yes Timeout : 200 StabDelay : 100 CmdexeDelay : 25 SyncLoops : 32 ByteDelay : 0 PollIndex : 3 PollValue : 0x53 Memory Detail : Block Poll Page Polled Memory Type Mode Delay Size Indx Paged Size Size #Pages MinW MaxW ReadBack ----------- ---- ----- ----- ---- ------ ------ ---- ------ ----- ----- --------- eeprom 65 20 4 0 no 1024 4 0 3600 3600 0xff 0xff flash 65 6 128 0 yes 32768 128 256 4500 4500 0xff 0xff lfuse 0 0 0 0 no 1 0 0 4500 4500 0x00 0x00 hfuse 0 0 0 0 no 1 0 0 4500 4500 0x00 0x00 efuse 0 0 0 0 no 1 0 0 4500 4500 0x00 0x00 lock 0 0 0 0 no 1 0 0 4500 4500 0x00 0x00 calibration 0 0 0 0 no 1 0 0 0 0 0x00 0x00 signature 0 0 0 0 no 3 0 0 0 0 0x00 0x00 Programmer Type : usbasp Description : USBasp, http://www.fischl.de/usbasp/ avrdude: auto set sck period (because given equals null) Writing | ################################################## | 100% 0.00s avrdude: 1 bytes of lock written avrdude: verifying lock memory against 0x3f: avrdude: load data lock data from input file 0x3f: avrdude: input file 0x3f contains 1 bytes avrdude: reading on-chip lock data: Reading | ################################################## | 100% 0.00s avrdude: verifying ... avrdude: 1 bytes of lock verified avrdude: reading input file "0xff" avrdude: writing efuse (1 bytes): Writing | ################################################## | 100% 0.00s avrdude: 1 bytes of efuse written avrdude: verifying efuse memory against 0xff: avrdude: load data efuse data from input file 0xff: avrdude: input file 0xff contains 1 bytes avrdude: reading on-chip efuse data: Reading | ################################################## | 100% 0.00s avrdude: verifying ... avrdude: 1 bytes of efuse verified avrdude: reading input file "0xd7" avrdude: writing hfuse (1 bytes): Writing | ################################################## | 100% 0.01s avrdude: 1 bytes of hfuse written avrdude: verifying hfuse memory against 0xd7: avrdude: load data hfuse data from input file 0xd7: avrdude: input file 0xd7 contains 1 bytes avrdude: reading on-chip hfuse data: Reading | ################################################## | 100% 0.00s avrdude: verifying ... avrdude: 1 bytes of hfuse verified avrdude: reading input file "0xe2" avrdude: writing lfuse (1 bytes): Writing | ################################################## | 100% 0.00s avrdude: 1 bytes of lfuse written avrdude: verifying lfuse memory against 0xe2: avrdude: load data lfuse data from input file 0xe2: avrdude: input file 0xe2 contains 1 bytes avrdude: reading on-chip lfuse data: Reading | ################################################## | 100% 0.00s avrdude: verifying ... avrdude: 1 bytes of lfuse verified avrdude done. Thank you. avrdude: AVR device initialized and ready to accept instructions Reading | ################################################## | 100% 0.00s avrdude: Device signature = 0x1e950f (probably m328p) avrdude: NOTE: "flash" memory has been specified, an erase cycle will be performed To disable this feature, specify the -D option. avrdude: erasing chip avrdude: auto set sck period (because given equals null) avrdude: reading input file "/root/.arduino15/packages/MiniCore/hardware/avr/2.0.1/bootloaders/empty/empty.hex" avrdude: writing flash (2 bytes): Writing | ################################################## | 100% 0.07s avrdude: 2 bytes of flash written avrdude: verifying flash memory against /root/.arduino15/packages/MiniCore/hardware/avr/2.0.1/bootloaders/empty/empty.hex: avrdude: load data flash data from input file /root/.arduino15/packages/MiniCore/hardware/avr/2.0.1/bootloaders/empty/empty.hex: avrdude: input file /root/.arduino15/packages/MiniCore/hardware/avr/2.0.1/bootloaders/empty/empty.hex contains 2 bytes avrdude: reading on-chip flash data: Reading | ################################################## | 100% 0.04s avrdude: verifying ... avrdude: 2 bytes of flash verified avrdude: reading input file "0x0f" avrdude: writing lock (1 bytes): Writing | ################################################## | 100% 0.01s avrdude: 1 bytes of lock written avrdude: verifying lock memory against 0x0f: avrdude: load data lock data from input file 0x0f: avrdude: input file 0x0f contains 1 bytes avrdude: reading on-chip lock data: Reading | ################################################## | 100% 0.00s avrdude: verifying ... avrdude: 1 bytes of lock verified avrdude done. Thank you. Just for reference, the parameters were: Board: Atmega328 Bootloader: No (only worked this way, but still not sure what this means: If is already a bootloader on the chip, or if we want to write a bootloader) Variant: 328P BOD: Disabled Clock: 8Mhz internal (here I think its what we want to configure on the target chip - I wasn't sure what was about because it could also have been the clock frequency of the programmer) Compiler LTO: Disabled Programer: USBASP Anyway, after this supposed success message, I believe I have a MiniCore bootloader in the chip and now it should be able to be programed with the AVRISPMKII (with the usb/serial programing adapter I use to program my mini-pros). However, I'm not able to get it working. Maybe I'm choosing the wrong definitions in the arduino IDE. As board definition, I'm using the same as when burning the bootloader: Board: Atmega328 (from the minicore subset) Bootloader: Yes Variant: 328P BOD: Disabled Clock: 8Mhz internal Compiler LTO: Disabled Programer: AVRISPMKII For instance, to load the ascii table example (for testing purposes), I get this error: Insert Code Build options changed, rebuilding all Sketch uses 2330 bytes (7%) of program storage space. Maximum is 32256 bytes. Global variables use 308 bytes (15%) of dynamic memory, leaving 1740 bytes for local variables. Maximum is 2048 bytes. /home/jabss/Desktop/arduino-1.8.2/hardware/tools/avr/bin/avrdude -C/root/.arduino15/packages/MiniCore/hardware/avr/2.0.1/avrdude.conf -v -patmega328p -carduino -P/dev/ttyUSB0 -b38400 -D -Uflash:w:/tmp/arduino_build_636369/ASCIITable.ino.hex:i avrdude: Version 6.3, compiled on Jan 17 2017 at 11:00:16 Copyright (c) 2000-2005 Brian Dean, http://www.bdmicro.com/ Copyright (c) 2007-2014 Joerg Wunsch System wide configuration file is "/root/.arduino15/packages/MiniCore/hardware/avr/2.0.1/avrdude.conf" User configuration file is "/home/jabss/.avrduderc" User configuration file does not exist or is not a regular file, skipping Using Port : /dev/ttyUSB0 Using Programmer : arduino Overriding Baud Rate : 38400 avrdude: stk500_recv(): programmer is not responding avrdude: stk500_getsync() attempt 1 of 10: not in sync: resp=0x00 avrdude: stk500_recv(): programmer is not responding avrdude: stk500_getsync() attempt 2 of 10: not in sync: resp=0x00 avrdude: stk500_recv(): programmer is not responding avrdude: stk500_getsync() attempt 3 of 10: not in sync: resp=0x00 avrdude: stk500_recv(): programmer is not responding avrdude: stk500_getsync() attempt 4 of 10: not in sync: resp=0x00 avrdude: stk500_recv(): programmer is not responding avrdude: stk500_getsync() attempt 5 of 10: not in sync: resp=0x00 avrdude: stk500_recv(): programmer is not responding avrdude: stk500_getsync() attempt 6 of 10: not in sync: resp=0x00 avrdude: stk500_recv(): programmer is not responding avrdude: stk500_getsync() attempt 7 of 10: not in sync: resp=0x00 avrdude: stk500_recv(): programmer is not responding avrdude: stk500_getsync() attempt 8 of 10: not in sync: resp=0x00 avrdude: stk500_recv(): programmer is not responding avrdude: stk500_getsync() attempt 9 of 10: not in sync: resp=0x00 avrdude: stk500_recv(): programmer is not responding avrdude: stk500_getsync() attempt 10 of 10: not in sync: resp=0x00 avrdude done. Thank you. Problem uploading to board. See http://www.arduino.cc/en/Guide/Troubleshooting#upload for suggestions. Any hint on what I may be doing wrong? Thanks,

When you read the data sheet correctly you can see, that the distance between the pins is different for a AA and AAA battery holder. That`s why I was asking if somebody can recommend a holder that fits.

@sundberg84 thank you for clarification. I expected email right after making an order. So, I will wait for finishing production and shipment.

@fets So far, I have only built the 5x5 board (but the others should be schematically identical). The only issue I have found so far is that I cannot get the ISP port to work. But I have checked and I have an identical setup on the 1.0 board and that worked, so I suspect the programmer is too weak to drive the net on this one. So it is not a board-issue per se, and might only be an issue on the 5x5 board as routing is the most complex on that one due to the size.

Since some people people have found this useful I'm posting an update. Six months have passed and I'm very happy with the results. The nodes using the 4 second sleep are barely now into the nominal voltage of two AA batteries (3V) and I think those can last a copule of years like that. The 2 second sleep node is dipping a lot faster, but I suspect that the cause is the Si7021 taking readings every 3minutes that is accelerating the decline, even then I think this one could almost make it to a year.

Thank Sensor ready work. (I have not valid binary Optiboot)

@NeverDie Perhaps but the design is a bit too simple and unoriginal. I'd have to clean up the files a bit and I haven't touched Eagle since I made this board several years ago.

http://forum.mysensors.org/topic/802/mqtt-and-batterylevel/2

Looks like it has been a year or two now. Is it still going on the original battery?

Hi @tbowmo, do you mind to explain a bit about the design? I'm interested with your design. I will use these steps for removing voltage regulator, http://goo.gl/CsZaNg So the design will be battery > external step up regulator (http://goo.gl/PFt99R - to stabilize 3.3v) > vcc pin ? with these then I can use my first post design? Thanks

@dzairo there is a nice PinChangeInterrupt library that you may want to look at.

@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```