Sophi KravitzThe setup:
Measure battery voltage (but use benchtop power supply so I can adjust it quickly), check corresponding analog measurement, and check voltage coming out of v-boost (how long will it boost to 3.3V). Analog measurement is sent over the radio to another board which is plugged into the serial monitor. The board taking the measurements is only on benchtop supply power.
The transmitting board has zero LEDs on except for blinking with TX.
Test 1:
| Battery 1.5 1.4 1.3 1.2 1.1 1.0 0.9 | Analog 712 708 701 697 687 676 too low |
Boost 3.3 3.3 3.3 3.262 3.261 2.8 |
Test 2:
Send data from a full battery and measure how long it lasts.
8 LEDS full on. Unfortunately they are yellow-white LEDs from the floor -shrug, no clue what they are- we can call them 20 mA.
UPDATE: it lasted 2 hours.
| Battery (volts) 1.5 (fresh battery) 1.1 (doesn't comm) | Analog
708 (timestamp 16:15:37) 675 (timestamp 18:15:12) |
TODO:
-Figure out conflict between Radiohead library interrupts and Atmega 328 native.
-Add interrupt 0 to code (interrupt 1 won't work with Radiohead)
-Look at battery datasheet, make a table with a couple of different ones.
-Figure out how to program board via UART (reset does not pull down, not sure why)
Discussions
Become a Hackaday.io Member
Create an account to leave a comment. Already have an account? Log In.
Your testing setup and initial results offer a clear insight into the performance characteristics of the v-boost circuit under various conditions. It's interesting to see how the v-boost manages to maintain 3.3V output down to a battery voltage of 1.2V, after which the efficiency drops, as evidenced by your test results. The second test's focus on battery longevity under a specific load (8 LEDs) provides practical data on power consumption and efficiency, which is valuable for understanding the real-world application of your setup.
The action items listed are crucial for refining the project. Resolving the conflict between the Radiohead library interrupts and the Atmega 328's native functions will significantly enhance the reliability of your system. Additionally, integrating an interrupt 0 into your code could open up new possibilities for your project, potentially improving its responsiveness and efficiency.
Exploring different batteries and documenting their performance will offer comprehensive insights that could guide the selection of the most suitable power source for your application. Lastly, troubleshooting the UART programming issue is vital for streamlining the development process, suggesting a deeper dive into the board's hardware configuration might be necessary.
Overall, I would say your methodical approach to testing and troubleshooting is commendable. It lays a solid foundation for further optimization and development of your project.
My site: TheUpdate.Ng
Are you sure? yes | no
Nice information. I love this blog
https://www.techfiver.com/
Are you sure? yes | no
Being a blogger has been my side dream. It was more fun considering the fact that you can make money from it. What's more fun than doing what you love and making money from it. <a href="https://www.tecteem.com/wapquick-tv-series-movies-videos-games-www-wapquick-com/">Reading this article</a>, I had a new perspective and definitely some hints. Thanks, Amigo!
I would be glad if you read https://www.tecteem.com/toxicwap-download-free-tv-series-musics-movies-games-videos-toxicwap-com/
Are you sure? yes | no
great test idea, I should start doing this myself!
Are you sure? yes | no